2 * Copyright notice from original mutt:
3 * Copyright (C) 1996-2002 Michael R. Elkins <me@mutt.org>
4 * Copyright (C) 2004 g10 Code GmbH
6 * Parts were writte/modified by:
7 * Nico Golde <nico@ngolde.de>
9 * This file is part of mutt-ng, see http://www.muttng.org/.
10 * It's licensed under the GNU General Public License,
11 * please see the file GPL in the top level source directory.
24 #define DT_BOOL 1 /* boolean option */
25 #define DT_NUM 2 /* a number */
26 #define DT_STR 3 /* a string */
27 #define DT_PATH 4 /* a pathname */
28 #define DT_QUAD 5 /* quad-option (yes/no/ask-yes/ask-no) */
29 #define DT_SORT 6 /* sorting methods */
30 #define DT_RX 7 /* regular expressions */
31 #define DT_MAGIC 8 /* mailbox type */
32 #define DT_SYN 9 /* synonym for another variable */
33 #define DT_ADDR 10 /* e-mail address */
34 #define DT_USER 11 /* user defined viar $user_ */
36 #define DTYPE(x) ((x) & DT_MASK)
39 #define DT_SUBTYPE_MASK 0xf0
40 #define DT_SORT_ALIAS 0x10
41 #define DT_SORT_BROWSER 0x20
42 #define DT_SORT_KEYS 0x40
43 #define DT_SORT_AUX 0x80
45 /* flags to parse_set() */
46 #define M_SET_INV (1<<0) /* default is to invert all vars */
47 #define M_SET_UNSET (1<<1) /* default is to unset all vars */
48 #define M_SET_RESET (1<<2) /* default is to reset all vars to default */
50 /* forced redraw/resort types */
52 #define R_INDEX (1<<0)
53 #define R_PAGER (1<<1)
54 #define R_RESORT (1<<2) /* resort the mailbox */
55 #define R_RESORT_SUB (1<<3) /* resort subthreads */
56 #define R_RESORT_INIT (1<<4) /* resort from scratch */
57 #define R_TREE (1<<5) /* redraw the thread tree */
58 #define R_BOTH (R_INDEX|R_PAGER)
59 #define R_RESORT_BOTH (R_RESORT|R_RESORT_SUB)
74 #define UL (unsigned long)
79 #define ISPELL "ispell"
82 /* build complete documentation */
89 # define MIXMASTER "mixmaster"
100 # ifndef USE_LIBESMTP
101 # define USE_LIBESMTP
112 # ifndef DL_STANDALONE
113 # define DL_STANDALONE
121 # ifndef HAVE_GETADDRINFO
122 # define HAVE_GETADDRINFO
126 struct option_t MuttVars[] = {
128 {"abort_noattach", DT_QUAD, R_NONE, OPT_ATTACH, "no" },
131 ** This variable specifies whether to abort sending if no attachment
132 ** was made but the content references them, i.e. the content
133 ** matches the regular expression given in
134 ** $$attach_remind_regexp. If a match was found and this
135 ** variable is set to \fIyes\fP, message sending will be aborted
136 ** but the mail will be send nevertheless if set to \fIno\fP.
139 ** This variable and $$attach_remind_regexp are intended to
140 ** remind the user to attach files if the message's text
144 ** See also the $$attach_remind_regexp variable.
146 {"abort_nosubject", DT_QUAD, R_NONE, OPT_SUBJECT, "ask-yes" },
149 ** If set to \fIyes\fP, when composing messages and no subject is given
150 ** at the subject prompt, composition will be aborted. If set to
151 ** \fIno\fP, composing messages with no subject given at the subject
152 ** prompt will never be aborted.
154 {"abort_unmodified", DT_QUAD, R_NONE, OPT_ABORT, "yes" },
157 ** If set to \fIyes\fP, composition will automatically abort after
158 ** editing the message body if no changes are made to the file (this
159 ** check only happens after the \fIfirst\fP edit of the file). When set
160 ** to \fIno\fP, composition will never be aborted.
162 {"alias_file", DT_PATH, R_NONE, UL &AliasFile, "~/.muttngrc"},
165 ** The default file in which to save aliases created by the
166 ** ``$create-alias'' function.
168 ** \fBNote:\fP Mutt-ng will not automatically source this file; you must
169 ** explicitly use the ``$source'' command for it to be executed.
171 {"alias_format", DT_STR, R_NONE, UL &AliasFmt, "%4n %2f %t %-10a %r"},
174 ** Specifies the format of the data displayed for the ``alias'' menu. The
175 ** following \fTprintf(3)\fP-style sequences are available:
178 ** .dt %a .dd alias name
179 ** .dt %f .dd flags - currently, a "d" for an alias marked for deletion
180 ** .dt %n .dd index number
181 ** .dt %r .dd address which alias expands to
182 ** .dt %t .dd character which indicates if the alias is tagged for inclusion
185 {"allow_8bit", DT_BOOL, R_NONE, OPTALLOW8BIT, "yes" },
188 ** Controls whether 8-bit data is converted to 7-bit using either
189 ** \fTquoted-printable\fP or \fTbase64\fP encoding when sending mail.
191 {"allow_ansi", DT_BOOL, R_NONE, OPTALLOWANSI, "no" },
194 ** Controls whether ANSI color codes in messages (and color tags in
195 ** rich text messages) are to be interpreted.
196 ** Messages containing these codes are rare, but if this option is set,
197 ** their text will be colored accordingly. Note that this may override
198 ** your color choices, and even present a security problem, since a
199 ** message could include a line like ``\fT[-- PGP output follows ...\fP" and
200 ** give it the same color as your attachment color.
202 {"arrow_cursor", DT_BOOL, R_BOTH, OPTARROWCURSOR, "no" },
205 ** When \fIset\fP, an arrow (``\fT->\fP'') will be used to indicate the current entry
206 ** in menus instead of highlighting the whole line. On slow network or modem
207 ** links this will make response faster because there is less that has to
208 ** be redrawn on the screen when moving to the next or previous entries
211 {"ascii_chars", DT_BOOL, R_BOTH, OPTASCIICHARS, "no" },
214 ** If \fIset\fP, Mutt-ng will use plain ASCII characters when displaying thread
215 ** and attachment trees, instead of the default \fTACS\fP characters.
217 {"askbcc", DT_BOOL, R_NONE, OPTASKBCC, "no" },
220 ** If \fIset\fP, Mutt-ng will prompt you for blind-carbon-copy (Bcc) recipients
221 ** before editing an outgoing message.
223 {"askcc", DT_BOOL, R_NONE, OPTASKCC, "no" },
226 ** If \fIset\fP, Mutt-ng will prompt you for carbon-copy (Cc) recipients before
227 ** editing the body of an outgoing message.
229 {"assumed_charset", DT_STR, R_NONE, UL &AssumedCharset, "us-ascii"},
232 ** This variable is a colon-separated list of character encoding
233 ** schemes for messages without character encoding indication.
234 ** Header field values and message body content without character encoding
235 ** indication would be assumed that they are written in one of this list.
236 ** By default, all the header fields and message body without any charset
237 ** indication are assumed to be in \fTus-ascii\fP.
239 ** For example, Japanese users might prefer this:
241 ** \fTset assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"\fP
243 ** However, only the first content is valid for the message body.
244 ** This variable is valid only if $$strict_mime is unset.
247 {"ask_followup_to", DT_SYN, R_NONE, UL "nntp_ask_followup_to", 0},
248 {"nntp_ask_followup_to", DT_BOOL, R_NONE, OPTASKFOLLOWUP, "no" },
251 ** Availability: NNTP
254 ** If \fIset\fP, Mutt-ng will prompt you for the \fTFollowup-To:\fP header
255 ** field before editing the body of an outgoing news article.
257 {"ask_x_comment_to", DT_SYN, R_NONE, UL "nntp_ask_x_comment_to", 0},
258 {"nntp_ask_x_comment_to", DT_BOOL, R_NONE, OPTASKXCOMMENTTO, "no" },
261 ** Availability: NNTP
264 ** If \fIset\fP, Mutt-ng will prompt you for the \fTX-Comment-To:\fP header
265 ** field before editing the body of an outgoing news article.
268 {"attach_format", DT_STR, R_NONE, UL &AttachFormat, "%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] "},
271 ** This variable describes the format of the ``attachment'' menu. The
272 ** following \fTprintf(3)\fP-style sequences are understood:
275 ** .dt %C .dd charset
276 ** .dt %c .dd requires charset conversion (n or c)
277 ** .dt %D .dd deleted flag
278 ** .dt %d .dd description
279 ** .dt %e .dd MIME \fTContent-Transfer-Encoding:\fP header field
280 ** .dt %f .dd filename
281 ** .dt %I .dd MIME \fTContent-Disposition:\fP header field (\fTI\fP=inline, \fTA\fP=attachment)
282 ** .dt %m .dd major MIME type
283 ** .dt %M .dd MIME subtype
284 ** .dt %n .dd attachment number
286 ** .dt %t .dd tagged flag
287 ** .dt %T .dd graphic tree characters
288 ** .dt %u .dd unlink (=to delete) flag
289 ** .dt %>X .dd right justify the rest of the string and pad with character "X"
290 ** .dt %|X .dd pad to the end of the line with character "X"
293 {"attach_remind_regexp", DT_RX, R_NONE, UL &AttachRemindRegexp, "attach"},
296 ** If this variable is non-empty, muttng will scan a message's contents
297 ** before sending for this regular expression. If it is found, it will
298 ** ask for what to do depending on the setting of $$abort_noattach.
300 ** This variable and $$abort_noattach are intended to remind the user
301 ** to attach files if the message's text references them.
303 {"attach_sep", DT_STR, R_NONE, UL &AttachSep, "\n"},
306 ** The separator to add between attachments when operating (saving,
307 ** printing, piping, etc) on a list of tagged attachments.
309 {"attach_split", DT_BOOL, R_NONE, OPTATTACHSPLIT, "yes" },
312 ** If this variable is \fIunset\fP, when operating (saving, printing, piping,
313 ** etc) on a list of tagged attachments, Mutt-ng will concatenate the
314 ** attachments and will operate on them as a single attachment. The
315 ** ``$$attach_sep'' separator is added after each attachment. When \fIset\fP,
316 ** Mutt-ng will operate on the attachments one by one.
318 {"attribution", DT_STR, R_NONE, UL &Attribution, "On %d, %n wrote:"},
321 ** This is the string that will precede a message which has been included
322 ** in a reply. For a full listing of defined \fTprintf(3)\fP-like sequences see
323 ** the section on ``$$index_format''.
325 {"autoedit", DT_BOOL, R_NONE, OPTAUTOEDIT, "no" },
328 ** When \fIset\fP along with ``$$edit_headers'', Mutt-ng will skip the initial
329 ** send-menu and allow you to immediately begin editing the body of your
330 ** message. The send-menu may still be accessed once you have finished
331 ** editing the body of your message.
333 ** Also see ``$$fast_reply''.
335 {"auto_tag", DT_BOOL, R_NONE, OPTAUTOTAG, "no" },
338 ** When \fIset\fP, functions in the \fIindex\fP menu which affect a message
339 ** will be applied to all tagged messages (if there are any). When
340 ** unset, you must first use the ``tag-prefix'' function (default: "\fT;\fP") to
341 ** make the next function apply to all tagged messages.
343 {"beep", DT_BOOL, R_NONE, OPTBEEP, "yes" },
346 ** When this variable is \fIset\fP, Mutt-ng will beep when an error occurs.
348 {"beep_new", DT_BOOL, R_NONE, OPTBEEPNEW, "no" },
351 ** When this variable is \fIset\fP, Mutt-ng will beep whenever it prints a message
352 ** notifying you of new mail. This is independent of the setting of the
353 ** ``$$beep'' variable.
355 {"bounce", DT_QUAD, R_NONE, OPT_BOUNCE, "ask-yes" },
358 ** Controls whether you will be asked to confirm bouncing messages.
359 ** If set to \fIyes\fP you don't get asked if you want to bounce a
360 ** message. Setting this variable to \fIno\fP is not generally useful,
361 ** and thus not recommended, because you are unable to bounce messages.
363 {"bounce_delivered", DT_BOOL, R_NONE, OPTBOUNCEDELIVERED, "yes" },
366 ** When this variable is \fIset\fP, Mutt-ng will include
367 ** \fTDelivered-To:\fP header fields when bouncing messages.
368 ** Postfix users may wish to \fIunset\fP this variable.
370 { "braille_friendly", DT_BOOL, R_NONE, OPTBRAILLEFRIENDLY, "no" },
373 ** When this variable is set, mutt will place the cursor at the beginning
374 ** of the current line in menus, even when the arrow_cursor variable
375 ** is unset, making it easier for blind persons using Braille displays to
376 ** follow these menus. The option is disabled by default because many
377 ** visual terminals don't permit making the cursor invisible.
380 {"catchup_newsgroup", DT_SYN, R_NONE, UL "nntp_catchup", 0},
381 {"nntp_catchup", DT_QUAD, R_NONE, OPT_CATCHUP, "ask-yes" },
384 ** Availability: NNTP
387 ** If this variable is \fIset\fP, Mutt-ng will mark all articles in a newsgroup
388 ** as read when you leaving it.
391 {"charset", DT_STR, R_NONE, UL &Charset, "" },
394 ** Character set your terminal uses to display and enter textual data.
396 {"check_new", DT_BOOL, R_NONE, OPTCHECKNEW, "yes" },
399 ** \fBNote:\fP this option only affects \fImaildir\fP and \fIMH\fP style
402 ** When \fIset\fP, Mutt-ng will check for new mail delivered while the
403 ** mailbox is open. Especially with MH mailboxes, this operation can
404 ** take quite some time since it involves scanning the directory and
405 ** checking each file to see if it has already been looked at. If it's
406 ** \fIunset\fP, no check for new mail is performed while the mailbox is open.
408 {"collapse_unread", DT_BOOL, R_NONE, OPTCOLLAPSEUNREAD, "yes" },
411 ** When \fIunset\fP, Mutt-ng will not collapse a thread if it contains any
414 {"uncollapse_jump", DT_BOOL, R_NONE, OPTUNCOLLAPSEJUMP, "no" },
417 ** When \fIset\fP, Mutt-ng will jump to the next unread message, if any,
418 ** when the current thread is \fIun\fPcollapsed.
420 {"compose_format", DT_STR, R_BOTH, UL &ComposeFormat, "-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-"},
423 ** Controls the format of the status line displayed in the ``compose''
424 ** menu. This string is similar to ``$$status_format'', but has its own
425 ** set of \fTprintf(3)\fP-like sequences:
428 ** .dt %a .dd total number of attachments
429 ** .dt %h .dd local hostname
430 ** .dt %l .dd approximate size (in bytes) of the current message
431 ** .dt %v .dd Mutt-ng version string
434 ** See the text describing the ``$$status_format'' option for more
435 ** information on how to set ``$$compose_format''.
437 {"config_charset", DT_STR, R_NONE, UL &ConfigCharset, "" },
440 ** When defined, Mutt-ng will recode commands in rc files from this
443 {"confirmappend", DT_BOOL, R_NONE, OPTCONFIRMAPPEND, "yes" },
446 ** When \fIset\fP, Mutt-ng will prompt for confirmation when appending messages to
447 ** an existing mailbox.
449 {"confirmcreate", DT_BOOL, R_NONE, OPTCONFIRMCREATE, "yes" },
452 ** When \fIset\fP, Mutt-ng will prompt for confirmation when saving messages to a
453 ** mailbox which does not yet exist before creating it.
455 {"connect_timeout", DT_NUM, R_NONE, UL &ConnectTimeout, "30" },
458 ** Causes Mutt-ng to timeout a network connection (for IMAP or POP) after this
459 ** many seconds if the connection is not able to be established. A negative
460 ** value causes Mutt-ng to wait indefinitely for the connection to succeed.
462 {"content_type", DT_STR, R_NONE, UL &ContentType, "text/plain"},
465 ** Sets the default \fTContent-Type:\fP header field for the body
466 ** of newly composed messages.
468 {"copy", DT_QUAD, R_NONE, OPT_COPY, "yes" },
471 ** This variable controls whether or not copies of your outgoing messages
472 ** will be saved for later references. Also see ``$$record'',
473 ** ``$$save_name'', ``$$force_name'' and ``$fcc-hook''.
476 {"crypt_use_gpgme", DT_BOOL, R_NONE, OPTCRYPTUSEGPGME, "no" },
479 ** This variable controls the use the GPGME enabled crypto backends.
480 ** If it is \fIset\fP and Mutt-ng was build with gpgme support, the gpgme code for
481 ** S/MIME and PGP will be used instead of the classic code.
483 ** \fBNote\fP: You need to use this option in your \fT.muttngrc\fP configuration
484 ** file as it won't have any effect when used interactively.
487 {"crypt_autopgp", DT_BOOL, R_NONE, OPTCRYPTAUTOPGP, "yes" },
490 ** This variable controls whether or not Mutt-ng may automatically enable
491 ** PGP encryption/signing for messages. See also ``$$crypt_autoencrypt'',
492 ** ``$$crypt_replyencrypt'',
493 ** ``$$crypt_autosign'', ``$$crypt_replysign'' and ``$$smime_is_default''.
495 {"crypt_autosmime", DT_BOOL, R_NONE, OPTCRYPTAUTOSMIME, "yes" },
498 ** This variable controls whether or not Mutt-ng may automatically enable
499 ** S/MIME encryption/signing for messages. See also ``$$crypt_autoencrypt'',
500 ** ``$$crypt_replyencrypt'',
501 ** ``$$crypt_autosign'', ``$$crypt_replysign'' and ``$$smime_is_default''.
503 {"date_format", DT_STR, R_BOTH, UL &DateFmt, "!%a, %b %d, %Y at %I:%M:%S%p %Z"},
506 ** This variable controls the format of the date printed by the ``\fT%d\fP''
507 ** sequence in ``$$index_format''. This is passed to \fTstrftime(3)\fP
508 ** to process the date.
510 ** Unless the first character in the string is a bang (``\fT!\fP''), the month
511 ** and week day names are expanded according to the locale specified in
512 ** the variable ``$$locale''. If the first character in the string is a
513 ** bang, the bang is discarded, and the month and week day names in the
514 ** rest of the string are expanded in the \fIC\fP locale (that is in US
517 {"default_hook", DT_STR, R_NONE, UL &DefaultHook, "~f %s !~P | (~P ~C %s)"},
520 ** This variable controls how send-hooks, message-hooks, save-hooks,
521 ** and fcc-hooks will
522 ** be interpreted if they are specified with only a simple regexp,
523 ** instead of a matching pattern. The hooks are expanded when they are
524 ** declared, so a hook will be interpreted according to the value of this
525 ** variable at the time the hook is declared. The default value matches
526 ** if the message is either from a user matching the regular expression
527 ** given, or if it is from you (if the from address matches
528 ** ``alternates'') and is to or cc'ed to a user matching the given
529 ** regular expression.
531 {"delete", DT_QUAD, R_NONE, OPT_DELETE, "ask-yes" },
534 ** Controls whether or not messages are really deleted when closing or
535 ** synchronizing a mailbox. If set to \fIyes\fP, messages marked for
536 ** deleting will automatically be purged without prompting. If set to
537 ** \fIno\fP, messages marked for deletion will be kept in the mailbox.
539 {"delete_space", DT_BOOL, R_NONE, OPTDELSP, "no" },
542 ** When sending messages with \fTformat=flowed\fP by \fIsetting\fP the
543 ** $$text_flowed variable, this variable specifies whether to also
544 ** set the \fTDelSp\fP parameter to \fTyes\fP. If this is \fIunset\fP,
545 ** no additional parameter will be send as a value of \fTno\fP already
546 ** is the default behavior.
549 ** \fBNote:\fP this variable only has an effect on \fIoutgoing\fP messages
550 ** (if $$text_flowed is \fIset\fP) but not on incomming.
552 {"delete_untag", DT_BOOL, R_NONE, OPTDELETEUNTAG, "yes" },
555 ** If this option is \fIset\fP, Mutt-ng will untag messages when marking them
556 ** for deletion. This applies when you either explicitly delete a message,
557 ** or when you save it to another folder.
559 {"digest_collapse", DT_BOOL, R_NONE, OPTDIGESTCOLLAPSE, "yes" },
562 ** If this option is \fIset\fP, Mutt-ng's received-attachments menu will not show the subparts of
563 ** individual messages in a multipart/digest. To see these subparts, press 'v' on that menu.
565 {"display_filter", DT_PATH, R_PAGER, UL &DisplayFilter, ""},
568 ** When \fIset\fP, specifies a command used to filter messages. When a message
569 ** is viewed it is passed as standard input to $$display_filter, and the
570 ** filtered message is read from the standard output.
572 #if defined(DL_STANDALONE) && defined(USE_DOTLOCK)
573 {"dotlock_program", DT_PATH, R_NONE, UL &MuttDotlock, BINDIR "/muttng_dotlock"},
576 ** Availability: Standalone and Dotlock
579 ** Contains the path of the \fTmuttng_dotlock(1)\fP binary to be used by
583 {"dsn_notify", DT_STR, R_NONE, UL &DsnNotify, ""},
586 ** \fBNote:\fP you should not enable this unless you are using Sendmail
587 ** 8.8.x or greater or in connection with the SMTP support via libESMTP.
589 ** This variable sets the request for when notification is returned. The
590 ** string consists of a comma separated list (no spaces!) of one or more
591 ** of the following: \fInever\fP, to never request notification,
592 ** \fIfailure\fP, to request notification on transmission failure,
593 ** \fIdelay\fP, to be notified of message delays, \fIsuccess\fP, to be
594 ** notified of successful transmission.
596 ** Example: \fTset dsn_notify="failure,delay"\fP
598 {"dsn_return", DT_STR, R_NONE, UL &DsnReturn, ""},
601 ** \fBNote:\fP you should not enable this unless you are using Sendmail
602 ** 8.8.x or greater or in connection with the SMTP support via libESMTP.
604 ** This variable controls how much of your message is returned in DSN
605 ** messages. It may be set to either \fIhdrs\fP to return just the
606 ** message header, or \fIfull\fP to return the full message.
608 ** Example: \fTset dsn_return=hdrs\fP
610 {"duplicate_threads", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTDUPTHREADS, "yes" },
613 ** This variable controls whether Mutt-ng, when sorting by threads, threads
614 ** messages with the same \fTMessage-Id:\fP header field together.
615 ** If it is \fIset\fP, it will indicate that it thinks they are duplicates
616 ** of each other with an equals sign in the thread diagram.
618 {"edit_headers", DT_BOOL, R_NONE, OPTEDITHDRS, "no" },
621 ** This option allows you to edit the header of your outgoing messages
622 ** along with the body of your message.
624 {"editor", DT_PATH, R_NONE, UL &Editor, "" },
627 ** This variable specifies which editor is used by Mutt-ng.
628 ** It defaults to the value of the \fT$$$VISUAL\fP, or \fT$$$EDITOR\fP, environment
629 ** variable, or to the string "\fTvi\fP" if neither of those are set.
631 {"encode_from", DT_BOOL, R_NONE, OPTENCODEFROM, "no" },
634 ** When \fIset\fP, Mutt-ng will \fTquoted-printable\fP encode messages when
635 ** they contain the string ``\fTFrom \fP'' (note the trailing space)
636 ** in the beginning of a line. Useful to avoid the tampering certain mail
637 ** delivery and transport agents tend to do with messages.
640 ** \fBNote:\fP as mutt-ng currently violates RfC3676 defining
641 ** \fTformat=flowed\fP, it's <em/strongly/ advised to \fIset\fP
642 ** this option although discouraged by the standard. Alternatively,
643 ** you must take care of space-stuffing <tt/From / lines (with a trailing
646 {"envelope_from", DT_BOOL, R_NONE, OPTENVFROM, "no" },
649 ** When \fIset\fP, Mutt-ng will try to derive the message's \fIenvelope\fP
650 ** sender from the ``\fTFrom:\fP'' header field. Note that this information is passed
651 ** to the sendmail command using the ``\fT-f\fP" command line switch, so don't set this
652 ** option if you are using that switch in $$sendmail yourself,
653 ** or if the sendmail on your machine doesn't support that command
656 {"escape", DT_STR, R_NONE, UL &EscChar, "~"},
659 ** Escape character to use for functions in the builtin editor.
661 {"fast_reply", DT_BOOL, R_NONE, OPTFASTREPLY, "no" },
664 ** When \fIset\fP, the initial prompt for recipients and subject are skipped
665 ** when replying to messages, and the initial prompt for subject is
666 ** skipped when forwarding messages.
668 ** \fBNote:\fP this variable has no effect when the ``$$autoedit''
669 ** variable is \fIset\fP.
671 {"fcc_attach", DT_BOOL, R_NONE, OPTFCCATTACH, "yes" },
674 ** This variable controls whether or not attachments on outgoing messages
675 ** are saved along with the main body of your message.
677 {"fcc_clear", DT_BOOL, R_NONE, OPTFCCCLEAR, "no" },
680 ** When this variable is \fIset\fP, FCCs will be stored unencrypted and
681 ** unsigned, even when the actual message is encrypted and/or
685 {"file_charset", DT_STR, R_NONE, UL &FileCharset, "" },
688 ** This variable is a colon-separated list of character encoding
689 ** schemes for text file attatchments.
690 ** If \fIunset\fP, $$charset value will be used instead.
691 ** For example, the following configuration would work for Japanese
694 ** \fTset file_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"\fP
696 ** Note: ``\fTiso-2022-*\fP'' must be put at the head of the value as shown above
699 {"folder", DT_PATH, R_NONE, UL &Maildir, "~/Mail"},
702 ** Specifies the default location of your mailboxes. A ``\fT+\fP'' or ``\fT=\fP'' at the
703 ** beginning of a pathname will be expanded to the value of this
704 ** variable. Note that if you change this variable from the default
705 ** value you need to make sure that the assignment occurs \fIbefore\fP
706 ** you use ``+'' or ``='' for any other variables since expansion takes place
707 ** during the ``set'' command.
709 {"folder_format", DT_STR, R_INDEX, UL &FolderFormat, "%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f"},
712 ** This variable allows you to customize the file browser display to your
713 ** personal taste. This string is similar to ``$$index_format'', but has
714 ** its own set of \fTprintf(3)\fP-like sequences:
717 ** .dt %C .dd current file number
718 ** .dt %d .dd date/time folder was last modified
719 ** .dt %f .dd filename
720 ** .dt %F .dd file permissions
721 ** .dt %g .dd group name (or numeric gid, if missing)
722 ** .dt %l .dd number of hard links
723 ** .dt %N .dd N if folder has new mail, blank otherwise
724 ** .dt %s .dd size in bytes
725 ** .dt %t .dd * if the file is tagged, blank otherwise
726 ** .dt %u .dd owner name (or numeric uid, if missing)
727 ** .dt %>X .dd right justify the rest of the string and pad with character "X"
728 ** .dt %|X .dd pad to the end of the line with character "X"
731 {"followup_to", DT_BOOL, R_NONE, OPTFOLLOWUPTO, "yes" },
734 ** Controls whether or not the \fTMail-Followup-To:\fP header field is
735 ** generated when sending mail. When \fIset\fP, Mutt-ng will generate this
736 ** field when you are replying to a known mailing list, specified with
737 ** the ``subscribe'' or ``$lists'' commands or detected by common mailing list
740 ** This field has two purposes. First, preventing you from
741 ** receiving duplicate copies of replies to messages which you send
742 ** to mailing lists. Second, ensuring that you do get a reply
743 ** separately for any messages sent to known lists to which you are
744 ** not subscribed. The header will contain only the list's address
745 ** for subscribed lists, and both the list address and your own
746 ** email address for unsubscribed lists. Without this header, a
747 ** group reply to your message sent to a subscribed list will be
748 ** sent to both the list and your address, resulting in two copies
749 ** of the same email for you.
752 {"followup_to_poster", DT_SYN, R_NONE, UL "nntp_followup_to_poster", 0},
753 {"nntp_followup_to_poster", DT_QUAD, R_NONE, OPT_FOLLOWUPTOPOSTER, "ask-yes" },
756 ** Availability: NNTP
759 ** If this variable is \fIset\fP and the keyword "\fTposter\fP" is present in
760 ** the \fTFollowup-To:\fP header field, a follow-up to the newsgroup is not
761 ** permitted. The message will be mailed to the submitter of the
765 {"force_name", DT_BOOL, R_NONE, OPTFORCENAME, "no" },
768 ** This variable is similar to ``$$save_name'', except that Mutt-ng will
769 ** store a copy of your outgoing message by the username of the address
770 ** you are sending to even if that mailbox does not exist.
772 ** Also see the ``$$record'' variable.
774 {"force_buffy_check", DT_BOOL, R_NONE, OPTFORCEBUFFYCHECK, "no" },
777 ** When \fIset\fP, it causes Mutt-ng to check for new mail when the
778 ** \fIbuffy-list\fP command is invoked. When \fIunset\fP, \fIbuffy_list\fP
779 ** will just list all mailboxes which are already known to have new mail.
781 ** Also see the following variables: ``$$timeout'', ``$$mail_check'' and
782 ** ``$$imap_mail_check''.
784 {"forward_decode", DT_BOOL, R_NONE, OPTFORWDECODE, "yes" },
787 ** Controls the decoding of complex MIME messages into \fTtext/plain\fP when
788 ** forwarding a message. The message header is also RFC2047 decoded.
789 ** This variable is only used, if ``$$mime_forward'' is \fIunset\fP,
790 ** otherwise ``$$mime_forward_decode'' is used instead.
792 {"forward_edit", DT_QUAD, R_NONE, OPT_FORWEDIT, "yes" },
795 ** This quadoption controls whether or not the user is automatically
796 ** placed in the editor when forwarding messages. For those who always want
797 ** to forward with no modification, use a setting of \fIno\fP.
799 {"forward_format", DT_STR, R_NONE, UL &ForwFmt, "[%a: %s]"},
802 ** This variable controls the default subject when forwarding a message.
803 ** It uses the same format sequences as the ``$$index_format'' variable.
805 {"forward_quote", DT_BOOL, R_NONE, OPTFORWQUOTE, "no" },
808 ** When \fIset\fP forwarded messages included in the main body of the
809 ** message (when ``$$mime_forward'' is \fIunset\fP) will be quoted using
810 ** ``$$indent_string''.
812 {"from", DT_ADDR, R_NONE, UL &From, "" },
815 ** This variable contains a default from address. It
816 ** can be overridden using my_hdr (including from send-hooks) and
817 ** ``$$reverse_name''. This variable is ignored if ``$$use_from''
821 ** \fTsend-hook Mutt-ng-devel@lists.berlios.de 'my_hdr From: Foo Bar <foo@bar.fb>'\fP
822 ** when replying to the mutt-ng developer's mailing list and Mutt-ng takes this email address.
824 ** Defaults to the contents of the environment variable \fT$$$EMAIL\fP.
826 {"gecos_mask", DT_RX, R_NONE, UL &GecosMask, "^[^,]*"},
829 ** A regular expression used by Mutt-ng to parse the GECOS field of a password
830 ** entry when expanding the alias. By default the regular expression is set
831 ** to ``\fT^[^,]*\fP'' which will return the string up to the first ``\fT,\fP'' encountered.
832 ** If the GECOS field contains a string like "lastname, firstname" then you
833 ** should do: \fTset gecos_mask=".*"\fP.
835 ** This can be useful if you see the following behavior: you address a e-mail
836 ** to user ID stevef whose full name is Steve Franklin. If Mutt-ng expands
837 ** stevef to ``Franklin'' stevef@foo.bar then you should set the gecos_mask to
838 ** a regular expression that will match the whole name so Mutt-ng will expand
839 ** ``Franklin'' to ``Franklin, Steve''.
842 {"group_index_format", DT_SYN, R_NONE, UL "nntp_group_index_format", 0},
843 {"nntp_group_index_format", DT_STR, R_BOTH, UL &GroupFormat, "%4C %M%N %5s %-45.45f %d"},
846 ** Availability: NNTP
849 ** This variable allows you to customize the newsgroup browser display to
850 ** your personal taste. This string is similar to ``$index_format'', but
851 ** has its own set of \fTprintf(3)\fP-like sequences:
854 ** %C current newsgroup number
855 ** %d description of newsgroup (retrieved from server)
857 ** %M ``-'' if newsgroup not allowed for direct post (moderated for example)
858 ** %N ``N'' if newsgroup is new, ``u'' if unsubscribed, blank otherwise
859 ** %n number of new articles in newsgroup
860 ** %s number of unread articles in newsgroup
861 ** %>X right justify the rest of the string and pad with character "X"
862 ** %|X pad to the end of the line with character "X"
866 {"hdrs", DT_BOOL, R_NONE, OPTHDRS, "yes" },
869 ** When \fIunset\fP, the header fields normally added by the ``$my_hdr''
870 ** command are not created. This variable \fImust\fP be \fIunset\fP before
871 ** composing a new message or replying in order to take effect. If \fIset\fP,
872 ** the user defined header fields are added to every new message.
874 {"header", DT_BOOL, R_NONE, OPTHEADER, "no" },
877 ** When \fIset\fP, this variable causes Mutt-ng to include the header
878 ** of the message you are replying to into the edit buffer.
879 ** The ``$$weed'' setting applies.
881 {"help", DT_BOOL, R_BOTH, OPTHELP, "yes" },
884 ** When \fIset\fP, help lines describing the bindings for the major functions
885 ** provided by each menu are displayed on the first line of the screen.
887 ** \fBNote:\fP The binding will not be displayed correctly if the
888 ** function is bound to a sequence rather than a single keystroke. Also,
889 ** the help line may not be updated if a binding is changed while Mutt-ng is
890 ** running. Since this variable is primarily aimed at new users, neither
891 ** of these should present a major problem.
893 {"hidden_host", DT_BOOL, R_NONE, OPTHIDDENHOST, "no" },
896 ** When \fIset\fP, Mutt-ng will skip the host name part of ``$$hostname'' variable
897 ** when adding the domain part to addresses. This variable does not
898 ** affect the generation of \fTMessage-ID:\fP header fields, and it will not lead to the
899 ** cut-off of first-level domains.
901 {"hide_limited", DT_BOOL, R_TREE|R_INDEX, OPTHIDELIMITED, "no" },
904 ** When \fIset\fP, Mutt-ng will not show the presence of messages that are hidden
905 ** by limiting, in the thread tree.
907 {"hide_missing", DT_BOOL, R_TREE|R_INDEX, OPTHIDEMISSING, "yes" },
910 ** When \fIset\fP, Mutt-ng will not show the presence of missing messages in the
913 {"hide_thread_subject", DT_BOOL, R_TREE|R_INDEX, OPTHIDETHREADSUBJECT, "yes" },
916 ** When \fIset\fP, Mutt-ng will not show the subject of messages in the thread
917 ** tree that have the same subject as their parent or closest previously
918 ** displayed sibling.
920 {"hide_top_limited", DT_BOOL, R_TREE|R_INDEX, OPTHIDETOPLIMITED, "no" },
923 ** When \fIset\fP, Mutt-ng will not show the presence of messages that are hidden
924 ** by limiting, at the top of threads in the thread tree. Note that when
925 ** $$hide_missing is set, this option will have no effect.
927 {"hide_top_missing", DT_BOOL, R_TREE|R_INDEX, OPTHIDETOPMISSING, "yes" },
930 ** When \fIset\fP, Mutt-ng will not show the presence of missing messages at the
931 ** top of threads in the thread tree. Note that when $$hide_limited is
932 ** \fIset\fP, this option will have no effect.
934 {"history", DT_NUM, R_NONE, UL &HistSize, "10" },
937 ** This variable controls the size (in number of strings remembered) of
938 ** the string history buffer. The buffer is cleared each time the
939 ** variable is changed.
941 {"honor_followup_to", DT_QUAD, R_NONE, OPT_MFUPTO, "yes" },
944 ** This variable controls whether or not a \fTMail-Followup-To:\fP header field is
945 ** honored when group-replying to a message.
947 {"hostname", DT_STR, R_NONE, UL &Fqdn, "" },
950 ** Specifies the hostname to use after the ``\fT@\fP'' in local e-mail
951 ** addresses and during generation of \fTMessage-Id:\fP headers.
953 ** Please be sure to really know what you are doing when changing this variable
954 ** to configure a custom domain part of Message-IDs.
956 {"ignore_list_reply_to", DT_BOOL, R_NONE, OPTIGNORELISTREPLYTO, "no" },
959 ** Affects the behaviour of the \fIreply\fP function when replying to
960 ** messages from mailing lists. When \fIset\fP, if the ``\fTReply-To:\fP'' header field is
961 ** set to the same value as the ``\fTTo:\fP'' header field, Mutt-ng assumes that the
962 ** ``\fTReply-To:\fP'' header field was set by the mailing list to automate responses
963 ** to the list, and will ignore this field. To direct a response to the
964 ** mailing list when this option is set, use the \fIlist-reply\fP
965 ** function; \fIgroup-reply\fP will reply to both the sender and the
969 {"imap_authenticators", DT_STR, R_NONE, UL &ImapAuthenticators, "" },
972 ** Availability: IMAP
975 ** This is a colon-delimited list of authentication methods Mutt-ng may
976 ** attempt to use to log in to an IMAP server, in the order Mutt-ng should
977 ** try them. Authentication methods are either ``\fTlogin\fP'' or the right
978 ** side of an IMAP ``\fTAUTH=\fP'' capability string, e.g. ``\fTdigest-md5\fP'',
979 ** ``\fTgssapi\fP'' or ``\fTcram-md5\fP''. This parameter is case-insensitive.
982 ** parameter is \fIunset\fP (the default) Mutt-ng will try all available methods,
983 ** in order from most-secure to least-secure.
985 ** Example: \fTset imap_authenticators="gssapi:cram-md5:login"\fP
987 ** \fBNote:\fP Mutt-ng will only fall back to other authentication methods if
988 ** the previous methods are unavailable. If a method is available but
989 ** authentication fails, Mutt-ng will not connect to the IMAP server.
991 { "imap_check_subscribed", DT_BOOL, R_NONE, OPTIMAPCHECKSUBSCRIBED, "no" },
994 ** When \fIset\fP, mutt will fetch the set of subscribed folders from
995 ** your server on connection, and add them to the set of mailboxes
996 ** it polls for new mail. See also the ``$mailboxes'' command.
999 {"imap_delim_chars", DT_STR, R_NONE, UL &ImapDelimChars, "/."},
1002 ** Availability: IMAP
1005 ** This contains the list of characters which you would like to treat
1006 ** as folder separators for displaying IMAP paths. In particular it
1007 ** helps in using the '\fT=\fP' shortcut for your $$folder variable.
1009 {"imap_headers", DT_STR, R_INDEX, UL &ImapHeaders, "" },
1012 ** Availability: IMAP
1015 ** Mutt-ng requests these header fields in addition to the default headers
1016 ** (``DATE FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE
1017 ** CONTENT-DESCRIPTION IN-REPLY-TO REPLY-TO LINES X-LABEL'') from IMAP
1018 ** servers before displaying the ``index'' menu. You may want to add more
1019 ** headers for spam detection.
1021 ** \fBNote:\fP This is a space separated list.
1023 {"imap_home_namespace", DT_STR, R_NONE, UL &ImapHomeNamespace, "" },
1026 ** Availability: IMAP
1029 ** You normally want to see your personal folders alongside
1030 ** your \fTINBOX\fP in the IMAP browser. If you see something else, you may set
1031 ** this variable to the IMAP path to your folders.
1033 {"imap_keepalive", DT_NUM, R_NONE, UL &ImapKeepalive, "900" },
1036 ** Availability: IMAP
1039 ** This variable specifies the maximum amount of time in seconds that Mutt-ng
1040 ** will wait before polling open IMAP connections, to prevent the server
1041 ** from closing them before Mutt-ng has finished with them.
1044 ** well within the RFC-specified minimum amount of time (30 minutes) before
1045 ** a server is allowed to do this, but in practice the RFC does get
1046 ** violated every now and then.
1048 ** Reduce this number if you find yourself
1049 ** getting disconnected from your IMAP server due to inactivity.
1051 {"imap_login", DT_STR, R_NONE, UL &ImapLogin, "" },
1054 ** Availability: IMAP
1057 ** Your login name on the IMAP server.
1059 ** This variable defaults to the value of ``$$imap_user.''
1061 {"imap_list_subscribed", DT_BOOL, R_NONE, OPTIMAPLSUB, "no" },
1064 ** Availability: IMAP
1067 ** This variable configures whether IMAP folder browsing will look for
1068 ** only subscribed folders or all folders. This can be toggled in the
1069 ** IMAP browser with the \fItoggle-subscribed\fP function.
1071 {"imap_mail_check", DT_NUM, R_NONE, UL &ImapBuffyTimeout, "300" },
1074 ** This variable configures how often (in seconds) Mutt-ng should look for
1075 ** new mail in IMAP folders. This is split from the ``$mail_check'' variable
1076 ** to generate less traffic and get more accurate information for local folders.
1078 {"imap_pass", DT_STR, R_NONE, UL &ImapPass, "" },
1081 ** Availability: IMAP
1084 ** Specifies the password for your IMAP account. If \fIunset\fP, Mutt-ng will
1085 ** prompt you for your password when you invoke the fetch-mail function.
1087 ** \fBWarning\fP: you should only use this option when you are on a
1088 ** fairly secure machine, because the superuser can read your configuration even
1089 ** if you are the only one who can read the file.
1091 {"imap_passive", DT_BOOL, R_NONE, OPTIMAPPASSIVE, "yes" },
1094 ** Availability: IMAP
1097 ** When \fIset\fP, Mutt-ng will not open new IMAP connections to check for new
1098 ** mail. Mutt-ng will only check for new mail over existing IMAP
1099 ** connections. This is useful if you don't want to be prompted to
1100 ** user/password pairs on Mutt-ng invocation, or if opening the connection
1103 {"imap_peek", DT_BOOL, R_NONE, OPTIMAPPEEK, "yes" },
1106 ** Availability: IMAP
1109 ** If \fIset\fP, Mutt-ng will avoid implicitly marking your mail as read whenever
1110 ** you fetch a message from the server. This is generally a good thing,
1111 ** but can make closing an IMAP folder somewhat slower. This option
1112 ** exists to appease speed freaks.
1114 {"imap_reconnect", DT_QUAD, R_NONE, OPT_IMAPRECONNECT, "ask-yes" },
1117 ** Availability: IMAP
1120 ** Controls whether or not Mutt-ng will try to reconnect to IMAP server when
1121 ** the connection is lost.
1123 {"imap_servernoise", DT_BOOL, R_NONE, OPTIMAPSERVERNOISE, "yes" },
1126 ** Availability: IMAP
1129 ** When \fIset\fP, Mutt-ng will display warning messages from the IMAP
1130 ** server as error messages. Since these messages are often
1131 ** harmless, or generated due to configuration problems on the
1132 ** server which are out of the users' hands, you may wish to suppress
1133 ** them at some point.
1135 {"imap_user", DT_STR, R_NONE, UL &ImapUser, "" },
1138 ** Availability: IMAP
1141 ** The name of the user whose mail you intend to access on the IMAP
1144 ** This variable defaults to your user name on the local machine.
1147 {"implicit_autoview", DT_BOOL, R_NONE, OPTIMPLICITAUTOVIEW, "no" },
1150 ** If \fIset\fP, Mutt-ng will look for a mailcap entry with the
1151 ** ``\fTcopiousoutput\fP'' flag set for \fIevery\fP MIME attachment it doesn't have
1152 ** an internal viewer defined for. If such an entry is found, Mutt-ng will
1153 ** use the viewer defined in that entry to convert the body part to text
1156 {"include", DT_QUAD, R_NONE, OPT_INCLUDE, "ask-yes" },
1159 ** Controls whether or not a copy of the message(s) you are replying to
1160 ** is included in your reply.
1162 {"include_onlyfirst", DT_BOOL, R_NONE, OPTINCLUDEONLYFIRST, "no" },
1165 ** Controls whether or not Mutt-ng includes only the first attachment
1166 ** of the message you are replying.
1168 {"indent_string", DT_STR, R_NONE, UL &Prefix, "> "},
1171 ** Specifies the string to prepend to each line of text quoted in a
1172 ** message to which you are replying. You are strongly encouraged not to
1173 ** change this value, as it tends to agitate the more fanatical netizens.
1175 {"index_format", DT_STR, R_BOTH, UL &HdrFmt, "%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s"},
1178 ** This variable allows you to customize the message index display to
1179 ** your personal taste.
1181 ** ``Format strings'' are similar to the strings used in the ``C''
1182 ** function \fTprintf(3)\fP to format output (see the man page for more detail).
1183 ** The following sequences are defined in Mutt-ng:
1186 ** .dt %a .dd address of the author
1187 ** .dt %A .dd reply-to address (if present; otherwise: address of author)
1188 ** .dt %b .dd filename of the original message folder (think mailBox)
1189 ** .dt %B .dd the list to which the letter was sent, or else the folder name (%b).
1190 ** .dt %c .dd number of characters (bytes) in the message
1191 ** .dt %C .dd current message number
1192 ** .dt %d .dd date and time of the message in the format specified by
1193 ** ``date_format'' converted to sender's time zone
1194 ** .dt %D .dd date and time of the message in the format specified by
1195 ** ``date_format'' converted to the local time zone
1196 ** .dt %e .dd current message number in thread
1197 ** .dt %E .dd number of messages in current thread
1198 ** .dt %f .dd entire From: line (address + real name)
1199 ** .dt %F .dd author name, or recipient name if the message is from you
1200 ** .dt %H .dd spam attribute(s) of this message
1201 ** .dt %g .dd newsgroup name (if compiled with nntp support)
1202 ** .dt %i .dd message-id of the current message
1203 ** .dt %l .dd number of lines in the message (does not work with maildir,
1204 ** mh, and possibly IMAP folders)
1205 ** .dt %L .dd If an address in the To or CC header field matches an address
1206 ** defined by the users ``subscribe'' command, this displays
1207 ** "To <list-name>", otherwise the same as %F.
1208 ** .dt %m .dd total number of message in the mailbox
1209 ** .dt %M .dd number of hidden messages if the thread is collapsed.
1210 ** .dt %N .dd message score
1211 ** .dt %n .dd author's real name (or address if missing)
1212 ** .dt %O .dd (_O_riginal save folder) Where Mutt-ng would formerly have
1213 ** stashed the message: list name or recipient name if no list
1214 ** .dt %s .dd subject of the message
1215 ** .dt %S .dd status of the message (N/D/d/!/r/\(as)
1216 ** .dt %t .dd `to:' field (recipients)
1217 ** .dt %T .dd the appropriate character from the $$to_chars string
1218 ** .dt %u .dd user (login) name of the author
1219 ** .dt %v .dd first name of the author, or the recipient if the message is from you
1220 ** .dt %W .dd name of organization of author (`organization:' field)
1221 ** .dt %y .dd `x-label:' field, if present
1222 ** .dt %Y .dd `x-label' field, if present, and (1) not at part of a thread tree,
1223 ** (2) at the top of a thread, or (3) `x-label' is different from
1224 ** preceding message's `x-label'.
1225 ** .dt %Z .dd message status flags
1226 ** .dt %{fmt} .dd the date and time of the message is converted to sender's
1227 ** time zone, and ``fmt'' is expanded by the library function
1228 ** ``strftime''; a leading bang disables locales
1229 ** .dt %[fmt] .dd the date and time of the message is converted to the local
1230 ** time zone, and ``fmt'' is expanded by the library function
1231 ** ``strftime''; a leading bang disables locales
1232 ** .dt %(fmt) .dd the local date and time when the message was received.
1233 ** ``fmt'' is expanded by the library function ``strftime'';
1234 ** a leading bang disables locales
1235 ** .dt %<fmt> .dd the current local time. ``fmt'' is expanded by the library
1236 ** function ``strftime''; a leading bang disables locales.
1237 ** .dt %>X .dd right justify the rest of the string and pad with character "X"
1238 ** .dt %|X .dd pad to the end of the line with character "X"
1241 ** See also: ``$$to_chars''.
1244 {"inews", DT_SYN, R_NONE, UL "nntp_inews", 0},
1245 {"nntp_inews", DT_PATH, R_NONE, UL &Inews, ""},
1248 ** Availability: NNTP
1251 ** If \fIset\fP, specifies the program and arguments used to deliver news posted
1252 ** by Mutt-ng. Otherwise, Mutt-ng posts article using current connection.
1253 ** The following \fTprintf(3)\fP-style sequence is understood:
1256 ** %s newsserver name
1259 ** Example: \fTset inews="/usr/local/bin/inews -hS"\fP
1262 {"ispell", DT_PATH, R_NONE, UL &Ispell, ISPELL},
1265 ** How to invoke ispell (GNU's spell-checking software).
1267 {"keep_flagged", DT_BOOL, R_NONE, OPTKEEPFLAGGED, "no" },
1270 ** If \fIset\fP, read messages marked as flagged will not be moved
1271 ** from your spool mailbox to your ``$$mbox'' mailbox, or as a result of
1272 ** a ``$mbox-hook'' command.
1274 {"locale", DT_STR, R_BOTH, UL &Locale, "C"},
1277 ** The locale used by \fTstrftime(3)\fP to format dates. Legal values are
1278 ** the strings your system accepts for the locale variable \fTLC_TIME\fP.
1280 {"list_reply", DT_QUAD, R_NONE, OPT_LISTREPLY, "no" },
1283 ** When \fIset\fP, address replies to the mailing list the original message came
1284 ** from (instead to the author only). Setting this option to ``\fIask-yes\fP'' or
1285 ** ``\fIask-no\fP'' will ask if you really intended to reply to the author only.
1287 {"max_display_recips", DT_NUM, R_PAGER, UL &MaxDispRecips, "0" },
1290 ** When set non-zero, this specifies the maximum number of recipient header
1291 ** lines (\fTTo:\fP, \fTCc:\fP and \fTBcc:\fP) to display in the pager if header
1292 ** weeding is turned on. In case the number of lines exeeds its value, the
1293 ** last line will have 3 dots appended.
1295 {"max_line_length", DT_NUM, R_PAGER, UL &MaxLineLength, "0" },
1298 ** When \fIset\fP, the maximum line length for displaying ``format = flowed'' messages is limited
1299 ** to this length. A value of 0 (which is also the default) means that the
1300 ** maximum line length is determined by the terminal width and $$wrapmargin.
1302 {"mail_check", DT_NUM, R_NONE, UL &BuffyTimeout, "5" },
1305 ** This variable configures how often (in seconds) Mutt-ng should look for
1308 ** \fBNote:\fP This does not apply to IMAP mailboxes, see $$imap_mail_check.
1310 {"mailcap_path", DT_STR, R_NONE, UL &MailcapPath, "" },
1313 ** This variable specifies which files to consult when attempting to
1314 ** display MIME bodies not directly supported by Mutt-ng.
1316 {"mailcap_sanitize", DT_BOOL, R_NONE, OPTMAILCAPSANITIZE, "yes" },
1319 ** If \fIset\fP, Mutt-ng will restrict possible characters in mailcap \fT%\fP expandos
1320 ** to a well-defined set of safe characters. This is the safe setting,
1321 ** but we are not sure it doesn't break some more advanced MIME stuff.
1323 ** \fBDON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE
1328 {"header_cache", DT_PATH, R_NONE, UL &HeaderCache, "" },
1331 ** Availability: Header Cache
1334 ** The $$header_cache variable points to the header cache database.
1336 ** If $$header_cache points to a directory it will contain a header cache
1337 ** database per folder. If $$header_cache points to a file that file will
1338 ** be a single global header cache. By default it is \fIunset\fP so no
1339 ** header caching will be used.
1341 {"maildir_header_cache_verify", DT_BOOL, R_NONE, OPTHCACHEVERIFY, "yes" },
1344 ** Availability: Header Cache
1347 ** Check for Maildir unaware programs other than Mutt-ng having modified maildir
1348 ** files when the header cache is in use. This incurs one \fTstat(2)\fP per
1349 ** message every time the folder is opened.
1351 #if HAVE_GDBM || HAVE_DB4
1352 {"header_cache_pagesize", DT_STR, R_NONE, UL &HeaderCachePageSize, "16384"},
1355 ** Availability: Header Cache
1358 ** Change the maildir header cache database page size.
1361 ** or too small of a page size for the common header can waste
1362 ** space, memory effectiveness, or CPU time. The default should be more or
1363 ** less the best you can get. For details google for mutt header
1364 ** cache (first hit).
1366 #endif /* HAVE_GDBM || HAVE_DB 4 */
1368 { "header_cache_compress", DT_BOOL, R_NONE, OPTHCACHECOMPRESS, "no" },
1371 ** If enabled the header cache will be compressed. So only one fifth of the usual
1372 ** diskspace is used, but the uncompression can result in a slower open of the
1375 #endif /* HAVE_QDBM */
1376 #endif /* USE_HCACHE */
1377 {"maildir_trash", DT_BOOL, R_NONE, OPTMAILDIRTRASH, "no" },
1380 ** If \fIset\fP, messages marked as deleted will be saved with the maildir
1381 ** (T)rashed flag instead of physically deleted.
1383 ** \fBNOTE:\fP this only applies
1384 ** to maildir-style mailboxes. Setting it will have no effect on other
1387 ** It is similiar to the trash option.
1389 {"mark_old", DT_BOOL, R_BOTH, OPTMARKOLD, "yes" },
1392 ** Controls whether or not Mutt-ng marks \fInew\fP \fBunread\fP
1393 ** messages as \fIold\fP if you exit a mailbox without reading them.
1395 ** With this option \fIset\fP, the next time you start Mutt-ng, the messages
1396 ** will show up with an "O" next to them in the ``index'' menu,
1397 ** indicating that they are old.
1399 {"markers", DT_BOOL, R_PAGER, OPTMARKERS, "yes" },
1402 ** Controls the display of wrapped lines in the internal pager. If set, a
1403 ** ``\fT+\fP'' marker is displayed at the beginning of wrapped lines. Also see
1404 ** the ``$$smart_wrap'' variable.
1406 {"mask", DT_RX, R_NONE, UL &Mask, "!^\\.[^.]"},
1409 ** A regular expression used in the file browser, optionally preceded by
1410 ** the \fInot\fP operator ``\fT!\fP''. Only files whose names match this mask
1411 ** will be shown. The match is always case-sensitive.
1413 {"mbox", DT_PATH, R_BOTH, UL &Inbox, "~/mbox"},
1416 ** This specifies the folder into which read mail in your ``$$spoolfile''
1417 ** folder will be appended.
1419 {"operating_system", DT_STR, R_NONE, UL &OperatingSystem, "" },
1422 ** This specifies the operating system name for the \fTUser-Agent:\fP header field. If
1423 ** this is \fIunset\fP, it will be set to the operating system name that \fTuname(2)\fP
1424 ** returns. If \fTuname(2)\fP fails, ``UNIX'' will be used.
1426 ** It may, for example, look as: ``\fTmutt-ng 1.5.9i (Linux)\fP''.
1428 {"sidebar_boundary", DT_STR, R_BOTH, UL &SidebarBoundary, "." },
1431 ** When the sidebar is displayed and $$sidebar_shorten_hierarchy is \fIset\fP, this
1432 ** variable specifies the characters at which to split a folder name into
1433 ** ``hierarchy items.''
1435 {"sidebar_delim", DT_STR, R_BOTH, UL &SidebarDelim, "|"},
1438 ** This specifies the delimiter between the sidebar (if visible) and
1441 {"sidebar_visible", DT_BOOL, R_BOTH, OPTMBOXPANE, "no" },
1444 ** This specifies whether or not to show the sidebar (a list of folders specified
1445 ** with the ``mailboxes'' command).
1447 {"sidebar_width", DT_NUM, R_BOTH, UL &SidebarWidth, "0" },
1450 ** The width of the sidebar.
1452 {"sidebar_newmail_only", DT_BOOL, R_BOTH, OPTSIDEBARNEWMAILONLY, "no" },
1455 ** If \fIset\fP, only folders with new mail will be shown in the sidebar.
1457 {"sidebar_number_format", DT_STR, R_BOTH, UL &SidebarNumberFormat, "%m%?n?(%n)?%?f?[%f]?"},
1460 ** This variable controls how message counts are printed when the sidebar
1461 ** is enabled. If this variable is \fIempty\fP (\fIand only if\fP), no numbers
1462 ** will be printed \fIand\fP mutt-ng won't frequently count mail (which
1463 ** may be a great speedup esp. with mbox-style mailboxes.)
1465 ** The following \fTprintf(3)\fP-like sequences are supported all of which
1466 ** may be printed non-zero:
1469 ** .dt %d .dd Number of deleted messages. 1)
1470 ** .dt %F .dd Number of flagged messages.
1471 ** .dt %m .dd Total number of messages.
1472 ** .dt %M .dd Total number of messages shown, i.e. not hidden by a limit. 1)
1473 ** .dt %n .dd Number of new messages.
1474 ** .dt %t .dd Number of tagged messages. 1)
1477 ** 1) These expandos only have a non-zero value for the current mailbox and
1478 ** will always be zero otherwise.
1480 {"sidebar_shorten_hierarchy", DT_BOOL, R_NONE, OPTSHORTENHIERARCHY, "no" },
1483 ** When \fIset\fP, the ``hierarchy'' of the sidebar entries will be shortened
1484 ** only if they cannot be printed in full length (because ``$$sidebar_width''
1485 ** is set to a too low value). For example, if the newsgroup name
1486 ** ``de.alt.sysadmin.recovery'' doesn't fit on the screen, it'll get shortened
1487 ** ``d.a.s.recovery'' while ``de.alt.d0'' still would and thus will not get
1490 ** At which characters this compression is done is controled via the
1491 ** $$sidebar_boundary variable.
1493 {"mbox_type", DT_MAGIC, R_NONE, UL &DefaultMagic, "mbox" },
1496 ** The default mailbox type used when creating new folders. May be any of
1497 ** \fTmbox\fP, \fTMMDF\fP, \fTMH\fP and \fTMaildir\fP.
1499 {"metoo", DT_BOOL, R_NONE, OPTMETOO, "no" },
1502 ** If \fIunset\fP, Mutt-ng will remove your address (see the ``alternates''
1503 ** command) from the list of recipients when replying to a message.
1505 {"menu_context", DT_NUM, R_NONE, UL &MenuContext, "0" },
1508 ** This variable controls the number of lines of context that are given
1509 ** when scrolling through menus. (Similar to ``$$pager_context''.)
1511 {"menu_move_off", DT_BOOL, R_NONE, OPTMENUMOVEOFF, "yes" },
1514 ** When \fIunset\fP, the bottom entry of menus will never scroll up past
1515 ** the bottom of the screen, unless there are less entries than lines.
1516 ** When \fIset\fP, the bottom entry may move off the bottom.
1518 {"menu_scroll", DT_BOOL, R_NONE, OPTMENUSCROLL, "no" },
1521 ** When \fIset\fP, menus will be scrolled up or down one line when you
1522 ** attempt to move across a screen boundary. If \fIunset\fP, the screen
1523 ** is cleared and the next or previous page of the menu is displayed
1524 ** (useful for slow links to avoid many redraws).
1526 {"meta_key", DT_BOOL, R_NONE, OPTMETAKEY, "no" },
1529 ** If \fIset\fP, forces Mutt-ng to interpret keystrokes with the high bit (bit 8)
1530 ** set as if the user had pressed the \fTESC\fP key and whatever key remains
1531 ** after having the high bit removed. For example, if the key pressed
1532 ** has an ASCII value of \fT0xf4\fP, then this is treated as if the user had
1533 ** pressed \fTESC\fP then ``\fTx\fP''. This is because the result of removing the
1534 ** high bit from ``\fT0xf4\fP'' is ``\fT0x74\fP'', which is the ASCII character
1537 {"mh_purge", DT_BOOL, R_NONE, OPTMHPURGE, "no" },
1540 ** When \fIunset\fP, Mutt-ng will mimic mh's behaviour and rename deleted messages
1541 ** to \fI,<old file name>\fP in mh folders instead of really deleting
1542 ** them. If the variable is set, the message files will simply be
1545 {"mh_seq_flagged", DT_STR, R_NONE, UL &MhFlagged, "flagged"},
1548 ** The name of the MH sequence used for flagged messages.
1550 {"mh_seq_replied", DT_STR, R_NONE, UL &MhReplied, "replied"},
1553 ** The name of the MH sequence used to tag replied messages.
1555 {"mh_seq_unseen", DT_STR, R_NONE, UL &MhUnseen, "unseen"},
1558 ** The name of the MH sequence used for unseen messages.
1560 {"mime_forward", DT_QUAD, R_NONE, OPT_MIMEFWD, "no" },
1563 ** When \fIset\fP, the message you are forwarding will be attached as a
1564 ** separate MIME part instead of included in the main body of the
1567 ** This is useful for forwarding MIME messages so the receiver
1568 ** can properly view the message as it was delivered to you. If you like
1569 ** to switch between MIME and not MIME from mail to mail, set this
1570 ** variable to ask-no or ask-yes.
1572 ** Also see ``$$forward_decode'' and ``$$mime_forward_decode''.
1574 {"mime_forward_decode", DT_BOOL, R_NONE, OPTMIMEFORWDECODE, "no" },
1577 ** Controls the decoding of complex MIME messages into \fTtext/plain\fP when
1578 ** forwarding a message while ``$$mime_forward'' is \fIset\fP. Otherwise
1579 ** ``$$forward_decode'' is used instead.
1581 {"mime_forward_rest", DT_QUAD, R_NONE, OPT_MIMEFWDREST, "yes" },
1584 ** When forwarding multiple attachments of a MIME message from the recvattach
1585 ** menu, attachments which cannot be decoded in a reasonable manner will
1586 ** be attached to the newly composed message if this option is set.
1590 {"mime_subject", DT_SYN, R_NONE, UL "nntp_mime_subject", 0},
1591 {"nntp_mime_subject", DT_BOOL, R_NONE, OPTMIMESUBJECT, "yes" },
1594 ** Availability: NNTP
1597 ** If \fIunset\fP, an 8-bit ``\fTSubject:\fP'' header field in a news article
1598 ** will not be encoded according to RFC2047.
1600 ** \fBNote:\fP Only change this setting if you know what you are doing.
1605 {"mix_entry_format", DT_STR, R_NONE, UL &MixEntryFormat, "%4n %c %-16s %a"},
1608 ** Availability: Mixmaster
1611 ** This variable describes the format of a remailer line on the mixmaster
1612 ** chain selection screen. The following \fTprintf(3)\fP-like sequences are
1616 ** .dt %n .dd The running number on the menu.
1617 ** .dt %c .dd Remailer capabilities.
1618 ** .dt %s .dd The remailer's short name.
1619 ** .dt %a .dd The remailer's e-mail address.
1622 {"mixmaster", DT_PATH, R_NONE, UL &Mixmaster, MIXMASTER},
1625 ** Availability: Mixmaster
1628 ** This variable contains the path to the Mixmaster binary on your
1629 ** system. It is used with various sets of parameters to gather the
1630 ** list of known remailers, and to finally send a message through the
1634 {"move", DT_QUAD, R_NONE, OPT_MOVE, "ask-no" },
1637 ** Controls whether or not Mutt-ng will move read messages
1638 ** from your spool mailbox to your ``$$mbox'' mailbox, or as a result of
1639 ** a ``$mbox-hook'' command.
1641 {"message_format", DT_STR, R_NONE, UL &MsgFmt, "%s"},
1644 ** This is the string displayed in the ``attachment'' menu for
1645 ** attachments of type \fTmessage/rfc822\fP. For a full listing of defined
1646 ** \fTprintf(3)\fP-like sequences see the section on ``$$index_format''.
1648 {"msgid_format", DT_STR, R_NONE, UL &MsgIdFormat, "%Y%m%d%h%M%s.G%P%p"},
1651 ** This is the format for the ``local part'' of the \fTMessage-Id:\fP header
1652 ** field generated by Mutt-ng. If this variable is empty, no \fTMessage-Id:\fP
1653 ** headers will be generated. The '%'
1654 ** character marks that certain data will be added to the string, similar to
1655 ** \fTprintf(3)\fP. The following characters are allowed:
1658 ** .dt %d .dd the current day of month
1659 ** .dt %h .dd the current hour
1660 ** .dt %m .dd the current month
1661 ** .dt %M .dd the current minute
1662 ** .dt %O .dd the current UNIX timestamp (octal)
1663 ** .dt %p .dd the process ID
1664 ** .dt %P .dd the current Message-ID prefix (a character rotating with
1665 ** every Message-ID being generated)
1666 ** .dt %r .dd a random integer value (decimal)
1667 ** .dt %R .dd a random integer value (hexadecimal)
1668 ** .dt %s .dd the current second
1669 ** .dt %T .dd the current UNIX timestamp (decimal)
1670 ** .dt %X .dd the current UNIX timestamp (hexadecimal)
1671 ** .dt %Y .dd the current year (Y2K compliant)
1672 ** .dt %% .dd the '%' character
1675 ** \fBNote:\fP Please only change this setting if you know what you are doing.
1676 ** Also make sure to consult RFC2822 to produce technically \fIvalid\fP strings.
1678 {"narrow_tree", DT_BOOL, R_TREE|R_INDEX, OPTNARROWTREE, "no" },
1681 ** This variable, when \fIset\fP, makes the thread tree narrower, allowing
1682 ** deeper threads to fit on the screen.
1685 {"news_cache_dir", DT_SYN, R_NONE, UL "nntp_cache_dir", 0},
1686 {"nntp_cache_dir", DT_PATH, R_NONE, UL &NewsCacheDir, "~/.muttng"},
1689 ** Availability: NNTP
1692 ** This variable points to directory where Mutt-ng will cache news
1693 ** article headers. If \fIunset\fP, headers will not be saved at all
1694 ** and will be reloaded each time when you enter a newsgroup.
1696 ** As for the header caching in connection with IMAP and/or Maildir,
1697 ** this drastically increases speed and lowers traffic.
1699 {"news_server", DT_SYN, R_NONE, UL "nntp_host", 0 },
1700 {"nntp_host", DT_STR, R_NONE, UL &NewsServer, "" },
1703 ** Availability: NNTP
1706 ** This variable specifies the name (or address) of the NNTP server to be used.
1709 ** defaults to the value specified via the environment variable
1710 ** \fT$$$NNTPSERVER\fP or contained in the file \fT/etc/nntpserver\fP.
1713 ** specify a username and an alternative port for each newsserver, e.g.
1715 ** \fT[nntp[s]://][username[:password]@]newsserver[:port]\fP
1717 ** \fBNote:\fP Using a password as shown and stored in a configuration file
1718 ** presents a security risk since the superuser of your machine may read it
1719 ** regardless of the file's permissions.
1721 {"newsrc", DT_SYN, R_NONE, UL "nntp_newsrc", 0},
1722 {"nntp_newsrc", DT_PATH, R_NONE, UL &NewsRc, "~/.newsrc"},
1725 ** Availability: NNTP
1728 ** This file contains information about subscribed newsgroup and
1729 ** articles read so far.
1731 ** To ease the use of multiple news servers, the following \fTprintf(3)\fP-style
1732 ** sequence is understood:
1735 ** %s newsserver name
1738 {"nntp_context", DT_NUM, R_NONE, UL &NntpContext, "1000" },
1741 ** Availability: NNTP
1744 ** This variable controls how many news articles to cache per newsgroup
1745 ** (if caching is enabled, see $$nntp_cache_dir) and how many news articles
1746 ** to show in the ``index'' menu.
1748 ** If there're more articles than defined with $$nntp_context, all older ones
1749 ** will be removed/not shown in the index.
1751 {"nntp_load_description", DT_BOOL, R_NONE, OPTLOADDESC, "yes" },
1754 ** Availability: NNTP
1757 ** This variable controls whether or not descriptions for newsgroups
1758 ** are to be loaded when subscribing to a newsgroup.
1760 {"nntp_user", DT_STR, R_NONE, UL &NntpUser, ""},
1763 ** Availability: NNTP
1766 ** Your login name on the NNTP server. If \fIunset\fP and the server requires
1767 ** authentification, Mutt-ng will prompt you for your account name.
1769 {"nntp_pass", DT_STR, R_NONE, UL &NntpPass, ""},
1772 ** Availability: NNTP
1775 ** Your password for NNTP account.
1777 ** \fBNote:\fP Storing passwords in a configuration file
1778 ** presents a security risk since the superuser of your machine may read it
1779 ** regardless of the file's permissions.
1781 {"nntp_poll", DT_SYN, R_NONE, UL "nntp_mail_check", 0},
1782 {"nntp_mail_check", DT_NUM, R_NONE, UL &NewsPollTimeout, "60" },
1785 ** Availability: NNTP
1788 ** The time in seconds until any operations on a newsgroup except posting a new
1789 ** article will cause a recheck for new news. If set to 0, Mutt-ng will
1790 ** recheck on each operation in index (stepping, read article, etc.).
1792 {"nntp_reconnect", DT_QUAD, R_NONE, OPT_NNTPRECONNECT, "ask-yes" },
1795 ** Availability: NNTP
1798 ** Controls whether or not Mutt-ng will try to reconnect to a newsserver when the
1799 ** was connection lost.
1802 {"pager", DT_PATH, R_NONE, UL &Pager, "builtin"},
1805 ** This variable specifies which pager you would like to use to view
1806 ** messages. ``builtin'' means to use the builtin pager, otherwise this
1807 ** variable should specify the pathname of the external pager you would
1810 ** Using an external pager may have some disadvantages: Additional
1811 ** keystrokes are necessary because you can't call Mutt-ng functions
1812 ** directly from the pager, and screen resizes cause lines longer than
1813 ** the screen width to be badly formatted in the help menu.
1815 {"pager_context", DT_NUM, R_NONE, UL &PagerContext, "0" },
1818 ** This variable controls the number of lines of context that are given
1819 ** when displaying the next or previous page in the internal pager. By
1820 ** default, Mutt-ng will display the line after the last one on the screen
1821 ** at the top of the next page (0 lines of context).
1823 {"pager_format", DT_STR, R_PAGER, UL &PagerFmt, "-%Z- %C/%m: %-20.20n %s"},
1826 ** This variable controls the format of the one-line message ``status''
1827 ** displayed before each message in either the internal or an external
1828 ** pager. The valid sequences are listed in the ``$$index_format''
1831 {"pager_index_lines", DT_NUM, R_PAGER, UL &PagerIndexLines, "0" },
1834 ** Determines the number of lines of a mini-index which is shown when in
1835 ** the pager. The current message, unless near the top or bottom of the
1836 ** folder, will be roughly one third of the way down this mini-index,
1837 ** giving the reader the context of a few messages before and after the
1838 ** message. This is useful, for example, to determine how many messages
1839 ** remain to be read in the current thread. One of the lines is reserved
1840 ** for the status bar from the index, so a \fIpager_index_lines\fP of 6
1841 ** will only show 5 lines of the actual index. A value of 0 results in
1842 ** no index being shown. If the number of messages in the current folder
1843 ** is less than \fIpager_index_lines\fP, then the index will only use as
1844 ** many lines as it needs.
1846 {"pager_stop", DT_BOOL, R_NONE, OPTPAGERSTOP, "no" },
1849 ** When \fIset\fP, the internal-pager will \fBnot\fP move to the next message
1850 ** when you are at the end of a message and invoke the \fInext-page\fP
1853 {"crypt_autosign", DT_BOOL, R_NONE, OPTCRYPTAUTOSIGN, "no" },
1856 ** Setting this variable will cause Mutt-ng to always attempt to
1857 ** cryptographically sign outgoing messages. This can be overridden
1858 ** by use of the \fIpgp-menu\fP, when signing is not required or
1859 ** encryption is requested as well. If ``$$smime_is_default'' is \fIset\fP,
1860 ** then OpenSSL is used instead to create S/MIME messages and settings can
1861 ** be overridden by use of the \fIsmime-menu\fP.
1864 {"crypt_autoencrypt", DT_BOOL, R_NONE, OPTCRYPTAUTOENCRYPT, "no" },
1867 ** Setting this variable will cause Mutt-ng to always attempt to PGP
1868 ** encrypt outgoing messages. This is probably only useful in
1869 ** connection to the \fIsend-hook\fP command. It can be overridden
1870 ** by use of the \fIpgp-menu\fP, when encryption is not required or
1871 ** signing is requested as well. If ``$$smime_is_default'' is \fIset\fP,
1872 ** then OpenSSL is used instead to create S/MIME messages and
1873 ** settings can be overridden by use of the \fIsmime-menu\fP.
1876 {"pgp_ignore_subkeys", DT_BOOL, R_NONE, OPTPGPIGNORESUB, "yes" },
1879 ** Setting this variable will cause Mutt-ng to ignore OpenPGP subkeys. Instead,
1880 ** the principal key will inherit the subkeys' capabilities. \fIUnset\fP this
1881 ** if you want to play interesting key selection games.
1884 {"crypt_replyencrypt", DT_BOOL, R_NONE, OPTCRYPTREPLYENCRYPT, "yes" },
1887 ** If \fIset\fP, automatically PGP or OpenSSL encrypt replies to messages which are
1891 {"crypt_replysign", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGN, "no" },
1894 ** If \fIset\fP, automatically PGP or OpenSSL sign replies to messages which are
1897 ** \fBNote:\fP this does not work on messages that are encrypted \fBand\fP signed!
1900 {"crypt_replysignencrypted", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGNENCRYPTED, "no" },
1903 ** If \fIset\fP, automatically PGP or OpenSSL sign replies to messages
1904 ** which are encrypted. This makes sense in combination with
1905 ** ``$$crypt_replyencrypt'', because it allows you to sign all
1906 ** messages which are automatically encrypted. This works around
1907 ** the problem noted in ``$$crypt_replysign'', that Mutt-ng is not able
1908 ** to find out whether an encrypted message is also signed.
1911 {"crypt_timestamp", DT_BOOL, R_NONE, OPTCRYPTTIMESTAMP, "yes" },
1914 ** If \fIset\fP, Mutt-ng will include a time stamp in the lines surrounding
1915 ** PGP or S/MIME output, so spoofing such lines is more difficult.
1916 ** If you are using colors to mark these lines, and rely on these,
1917 ** you may \fIunset\fP this setting.
1920 {"pgp_use_gpg_agent", DT_BOOL, R_NONE, OPTUSEGPGAGENT, "no" },
1923 ** If \fIset\fP, Mutt-ng will use a possibly-running gpg-agent process.
1926 {"crypt_verify_sig", DT_QUAD, R_NONE, OPT_VERIFYSIG, "yes" },
1929 ** If ``\fIyes\fP'', always attempt to verify PGP or S/MIME signatures.
1930 ** If ``\fIask\fP'', ask whether or not to verify the signature.
1931 ** If ``\fIno\fP'', never attempt to verify cryptographic signatures.
1934 {"smime_is_default", DT_BOOL, R_NONE, OPTSMIMEISDEFAULT, "no" },
1937 ** The default behaviour of Mutt-ng is to use PGP on all auto-sign/encryption
1938 ** operations. To override and to use OpenSSL instead this must be \fIset\fP.
1940 ** However, this has no effect while replying, since Mutt-ng will automatically
1941 ** select the same application that was used to sign/encrypt the original
1944 ** (Note that this variable can be overridden by unsetting $$crypt_autosmime.)
1947 {"smime_ask_cert_label", DT_BOOL, R_NONE, OPTASKCERTLABEL, "yes" },
1950 ** This flag controls whether you want to be asked to enter a label
1951 ** for a certificate about to be added to the database or not. It is
1952 ** \fIset\fP by default.
1955 {"smime_decrypt_use_default_key", DT_BOOL, R_NONE, OPTSDEFAULTDECRYPTKEY, "yes" },
1958 ** If \fIset\fP (default) this tells Mutt-ng to use the default key for decryption. Otherwise,
1959 ** if manage multiple certificate-key-pairs, Mutt-ng will try to use the mailbox-address
1960 ** to determine the key to use. It will ask you to supply a key, if it can't find one.
1963 {"pgp_entry_format", DT_STR, R_NONE, UL &PgpEntryFormat, "%4n %t%f %4l/0x%k %-4a %2c %u"},
1966 ** This variable allows you to customize the PGP key selection menu to
1967 ** your personal taste. This string is similar to ``$$index_format'', but
1968 ** has its own set of \fTprintf(3)\fP-like sequences:
1971 ** .dt %n .dd number
1972 ** .dt %k .dd key id
1973 ** .dt %u .dd user id
1974 ** .dt %a .dd algorithm
1975 ** .dt %l .dd key length
1977 ** .dt %c .dd capabilities
1978 ** .dt %t .dd trust/validity of the key-uid association
1979 ** .dt %[<s>] .dd date of the key where <s> is an \fTstrftime(3)\fP expression
1984 {"pgp_good_sign", DT_RX, R_NONE, UL &PgpGoodSign, "" },
1987 ** If you assign a text to this variable, then a PGP signature is only
1988 ** considered verified if the output from $$pgp_verify_command contains
1989 ** the text. Use this variable if the exit code from the command is 0
1990 ** even for bad signatures.
1993 {"pgp_check_exit", DT_BOOL, R_NONE, OPTPGPCHECKEXIT, "yes" },
1996 ** If \fIset\fP, Mutt-ng will check the exit code of the PGP subprocess when
1997 ** signing or encrypting. A non-zero exit code means that the
1998 ** subprocess failed.
2001 {"pgp_long_ids", DT_BOOL, R_NONE, OPTPGPLONGIDS, "no" },
2004 ** If \fIset\fP, use 64 bit PGP key IDs. \fIUnset\fP uses the normal 32 bit Key IDs.
2007 {"pgp_retainable_sigs", DT_BOOL, R_NONE, OPTPGPRETAINABLESIG, "no" },
2010 ** If \fIset\fP, signed and encrypted messages will consist of nested
2011 ** multipart/signed and multipart/encrypted body parts.
2013 ** This is useful for applications like encrypted and signed mailing
2014 ** lists, where the outer layer (multipart/encrypted) can be easily
2015 ** removed, while the inner multipart/signed part is retained.
2018 {"pgp_autoinline", DT_BOOL, R_NONE, OPTPGPAUTOINLINE, "no" },
2021 ** This option controls whether Mutt-ng generates old-style inline
2022 ** (traditional) PGP encrypted or signed messages under certain
2023 ** circumstances. This can be overridden by use of the \fIpgp-menu\fP,
2024 ** when inline is not required.
2026 ** Note that Mutt-ng might automatically use PGP/MIME for messages
2027 ** which consist of more than a single MIME part. Mutt-ng can be
2028 ** configured to ask before sending PGP/MIME messages when inline
2029 ** (traditional) would not work.
2030 ** See also: ``$$pgp_mime_auto''.
2032 ** Also note that using the old-style PGP message format is \fBstrongly\fP
2033 ** \fBdeprecated\fP.
2036 {"pgp_replyinline", DT_BOOL, R_NONE, OPTPGPREPLYINLINE, "no" },
2039 ** Setting this variable will cause Mutt-ng to always attempt to
2040 ** create an inline (traditional) message when replying to a
2041 ** message which is PGP encrypted/signed inline. This can be
2042 ** overridden by use of the \fIpgp-menu\fP, when inline is not
2043 ** required. This option does not automatically detect if the
2044 ** (replied-to) message is inline; instead it relies on Mutt-ng
2045 ** internals for previously checked/flagged messages.
2047 ** Note that Mutt-ng might automatically use PGP/MIME for messages
2048 ** which consist of more than a single MIME part. Mutt-ng can be
2049 ** configured to ask before sending PGP/MIME messages when inline
2050 ** (traditional) would not work.
2051 ** See also: ``$$pgp_mime_auto''.
2053 ** Also note that using the old-style PGP message format is \fBstrongly\fP
2054 ** \fBdeprecated\fP.
2058 {"pgp_show_unusable", DT_BOOL, R_NONE, OPTPGPSHOWUNUSABLE, "yes" },
2061 ** If \fIset\fP, Mutt-ng will display non-usable keys on the PGP key selection
2062 ** menu. This includes keys which have been revoked, have expired, or
2063 ** have been marked as ``disabled'' by the user.
2066 {"pgp_sign_as", DT_STR, R_NONE, UL &PgpSignAs, "" },
2069 ** If you have more than one key pair, this option allows you to specify
2070 ** which of your private keys to use. It is recommended that you use the
2071 ** keyid form to specify your key (e.g., ``\fT0x00112233\fP'').
2074 {"pgp_strict_enc", DT_BOOL, R_NONE, OPTPGPSTRICTENC, "yes" },
2077 ** If \fIset\fP, Mutt-ng will automatically encode PGP/MIME signed messages as
2078 ** \fTquoted-printable\fP. Please note that unsetting this variable may
2079 ** lead to problems with non-verifyable PGP signatures, so only change
2080 ** this if you know what you are doing.
2083 {"pgp_timeout", DT_NUM, R_NONE, UL &PgpTimeout, "300" },
2086 ** The number of seconds after which a cached passphrase will expire if
2087 ** not used. Default: 300.
2090 {"pgp_sort_keys", DT_SORT|DT_SORT_KEYS, R_NONE, UL &PgpSortKeys, "address" },
2093 ** Specifies how the entries in the ``pgp keys'' menu are sorted. The
2094 ** following are legal values:
2097 ** .dt address .dd sort alphabetically by user id
2098 ** .dt keyid .dd sort alphabetically by key id
2099 ** .dt date .dd sort by key creation date
2100 ** .dt trust .dd sort by the trust of the key
2103 ** If you prefer reverse order of the above values, prefix it with
2107 {"pgp_mime_auto", DT_QUAD, R_NONE, OPT_PGPMIMEAUTO, "ask-yes" },
2110 ** This option controls whether Mutt-ng will prompt you for
2111 ** automatically sending a (signed/encrypted) message using
2112 ** PGP/MIME when inline (traditional) fails (for any reason).
2114 ** Also note that using the old-style PGP message format is \fBstrongly\fP
2115 ** \fBdeprecated\fP.
2118 {"pgp_auto_decode", DT_BOOL, R_NONE, OPTPGPAUTODEC, "no" },
2121 ** If \fIset\fP, Mutt-ng will automatically attempt to decrypt traditional PGP
2122 ** messages whenever the user performs an operation which ordinarily would
2123 ** result in the contents of the message being operated on. For example,
2124 ** if the user displays a pgp-traditional message which has not been manually
2125 ** checked with the check-traditional-pgp function, Mutt-ng will automatically
2126 ** check the message for traditional pgp.
2129 /* XXX Default values! */
2131 {"pgp_decode_command", DT_STR, R_NONE, UL &PgpDecodeCommand, "" },
2134 ** This format strings specifies a command which is used to decode
2135 ** application/pgp attachments.
2137 ** The PGP command formats have their own set of \fTprintf(3)\fP-like sequences:
2140 ** .dt %p .dd Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
2141 ** string otherwise. Note: This may be used with a %? construct.
2142 ** .dt %f .dd Expands to the name of a file containing a message.
2143 ** .dt %s .dd Expands to the name of a file containing the signature part
2144 ** . of a multipart/signed attachment when verifying it.
2145 ** .dt %a .dd The value of $$pgp_sign_as.
2146 ** .dt %r .dd One or more key IDs.
2149 ** For examples on how to configure these formats for the various versions
2150 ** of PGP which are floating around, see the pgp*.rc and gpg.rc files in
2151 ** the \fTsamples/\fP subdirectory which has been installed on your system
2152 ** alongside the documentation.
2155 {"pgp_getkeys_command", DT_STR, R_NONE, UL &PgpGetkeysCommand, "" },
2158 ** This command is invoked whenever Mutt-ng will need public key information.
2159 ** \fT%r\fP is the only \fTprintf(3)\fP-like sequence used with this format.
2162 {"pgp_verify_command", DT_STR, R_NONE, UL &PgpVerifyCommand, "" },
2165 ** This command is used to verify PGP signatures.
2168 {"pgp_decrypt_command", DT_STR, R_NONE, UL &PgpDecryptCommand, "" },
2171 ** This command is used to decrypt a PGP encrypted message.
2174 {"pgp_clearsign_command", DT_STR, R_NONE, UL &PgpClearSignCommand, "" },
2177 ** This format is used to create a old-style ``clearsigned'' PGP message.
2179 ** Note that the use of this format is \fBstrongly\fP \fBdeprecated\fP.
2182 {"pgp_sign_command", DT_STR, R_NONE, UL &PgpSignCommand, "" },
2185 ** This command is used to create the detached PGP signature for a
2186 ** multipart/signed PGP/MIME body part.
2189 {"pgp_encrypt_sign_command", DT_STR, R_NONE, UL &PgpEncryptSignCommand, "" },
2192 ** This command is used to both sign and encrypt a body part.
2195 {"pgp_encrypt_only_command", DT_STR, R_NONE, UL &PgpEncryptOnlyCommand, "" },
2198 ** This command is used to encrypt a body part without signing it.
2201 {"pgp_import_command", DT_STR, R_NONE, UL &PgpImportCommand, "" },
2204 ** This command is used to import a key from a message into
2205 ** the user's public key ring.
2208 {"pgp_export_command", DT_STR, R_NONE, UL &PgpExportCommand, "" },
2211 ** This command is used to export a public key from the user's
2215 {"pgp_verify_key_command", DT_STR, R_NONE, UL &PgpVerifyKeyCommand, "" },
2218 ** This command is used to verify key information from the key selection
2222 {"pgp_list_secring_command", DT_STR, R_NONE, UL &PgpListSecringCommand, "" },
2225 ** This command is used to list the secret key ring's contents. The
2226 ** output format must be analogous to the one used by
2227 ** \fTgpg --list-keys --with-colons\fP.
2229 ** This format is also generated by the \fTpgpring\fP utility which comes
2233 {"pgp_list_pubring_command", DT_STR, R_NONE, UL &PgpListPubringCommand, "" },
2236 ** This command is used to list the public key ring's contents. The
2237 ** output format must be analogous to the one used by
2238 ** \fTgpg --list-keys --with-colons\fP.
2240 ** This format is also generated by the \fTpgpring\fP utility which comes
2244 {"forward_decrypt", DT_BOOL, R_NONE, OPTFORWDECRYPT, "yes" },
2247 ** Controls the handling of encrypted messages when forwarding a message.
2248 ** When \fIset\fP, the outer layer of encryption is stripped off. This
2249 ** variable is only used if ``$$mime_forward'' is \fIset\fP and
2250 ** ``$$mime_forward_decode'' is \fIunset\fP.
2253 {"smime_timeout", DT_NUM, R_NONE, UL &SmimeTimeout, "300" },
2256 ** The number of seconds after which a cached passphrase will expire if
2260 {"smime_encrypt_with", DT_STR, R_NONE, UL &SmimeCryptAlg, "" },
2263 ** This sets the algorithm that should be used for encryption.
2264 ** Valid choices are ``\fTdes\fP'', ``\fTdes3\fP'', ``\fTrc2-40\fP'',
2265 ** ``\fTrc2-64\fP'', ``\frc2-128\fP''.
2267 ** If \fIunset\fP ``\fI3des\fP'' (TripleDES) is used.
2270 {"smime_keys", DT_PATH, R_NONE, UL &SmimeKeys, "" },
2273 ** Since there is no pubring/secring as with PGP, Mutt-ng has to handle
2274 ** storage ad retrieval of keys/certs by itself. This is very basic right now,
2275 ** and stores keys and certificates in two different directories, both
2276 ** named as the hash-value retrieved from OpenSSL. There is an index file
2277 ** which contains mailbox-address keyid pair, and which can be manually
2278 ** edited. This one points to the location of the private keys.
2281 {"smime_ca_location", DT_PATH, R_NONE, UL &SmimeCALocation, "" },
2284 ** This variable contains the name of either a directory, or a file which
2285 ** contains trusted certificates for use with OpenSSL.
2288 {"smime_certificates", DT_PATH, R_NONE, UL &SmimeCertificates, "" },
2291 ** Since there is no pubring/secring as with PGP, Mutt-ng has to handle
2292 ** storage and retrieval of keys by itself. This is very basic right
2293 ** now, and keys and certificates are stored in two different
2294 ** directories, both named as the hash-value retrieved from
2295 ** OpenSSL. There is an index file which contains mailbox-address
2296 ** keyid pairs, and which can be manually edited. This one points to
2297 ** the location of the certificates.
2300 {"smime_decrypt_command", DT_STR, R_NONE, UL &SmimeDecryptCommand, "" },
2303 ** This format string specifies a command which is used to decrypt
2304 ** \fTapplication/x-pkcs7-mime\fP attachments.
2306 ** The OpenSSL command formats have their own set of \fTprintf(3)\fP-like sequences
2307 ** similar to PGP's:
2310 ** .dt %f .dd Expands to the name of a file containing a message.
2311 ** .dt %s .dd Expands to the name of a file containing the signature part
2312 ** . of a multipart/signed attachment when verifying it.
2313 ** .dt %k .dd The key-pair specified with $$smime_default_key
2314 ** .dt %c .dd One or more certificate IDs.
2315 ** .dt %a .dd The algorithm used for encryption.
2316 ** .dt %C .dd CA location: Depending on whether $$smime_ca_location
2317 ** . points to a directory or file, this expands to
2318 ** . "-CApath $$smime_ca_location" or "-CAfile $$smime_ca_location".
2321 ** For examples on how to configure these formats, see the smime.rc in
2322 ** the \fTsamples/\fP subdirectory which has been installed on your system
2323 ** alongside the documentation.
2326 {"smime_verify_command", DT_STR, R_NONE, UL &SmimeVerifyCommand, "" },
2329 ** This command is used to verify S/MIME signatures of type \fTmultipart/signed\fP.
2332 {"smime_verify_opaque_command", DT_STR, R_NONE, UL &SmimeVerifyOpaqueCommand, "" },
2335 ** This command is used to verify S/MIME signatures of type
2336 ** \fTapplication/x-pkcs7-mime\fP.
2339 {"smime_sign_command", DT_STR, R_NONE, UL &SmimeSignCommand, "" },
2342 ** This command is used to created S/MIME signatures of type
2343 ** \fTmultipart/signed\fP, which can be read by all mail clients.
2346 {"smime_sign_opaque_command", DT_STR, R_NONE, UL &SmimeSignOpaqueCommand, "" },
2349 ** This command is used to created S/MIME signatures of type
2350 ** \fTapplication/x-pkcs7-signature\fP, which can only be handled by mail
2351 ** clients supporting the S/MIME extension.
2354 {"smime_encrypt_command", DT_STR, R_NONE, UL &SmimeEncryptCommand, "" },
2357 ** This command is used to create encrypted S/MIME messages.
2360 {"smime_pk7out_command", DT_STR, R_NONE, UL &SmimePk7outCommand, "" },
2363 ** This command is used to extract PKCS7 structures of S/MIME signatures,
2364 ** in order to extract the public X509 certificate(s).
2367 {"smime_get_cert_command", DT_STR, R_NONE, UL &SmimeGetCertCommand, "" },
2370 ** This command is used to extract X509 certificates from a PKCS7 structure.
2373 {"smime_get_signer_cert_command", DT_STR, R_NONE, UL &SmimeGetSignerCertCommand, "" },
2376 ** This command is used to extract only the signers X509 certificate from a S/MIME
2377 ** signature, so that the certificate's owner may get compared to the
2378 ** email's ``\fTFrom:\fP'' header field.
2381 {"smime_import_cert_command", DT_STR, R_NONE, UL &SmimeImportCertCommand, "" },
2384 ** This command is used to import a certificate via \fTsmime_keysng\fP.
2387 {"smime_get_cert_email_command", DT_STR, R_NONE, UL &SmimeGetCertEmailCommand, "" },
2390 ** This command is used to extract the mail address(es) used for storing
2391 ** X509 certificates, and for verification purposes (to check whether the
2392 ** certificate was issued for the sender's mailbox).
2395 {"smime_default_key", DT_STR, R_NONE, UL &SmimeDefaultKey, "" },
2398 ** This is the default key-pair to use for signing. This must be set to the
2399 ** keyid (the hash-value that OpenSSL generates) to work properly
2402 #if defined(USE_LIBESMTP)
2403 {"smtp_auth_username", DT_SYN, R_NONE, UL "smtp_user", 0},
2404 {"smtp_user", DT_STR, R_NONE, UL &SmtpAuthUser, "" },
2407 ** Availability: SMTP
2410 ** Defines the username to use with SMTP AUTH. Setting this variable will
2411 ** cause Mutt-ng to attempt to use SMTP AUTH when sending.
2413 {"smtp_auth_password", DT_SYN, R_NONE, UL "smtp_pass", 0},
2414 {"smtp_pass", DT_STR, R_NONE, UL &SmtpAuthPass, "" },
2417 ** Availability: SMTP
2420 ** Defines the password to use with SMTP AUTH. If ``$$smtp_user''
2421 ** is set, but this variable is not, you will be prompted for a password
2424 ** \fBNote:\fP Storing passwords in a configuration file
2425 ** presents a security risk since the superuser of your machine may read it
2426 ** regardless of the file's permissions.
2428 {"smtp_envelope", DT_STR, R_NONE, UL &SmtpEnvFrom, "" },
2431 ** Availability: SMTP
2434 ** If this variable is non-empty, it'll be used as the envelope sender. If it's empty
2435 ** (the default), the value of the regular \fTFrom:\fP header will be used.
2438 ** This may be necessary as some providers don't allow for arbitrary values
2439 ** as the envelope sender but only a particular one which may not be the same as the
2440 ** user's desired \fTFrom:\fP header.
2442 {"smtp_host", DT_STR, R_NONE, UL &SmtpHost, "" },
2445 ** Availability: SMTP
2448 ** Defines the SMTP host which will be used to deliver mail, as opposed
2449 ** to invoking the sendmail binary. Setting this variable overrides the
2450 ** value of ``$$sendmail'', and any associated variables.
2452 {"smtp_port", DT_NUM, R_NONE, UL &SmtpPort, "25" },
2455 ** Availability: SMTP
2458 ** Defines the port that the SMTP host is listening on for mail delivery.
2459 ** Must be specified as a number.
2461 ** Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP
2462 ** servers will probably desire 587, the mail submission port.
2464 {"smtp_use_tls", DT_STR, R_NONE, UL &SmtpUseTLS, "" },
2467 ** Availability: SMTP (and SSL)
2470 ** Defines wether to use STARTTLS. If this option is set to ``\fIrequired\fP''
2471 ** and the server does not support STARTTLS or there is an error in the
2472 ** TLS Handshake, the connection will fail. Setting this to ``\fIenabled\fP''
2473 ** will try to start TLS and continue without TLS in case of an error.
2476 ** Muttng still needs to have SSL support enabled in order to use it.
2479 #if defined(USE_SSL) || defined(USE_GNUTLS)
2481 {"ssl_client_cert", DT_PATH, R_NONE, UL &SslClientCert, "" },
2484 ** Availability: SSL
2487 ** The file containing a client certificate and its associated private
2490 #endif /* USE_SSL */
2491 {"ssl_force_tls", DT_BOOL, R_NONE, OPTSSLFORCETLS, "no" },
2494 ** If this variable is \fIset\fP, mutt-ng will require that all connections
2495 ** to remote servers be encrypted. Furthermore it will attempt to
2496 ** negotiate TLS even if the server does not advertise the capability,
2497 ** since it would otherwise have to abort the connection anyway. This
2498 ** option supersedes ``$$ssl_starttls''.
2500 {"ssl_starttls", DT_QUAD, R_NONE, OPT_SSLSTARTTLS, "yes" },
2503 ** Availability: SSL or GNUTLS
2506 ** If \fIset\fP (the default), Mutt-ng will attempt to use STARTTLS on servers
2507 ** advertising the capability. When \fIunset\fP, Mutt-ng will not attempt to
2508 ** use STARTTLS regardless of the server's capabilities.
2510 {"certificate_file", DT_PATH, R_NONE, UL &SslCertFile, "~/.mutt_certificates"},
2513 ** Availability: SSL or GNUTLS
2516 ** This variable specifies the file where the certificates you trust
2517 ** are saved. When an unknown certificate is encountered, you are asked
2518 ** if you accept it or not. If you accept it, the certificate can also
2519 ** be saved in this file and further connections are automatically
2522 ** You can also manually add CA certificates in this file. Any server
2523 ** certificate that is signed with one of these CA certificates are
2524 ** also automatically accepted.
2526 ** Example: \fTset certificate_file=~/.muttng/certificates\fP
2528 # if defined(_MAKEDOC) || !defined (USE_GNUTLS)
2529 {"ssl_usesystemcerts", DT_BOOL, R_NONE, OPTSSLSYSTEMCERTS, "yes" },
2532 ** Availability: SSL
2535 ** If set to \fIyes\fP, Mutt-ng will use CA certificates in the
2536 ** system-wide certificate store when checking if server certificate
2537 ** is signed by a trusted CA.
2539 {"entropy_file", DT_PATH, R_NONE, UL &SslEntropyFile, "" },
2542 ** Availability: SSL
2545 ** The file which includes random data that is used to initialize SSL
2546 ** library functions.
2548 {"ssl_use_sslv2", DT_BOOL, R_NONE, OPTSSLV2, "yes" },
2551 ** Availability: SSL
2554 ** This variables specifies whether to attempt to use SSLv2 in the
2555 ** SSL authentication process.
2557 # endif /* _MAKEDOC || !USE_GNUTLS */
2558 {"ssl_use_sslv3", DT_BOOL, R_NONE, OPTSSLV3, "yes" },
2561 ** Availability: SSL or GNUTLS
2564 ** This variables specifies whether to attempt to use SSLv3 in the
2565 ** SSL authentication process.
2567 {"ssl_use_tlsv1", DT_BOOL, R_NONE, OPTTLSV1, "yes" },
2570 ** Availability: SSL or GNUTLS
2573 ** This variables specifies whether to attempt to use TLSv1 in the
2574 ** SSL authentication process.
2577 {"ssl_min_dh_prime_bits", DT_NUM, R_NONE, UL &SslDHPrimeBits, "0" },
2580 ** Availability: GNUTLS
2583 ** This variable specifies the minimum acceptable prime size (in bits)
2584 ** for use in any Diffie-Hellman key exchange. A value of 0 will use
2585 ** the default from the GNUTLS library.
2587 {"ssl_ca_certificates_file", DT_PATH, R_NONE, UL &SslCACertFile, "" },
2590 ** This variable specifies a file containing trusted CA certificates.
2591 ** Any server certificate that is signed with one of these CA
2592 ** certificates are also automatically accepted.
2594 ** Example: \fTset ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt\fP
2596 # endif /* USE_GNUTLS */
2597 # endif /* USE_SSL || USE_GNUTLS */
2598 {"pipe_split", DT_BOOL, R_NONE, OPTPIPESPLIT, "no" },
2601 ** Used in connection with the \fIpipe-message\fP command and the ``tag-
2602 ** prefix'' or ``tag-prefix-cond'' operators.
2603 ** If this variable is \fIunset\fP, when piping a list of
2604 ** tagged messages Mutt-ng will concatenate the messages and will pipe them
2605 ** as a single folder. When \fIset\fP, Mutt-ng will pipe the messages one by one.
2606 ** In both cases the messages are piped in the current sorted order,
2607 ** and the ``$$pipe_sep'' separator is added after each message.
2609 {"pipe_decode", DT_BOOL, R_NONE, OPTPIPEDECODE, "no" },
2612 ** Used in connection with the \fIpipe-message\fP command. When \fIunset\fP,
2613 ** Mutt-ng will pipe the messages without any preprocessing. When \fIset\fP, Mutt-ng
2614 ** will weed headers and will attempt to PGP/MIME decode the messages
2617 {"pipe_sep", DT_STR, R_NONE, UL &PipeSep, "\n"},
2620 ** The separator to add between messages when piping a list of tagged
2621 ** messages to an external Unix command.
2624 {"pop_authenticators", DT_STR, R_NONE, UL &PopAuthenticators, "" },
2627 ** Availability: POP
2630 ** This is a colon-delimited list of authentication methods Mutt-ng may
2631 ** attempt to use to log in to an POP server, in the order Mutt-ng should
2632 ** try them. Authentication methods are either ``\fTuser\fP'', ``\fTapop\fP''
2633 ** or any SASL mechanism, eg ``\fTdigest-md5\fP'', ``\fTgssapi\fP'' or ``\fTcram-md5\fP''.
2635 ** This parameter is case-insensitive. If this parameter is \fIunset\fP
2636 ** (the default) Mutt-ng will try all available methods, in order from
2637 ** most-secure to least-secure.
2639 ** Example: \fTset pop_authenticators="digest-md5:apop:user"\fP
2641 {"pop_auth_try_all", DT_BOOL, R_NONE, OPTPOPAUTHTRYALL, "yes" },
2644 ** Availability: POP
2647 ** If \fIset\fP, Mutt-ng will try all available methods. When \fIunset\fP, Mutt-ng will
2648 ** only fall back to other authentication methods if the previous
2649 ** methods are unavailable. If a method is available but authentication
2650 ** fails, Mutt-ng will not connect to the POP server.
2652 {"pop_checkinterval", DT_SYN, R_NONE, UL "pop_mail_check", 0},
2653 {"pop_mail_check", DT_NUM, R_NONE, UL &PopCheckTimeout, "60" },
2656 ** Availability: POP
2659 ** This variable configures how often (in seconds) POP should look for
2662 {"pop_delete", DT_QUAD, R_NONE, OPT_POPDELETE, "ask-no" },
2665 ** Availability: POP
2668 ** If \fIset\fP, Mutt-ng will delete successfully downloaded messages from the POP
2669 ** server when using the ``fetch-mail'' function. When \fIunset\fP, Mutt-ng will
2670 ** download messages but also leave them on the POP server.
2672 {"pop_host", DT_STR, R_NONE, UL &PopHost, ""},
2675 ** Availability: POP
2678 ** The name of your POP server for the ``fetch-mail'' function. You
2679 ** can also specify an alternative port, username and password, i.e.:
2681 ** \fT[pop[s]://][username[:password]@]popserver[:port]\fP
2683 ** \fBNote:\fP Storing passwords in a configuration file
2684 ** presents a security risk since the superuser of your machine may read it
2685 ** regardless of the file's permissions.
2687 {"pop_last", DT_BOOL, R_NONE, OPTPOPLAST, "no" },
2690 ** Availability: POP
2693 ** If this variable is \fIset\fP, Mutt-ng will try to use the ``\fTLAST\fP'' POP command
2694 ** for retrieving only unread messages from the POP server when using
2695 ** the ``fetch-mail'' function.
2697 {"pop_reconnect", DT_QUAD, R_NONE, OPT_POPRECONNECT, "ask-yes" },
2700 ** Availability: POP
2703 ** Controls whether or not Mutt-ng will try to reconnect to a POP server when the
2704 ** connection is lost.
2706 {"pop_user", DT_STR, R_NONE, UL &PopUser, "" },
2709 ** Availability: POP
2712 ** Your login name on the POP server.
2714 ** This variable defaults to your user name on the local machine.
2716 {"pop_pass", DT_STR, R_NONE, UL &PopPass, ""},
2719 ** Availability: POP
2722 ** Specifies the password for your POP account. If \fIunset\fP, Mutt-ng will
2723 ** prompt you for your password when you open POP mailbox.
2725 ** \fBNote:\fP Storing passwords in a configuration file
2726 ** presents a security risk since the superuser of your machine may read it
2727 ** regardless of the file's permissions.
2729 #endif /* USE_POP */
2730 {"post_indent_string", DT_STR, R_NONE, UL &PostIndentString, ""},
2733 ** Similar to the ``$$attribution'' variable, Mutt-ng will append this
2734 ** string after the inclusion of a message which is being replied to.
2737 {"post_moderated", DT_SYN, R_NONE, UL "nntp_post_moderated", 0 },
2738 {"nntp_post_moderated", DT_QUAD, R_NONE, OPT_TOMODERATED, "ask-yes" },
2741 ** Availability: NNTP
2744 ** If set to \fIyes\fP, Mutt-ng will post articles to newsgroup that have
2745 ** not permissions to post (e.g. moderated).
2747 ** \fBNote:\fP if the newsserver
2748 ** does not support posting to that newsgroup or a group is totally read-only, that
2749 ** posting will not have any effect.
2752 {"postpone", DT_QUAD, R_NONE, OPT_POSTPONE, "ask-yes" },
2755 ** Controls whether or not messages are saved in the ``$$postponed''
2756 ** mailbox when you elect not to send immediately.
2758 {"postponed", DT_PATH, R_NONE, UL &Postponed, "~/postponed"},
2761 ** Mutt-ng allows you to indefinitely ``$postpone sending a message'' which
2762 ** you are editing. When you choose to postpone a message, Mutt-ng saves it
2763 ** in the mailbox specified by this variable. Also see the ``$$postpone''
2767 {"preconnect", DT_STR, R_NONE, UL &Preconnect, "" },
2770 ** If \fIset\fP, a shell command to be executed if Mutt-ng fails to establish
2771 ** a connection to the server. This is useful for setting up secure
2772 ** connections, e.g. with \fTssh(1)\fP. If the command returns a nonzero
2773 ** status, Mutt-ng gives up opening the server. Example:
2775 ** \fTpreconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net
2776 ** sleep 20 < /dev/null > /dev/null"\fP
2778 ** Mailbox ``foo'' on mailhost.net can now be reached
2779 ** as ``{localhost:1234}foo''.
2781 ** \fBNote:\fP For this example to work, you must be able to log in to the
2782 ** remote machine without having to enter a password.
2784 #endif /* USE_SOCKET */
2785 {"print", DT_QUAD, R_NONE, OPT_PRINT, "ask-no" },
2788 ** Controls whether or not Mutt-ng really prints messages.
2789 ** This is set to \fIask-no\fP by default, because some people
2790 ** accidentally hit ``p'' often.
2792 {"print_command", DT_PATH, R_NONE, UL &PrintCmd, "lpr"},
2795 ** This specifies the command pipe that should be used to print messages.
2797 {"print_decode", DT_BOOL, R_NONE, OPTPRINTDECODE, "yes" },
2800 ** Used in connection with the print-message command. If this
2801 ** option is \fIset\fP, the message is decoded before it is passed to the
2802 ** external command specified by $$print_command. If this option
2803 ** is \fIunset\fP, no processing will be applied to the message when
2804 ** printing it. The latter setting may be useful if you are using
2805 ** some advanced printer filter which is able to properly format
2806 ** e-mail messages for printing.
2808 {"print_split", DT_BOOL, R_NONE, OPTPRINTSPLIT, "no" },
2811 ** Used in connection with the print-message command. If this option
2812 ** is \fIset\fP, the command specified by $$print_command is executed once for
2813 ** each message which is to be printed. If this option is \fIunset\fP,
2814 ** the command specified by $$print_command is executed only once, and
2815 ** all the messages are concatenated, with a form feed as the message
2818 ** Those who use the \fTenscript(1)\fP program's mail-printing mode will
2819 ** most likely want to set this option.
2821 {"prompt_after", DT_BOOL, R_NONE, OPTPROMPTAFTER, "yes" },
2824 ** If you use an \fIexternal\fP ``$$pager'', setting this variable will
2825 ** cause Mutt-ng to prompt you for a command when the pager exits rather
2826 ** than returning to the index menu. If \fIunset\fP, Mutt-ng will return to the
2827 ** index menu when the external pager exits.
2829 {"query_command", DT_PATH, R_NONE, UL &QueryCmd, ""},
2832 ** This specifies the command that Mutt-ng will use to make external address
2833 ** queries. The string should contain a \fT%s\fP, which will be substituted
2834 ** with the query string the user types. See ``$query'' for more
2837 {"quit", DT_QUAD, R_NONE, OPT_QUIT, "yes" },
2840 ** This variable controls whether ``quit'' and ``exit'' actually quit
2841 ** from Mutt-ng. If it set to \fIyes\fP, they do quit, if it is set to \fIno\fP, they
2842 ** have no effect, and if it is set to \fIask-yes\fP or \fIask-no\fP, you are
2843 ** prompted for confirmation when you try to quit.
2845 {"quote_empty", DT_BOOL, R_NONE, OPTQUOTEEMPTY, "yes" },
2848 ** Controls whether or not empty lines will be quoted using
2849 ** ``$indent_string''.
2851 {"quote_quoted", DT_BOOL, R_NONE, OPTQUOTEQUOTED, "no" },
2854 ** Controls how quoted lines will be quoted. If \fIset\fP, one quote
2855 ** character will be added to the end of existing prefix. Otherwise,
2856 ** quoted lines will be prepended by ``$indent_string''.
2858 {"quote_regexp", DT_RX, R_PAGER, UL &QuoteRegexp, "^([ \t]*[|>:}#])+"},
2861 ** A regular expression used in the internal-pager to determine quoted
2862 ** sections of text in the body of a message.
2864 ** \fBNote:\fP In order to use the \fIquoted\fP\fBx\fP patterns in the
2865 ** internal pager, you need to set this to a regular expression that
2866 ** matches \fIexactly\fP the quote characters at the beginning of quoted
2869 {"read_inc", DT_NUM, R_NONE, UL &ReadInc, "10" },
2872 ** If set to a value greater than 0, Mutt-ng will display which message it
2873 ** is currently on when reading a mailbox. The message is printed after
2874 ** \fIread_inc\fP messages have been read (e.g., if set to 25, Mutt-ng will
2875 ** print a message when it reads message 25, and then again when it gets
2876 ** to message 50). This variable is meant to indicate progress when
2877 ** reading large mailboxes which may take some time.
2878 ** When set to 0, only a single message will appear before the reading
2881 ** Also see the ``$$write_inc'' variable.
2883 {"read_only", DT_BOOL, R_NONE, OPTREADONLY, "no" },
2886 ** If set, all folders are opened in read-only mode.
2888 {"realname", DT_STR, R_BOTH, UL &Realname, "" },
2891 ** This variable specifies what ``real'' or ``personal'' name should be used
2892 ** when sending messages.
2894 ** By default, this is the GECOS field from \fT/etc/passwd\fP.
2897 ** variable will \fInot\fP be used when the user has set a real name
2898 ** in the $$from variable.
2900 {"recall", DT_QUAD, R_NONE, OPT_RECALL, "ask-yes" },
2903 ** Controls whether or not Mutt-ng recalls postponed messages
2904 ** when composing a new message. Also see ``$$postponed''.
2906 ** Setting this variable to \fIyes\fP is not generally useful, and thus not
2909 {"record", DT_PATH, R_NONE, UL &Outbox, ""},
2912 ** This specifies the file into which your outgoing messages should be
2913 ** appended. (This is meant as the primary method for saving a copy of
2914 ** your messages, but another way to do this is using the ``$my_hdr''
2915 ** command to create a \fTBcc:\fP header field with your email address in it.)
2917 ** The value of \fI$$record\fP is overridden by the ``$$force_name'' and
2918 ** ``$$save_name'' variables, and the ``$fcc-hook'' command.
2920 {"reply_regexp", DT_RX, R_INDEX|R_RESORT, UL &ReplyRegexp, "^(re([\\[0-9\\]+])*|aw):[ \t]*"},
2923 ** A regular expression used to recognize reply messages when threading
2924 ** and replying. The default value corresponds to the English ``Re:'' and
2925 ** the German ``Aw:''.
2927 {"reply_self", DT_BOOL, R_NONE, OPTREPLYSELF, "no" },
2930 ** If \fIunset\fP and you are replying to a message sent by you, Mutt-ng will
2931 ** assume that you want to reply to the recipients of that message rather
2932 ** than to yourself.
2934 {"reply_to", DT_QUAD, R_NONE, OPT_REPLYTO, "ask-yes" },
2937 ** If \fIset\fP, when replying to a message, Mutt-ng will use the address listed
2938 ** in the ``\fTReply-To:\fP'' header field as the recipient of the reply. If \fIunset\fP,
2939 ** it will use the address in the ``\fTFrom:\fP'' header field instead.
2942 ** option is useful for reading a mailing list that sets the ``\fTReply-To:\fP''
2943 ** header field to the list address and you want to send a private
2944 ** message to the author of a message.
2946 {"resolve", DT_BOOL, R_NONE, OPTRESOLVE, "yes" },
2949 ** When set, the cursor will be automatically advanced to the next
2950 ** (possibly undeleted) message whenever a command that modifies the
2951 ** current message is executed.
2953 {"reverse_alias", DT_BOOL, R_BOTH, OPTREVALIAS, "no" },
2956 ** This variable controls whether or not Mutt-ng will display the ``personal''
2957 ** name from your aliases in the index menu if it finds an alias that
2958 ** matches the message's sender. For example, if you have the following
2961 ** \fTalias juser abd30425@somewhere.net (Joe User)\fP
2963 ** and then you receive mail which contains the following header:
2965 ** \fTFrom: abd30425@somewhere.net\fP
2967 ** It would be displayed in the index menu as ``Joe User'' instead of
2968 ** ``abd30425@somewhere.net.'' This is useful when the person's e-mail
2969 ** address is not human friendly (like CompuServe addresses).
2971 {"reverse_name", DT_BOOL, R_BOTH, OPTREVNAME, "no" },
2974 ** It may sometimes arrive that you receive mail to a certain machine,
2975 ** move the messages to another machine, and reply to some the messages
2976 ** from there. If this variable is \fIset\fP, the default \fTFrom:\fP line of
2977 ** the reply messages is built using the address where you received the
2978 ** messages you are replying to \fBif\fP that address matches your
2979 ** alternates. If the variable is \fIunset\fP, or the address that would be
2980 ** used doesn't match your alternates, the \fTFrom:\fP line will use
2981 ** your address on the current machine.
2983 {"reverse_realname", DT_BOOL, R_BOTH, OPTREVREAL, "yes" },
2986 ** This variable fine-tunes the behaviour of the $reverse_name feature.
2987 ** When it is \fIset\fP, Mutt-ng will use the address from incoming messages as-is,
2988 ** possibly including eventual real names. When it is \fIunset\fP, Mutt-ng will
2989 ** override any such real names with the setting of the $realname variable.
2991 {"rfc2047_parameters", DT_BOOL, R_NONE, OPTRFC2047PARAMS, "no" },
2994 ** When this variable is \fIset\fP, Mutt-ng will decode RFC-2047-encoded MIME
2995 ** parameters. You want to set this variable when Mutt-ng suggests you
2996 ** to save attachments to files named like this:
2998 ** \fT=?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=\fP
3000 ** When this variable is \fIset\fP interactively, the change doesn't have
3001 ** the desired effect before you have changed folders.
3003 ** Note that this use of RFC 2047's encoding is explicitly,
3004 ** prohibited by the standard, but nevertheless encountered in the
3007 ** Also note that setting this parameter will \fInot\fP have the effect
3008 ** that Mutt-ng \fIgenerates\fP this kind of encoding. Instead, Mutt-ng will
3009 ** unconditionally use the encoding specified in RFC 2231.
3011 {"save_address", DT_BOOL, R_NONE, OPTSAVEADDRESS, "no" },
3014 ** If \fIset\fP, Mutt-ng will take the sender's full address when choosing a
3015 ** default folder for saving a mail. If ``$$save_name'' or ``$$force_name''
3016 ** is \fIset\fP too, the selection of the fcc folder will be changed as well.
3018 {"save_empty", DT_BOOL, R_NONE, OPTSAVEEMPTY, "yes" },
3021 ** When \fIunset\fP, mailboxes which contain no saved messages will be removed
3022 ** when closed (the exception is ``$$spoolfile'' which is never removed).
3023 ** If \fIset\fP, mailboxes are never removed.
3025 ** \fBNote:\fP This only applies to mbox and MMDF folders, Mutt-ng does not
3026 ** delete MH and Maildir directories.
3028 {"save_name", DT_BOOL, R_NONE, OPTSAVENAME, "no" },
3031 ** This variable controls how copies of outgoing messages are saved.
3032 ** When set, a check is made to see if a mailbox specified by the
3033 ** recipient address exists (this is done by searching for a mailbox in
3034 ** the ``$$folder'' directory with the \fIusername\fP part of the
3035 ** recipient address). If the mailbox exists, the outgoing message will
3036 ** be saved to that mailbox, otherwise the message is saved to the
3037 ** ``$$record'' mailbox.
3039 ** Also see the ``$$force_name'' variable.
3041 {"score", DT_BOOL, R_NONE, OPTSCORE, "yes" },
3044 ** When this variable is \fIunset\fP, scoring is turned off. This can
3045 ** be useful to selectively disable scoring for certain folders when the
3046 ** ``$$score_threshold_delete'' variable and friends are used.
3049 {"score_threshold_delete", DT_NUM, R_NONE, UL &ScoreThresholdDelete, "-1" },
3052 ** Messages which have been assigned a score equal to or lower than the value
3053 ** of this variable are automatically marked for deletion by Mutt-ng. Since
3054 ** Mutt-ng scores are always greater than or equal to zero, the default setting
3055 ** of this variable will never mark a message for deletion.
3057 {"score_threshold_flag", DT_NUM, R_NONE, UL &ScoreThresholdFlag, "9999" },
3060 ** Messages which have been assigned a score greater than or equal to this
3061 ** variable's value are automatically marked ``flagged''.
3063 {"score_threshold_read", DT_NUM, R_NONE, UL &ScoreThresholdRead, "-1" },
3066 ** Messages which have been assigned a score equal to or lower than the value
3067 ** of this variable are automatically marked as read by Mutt-ng. Since
3068 ** Mutt-ng scores are always greater than or equal to zero, the default setting
3069 ** of this variable will never mark a message read.
3071 {"send_charset", DT_STR, R_NONE, UL &SendCharset, "us-ascii:iso-8859-1:utf-8"},
3074 ** A list of character sets for outgoing messages. Mutt-ng will use the
3075 ** first character set into which the text can be converted exactly.
3076 ** If your ``$$charset'' is not \fTiso-8859-1\fP and recipients may not
3077 ** understand \fTUTF-8\fP, it is advisable to include in the list an
3078 ** appropriate widely used standard character set (such as
3079 ** \fTiso-8859-2\fP, \fTkoi8-r\fP or \fTiso-2022-jp\fP) either
3080 ** instead of or after \fTiso-8859-1\fP.
3082 {"sendmail", DT_PATH, R_NONE, UL &Sendmail, SENDMAIL " -oem -oi"},
3085 ** Specifies the program and arguments used to deliver mail sent by Mutt-ng.
3086 ** Mutt-ng expects that the specified program interprets additional
3087 ** arguments as recipient addresses.
3089 {"sendmail_wait", DT_NUM, R_NONE, UL &SendmailWait, "0" },
3092 ** Specifies the number of seconds to wait for the ``$$sendmail'' process
3093 ** to finish before giving up and putting delivery in the background.
3095 ** Mutt-ng interprets the value of this variable as follows:
3097 ** .dt >0 .dd number of seconds to wait for sendmail to finish before continuing
3098 ** .dt 0 .dd wait forever for sendmail to finish
3099 ** .dt <0 .dd always put sendmail in the background without waiting
3102 ** Note that if you specify a value other than 0, the output of the child
3103 ** process will be put in a temporary file. If there is some error, you
3104 ** will be informed as to where to find the output.
3106 {"shell", DT_PATH, R_NONE, UL &Shell, "" },
3109 ** Command to use when spawning a subshell. By default, the user's login
3110 ** shell from \fT/etc/passwd\fP is used.
3113 {"save_unsubscribed", DT_SYN, R_NONE, UL "nntp_save_unsubscribed", 0 },
3114 {"nntp_save_unsubscribed", DT_BOOL, R_NONE, OPTSAVEUNSUB, "no" },
3117 ** Availability: NNTP
3120 ** When \fIset\fP, info about unsubscribed newsgroups will be saved into the
3121 ** ``newsrc'' file and into the news cache.
3125 {"show_new_news", DT_SYN, R_NONE, UL "nntp_show_new_news", 0 },
3126 {"nntp_show_new_news", DT_BOOL, R_NONE, OPTSHOWNEWNEWS, "yes" },
3129 ** Availability: NNTP
3132 ** If \fIset\fP, the newsserver will be asked for new newsgroups on entering
3133 ** the browser. Otherwise, it will be done only once for a newsserver.
3134 ** Also controls whether or not the number of new articles of subscribed
3135 ** newsgroups will be checked.
3137 {"show_only_unread", DT_SYN, R_NONE, UL "nntp_show_only_unread", 0 },
3138 {"nntp_show_only_unread", DT_BOOL, R_NONE, OPTSHOWONLYUNREAD, "no" },
3141 ** Availability: NNTP
3144 ** If \fIset\fP, only subscribed newsgroups that contain unread articles
3145 ** will be displayed in the newsgroup browser.
3148 {"sig_dashes", DT_BOOL, R_NONE, OPTSIGDASHES, "yes" },
3151 ** If set, a line containing ``\fT-- \fP'' (dash, dash, space)
3152 ** will be inserted before your ``$$signature''. It is \fBstrongly\fP
3153 ** recommended that you not unset this variable unless your ``signature''
3154 ** contains just your name. The reason for this is because many software
3155 ** packages use ``\fT-- \n\fP'' to detect your signature.
3157 ** For example, Mutt-ng has the ability to highlight
3158 ** the signature in a different color in the builtin pager.
3160 {"sig_on_top", DT_BOOL, R_NONE, OPTSIGONTOP, "no" },
3163 ** If \fIset\fP, the signature will be included before any quoted or forwarded
3164 ** text. It is \fBstrongly\fP recommended that you do not set this variable
3165 ** unless you really know what you are doing, and are prepared to take
3166 ** some heat from netiquette guardians.
3168 {"signature", DT_PATH, R_NONE, UL &Signature, "~/.signature"},
3171 ** Specifies the filename of your signature, which is appended to all
3172 ** outgoing messages. If the filename ends with a pipe (``\fT|\fP''), it is
3173 ** assumed that filename is a shell command and input should be read from
3176 {"signoff_string", DT_STR, R_NONE, UL &SignOffString, "" },
3179 ** If \fIset\fP, this string will be inserted before the signature. This is useful
3180 ** for people that want to sign off every message they send with their name.
3182 ** If you want to insert your website's URL, additional contact information or
3183 ** witty quotes into your mails, better use a signature file instead of
3184 ** the signoff string.
3186 {"simple_search", DT_STR, R_NONE, UL &SimpleSearch, "~f %s | ~s %s"},
3189 ** Specifies how Mutt-ng should expand a simple search into a real search
3190 ** pattern. A simple search is one that does not contain any of the ~
3191 ** operators. See ``$patterns'' for more information on search patterns.
3193 ** For example, if you simply type ``joe'' at a search or limit prompt, Mutt-ng
3194 ** will automatically expand it to the value specified by this variable.
3195 ** For the default value it would be:
3197 ** \fT~f joe | ~s joe\fP
3199 {"smart_wrap", DT_BOOL, R_PAGER, OPTWRAP, "yes" },
3202 ** Controls the display of lines longer than the screen width in the
3203 ** internal pager. If \fIset\fP, long lines are wrapped at a word boundary.
3204 ** If \fIunset\fP, lines are simply wrapped at the screen edge. Also see the
3205 ** ``$$markers'' variable.
3207 {"smileys", DT_RX, R_PAGER, UL &Smileys, "(>From )|(:[-^]?[][)(><}{|/DP])"},
3210 ** The \fIpager\fP uses this variable to catch some common false
3211 ** positives of ``$$quote_regexp'', most notably smileys in the beginning
3214 {"sleep_time", DT_NUM, R_NONE, UL &SleepTime, "1" },
3217 ** Specifies time, in seconds, to pause while displaying certain informational
3218 ** messages, while moving from folder to folder and after expunging
3219 ** messages from the current folder. The default is to pause one second, so
3220 ** a value of zero for this option suppresses the pause.
3222 {"sort", DT_SORT, R_INDEX|R_RESORT, UL &Sort, "date" },
3225 ** Specifies how to sort messages in the \fIindex\fP menu. Valid values
3229 ** . date or date-sent
3232 ** . mailbox-order (unsorted)
3241 ** You may optionally use the ``reverse-'' prefix to specify reverse sorting
3242 ** order (example: \fTset sort=reverse-date-sent\fP).
3244 {"sort_alias", DT_SORT|DT_SORT_ALIAS, R_NONE, UL &SortAlias, "alias" },
3247 ** Specifies how the entries in the ``alias'' menu are sorted. The
3248 ** following are legal values:
3251 ** . address (sort alphabetically by email address)
3252 ** . alias (sort alphabetically by alias name)
3253 ** . unsorted (leave in order specified in .muttrc)
3256 {"sort_aux", DT_SORT|DT_SORT_AUX, R_INDEX|R_RESORT_BOTH, UL &SortAux, "date" },
3259 ** When sorting by threads, this variable controls how threads are sorted
3260 ** in relation to other threads, and how the branches of the thread trees
3261 ** are sorted. This can be set to any value that ``$$sort'' can, except
3262 ** threads (in that case, Mutt-ng will just use date-sent). You can also
3263 ** specify the ``last-'' prefix in addition to ``reverse-'' prefix, but last-
3264 ** must come after reverse-. The last- prefix causes messages to be
3265 ** sorted against its siblings by which has the last descendant, using
3266 ** the rest of sort_aux as an ordering.
3268 ** For instance, \fTset sort_aux=last-date-received\fP would mean that if
3269 ** a new message is received in a thread, that thread becomes the last one
3270 ** displayed (or the first, if you have \fTset sort=reverse-threads\fP.)
3272 ** \fBNote:\fP For reversed ``$$sort'' order $$sort_aux is reversed again
3273 ** (which is not the right thing to do, but kept to not break any existing
3274 ** configuration setting).
3276 {"sort_browser", DT_SORT|DT_SORT_BROWSER, R_NONE, UL &BrowserSort, "alpha" },
3279 ** Specifies how to sort entries in the file browser. By default, the
3280 ** entries are sorted alphabetically. Valid values:
3283 ** . alpha (alphabetically)
3289 ** You may optionally use the ``reverse-'' prefix to specify reverse sorting
3290 ** order (example: \fTset sort_browser=reverse-date\fP).
3292 {"sort_re", DT_BOOL, R_INDEX|R_RESORT|R_RESORT_INIT, OPTSORTRE, "yes" },
3295 ** This variable is only useful when sorting by threads with
3296 ** ``$$strict_threads'' \fIunset\fP. In that case, it changes the heuristic
3297 ** Mutt-ng uses to thread messages by subject. With $$sort_re \fIset\fP,
3298 ** Mutt-ng will only attach a message as the child of another message by
3299 ** subject if the subject of the child message starts with a substring
3300 ** matching the setting of ``$$reply_regexp''. With $$sort_re \fIunset\fP,
3301 ** Mutt-ng will attach the message whether or not this is the case,
3302 ** as long as the non-``$$reply_regexp'' parts of both messages are identical.
3304 {"spam_separator", DT_STR, R_NONE, UL &SpamSep, ","},
3307 ** ``$spam_separator'' controls what happens when multiple spam headers
3308 ** are matched: if \fIunset\fP, each successive header will overwrite any
3309 ** previous matches value for the spam label. If \fIset\fP, each successive
3310 ** match will append to the previous, using ``$spam_separator'' as a
3313 {"spoolfile", DT_PATH, R_NONE, UL &Spoolfile, "" },
3316 ** If your spool mailbox is in a non-default place where Mutt-ng cannot find
3317 ** it, you can specify its location with this variable. Mutt-ng will
3318 ** automatically set this variable to the value of the environment
3319 ** variable $$$MAIL if it is not set.
3321 {"status_chars", DT_STR, R_BOTH, UL &StChars, "-*%A"},
3324 ** Controls the characters used by the ``\fT%r\fP'' indicator in
3325 ** ``$$status_format''. The first character is used when the mailbox is
3326 ** unchanged. The second is used when the mailbox has been changed, and
3327 ** it needs to be resynchronized. The third is used if the mailbox is in
3328 ** read-only mode, or if the mailbox will not be written when exiting
3329 ** that mailbox (You can toggle whether to write changes to a mailbox
3330 ** with the toggle-write operation, bound by default to ``\fT%\fP'').
3331 ** The fourth is used to indicate that the current folder has been
3332 ** opened in attach-message mode (Certain operations like composing
3333 ** a new mail, replying, forwarding, etc. are not permitted in this mode).
3335 {"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)---"},
3338 ** Controls the format of the status line displayed in the \fIindex\fP
3339 ** menu. This string is similar to ``$$index_format'', but has its own
3340 ** set of \fTprintf(3)\fP-like sequences:
3343 ** .dt %b .dd number of mailboxes with new mail *
3344 ** .dt %B .dd the short pathname of the current mailbox
3345 ** .dt %d .dd number of deleted messages *
3346 ** .dt %f .dd the full pathname of the current mailbox
3347 ** .dt %F .dd number of flagged messages *
3348 ** .dt %h .dd local hostname
3349 ** .dt %l .dd size (in bytes) of the current mailbox *
3350 ** .dt %L .dd size (in bytes) of the messages shown
3351 ** (i.e., which match the current limit) *
3352 ** .dt %m .dd the number of messages in the mailbox *
3353 ** .dt %M .dd the number of messages shown (i.e., which match the current limit) *
3354 ** .dt %n .dd number of new messages in the mailbox *
3355 ** .dt %o .dd number of old unread messages *
3356 ** .dt %p .dd number of postponed messages *
3357 ** .dt %P .dd percentage of the way through the index
3358 ** .dt %r .dd modified/read-only/won't-write/attach-message indicator,
3359 ** according to $$status_chars
3360 ** .dt %s .dd current sorting mode ($$sort)
3361 ** .dt %S .dd current aux sorting method ($$sort_aux)
3362 ** .dt %t .dd number of tagged messages *
3363 ** .dt %u .dd number of unread messages *
3364 ** .dt %v .dd Mutt-ng version string
3365 ** .dt %V .dd currently active limit pattern, if any *
3366 ** .dt %>X .dd right justify the rest of the string and pad with "X"
3367 ** .dt %|X .dd pad to the end of the line with "X"
3370 ** * = can be optionally printed if nonzero
3372 ** Some of the above sequences can be used to optionally print a string
3373 ** if their value is nonzero. For example, you may only want to see the
3374 ** number of flagged messages if such messages exist, since zero is not
3375 ** particularly meaningful. To optionally print a string based upon one
3376 ** of the above sequences, the following construct is used
3378 ** \fT%?<sequence_char>?<optional_string>?\fP
3380 ** where \fIsequence_char\fP is a character from the table above, and
3381 ** \fIoptional_string\fP is the string you would like printed if
3382 ** \fIsequence_char\fP is nonzero. \fIoptional_string\fP \fBmay\fP contain
3383 ** other sequences as well as normal text, but you may \fBnot\fP nest
3384 ** optional strings.
3386 ** Here is an example illustrating how to optionally print the number of
3387 ** new messages in a mailbox:
3389 ** \fT%?n?%n new messages.?\fP
3391 ** Additionally you can switch between two strings, the first one, if a
3392 ** value is zero, the second one, if the value is nonzero, by using the
3393 ** following construct:
3395 ** \fT%?<sequence_char>?<if_string>&<else_string>?\fP
3397 ** You can additionally force the result of any \fTprintf(3)\fP-like sequence
3398 ** to be lowercase by prefixing the sequence character with an underscore
3399 ** (\fT_\fP) sign. For example, if you want to display the local hostname in
3400 ** lowercase, you would use:
3404 ** If you prefix the sequence character with a colon (\fT:\fP) character, Mutt-ng
3405 ** will replace any dots in the expansion by underscores. This might be helpful
3406 ** with IMAP folders that don't like dots in folder names.
3408 {"status_on_top", DT_BOOL, R_BOTH, OPTSTATUSONTOP, "no" },
3411 ** Setting this variable causes the ``status bar'' to be displayed on
3412 ** the first line of the screen rather than near the bottom.
3414 {"strict_mailto", DT_BOOL, R_NONE, OPTSTRICTMAILTO, "yes" },
3418 ** With mailto: style links, a body as well as arbitrary header information
3419 ** may be embedded. This may lead to (user) headers being overwriten without note
3420 ** if ``$$edit_headers'' is unset.
3423 ** If this variable is \fIset\fP, mutt-ng is strict and allows anything to be
3424 ** changed. If it's \fIunset\fP, all headers given will be prefixed with
3425 ** ``X-Mailto-'' and the message including headers will be shown in the editor
3426 ** regardless of what ``$$edit_headers'' is set to.
3428 {"strict_mime", DT_BOOL, R_NONE, OPTSTRICTMIME, "yes" },
3431 ** When \fIunset\fP, non MIME-compliant messages that doesn't have any
3432 ** charset indication in the ``\fTContent-Type:\fP'' header field can
3433 ** be displayed (non MIME-compliant messages are often generated by old
3434 ** mailers or buggy mailers like MS Outlook Express).
3435 ** See also $$assumed_charset.
3437 ** This option also replaces linear-white-space between encoded-word
3438 ** and *text to a single space to prevent the display of MIME-encoded
3439 ** ``\fTSubject:\fP'' header field from being devided into multiple lines.
3441 {"strict_threads", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTSTRICTTHREADS, "no" },
3444 ** If \fIset\fP, threading will only make use of the ``\fTIn-Reply-To:\fP'' and
3445 ** ``\fTReferences:\fP'' header fields when you ``$$sort'' by message threads. By
3446 ** default, messages with the same subject are grouped together in
3447 ** ``pseudo threads.'' This may not always be desirable, such as in a
3448 ** personal mailbox where you might have several unrelated messages with
3449 ** the subject ``hi'' which will get grouped together.
3451 {"strip_was", DT_BOOL, R_NONE, OPTSTRIPWAS, "no" },
3454 ** When \fIset\fP, mutt-ng will remove the trailing part of the ``\fTSubject:\fP''
3455 ** line which matches $$strip_was_regex when replying. This is useful to
3456 ** properly react on subject changes and reduce ``subject noise.'' (esp. in Usenet)
3458 {"strip_was_regex", DT_RX, R_NONE, UL &StripWasRegexp, "\\([Ww][Aa][RrSs]: .*\\)[ ]*$"},
3461 ** When non-empty and $$strip_was is \fIset\fP, mutt-ng will remove this
3462 ** trailing part of the ``Subject'' line when replying if it won't be empty
3465 {"stuff_quoted", DT_BOOL, R_BOTH, OPTSTUFFQUOTED, "no" },
3468 ** If \fIset\fP, attachments with flowed format will have their quoting ``stuffed'',
3469 ** i.e. a space will be inserted between the quote characters and the actual
3472 {"suspend", DT_BOOL, R_NONE, OPTSUSPEND, "yes" },
3475 ** When \fIunset\fP, Mutt-ng won't stop when the user presses the terminal's
3476 ** \fIsusp\fP key, usually \fTCTRL+Z\fP. This is useful if you run Mutt-ng
3477 ** inside an xterm using a command like ``\fTxterm -e muttng\fP.''
3479 {"text_flowed", DT_BOOL, R_NONE, OPTTEXTFLOWED, "no" },
3482 ** When \fIset\fP, Mutt-ng will generate \fTtext/plain; format=flowed\fP attachments.
3483 ** This format is easier to handle for some mailing software, and generally
3484 ** just looks like ordinary text. To actually make use of this format's
3485 ** features, you'll need support in your editor.
3487 ** Note that $$indent_string is ignored when this option is set.
3489 {"thread_received", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTTHREADRECEIVED, "no" },
3492 ** When \fIset\fP, Mutt-ng uses the date received rather than the date sent
3493 ** to thread messages by subject.
3495 {"thorough_search", DT_BOOL, R_NONE, OPTTHOROUGHSRC, "no" },
3498 ** Affects the \fT~b\fP and \fT~h\fP search operations described in
3499 ** section ``$patterns'' above. If \fIset\fP, the headers and attachments of
3500 ** messages to be searched are decoded before searching. If \fIunset\fP,
3501 ** messages are searched as they appear in the folder.
3503 {"tilde", DT_BOOL, R_PAGER, OPTTILDE, "no" },
3506 ** When \fIset\fP, the internal-pager will pad blank lines to the bottom of the
3507 ** screen with a tilde (~).
3509 {"timeout", DT_NUM, R_NONE, UL &Timeout, "600" },
3512 ** This variable controls the \fInumber of seconds\fP Mutt-ng will wait
3513 ** for a key to be pressed in the main menu before timing out and
3514 ** checking for new mail. A value of zero or less will cause Mutt-ng
3515 ** to never time out.
3517 {"tmpdir", DT_PATH, R_NONE, UL &Tempdir, "" },
3520 ** This variable allows you to specify where Mutt-ng will place its
3521 ** temporary files needed for displaying and composing messages. If
3522 ** this variable is not set, the environment variable \fT$$$TMPDIR\fP is
3523 ** used. If \fT$$$TMPDIR\fP is not set then "\fT/tmp\fP" is used.
3525 {"to_chars", DT_STR, R_BOTH, UL &Tochars, " +TCFL"},
3528 ** Controls the character used to indicate mail addressed to you. The
3529 ** first character is the one used when the mail is NOT addressed to your
3530 ** address (default: space). The second is used when you are the only
3531 ** recipient of the message (default: +). The third is when your address
3532 ** appears in the ``\fTTo:\fP'' header field, but you are not the only recipient of
3533 ** the message (default: T). The fourth character is used when your
3534 ** address is specified in the ``\fTCc:\fP'' header field, but you are not the only
3535 ** recipient. The fifth character is used to indicate mail that was sent
3536 ** by \fIyou\fP. The sixth character is used to indicate when a mail
3537 ** was sent to a mailing-list you're subscribe to (default: L).
3539 {"trash", DT_PATH, R_NONE, UL &TrashPath, "" },
3542 ** If \fIset\fP, this variable specifies the path of the trash folder where the
3543 ** mails marked for deletion will be moved, instead of being irremediably
3546 ** \fBNote\fP: When you delete a message in the trash folder, it is really
3547 ** deleted, so that there is no way to recover mail.
3550 {"tunnel", DT_STR, R_NONE, UL &Tunnel, "" },
3553 ** Setting this variable will cause Mutt-ng to open a pipe to a command
3554 ** instead of a raw socket. You may be able to use this to set up
3555 ** preauthenticated connections to your IMAP/POP3 server. Example:
3557 ** \fTtunnel="ssh -q mailhost.net /usr/local/libexec/imapd"\fP
3559 ** \fBNote:\fP For this example to work you must be able to log in to the remote
3560 ** machine without having to enter a password.
3563 {"umask", DT_NUM, R_NONE, UL &Umask, "0077" },
3566 ** This sets the umask that will be used by Mutt-ng when creating all
3567 ** kinds of files. If \fIunset\fP, the default value is \fT077\fP.
3569 {"use_8bitmime", DT_BOOL, R_NONE, OPTUSE8BITMIME, "no" },
3572 ** \fBWarning:\fP do not set this variable unless you are using a version
3573 ** of sendmail which supports the \fT-B8BITMIME\fP flag (such as sendmail
3574 ** 8.8.x) or in connection with the SMTP support via libESMTP.
3575 ** Otherwise you may not be able to send mail.
3577 ** When \fIset\fP, Mutt-ng will either invoke ``$$sendmail'' with the \fT-B8BITMIME\fP
3578 ** flag when sending 8-bit messages to enable ESMTP negotiation or tell
3579 ** libESMTP to do so.
3581 {"use_domain", DT_BOOL, R_NONE, OPTUSEDOMAIN, "yes" },
3584 ** When \fIset\fP, Mutt-ng will qualify all local addresses (ones without the
3585 ** @host portion) with the value of ``$$hostname''. If \fIunset\fP, no
3586 ** addresses will be qualified.
3588 {"use_from", DT_BOOL, R_NONE, OPTUSEFROM, "yes" },
3591 ** When \fIset\fP, Mutt-ng will generate the ``\fTFrom:\fP'' header field when
3592 ** sending messages. If \fIunset\fP, no ``\fTFrom:\fP'' header field will be
3593 ** generated unless the user explicitly sets one using the ``$my_hdr''
3597 {"use_idn", DT_BOOL, R_BOTH, OPTUSEIDN, "yes" },
3600 ** Availability: IDN
3603 ** When \fIset\fP, Mutt-ng will show you international domain names decoded.
3605 ** \fBNote:\fP You can use IDNs for addresses even if this is \fIunset\fP.
3606 ** This variable only affects decoding.
3608 #endif /* HAVE_LIBIDN */
3609 #ifdef HAVE_GETADDRINFO
3610 {"use_ipv6", DT_BOOL, R_NONE, OPTUSEIPV6, "yes" },
3613 ** When \fIset\fP, Mutt-ng will look for IPv6 addresses of hosts it tries to
3614 ** contact. If this option is \fIunset\fP, Mutt-ng will restrict itself to IPv4 addresses.
3615 ** Normally, the default should work.
3617 #endif /* HAVE_GETADDRINFO */
3618 {"user_agent", DT_SYN, R_NONE, UL "agent_string", 0 },
3619 {"agent_string", DT_BOOL, R_NONE, OPTXMAILER, "yes" },
3622 ** When \fIset\fP, Mutt-ng will add a ``\fTUser-Agent:\fP'' header to outgoing
3623 ** messages, indicating which version of Mutt-ng was used for composing
3626 {"visual", DT_PATH, R_NONE, UL &Visual, "" },
3629 ** Specifies the visual editor to invoke when the \fI~v\fP command is
3630 ** given in the builtin editor.
3632 {"wait_key", DT_BOOL, R_NONE, OPTWAITKEY, "yes" },
3635 ** Controls whether Mutt-ng will ask you to press a key after \fIshell-
3636 ** escape\fP, \fIpipe-message\fP, \fIpipe-entry\fP, \fIprint-message\fP,
3637 ** and \fIprint-entry\fP commands.
3639 ** It is also used when viewing attachments with ``$auto_view'', provided
3640 ** that the corresponding mailcap entry has a \fTneedsterminal\fP flag,
3641 ** and the external program is interactive.
3643 ** When \fIset\fP, Mutt-ng will always ask for a key. When \fIunset\fP, Mutt-ng will wait
3644 ** for a key only if the external command returned a non-zero status.
3646 {"weed", DT_BOOL, R_NONE, OPTWEED, "yes" },
3649 ** When \fIset\fP, Mutt-ng will weed headers when displaying, forwarding,
3650 ** printing, or replying to messages.
3652 {"wrap_search", DT_BOOL, R_NONE, OPTWRAPSEARCH, "yes" },
3655 ** Controls whether searches wrap around the end of the mailbox.
3657 ** When \fIset\fP, searches will wrap around the first (or last) message. When
3658 ** \fIunset\fP, searches will not wrap.
3660 {"wrapmargin", DT_NUM, R_PAGER, UL &WrapMargin, "0" },
3663 ** Controls the size of the margin remaining at the right side of
3664 ** the terminal when Mutt-ng's pager does smart wrapping.
3666 {"write_inc", DT_NUM, R_NONE, UL &WriteInc, "10" },
3669 ** When writing a mailbox, a message will be printed every
3670 ** \fIwrite_inc\fP messages to indicate progress. If set to 0, only a
3671 ** single message will be displayed before writing a mailbox.
3673 ** Also see the ``$$read_inc'' variable.
3675 {"write_bcc", DT_BOOL, R_NONE, OPTWRITEBCC, "yes" },
3678 ** Controls whether Mutt-ng writes out the Bcc header when preparing
3679 ** messages to be sent. Exim users may wish to \fIunset\fP this.
3681 {"xterm_icon", DT_STR, R_BOTH, UL &XtermIcon, "M%?n?AIL&ail?"},
3684 ** Controls the format of the X11 icon title, as long as $$xterm_set_titles
3685 ** is \fIset\fP. This string is identical in formatting to the one used by
3686 ** ``$$status_format''.
3688 {"xterm_set_titles", DT_BOOL, R_BOTH, OPTXTERMSETTITLES, "no" },
3691 ** Controls whether Mutt-ng sets the xterm title bar and icon name
3692 ** (as long as you're in an appropriate terminal). The default must
3693 ** be \fIunset\fP to force in the validity checking.
3695 {"xterm_leave", DT_STR, R_BOTH, UL &XtermLeave, "" },
3698 ** If $$xterm_set_titles is \fIset\fP, this string will be used to
3699 ** set the title when leaving mutt-ng. For terminal-based programs,
3700 ** there's no easy and portable way to read the current title so mutt-ng
3701 ** cannot read it upon startup and restore it when exiting.
3704 ** Based on the xterm FAQ, the following might work:
3707 ** \fTset xterm_leave = "`test x$$$DISPLAY != x && xprop -id $$$WINDOWID | grep WM_NAME | cut -d '"' -f 2`"\fP
3709 {"xterm_title", DT_STR, R_BOTH, UL &XtermTitle, "Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?"},
3712 ** Controls the format of the title bar of the xterm provided that
3713 ** $$xterm_set_titles has been \fIset\fP. This string is identical in formatting
3714 ** to the one used by ``$$status_format''.
3717 {"x_comment_to", DT_SYN, R_NONE, UL "nntp_x_comment_to", 0},
3718 {"nntp_x_comment_to", DT_BOOL, R_NONE, OPTXCOMMENTTO, "no" },
3721 ** Availability: NNTP
3724 ** If \fIset\fP, Mutt-ng will add a ``\fTX-Comment-To:\fP'' header field
3725 ** (that contains full name of the original article author) to articles that
3733 const struct feature_t Features[] = {
3735 #ifdef NCURSES_VERSION
3741 #ifdef USE_SLANG_CURSES
3747 #ifdef _LIBICONV_VERSION
3765 #ifdef DL_STANDALONE
3819 #ifdef USE_COMPRESSED
3831 #ifdef CRYPT_BACKEND_CLASSIC_PGP
3836 }, {"classic_smime",
3837 #ifdef CRYPT_BACKEND_CLASSIC_SMIME
3843 #ifdef CRYPT_BACKEND_GPGME
3877 const struct mapping_t SortMethods[] = {
3878 {"date", SORT_DATE},
3879 {"date-sent", SORT_DATE},
3880 {"date-received", SORT_RECEIVED},
3881 {"mailbox-order", SORT_ORDER},
3882 {"subject", SORT_SUBJECT},
3883 {"from", SORT_FROM},
3884 {"size", SORT_SIZE},
3885 {"threads", SORT_THREADS},
3887 {"score", SORT_SCORE},
3888 {"spam", SORT_SPAM},
3892 /* same as SortMethods, but with "threads" replaced by "date" */
3894 const struct mapping_t SortAuxMethods[] = {
3895 {"date", SORT_DATE},
3896 {"date-sent", SORT_DATE},
3897 {"date-received", SORT_RECEIVED},
3898 {"mailbox-order", SORT_ORDER},
3899 {"subject", SORT_SUBJECT},
3900 {"from", SORT_FROM},
3901 {"size", SORT_SIZE},
3902 {"threads", SORT_DATE}, /* note: sort_aux == threads
3906 {"score", SORT_SCORE},
3907 {"spam", SORT_SPAM},
3912 const struct mapping_t SortBrowserMethods[] = {
3913 {"alpha", SORT_SUBJECT},
3914 {"date", SORT_DATE},
3915 {"size", SORT_SIZE},
3916 {"unsorted", SORT_ORDER},
3920 const struct mapping_t SortAliasMethods[] = {
3921 {"alias", SORT_ALIAS},
3922 {"address", SORT_ADDRESS},
3923 {"unsorted", SORT_ORDER},
3927 const struct mapping_t SortKeyMethods[] = {
3928 {"address", SORT_ADDRESS},
3929 {"date", SORT_DATE},
3930 {"keyid", SORT_KEYID},
3931 {"trust", SORT_TRUST},
3936 /* functions used to parse commands in a rc file */
3938 static int parse_list (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3939 static int parse_spam_list (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3940 static int parse_unlist (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3942 static int parse_lists (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3943 static int parse_unlists (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3944 static int parse_alias (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3945 static int parse_unalias (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3946 static int parse_ifdef (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3947 static int parse_ignore (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3948 static int parse_unignore (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3949 static int parse_source (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3950 static int parse_set (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3951 static int parse_my_hdr (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3952 static int parse_unmy_hdr (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3953 static int parse_subscribe (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3954 static int parse_unsubscribe (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3956 static int parse_alternates (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3957 static int parse_unalternates (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3961 int (*func) (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3963 unsigned long data1;
3966 struct command_t Commands[] = {
3967 {"alternates", parse_alternates, 0},
3968 {"unalternates", parse_unalternates, 0},
3970 {"account-hook", mutt_parse_hook, M_ACCOUNTHOOK},
3972 {"alias", parse_alias, 0},
3973 {"auto_view", parse_list, UL &AutoViewList},
3974 {"alternative_order", parse_list, UL &AlternativeOrderList},
3975 {"bind", mutt_parse_bind, 0},
3976 {"charset-hook", mutt_parse_hook, M_CHARSETHOOK},
3978 {"color", mutt_parse_color, 0},
3979 {"uncolor", mutt_parse_uncolor, 0},
3981 {"exec", mutt_parse_exec, 0},
3982 {"fcc-hook", mutt_parse_hook, M_FCCHOOK},
3983 {"fcc-save-hook", mutt_parse_hook, M_FCCHOOK|M_SAVEHOOK},
3984 {"folder-hook", mutt_parse_hook, M_FOLDERHOOK},
3985 #ifdef USE_COMPRESSED
3986 {"open-hook", mutt_parse_hook, M_OPENHOOK},
3987 {"close-hook", mutt_parse_hook, M_CLOSEHOOK},
3988 {"append-hook", mutt_parse_hook, M_APPENDHOOK},
3990 {"hdr_order", parse_list, UL &HeaderOrderList},
3991 {"ifdef", parse_ifdef, 1},
3992 {"ifndef", parse_ifdef, 0},
3994 {"iconv-hook", mutt_parse_hook, M_ICONVHOOK},
3996 {"ignore", parse_ignore, 0},
3997 {"lists", parse_lists, 0},
3998 {"macro", mutt_parse_macro, 0},
3999 {"mailboxes", buffy_parse_mailboxes, M_MAILBOXES},
4000 {"unmailboxes", buffy_parse_mailboxes, M_UNMAILBOXES},
4001 {"message-hook", mutt_parse_hook, M_MESSAGEHOOK},
4002 {"mbox-hook", mutt_parse_hook, M_MBOXHOOK},
4003 {"mime_lookup", parse_list, UL &MimeLookupList},
4004 {"unmime_lookup", parse_unlist, UL &MimeLookupList},
4005 {"mono", mutt_parse_mono, 0},
4006 {"my_hdr", parse_my_hdr, 0},
4007 {"pgp-hook", mutt_parse_hook, M_CRYPTHOOK},
4008 {"crypt-hook", mutt_parse_hook, M_CRYPTHOOK},
4009 {"push", mutt_parse_push, 0},
4010 {"reply-hook", mutt_parse_hook, M_REPLYHOOK},
4011 {"reset", parse_set, M_SET_RESET},
4012 {"save-hook", mutt_parse_hook, M_SAVEHOOK},
4013 {"score", mutt_parse_score, 0},
4014 {"send-hook", mutt_parse_hook, M_SENDHOOK},
4015 {"send2-hook", mutt_parse_hook, M_SEND2HOOK},
4016 {"set", parse_set, 0},
4017 {"source", parse_source, 0},
4018 {"spam", parse_spam_list, M_SPAM},
4019 {"nospam", parse_spam_list, M_NOSPAM},
4020 {"subscribe", parse_subscribe, 0},
4021 {"toggle", parse_set, M_SET_INV},
4022 {"unalias", parse_unalias, 0},
4023 {"unalternative_order", parse_unlist, UL &AlternativeOrderList},
4024 {"unauto_view", parse_unlist, UL &AutoViewList},
4025 {"unhdr_order", parse_unlist, UL &HeaderOrderList},
4026 {"unhook", mutt_parse_unhook, 0},
4027 {"unignore", parse_unignore, 0},
4028 {"unlists", parse_unlists, 0},
4029 {"unmono", mutt_parse_unmono, 0},
4030 {"unmy_hdr", parse_unmy_hdr, 0},
4031 {"unscore", mutt_parse_unscore, 0},
4032 {"unset", parse_set, M_SET_UNSET},
4033 {"unsubscribe", parse_unsubscribe, 0},