- {"pgp_timeout", DT_NUM, R_NONE, UL &PgpTimeout, 300},
- /*
- ** .pp
- ** The number of seconds after which a cached passphrase will expire if
- ** not used. Default: 300.
- ** (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 \fIset\fP, 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 \fTprintf(3)\fP-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 \fTsamples/\fP 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.
- ** \fT%r\fP is the only \fTprintf(3)\fP-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.
- ** .pp
- ** 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
- ** \fTgpg --list-keys --with-colons\fP.
- ** .pp
- ** This format is also generated by the \fTpgpring\fP 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
- ** \fTgpg --list-keys --with-colons\fP.
- ** .pp
- ** This format is also generated by the \fTpgpring\fP 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 \fIset\fP, 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)
- */
- {"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 ``\fTdes\fP'', ``\fTdes3\fP'', ``\fTrc2-40\fP'',
- ** ``\fTrc2-64\fP'', ``\frc2-128\fP''.
- ** .pp
- ** If \fIunset\fP ``\fI3des\fP'' (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
- ** \fTapplication/x-pkcs7-mime\fP attachments.
- ** .pp
- ** The OpenSSL command formats have their own set of \fTprintf(3)\fP-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 \fTsamples/\fP 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 \fTmultipart/signed\fP.
- ** (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
- ** \fTapplication/x-pkcs7-mime\fP.
- ** (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
- ** \fTmultipart/signed\fP, 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
- ** \fTapplication/x-pkcs7-signature\fP, 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 ``\fTFrom:\fP'' header 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 \fTsmime_keysng\fP.
- ** (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_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_SYN, R_NONE, UL "smtp_user", 0},
- {"smtp_user", 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_SYN, R_NONE, UL "smtp_pass", 0},
- {"smtp_pass", DT_STR, R_NONE, UL &SmtpAuthPass, 0},
- /*
- ** .pp
- ** Availability: SMTP
- **
- ** .pp
- ** Defines the password to use with SMTP AUTH. If ``$$smtp_user''
- ** is set, but this variable is not, you will be prompted for a password
- ** when sending.
- ** .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.
- */
- {"smtp_envelope", DT_STR, R_NONE, UL &SmtpEnvFrom, 0},
- /*
- ** .pp
- ** Availability: SMTP
- **
- ** .pp
- ** If this variable is non-empty, it'll be used as the envelope sender. If it's empty
- ** (the default), the value of the regular \fTFrom:\fP header will be used.
- **
- ** .pp
- ** This may be necessary as some providers don't allow for arbitrary values
- ** as the envelope sender but only a particular one which may not be the same as the
- ** user's desired \fTFrom:\fP header.
- */
- {"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.
- */
- {"smtp_use_tls", DT_STR, R_NONE, UL &SmtpUseTLS, 0},
- /*
- ** .pp
- ** Availability: SMTP (and SSL)
- **
- ** .pp
- ** Defines wether to use STARTTLS. If this option is set to ``\fIrequired\fP''
- ** and the server does not support STARTTLS or there is an error in the
- ** TLS Handshake, the connection will fail. Setting this to ``\fIenabled\fP''
- ** will try to start TLS and continue without TLS in case of an error.
- **
- **.pp
- ** Muttng still needs to have SSL support enabled in order to use it.
- */
-#endif
-#if defined(USE_SSL) || 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 /* USE_SSL */
- {"ssl_force_tls", DT_BOOL, R_NONE, OPTSSLFORCETLS, 0 },
- /*
- ** .pp
- ** If this variable is \fIset\fP, mutt-ng will require that all connections
- ** to remote servers be encrypted. Furthermore it will attempt to
- ** negotiate TLS even if the server does not advertise the capability,
- ** since it would otherwise have to abort the connection anyway. This
- ** option supersedes ``$$ssl_starttls''.
- */
- {"ssl_starttls", DT_QUAD, R_NONE, OPT_SSLSTARTTLS, M_YES},
- /*
- ** .pp
- ** Availability: SSL or GNUTLS
- **
- ** .pp
- ** If \fIset\fP (the default), Mutt-ng will attempt to use STARTTLS on servers
- ** advertising the capability. When \fIunset\fP, Mutt-ng will not attempt to
- ** use STARTTLS regardless of the server's capabilities.
- */
- {"certificate_file", DT_PATH, R_NONE, UL &SslCertFile, UL "~/.mutt_certificates"},
- /*
- ** .pp
- ** Availability: SSL 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: \fTset certificate_file=~/.muttng/certificates\fP
- */
-# if defined(_MAKEDOC) || !defined (USE_GNUTLS)
- {"ssl_usesystemcerts", DT_BOOL, R_NONE, OPTSSLSYSTEMCERTS, 1},
- /*
- ** .pp
- ** Availability: SSL
- **
- ** .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
- **
- ** .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
- **
- ** .pp
- ** This variables specifies whether to attempt to use SSLv2 in the
- ** SSL authentication process.
- */
-# endif /* _MAKEDOC || !USE_GNUTLS */
- {"ssl_use_sslv3", DT_BOOL, R_NONE, OPTSSLV3, 1},
- /*
- ** .pp
- ** Availability: SSL 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 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: \fTset ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt\fP
- */
-# endif /* USE_GNUTLS */
-# endif /* USE_SSL || USE_GNUTLS */
- {"pipe_split", DT_BOOL, R_NONE, OPTPIPESPLIT, 0},
- /*
- ** .pp
- ** Used in connection with the \fIpipe-message\fP command and the ``tag-
- ** prefix'' or ``tag-prefix-cond'' operators.
- ** If this variable is \fIunset\fP, when piping a list of
- ** tagged messages Mutt-ng will concatenate the messages and will pipe them
- ** as a single folder. When \fIset\fP, 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 \fIunset\fP,
- ** Mutt-ng will pipe the messages without any preprocessing. When \fIset\fP, 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 ``\fTuser\fP'', ``\fTapop\fP''
- ** or any SASL mechanism, eg ``\fTdigest-md5\fP'', ``\fTgssapi\fP'' or ``\fTcram-md5\fP''.
- ** .pp
- ** This parameter is case-insensitive. If this parameter is \fIunset\fP
- ** (the default) Mutt-ng will try all available methods, in order from
- ** most-secure to least-secure.
- ** .pp
- ** Example: \fTset pop_authenticators="digest-md5:apop:user"\fP
- */
- {"pop_auth_try_all", DT_BOOL, R_NONE, OPTPOPAUTHTRYALL, 1},
- /*
- ** .pp
- ** Availability: POP
- **
- ** .pp
- ** If \fIset\fP, Mutt-ng will try all available methods. When \fIunset\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 POP server.
- */
- {"pop_checkinterval", DT_SYN, R_NONE, UL "pop_mail_check", 0},
- {"pop_mail_check", 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 \fIset\fP, Mutt-ng will delete successfully downloaded messages from the POP
- ** server when using the ``fetch-mail'' function. When \fIunset\fP, 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, i.e.:
- ** .pp
- ** \fT[pop[s]://][username[:password]@]popserver[:port]\fP
- ** .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.
- */
- {"pop_last", DT_BOOL, R_NONE, OPTPOPLAST, 0},
- /*
- ** .pp
- ** Availability: POP
- **
- ** .pp
- ** If this variable is \fIset\fP, Mutt-ng will try to use the ``\fTLAST\fP'' 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 a POP server when the
- ** connection is 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 \fIunset\fP, Mutt-ng will
- ** prompt you for your password when you open POP mailbox.
- ** .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.
- */
-#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.
- */
-#ifdef USE_NNTP
- {"post_moderated", DT_SYN, R_NONE, UL "nntp_post_moderated", 0 },
- {"nntp_post_moderated", DT_QUAD, R_NONE, OPT_TOMODERATED, M_ASKYES},
- /*
- ** .pp
- ** Availability: NNTP
- **
- ** .pp
- ** If set to \fIyes\fP, Mutt-ng will post articles to newsgroup that have
- ** not permissions to post (e.g. moderated).
- ** .pp
- ** \fBNote:\fP if the newsserver
- ** does not support posting to that newsgroup or a group is totally read-only, that
- ** posting will not have any 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 \fIset\fP, 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 \fTssh(1)\fP. If the command returns a nonzero
- ** status, Mutt-ng gives up opening the server. Example:
- ** .pp
- ** \fTpreconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net
- ** sleep 20 < /dev/null > /dev/null"\fP
- ** .pp
- ** Mailbox ``foo'' on mailhost.net can now be reached
- ** as ``{localhost:1234}foo''.
- ** .pp
- ** \fBNote:\fP 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.
- */
- {"print_command", DT_PATH, R_NONE, UL &PrintCmd, UL "lpr"},
- /*
- ** .pp
- ** This specifies the command pipe that should be used to print messages.
- */
- {"print_decode", DT_BOOL, R_NONE, OPTPRINTDECODE, 1},