- {"nntp_pass", DT_STR, R_NONE, UL &NntpPass, ""},
- /*
- ** .pp
- ** Availability: NNTP
- **
- ** .pp
- ** Your password for NNTP account.
- ** .pp
- ** \fBNote:\fP Storing passwords in a configuration file
- ** presents a security risk since the superuser of your machine may read it
- ** regardless of the file's permissions.
- */
- {"nntp_mail_check", DT_NUM, R_NONE, UL &NewsPollTimeout, "60" },
- /*
- ** .pp
- ** Availability: NNTP
- **
- ** .pp
- ** The time in seconds until any operations on a newsgroup except posting a new
- ** article will cause a recheck for new news. If set to 0, Madmutt will
- ** recheck on each operation in index (stepping, read article, etc.).
- */
- {"nntp_reconnect", DT_QUAD, R_NONE, OPT_NNTPRECONNECT, "ask-yes" },
- /*
- ** .pp
- ** Availability: NNTP
- **
- ** .pp
- ** Controls whether or not Madmutt will try to reconnect to a newsserver when the
- ** was connection lost.
- */
-#endif
- { "net_inc", DT_NUM, R_NONE, UL &NetInc, "10" },
- /*
- ** .pp
- ** Operations that expect to transfer a large amount of data over the
- ** network will update their progress every \fInet_inc\fP kilobytes.
- ** If set to 0, no progress messages will be displayed.
- ** .pp
- ** See also ``$$read_inc'' and ``$$write_inc''.
- */
- {"pager", DT_PATH, R_NONE, UL &Pager, "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 Madmutt 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, Madmutt 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, "-%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, "no" },
- /*
- ** .pp
- ** When \fIset\fP, 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.
- */
- {"crypt_autosign", DT_BOOL, R_NONE, OPTCRYPTAUTOSIGN, "no" },
- /*
- ** .pp
- ** Setting this variable will cause Madmutt 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 \fIset\fP,
- ** then OpenSSL is used instead to create S/MIME messages and settings can
- ** be overridden by use of the \fIsmime-menu\fP.
- ** (Crypto only)
- */
- {"crypt_autoencrypt", DT_BOOL, R_NONE, OPTCRYPTAUTOENCRYPT, "no" },
- /*
- ** .pp
- ** Setting this variable will cause Madmutt 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 \fIset\fP,
- ** 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, "yes" },
- /*
- ** .pp
- ** Setting this variable will cause Madmutt to ignore OpenPGP subkeys. Instead,
- ** the principal key will inherit the subkeys' capabilities. \fIUnset\fP this
- ** if you want to play interesting key selection games.
- ** (PGP only)
- */
- {"crypt_replyencrypt", DT_BOOL, R_NONE, OPTCRYPTREPLYENCRYPT, "yes" },
- /*
- ** .pp
- ** If \fIset\fP, automatically PGP or OpenSSL encrypt replies to messages which are
- ** encrypted.
- ** (Crypto only)
- */
- {"crypt_replysign", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGN, "no" },
- /*
- ** .pp
- ** If \fIset\fP, 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)
- */
- {"crypt_replysignencrypted", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGNENCRYPTED, "no" },
- /*
- ** .pp
- ** If \fIset\fP, 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 Madmutt is not able
- ** to find out whether an encrypted message is also signed.
- ** (Crypto only)
- */
- {"crypt_timestamp", DT_BOOL, R_NONE, OPTCRYPTTIMESTAMP, "yes" },
- /*
- ** .pp
- ** If \fIset\fP, Madmutt 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 \fIunset\fP this setting.
- ** (Crypto only)
- */
- {"pgp_use_gpg_agent", DT_BOOL, R_NONE, OPTUSEGPGAGENT, "no" },
- /*
- ** .pp
- ** If \fIset\fP, Madmutt will use a possibly-running gpg-agent process.
- ** (PGP only)
- */
- {"crypt_verify_sig", DT_QUAD, R_NONE, OPT_VERIFYSIG, "yes" },
- /*
- ** .pp
- ** If ``\fIyes\fP'', always attempt to verify PGP or S/MIME signatures.
- ** If ``\fIask\fP'', ask whether or not to verify the signature.
- ** If ``\fIno\fP'', never attempt to verify cryptographic signatures.
- ** (Crypto only)
- */
- {"smime_is_default", DT_BOOL, R_NONE, OPTSMIMEISDEFAULT, "no" },
- /*
- ** .pp
- ** The default behaviour of Madmutt is to use PGP on all auto-sign/encryption
- ** operations. To override and to use OpenSSL instead this must be \fIset\fP.
- ** .pp
- ** However, this has no effect while replying, since Madmutt will automatically
- ** select the same application that was used to sign/encrypt the original
- ** message.
- ** .pp
- ** (Note that this variable can be overridden by unsetting $$crypt_autosmime.)
- ** (S/MIME only)
- */
- {"smime_ask_cert_label", DT_BOOL, R_NONE, OPTASKCERTLABEL, "yes" },
- /*
- ** .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
- ** \fIset\fP by default.
- ** (S/MIME only)
- */
- {"smime_decrypt_use_default_key", DT_BOOL, R_NONE, OPTSDEFAULTDECRYPTKEY, "yes" },
- /*
- ** .pp
- ** If \fIset\fP (default) this tells Madmutt to use the default key for decryption. Otherwise,
- ** if manage multiple certificate-key-pairs, Madmutt 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, "%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 \fTprintf(3)\fP-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 \fTstrftime(3)\fP expression
- ** .de
- ** .pp
- ** (PGP only)
- */
- {"pgp_good_sign", DT_RX, R_NONE, UL &PgpGoodSign, "" },
- /*
- ** .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, "yes" },
- /*
- ** .pp
- ** If \fIset\fP, Madmutt 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, "no" },
- /*
- ** .pp
- ** If \fIset\fP, use 64 bit PGP key IDs. \fIUnset\fP uses the normal 32 bit Key IDs.
- ** (PGP only)
- */
- {"pgp_retainable_sigs", DT_BOOL, R_NONE, OPTPGPRETAINABLESIG, "no" },
- /*
- ** .pp
- ** If \fIset\fP, 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_autoinline", DT_BOOL, R_NONE, OPTPGPAUTOINLINE, "no" },
- /*
- ** .pp
- ** This option controls whether Madmutt 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 Madmutt might automatically use PGP/MIME for messages
- ** which consist of more than a single MIME part. Madmutt 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_replyinline", DT_BOOL, R_NONE, OPTPGPREPLYINLINE, "no" },
- /*
- ** .pp
- ** Setting this variable will cause Madmutt 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 Madmutt
- ** internals for previously checked/flagged messages.
- ** .pp
- ** Note that Madmutt might automatically use PGP/MIME for messages
- ** which consist of more than a single MIME part. Madmutt 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, "yes" },