- ** .pp
- ** 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.
- ** .pp
- ** Also see the ``$$record'' variable.
- */
- { "force_buffy_check", DT_BOOL, R_NONE, OPTFORCEBUFFYCHECK, 0 },
- /*
- ** .pp
- ** When \fIset\fP, it causes mutt-ng to check for new mail when the
- ** \fIbuffy-list\fP command is invoked. When \fIunset\fP, \fIbuffy_list\fP
- ** will just list all mailboxes which are already known to have new mail.
- ** .pp
- ** Also see the following variables: ``$$timeout'', ``$$mail_check'' and
- ** ``$$imap_mail_check''.
- */
- { "forward_decode", DT_BOOL, R_NONE, OPTFORWDECODE, 1 },
- /*
- ** .pp
- ** 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 \fIunset\fP,
- ** otherwise ``$$mime_forward_decode'' is used instead.
- */
- { "forw_decode", DT_SYN, R_NONE, UL "forward_decode", 0 },
- /*
- */
- { "forward_edit", DT_QUAD, R_NONE, OPT_FORWEDIT, M_YES },
- /*
- ** .pp
- ** 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''.
- */
- { "forward_format", DT_STR, R_NONE, UL &ForwFmt, UL "[%a: %s]" },
- /*
- ** .pp
- ** This variable controls the default subject when forwarding a message.
- ** It uses the same format sequences as the ``$$index_format'' variable.
- */
- { "forw_format", DT_SYN, R_NONE, UL "forward_format", 0 },
- /*
- */
- { "forward_quote", DT_BOOL, R_NONE, OPTFORWQUOTE, 0 },
- /*
- ** .pp
- ** When \fIset\fP forwarded messages included in the main body of the
- ** message (when ``$$mime_forward'' is \fIunset\fP) will be quoted using
- ** ``$$indent_string''.
- */
- { "forw_quote", DT_SYN, R_NONE, UL "forward_quote", 0 },
- /*
- */
- { "from", DT_ADDR, R_NONE, UL &From, UL 0 },
- /*
- ** .pp
- ** When set, 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.
- ** .pp
- ** Defaults to the contents of the environment variable EMAIL.
- */
- { "gecos_mask", DT_RX, R_NONE, UL &GecosMask, UL "^[^,]*" },
- /*
- ** .pp
- ** A regular expression used by mutt-ng to parse the GECOS field of a password
- ** entry when expanding the alias. By default the regular expression is set
- ** to "^[^,]*" which will return the string up to the first "," encountered.
- ** If the GECOS field contains a string like "lastname, firstname" then you
- ** should set the gecos_mask=".*".
- ** .pp
- ** 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".
- */
-#ifdef USE_NNTP
- { "group_index_format", DT_STR, R_BOTH, UL &GroupFormat, UL "%4C %M%N %5s %-45.45f %d" },
- /*
- ** .pp
- ** Availability: NNTP
- **
- ** .pp
- ** 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()-like sequences:
- ** .pp
- ** .ts
- ** %C current newsgroup number
- ** %d description of newsgroup (becomes from server)
- ** %f newsgroup name
- ** %M - if newsgroup not allowed for direct post (moderated for example)
- ** %N N if newsgroup is new, u if unsubscribed, blank otherwise
- ** %n number of new articles in newsgroup
- ** %s number of unread articles in newsgroup
- ** %>X right justify the rest of the string and pad with character "X"
- ** %|X pad to the end of the line with character "X"
- ** .te
- */
-#endif
- { "hdr_format", DT_SYN, R_NONE, UL "index_format", 0 },
- /*
- */
- { "hdrs", DT_BOOL, R_NONE, OPTHDRS, 1 },
- /*
- ** .pp
- ** When unset, the header fields normally added by the ``$my_hdr''
- ** command are not created. This variable \fImust\fP 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.
- */
- { "header", DT_BOOL, R_NONE, OPTHEADER, 0 },
- /*
- ** .pp
- ** 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.
- */
- { "help", DT_BOOL, R_BOTH, OPTHELP, 1 },
- /*
- ** .pp
- ** When set, help lines describing the bindings for the major functions
- ** provided by each menu are displayed on the first line of the screen.
- ** .pp
- ** \fBNote:\fP 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.
- */
- { "hidden_host", DT_BOOL, R_NONE, OPTHIDDENHOST, 0 },
- /*
- ** .pp
- ** When set, mutt-ng will skip the host name part of ``$$hostname'' variable
- ** when adding the domain part to addresses. This variable does not
- ** affect the generation of Message-IDs, and it will not lead to the
- ** cut-off of first-level domains.
- */
- { "hide_limited", DT_BOOL, R_TREE|R_INDEX, OPTHIDELIMITED, 0 },
- /*
- ** .pp
- ** When set, mutt-ng will not show the presence of messages that are hidden
- ** by limiting, in the thread tree.
- */
- { "hide_missing", DT_BOOL, R_TREE|R_INDEX, OPTHIDEMISSING, 1 },
- /*
- ** .pp
- ** When set, mutt-ng will not show the presence of missing messages in the
- ** thread tree.
- */
- { "hide_thread_subject", DT_BOOL, R_TREE|R_INDEX, OPTHIDETHREADSUBJECT, 1 },
- /*
- ** .pp
- ** 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.
- */
- { "hide_top_limited", DT_BOOL, R_TREE|R_INDEX, OPTHIDETOPLIMITED, 0 },
- /*
- ** .pp
- ** 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.
- */
- { "hide_top_missing", DT_BOOL, R_TREE|R_INDEX, OPTHIDETOPMISSING, 1 },
- /*
- ** .pp
- ** 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.
- */
- { "history", DT_NUM, R_NONE, UL &HistSize, 10 },
- /*
- ** .pp
- ** This variable controls the size (in number of strings remembered) of
- ** the string history buffer. The buffer is cleared each time the
- ** variable is set.
- */
- { "honor_followup_to", DT_QUAD, R_NONE, OPT_MFUPTO, M_YES },
- /*
- ** .pp
- ** This variable controls whether or not a Mail-Followup-To header is
- ** honored when group-replying to a message.
- */
- { "hostname", DT_STR, R_NONE, UL &Fqdn, 0 },
- /*
- ** .pp
- ** Specifies the hostname to use after the ``@'' in local e-mail
- ** addresses. This overrides the compile time definition obtained from
- ** /etc/resolv.conf.
- */
- { "ignore_list_reply_to", DT_BOOL, R_NONE, OPTIGNORELISTREPLYTO, 0 },
- /*
- ** .pp
- ** Affects the behaviour of the \fIreply\fP function when replying to
- ** messages from mailing lists. When set, if the ``Reply-To:'' field is
- ** set to the same value as the ``To:'' field, Mutt-ng assumes that the
- ** ``Reply-To:'' field was set by the mailing list to automate responses
- ** to the list, and will ignore this field. To direct a response to the
- ** mailing list when this option is set, use the \fIlist-reply\fP
- ** function; \fIgroup-reply\fP will reply to both the sender and the
- ** list.
- */
-#ifdef USE_IMAP
- { "imap_authenticators", DT_STR, R_NONE, UL &ImapAuthenticators, UL 0 },
- /*
- ** .pp
- ** Availability: IMAP
- **
- ** .pp
- ** This is a colon-delimited list of authentication methods mutt-ng may
- ** attempt to use to log in to an IMAP server, in the order mutt-ng should
- ** try them. Authentication methods are either 'login' or the right
- ** side of an IMAP 'AUTH=xxx' capability string, eg 'digest-md5', 'gssapi'
- ** or 'cram-md5'. This parameter is case-insensitive. If this
- ** parameter is unset (the default) mutt-ng will try all available methods,
- ** in order from most-secure to least-secure.
- ** .pp
- ** Example: set imap_authenticators="gssapi:cram-md5:login"
- ** .pp
- ** \fBNote:\fP 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.
- */
- { "imap_delim_chars", DT_STR, R_NONE, UL &ImapDelimChars, UL "/." },
- /*
- ** .pp
- ** Availability: IMAP
- **
- ** .pp
- ** 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 \fIfolder\fP variable.
- */
-# if defined(USE_SSL) || defined(USE_GNUTLS)
- { "imap_force_ssl", DT_BOOL, R_NONE, OPTIMAPFORCESSL, 0 },
- /*
- ** .pp
- ** Availability: IMAP and SSL or IMAP and GNUTLS
- **
- ** .pp
- ** If this variable is set, Mutt-ng will always use SSL when
- ** connecting to IMAP servers.
- */
-# endif
- { "imap_headers", DT_STR, R_INDEX, UL &ImapHeaders, UL 0},
- /*
- ** .pp
- ** Availability: IMAP
- **
- ** .pp
- ** 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. \fBNote:\fP This is a space separated list.
- */
- { "imap_home_namespace", DT_STR, R_NONE, UL &ImapHomeNamespace, UL 0},
- /*
- ** .pp
- ** Availability: IMAP
- **
- ** .pp
- ** 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.
- */
- { "imap_keepalive", DT_NUM, R_NONE, UL &ImapKeepalive, 900 },
- /*
- ** .pp
- ** Availability: IMAP
- **
- ** .pp
- ** 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.
- */
- { "imap_list_subscribed", DT_BOOL, R_NONE, OPTIMAPLSUB, 0 },
- /*
- ** .pp
- ** Availability: IMAP
- **
- ** .pp
- ** 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 \fItoggle-subscribed\fP function.
- */
- { "imap_mail_check", DT_NUM, R_NONE, UL &ImapBuffyTimeout, 5 },
- /*
- ** .pp
- ** 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.
- ** .pp
- ** It defaults to the default value of ``$mail_check'' which is 5 seconds. But
- ** you may want to increase it.
- */
- { "imap_pass", DT_STR, R_NONE, UL &ImapPass, UL 0 },
- /*
- ** .pp
- ** Availability: IMAP
- **
- ** .pp
- ** Specifies the password for your IMAP account. If unset, Mutt-ng will
- ** prompt you for your password when you invoke the fetch-mail function.
- ** \fBWarning\fP: you should only use this option when you are on a
- ** fairly secure machine, because the superuser can read your muttngrc even
- ** if you are the only one who can read the file.
- */
- { "imap_passive", DT_BOOL, R_NONE, OPTIMAPPASSIVE, 1 },
- /*
- ** .pp
- ** Availability: IMAP
- **
- ** .pp
- ** 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.
- */
- { "imap_peek", DT_BOOL, R_NONE, OPTIMAPPEEK, 1 },
- /*
- ** .pp
- ** Availability: IMAP
- **
- ** .pp
- ** 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.
- */
- { "imap_reconnect", DT_QUAD, R_NONE, OPT_IMAPRECONNECT, M_ASKYES },
- /*
- ** .pp
- ** Availability: IMAP
- **
- ** .pp
- ** Controls whether or not Mutt-ng will try to reconnect to IMAP server when
- ** the connection is lost.
- */
- { "imap_servernoise", DT_BOOL, R_NONE, OPTIMAPSERVERNOISE, 1 },
- /*
- ** .pp
- ** Availability: IMAP
- **
- ** .pp
- ** 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.
- */
- { "imap_user", DT_STR, R_NONE, UL &ImapUser, UL 0 },
- /*
- ** .pp
- ** Availability: IMAP
- **
- ** .pp
- ** Your login name on the IMAP server.
- ** .pp
- ** This variable defaults to your user name on the local machine.
- */
-#endif
- { "implicit_autoview", DT_BOOL,R_NONE, OPTIMPLICITAUTOVIEW, 0},
- /*
- ** .pp
- ** If set to ``yes'', mutt-ng will look for a mailcap entry with the
- ** copiousoutput flag set for \fIevery\fP 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.
- */
- { "include", DT_QUAD, R_NONE, OPT_INCLUDE, M_ASKYES },
- /*
- ** .pp
- ** Controls whether or not a copy of the message(s) you are replying to
- ** is included in your reply.
- */
- { "include_onlyfirst", DT_BOOL, R_NONE, OPTINCLUDEONLYFIRST, 0},
- /*
- ** .pp
- ** Controls whether or not Mutt-ng includes only the first attachment
- ** of the message you are replying.
- */
- { "indent_string", DT_STR, R_NONE, UL &Prefix, UL "> " },
- /*
- ** .pp
- ** 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.
- */
- { "indent_str", DT_SYN, R_NONE, UL "indent_string", 0 },
- /*
- */
- { "index_format", DT_STR, R_BOTH, UL &HdrFmt, UL "%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s" },
- /*
- ** .pp
- ** This variable allows you to customize the message index display to
- ** your personal taste.
- ** .pp
- ** ``Format strings'' are similar to the strings used in the ``C''
- ** function printf to format output (see the man page for more detail).
- ** The following sequences are defined in Mutt-ng:
- ** .pp
- ** .dl
- ** .dt %a .dd address of the author
- ** .dt %A .dd reply-to address (if present; otherwise: address of author)
- ** .dt %b .dd filename of the original message folder (think mailBox)
- ** .dt %B .dd the list to which the letter was sent, or else the folder name (%b).
- ** .dt %c .dd number of characters (bytes) in the message
- ** .dt %C .dd current message number
- ** .dt %d .dd date and time of the message in the format specified by
- ** ``date_format'' converted to sender's time zone
- ** .dt %D .dd date and time of the message in the format specified by
- ** ``date_format'' converted to the local time zone
- ** .dt %e .dd current message number in thread
- ** .dt %E .dd number of messages in current thread
- ** .dt %f .dd entire From: line (address + real name)
- ** .dt %F .dd author name, or recipient name if the message is from you
- ** .dt %H .dd spam attribute(s) of this message
- ** .dt %g .dd newsgroup name (if compiled with nntp support)
- ** .dt %i .dd message-id of the current message
- ** .dt %l .dd number of lines in the message (does not work with maildir,
- ** mh, and possibly IMAP folders)
- ** .dt %L .dd 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.
- ** .dt %m .dd total number of message in the mailbox
- ** .dt %M .dd number of hidden messages if the thread is collapsed.
- ** .dt %N .dd message score
- ** .dt %n .dd author's real name (or address if missing)
- ** .dt %O .dd (_O_riginal save folder) Where mutt-ng would formerly have
- ** stashed the message: list name or recipient name if no list
- ** .dt %s .dd subject of the message
- ** .dt %S .dd status of the message (N/D/d/!/r/\(as)
- ** .dt %t .dd `to:' field (recipients)
- ** .dt %T .dd the appropriate character from the $$to_chars string
- ** .dt %u .dd user (login) name of the author
- ** .dt %v .dd first name of the author, or the recipient if the message is from you
- ** .dt %W .dd name of organization of author (`organization:' field)
- ** .dt %y .dd `x-label:' field, if present
- ** .dt %Y .dd `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'.
- ** .dt %Z .dd message status flags
- ** .dt %{fmt} .dd 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
- ** .dt %[fmt] .dd 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
- ** .dt %(fmt) .dd the local date and time when the message was received.
- ** ``fmt'' is expanded by the library function ``strftime'';
- ** a leading bang disables locales
- ** .dt %<fmt> .dd the current local time. ``fmt'' is expanded by the library
- ** function ``strftime''; a leading bang disables locales.
- ** .dt %>X .dd right justify the rest of the string and pad with character "X"
- ** .dt %|X .dd pad to the end of the line with character "X"
- ** .de
- ** .pp
- ** See also: ``$$to_chars''.
- */
-#ifdef USE_NNTP
- { "inews", DT_PATH, R_NONE, UL &Inews, UL "" },
- /*
- ** .pp
- ** Availability: NNTP
- **
- ** .pp
- ** If set, specifies the program and arguments used to deliver news posted
- ** by Mutt-ng. Otherwise, mutt-ng posts article using current connection to
- ** news server. The following printf-style sequence is understood:
- ** .pp
- ** .ts
- ** %s newsserver name
- ** .te
- ** .pp
- ** Example: set inews="/usr/local/bin/inews -hS"
- */
-#endif
- { "ispell", DT_PATH, R_NONE, UL &Ispell, UL ISPELL },
- /*
- ** .pp
- ** How to invoke ispell (GNU's spell-checking software).
- */
- { "keep_flagged", DT_BOOL, R_NONE, OPTKEEPFLAGGED, 0 },
- /*
- ** .pp
- ** 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.
- */
- { "locale", DT_STR, R_BOTH, UL &Locale, UL "C" },
- /*
- ** .pp
- ** The locale used by \fIstrftime(3)\fP to format dates. Legal values are
- ** the strings your system accepts for the locale variable \fILC_TIME\fP.
- */
- { "list_reply", DT_QUAD, R_NONE, OPT_LISTREPLY, M_NO },
- /*
- ** .pp
- ** 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.
- */
- { "max_line_length", DT_NUM, R_NONE, UL &MaxLineLength, 0 },
- /*
- ** .pp
- ** When set, the maximum line length for displaying f=f messages is limited
- ** to this length. A value of 0 (which is also the default) means that the
- ** maximum line length is determined by the terminal width and $$wrapmargin.
- */
- { "mail_check", DT_NUM, R_NONE, UL &BuffyTimeout, 5 },
- /*
- ** .pp
- ** This variable configures how often (in seconds) mutt-ng should look for
- ** new mail.
- */
- { "mailcap_path", DT_STR, R_NONE, UL &MailcapPath, 0 },
- /*
- ** .pp
- ** This variable specifies which files to consult when attempting to
- ** display MIME bodies not directly supported by Mutt-ng.
- */
- { "mailcap_sanitize", DT_BOOL, R_NONE, OPTMAILCAPSANITIZE, 1 },
- /*
- ** .pp
- ** 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.
- ** .pp
- ** \fBDON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE
- ** DOING!\fP
- */
-#if USE_HCACHE
-
- { "header_cache", DT_PATH, R_NONE, UL &HeaderCache, 0 },
- /*
- ** .pp
- ** Availability: Header Cache
- **
- ** .pp
- ** 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 and so no
- ** header caching will be used.
- */
- { "maildir_header_cache_verify", DT_BOOL, R_NONE, OPTHCACHEVERIFY, 1 },
- /*
- ** .pp
- ** Availability: Header Cache
- **
- ** .pp
- ** 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.
- */
- { "header_cache_pagesize", DT_STR, R_NONE, UL &HeaderCachePageSize, UL "16384" },
- /*
- ** .pp
- ** Availability: Header Cache
- **
- ** .pp
- ** Change the maildir header cache database page size. Too large
- ** or too small of a page size for the common header can waste
- ** space, memory effectiveness, or CPU time. The default should be more or
- ** less the best you can get. For details google after mutt-ng maildir header
- ** cache (first hit).
- */
-#endif /* USE_HCACHE */
- { "maildir_trash", DT_BOOL, R_NONE, OPTMAILDIRTRASH, 0 },
- /*
- ** .pp
- ** If set, messages marked as deleted will be saved with the maildir
- ** (T)rashed flag instead of unlinked. \fBNOTE:\fP this only applies
- ** to maildir-style mailboxes. Setting it will have no effect on other
- ** mailbox types.
- */
- { "mark_old", DT_BOOL, R_BOTH, OPTMARKOLD, 1 },
- /*
- ** .pp
- ** Controls whether or not mutt-ng marks \fInew\fP \fBunread\fP
- ** messages as \fIold\fP 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.
- */
- { "markers", DT_BOOL, R_PAGER, OPTMARKERS, 1 },
- /*
- ** .pp
- ** 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.
- */
- { "mask", DT_RX, R_NONE, UL &Mask, UL "!^\\.[^.]" },
- /*
- ** .pp
- ** A regular expression used in the file browser, optionally preceded by
- ** the \fInot\fP operator ``!''. Only files whose names match this mask
- ** will be shown. The match is always case-sensitive.
- */
- { "mbox", DT_PATH, R_BOTH, UL &Inbox, UL "~/mbox" },
- /*
- ** .pp
- ** This specifies the folder into which read mail in your ``$$spoolfile''
- ** folder will be appended.
- */
- { "operating_system", DT_STR, R_NONE, UL&OperatingSystem, 0 },
- /*
- ** .pp
- ** This specifies the operating system name for the User-Agent header. If
- ** this is unset, it will be set to the operating system name that uname(2)
- ** returns. If uname(2) fails, "UNIX" will be used.
- */
- { "sidebar_delim", DT_STR, R_BOTH, UL &SidebarDelim, UL "|" },
- /*
- ** .pp
- ** This specifies the delimiter between the sidebar (if visible) and
- ** other screens.
- */
- { "sidebar_visible", DT_BOOL, R_BOTH, OPTMBOXPANE, 0 },
- /*
- ** .pp
- ** This specifies whether or not to show the mailbox list pane.
- */
- { "sidebar_width", DT_NUM, R_BOTH, UL &SidebarWidth, 0 },
- /*
- ** .pp
- ** The width of the mailbox list pane (left sidebar like in GUIs).
- */
- { "mbox_type", DT_MAGIC,R_NONE, UL &DefaultMagic, M_MBOX },
- /*
- ** .pp
- ** The default mailbox type used when creating new folders. May be any of
- ** mbox, MMDF, MH and Maildir.
- */
- { "metoo", DT_BOOL, R_NONE, OPTMETOO, 0 },
- /*
- ** .pp
- ** If unset, Mutt-ng will remove your address (see the ``alternates''
- ** command) from the list of recipients when replying to a message.
- */
- { "menu_context", DT_NUM, R_NONE, UL &MenuContext, 0 },
- /*
- ** .pp
- ** This variable controls the number of lines of context that are given
- ** when scrolling through menus. (Similar to ``$$pager_context''.)
- */
- { "menu_scroll", DT_BOOL, R_NONE, OPTMENUSCROLL, 0 },
- /*
- ** .pp
- ** When \fIset\fP, menus will be scrolled up or down one line when you
- ** attempt to move across a screen boundary. If \fIunset\fP, the screen
- ** is cleared and the next or previous page of the menu is displayed
- ** (useful for slow links to avoid many redraws).
- */
- { "meta_key", DT_BOOL, R_NONE, OPTMETAKEY, 0 },
- /*
- ** .pp
- ** 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''.
- */
- { "mh_purge", DT_BOOL, R_NONE, OPTMHPURGE, 0 },
- /*
- ** .pp
- ** When unset, mutt-ng will mimic mh's behaviour and rename deleted messages
- ** to \fI,<old file name>\fP in mh folders instead of really deleting
- ** them. If the variable is set, the message files will simply be
- ** deleted.
- */
- { "mh_seq_flagged", DT_STR, R_NONE, UL &MhFlagged, UL "flagged" },
- /*
- ** .pp
- ** The name of the MH sequence used for flagged messages.
- */
- { "mh_seq_replied", DT_STR, R_NONE, UL &MhReplied, UL "replied" },
- /*
- ** .pp
- ** The name of the MH sequence used to tag replied messages.
- */
- { "mh_seq_unseen", DT_STR, R_NONE, UL &MhUnseen, UL "unseen" },
- /*
- ** .pp
- ** The name of the MH sequence used for unseen messages.
- */
- { "mime_forward", DT_QUAD, R_NONE, OPT_MIMEFWD, M_NO },
- /*
- ** .pp
- ** 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.
- ** .pp
- ** Also see ``$$forward_decode'' and ``$$mime_forward_decode''.
- */
- { "mime_forward_decode", DT_BOOL, R_NONE, OPTMIMEFORWDECODE, 0 },
- /*
- ** .pp
- ** Controls the decoding of complex MIME messages into text/plain when
- ** forwarding a message while ``$$mime_forward'' is \fIset\fP. Otherwise
- ** ``$$forward_decode'' is used instead.
- */
- { "mime_fwd", DT_SYN, R_NONE, UL "mime_forward", 0 },
- /*
- */
-
- { "mime_forward_rest", DT_QUAD, R_NONE, OPT_MIMEFWDREST, M_YES },
- /*
- ** .pp
- ** 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.
- */
-
-#ifdef USE_NNTP
- { "mime_subject", DT_BOOL, R_NONE, OPTMIMESUBJECT, 1 },
- /*
- ** .pp
- ** Availability: NNTP
- **
- ** .pp
- ** If \fIunset\fP, 8-bit ``subject:'' line in article header will not be
- ** encoded according to RFC2047 to base64. This is useful when message
- ** is Usenet article, because MIME for news is nonstandard feature.
- */
-#endif
-
-#ifdef MIXMASTER
- { "mix_entry_format", DT_STR, R_NONE, UL &MixEntryFormat, UL "%4n %c %-16s %a" },
- /*
- ** .pp
- ** Availability: Mixmaster
- **
- ** .pp
- ** This variable describes the format of a remailer line on the mixmaster
- ** chain selection screen. The following printf-like sequences are
- ** supported:
- ** .pp
- ** .dl
- ** .dt %n .dd The running number on the menu.
- ** .dt %c .dd Remailer capabilities.
- ** .dt %s .dd The remailer's short name.
- ** .dt %a .dd The remailer's e-mail address.
- ** .de
- */
- { "mixmaster", DT_PATH, R_NONE, UL &Mixmaster, UL MIXMASTER },
- /*
- ** .pp
- ** Availability: Mixmaster
- **
- ** .pp
- ** 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.
- */
-#endif
- { "move", DT_QUAD, R_NONE, OPT_MOVE, M_ASKNO },
- /*
- ** .pp
- ** 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.
- */
- { "message_format", DT_STR, R_NONE, UL &MsgFmt, UL "%s" },
- /*
- ** .pp
- ** This is the string displayed in the ``attachment'' menu for
- ** attachments of type message/rfc822. For a full listing of defined
- ** printf()-like sequences see the section on ``$$index_format''.
- */
- { "msg_format", DT_SYN, R_NONE, UL "message_format", 0 },
- /*
- */
- { "msgid_format", DT_STR, R_NONE, UL &MsgIdFormat, UL "%Y%m%d%h%M%s.G%P%p" },
- /*
- ** .pp
- ** This is the format for the ``local part'' of the message-IDs generated
- ** by Mutt-ng. The format string contains of one or more characters. The '%'
- ** character marks that certain data will be added to the string, similar to
- ** printf(). The following characters are allowed:
- ** .pp
- ** .dl
- ** .dt %d .dd the current day of month
- ** .dt %h .dd the current hour
- ** .dt %m .dd the current month
- ** .dt %M .dd the current minute
- ** .dt %O .dd the current UNIX timestamp (octal)
- ** .dt %p .dd the process ID
- ** .dt %P .dd the current message-ID prefix (a character rotating with
- ** every message-ID being generated)
- ** .dt %r .dd a random integer value (decimal)
- ** .dt %R .dd a random integer value (hexadecimal)
- ** .dt %s .dd the current second
- ** .dt %T .dd the current UNIX timestamp (decimal)
- ** .dt %X .dd the current UNIX timestamp (hexadecimal)
- ** .dt %Y .dd the current year (Y2K compliant)
- ** .dt %% .dd the '%' character
- ** .de
- */
- { "narrow_tree", DT_BOOL, R_TREE|R_INDEX, OPTNARROWTREE, 0 },
- /*
- ** .pp
- ** This variable, when set, makes the thread tree narrower, allowing
- ** deeper threads to fit on the screen.
- */
-#ifdef USE_NNTP
- { "news_cache_dir", DT_PATH, R_NONE, UL &NewsCacheDir, UL "~/.mutt" },
- /*
- ** .pp
- ** Availability: NNTP
- **
- ** .pp
- ** This variable pointing to directory where Mutt-ng will save cached news
- ** articles headers in. If \fIunset\fP, headers will not be saved at all
- ** and will be reloaded each time when you enter to newsgroup.
- */
- { "news_server", DT_STR, R_NONE, UL &NewsServer, 0 },
- /*
- ** .pp
- ** Availability: NNTP
- **
- ** .pp
- ** This variable specifies domain name or address of NNTP server. It
- ** defaults to the newsserver specified in the environment variable
- ** $$$NNTPSERVER or contained in the file /etc/nntpserver. You can also
- ** specify username and an alternative port for each newsserver, ie:
- ** .pp
- ** [nntp[s]://][username[:password]@]newsserver[:port]
- */
- { "newsrc", DT_PATH, R_NONE, UL &NewsRc, UL "~/.newsrc" },
- /*
- ** .pp
- ** Availability: NNTP
- **
- ** .pp
- ** The file, containing info about subscribed newsgroups - names and
- ** indexes of read articles. The following printf-style sequence
- ** is understood:
- ** .pp
- ** .ts
- ** %s newsserver name
- ** .te
- */
- { "nntp_context", DT_NUM, R_NONE, UL &NntpContext, 1000 },
- /*
- ** .pp
- ** Availability: NNTP
- **
- ** .pp
- ** This variable defines number of articles which will be in index when
- ** newsgroup entered. If active newsgroup have more articles than this
- ** number, oldest articles will be ignored. Also controls how many
- ** articles headers will be saved in cache when you quit newsgroup.
- */
- { "nntp_load_description", DT_BOOL, R_NONE, OPTLOADDESC, 1 },
- /*
- ** .pp
- ** Availability: NNTP
- **
- ** .pp
- ** This variable controls whether or not descriptions for each newsgroup
- ** must be loaded when newsgroup is added to list (first time list
- ** loading or new newsgroup adding).
- */
- { "nntp_user", DT_STR, R_NONE, UL &NntpUser, UL "" },
- /*
- ** .pp
- ** Availability: NNTP
- **
- ** .pp
- ** Your login name on the NNTP server. If \fIunset\fP and NNTP server requires
- ** authentification, Mutt-ng will prompt you for your account name when you
- ** connect to newsserver.
- */
- { "nntp_pass", DT_STR, R_NONE, UL &NntpPass, UL "" },
- /*
- ** .pp
- ** Availability: NNTP
- **
- ** .pp
- ** Your password for NNTP account.
- */
- { "nntp_poll", DT_NUM, R_NONE, UL &NewsPollTimeout, 60 },
- /*
- ** .pp
- ** Availability: NNTP
- **
- ** .pp
- ** The time in seconds until any operations on newsgroup except post new
- ** article will cause recheck for new news. If set to 0, Mutt-ng will
- ** recheck newsgroup on each operation in index (stepping, read article,
- ** etc.).
- */
- { "nntp_reconnect", DT_QUAD, R_NONE, OPT_NNTPRECONNECT, M_ASKYES },
- /*
- ** .pp
- ** Availability: NNTP
- **
- ** .pp
- ** Controls whether or not Mutt-ng will try to reconnect to newsserver when
- ** connection lost.
- */
-#endif
- { "pager", DT_PATH, R_NONE, UL &Pager, UL "builtin" },
- /*
- ** .pp
- ** 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.
- ** .pp
- ** 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.
- */
- { "pager_context", DT_NUM, R_NONE, UL &PagerContext, 0 },
- /*
- ** .pp
- ** 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).
- */
- { "pager_format", DT_STR, R_PAGER, UL &PagerFmt, UL "-%Z- %C/%m: %-20.20n %s" },
- /*
- ** .pp
- ** 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.
- */
- { "pager_index_lines",DT_NUM, R_PAGER, UL &PagerIndexLines, 0 },
- /*
- ** .pp
- ** 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 \fIpager_index_lines\fP 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 \fIpager_index_lines\fP, then the index will only use as
- ** many lines as it needs.
- */
- { "pager_stop", DT_BOOL, R_NONE, OPTPAGERSTOP, 0 },
- /*
- ** .pp
- ** When set, the internal-pager will \fBnot\fP move to the next message
- ** when you are at the end of a message and invoke the \fInext-page\fP
- ** function.
- */
- { "pgp_autosign", DT_SYN, R_NONE, UL "crypt_autosign", 0 },
- { "crypt_autosign", DT_BOOL, R_NONE, OPTCRYPTAUTOSIGN, 0 },
- /*
- ** .pp
- ** Setting this variable will cause Mutt-ng to always attempt to
- ** cryptographically sign outgoing messages. This can be overridden
- ** by use of the \fIpgp-menu\fP, 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 \fIsmime-menu\fP.
- ** (Crypto only)
- */
- { "pgp_autoencrypt", DT_SYN, R_NONE, UL "crypt_autoencrypt", 0 },
- { "crypt_autoencrypt", DT_BOOL, R_NONE, OPTCRYPTAUTOENCRYPT, 0 },
- /*
- ** .pp
- ** Setting this variable will cause Mutt-ng to always attempt to PGP
- ** encrypt outgoing messages. This is probably only useful in
- ** connection to the \fIsend-hook\fP command. It can be overridden
- ** by use of the \fIpgp-menu\fP, 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 \fIsmime-menu\fP.
- ** (Crypto only)
- */
- { "pgp_ignore_subkeys", DT_BOOL, R_NONE, OPTPGPIGNORESUB, 1},
- /*
- ** .pp
- ** 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)
- */
- { "pgp_replyencrypt", DT_SYN, R_NONE, UL "crypt_replyencrypt", 1 },
- { "crypt_replyencrypt", DT_BOOL, R_NONE, OPTCRYPTREPLYENCRYPT, 1 },
- /*
- ** .pp
- ** If set, automatically PGP or OpenSSL encrypt replies to messages which are
- ** encrypted.
- ** (Crypto only)
- */
- { "pgp_replysign", DT_SYN, R_NONE, UL "crypt_replysign", 0 },
- { "crypt_replysign", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGN, 0 },
- /*
- ** .pp
- ** If set, automatically PGP or OpenSSL sign replies to messages which are
- ** signed.
- ** .pp
- ** \fBNote:\fP this does not work on messages that are encrypted
- ** \fBand\fP signed!
- ** (Crypto only)
- */
- { "pgp_replysignencrypted", DT_SYN, R_NONE, UL "crypt_replysignencrypted", 0},
- { "crypt_replysignencrypted", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGNENCRYPTED, 0 },
- /*
- ** .pp
- ** 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)
- */
- { "crypt_timestamp", DT_BOOL, R_NONE, OPTCRYPTTIMESTAMP, 1 },
- /*
- ** .pp
- ** 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)
- */
- { "pgp_use_gpg_agent", DT_BOOL, R_NONE, OPTUSEGPGAGENT, 0},
- /*
- ** .pp
- ** If set, mutt-ng will use a possibly-running gpg-agent process.
- ** (PGP only)
- */
- { "pgp_verify_sig", DT_SYN, R_NONE, UL "crypt_verify_sig", 0},
- { "crypt_verify_sig", DT_QUAD, R_NONE, OPT_VERIFYSIG, M_YES },
- /*
- ** .pp
- ** 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)
- */
- { "smime_is_default", DT_BOOL, R_NONE, OPTSMIMEISDEFAULT, 0},
- /*
- ** .pp
- ** 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)
- */
- { "smime_ask_cert_label", DT_BOOL, R_NONE, OPTASKCERTLABEL, 1 },
- /*
- ** .pp
- ** 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)
- */
- { "smime_decrypt_use_default_key", DT_BOOL, R_NONE, OPTSDEFAULTDECRYPTKEY, 1 },
- /*
- ** .pp
- ** 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)
- */
- { "pgp_entry_format", DT_STR, R_NONE, UL &PgpEntryFormat, UL "%4n %t%f %4l/0x%k %-4a %2c %u" },
- /*
- ** .pp
- ** 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()-like sequences:
- ** .pp
- ** .dl
- ** .dt %n .dd number
- ** .dt %k .dd key id
- ** .dt %u .dd user id
- ** .dt %a .dd algorithm
- ** .dt %l .dd key length
- ** .dt %f .dd flags
- ** .dt %c .dd capabilities
- ** .dt %t .dd trust/validity of the key-uid association
- ** .dt %[<s>] .dd date of the key where <s> is an strftime(3) expression
- ** .de
- ** .pp
- ** (PGP only)
- */
- { "pgp_good_sign", DT_RX, R_NONE, UL &PgpGoodSign, 0 },
- /*
- ** .pp
- ** 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)
- */
- { "pgp_check_exit", DT_BOOL, R_NONE, OPTPGPCHECKEXIT, 1 },
- /*
- ** .pp
- ** 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)
- */
- { "pgp_long_ids", DT_BOOL, R_NONE, OPTPGPLONGIDS, 0 },
- /*
- ** .pp
- ** If set, use 64 bit PGP key IDs. Unset uses the normal 32 bit Key IDs.
- ** (PGP only)
- */
- { "pgp_retainable_sigs", DT_BOOL, R_NONE, OPTPGPRETAINABLESIG, 0 },
- /*
- ** .pp
- ** If set, signed and encrypted messages will consist of nested
- ** multipart/signed and multipart/encrypted body parts.
- ** .pp
- ** 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)
- */
- { "pgp_create_traditional", DT_SYN, R_NONE, UL "pgp_autoinline", 0 },
- { "pgp_autoinline", DT_BOOL, R_NONE, OPTPGPAUTOINLINE, 0 },
- /*
- ** .pp
- ** 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 \fIpgp-menu\fP,
- ** when inline is not required.
- ** .pp
- ** 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''.
- ** .pp
- ** Also note that using the old-style PGP message format is \fBstrongly\fP
- ** \fBdeprecated\fP.
- ** (PGP only)
- */
- { "pgp_auto_traditional", DT_SYN, R_NONE, UL "pgp_replyinline", 0 },
- { "pgp_replyinline", DT_BOOL, R_NONE, OPTPGPREPLYINLINE, 0 },
- /*
- ** .pp
- ** 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 \fIpgp-menu\fP, 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.
- ** .pp
- ** 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''.
- ** .pp
- ** Also note that using the old-style PGP message format is \fBstrongly\fP
- ** \fBdeprecated\fP.
- ** (PGP only)
- **
- */
- { "pgp_show_unusable", DT_BOOL, R_NONE, OPTPGPSHOWUNUSABLE, 1 },
- /*
- ** .pp
- ** 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)
- */
- { "pgp_sign_as", DT_STR, R_NONE, UL &PgpSignAs, 0 },
- /*
- ** .pp
- ** 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)
- */
- { "pgp_strict_enc", DT_BOOL, R_NONE, OPTPGPSTRICTENC, 1 },
- /*
- ** .pp
- ** If set, Mutt-ng will automatically encode PGP/MIME signed messages as
- ** \fIquoted-printable\fP. 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)
- */
- { "pgp_timeout", DT_NUM, R_NONE, UL &PgpTimeout, 300 },
- /*
- ** .pp
- ** The number of seconds after which a cached passphrase will expire if
- ** not used.
- ** (PGP only)
- */
- { "pgp_sort_keys", DT_SORT|DT_SORT_KEYS, R_NONE, UL &PgpSortKeys, SORT_ADDRESS },
- /*
- ** .pp
- ** Specifies how the entries in the `pgp keys' menu are sorted. The
- ** following are legal values:
- ** .pp
- ** .dl
- ** .dt address .dd sort alphabetically by user id
- ** .dt keyid .dd sort alphabetically by key id
- ** .dt date .dd sort by key creation date
- ** .dt trust .dd sort by the trust of the key
- ** .de
- ** .pp
- ** If you prefer reverse order of the above values, prefix it with
- ** `reverse-'.
- ** (PGP only)
- */
- { "pgp_mime_auto", DT_QUAD, R_NONE, OPT_PGPMIMEAUTO, M_ASKYES },
- /*
- ** .pp
- ** 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).
- ** .pp
- ** Also note that using the old-style PGP message format is \fBstrongly\fP
- ** \fBdeprecated\fP.
- ** (PGP only)
- */
- { "pgp_auto_decode", DT_BOOL, R_NONE, OPTPGPAUTODEC, 0 },
- /*
- ** .pp
- ** 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.
- */
-
-
- /* XXX Default values! */
-
- { "pgp_decode_command", DT_STR, R_NONE, UL &PgpDecodeCommand, 0},
- /*
- ** .pp
- ** This format strings specifies a command which is used to decode
- ** application/pgp attachments.
- ** .pp
- ** The PGP command formats have their own set of printf-like sequences:
- ** .pp
- ** .dl
- ** .dt %p .dd Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
- ** string otherwise. Note: This may be used with a %? construct.
- ** .dt %f .dd Expands to the name of a file containing a message.
- ** .dt %s .dd Expands to the name of a file containing the signature part
- ** . of a multipart/signed attachment when verifying it.
- ** .dt %a .dd The value of $$pgp_sign_as.
- ** .dt %r .dd One or more key IDs.
- ** .de
- ** .pp
- ** 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)
- */
- { "pgp_getkeys_command", DT_STR, R_NONE, UL &PgpGetkeysCommand, 0},
- /*
- ** .pp
- ** This command is invoked whenever mutt-ng will need public key information.
- ** %r is the only printf-like sequence used with this format.
- ** (PGP only)
- */
- { "pgp_verify_command", DT_STR, R_NONE, UL &PgpVerifyCommand, 0},
- /*
- ** .pp
- ** This command is used to verify PGP signatures.
- ** (PGP only)
- */
- { "pgp_decrypt_command", DT_STR, R_NONE, UL &PgpDecryptCommand, 0},
- /*
- ** .pp
- ** This command is used to decrypt a PGP encrypted message.
- ** (PGP only)
- */
- { "pgp_clearsign_command", DT_STR, R_NONE, UL &PgpClearSignCommand, 0 },
- /*
- ** .pp
- ** This format is used to create a old-style "clearsigned" PGP
- ** message. Note that the use of this format is \fBstrongly\fP
- ** \fBdeprecated\fP.
- ** (PGP only)
- */
- { "pgp_sign_command", DT_STR, R_NONE, UL &PgpSignCommand, 0},
- /*
- ** .pp
- ** This command is used to create the detached PGP signature for a
- ** multipart/signed PGP/MIME body part.
- ** (PGP only)
- */
- { "pgp_encrypt_sign_command", DT_STR, R_NONE, UL &PgpEncryptSignCommand, 0},
- /*
- ** .pp
- ** This command is used to both sign and encrypt a body part.
- ** (PGP only)
- */
- { "pgp_encrypt_only_command", DT_STR, R_NONE, UL &PgpEncryptOnlyCommand, 0},
- /*
- ** .pp
- ** This command is used to encrypt a body part without signing it.
- ** (PGP only)
- */
- { "pgp_import_command", DT_STR, R_NONE, UL &PgpImportCommand, 0},
- /*
- ** .pp
- ** This command is used to import a key from a message into
- ** the user's public key ring.
- ** (PGP only)
- */
- { "pgp_export_command", DT_STR, R_NONE, UL &PgpExportCommand, 0},
- /*
- ** .pp
- ** This command is used to export a public key from the user's
- ** key ring.
- ** (PGP only)
- */
- { "pgp_verify_key_command", DT_STR, R_NONE, UL &PgpVerifyKeyCommand, 0},
- /*
- ** .pp
- ** This command is used to verify key information from the key selection
- ** menu.
- ** (PGP only)
- */
- { "pgp_list_secring_command", DT_STR, R_NONE, UL &PgpListSecringCommand, 0},
- /*
- ** .pp
- ** 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.
- ** .pp
- ** This format is also generated by the pgpring utility which comes
- ** with mutt-ng.
- ** (PGP only)
- */
- { "pgp_list_pubring_command", DT_STR, R_NONE, UL &PgpListPubringCommand, 0},
- /*
- ** .pp
- ** 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.
- ** .pp
- ** This format is also generated by the pgpring utility which comes
- ** with mutt-ng.
- ** (PGP only)
- */
- { "forward_decrypt", DT_BOOL, R_NONE, OPTFORWDECRYPT, 1 },
- /*
- ** .pp
- ** 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 \fIset\fP and
- ** ``$$mime_forward_decode'' is \fIunset\fP.
- ** (PGP only)
- */
- { "forw_decrypt", DT_SYN, R_NONE, UL "forward_decrypt", 0 },
- /*
- */
-
- { "smime_timeout", DT_NUM, R_NONE, UL &SmimeTimeout, 300 },
- /*
- ** .pp
- ** The number of seconds after which a cached passphrase will expire if
- ** not used.
- ** (S/MIME only)
- */
- { "smime_encrypt_with", DT_STR, R_NONE, UL &SmimeCryptAlg, 0 },
- /*
- ** .pp
- ** This sets the algorithm that should be used for encryption.
- ** Valid choices are "des", "des3", "rc2-40", "rc2-64", "rc2-128".
- ** If unset "3des" (TripleDES) is used.
- ** (S/MIME only)
- */
- { "smime_keys", DT_PATH, R_NONE, UL &SmimeKeys, 0 },
- /*
- ** .pp
- ** 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)
- */
- { "smime_ca_location", DT_PATH, R_NONE, UL &SmimeCALocation, 0 },
- /*
- ** .pp
- ** This variable contains the name of either a directory, or a file which
- ** contains trusted certificates for use with OpenSSL.
- ** (S/MIME only)
- */
- { "smime_certificates", DT_PATH, R_NONE, UL &SmimeCertificates, 0 },
- /*
- ** .pp
- ** 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)
- */
- { "smime_decrypt_command", DT_STR, R_NONE, UL &SmimeDecryptCommand, 0},
- /*
- ** .pp
- ** This format string specifies a command which is used to decrypt
- ** application/x-pkcs7-mime attachments.
- ** .pp
- ** The OpenSSL command formats have their own set of printf-like sequences
- ** similar to PGP's:
- ** .pp
- ** .dl
- ** .dt %f .dd Expands to the name of a file containing a message.
- ** .dt %s .dd Expands to the name of a file containing the signature part
- ** . of a multipart/signed attachment when verifying it.
- ** .dt %k .dd The key-pair specified with $$smime_default_key
- ** .dt %c .dd One or more certificate IDs.
- ** .dt %a .dd The algorithm used for encryption.
- ** .dt %C .dd 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".
- ** .de
- ** .pp
- ** 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)
- */
- { "smime_verify_command", DT_STR, R_NONE, UL &SmimeVerifyCommand, 0},
- /*
- ** .pp
- ** This command is used to verify S/MIME signatures of type multipart/signed.
- ** (S/MIME only)
- */
- { "smime_verify_opaque_command", DT_STR, R_NONE, UL &SmimeVerifyOpaqueCommand, 0},
- /*
- ** .pp
- ** This command is used to verify S/MIME signatures of type
- ** application/x-pkcs7-mime.
- ** (S/MIME only)
- */
- { "smime_sign_command", DT_STR, R_NONE, UL &SmimeSignCommand, 0},
- /*
- ** .pp
- ** This command is used to created S/MIME signatures of type
- ** multipart/signed, which can be read by all mail clients.
- ** (S/MIME only)
- */
- { "smime_sign_opaque_command", DT_STR, R_NONE, UL &SmimeSignOpaqueCommand, 0},
- /*
- ** .pp
- ** 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)
- */
- { "smime_encrypt_command", DT_STR, R_NONE, UL &SmimeEncryptCommand, 0},
- /*
- ** .pp
- ** This command is used to create encrypted S/MIME messages.
- ** (S/MIME only)
- */
- { "smime_pk7out_command", DT_STR, R_NONE, UL &SmimePk7outCommand, 0},
- /*
- ** .pp
- ** This command is used to extract PKCS7 structures of S/MIME signatures,
- ** in order to extract the public X509 certificate(s).
- ** (S/MIME only)
- */
- { "smime_get_cert_command", DT_STR, R_NONE, UL &SmimeGetCertCommand, 0},
- /*
- ** .pp
- ** This command is used to extract X509 certificates from a PKCS7 structure.
- ** (S/MIME only)
- */
- { "smime_get_signer_cert_command", DT_STR, R_NONE, UL &SmimeGetSignerCertCommand, 0},
- /*
- ** .pp
- ** This command is used to extract only the signers X509 certificate from a S/MIME
- ** signature, so that the certificate's owner may get compared to the
- ** email's 'From'-field.
- ** (S/MIME only)
- */
- { "smime_import_cert_command", DT_STR, R_NONE, UL &SmimeImportCertCommand, 0},
- /*
- ** .pp
- ** This command is used to import a certificate via smime_keys.
- ** (S/MIME only)
- */
- { "smime_get_cert_email_command", DT_STR, R_NONE, UL &SmimeGetCertEmailCommand, 0},
- /*
- ** .pp
- ** 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)
- */
- { "smime_sign_as", DT_SYN, R_NONE, UL "smime_default_key", 0 },
- { "smime_default_key", DT_STR, R_NONE, UL &SmimeDefaultKey, 0 },
- /*
- ** .pp
- ** 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)
- */
-#if defined(USE_LIBESMTP)
- { "smtp_auth_username", DT_STR, R_NONE, UL &SmtpAuthUser, 0 },
- /*
- ** .pp
- ** Availability: SMTP
- **
- ** .pp
- ** Defines the username to use with SMTP AUTH. Setting this variable will
- ** cause mutt-ng to attempt to use SMTP AUTH when sending.
- */
- { "smtp_auth_password", DT_STR, R_NONE, UL &SmtpAuthPass, 0 },
- /*
- ** .pp
- ** Availability: SMTP
- **
- ** .pp
- ** Defines the password to use with SMTP AUTH. If ``$$smtp_auth_username''
- ** is set, but this variable is not, you will be prompted for a password
- ** when sending.
- */
- { "smtp_host", DT_STR, R_NONE, UL &SmtpHost, 0 },
- /*
- ** .pp
- ** Availability: SMTP
- **
- ** .pp
- ** 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.
- */
- { "smtp_port", DT_NUM, R_NONE, UL &SmtpPort, 25 },
- /*
- ** .pp
- ** Availability: SMTP
- **
- ** .pp
- ** Defines the port that the SMTP host is listening on for mail delivery.
- ** Must be specified as a number.
- ** .pp
- ** Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP
- ** servers will probably desire 587, the mail submission port.
- */
-#endif
-#if defined(USE_SSL)||defined(USE_NSS)||defined(USE_GNUTLS)
-#ifdef USE_SSL
- { "ssl_client_cert", DT_PATH, R_NONE, UL &SslClientCert, 0 },
- /*
- ** .pp
- ** Availability: SSL
- **
- ** .pp
- ** The file containing a client certificate and its associated private
- ** key.
- */
-#endif
-# if defined(USE_SSL)||defined(USE_GNUTLS)
- { "ssl_starttls", DT_QUAD, R_NONE, OPT_SSLSTARTTLS, M_YES },
- /*
- ** .pp
- ** Availability: SSL or GNUTLS
- **
- ** .pp
- ** 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.
- */
-# endif
- { "certificate_file", DT_PATH, R_NONE, UL &SslCertFile, UL "~/.mutt_certificates" },
- /*
- ** .pp
- ** Availability: SSL or NSS or GNUTLS
- **
- ** .pp
- ** 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.
- ** .pp
- ** 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.
- ** .pp
- ** Example: set certificate_file=~/.mutt/certificates
- */
-# ifndef USE_GNUTLS
- { "ssl_usesystemcerts", DT_BOOL, R_NONE, OPTSSLSYSTEMCERTS, 1 },
- /*
- ** .pp
- ** Availability: SSL or NSS
- **
- ** .pp
- ** If set to \fIyes\fP, mutt-ng will use CA certificates in the
- ** system-wide certificate store when checking if server certificate
- ** is signed by a trusted CA.
- */
- { "entropy_file", DT_PATH, R_NONE, UL &SslEntropyFile, 0 },
- /*
- ** .pp
- ** Availability: SSL or NSS
- **
- ** .pp
- ** The file which includes random data that is used to initialize SSL
- ** library functions.
- */
- { "ssl_use_sslv2", DT_BOOL, R_NONE, OPTSSLV2, 1 },
- /*
- ** .pp
- ** Availability: SSL or NSS
- **
- ** .pp
- ** This variables specifies whether to attempt to use SSLv2 in the
- ** SSL authentication process.
- */
-# endif
- { "ssl_use_sslv3", DT_BOOL, R_NONE, OPTSSLV3, 1 },
- /*
- ** .pp
- ** Availability: SSL or NSS or GNUTLS
- **
- ** .pp
- ** This variables specifies whether to attempt to use SSLv3 in the
- ** SSL authentication process.
- */
- { "ssl_use_tlsv1", DT_BOOL, R_NONE, OPTTLSV1, 1 },
- /*
- ** .pp
- ** Availability: SSL or NSS or GNUTLS
- **
- ** .pp
- ** This variables specifies whether to attempt to use TLSv1 in the
- ** SSL authentication process.
- */
-#ifdef USE_GNUTLS
- { "ssl_min_dh_prime_bits", DT_NUM, R_NONE, UL &SslDHPrimeBits, 0 },
- /*
- ** .pp
- ** Availability: GNUTLS
- **
- ** .pp
- ** 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.
- */
- { "ssl_ca_certificates_file", DT_PATH, R_NONE, UL &SslCACertFile, 0 },
- /*
- ** .pp
- ** 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.
- ** .pp
- ** Example: set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt
- */
-#endif
-#endif
- { "pipe_split", DT_BOOL, R_NONE, OPTPIPESPLIT, 0 },
- /*
- ** .pp
- ** Used in connection with the \fIpipe-message\fP command and the ``tag-
- ** prefix'' operator. 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.
- */
- { "pipe_decode", DT_BOOL, R_NONE, OPTPIPEDECODE, 0 },
- /*
- ** .pp
- ** Used in connection with the \fIpipe-message\fP 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.
- */
- { "pipe_sep", DT_STR, R_NONE, UL &PipeSep, UL "\n" },
- /*
- ** .pp
- ** The separator to add between messages when piping a list of tagged
- ** messages to an external Unix command.
- */
-#ifdef USE_POP
- { "pop_authenticators", DT_STR, R_NONE, UL &PopAuthenticators, UL 0 },
- /*
- ** .pp
- ** Availability: POP
- **
- ** .pp
- ** 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.
- ** .pp
- ** Example: set pop_authenticators="digest-md5:apop:user"
- */
- { "pop_auth_try_all", DT_BOOL, R_NONE, OPTPOPAUTHTRYALL, 1 },
- /*
- ** .pp
- ** Availability: POP
- **
- ** .pp
- ** 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.
- */
- { "pop_checkinterval", DT_NUM, R_NONE, UL &PopCheckTimeout, 60 },
- /*
- ** .pp
- ** Availability: POP
- **
- ** .pp
- ** This variable configures how often (in seconds) POP should look for
- ** new mail.
- */
- { "pop_delete", DT_QUAD, R_NONE, OPT_POPDELETE, M_ASKNO },
- /*
- ** .pp
- ** Availability: POP
- **
- ** .pp
- ** 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.
- */
- { "pop_host", DT_STR, R_NONE, UL &PopHost, UL "" },
- /*
- ** .pp
- ** Availability: POP
- **
- ** .pp
- ** The name of your POP server for the fetch-mail function. You
- ** can also specify an alternative port, username and password, ie:
- ** .pp
- ** [pop[s]://][username[:password]@]popserver[:port]
- */
- { "pop_last", DT_BOOL, R_NONE, OPTPOPLAST, 0 },
- /*
- ** .pp
- ** Availability: POP
- **
- ** .pp
- ** 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.
- */
- { "pop_reconnect", DT_QUAD, R_NONE, OPT_POPRECONNECT, M_ASKYES },
- /*
- ** .pp
- ** Availability: POP
- **
- ** .pp
- ** Controls whether or not Mutt-ng will try to reconnect to POP server when
- ** connection lost.
- */
- { "pop_user", DT_STR, R_NONE, UL &PopUser, 0 },
- /*
- ** .pp
- ** Availability: POP
- **
- ** .pp
- ** Your login name on the POP server.
- ** .pp
- ** This variable defaults to your user name on the local machine.
- */
- { "pop_pass", DT_STR, R_NONE, UL &PopPass, UL "" },
- /*
- ** .pp
- ** Availability: POP
- **
- ** .pp
- ** Specifies the password for your POP account. If unset, Mutt-ng will
- ** prompt you for your password when you open POP mailbox.
- ** \fBWarning\fP: you should only use this option when you are on a
- ** fairly secure machine, because the superuser can read your muttngrc
- ** even if you are the only one who can read the file.
- */
-#endif /* USE_POP */
- { "post_indent_string",DT_STR, R_NONE, UL &PostIndentString, UL "" },
- /*
- ** .pp
- ** Similar to the ``$$attribution'' variable, Mutt-ng will append this
- ** string after the inclusion of a message which is being replied to.
- */
- { "post_indent_str", DT_SYN, R_NONE, UL "post_indent_string", 0 },
- /*
- */
-#ifdef USE_NNTP
- { "post_moderated", DT_QUAD, R_NONE, OPT_TOMODERATED, M_ASKYES },
- /*
- ** .pp
- ** Availability: NNTP
- **
- ** .pp
- ** If set to \fIyes\fP, Mutt-ng will post article to newsgroup that have
- ** not permissions to posting (e.g. moderated). \fBNote:\fP if newsserver
- ** does not support posting to that newsgroup or totally read-only, that
- ** posting will not have an effect.
- */
-#endif
- { "postpone", DT_QUAD, R_NONE, OPT_POSTPONE, M_ASKYES },
- /*
- ** .pp
- ** Controls whether or not messages are saved in the ``$$postponed''
- ** mailbox when you elect not to send immediately.
- */
- { "postponed", DT_PATH, R_NONE, UL &Postponed, UL "~/postponed" },
- /*
- ** .pp
- ** 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.
- */
-#ifdef USE_SOCKET
- { "preconnect", DT_STR, R_NONE, UL &Preconnect, UL 0},
- /*
- ** .pp
- ** 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:
- ** .pp
- ** preconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net
- ** sleep 20 < /dev/null > /dev/null"
- ** .pp
- ** Mailbox 'foo' on mailhost.net can now be reached
- ** as '{localhost:1234}foo'.
- ** .pp
- ** NOTE: For this example to work, you must be able to log in to the
- ** remote machine without having to enter a password.
- */
-#endif /* USE_SOCKET */
- { "print", DT_QUAD, R_NONE, OPT_PRINT, M_ASKNO },
- /*
- ** .pp
- ** Controls whether or not Mutt-ng really prints messages.
- ** This is set to \fIask-no\fP by default, because some people
- ** accidentally hit ``p'' often (like me).
- */
- { "print_command", DT_PATH, R_NONE, UL &PrintCmd, UL "lpr" },
- /*
- ** .pp
- ** This specifies the command pipe that should be used to print messages.
- */
- { "print_cmd", DT_SYN, R_NONE, UL "print_command", 0 },
- /*
- */
- { "print_decode", DT_BOOL, R_NONE, OPTPRINTDECODE, 1 },
- /*
- ** .pp
- ** 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.
- */
- { "print_split", DT_BOOL, R_NONE, OPTPRINTSPLIT, 0 },
- /*
- ** .pp
- ** 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.
- ** .pp
- ** Those who use the \fBenscript\fP(1) program's mail-printing mode will
- ** most likely want to set this option.
- */
- { "prompt_after", DT_BOOL, R_NONE, OPTPROMPTAFTER, 1 },
- /*
- ** .pp
- ** If you use an \fIexternal\fP ``$$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.
- */
- { "query_command", DT_PATH, R_NONE, UL &QueryCmd, UL "" },
- /*
- ** .pp
- ** 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.
- */
- { "quit", DT_QUAD, R_NONE, OPT_QUIT, M_YES },
- /*
- ** .pp
- ** 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.
- */
- { "quote_empty", DT_BOOL, R_NONE, OPTQUOTEEMPTY, 1 },
- /*
- ** .pp
- ** Controls whether or not empty lines will be quoted using
- ** ``$indent_string''.
- */
- { "quote_quoted", DT_BOOL, R_NONE, OPTQUOTEQUOTED, 0 },
- /*
- ** .pp
- ** 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''.
- */
- { "quote_regexp", DT_RX, R_PAGER, UL &QuoteRegexp, UL "^([ \t]*[|>:}#])+" },
- /*
- ** .pp
- ** A regular expression used in the internal-pager to determine quoted
- ** sections of text in the body of a message.
- ** .pp
- ** \fBNote:\fP In order to use the \fIquoted\fP\fBx\fP patterns in the
- ** internal pager, you need to set this to a regular expression that
- ** matches \fIexactly\fP the quote characters at the beginning of quoted
- ** lines.
- */
- { "read_inc", DT_NUM, R_NONE, UL &ReadInc, 10 },
- /*
- ** .pp
- ** 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
- ** \fIread_inc\fP 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.
- ** .pp
- ** Also see the ``$$write_inc'' variable.
- */
- { "read_only", DT_BOOL, R_NONE, OPTREADONLY, 0 },
- /*
- ** .pp
- ** If set, all folders are opened in read-only mode.
- */
- { "realname", DT_STR, R_BOTH, UL &Realname, 0 },
- /*
- ** .pp
- ** This variable specifies what "real" or "personal" name should be used
- ** when sending messages.
- ** .pp
- ** By default, this is the GECOS field from /etc/passwd. Note that this
- ** variable will \fInot\fP be used when the user has set a real name
- ** in the $$from variable.
- */
- { "recall", DT_QUAD, R_NONE, OPT_RECALL, M_ASKYES },
- /*
- ** .pp
- ** Controls whether or not Mutt-ng recalls postponed messages
- ** when composing a new message. Also see ``$$postponed''.
- ** .pp
- ** Setting this variable to ``yes'' is not generally useful, and thus not
- ** recommended.
- */
- { "record", DT_PATH, R_NONE, UL &Outbox, UL "" },
- /*
- ** .pp
- ** 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 \fIBcc:\fP field with your email address in it.)
- ** .pp
- ** The value of \fI$$record\fP is overridden by the ``$$force_name'' and
- ** ``$$save_name'' variables, and the ``$fcc-hook'' command.
- */
- { "reply_regexp", DT_RX, R_INDEX|R_RESORT, UL &ReplyRegexp, UL "^(re([\\[0-9\\]+])*|aw):[ \t]*" },
- /*
- ** .pp
- ** A regular expression used to recognize reply messages when threading
- ** and replying. The default value corresponds to the English "Re:" and
- ** the German "Aw:".
- */
- { "reply_self", DT_BOOL, R_NONE, OPTREPLYSELF, 0 },
- /*
- ** .pp
- ** 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.
- */
- { "reply_to", DT_QUAD, R_NONE, OPT_REPLYTO, M_ASKYES },
- /*
- ** .pp
- ** If set, when replying to a message, Mutt-ng will use the address listed
- ** in the Reply-to: header as the recipient of the reply. If unset,
- ** it will use the address in the From: header field instead. This
- ** option is useful for reading a mailing list that sets the Reply-To:
- ** header field to the list address and you want to send a private
- ** message to the author of a message.
- */
- { "resolve", DT_BOOL, R_NONE, OPTRESOLVE, 1 },
- /*
- ** .pp
- ** When set, the cursor will be automatically advanced to the next
- ** (possibly undeleted) message whenever a command that modifies the
- ** current message is executed.
- */
- { "reverse_alias", DT_BOOL, R_BOTH, OPTREVALIAS, 0 },
- /*
- ** .pp
- ** 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:
- ** .pp
- ** .ts
- ** alias juser abd30425@somewhere.net (Joe User)
- ** .te
- ** .pp
- ** and then you receive mail which contains the following header:
- ** .pp
- ** .ts
- ** From: abd30425@somewhere.net
- ** .te
- ** .pp
- ** 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).
- */
- { "reverse_name", DT_BOOL, R_BOTH, OPTREVNAME, 0 },
- /*
- ** .pp
- ** 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 \fIFrom:\fP line of
- ** the reply messages is built using the address where you received the
- ** messages you are replying to \fBif\fP that address matches your
- ** alternates. If the variable is unset, or the address that would be
- ** used doesn't match your alternates, the \fIFrom:\fP line will use
- ** your address on the current machine.
- */
- { "reverse_realname", DT_BOOL, R_BOTH, OPTREVREAL, 1 },
- /*
- ** .pp
- ** 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.
- */
- { "rfc2047_parameters", DT_BOOL, R_NONE, OPTRFC2047PARAMS, 0 },