- ** .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_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 will remove your address (see the ``alternates''
- ** command) from the list of recipients when replying to a message.
- */
- { "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 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 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
- ** 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
- ** 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
- ** 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 you will be asked to confirm moving read messages
- ** from your spool mailbox to your ``$$mbox'' mailbox, or as a result of
- ** a ``$mbox-hook'' command.
- */
- { "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 },
- /*
- */
- { "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
- ** This variable pointing to directory where Mutt 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
- ** 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
- ** 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
- ** 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
- ** 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
- ** Your login name on the NNTP server. If \fIunset\fP and NNTP server requires
- ** authentification, Mutt will prompt you for your account name when you
- ** connect to newsserver.
- */
- { "nntp_pass", DT_STR, R_NONE, UL &NntpPass, UL "" },
- /*
- ** .pp
- ** Your password for NNTP account.
- */
- { "nntp_poll", DT_NUM, R_NONE, UL &NewsPollTimeout, 60 },
- /*
- ** .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 will
- ** recheck newsgroup on each operation in index (stepping, read article,
- ** etc.).
- */
- { "nntp_reconnect", DT_QUAD, R_NONE, OPT_NNTPRECONNECT, M_ASKYES },
- /*
- ** .pp
- ** Controls whether or not Mutt 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 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 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 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 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 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 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 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 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 is to use PGP on all auto-sign/encryption
- ** operations. To override and to use OpenSSL instead this must be set.
- ** However, this has no effect while replying, since mutt will automatically
- ** select the same application that was used to sign/encrypt the original
- ** message. (Note that this variable can be overridden by unsetting $$crypt_autosmime.)
- ** (S/MIME only)
- */
- { "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 to use the default key for decryption. Otherwise,
- ** if manage multiple certificate-key-pairs, mutt will try to use the mailbox-address
- ** to determine the key to use. It will ask you to supply a key, if it can't find one.
- ** (S/MIME only)
- */
- { "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 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_show_unusable", DT_BOOL, R_NONE, OPTPGPSHOWUNUSABLE, 1 },
- /*
- ** .pp
- ** If set, mutt 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 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_create_traditional", DT_QUAD, R_NONE, OPT_PGPTRADITIONAL, M_NO },
- /*
- ** .pp
- ** This option controls whether Mutt generates old-style inline PGP
- ** encrypted or signed messages.
- ** .pp
- ** Note that PGP/MIME will be used automatically for messages which have
- ** a character set different from us-ascii, or which consist of more than
- ** a single MIME part.
- ** .pp
- ** Also note that using the old-style PGP message format is \fBstrongly\fP
- ** \fBdeprecated\fP.
- ** (PGP only)
- */
- { "pgp_auto_traditional", DT_BOOL, R_NONE, OPTPGPAUTOTRAD, 0 },
- /*
- ** .pp
- ** This option causes Mutt to generate an old-style inline PGP
- ** encrypted or signed message when replying to an old-style
- ** message, and a PGP/MIME message when replying to a PGP/MIME
- ** message. Note that this option is only meaningful when using
- ** ``$$crypt_replyencrypt'', ``$$crypt_replysign'', or
- ** ``$$crypt_replysignencrypted''.
- ** .pp
- ** Also note that PGP/MIME will be used automatically for messages
- ** which have a character set different from us-ascii, or which
- ** consist of more than a single MIME part.
- ** .pp
- ** This option overrides ``$$pgp_create_traditional''
- ** (PGP only)
- */
-
- /* 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 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.
- ** (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.
- ** (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 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 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
- ** Defines the username to use with SMTP AUTH. Setting this variable will
- ** cause mutt to attempt to use SMTP AUTH when sending.
- */
- { "smtp_auth_password", DT_STR, R_NONE, UL &SmtpAuthPass, 0 },
- /*
- ** .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
- ** 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
- ** 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)
-# if defined(USE_SSL)||defined(USE_GNUTLS)
- { "ssl_starttls", DT_QUAD, R_NONE, OPT_SSLSTARTTLS, M_YES },
- /*
- ** .pp
- ** If set (the default), mutt will attempt to use STARTTLS on servers
- ** advertising the capability. When unset, mutt will not attempt to
- ** use STARTTLS regardless of the server's capabilities.
- */
-# endif
- { "certificate_file", DT_PATH, R_NONE, UL &SslCertFile, 0 },
- /*
- ** .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
- ** If set to \fIyes\fP, mutt 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
- ** The file which includes random data that is used to initialize SSL
- ** library functions.