always build mutt with pgp + smime support.

[apps/madmutt.git] / init.h

/*
 * Copyright notice from original mutt:
 * Copyright (C) 1996-2002 Michael R. Elkins <me@mutt.org>
 * Copyright (C) 2004 g10 Code GmbH
 *
 * Parts were writte/modified by:
 * Nico Golde <nico@ngolde.de>
 *
 * This file is part of mutt-ng, see http://www.muttng.org/.
 * It's licensed under the GNU General Public License,
 * please see the file GPL in the top level source directory.
 */

#ifdef _MAKEDOC
# include "config.h"
#else
# include "sort.h"
#endif

#include "buffy.h"
#include "mutt.h"
#include "version.h"
#include "lib/debug.h"

#ifndef _MAKEDOC
#define DT_MASK         0x0f
#define DT_BOOL         1       /* boolean option */
#define DT_NUM          2       /* a number */
#define DT_STR          3       /* a string */
#define DT_PATH         4       /* a pathname */
#define DT_QUAD         5       /* quad-option (yes/no/ask-yes/ask-no) */
#define DT_SORT         6       /* sorting methods */
#define DT_RX           7       /* regular expressions */
#define DT_MAGIC        8       /* mailbox type */
#define DT_SYN          9       /* synonym for another variable */
#define DT_ADDR         10      /* e-mail address */
#define DT_USER         11      /* user defined via $user_ */
#define DT_SYS          12      /* pre-defined via $muttng_ */

#define DTYPE(x) ((x) & DT_MASK)

/* subtypes */
#define DT_SUBTYPE_MASK 0xf0
#define DT_SORT_ALIAS   0x10
#define DT_SORT_BROWSER 0x20
#define DT_SORT_KEYS    0x40
#define DT_SORT_AUX     0x80

/* flags to parse_set() */
#define M_SET_INV       (1<<0)  /* default is to invert all vars */
#define M_SET_UNSET     (1<<1)  /* default is to unset all vars */
#define M_SET_RESET     (1<<2)  /* default is to reset all vars to default */

/* forced redraw/resort types */
#define R_NONE          0
#define R_INDEX         (1<<0)
#define R_PAGER         (1<<1)
#define R_RESORT        (1<<2)  /* resort the mailbox */
#define R_RESORT_SUB    (1<<3)  /* resort subthreads */
#define R_RESORT_INIT   (1<<4)  /* resort from scratch */
#define R_TREE          (1<<5)  /* redraw the thread tree */
#define R_BOTH          (R_INDEX|R_PAGER)
#define R_RESORT_BOTH   (R_RESORT|R_RESORT_SUB)

struct option_t {
  const char *option;
  short type;
  short flags;
  unsigned long data;
  const char *init;
};

#define UL (unsigned long)

#endif /* _MAKEDOC */

#ifndef ISPELL
#define ISPELL "ispell"
#endif

/* build complete documentation */

#ifdef _MAKEDOC
# ifndef USE_IMAP
#  define USE_IMAP
# endif
# ifndef MIXMASTER
#  define MIXMASTER "mixmaster"
# endif
# ifndef USE_POP
#  define USE_POP
# endif
# ifndef USE_SSL
#  define USE_SSL
# endif
# ifndef USE_SOCKET
#  define USE_SOCKET
# endif
# ifndef USE_LIBESMTP
#  define USE_LIBESMTP
# endif
# ifndef USE_NNTP
#  define USE_NNTP
# endif
# ifndef USE_GNUTLS
#  define USE_GNUTLS
# endif
# ifndef USE_DOTLOCK
#  define USE_DOTLOCK
# endif
# ifndef USE_HCACHE
#  define USE_HCACHE
# endif
# ifndef HAVE_LIBIDN
#  define HAVE_LIBIDN
# endif
# ifndef HAVE_GETADDRINFO
#  define HAVE_GETADDRINFO
# endif
#endif

struct option_t MuttVars[] = {
  /*++*/
  {"abort_noattach", DT_QUAD, R_NONE, OPT_ATTACH, "no" },
  /*
   ** .pp
   ** This variable specifies whether to abort sending if no attachment
   ** was made but the content references them, i.e. the content
   ** matches the regular expression given in
   ** $$attach_remind_regexp. If a match was found and this
   ** variable is set to \fIyes\fP, message sending will be aborted
   ** but the mail will be send nevertheless if set to \fIno\fP.
   **
   ** .pp
   ** This variable and $$attach_remind_regexp are intended to
   ** remind the user to attach files if the message's text
   ** references them.
   **
   ** .pp
   ** See also the $$attach_remind_regexp variable.
   */
  {"abort_nosubject", DT_QUAD, R_NONE, OPT_SUBJECT, "ask-yes" },
  /*
   ** .pp
   ** If set to \fIyes\fP, when composing messages and no subject is given
   ** at the subject prompt, composition will be aborted.  If set to
   ** \fIno\fP, composing messages with no subject given at the subject
   ** prompt will never be aborted.
   */
  {"abort_unmodified", DT_QUAD, R_NONE, OPT_ABORT, "yes" },
  /*
   ** .pp
   ** If set to \fIyes\fP, composition will automatically abort after
   ** editing the message body if no changes are made to the file (this
   ** check only happens after the \fIfirst\fP edit of the file).  When set
   ** to \fIno\fP, composition will never be aborted.
   */
  {"alias_file", DT_PATH, R_NONE, UL &AliasFile, "~/.muttngrc"},
  /*
   ** .pp
   ** The default file in which to save aliases created by the 
   ** ``$create-alias'' function.
   ** .pp
   ** \fBNote:\fP Mutt-ng will not automatically source this file; you must
   ** explicitly use the ``$source'' command for it to be executed.
   */
  {"alias_format", DT_STR, R_NONE, UL &AliasFmt, "%4n %2f %t %-10a   %r"},
  /*
   ** .pp
   ** Specifies the format of the data displayed for the ``alias'' menu. The
   ** following \fTprintf(3)\fP-style sequences are available:
   ** .pp
   ** .dl
   ** .dt %a .dd alias name
   ** .dt %f .dd flags - currently, a "d" for an alias marked for deletion
   ** .dt %n .dd index number
   ** .dt %r .dd address which alias expands to
   ** .dt %t .dd character which indicates if the alias is tagged for inclusion
   ** .de
   */
  {"allow_8bit", DT_BOOL, R_NONE, OPTALLOW8BIT, "yes" },
  /*
   ** .pp
   ** Controls whether 8-bit data is converted to 7-bit using either
   ** \fTquoted-printable\fP or \fTbase64\fP encoding when sending mail.
   */
  {"allow_ansi", DT_BOOL, R_NONE, OPTALLOWANSI, "no" },
  /*
   ** .pp
   ** Controls whether ANSI color codes in messages (and color tags in 
   ** rich text messages) are to be interpreted.
   ** Messages containing these codes are rare, but if this option is set,
   ** their text will be colored accordingly. Note that this may override
   ** your color choices, and even present a security problem, since a
   ** message could include a line like ``\fT[-- PGP output follows ...\fP" and
   ** give it the same color as your attachment color.
   */
  {"arrow_cursor", DT_BOOL, R_BOTH, OPTARROWCURSOR, "no" },
  /*
   ** .pp
   ** When \fIset\fP, an arrow (``\fT->\fP'') will be used to indicate the current entry
   ** in menus instead of highlighting the whole line.  On slow network or modem
   ** links this will make response faster because there is less that has to
   ** be redrawn on the screen when moving to the next or previous entries
   ** in the menu.
   */
  {"ascii_chars", DT_BOOL, R_BOTH, OPTASCIICHARS, "no" },
  /*
   ** .pp
   ** If \fIset\fP, Mutt-ng will use plain ASCII characters when displaying thread
   ** and attachment trees, instead of the default \fTACS\fP characters.
   */
  {"askbcc", DT_BOOL, R_NONE, OPTASKBCC, "no" },
  /*
   ** .pp
   ** If \fIset\fP, Mutt-ng will prompt you for blind-carbon-copy (Bcc) recipients
   ** before editing an outgoing message.
   */
  {"askcc", DT_BOOL, R_NONE, OPTASKCC, "no" },
  /*
   ** .pp
   ** If \fIset\fP, Mutt-ng will prompt you for carbon-copy (Cc) recipients before
   ** editing the body of an outgoing message.
   */
  {"assumed_charset", DT_STR, R_NONE, UL &AssumedCharset, "us-ascii"},
  /*
   ** .pp
   ** This variable is a colon-separated list of character encoding
   ** schemes for messages without character encoding indication.
   ** Header field values and message body content without character encoding
   ** indication would be assumed that they are written in one of this list.
   ** By default, all the header fields and message body without any charset
   ** indication are assumed to be in \fTus-ascii\fP.
   ** .pp
   ** For example, Japanese users might prefer this:
   ** .pp
   ** \fTset assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"\fP
   ** .pp
   ** However, only the first content is valid for the message body.
   ** This variable is valid only if $$strict_mime is unset.
   */
#ifdef USE_NNTP
  {"nntp_ask_followup_to", DT_BOOL, R_NONE, OPTASKFOLLOWUP, "no" },
  /*
   ** .pp
   ** Availability: NNTP
   **
   ** .pp
   ** If \fIset\fP, Mutt-ng will prompt you for the \fTFollowup-To:\fP header
   ** field before editing the body of an outgoing news article.
   */
  {"nntp_ask_x_comment_to", DT_BOOL, R_NONE, OPTASKXCOMMENTTO, "no" },
  /*
   ** .pp
   ** Availability: NNTP
   **
   ** .pp
   ** If \fIset\fP, Mutt-ng will prompt you for the \fTX-Comment-To:\fP header
   ** field before editing the body of an outgoing news article.
   */
#endif
  {"attach_format", DT_STR, R_NONE, UL &AttachFormat, "%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] "},
  /*
   ** .pp
   ** This variable describes the format of the ``attachment'' menu.  The
   ** following \fTprintf(3)\fP-style sequences are understood:
   ** .pp
   ** .dl
   ** .dt %C  .dd charset
   ** .dt %c  .dd requires charset conversion (n or c)
   ** .dt %D  .dd deleted flag
   ** .dt %d  .dd description
   ** .dt %e  .dd MIME \fTContent-Transfer-Encoding:\fP header field
   ** .dt %f  .dd filename
   ** .dt %I  .dd MIME \fTContent-Disposition:\fP header field (\fTI\fP=inline, \fTA\fP=attachment)
   ** .dt %m  .dd major MIME type
   ** .dt %M  .dd MIME subtype
   ** .dt %n  .dd attachment number
   ** .dt %Q  .dd "Q", if MIME part qualifies for attachment counting
   ** .dt %s  .dd size
   ** .dt %t  .dd tagged flag
   ** .dt %T  .dd graphic tree characters
   ** .dt %u  .dd unlink (=to delete) flag
   ** .dt %X  .dd number of qualifying MIME parts in this part and its children
   ** .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
   */
  {"attach_remind_regexp", DT_RX, R_NONE, UL &AttachRemindRegexp, "attach"},
  /*
   ** .pp
   ** If this variable is non-empty, muttng will scan a message's contents
   ** before sending for this regular expression. If it is found, it will
   ** ask for what to do depending on the setting of $$abort_noattach.
   ** .pp
   ** This variable and $$abort_noattach are intended to remind the user
   ** to attach files if the message's text references them.
   */
  {"attach_sep", DT_STR, R_NONE, UL &AttachSep, "\n"},
  /*
   ** .pp
   ** The separator to add between attachments when operating (saving,
   ** printing, piping, etc) on a list of tagged attachments.
   */
  {"attach_split", DT_BOOL, R_NONE, OPTATTACHSPLIT, "yes" },
  /*
   ** .pp
   ** If this variable is \fIunset\fP, when operating (saving, printing, piping,
   ** etc) on a list of tagged attachments, Mutt-ng will concatenate the
   ** attachments and will operate on them as a single attachment. The
   ** ``$$attach_sep'' separator is added after each attachment. When \fIset\fP,
   ** Mutt-ng will operate on the attachments one by one.
   */
  {"attribution", DT_STR, R_NONE, UL &Attribution, "On %d, %n wrote:"},
  /*
   ** .pp
   ** This is the string that will precede a message which has been included
   ** in a reply.  For a full listing of defined \fTprintf(3)\fP-like sequences see
   ** the section on ``$$index_format''.
   */
  {"autoedit", DT_BOOL, R_NONE, OPTAUTOEDIT, "no" },
  /*
   ** .pp
   ** When \fIset\fP along with ``$$edit_headers'', Mutt-ng will skip the initial
   ** send-menu and allow you to immediately begin editing the body of your
   ** message.  The send-menu may still be accessed once you have finished
   ** editing the body of your message.
   ** .pp
   ** Also see ``$$fast_reply''.
   */
  {"auto_tag", DT_BOOL, R_NONE, OPTAUTOTAG, "no" },
  /*
   ** .pp
   ** When \fIset\fP, functions in the \fIindex\fP menu which affect a message
   ** will be applied to all tagged messages (if there are any).  When
   ** unset, you must first use the ``tag-prefix'' function (default: "\fT;\fP") to
   ** make the next function apply to all tagged messages.
   */
  {"beep", DT_BOOL, R_NONE, OPTBEEP, "yes" },
  /*
   ** .pp
   ** When this variable is \fIset\fP, Mutt-ng will beep when an error occurs.
   */
  {"beep_new", DT_BOOL, R_NONE, OPTBEEPNEW, "no" },
  /*
   ** .pp
   ** When this variable is \fIset\fP, Mutt-ng will beep whenever it prints a message
   ** notifying you of new mail.  This is independent of the setting of the
   ** ``$$beep'' variable.
   */
  {"bounce", DT_QUAD, R_NONE, OPT_BOUNCE, "ask-yes" },
  /*
   ** .pp
   ** Controls whether you will be asked to confirm bouncing messages.
   ** If set to \fIyes\fP you don't get asked if you want to bounce a
   ** message. Setting this variable to \fIno\fP is not generally useful,
   ** and thus not recommended, because you are unable to bounce messages.
   */
  {"bounce_delivered", DT_BOOL, R_NONE, OPTBOUNCEDELIVERED, "yes" },
  /*
   ** .pp
   ** When this variable is \fIset\fP, Mutt-ng will include 
   ** \fTDelivered-To:\fP header fields when bouncing messages.
   ** Postfix users may wish to \fIunset\fP this variable.
   */
  { "braille_friendly", DT_BOOL, R_NONE, OPTBRAILLEFRIENDLY, "no" },
  /*
   ** .pp
   ** When this variable is set, mutt will place the cursor at the beginning
   ** of the current line in menus, even when the arrow_cursor variable
   ** is unset, making it easier for blind persons using Braille displays to 
   ** follow these menus.  The option is disabled by default because many 
   ** visual terminals don't permit making the cursor invisible.
   */
#ifdef USE_NNTP
  {"nntp_catchup", DT_QUAD, R_NONE, OPT_CATCHUP, "ask-yes" },
  /*
   ** .pp
   ** Availability: NNTP
   **
   ** .pp
   ** If this variable is \fIset\fP, Mutt-ng will mark all articles in a newsgroup
   ** as read when you leaving it.
   */
#endif
  {"charset", DT_STR, R_NONE, UL &Charset, "" },
  /*
   ** .pp
   ** Character set your terminal uses to display and enter textual data.
   */
  {"check_new", DT_BOOL, R_NONE, OPTCHECKNEW, "yes" },
  /*
   ** .pp
   ** \fBNote:\fP this option only affects \fImaildir\fP and \fIMH\fP style
   ** mailboxes.
   ** .pp
   ** When \fIset\fP, Mutt-ng will check for new mail delivered while the
   ** mailbox is open.  Especially with MH mailboxes, this operation can
   ** take quite some time since it involves scanning the directory and
   ** checking each file to see if it has already been looked at.  If it's
   ** \fIunset\fP, no check for new mail is performed while the mailbox is open.
   */
  {"collapse_unread", DT_BOOL, R_NONE, OPTCOLLAPSEUNREAD, "yes" },
  /*
   ** .pp
   ** When \fIunset\fP, Mutt-ng will not collapse a thread if it contains any
   ** unread messages.
   */
  {"count_attachments", DT_BOOL, R_NONE, OPTCOUNTATTACH, "yes"},
  /*
   ** .pp
   ** This variable controls whether attachments should be counted for $$$index_format
   ** and its \fT%X\fP expando or not. As for scoring, this variable can be used to
   ** selectively turn counting on or off instead of removing and re-adding rules as
   ** prefered because counting requires full loading of messages.
   ** .pp
   ** If it is \fIset\fP and rules were defined via the \fTattachments\fP and/or
   ** \fTunattachments\fP commands, counting will be done. If it is \fIunset\fP no
   ** counting will be done regardless whether rules were defined or not.
   */
  {"uncollapse_jump", DT_BOOL, R_NONE, OPTUNCOLLAPSEJUMP, "no" },
  /*
   ** .pp
   ** When \fIset\fP, Mutt-ng will jump to the next unread message, if any,
   ** when the current thread is \fIun\fPcollapsed.
   */
  {"compose_format", DT_STR, R_BOTH, UL &ComposeFormat, "-- Mutt-ng: Compose  [Approx. msg size: %l   Atts: %a]%>-"},
  /*
   ** .pp
   ** Controls the format of the status line displayed in the ``compose''
   ** menu.  This string is similar to ``$$status_format'', but has its own
   ** set of \fTprintf(3)\fP-like sequences:
   ** .pp
   ** .dl
   ** .dt %a .dd total number of attachments 
   ** .dt %h .dd local hostname
   ** .dt %l .dd approximate size (in bytes) of the current message
   ** .dt %v .dd Mutt-ng version string
   ** .de
   ** .pp
   ** See the text describing the ``$$status_format'' option for more 
   ** information on how to set ``$$compose_format''.
   */
  {"config_charset", DT_STR, R_NONE, UL &ConfigCharset, "" },
  /*
   ** .pp
   ** When defined, Mutt-ng will recode commands in rc files from this
   ** encoding.
   */
  {"confirmappend", DT_BOOL, R_NONE, OPTCONFIRMAPPEND, "yes" },
  /*
   ** .pp
   ** When \fIset\fP, Mutt-ng will prompt for confirmation when appending messages to
   ** an existing mailbox.
   */
  {"confirmcreate", DT_BOOL, R_NONE, OPTCONFIRMCREATE, "yes" },
  /*
   ** .pp
   ** When \fIset\fP, Mutt-ng will prompt for confirmation when saving messages to a
   ** mailbox which does not yet exist before creating it.
   */
  {"connect_timeout", DT_NUM, R_NONE, UL &ConnectTimeout, "30" },
  /*
   ** .pp
   ** Causes Mutt-ng to timeout a network connection (for IMAP or POP) after this
   ** many seconds if the connection is not able to be established.  A negative
   ** value causes Mutt-ng to wait indefinitely for the connection to succeed.
   */
  {"content_type", DT_STR, R_NONE, UL &ContentType, "text/plain"},
  /*
   ** .pp
   ** Sets the default \fTContent-Type:\fP header field for the body
   ** of newly composed messages.
   */
  {"copy", DT_QUAD, R_NONE, OPT_COPY, "yes" },
  /*
   ** .pp
   ** This variable controls whether or not copies of your outgoing messages
   ** will be saved for later references.  Also see ``$$record'',
   ** ``$$save_name'', ``$$force_name'' and ``$fcc-hook''.
   */

  {"crypt_use_gpgme", DT_BOOL, R_NONE, OPTCRYPTUSEGPGME, "no" },
  /*
   ** .pp
   ** This variable controls the use the GPGME enabled crypto backends.
   ** If it is \fIset\fP and Mutt-ng was build with gpgme support, the gpgme code for
   ** S/MIME and PGP will be used instead of the classic code.
   ** .pp
   ** \fBNote\fP: You need to use this option in your \fT.muttngrc\fP configuration
   ** file as it won't have any effect when used interactively.
   */

  {"crypt_autopgp", DT_BOOL, R_NONE, OPTCRYPTAUTOPGP, "yes" },
  /*
   ** .pp
   ** This variable controls whether or not Mutt-ng may automatically enable
   ** PGP encryption/signing for messages.  See also ``$$crypt_autoencrypt'',
   ** ``$$crypt_replyencrypt'',
   ** ``$$crypt_autosign'', ``$$crypt_replysign'' and ``$$smime_is_default''.
   */
  {"crypt_autosmime", DT_BOOL, R_NONE, OPTCRYPTAUTOSMIME, "yes" },
  /*
   ** .pp
   ** This variable controls whether or not Mutt-ng may automatically enable
   ** S/MIME encryption/signing for messages. See also ``$$crypt_autoencrypt'',
   ** ``$$crypt_replyencrypt'',
   ** ``$$crypt_autosign'', ``$$crypt_replysign'' and ``$$smime_is_default''.
   */
  {"date_format", DT_STR, R_BOTH, UL &DateFmt, "!%a, %b %d, %Y at %I:%M:%S%p %Z"},
  /*
   ** .pp
   ** This variable controls the format of the date printed by the ``\fT%d\fP''
   ** sequence in ``$$index_format''.  This is passed to \fTstrftime(3)\fP
   ** to process the date.
   ** .pp
   ** Unless the first character in the string is a bang (``\fT!\fP''), the month
   ** and week day names are expanded according to the locale specified in
   ** the variable ``$$locale''. If the first character in the string is a
   ** bang, the bang is discarded, and the month and week day names in the
   ** rest of the string are expanded in the \fIC\fP locale (that is in US
   ** English).
   */
#ifdef DEBUG
  {"debug_level", DT_NUM, R_NONE, UL &DebugLevel, "1" },
  /*
   ** .pp
   ** Availability: debug
   **
   ** .pp
   ** This variable specifies the current debug level and
   ** may be used to increase or decrease the verbosity level
   ** during runtime. It overrides the level given with the
   ** \fT-d\fP command line option.
   **
   ** .pp
   ** Currently, this number must be >= 0 and <= 5 and muttng
   ** must be started with \fT-d\fP to enable debugging at all;
   ** enabling at runtime is not possible.
   */
#endif
  {"default_hook", DT_STR, R_NONE, UL &DefaultHook, "~f %s !~P | (~P ~C %s)"},
  /*
   ** .pp
   ** This variable controls how send-hooks, message-hooks, save-hooks,
   ** and fcc-hooks will
   ** be interpreted if they are specified with only a simple regexp,
   ** instead of a matching pattern.  The hooks are expanded when they are
   ** declared, so a hook will be interpreted according to the value of this
   ** variable at the time the hook is declared.  The default value matches
   ** if the message is either from a user matching the regular expression
   ** given, or if it is from you (if the from address matches
   ** ``alternates'') and is to or cc'ed to a user matching the given
   ** regular expression.
   */
  {"delete", DT_QUAD, R_NONE, OPT_DELETE, "ask-yes" },
  /*
   ** .pp
   ** Controls whether or not messages are really deleted when closing or
   ** synchronizing a mailbox.  If set to \fIyes\fP, messages marked for
   ** deleting will automatically be purged without prompting.  If set to
   ** \fIno\fP, messages marked for deletion will be kept in the mailbox.
   */
  {"delete_space", DT_BOOL, R_NONE, OPTDELSP, "no" },
  /*
   ** .pp
   ** When sending messages with \fTformat=flowed\fP by \fIsetting\fP the
   ** $$text_flowed variable, this variable specifies whether to also
   ** set the \fTDelSp\fP parameter to \fTyes\fP. If this is \fIunset\fP,
   ** no additional parameter will be send as a value of \fTno\fP already
   ** is the default behavior.
   **
   ** .pp
   ** \fBNote:\fP this variable only has an effect on \fIoutgoing\fP messages
   ** (if $$text_flowed is \fIset\fP) but not on incomming.
   */
  {"delete_untag", DT_BOOL, R_NONE, OPTDELETEUNTAG, "yes" },
  /*
   ** .pp
   ** If this option is \fIset\fP, Mutt-ng will untag messages when marking them
   ** for deletion.  This applies when you either explicitly delete a message,
   ** or when you save it to another folder.
   */
  {"digest_collapse", DT_BOOL, R_NONE, OPTDIGESTCOLLAPSE, "yes" },
  /*
   ** .pp
   ** If this option is \fIset\fP, Mutt-ng's received-attachments menu will not show the subparts of
   ** individual messages in a multipart/digest.  To see these subparts, press 'v' on that menu.
   */
  {"display_filter", DT_PATH, R_PAGER, UL &DisplayFilter, ""},
  /*
   ** .pp
   ** When \fIset\fP, specifies a command used to filter messages.  When a message
   ** is viewed it is passed as standard input to $$display_filter, and the
   ** filtered message is read from the standard output.
   */
#if defined(USE_DOTLOCK)
  {"dotlock_program", DT_PATH, R_NONE, UL &MuttDotlock, "$muttng_bindir/muttng_dotlock"},
  /*
   ** .pp
   ** Availability: Dotlock
   **
   ** .pp
   ** Contains the path of the \fTmuttng_dotlock(1)\fP binary to be used by
   ** Mutt-ng.
   */
#endif
  {"dsn_notify", DT_STR, R_NONE, UL &DsnNotify, ""},
  /*
   ** .pp
   ** \fBNote:\fP you should not enable this unless you are using Sendmail
   ** 8.8.x or greater or in connection with the SMTP support via libESMTP.
   ** .pp
   ** This variable sets the request for when notification is returned.  The
   ** string consists of a comma separated list (no spaces!) of one or more
   ** of the following: \fInever\fP, to never request notification,
   ** \fIfailure\fP, to request notification on transmission failure,
   ** \fIdelay\fP, to be notified of message delays, \fIsuccess\fP, to be
   ** notified of successful transmission.
   ** .pp
   ** Example: \fTset dsn_notify="failure,delay"\fP
   */
  {"dsn_return", DT_STR, R_NONE, UL &DsnReturn, ""},
  /*
   ** .pp
   ** \fBNote:\fP you should not enable this unless you are using Sendmail
   ** 8.8.x or greater or in connection with the SMTP support via libESMTP.
   ** .pp
   ** This variable controls how much of your message is returned in DSN
   ** messages.  It may be set to either \fIhdrs\fP to return just the
   ** message header, or \fIfull\fP to return the full message.
   ** .pp
   ** Example: \fTset dsn_return=hdrs\fP
   */
  {"duplicate_threads", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTDUPTHREADS, "yes" },
  /*
   ** .pp
   ** This variable controls whether Mutt-ng, when sorting by threads, threads
   ** messages with the same \fTMessage-ID:\fP header field together.
   ** If it is \fIset\fP, it will indicate that it thinks they are duplicates
   ** of each other with an equals sign in the thread diagram.
   */
  {"edit_headers", DT_BOOL, R_NONE, OPTEDITHDRS, "no" },
  /*
   ** .pp
   ** This option allows you to edit the header of your outgoing messages
   ** along with the body of your message.
   **
   ** .pp
   ** Which empty header fields to show is controlled by the
   ** $$editor_headers option.
   */
#ifdef USE_NNTP
  {"editor_headers", DT_STR, R_NONE, UL &EditorHeaders, "From: To: Cc: Bcc: Subject: Reply-To: Newsgroups: Followup-To: X-Comment-To:" },
#else
  {"editor_headers", DT_STR, R_NONE, UL &EditorHeaders, "From: To: Cc: Bcc: Subject: Reply-To:" },
#endif
  /*
   ** .pp
   ** If $$edit_headers is \fIset\fP, this space-separated list specifies
   ** which \fInon-empty\fP header fields to edit in addition to
   ** user-defined headers.
   **
   ** .pp
   ** Note: if $$edit_headers had to be turned on by force because
   ** $$strict_mailto is \fIunset\fP, this option has no effect.
   */
  {"editor", DT_PATH, R_NONE, UL &Editor, "" },
  /*
   ** .pp
   ** This variable specifies which editor is used by Mutt-ng.
   ** It defaults to the value of the \fT$$$VISUAL\fP, or \fT$$$EDITOR\fP, environment
   ** variable, or to the string "\fTvi\fP" if neither of those are set.
   */
  {"encode_from", DT_BOOL, R_NONE, OPTENCODEFROM, "no" },
  /*
   ** .pp
   ** When \fIset\fP, Mutt-ng will \fTquoted-printable\fP encode messages when
   ** they contain the string ``\fTFrom \fP'' (note the trailing space)
   ** in the beginning of a line. Useful to avoid the tampering certain mail
   ** delivery and transport agents tend to do with messages.
   **
   ** .pp
   ** \fBNote:\fP as Mutt-ng currently violates RfC3676 defining
   ** \fTformat=flowed\fP, it's <em/strongly/ advised to \fIset\fP
   ** this option although discouraged by the standard. Alternatively,
   ** you must take care of space-stuffing <tt/From / lines (with a trailing
   ** space) yourself.
   */
  {"envelope_from", DT_SYN, R_NONE, UL "use_envelope_from", 0 },
  {"use_envelope_from", DT_BOOL, R_NONE, OPTENVFROM, "no" },
  /*
   ** .pp
   ** When \fIset\fP, Mutt-ng will use ``$$envelope_from_address'' as the
   ** \fIenvelope\fP sender if that is set, otherwise it will attempt to
   ** derive it from the "From:" header.
   **
   ** .pp
   ** \fBNote:\fP This information is passed
   ** to sendmail command using the "-f" command line switch and
   ** passed to the SMTP server for libESMTP (if support is compiled in).
   */
  {"envelope_from_address", DT_ADDR, R_NONE, UL &EnvFrom, "" },
  /*
  ** .pp
  ** Manually sets the \fIenvelope\fP sender for outgoing messages.
  ** This value is ignored if ``$$use_envelope_from'' is unset.
  */
  {"escape", DT_STR, R_NONE, UL &EscChar, "~"},
  /*
   ** .pp
   ** Escape character to use for functions in the builtin editor.
   */
  {"fast_reply", DT_BOOL, R_NONE, OPTFASTREPLY, "no" },
  /*
   ** .pp
   ** When \fIset\fP, the initial prompt for recipients and subject are skipped
   ** when replying to messages, and the initial prompt for subject is
   ** skipped when forwarding messages.
   ** .pp
   ** \fBNote:\fP this variable has no effect when the ``$$autoedit''
   ** variable is \fIset\fP.
   */
  {"fcc_attach", DT_BOOL, R_NONE, OPTFCCATTACH, "yes" },
  /*
   ** .pp
   ** This variable controls whether or not attachments on outgoing messages
   ** are saved along with the main body of your message.
   */
  {"fcc_clear", DT_BOOL, R_NONE, OPTFCCCLEAR, "no" },
  /*
   ** .pp
   ** When this variable is \fIset\fP, FCCs will be stored unencrypted and
   ** unsigned, even when the actual message is encrypted and/or
   ** signed.
   ** (PGP only)
   */
  {"file_charset", DT_STR, R_NONE, UL &FileCharset, "" },
  /*
   ** .pp
   ** This variable is a colon-separated list of character encoding
   ** schemes for text file attatchments.
   ** If \fIunset\fP, $$charset value will be used instead.
   ** For example, the following configuration would work for Japanese
   ** text handling:
   ** .pp
   ** \fTset file_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"\fP
   ** .pp
   ** Note: ``\fTiso-2022-*\fP'' must be put at the head of the value as shown above
   ** if included.
   */
  {"folder", DT_PATH, R_NONE, UL &Maildir, "~/Mail"},
  /*
   ** .pp
   ** Specifies the default location of your mailboxes.  A ``\fT+\fP'' or ``\fT=\fP'' at the
   ** beginning of a pathname will be expanded to the value of this
   ** variable.  Note that if you change this variable from the default
   ** value you need to make sure that the assignment occurs \fIbefore\fP
   ** you use ``+'' or ``='' for any other variables since expansion takes place
   ** during the ``set'' command.
   */
  {"folder_format", DT_STR, R_INDEX, UL &FolderFormat, "%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f"},
  /*
   ** .pp
   ** This variable allows you to customize the file browser display 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 %C  .dd current file number
   ** .dt %d  .dd date/time folder was last modified
   ** .dt %f  .dd filename
   ** .dt %F  .dd file permissions
   ** .dt %g  .dd group name (or numeric gid, if missing)
   ** .dt %l  .dd number of hard links
   ** .dt %N  .dd N if folder has new mail, blank otherwise
   ** .dt %s  .dd size in bytes
   ** .dt %t  .dd * if the file is tagged, blank otherwise
   ** .dt %u  .dd owner name (or numeric uid, if missing)
   ** .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
   */
  {"followup_to", DT_BOOL, R_NONE, OPTFOLLOWUPTO, "yes" },
  /*
   ** .pp
   ** Controls whether or not the \fTMail-Followup-To:\fP header field is
   ** generated when sending mail.  When \fIset\fP, Mutt-ng will generate this
   ** field when you are replying to a known mailing list, specified with
   ** the ``subscribe'' or ``$lists'' commands or detected by common mailing list
   ** headers.
   ** .pp
   ** This field has two purposes.  First, preventing you from
   ** receiving duplicate copies of replies to messages which you send
   ** to mailing lists. Second, ensuring that you do get a reply
   ** separately for any messages sent to known lists to which you are
   ** not subscribed.  The header will contain only the list's address
   ** for subscribed lists, and both the list address and your own
   ** email address for unsubscribed lists.  Without this header, a
   ** group reply to your message sent to a subscribed list will be
   ** sent to both the list and your address, resulting in two copies
   ** of the same email for you.
   */
#ifdef USE_NNTP
  {"nntp_followup_to_poster", DT_QUAD, R_NONE, OPT_FOLLOWUPTOPOSTER, "ask-yes" },
  /*
   ** .pp
   ** Availability: NNTP
   **
   ** .pp
   ** If this variable is \fIset\fP and the keyword "\fTposter\fP" is present in
   ** the \fTFollowup-To:\fP header field, a follow-up to the newsgroup is not
   ** permitted.  The message will be mailed to the submitter of the
   ** message via mail.
   */
#endif
  {"force_name", DT_BOOL, R_NONE, OPTFORCENAME, "no" },
  /*
   ** .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, "no" },
  /*
   ** .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, "yes" },
  /*
   ** .pp
   ** Controls the decoding of complex MIME messages into \fTtext/plain\fP 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.
   */
  {"forward_edit", DT_QUAD, R_NONE, OPT_FORWEDIT, "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 \fIno\fP.
   */
  {"forward_format", DT_STR, R_NONE, UL &ForwFmt, "[%a: %s]"},
  /*
   ** .pp
   ** This variable controls the default subject when forwarding a message.
   ** It uses the same format sequences as the ``$$index_format'' variable.
   */
  {"forward_quote", DT_BOOL, R_NONE, OPTFORWQUOTE, "no" },
  /*
   ** .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''.
   */
  {"from", DT_ADDR, R_NONE, UL &From, "" },
  /*
   ** .pp
   ** 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
   ** E.g. you can use 
   ** \fTsend-hook Mutt-ng-devel@lists.berlios.de 'my_hdr From: Foo Bar <foo@bar.fb>'\fP
   ** when replying to the Mutt-ng developer's mailing list and Mutt-ng takes this email address.
   ** .pp
   ** Defaults to the contents of the environment variable \fT$$$EMAIL\fP.
   */
  {"gecos_mask", DT_RX, R_NONE, UL &GecosMask, "^[^,]*"},
  /*
   ** .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 ``\fT^[^,]*\fP'' which will return the string up to the first ``\fT,\fP'' encountered.
   ** If the GECOS field contains a string like "lastname, firstname" then you
   ** should do: \fTset gecos_mask=".*"\fP.
   ** .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
  {"nntp_group_index_format", DT_STR, R_BOTH, UL &GroupFormat, "%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 \fTprintf(3)\fP-like sequences:
   ** .pp
   ** .ts
   ** %C      current newsgroup number
   ** %d      description of newsgroup (retrieved from server)
   ** %f      newsgroup name
   ** %M      ``-'' if newsgroup not allowed for direct post (moderated for example)
   ** %N      ``N'' if newsgroup is new, ``u'' if unsubscribed, blank otherwise
   ** %n      number of new articles in newsgroup
   ** %s      number of unread articles in newsgroup
   ** %>X     right justify the rest of the string and pad with character "X"
   ** %|X     pad to the end of the line with character "X"
   ** .te
   */
#endif
  {"hdrs", DT_BOOL, R_NONE, OPTHDRS, "yes" },
  /*
   ** .pp
   ** When \fIunset\fP, the header fields normally added by the ``$my_hdr''
   ** command are not created.  This variable \fImust\fP be \fIunset\fP before
   ** composing a new message or replying in order to take effect.  If \fIset\fP,
   ** the user defined header fields are added to every new message.
   */
  {"header", DT_BOOL, R_NONE, OPTHEADER, "no" },
  /*
   ** .pp
   ** When \fIset\fP, 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, "yes" },
  /*
   ** .pp
   ** When \fIset\fP, 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, "no" },
  /*
   ** .pp
   ** When \fIset\fP, 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 \fTMessage-ID:\fP header fields, and it will not lead to the 
   ** cut-off of first-level domains.
   */
  {"hide_limited", DT_BOOL, R_TREE|R_INDEX, OPTHIDELIMITED, "no" },
  /*
   ** .pp
   ** When \fIset\fP, 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, "yes" },
  /*
   ** .pp
   ** When \fIset\fP, Mutt-ng will not show the presence of missing messages in the
   ** thread tree.
   */
  {"hide_thread_subject", DT_BOOL, R_TREE|R_INDEX, OPTHIDETHREADSUBJECT, "yes" },
  /*
   ** .pp
   ** When \fIset\fP, 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, "no" },
  /*
   ** .pp
   ** When \fIset\fP, 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 \fIset\fP, this option will have no effect.
   */
  {"hide_top_missing", DT_BOOL, R_TREE|R_INDEX, OPTHIDETOPMISSING, "yes" },
  /*
   ** .pp
   ** When \fIset\fP, 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
   ** \fIset\fP, 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 changed.
   */
  {"honor_followup_to", DT_QUAD, R_NONE, OPT_MFUPTO, "yes" },
  /*
   ** .pp
   ** This variable controls whether or not a \fTMail-Followup-To:\fP header field is
   ** honored when group-replying to a message.
   */
  {"hostname", DT_STR, R_NONE, UL &Fqdn, "" },
  /*
   ** .pp
   ** Specifies the hostname to use after the ``\fT@\fP'' in local e-mail
   ** addresses and during generation of \fTMessage-ID:\fP headers.
   ** .pp
   ** Please be sure to really know what you are doing when changing this variable
   ** to configure a custom domain part of Message-IDs.
   */
  {"ignore_list_reply_to", DT_BOOL, R_NONE, OPTIGNORELISTREPLYTO, "no" },
  /*
   ** .pp
   ** Affects the behaviour of the \fIreply\fP function when replying to
   ** messages from mailing lists.  When \fIset\fP, if the ``\fTReply-To:\fP'' header field is
   ** set to the same value as the ``\fTTo:\fP'' header field, Mutt-ng assumes that the
   ** ``\fTReply-To:\fP'' header 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.
   ** Remember: This option works only for mailing lists which are explicitly set in your muttngrc
   ** configuration file.
   */
#ifdef USE_IMAP
  {"imap_authenticators", DT_STR, R_NONE, UL &ImapAuthenticators, "" },
  /*
   ** .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 ``\fTlogin\fP'' or the right
   ** side of an IMAP ``\fTAUTH=\fP'' capability string, e.g. ``\fTdigest-md5\fP'',
   ** ``\fTgssapi\fP'' or ``\fTcram-md5\fP''. This parameter is case-insensitive.
   ** .pp
   ** 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 imap_authenticators="gssapi:cram-md5:login"\fP
   ** .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_check_subscribed",  DT_BOOL, R_NONE, OPTIMAPCHECKSUBSCRIBED, "no" },
  /*
   ** .pp
   ** When \fIset\fP, mutt will fetch the set of subscribed folders from
   ** your server on connection, and add them to the set of mailboxes
   ** it polls for new mail. See also the ``$mailboxes'' command.
   */
  
  {"imap_delim_chars", DT_STR, R_NONE, UL &ImapDelimChars, "/."},
  /*
   ** .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 '\fT=\fP' shortcut for your $$folder variable.
   */
  {"imap_headers", DT_STR, R_INDEX, UL &ImapHeaders, "" },
  /*
   ** .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.
   ** .pp
   ** \fBNote:\fP This is a space separated list.
   */
  {"imap_home_namespace", DT_STR, R_NONE, UL &ImapHomeNamespace, "" },
  /*
   ** .pp
   ** Availability: IMAP
   **
   ** .pp
   ** You normally want to see your personal folders alongside
   ** your \fTINBOX\fP 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.
   ** .pp
   ** 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.
   ** .pp
   ** Reduce this number if you find yourself
   ** getting disconnected from your IMAP server due to inactivity.
   */
  {"imap_login", DT_STR, R_NONE, UL &ImapLogin, "" },
  /*
   ** .pp
   ** Availability: IMAP
   **
   ** .pp
   ** Your login name on the IMAP server.
   ** .pp
   ** This variable defaults to the value of ``$$imap_user.''
   */
  {"imap_list_subscribed", DT_BOOL, R_NONE, OPTIMAPLSUB, "no" },
  /*
   ** .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, "300" },
  /*
   ** .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.
   */
  {"imap_pass", DT_STR, R_NONE, UL &ImapPass, "" },
  /*
   ** .pp
   ** Availability: IMAP
   **
   ** .pp
   ** Specifies the password for your IMAP account.  If \fIunset\fP, Mutt-ng will
   ** prompt you for your password when you invoke the fetch-mail function.
   ** .pp
   ** \fBWarning\fP: you should only use this option when you are on a
   ** fairly secure machine, because the superuser can read your configuration even
   ** if you are the only one who can read the file.
   */
  {"imap_passive", DT_BOOL, R_NONE, OPTIMAPPASSIVE, "yes" },
  /*
   ** .pp
   ** Availability: IMAP
   **
   ** .pp
   ** When \fIset\fP, 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, "yes" },
  /*
   ** .pp
   ** Availability: IMAP
   **
   ** .pp
   ** If \fIset\fP, 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, "ask-yes" },
  /*
   ** .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, "yes" },
  /*
   ** .pp
   ** Availability: IMAP
   **
   ** .pp
   ** When \fIset\fP, 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, "" },
  /*
   ** .pp
   ** Availability: IMAP
   **
   ** .pp
   ** The name of the user whose mail you intend to access on the IMAP
   ** server.
   ** .pp
   ** This variable defaults to your user name on the local machine.
   */
#endif
  {"implicit_autoview", DT_BOOL, R_NONE, OPTIMPLICITAUTOVIEW, "no" },
  /*
   ** .pp
   ** If \fIset\fP, Mutt-ng will look for a mailcap entry with the
   ** ``\fTcopiousoutput\fP'' 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, "ask-yes" },
  /*
   ** .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, "no" },
  /*
   ** .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, "> "},
  /*
   ** .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.
   */
  {"index_format", DT_STR, R_BOTH, UL &HdrFmt, "%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 \fTprintf(3)\fP 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 %X .dd number of attachments
   ** .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
  {"nntp_inews", DT_PATH, R_NONE, UL &Inews, ""},
  /*
   ** .pp
   ** Availability: NNTP
   **
   ** .pp
   ** If \fIset\fP, specifies the program and arguments used to deliver news posted
   ** by Mutt-ng.  Otherwise, Mutt-ng posts article using current connection.
   ** The following \fTprintf(3)\fP-style sequence is understood:
   ** .pp
   ** .ts
   ** %s      newsserver name
   ** .te
   ** .pp
   ** Example: \fTset inews="/usr/local/bin/inews -hS"\fP
   */
#endif
  {"ispell", DT_PATH, R_NONE, UL &Ispell, ISPELL},
  /*
   ** .pp
   ** How to invoke ispell (GNU's spell-checking software).
   */
  {"keep_flagged", DT_BOOL, R_NONE, OPTKEEPFLAGGED, "no" },
  /*
   ** .pp
   ** If \fIset\fP, 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, "C"},
  /*
   ** .pp
   ** The locale used by \fTstrftime(3)\fP to format dates. Legal values are
   ** the strings your system accepts for the locale variable \fTLC_TIME\fP.
   */
  {"force_list_reply", DT_QUAD, R_NONE, OPT_LISTREPLY, "ask-no" },
  /*
   ** .pp
   ** This variable controls what effect ordinary replies have on mailing list
   ** messages: if \fIset\fP, a normal reply will be interpreted as list-reply
   ** while if it's \fIunset\fP the reply functions work as usual.
   */
  {"max_display_recips", DT_NUM, R_PAGER, UL &MaxDispRecips, "0" },
  /*
   ** .pp
   ** When set non-zero, this specifies the maximum number of recipient header
   ** lines (\fTTo:\fP, \fTCc:\fP and \fTBcc:\fP) to display in the pager if header
   ** weeding is turned on. In case the number of lines exeeds its value, the
   ** last line will have 3 dots appended.
   */
  {"max_line_length", DT_NUM, R_PAGER, UL &MaxLineLength, "0" },
  /*
   ** .pp
   ** When \fIset\fP, the maximum line length for displaying ``format = flowed'' messages is limited
   ** to this length. A value of 0 (which is also the default) means that the
   ** maximum line length is determined by the terminal width and $$wrapmargin.
   */
  {"mail_check", DT_NUM, R_NONE, UL &BuffyTimeout, "5" },
  /*
   ** .pp
   ** This variable configures how often (in seconds) Mutt-ng should look for
   ** new mail.
   ** .pp
   ** \fBNote:\fP This does not apply to IMAP mailboxes, see $$imap_mail_check.
   */
  {"mailcap_path", DT_STR, R_NONE, UL &MailcapPath, "" },
  /*
   ** .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, "yes" },
  /*
   ** .pp
   ** If \fIset\fP, Mutt-ng will restrict possible characters in mailcap \fT%\fP 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
   */
#ifdef USE_HCACHE

  {"header_cache", DT_PATH, R_NONE, UL &HeaderCache, "" },
  /*
   ** .pp
   ** Availability: Header Cache
   **
   ** .pp
   ** The $$header_cache variable points to the header cache database.
   ** .pp
   ** 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 \fIunset\fP so no
   ** header caching will be used.
   */
  {"maildir_header_cache_verify", DT_BOOL, R_NONE, OPTHCACHEVERIFY, "yes" },
  /*
   ** .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 \fTstat(2)\fP per
   ** message every time the folder is opened.
   */
#if HAVE_GDBM || HAVE_DB4
  {"header_cache_pagesize", DT_STR, R_NONE, UL &HeaderCachePageSize, "16384"},
  /*
   ** .pp
   ** Availability: Header Cache
   **
   ** .pp
   ** Change the maildir header cache database page size.
   ** .pp
   ** 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 for mutt header
   ** cache (first hit).
   */
#endif /* HAVE_GDBM || HAVE_DB 4 */
#if HAVE_QDBM
  { "header_cache_compress", DT_BOOL, R_NONE, OPTHCACHECOMPRESS, "no" },
  /*
  ** .pp
  ** If enabled the header cache will be compressed. So only one fifth of the usual
  ** diskspace is used, but the uncompression can result in a slower open of the
  ** cached folder.
  */
#endif /* HAVE_QDBM */
#endif /* USE_HCACHE */
  {"maildir_trash", DT_BOOL, R_NONE, OPTMAILDIRTRASH, "no" },
  /*
   ** .pp
   ** If \fIset\fP, messages marked as deleted will be saved with the maildir
   ** (T)rashed flag instead of physically deleted.
   ** .pp
   ** \fBNOTE:\fP this only applies
   ** to maildir-style mailboxes. Setting it will have no effect on other
   ** mailbox types.
   ** .pp
   ** It is similiar to the trash option.
   */
  {"mark_old", DT_BOOL, R_BOTH, OPTMARKOLD, "yes" },
  /*
   ** .pp
   ** Controls whether or not Mutt-ng marks \fInew\fP \fBunread\fP
   ** messages as \fIold\fP if you exit a mailbox without reading them.
   ** .pp
   ** With this option \fIset\fP, 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, "yes" },
  /*
   ** .pp
   ** Controls the display of wrapped lines in the internal pager. If set, a
   ** ``\fT+\fP'' marker is displayed at the beginning of wrapped lines. Also see
   ** the ``$$smart_wrap'' variable.
   */
  {"mask", DT_RX, R_NONE, UL &Mask, "!^\\.[^.]"},
  /*
   ** .pp
   ** A regular expression used in the file browser, optionally preceded by
   ** the \fInot\fP operator ``\fT!\fP''.  Only files whose names match this mask
   ** will be shown. The match is always case-sensitive.
   */
  {"mbox", DT_PATH, R_BOTH, UL &Inbox, "~/mbox"},
  /*
   ** .pp
   ** This specifies the folder into which read mail in your ``$$spoolfile''
   ** folder will be appended.
   */
  {"muttng_version", DT_SYS, R_NONE, 0, VERSION },
  /*
   ** .pp
   ** \fIThis is a read-only system property and specifies muttng's
   ** version string.\fP
   */
  {"muttng_revision", DT_SYS, R_NONE, 0, MUTT_REVISION },
  /*
   ** .pp
   ** \fIThis is a read-only system property and specifies muttng's
   ** subversion revision string.\fP
   */
  {"muttng_sysconfdir", DT_SYS, R_NONE, 0, SYSCONFDIR },
  /*
   ** .pp
   ** \fIThis is a read-only system property and specifies the
   ** directory containing the muttng system-wide configuration.\fP
   */
  {"muttng_bindir", DT_SYS, R_NONE, 0, BINDIR },
  /*
   ** .pp
   ** \fIThis is a read-only system property and specifies the
   ** directory containing the muttng binary.\fP
   */
  {"muttng_docdir", DT_SYS, R_NONE, 0, PKGDOCDIR },
  /*
   ** .pp
   ** \fIThis is a read-only system property and specifies the
   ** directory containing the muttng documentation.\fP
   */
#ifdef USE_HCACHE
#if HAVE_QDBM
  {"muttng_hcache_backend", DT_SYS, R_NONE, 0, "qdbm" },
#elif HAVE_GDBM
  {"muttng_hcache_backend", DT_SYS, R_NONE, 0, "gdbm" },
#elif HAVE_DB4
  {"muttng_hcache_backend", DT_SYS, R_NONE, 0, "db4" },
#else
  {"muttng_hcache_backend", DT_SYS, R_NONE, 0, "unknown" },
#endif
  /*
   ** .pp
   ** \fIThis is a read-only system property and specifies the
   ** header chaching's database backend.\fP
   */
#endif
  {"muttng_folder_path", DT_SYS, R_NONE, 0, "" },
  /*
   ** .pp
   ** \fIThis is a read-only system property and, at runtime,
   ** specifies the full path or URI of the folder currently
   ** open (if any).\fP
   */
  {"muttng_folder_name", DT_SYS, R_NONE, 0, "" },
  /*
   ** .pp
   ** \fIThis is a read-only system property and, at runtime,
   ** specifies the actual name of the folder as far as it could
   ** be detected.\fP
   ** .pp
   ** For detection, $$$folder is first taken into account
   ** and simply stripped to form the result when a match is found. For
   ** example, with $$$folder being \fTimap://host\fP and the folder is
   ** \fTimap://host/INBOX/foo\fP, $$$muttng_folder_name will be just
   ** \fTINBOX/foo\fP.)
   ** .pp
   ** Second, if the initial portion of a name is not $$$folder,
   ** the result will be everything after the last ``/''.
   ** .pp
   ** Third and last, the result will be just the name if neither
   ** $$$folder nor a ``/'' were found in the name.
   */
  {"muttng_pwd", DT_SYS, R_NONE, 0, "" },
  /*
   ** .pp
   ** \fIThis is a read-only system property and, at runtime,
   ** specifies the current working directory of the muttng
   ** binary.\fP
   */
  {"operating_system", DT_STR, R_NONE, UL &OperatingSystem, "" },
  /*
   ** .pp
   ** This specifies the operating system name for the \fTUser-Agent:\fP header field. If
   ** this is \fIunset\fP, it will be set to the operating system name that \fTuname(2)\fP
   ** returns. If \fTuname(2)\fP fails, ``UNIX'' will be used.
   ** .pp
   ** It may, for example, look as: ``\fTmutt-ng 1.5.9i (Linux)\fP''.
   */
  {"sidebar_boundary", DT_STR, R_BOTH, UL &SidebarBoundary, "." },
  /*
   ** .pp
   ** When the sidebar is displayed and $$sidebar_shorten_hierarchy is \fIset\fP, this
   ** variable specifies the characters at which to split a folder name into
   ** ``hierarchy items.''
   */
  {"sidebar_delim", DT_STR, R_BOTH, UL &SidebarDelim, "|"},
  /*
   ** .pp
   ** This specifies the delimiter between the sidebar (if visible) and 
   ** other screens.
   */
  {"sidebar_visible", DT_BOOL, R_BOTH, OPTMBOXPANE, "no" },
  /*
   ** .pp
   ** This specifies whether or not to show the sidebar (a list of folders specified
   ** with the ``mailboxes'' command).
   */
  {"sidebar_width", DT_NUM, R_BOTH, UL &SidebarWidth, "0" },
  /*
   ** .pp
   ** The width of the sidebar.
   */
  {"sidebar_newmail_only", DT_BOOL, R_BOTH, OPTSIDEBARNEWMAILONLY, "no" },
  /*
   ** .pp
   ** If \fIset\fP, only folders with new mail will be shown in the sidebar.
   */
  {"sidebar_number_format", DT_STR, R_BOTH, UL &SidebarNumberFormat, "%m%?n?(%n)?%?f?[%f]?"},
  /*
   ** .pp
   ** This variable controls how message counts are printed when the sidebar
   ** is enabled. If this variable is \fIempty\fP (\fIand only if\fP), no numbers
   ** will be printed \fIand\fP Mutt-ng won't frequently count mail (which
   ** may be a great speedup esp. with mbox-style mailboxes.)
   ** .pp
   ** The following \fTprintf(3)\fP-like sequences are supported all of which
   ** may be printed non-zero:
   ** .pp
   ** .dl
   ** .dt %d .dd Number of deleted messages. 1)
   ** .dt %F .dd Number of flagged messages.
   ** .dt %m .dd Total number of messages.
   ** .dt %M .dd Total number of messages shown, i.e. not hidden by a limit. 1)
   ** .dt %n .dd Number of new messages.
   ** .dt %t .dd Number of tagged messages. 1)
   ** .dt %u .dd Number of unread messages.
   ** .de
   ** .pp
   ** 1) These expandos only have a non-zero value for the current mailbox and
   ** will always be zero otherwise.
   */
  {"sidebar_shorten_hierarchy", DT_BOOL, R_NONE, OPTSHORTENHIERARCHY, "no" },
  /*
   ** .pp
   ** When \fIset\fP, the ``hierarchy'' of the sidebar entries will be shortened
   ** only if they cannot be printed in full length (because ``$$sidebar_width''
   ** is set to a too low value). For example, if the newsgroup name 
   ** ``de.alt.sysadmin.recovery'' doesn't fit on the screen, it'll get shortened
   ** ``d.a.s.recovery'' while ``de.alt.d0'' still would and thus will not get 
   ** shortened.
   ** .pp
   ** At which characters this compression is done is controled via the
   ** $$sidebar_boundary variable.
   */
  {"mbox_type", DT_MAGIC, R_NONE, UL &DefaultMagic, "mbox" },
  /*
   ** .pp
   ** The default mailbox type used when creating new folders. May be any of
   ** \fTmbox\fP, \fTMMDF\fP, \fTMH\fP and \fTMaildir\fP.
   */
  {"metoo", DT_BOOL, R_NONE, OPTMETOO, "no" },
  /*
   ** .pp
   ** If \fIunset\fP, 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_move_off", DT_BOOL, R_NONE, OPTMENUMOVEOFF, "yes" },
  /*
   ** .pp
   ** When \fIunset\fP, the bottom entry of menus will never scroll up past
   ** the bottom of the screen, unless there are less entries than lines.
   ** When \fIset\fP, the bottom entry may move off the bottom.
   */
  {"menu_scroll", DT_BOOL, R_NONE, OPTMENUSCROLL, "no" },
  /*
   ** .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, "no" },
  /*
   ** .pp
   ** If \fIset\fP, forces Mutt-ng to interpret keystrokes with the high bit (bit 8)
   ** set as if the user had pressed the \fTESC\fP key and whatever key remains
   ** after having the high bit removed.  For example, if the key pressed
   ** has an ASCII value of \fT0xf8\fP, then this is treated as if the user had
   ** pressed \fTESC\fP then ``\fTx\fP''.  This is because the result of removing the
   ** high bit from ``\fT0xf8\fP'' is ``\fT0x78\fP'', which is the ASCII character
   ** ``\fTx\fP''.
   */
  {"mh_purge", DT_BOOL, R_NONE, OPTMHPURGE, "no" },
  /*
   ** .pp
   ** When \fIunset\fP, 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, "flagged"},
  /*
   ** .pp
   ** The name of the MH sequence used for flagged messages.
   */
  {"mh_seq_replied", DT_STR, R_NONE, UL &MhReplied, "replied"},
  /*
   ** .pp
   ** The name of the MH sequence used to tag replied messages.
   */
  {"mh_seq_unseen", DT_STR, R_NONE, UL &MhUnseen, "unseen"},
  /*
   ** .pp
   ** The name of the MH sequence used for unseen messages.
   */
  {"mime_forward", DT_QUAD, R_NONE, OPT_MIMEFWD, "no" },
  /*
   ** .pp
   ** When \fIset\fP, the message you are forwarding will be attached as a
   ** separate MIME part instead of included in the main body of the
   ** message.
   ** .pp
   ** 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, "no" },
  /*
   ** .pp
   ** Controls the decoding of complex MIME messages into \fTtext/plain\fP when
   ** forwarding a message while ``$$mime_forward'' is \fIset\fP. Otherwise
   ** ``$$forward_decode'' is used instead.
   */
  {"mime_forward_rest", DT_QUAD, R_NONE, OPT_MIMEFWDREST, "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
  {"nntp_mime_subject", DT_BOOL, R_NONE, OPTMIMESUBJECT, "yes" },
  /*
   ** .pp
   ** Availability: NNTP
   **
   ** .pp
   ** If \fIunset\fP, an 8-bit ``\fTSubject:\fP'' header field in a news article
   ** will not be encoded according to RFC2047.
   ** .pp
   ** \fBNote:\fP Only change this setting if you know what you are doing.
   */
#endif

#ifdef MIXMASTER
  {"mix_entry_format", DT_STR, R_NONE, UL &MixEntryFormat, "%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 \fTprintf(3)\fP-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, 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, "ask-no" },
  /*
   ** .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, "%s"},
  /*
   ** .pp
   ** This is the string displayed in the ``attachment'' menu for
   ** attachments of type \fTmessage/rfc822\fP.  For a full listing of defined
   ** \fTprintf(3)\fP-like sequences see the section on ``$$index_format''.
   */
  {"msgid_format", DT_STR, R_NONE, UL &MsgIdFormat, "%Y%m%d%h%M%s.G%P%p"},
  /*
   ** .pp
   ** This is the format for the ``local part'' of the \fTMessage-ID:\fP header
   ** field generated by Mutt-ng. If this variable is empty, no \fTMessage-ID:\fP
   ** headers will be generated. The '%'
   ** character marks that certain data will be added to the string, similar to
   ** \fTprintf(3)\fP. 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
   ** .pp
   ** \fBNote:\fP Please only change this setting if you know what you are doing.
   ** Also make sure to consult RFC2822 to produce technically \fIvalid\fP strings.
   */
  {"narrow_tree", DT_BOOL, R_TREE|R_INDEX, OPTNARROWTREE, "no" },
  /*
   ** .pp
   ** This variable, when \fIset\fP, makes the thread tree narrower, allowing
   ** deeper threads to fit on the screen.
   */
#ifdef USE_NNTP
  {"nntp_cache_dir", DT_PATH, R_NONE, UL &NewsCacheDir, "~/.muttng"},
  /*
   ** .pp
   ** Availability: NNTP
   **
   ** .pp
   ** This variable points to directory where Mutt-ng will cache news
   ** article headers. If \fIunset\fP, headers will not be saved at all
   ** and will be reloaded each time when you enter a newsgroup.
   ** .pp
   ** As for the header caching in connection with IMAP and/or Maildir,
   ** this drastically increases speed and lowers traffic.
   */
  {"nntp_host", DT_STR, R_NONE, UL &NewsServer, "" },
  /*
   ** .pp
   ** Availability: NNTP
   **
   ** .pp
   ** This variable specifies the name (or address) of the NNTP server to be used.
   ** .pp
   ** It
   ** defaults to the value specified via the environment variable
   ** \fT$$$NNTPSERVER\fP or contained in the file \fT/etc/nntpserver\fP.
   ** .pp
   ** You can also
   ** specify a username and an alternative port for each newsserver, e.g.
   ** .pp
   ** \fT[nntp[s]://][username[:password]@]newsserver[:port]\fP
   ** .pp
   ** \fBNote:\fP Using a password as shown and stored in a configuration file
   ** presents a security risk since the superuser of your machine may read it
   ** regardless of the file's permissions.
   */
  {"nntp_newsrc", DT_PATH, R_NONE, UL &NewsRc, "~/.newsrc"},
  /*
   ** .pp
   ** Availability: NNTP
   **
   ** .pp
   ** This file contains information about subscribed newsgroup and
   ** articles read so far.
   ** .pp
   ** To ease the use of multiple news servers, the following \fTprintf(3)\fP-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 controls how many news articles to cache per newsgroup
   ** (if caching is enabled, see $$nntp_cache_dir) and how many news articles
   ** to show in the ``index'' menu.
   ** .pp
   ** If there're more articles than defined with $$nntp_context, all older ones
   ** will be removed/not shown in the index.
   */
  {"nntp_load_description", DT_BOOL, R_NONE, OPTLOADDESC, "yes" },
  /*
   ** .pp
   ** Availability: NNTP
   **
   ** .pp
   ** This variable controls whether or not descriptions for newsgroups
   ** are to be loaded when subscribing to a newsgroup.
   */
  {"nntp_user", DT_STR, R_NONE, UL &NntpUser, ""},
  /*
   ** .pp
   ** Availability: NNTP
   **
   ** .pp
   ** Your login name on the NNTP server.  If \fIunset\fP and the server requires
   ** authentification, Mutt-ng will prompt you for your account name.
   */
  {"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, Mutt-ng 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 Mutt-ng will try to reconnect to a newsserver when the
   ** was connection lost.
   */
#endif
#ifdef USE_SOCKET
  { "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''.
  */
#endif 
  {"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 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, "-%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 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 \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 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 \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 Mutt-ng 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 Mutt-ng 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, 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 \fIunset\fP this setting.
   ** (Crypto only)
   */
  {"pgp_use_gpg_agent", DT_BOOL, R_NONE, OPTUSEGPGAGENT, "no" },
  /*
   ** .pp
   ** If \fIset\fP, Mutt-ng 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 Mutt-ng 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 Mutt-ng 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 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, "%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, 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, "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 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_replyinline", DT_BOOL, R_NONE, OPTPGPREPLYINLINE, "no" },
  /*
   ** .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, "yes" },
  /*
   ** .pp
   ** If \fIset\fP, 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, "" },
  /*
   ** .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., ``\fT0x00112233\fP'').
   ** (PGP only)
   */
  {"pgp_strict_enc", DT_BOOL, R_NONE, OPTPGPSTRICTENC, "yes" },
  /*
   ** .pp
   ** If \fIset\fP, Mutt-ng will automatically encode PGP/MIME signed messages as
   ** \fTquoted-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. Default: 300.
   ** (PGP only)
   */
  {"pgp_sort_keys", DT_SORT|DT_SORT_KEYS, R_NONE, UL &PgpSortKeys, "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, "ask-yes" },
  /*
   ** .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, "no" },
  /*
   ** .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, "" },
  /*
   ** .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, "" },
  /*
   ** .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, "" },
  /*
   ** .pp
   ** This command is used to verify PGP signatures.
   ** (PGP only)
   */
  {"pgp_decrypt_command", DT_STR, R_NONE, UL &PgpDecryptCommand, "" },
  /*
   ** .pp
   ** This command is used to decrypt a PGP encrypted message.
   ** (PGP only)
   */
  {"pgp_clearsign_command", DT_STR, R_NONE, UL &PgpClearSignCommand, "" },
  /*
   ** .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, "" },
  /*
   ** .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, "" },
  /*
   ** .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, "" },
  /*
   ** .pp
   ** This command is used to encrypt a body part without signing it.
   ** (PGP only)
   */
  {"pgp_import_command", DT_STR, R_NONE, UL &PgpImportCommand, "" },
  /*
   ** .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, "" },
  /*
   ** .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, "" },
  /*
   ** .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, "" },
  /*
   ** .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, "" },
  /*
   ** .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, "yes" },
  /*
   ** .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, "" },
  /*
   ** .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, "" },
  /*
   ** .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, "" },
  /*
   ** .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, "" },
  /*
   ** .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, "" },
  /*
   ** .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, "" },
  /*
   ** .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, "" },
  /*
   ** .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, "" },
  /*
   ** .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, "" },
  /*
   ** .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, "" },
  /*
   ** .pp
   ** This command is used to create encrypted S/MIME messages.
   ** (S/MIME only)
   */
  {"smime_pk7out_command", DT_STR, R_NONE, UL &SmimePk7outCommand, "" },
  /*
   ** .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, "" },
  /*
   ** .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, "" },
  /*
   ** .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, "" },
  /*
   ** .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, "" },
  /*
   ** .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, "" },
  /*
   ** .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, "" },
  /*
   ** .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, "" },
  /*
   ** .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_SYN, R_NONE, UL "envelope_from_address", 0 },

  {"smtp_host", DT_STR, R_NONE, UL &SmtpHost, "" },
  /*
   ** .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, "" },
  /*
   ** .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, "" },
  /*
   ** .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, "no" },
  /*
   ** .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, "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, "~/.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, "yes" },
  /*
   ** .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, "" },
  /*
   ** .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, "no" },
  /*
   ** .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, "yes" },
  /*
   ** .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, "yes" },
  /*
   ** .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, "" },
  /*
   ** .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, "no" },
  /*
   ** .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, "no" },
  /*
   ** .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, "\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, "" },
  /*
   ** .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, "yes" },
  /*
   ** .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) Mutt-ng should look for
   ** new mail.
   */
  {"pop_delete", DT_QUAD, R_NONE, OPT_POPDELETE, "ask-no" },
  /*
   ** .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, ""},
  /*
   ** .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, "no" },
  /*
   ** .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, "ask-yes" },
  /*
   ** .pp
   ** Availability: POP
   **
   ** .pp
   ** Controls whether or not Mutt-ng will try to reconnect to a POP server if the
   ** connection is lost.
   */
  {"pop_user", DT_STR, R_NONE, UL &PopUser, "" },
  /*
   ** .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, ""},
  /*
   ** .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, ""},
  /*
   ** .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
  {"nntp_post_moderated", DT_QUAD, R_NONE, OPT_TOMODERATED, "ask-yes" },
  /*
   ** .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, "ask-yes" },
  /*
   ** .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, "~/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, "" },
  /*
   ** .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, "ask-no" },
  /*
   ** .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, "lpr"},
  /*
   ** .pp
   ** This specifies the command pipe that should be used to print messages.
   */
  {"print_decode", DT_BOOL, R_NONE, OPTPRINTDECODE, "yes" },
  /*
   ** .pp
   ** Used in connection with the print-message command.  If this
   ** option is \fIset\fP, the message is decoded before it is passed to the
   ** external command specified by $$print_command.  If this option
   ** is \fIunset\fP, 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, "no" },
  /*
   ** .pp
   ** Used in connection with the print-message command.  If this option
   ** is \fIset\fP, the command specified by $$print_command is executed once for
   ** each message which is to be printed.  If this option is \fIunset\fP, 
   ** 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 \fTenscript(1)\fP program's mail-printing mode will
   ** most likely want to set this option.
   */
  {"prompt_after", DT_BOOL, R_NONE, OPTPROMPTAFTER, "yes" },
  /*
   ** .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 \fIunset\fP, Mutt-ng will return to the
   ** index menu when the external pager exits.
   */
  {"query_command", DT_PATH, R_NONE, UL &QueryCmd, ""},
  /*
   ** .pp
   ** This specifies the command that Mutt-ng will use to make external address
   ** queries.  The string should contain a \fT%s\fP, which will be substituted
   ** with the query string the user types.  See ``$query'' for more
   ** information.
   */
  {"quit", DT_QUAD, R_NONE, OPT_QUIT, "yes" },
  /*
   ** .pp
   ** This variable controls whether ``quit'' and ``exit'' actually quit
   ** from Mutt-ng.  If it set to \fIyes\fP, they do quit, if it is set to \fIno\fP, they
   ** have no effect, and if it is set to \fIask-yes\fP or \fIask-no\fP, you are
   ** prompted for confirmation when you try to quit.
   */
  {"quote_empty", DT_BOOL, R_NONE, OPTQUOTEEMPTY, "yes" },
  /*
   ** .pp
   ** Controls whether or not empty lines will be quoted using
   ** ``$indent_string''.
   */
  {"quote_quoted", DT_BOOL, R_NONE, OPTQUOTEQUOTED, "no" },
  /*
   ** .pp
   ** Controls how quoted lines will be quoted. If \fIset\fP, 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, "^([ \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, "no" },
  /*
   ** .pp
   ** If set, all folders are opened in read-only mode.
   */
  {"realname", DT_STR, R_BOTH, UL &Realname, "" },
  /*
   ** .pp
   ** This variable specifies what ``real'' or ``personal'' name should be used
   ** when sending messages.
   ** .pp
   ** By default, this is the GECOS field from \fT/etc/passwd\fP.
   ** .pp
   ** \fINote:\fP 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, "ask-yes" },
  /*
   ** .pp
   ** Controls whether or not Mutt-ng recalls postponed messages
   ** when composing a new message.  Also see ``$$postponed''.
   ** .pp
   ** Setting this variable to \fIyes\fP is not generally useful, and thus not
   ** recommended.
   */
  {"record", DT_PATH, R_NONE, UL &Outbox, ""},
  /*
   ** .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 \fTBcc:\fP header 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, "^(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, "no" },
  /*
   ** .pp
   ** If \fIunset\fP 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, "ask-yes" },
  /*
   ** .pp
   ** If \fIset\fP, when replying to a message, Mutt-ng will use the address listed
   ** in the ``\fTReply-To:\fP'' header field as the recipient of the reply.  If \fIunset\fP,
   ** it will use the address in the ``\fTFrom:\fP'' header field instead.
   ** .pp 
   ** This
   ** option is useful for reading a mailing list that sets the ``\fTReply-To:\fP''
   ** 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, "yes" },
  /*
   ** .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, "no" },
  /*
   ** .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
   **  \fTalias juser abd30425@somewhere.net (Joe User)\fP
   ** .pp
   ** and then you receive mail which contains the following header:
   ** .pp
   **  \fTFrom: abd30425@somewhere.net\fP
   ** .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, "no" },
  /*
   ** .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 \fIset\fP, the default \fTFrom:\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 \fIunset\fP, or the address that would be
   ** used doesn't match your alternates, the \fTFrom:\fP line will use
   ** your address on the current machine.
   */
  {"reverse_realname", DT_BOOL, R_BOTH, OPTREVREAL, "yes" },
  /*
   ** .pp
   ** This variable fine-tunes the behaviour of the $reverse_name feature.
   ** When it is \fIset\fP, Mutt-ng will use the address from incoming messages as-is,
   ** possibly including eventual real names.  When it is \fIunset\fP, Mutt-ng will
   ** override any such real names with the setting of the $realname variable.
   */
  {"rfc2047_parameters", DT_BOOL, R_NONE, OPTRFC2047PARAMS, "no" },
  /*
   ** .pp
   ** When this variable is \fIset\fP, Mutt-ng will decode RFC-2047-encoded MIME 
   ** parameters. You want to set this variable when Mutt-ng suggests you
   ** to save attachments to files named like this:
   ** .pp
   **  \fT=?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=\fP
   ** .pp
   ** When this variable is \fIset\fP interactively, the change doesn't have
   ** the desired effect before you have changed folders.
   ** .pp
   ** Note that this use of RFC 2047's encoding is explicitly,
   ** prohibited by the standard, but nevertheless encountered in the
   ** wild.
   ** .pp
   ** Also note that setting this parameter will \fInot\fP have the effect 
   ** that Mutt-ng \fIgenerates\fP this kind of encoding.  Instead, Mutt-ng will
   ** unconditionally use the encoding specified in RFC 2231.
   */
  {"save_address", DT_BOOL, R_NONE, OPTSAVEADDRESS, "no" },
  /*
   ** .pp
   ** If \fIset\fP, Mutt-ng will take the sender's full address when choosing a
   ** default folder for saving a mail. If ``$$save_name'' or ``$$force_name''
   ** is \fIset\fP too, the selection of the fcc folder will be changed as well.
   */
  {"save_empty", DT_BOOL, R_NONE, OPTSAVEEMPTY, "yes" },
  /*
   ** .pp
   ** When \fIunset\fP, mailboxes which contain no saved messages will be removed
   ** when closed (the exception is ``$$spoolfile'' which is never removed).
   ** If \fIset\fP, mailboxes are never removed.
   ** .pp
   ** \fBNote:\fP This only applies to mbox and MMDF folders, Mutt-ng does not
   ** delete MH and Maildir directories.
   */
  {"save_name", DT_BOOL, R_NONE, OPTSAVENAME, "no" },
  /*
   ** .pp
   ** This variable controls how copies of outgoing messages are saved.
   ** When set, a check is made to see if a mailbox specified by the
   ** recipient address exists (this is done by searching for a mailbox in
   ** the ``$$folder'' directory with the \fIusername\fP part of the
   ** recipient address).  If the mailbox exists, the outgoing message will
   ** be saved to that mailbox, otherwise the message is saved to the
   ** ``$$record'' mailbox.
   ** .pp
   ** Also see the ``$$force_name'' variable.
   */
  {"score", DT_BOOL, R_NONE, OPTSCORE, "yes" },
  /*
   ** .pp
   ** When this variable is \fIunset\fP, scoring is turned off.  This can
   ** be useful to selectively disable scoring for certain folders when the
   ** ``$$score_threshold_delete'' variable and friends are used.
   **
   */
  {"score_threshold_delete", DT_NUM, R_NONE, UL &ScoreThresholdDelete, "-1" },
  /*
   ** .pp
   ** Messages which have been assigned a score equal to or lower than the value
   ** of this variable are automatically marked for deletion by Mutt-ng.  Since
   ** Mutt-ng scores are always greater than or equal to zero, the default setting
   ** of this variable will never mark a message for deletion.
   */
  {"score_threshold_flag", DT_NUM, R_NONE, UL &ScoreThresholdFlag, "9999" },
  /* 
   ** .pp
   ** Messages which have been assigned a score greater than or equal to this 
   ** variable's value are automatically marked ``flagged''.
   */
  {"score_threshold_read", DT_NUM, R_NONE, UL &ScoreThresholdRead, "-1" },
  /*
   ** .pp
   ** Messages which have been assigned a score equal to or lower than the value
   ** of this variable are automatically marked as read by Mutt-ng.  Since
   ** Mutt-ng scores are always greater than or equal to zero, the default setting
   ** of this variable will never mark a message read.
   */
  {"send_charset", DT_STR, R_NONE, UL &SendCharset, "us-ascii:iso-8859-1:utf-8"},
  /*
   ** .pp
   ** A list of character sets for outgoing messages. Mutt-ng will use the
   ** first character set into which the text can be converted exactly.
   ** If your ``$$charset'' is not \fTiso-8859-1\fP and recipients may not
   ** understand \fTUTF-8\fP, it is advisable to include in the list an
   ** appropriate widely used standard character set (such as
   ** \fTiso-8859-2\fP, \fTkoi8-r\fP or \fTiso-2022-jp\fP) either
   ** instead of or after \fTiso-8859-1\fP.
   */
  {"sendmail", DT_PATH, R_NONE, UL &Sendmail, SENDMAIL " -oem -oi"},
  /*
   ** .pp
   ** Specifies the program and arguments used to deliver mail sent by Mutt-ng.
   ** Mutt-ng expects that the specified program interprets additional
   ** arguments as recipient addresses.
   */
  {"sendmail_wait", DT_NUM, R_NONE, UL &SendmailWait, "0" },
  /*
   ** .pp
   ** Specifies the number of seconds to wait for the ``$$sendmail'' process
   ** to finish before giving up and putting delivery in the background.
   ** .pp
   ** Mutt-ng interprets the value of this variable as follows:
   ** .dl
   ** .dt >0 .dd number of seconds to wait for sendmail to finish before continuing
   ** .dt 0  .dd wait forever for sendmail to finish
   ** .dt <0 .dd always put sendmail in the background without waiting
   ** .de
   ** .pp
   ** Note that if you specify a value other than 0, the output of the child
   ** process will be put in a temporary file.  If there is some error, you
   ** will be informed as to where to find the output.
   */
  {"shell", DT_PATH, R_NONE, UL &Shell, "" },
  /*
   ** .pp
   ** Command to use when spawning a subshell.  By default, the user's login
   ** shell from \fT/etc/passwd\fP is used.
   */
#ifdef USE_NNTP
  {"nntp_save_unsubscribed", DT_BOOL, R_NONE, OPTSAVEUNSUB, "no" },
  /*
   ** .pp
   ** Availability: NNTP
   **
   ** .pp
   ** When \fIset\fP, info about unsubscribed newsgroups will be saved into the
   ** ``newsrc'' file and into the news cache.
   */
#endif
#ifdef USE_NNTP
  {"nntp_show_new_news", DT_BOOL, R_NONE, OPTSHOWNEWNEWS, "yes" },
  /*
   ** .pp
   ** Availability: NNTP
   **
   ** .pp
   ** If \fIset\fP, the newsserver will be asked for new newsgroups on entering
   ** the browser.  Otherwise, it will be done only once for a newsserver.
   ** Also controls whether or not the number of new articles of subscribed
   ** newsgroups will be checked.
   */
  {"nntp_show_only_unread", DT_BOOL, R_NONE, OPTSHOWONLYUNREAD, "no" },
  /*
   ** .pp
   ** Availability: NNTP
   **
   ** .pp
   ** If \fIset\fP, only subscribed newsgroups that contain unread articles
   ** will be displayed in the newsgroup browser.
   */
#endif
  {"sig_dashes", DT_BOOL, R_NONE, OPTSIGDASHES, "yes" },
  /*
   ** .pp
   ** If set, a line containing ``\fT-- \fP'' (dash, dash, space)
   ** will be inserted before your ``$$signature''.  It is \fBstrongly\fP
   ** recommended that you not unset this variable unless your ``signature''
   ** contains just your name. The reason for this is because many software
   ** packages use ``\fT-- \n\fP'' to detect your signature.
   ** .pp
   ** For example, Mutt-ng has the ability to highlight
   ** the signature in a different color in the builtin pager.
   */
  {"sig_on_top", DT_BOOL, R_NONE, OPTSIGONTOP, "no" },
  /*
   ** .pp
   ** If \fIset\fP, the signature will be included before any quoted or forwarded
   ** text.  It is \fBstrongly\fP recommended that you do not set this variable
   ** unless you really know what you are doing, and are prepared to take
   ** some heat from netiquette guardians.
   */
  {"signature", DT_PATH, R_NONE, UL &Signature, "~/.signature"},
  /*
   ** .pp
   ** Specifies the filename of your signature, which is appended to all
   ** outgoing messages.   If the filename ends with a pipe (``\fT|\fP''), it is
   ** assumed that filename is a shell command and input should be read from
   ** its stdout.
   */
  {"signoff_string", DT_STR, R_NONE, UL &SignOffString, "" },
  /*
   ** .pp
   ** If \fIset\fP, this string will be inserted before the signature. This is useful
   ** for people that want to sign off every message they send with their name.
   ** .pp
   ** If you want to insert your website's URL, additional contact information or 
   ** witty quotes into your mails, better use a signature file instead of
   ** the signoff string.
   */
  {"simple_search", DT_STR, R_NONE, UL &SimpleSearch, "~f %s | ~s %s"},
  /*
   ** .pp
   ** Specifies how Mutt-ng should expand a simple search into a real search
   ** pattern.  A simple search is one that does not contain any of the ~
   ** operators.  See ``$patterns'' for more information on search patterns.
   ** .pp
   ** For example, if you simply type ``joe'' at a search or limit prompt, Mutt-ng
   ** will automatically expand it to the value specified by this variable.
   ** For the default value it would be:
   ** .pp
   ** \fT~f joe | ~s joe\fP
   */
  {"smart_wrap", DT_BOOL, R_PAGER, OPTWRAP, "yes" },
  /*
   ** .pp
   ** Controls the display of lines longer than the screen width in the
   ** internal pager. If \fIset\fP, long lines are wrapped at a word boundary.
   ** If \fIunset\fP, lines are simply wrapped at the screen edge. Also see the
   ** ``$$markers'' variable.
   */
  {"smileys", DT_RX, R_PAGER, UL &Smileys, "(>From )|(:[-^]?[][)(><}{|/DP])"},
  /*
   ** .pp
   ** The \fIpager\fP uses this variable to catch some common false
   ** positives of ``$$quote_regexp'', most notably smileys in the beginning
   ** of a line
   */
  {"sleep_time", DT_NUM, R_NONE, UL &SleepTime, "1" },
  /*
   ** .pp
   ** Specifies time, in seconds, to pause while displaying certain informational
   ** messages, while moving from folder to folder and after expunging
   ** messages from the current folder.  The default is to pause one second, so 
   ** a value of zero for this option suppresses the pause.
   */
  {"sort", DT_SORT, R_INDEX|R_RESORT, UL &Sort, "date" },
  /*
   ** .pp
   ** Specifies how to sort messages in the \fIindex\fP menu.  Valid values
   ** are:
   ** .pp
   ** .ts
   ** .  date or date-sent
   ** .  date-received
   ** .  from
   ** .  mailbox-order (unsorted)
   ** .  score
   ** .  size
   ** .  spam
   ** .  subject
   ** .  threads
   ** .  to
   ** .te
   ** .pp
   ** You may optionally use the ``reverse-'' prefix to specify reverse sorting
   ** order (example: \fTset sort=reverse-date-sent\fP).
   */
  {"sort_alias", DT_SORT|DT_SORT_ALIAS, R_NONE, UL &SortAlias, "alias" },
  /*
   ** .pp
   ** Specifies how the entries in the ``alias'' menu are sorted.  The
   ** following are legal values:
   ** .pp
   ** .ts
   ** .  address (sort alphabetically by email address)
   ** .  alias (sort alphabetically by alias name)
   ** .  unsorted (leave in order specified in .muttrc)
   ** .te
   */
  {"sort_aux", DT_SORT|DT_SORT_AUX, R_INDEX|R_RESORT_BOTH, UL &SortAux, "date" },
  /*
   ** .pp
   ** When sorting by threads, this variable controls how threads are sorted
   ** in relation to other threads, and how the branches of the thread trees
   ** are sorted.  This can be set to any value that ``$$sort'' can, except
   ** threads (in that case, Mutt-ng will just use date-sent).  You can also
   ** specify the ``last-'' prefix in addition to ``reverse-'' prefix, but last-
   ** must come after reverse-.  The last- prefix causes messages to be
   ** sorted against its siblings by which has the last descendant, using
   ** the rest of sort_aux as an ordering.
   ** .pp
   ** For instance, \fTset sort_aux=last-date-received\fP would mean that if
   ** a new message is received in a thread, that thread becomes the last one
   ** displayed (or the first, if you have \fTset sort=reverse-threads\fP.)
   ** .pp
   ** \fBNote:\fP For reversed ``$$sort'' order $$sort_aux is reversed again
   ** (which is not the right thing to do, but kept to not break any existing
   ** configuration setting).
   */
  {"sort_browser", DT_SORT|DT_SORT_BROWSER, R_NONE, UL &BrowserSort, "alpha" },
  /*
   ** .pp
   ** Specifies how to sort entries in the file browser.  By default, the
   ** entries are sorted alphabetically.  Valid values:
   ** .pp
   ** .ts
   ** .  alpha (alphabetically)
   ** .  date
   ** .  size
   ** .  unsorted
   ** .te
   ** .pp
   ** You may optionally use the ``reverse-'' prefix to specify reverse sorting
   ** order (example: \fTset sort_browser=reverse-date\fP).
   */
  {"sort_re", DT_BOOL, R_INDEX|R_RESORT|R_RESORT_INIT, OPTSORTRE, "yes" },
  /*
   ** .pp
   ** This variable is only useful when sorting by threads with
   ** ``$$strict_threads'' \fIunset\fP. In that case, it changes the heuristic
   ** Mutt-ng uses to thread messages by subject.  With $$sort_re \fIset\fP,
   ** Mutt-ng will only attach a message as the child of another message by
   ** subject if the subject of the child message starts with a substring
   ** matching the setting of ``$$reply_regexp''. With $$sort_re \fIunset\fP,
   ** Mutt-ng will attach the message whether or not this is the case,
   ** as long as the non-``$$reply_regexp'' parts of both messages are identical.
   */
  {"spam_separator", DT_STR, R_NONE, UL &SpamSep, ","},
  /*
   ** .pp
   ** ``$spam_separator'' controls what happens when multiple spam headers
   ** are matched: if \fIunset\fP, each successive header will overwrite any
   ** previous matches value for the spam label. If \fIset\fP, each successive
   ** match will append to the previous, using ``$spam_separator'' as a
   ** separator.
   */
  {"spoolfile", DT_PATH, R_NONE, UL &Spoolfile, "" },
  /*
   ** .pp
   ** If your spool mailbox is in a non-default place where Mutt-ng cannot find
   ** it, you can specify its location with this variable.  Mutt-ng will
   ** automatically set this variable to the value of the environment
   ** variable $$$MAIL if it is not set.
   */
  {"status_chars", DT_STR, R_BOTH, UL &StChars, "-*%A"},
  /*
   ** .pp
   ** Controls the characters used by the ``\fT%r\fP'' indicator in
   ** ``$$status_format''. The first character is used when the mailbox is
   ** unchanged. The second is used when the mailbox has been changed, and
   ** it needs to be resynchronized. The third is used if the mailbox is in
   ** read-only mode, or if the mailbox will not be written when exiting
   ** that mailbox (You can toggle whether to write changes to a mailbox
   ** with the toggle-write operation, bound by default to ``\fT%\fP'').
   ** The fourth  is used to indicate that the current folder has been
   ** opened in attach-message mode (Certain operations like composing
   ** a new mail, replying, forwarding, etc. are not permitted in this mode).
   */
  {"status_format", DT_STR, R_BOTH, UL &Status, "-%r-Mutt-ng: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l? %l?]---(%s/%S)-%>-(%P)---"},
  /*
   ** .pp
   ** Controls the format of the status line displayed in the \fIindex\fP
   ** menu.  This string is similar to ``$$index_format'', but has its own
   ** set of \fTprintf(3)\fP-like sequences:
   ** .pp
   ** .dl
   ** .dt %b  .dd number of mailboxes with new mail *
   ** .dt %B  .dd the short pathname of the current mailbox
   ** .dt %d  .dd number of deleted messages *
   ** .dt %f  .dd the full pathname of the current mailbox
   ** .dt %F  .dd number of flagged messages *
   ** .dt %h  .dd local hostname
   ** .dt %l  .dd size (in bytes) of the current mailbox *
   ** .dt %L  .dd size (in bytes) of the messages shown 
   **             (i.e., which match the current limit) *
   ** .dt %m  .dd the number of messages in the mailbox *
   ** .dt %M  .dd the number of messages shown (i.e., which match the current limit) *
   ** .dt %n  .dd number of new messages in the mailbox *
   ** .dt %o  .dd number of old unread messages *
   ** .dt %p  .dd number of postponed messages *
   ** .dt %P  .dd percentage of the way through the index
   ** .dt %r  .dd modified/read-only/won't-write/attach-message indicator,
   **             according to $$status_chars
   ** .dt %s  .dd current sorting mode ($$sort)
   ** .dt %S  .dd current aux sorting method ($$sort_aux)
   ** .dt %t  .dd number of tagged messages *
   ** .dt %u  .dd number of unread messages *
   ** .dt %v  .dd Mutt-ng version string
   ** .dt %V  .dd currently active limit pattern, if any *
   ** .dt %>X .dd right justify the rest of the string and pad with "X"
   ** .dt %|X .dd pad to the end of the line with "X"
   ** .de
   ** .pp
   ** * = can be optionally printed if nonzero
   ** .pp
   ** Some of the above sequences can be used to optionally print a string
   ** if their value is nonzero.  For example, you may only want to see the
   ** number of flagged messages if such messages exist, since zero is not
   ** particularly meaningful.  To optionally print a string based upon one
   ** of the above sequences, the following construct is used
   ** .pp
   **  \fT%?<sequence_char>?<optional_string>?\fP
   ** .pp
   ** where \fIsequence_char\fP is a character from the table above, and
   ** \fIoptional_string\fP is the string you would like printed if
   ** \fIsequence_char\fP is nonzero.  \fIoptional_string\fP \fBmay\fP contain
   ** other sequences as well as normal text, but you may \fBnot\fP nest
   ** optional strings.
   ** .pp
   ** Here is an example illustrating how to optionally print the number of
   ** new messages in a mailbox:
   ** .pp
   **  \fT%?n?%n new messages.?\fP
   ** .pp
   ** Additionally you can switch between two strings, the first one, if a
   ** value is zero, the second one, if the value is nonzero, by using the
   ** following construct:
   ** .pp
   **  \fT%?<sequence_char>?<if_string>&<else_string>?\fP
   ** .pp
   ** You can additionally force the result of any \fTprintf(3)\fP-like sequence
   ** to be lowercase by prefixing the sequence character with an underscore
   ** (\fT_\fP) sign.  For example, if you want to display the local hostname in
   ** lowercase, you would use:
   ** .pp
   **  \fT%_h\fP
   ** .pp
   ** If you prefix the sequence character with a colon (\fT:\fP) character, Mutt-ng
   ** will replace any dots in the expansion by underscores. This might be helpful 
   ** with IMAP folders that don't like dots in folder names.
   */
  {"status_on_top", DT_BOOL, R_BOTH, OPTSTATUSONTOP, "no" },
  /*
   ** .pp
   ** Setting this variable causes the ``status bar'' to be displayed on
   ** the first line of the screen rather than near the bottom.
   */
  {"strict_mailto", DT_BOOL, R_NONE, OPTSTRICTMAILTO, "yes" },
  /*
   **
   ** .pp
   ** With mailto: style links, a body as well as arbitrary header information
   ** may be embedded. This may lead to (user) headers being overwriten without note
   ** if ``$$edit_headers'' is unset.
   **
   ** .pp
   ** If this variable is \fIset\fP, Mutt-ng is strict and allows anything to be
   ** changed. If it's \fIunset\fP, all headers given will be prefixed with
   ** ``X-Mailto-'' and the message including headers will be shown in the editor
   ** regardless of what ``$$edit_headers'' is set to.
   **/
  {"strict_mime", DT_BOOL, R_NONE, OPTSTRICTMIME, "yes" },
  /*
   ** .pp
   ** When \fIunset\fP, non MIME-compliant messages that doesn't have any
   ** charset indication in the ``\fTContent-Type:\fP'' header field can 
   ** be displayed (non MIME-compliant messages are often generated by old
   ** mailers or buggy mailers like MS Outlook Express).
   ** See also $$assumed_charset.
   ** .pp
   ** This option also replaces linear-white-space between encoded-word
   ** and *text to a single space to prevent the display of MIME-encoded
   ** ``\fTSubject:\fP'' header field from being devided into multiple lines.
   */
  {"strict_threads", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTSTRICTTHREADS, "no" },
  /*
   ** .pp
   ** If \fIset\fP, threading will only make use of the ``\fTIn-Reply-To:\fP'' and
   ** ``\fTReferences:\fP'' header fields when you ``$$sort'' by message threads.  By
   ** default, messages with the same subject are grouped together in
   ** ``pseudo threads.''  This may not always be desirable, such as in a
   ** personal mailbox where you might have several unrelated messages with
   ** the subject ``hi'' which will get grouped together. See also
   ** ``$$sort_re'' for a less drastic way of controlling this
   ** behaviour.
   */
  {"strip_was", DT_BOOL, R_NONE, OPTSTRIPWAS, "no" },
  /**
  ** .pp
  ** When \fIset\fP, Mutt-ng will remove the trailing part of the ``\fTSubject:\fP''
  ** line which matches $$strip_was_regex when replying. This is useful to
  ** properly react on subject changes and reduce ``subject noise.'' (esp. in Usenet)
  **/
  {"strip_was_regex", DT_RX, R_NONE, UL &StripWasRegexp, "\\([Ww][Aa][RrSs]: .*\\)[ ]*$"},
  /**
  ** .pp
  ** When non-empty and $$strip_was is \fIset\fP, Mutt-ng will remove this
  ** trailing part of the ``Subject'' line when replying if it won't be empty
  ** afterwards.
  **/
  {"stuff_quoted", DT_BOOL, R_BOTH, OPTSTUFFQUOTED, "no" },
  /*
   ** .pp
   ** If \fIset\fP, attachments with flowed format will have their quoting ``stuffed'',
   ** i.e. a space will be inserted between the quote characters and the actual
   ** text.
   */
  {"suspend", DT_BOOL, R_NONE, OPTSUSPEND, "yes" },
  /*
   ** .pp
   ** When \fIunset\fP, Mutt-ng won't stop when the user presses the terminal's
   ** \fIsusp\fP key, usually \fTCTRL+Z\fP. This is useful if you run Mutt-ng
   ** inside an xterm using a command like ``\fTxterm -e muttng\fP.''
   */
  {"text_flowed", DT_BOOL, R_NONE, OPTTEXTFLOWED, "no" },
  /*
   ** .pp
   ** When \fIset\fP, Mutt-ng will generate \fTtext/plain; format=flowed\fP attachments.
   ** This format is easier to handle for some mailing software, and generally
   ** just looks like ordinary text.  To actually make use of this format's 
   ** features, you'll need support in your editor.
   ** .pp
   ** Note that $$indent_string is ignored when this option is set.
   */
  {"thread_received", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTTHREADRECEIVED, "no" },
  /*
   ** .pp
   ** When \fIset\fP, Mutt-ng uses the date received rather than the date sent
   ** to thread messages by subject.
   */
  {"thorough_search", DT_BOOL, R_NONE, OPTTHOROUGHSRC, "no" },
  /*
   ** .pp
   ** Affects the \fT~b\fP and \fT~h\fP search operations described in
   ** section ``$patterns'' above.  If \fIset\fP, the headers and attachments of
   ** messages to be searched are decoded before searching.  If \fIunset\fP,
   ** messages are searched as they appear in the folder.
   */
  {"tilde", DT_BOOL, R_PAGER, OPTTILDE, "no" },
  /*
   ** .pp
   ** When \fIset\fP, the internal-pager will pad blank lines to the bottom of the
   ** screen with a tilde (~).
   */
  {"timeout", DT_NUM, R_NONE, UL &Timeout, "600" },
  /*
   ** .pp
   ** This variable controls the \fInumber of seconds\fP Mutt-ng will wait
   ** for a key to be pressed in the main menu before timing out and
   ** checking for new mail.  A value of zero or less will cause Mutt-ng
   ** to never time out.
   */
  {"tmpdir", DT_PATH, R_NONE, UL &Tempdir, "" },
  /*
   ** .pp
   ** This variable allows you to specify where Mutt-ng will place its
   ** temporary files needed for displaying and composing messages.  If
   ** this variable is not set, the environment variable \fT$$$TMPDIR\fP is
   ** used.  If \fT$$$TMPDIR\fP is not set then "\fT/tmp\fP" is used.
   */
  {"to_chars", DT_STR, R_BOTH, UL &Tochars, " +TCFL"},
  /*
   ** .pp
   ** Controls the character used to indicate mail addressed to you.  The
   ** first character is the one used when the mail is NOT addressed to your
   ** address (default: space).  The second is used when you are the only
   ** recipient of the message (default: +).  The third is when your address
   ** appears in the ``\fTTo:\fP'' header field, but you are not the only recipient of
   ** the message (default: T).  The fourth character is used when your
   ** address is specified in the ``\fTCc:\fP'' header field, but you are not the only
   ** recipient.  The fifth character is used to indicate mail that was sent
   ** by \fIyou\fP.  The sixth character is used to indicate when a mail
   ** was sent to a mailing-list you're subscribe to (default: L).
   */
  {"trash", DT_PATH, R_NONE, UL &TrashPath, "" },
  /*
   ** .pp
   ** If \fIset\fP, this variable specifies the path of the trash folder where the
   ** mails marked for deletion will be moved, instead of being irremediably
   ** purged.
   ** .pp
   ** \fBNote\fP: When you delete a message in the trash folder, it is really
   ** deleted, so that there is no way to recover mail.
   */
#ifdef USE_SOCKET
  {"tunnel", DT_STR, R_NONE, UL &Tunnel, "" },
  /*
   ** .pp
   ** Setting this variable will cause Mutt-ng to open a pipe to a command
   ** instead of a raw socket. You may be able to use this to set up
   ** preauthenticated connections to your IMAP/POP3 server. Example:
   ** .pp
   **  \fTtunnel="ssh -q mailhost.net /usr/local/libexec/imapd"\fP
   ** .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
  {"umask", DT_NUM, R_NONE, UL &Umask, "0077" },
  /*
   ** .pp
   ** This sets the umask that will be used by Mutt-ng when creating all
   ** kinds of files. If \fIunset\fP, the default value is \fT077\fP.
   */
  {"use_8bitmime", DT_BOOL, R_NONE, OPTUSE8BITMIME, "no" },
  /*
   ** .pp
   ** \fBWarning:\fP do not set this variable unless you are using a version
   ** of sendmail which supports the \fT-B8BITMIME\fP flag (such as sendmail
   ** 8.8.x) or in connection with the SMTP support via libESMTP.
   ** Otherwise you may not be able to send mail.
   ** .pp
   ** When \fIset\fP, Mutt-ng will either invoke ``$$sendmail'' with the \fT-B8BITMIME\fP
   ** flag when sending 8-bit messages to enable ESMTP negotiation or tell
   ** libESMTP to do so.
   */
  {"use_domain", DT_BOOL, R_NONE, OPTUSEDOMAIN, "yes" },
  /*
   ** .pp
   ** When \fIset\fP, Mutt-ng will qualify all local addresses (ones without the
   ** @host portion) with the value of ``$$hostname''.  If \fIunset\fP, no
   ** addresses will be qualified.
   */
  {"use_from", DT_BOOL, R_NONE, OPTUSEFROM, "yes" },
  /*
   ** .pp
   ** When \fIset\fP, Mutt-ng will generate the ``\fTFrom:\fP'' header field when
   ** sending messages. If \fIunset\fP, no ``\fTFrom:\fP'' header field will be
   ** generated unless the user explicitly sets one using the ``$my_hdr''
   ** command.
   */
#ifdef HAVE_LIBIDN
  {"use_idn", DT_BOOL, R_BOTH, OPTUSEIDN, "yes" },
  /*
   ** .pp
   ** Availability: IDN
   **
   ** .pp
   ** When \fIset\fP, Mutt-ng will show you international domain names decoded.
   ** .pp
   ** \fBNote:\fP You can use IDNs for addresses even if this is \fIunset\fP.
   ** This variable only affects decoding.
   */
#endif /* HAVE_LIBIDN */
#ifdef HAVE_GETADDRINFO
  {"use_ipv6", DT_BOOL, R_NONE, OPTUSEIPV6, "yes" },
  /*
   ** .pp
   ** When \fIset\fP, Mutt-ng will look for IPv6 addresses of hosts it tries to
   ** contact.  If this option is \fIunset\fP, Mutt-ng will restrict itself to IPv4 addresses.
   ** Normally, the default should work.
   */
#endif /* HAVE_GETADDRINFO */
  {"user_agent", DT_SYN, R_NONE, UL "agent_string", 0 },
  {"agent_string", DT_BOOL, R_NONE, OPTXMAILER, "yes" },
  /*
   ** .pp
   ** When \fIset\fP, Mutt-ng will add a ``\fTUser-Agent:\fP'' header to outgoing
   ** messages, indicating which version of Mutt-ng was used for composing
   ** them.
   */
  {"visual", DT_PATH, R_NONE, UL &Visual, "" },
  /*
   ** .pp
   ** Specifies the visual editor to invoke when the \fI~v\fP command is
   ** given in the builtin editor.
   */
  {"wait_key", DT_BOOL, R_NONE, OPTWAITKEY, "yes" },
  /*
   ** .pp
   ** Controls whether Mutt-ng will ask you to press a key after \fIshell-
   ** escape\fP, \fIpipe-message\fP, \fIpipe-entry\fP, \fIprint-message\fP,
   ** and \fIprint-entry\fP commands.
   ** .pp
   ** It is also used when viewing attachments with ``$auto_view'', provided
   ** that the corresponding mailcap entry has a \fTneedsterminal\fP flag,
   ** and the external program is interactive.
   ** .pp
   ** When \fIset\fP, Mutt-ng will always ask for a key. When \fIunset\fP, Mutt-ng will wait
   ** for a key only if the external command returned a non-zero status.
   */
  {"weed", DT_BOOL, R_NONE, OPTWEED, "yes" },
  /*
   ** .pp
   ** When \fIset\fP, Mutt-ng will weed headers when displaying, forwarding,
   ** printing, or replying to messages.
   */
  {"wrap_search", DT_BOOL, R_NONE, OPTWRAPSEARCH, "yes" },
  /*
   ** .pp
   ** Controls whether searches wrap around the end of the mailbox.
   ** .pp
   ** When \fIset\fP, searches will wrap around the first (or last) message. When
   ** \fIunset\fP, searches will not wrap.
   */
  {"wrapmargin", DT_NUM, R_PAGER, UL &WrapMargin, "0" },
  /*
   ** .pp
   ** Controls the size of the margin remaining at the right side of
   ** the terminal when Mutt-ng's pager does smart wrapping.
   */
  {"write_inc", DT_NUM, R_NONE, UL &WriteInc, "10" },
  /*
   ** .pp
   ** When writing a mailbox, a message will be printed every
   ** \fIwrite_inc\fP messages to indicate progress.  If set to 0, only a
   ** single message will be displayed before writing a mailbox.
   ** .pp
   ** Also see the ``$$read_inc'' variable.
   */
  {"write_bcc", DT_BOOL, R_NONE, OPTWRITEBCC, "yes" },
  /*
   ** .pp
   ** Controls whether Mutt-ng writes out the Bcc header when preparing
   ** messages to be sent.  Exim users may wish to \fIunset\fP this.
   */
  {"xterm_icon", DT_STR, R_BOTH, UL &XtermIcon, "M%?n?AIL&ail?"},
  /*
   ** .pp
   ** Controls the format of the X11 icon title, as long as $$xterm_set_titles
   ** is \fIset\fP. This string is identical in formatting to the one used by
   ** ``$$status_format''.
   */
  {"xterm_set_titles", DT_BOOL, R_BOTH, OPTXTERMSETTITLES, "no" },
  /*
   ** .pp
   ** Controls whether Mutt-ng sets the xterm title bar and icon name
   ** (as long as you're in an appropriate terminal). The default must
   ** be \fIunset\fP to force in the validity checking.
   */
  {"xterm_leave", DT_STR, R_BOTH, UL &XtermLeave, "" },
  /*
   ** .pp
   ** If $$xterm_set_titles is \fIset\fP, this string will be used to
   ** set the title when leaving Mutt-ng. For terminal-based programs,
   ** there's no easy and portable way to read the current title so Mutt-ng
   ** cannot read it upon startup and restore it when exiting.
   **
   ** .pp
   ** Based on the xterm FAQ, the following might work:
   **
   ** .pp
   ** \fTset xterm_leave = "`test x$$$DISPLAY != x && xprop -id $$$WINDOWID | grep WM_NAME | cut -d '"' -f 2`"\fP
   */
  {"xterm_title", DT_STR, R_BOTH, UL &XtermTitle, "Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?"},
  /*
   ** .pp
   ** Controls the format of the title bar of the xterm provided that
   ** $$xterm_set_titles has been \fIset\fP. This string is identical in formatting
   ** to the one used by ``$$status_format''.
   */
#ifdef USE_NNTP
  {"nntp_x_comment_to", DT_BOOL, R_NONE, OPTXCOMMENTTO, "no" },
  /*
   ** .pp
   ** Availability: NNTP
   **
   ** .pp
   ** If \fIset\fP, Mutt-ng will add a ``\fTX-Comment-To:\fP'' header field
   ** (that contains full name of the original article author) to articles that 
   ** you followup to.
   */
#endif
  /*--*/
  { NULL, -1, R_NONE, -1, NULL }
};

static const char* Features[] = {
#ifdef NCURSES_VERSION
  "ncurses",
#endif
#ifdef USE_SLANG_CURSES
  "slang",
#endif
#ifdef _LIBICONV_VERSION
  "iconv",
#endif
#ifdef HAVE_LIBIDN
  "idn",
#endif
#ifdef USE_DOTLOCK
  "dotlock",
#endif
#ifdef USE_POP
  "pop",
#endif
#ifdef USE_NNTP
  "nntp",
#endif
#ifdef USE_IMAP
  "imap",
#endif
#ifdef USE_SSL
  "ssl",
#endif
#ifdef USE_GNUTLS
  "gnutls",
#endif
#ifdef USE_SASL
  "sasl",
#endif
#ifdef USE_LIBESMTP
  "libesmtp",
#endif
#ifdef USE_COMPRESSED
  "compessed",
#endif
#ifdef HAVE_COLOR
  "color",
#endif
#ifdef CRYPT_BACKEND_GPGME
  "gpgme",
#endif
#ifdef USE_HCACHE
  "header_cache",
#endif
#ifdef HAVE_QDBM
  "qdbm",
#endif
#ifdef HAVE_GDBM
  "gdbm",
#endif
#ifdef HAVE_DB4
  "db4",
#endif
  /* last */
  NULL
};

const struct mapping_t SortMethods[] = {
  {"date", SORT_DATE},
  {"date-sent", SORT_DATE},
  {"date-received", SORT_RECEIVED},
  {"mailbox-order", SORT_ORDER},
  {"subject", SORT_SUBJECT},
  {"from", SORT_FROM},
  {"size", SORT_SIZE},
  {"threads", SORT_THREADS},
  {"to", SORT_TO},
  {"score", SORT_SCORE},
  {"spam", SORT_SPAM},
  {NULL, 0}
};

/* same as SortMethods, but with "threads" replaced by "date" */

const struct mapping_t SortAuxMethods[] = {
  {"date", SORT_DATE},
  {"date-sent", SORT_DATE},
  {"date-received", SORT_RECEIVED},
  {"mailbox-order", SORT_ORDER},
  {"subject", SORT_SUBJECT},
  {"from", SORT_FROM},
  {"size", SORT_SIZE},
  {"threads", SORT_DATE},       /* note: sort_aux == threads
                                 * isn't possible. 
                                 */
  {"to", SORT_TO},
  {"score", SORT_SCORE},
  {"spam", SORT_SPAM},
  {NULL, 0}
};


const struct mapping_t SortBrowserMethods[] = {
  {"alpha", SORT_SUBJECT},
  {"date", SORT_DATE},
  {"size", SORT_SIZE},
  {"unsorted", SORT_ORDER},
  {NULL, 0}
};

const struct mapping_t SortAliasMethods[] = {
  {"alias", SORT_ALIAS},
  {"address", SORT_ADDRESS},
  {"unsorted", SORT_ORDER},
  {NULL, 0}
};

const struct mapping_t SortKeyMethods[] = {
  {"address", SORT_ADDRESS},
  {"date", SORT_DATE},
  {"keyid", SORT_KEYID},
  {"trust", SORT_TRUST},
  {NULL, 0}
};


/* functions used to parse commands in a rc file */

static int parse_list (BUFFER *, BUFFER *, unsigned long, BUFFER *);
static int parse_spam_list (BUFFER *, BUFFER *, unsigned long, BUFFER *);
static int parse_unlist (BUFFER *, BUFFER *, unsigned long, BUFFER *);
static int parse_attachments (BUFFER *, BUFFER *, unsigned long, BUFFER *);
static int parse_unattachments (BUFFER *, BUFFER *, unsigned long, BUFFER *);
static int parse_lists (BUFFER *, BUFFER *, unsigned long, BUFFER *);
static int parse_unlists (BUFFER *, BUFFER *, unsigned long, BUFFER *);
static int parse_alias (BUFFER *, BUFFER *, unsigned long, BUFFER *);
static int parse_unalias (BUFFER *, BUFFER *, unsigned long, BUFFER *);
static int parse_ifdef (BUFFER *, BUFFER *, unsigned long, BUFFER *);
static int parse_ignore (BUFFER *, BUFFER *, unsigned long, BUFFER *);
static int parse_unignore (BUFFER *, BUFFER *, unsigned long, BUFFER *);
static int parse_source (BUFFER *, BUFFER *, unsigned long, BUFFER *);
static int parse_set (BUFFER *, BUFFER *, unsigned long, BUFFER *);
static int parse_my_hdr (BUFFER *, BUFFER *, unsigned long, BUFFER *);
static int parse_unmy_hdr (BUFFER *, BUFFER *, unsigned long, BUFFER *);
static int parse_subscribe (BUFFER *, BUFFER *, unsigned long, BUFFER *);
static int parse_unsubscribe (BUFFER *, BUFFER *, unsigned long, BUFFER *);

static int parse_alternates (BUFFER *, BUFFER *, unsigned long, BUFFER *);
static int parse_unalternates (BUFFER *, BUFFER *, unsigned long, BUFFER *);

struct command_t {
  const char *name;
  int (*func) (BUFFER *, BUFFER *, unsigned long, BUFFER *);
  unsigned long data;
};

struct command_t Commands[] = {
  {"alternates", parse_alternates, 0},
  {"attachments", parse_attachments, 0 },
  {"unattachments",parse_unattachments,0 },
  {"unalternates", parse_unalternates, 0},
#ifdef USE_SOCKET
  {"account-hook", mutt_parse_hook, M_ACCOUNTHOOK},
#endif
  {"alias", parse_alias, 0},
  {"auto_view", parse_list, UL &AutoViewList},
  {"alternative_order", parse_list, UL &AlternativeOrderList},
  {"bind", mutt_parse_bind, 0},
  {"charset-hook", mutt_parse_hook, M_CHARSETHOOK},
#ifdef HAVE_COLOR
  {"color", mutt_parse_color, 0},
  {"uncolor", mutt_parse_uncolor, 0},
#endif
  {"exec", mutt_parse_exec, 0},
  {"fcc-hook", mutt_parse_hook, M_FCCHOOK},
  {"fcc-save-hook", mutt_parse_hook, M_FCCHOOK|M_SAVEHOOK},
  {"folder-hook", mutt_parse_hook, M_FOLDERHOOK},
#ifdef USE_COMPRESSED
  {"open-hook", mutt_parse_hook, M_OPENHOOK},
  {"close-hook", mutt_parse_hook, M_CLOSEHOOK},
  {"append-hook", mutt_parse_hook, M_APPENDHOOK},
#endif
  {"hdr_order", parse_list, UL &HeaderOrderList},
  {"ifdef", parse_ifdef, 1},
  {"ifndef", parse_ifdef, 0},
#ifdef HAVE_ICONV
  {"iconv-hook", mutt_parse_hook, M_ICONVHOOK},
#endif
  {"ignore", parse_ignore, 0},
  {"lists", parse_lists, 0},
  {"macro", mutt_parse_macro, 0},
  {"mailboxes", buffy_parse_mailboxes, M_MAILBOXES},
  {"unmailboxes", buffy_parse_mailboxes, M_UNMAILBOXES},
  {"message-hook", mutt_parse_hook, M_MESSAGEHOOK},
  {"mbox-hook", mutt_parse_hook, M_MBOXHOOK},
  {"mime_lookup", parse_list, UL &MimeLookupList},
  {"unmime_lookup", parse_unlist, UL &MimeLookupList},
  {"mono", mutt_parse_mono, 0},
  {"my_hdr", parse_my_hdr, 0},
  {"pgp-hook", mutt_parse_hook, M_CRYPTHOOK},
  {"crypt-hook", mutt_parse_hook, M_CRYPTHOOK},
  {"push", mutt_parse_push, 0},
  {"reply-hook", mutt_parse_hook, M_REPLYHOOK},
  {"reset", parse_set, M_SET_RESET},
  {"save-hook", mutt_parse_hook, M_SAVEHOOK},
  {"score", mutt_parse_score, 0},
  {"send-hook", mutt_parse_hook, M_SENDHOOK},
  {"send2-hook", mutt_parse_hook, M_SEND2HOOK},
  {"set", parse_set, 0},
  {"source", parse_source, 0},
  {"spam", parse_spam_list, M_SPAM},
  {"nospam", parse_spam_list, M_NOSPAM},
  {"subscribe", parse_subscribe, 0},
  {"toggle", parse_set, M_SET_INV},
  {"unalias", parse_unalias, 0},
  {"unalternative_order", parse_unlist, UL &AlternativeOrderList},
  {"unauto_view", parse_unlist, UL &AutoViewList},
  {"unhdr_order", parse_unlist, UL &HeaderOrderList},
  {"unhook", mutt_parse_unhook, 0},
  {"unignore", parse_unignore, 0},
  {"unlists", parse_unlists, 0},
  {"unmono", mutt_parse_unmono, 0},
  {"unmy_hdr", parse_unmy_hdr, 0},
  {"unscore", mutt_parse_unscore, 0},
  {"unset", parse_set, M_SET_UNSET},
  {"unsubscribe", parse_unsubscribe, 0},
  {NULL, NULL, 0}
};