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 */
35 #define DTYPE(x) ((x) & DT_MASK)
38 #define DT_SUBTYPE_MASK 0xf0
39 #define DT_SORT_ALIAS 0x10
40 #define DT_SORT_BROWSER 0x20
41 #define DT_SORT_KEYS 0x40
42 #define DT_SORT_AUX 0x80
44 /* flags to parse_set() */
45 #define M_SET_INV (1<<0) /* default is to invert all vars */
46 #define M_SET_UNSET (1<<1) /* default is to unset all vars */
47 #define M_SET_RESET (1<<2) /* default is to reset all vars to default */
49 /* forced redraw/resort types */
51 #define R_INDEX (1<<0)
52 #define R_PAGER (1<<1)
53 #define R_RESORT (1<<2) /* resort the mailbox */
54 #define R_RESORT_SUB (1<<3) /* resort subthreads */
55 #define R_RESORT_INIT (1<<4) /* resort from scratch */
56 #define R_TREE (1<<5) /* redraw the thread tree */
57 #define R_BOTH (R_INDEX|R_PAGER)
58 #define R_RESORT_BOTH (R_RESORT|R_RESORT_SUB)
65 unsigned long init; /* initial value */
73 #define UL (unsigned long)
78 #define ISPELL "ispell"
81 /* build complete documentation */
88 # define MIXMASTER "mixmaster"
100 # define USE_LIBESMTP
110 struct option_t MuttVars[] = {
112 {"abort_nosubject", DT_QUAD, R_NONE, OPT_SUBJECT, M_ASKYES},
115 ** If set to \fIyes\fP, when composing messages and no subject is given
116 ** at the subject prompt, composition will be aborted. If set to
117 ** \fIno\fP, composing messages with no subject given at the subject
118 ** prompt will never be aborted.
120 {"abort_unmodified", DT_QUAD, R_NONE, OPT_ABORT, M_YES},
123 ** If set to \fIyes\fP, composition will automatically abort after
124 ** editing the message body if no changes are made to the file (this
125 ** check only happens after the \fIfirst\fP edit of the file). When set
126 ** to \fIno\fP, composition will never be aborted.
128 {"alias_file", DT_PATH, R_NONE, UL &AliasFile, UL "~/.muttngrc"},
131 ** The default file in which to save aliases created by the
132 ** ``$create-alias'' function.
134 ** \fBNote:\fP Mutt-ng will not automatically source this file; you must
135 ** explicitly use the ``$source'' command for it to be executed.
137 {"alias_format", DT_STR, R_NONE, UL &AliasFmt, UL "%4n %2f %t %-10a %r"},
140 ** Specifies the format of the data displayed for the ``alias'' menu. The
141 ** following \fTprintf(3)\fP-style sequences are available:
144 ** .dt %a .dd alias name
145 ** .dt %f .dd flags - currently, a "d" for an alias marked for deletion
146 ** .dt %n .dd index number
147 ** .dt %r .dd address which alias expands to
148 ** .dt %t .dd character which indicates if the alias is tagged for inclusion
151 {"allow_8bit", DT_BOOL, R_NONE, OPTALLOW8BIT, 1},
154 ** Controls whether 8-bit data is converted to 7-bit using either
155 ** \fTquoted-printable\fP or \fTbase64\fP encoding when sending mail.
157 {"allow_ansi", DT_BOOL, R_NONE, OPTALLOWANSI, 0},
160 ** Controls whether ANSI color codes in messages (and color tags in
161 ** rich text messages) are to be interpreted.
162 ** Messages containing these codes are rare, but if this option is set,
163 ** their text will be colored accordingly. Note that this may override
164 ** your color choices, and even present a security problem, since a
165 ** message could include a line like ``\fT[-- PGP output follows ...\fP" and
166 ** give it the same color as your attachment color.
168 {"arrow_cursor", DT_BOOL, R_BOTH, OPTARROWCURSOR, 0},
171 ** When \fIset\fP, an arrow (``\fT->\fP'') will be used to indicate the current entry
172 ** in menus instead of highlighting the whole line. On slow network or modem
173 ** links this will make response faster because there is less that has to
174 ** be redrawn on the screen when moving to the next or previous entries
177 {"ascii_chars", DT_BOOL, R_BOTH, OPTASCIICHARS, 0},
180 ** If \fIset\fP, Mutt-ng will use plain ASCII characters when displaying thread
181 ** and attachment trees, instead of the default \fTACS\fP characters.
183 {"askbcc", DT_BOOL, R_NONE, OPTASKBCC, 0},
186 ** If \fIset\fP, Mutt-ng will prompt you for blind-carbon-copy (Bcc) recipients
187 ** before editing an outgoing message.
189 {"askcc", DT_BOOL, R_NONE, OPTASKCC, 0},
192 ** If \fIset\fP, Mutt-ng will prompt you for carbon-copy (Cc) recipients before
193 ** editing the body of an outgoing message.
195 {"assumed_charset", DT_STR, R_NONE, UL &AssumedCharset, UL "us-ascii"},
198 ** This variable is a colon-separated list of character encoding
199 ** schemes for messages without character encoding indication.
200 ** Header field values and message body content without character encoding
201 ** indication would be assumed that they are written in one of this list.
202 ** By default, all the header fields and message body without any charset
203 ** indication are assumed to be in \fTus-ascii\fP.
205 ** For example, Japanese users might prefer this:
207 ** \fTset assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"\fP
209 ** However, only the first content is valid for the message body.
210 ** This variable is valid only if $$strict_mime is unset.
213 {"ask_followup_to", DT_SYN, R_NONE, UL "nntp_ask_followup_to", 0},
214 {"nntp_ask_followup_to", DT_BOOL, R_NONE, OPTASKFOLLOWUP, 0},
217 ** Availability: NNTP
220 ** If \fIset\fP, Mutt-ng will prompt you for the \fTFollowup-To:\fP header
221 ** field before editing the body of an outgoing news article.
223 {"ask_x_comment_to", DT_SYN, R_NONE, UL "nntp_ask_x_comment_to", 0},
224 {"nntp_ask_x_comment_to", DT_BOOL, R_NONE, OPTASKXCOMMENTTO, 0},
227 ** Availability: NNTP
230 ** If \fIset\fP, Mutt-ng will prompt you for the \fTX-Comment-To:\fP header
231 ** field before editing the body of an outgoing news article.
234 {"attach_format", DT_STR, R_NONE, UL &AttachFormat, UL "%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] "},
237 ** This variable describes the format of the ``attachment'' menu. The
238 ** following \fTprintf(3)\fP-style sequences are understood:
241 ** .dt %C .dd charset
242 ** .dt %c .dd requires charset conversion (n or c)
243 ** .dt %D .dd deleted flag
244 ** .dt %d .dd description
245 ** .dt %e .dd MIME \fTContent-Transfer-Encoding:\fP header field
246 ** .dt %f .dd filename
247 ** .dt %I .dd MIME \fTContent-Disposition:\fP header field (\fTI\fP=inline, \fTA\fP=attachment)
248 ** .dt %m .dd major MIME type
249 ** .dt %M .dd MIME subtype
250 ** .dt %n .dd attachment number
252 ** .dt %t .dd tagged flag
253 ** .dt %T .dd graphic tree characters
254 ** .dt %u .dd unlink (=to delete) flag
255 ** .dt %>X .dd right justify the rest of the string and pad with character "X"
256 ** .dt %|X .dd pad to the end of the line with character "X"
259 {"attach_sep", DT_STR, R_NONE, UL &AttachSep, UL "\n"},
262 ** The separator to add between attachments when operating (saving,
263 ** printing, piping, etc) on a list of tagged attachments.
265 {"attach_split", DT_BOOL, R_NONE, OPTATTACHSPLIT, 1},
268 ** If this variable is \fIunset\fP, when operating (saving, printing, piping,
269 ** etc) on a list of tagged attachments, Mutt-ng will concatenate the
270 ** attachments and will operate on them as a single attachment. The
271 ** ``$$attach_sep'' separator is added after each attachment. When \fIset\fP,
272 ** Mutt-ng will operate on the attachments one by one.
274 {"attribution", DT_STR, R_NONE, UL &Attribution, UL "On %d, %n wrote:"},
277 ** This is the string that will precede a message which has been included
278 ** in a reply. For a full listing of defined \fTprintf(3)\fP-like sequences see
279 ** the section on ``$$index_format''.
281 {"autoedit", DT_BOOL, R_NONE, OPTAUTOEDIT, 0},
284 ** When \fIset\fP along with ``$$edit_headers'', Mutt-ng will skip the initial
285 ** send-menu and allow you to immediately begin editing the body of your
286 ** message. The send-menu may still be accessed once you have finished
287 ** editing the body of your message.
289 ** Also see ``$$fast_reply''.
291 {"auto_tag", DT_BOOL, R_NONE, OPTAUTOTAG, 0},
294 ** When \fIset\fP, functions in the \fIindex\fP menu which affect a message
295 ** will be applied to all tagged messages (if there are any). When
296 ** unset, you must first use the ``tag-prefix'' function (default: "\fT;\fP") to
297 ** make the next function apply to all tagged messages.
299 {"beep", DT_BOOL, R_NONE, OPTBEEP, 1},
302 ** When this variable is \fIset\fP, Mutt-ng will beep when an error occurs.
304 {"beep_new", DT_BOOL, R_NONE, OPTBEEPNEW, 0},
307 ** When this variable is \fIset\fP, Mutt-ng will beep whenever it prints a message
308 ** notifying you of new mail. This is independent of the setting of the
309 ** ``$$beep'' variable.
311 {"bounce", DT_QUAD, R_NONE, OPT_BOUNCE, M_ASKYES},
314 ** Controls whether you will be asked to confirm bouncing messages.
315 ** If set to \fIyes\fP you don't get asked if you want to bounce a
316 ** message. Setting this variable to \fIno\fP is not generally useful,
317 ** and thus not recommended, because you are unable to bounce messages.
319 {"bounce_delivered", DT_BOOL, R_NONE, OPTBOUNCEDELIVERED, 1},
322 ** When this variable is \fIset\fP, Mutt-ng will include
323 ** \fTDelivered-To:\fP header fields when bouncing messages.
324 ** Postfix users may wish to \fIunset\fP this variable.
326 { "braille_friendly", DT_BOOL, R_NONE, OPTBRAILLEFRIENDLY, 0 },
329 ** When this variable is set, mutt will place the cursor at the beginning
330 ** of the current line in menus, even when the arrow_cursor variable
331 ** is unset, making it easier for blind persons using Braille displays to
332 ** follow these menus. The option is disabled by default because many
333 ** visual terminals don't permit making the cursor invisible.
336 {"catchup_newsgroup", DT_SYN, R_NONE, UL "nntp_catchup", 0},
337 {"nntp_catchup", DT_QUAD, R_NONE, OPT_CATCHUP, M_ASKYES},
340 ** Availability: NNTP
343 ** If this variable is \fIset\fP, Mutt-ng will mark all articles in a newsgroup
344 ** as read when you leaving it.
347 {"charset", DT_STR, R_NONE, UL &Charset, UL 0},
350 ** Character set your terminal uses to display and enter textual data.
352 {"check_new", DT_BOOL, R_NONE, OPTCHECKNEW, 1},
355 ** \fBNote:\fP this option only affects \fImaildir\fP and \fIMH\fP style
358 ** When \fIset\fP, Mutt-ng will check for new mail delivered while the
359 ** mailbox is open. Especially with MH mailboxes, this operation can
360 ** take quite some time since it involves scanning the directory and
361 ** checking each file to see if it has already been looked at. If it's
362 ** \fIunset\fP, no check for new mail is performed while the mailbox is open.
364 {"collapse_unread", DT_BOOL, R_NONE, OPTCOLLAPSEUNREAD, 1},
367 ** When \fIunset\fP, Mutt-ng will not collapse a thread if it contains any
370 {"uncollapse_jump", DT_BOOL, R_NONE, OPTUNCOLLAPSEJUMP, 0},
373 ** When \fIset\fP, Mutt-ng will jump to the next unread message, if any,
374 ** when the current thread is \fIun\fPcollapsed.
376 {"compose_format", DT_STR, R_BOTH, UL &ComposeFormat, UL "-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-"},
379 ** Controls the format of the status line displayed in the ``compose''
380 ** menu. This string is similar to ``$$status_format'', but has its own
381 ** set of \fTprintf(3)\fP-like sequences:
384 ** .dt %a .dd total number of attachments
385 ** .dt %h .dd local hostname
386 ** .dt %l .dd approximate size (in bytes) of the current message
387 ** .dt %v .dd Mutt-ng version string
390 ** See the text describing the ``$$status_format'' option for more
391 ** information on how to set ``$$compose_format''.
393 {"config_charset", DT_STR, R_NONE, UL &ConfigCharset, UL 0},
396 ** When defined, Mutt-ng will recode commands in rc files from this
399 {"confirmappend", DT_BOOL, R_NONE, OPTCONFIRMAPPEND, 1},
402 ** When \fIset\fP, Mutt-ng will prompt for confirmation when appending messages to
403 ** an existing mailbox.
405 {"confirmcreate", DT_BOOL, R_NONE, OPTCONFIRMCREATE, 1},
408 ** When \fIset\fP, Mutt-ng will prompt for confirmation when saving messages to a
409 ** mailbox which does not yet exist before creating it.
411 {"connect_timeout", DT_NUM, R_NONE, UL &ConnectTimeout, 30},
414 ** Causes Mutt-ng to timeout a network connection (for IMAP or POP) after this
415 ** many seconds if the connection is not able to be established. A negative
416 ** value causes Mutt-ng to wait indefinitely for the connection to succeed.
418 {"content_type", DT_STR, R_NONE, UL &ContentType, UL "text/plain"},
421 ** Sets the default \fTContent-Type:\fP header field for the body
422 ** of newly composed messages.
424 {"copy", DT_QUAD, R_NONE, OPT_COPY, M_YES},
427 ** This variable controls whether or not copies of your outgoing messages
428 ** will be saved for later references. Also see ``$$record'',
429 ** ``$$save_name'', ``$$force_name'' and ``$fcc-hook''.
432 {"crypt_use_gpgme", DT_BOOL, R_NONE, OPTCRYPTUSEGPGME, 0},
435 ** This variable controls the use the GPGME enabled crypto backends.
436 ** If it is \fIset\fP and Mutt-ng was build with gpgme support, the gpgme code for
437 ** S/MIME and PGP will be used instead of the classic code.
439 ** \fBNote\fP: You need to use this option in your \fT.muttngrc\fP configuration
440 ** file as it won't have any effect when used interactively.
443 {"crypt_autopgp", DT_BOOL, R_NONE, OPTCRYPTAUTOPGP, 1},
446 ** This variable controls whether or not Mutt-ng may automatically enable
447 ** PGP encryption/signing for messages. See also ``$$crypt_autoencrypt'',
448 ** ``$$crypt_replyencrypt'',
449 ** ``$$crypt_autosign'', ``$$crypt_replysign'' and ``$$smime_is_default''.
451 {"crypt_autosmime", DT_BOOL, R_NONE, OPTCRYPTAUTOSMIME, 1},
454 ** This variable controls whether or not Mutt-ng may automatically enable
455 ** S/MIME encryption/signing for messages. See also ``$$crypt_autoencrypt'',
456 ** ``$$crypt_replyencrypt'',
457 ** ``$$crypt_autosign'', ``$$crypt_replysign'' and ``$$smime_is_default''.
459 {"date_format", DT_STR, R_BOTH, UL &DateFmt, UL "!%a, %b %d, %Y at %I:%M:%S%p %Z"},
462 ** This variable controls the format of the date printed by the ``\fT%d\fP''
463 ** sequence in ``$$index_format''. This is passed to \fTstrftime(3)\fP
464 ** to process the date.
466 ** Unless the first character in the string is a bang (``\fT!\fP''), the month
467 ** and week day names are expanded according to the locale specified in
468 ** the variable ``$$locale''. If the first character in the string is a
469 ** bang, the bang is discarded, and the month and week day names in the
470 ** rest of the string are expanded in the \fIC\fP locale (that is in US
473 {"default_hook", DT_STR, R_NONE, UL &DefaultHook, UL "~f %s !~P | (~P ~C %s)"},
476 ** This variable controls how send-hooks, message-hooks, save-hooks,
477 ** and fcc-hooks will
478 ** be interpreted if they are specified with only a simple regexp,
479 ** instead of a matching pattern. The hooks are expanded when they are
480 ** declared, so a hook will be interpreted according to the value of this
481 ** variable at the time the hook is declared. The default value matches
482 ** if the message is either from a user matching the regular expression
483 ** given, or if it is from you (if the from address matches
484 ** ``alternates'') and is to or cc'ed to a user matching the given
485 ** regular expression.
487 {"delete", DT_QUAD, R_NONE, OPT_DELETE, M_ASKYES},
490 ** Controls whether or not messages are really deleted when closing or
491 ** synchronizing a mailbox. If set to \fIyes\fP, messages marked for
492 ** deleting will automatically be purged without prompting. If set to
493 ** \fIno\fP, messages marked for deletion will be kept in the mailbox.
495 {"delete_untag", DT_BOOL, R_NONE, OPTDELETEUNTAG, 1},
498 ** If this option is \fIset\fP, Mutt-ng will untag messages when marking them
499 ** for deletion. This applies when you either explicitly delete a message,
500 ** or when you save it to another folder.
502 {"digest_collapse", DT_BOOL, R_NONE, OPTDIGESTCOLLAPSE, 1},
505 ** If this option is \fIset\fP, Mutt-ng's received-attachments menu will not show the subparts of
506 ** individual messages in a multipart/digest. To see these subparts, press 'v' on that menu.
508 {"display_filter", DT_PATH, R_PAGER, UL &DisplayFilter, UL ""},
511 ** When \fIset\fP, specifies a command used to filter messages. When a message
512 ** is viewed it is passed as standard input to $$display_filter, and the
513 ** filtered message is read from the standard output.
515 #if defined(DL_STANDALONE) && defined(USE_DOTLOCK)
516 {"dotlock_program", DT_PATH, R_NONE, UL &MuttDotlock, UL BINDIR "/muttng_dotlock"},
519 ** Availability: Standalone and Dotlock
522 ** Contains the path of the \fTmuttng_dotlock(1)\fP binary to be used by
526 {"dsn_notify", DT_STR, R_NONE, UL &DsnNotify, UL ""},
529 ** \fBNote:\fP you should not enable this unless you are using Sendmail
532 ** This variable sets the request for when notification is returned. The
533 ** string consists of a comma separated list (no spaces!) of one or more
534 ** of the following: \fInever\fP, to never request notification,
535 ** \fIfailure\fP, to request notification on transmission failure,
536 ** \fIdelay\fP, to be notified of message delays, \fIsuccess\fP, to be
537 ** notified of successful transmission.
539 ** Example: \fTset dsn_notify="failure,delay"\fP
541 {"dsn_return", DT_STR, R_NONE, UL &DsnReturn, UL ""},
544 ** \fBNote:\fP you should not enable this unless you are using Sendmail
547 ** This variable controls how much of your message is returned in DSN
548 ** messages. It may be set to either \fIhdrs\fP to return just the
549 ** message header, or \fIfull\fP to return the full message.
551 ** Example: \fTset dsn_return=hdrs\fP
553 {"duplicate_threads", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTDUPTHREADS, 1},
556 ** This variable controls whether Mutt-ng, when sorting by threads, threads
557 ** messages with the same \fTMessage-Id:\fP header field together.
558 ** If it is \fIset\fP, it will indicate that it thinks they are duplicates
559 ** of each other with an equals sign in the thread diagram.
561 {"edit_headers", DT_BOOL, R_NONE, OPTEDITHDRS, 0},
564 ** This option allows you to edit the header of your outgoing messages
565 ** along with the body of your message.
567 {"editor", DT_PATH, R_NONE, UL &Editor, 0},
570 ** This variable specifies which editor is used by Mutt-ng.
571 ** It defaults to the value of the \fT$$$VISUAL\fP, or \fT$$$EDITOR\fP, environment
572 ** variable, or to the string "\fTvi\fP" if neither of those are set.
574 {"encode_from", DT_BOOL, R_NONE, OPTENCODEFROM, 0},
577 ** When \fIset\fP, Mutt-ng will \fTquoted-printable\fP encode messages when
578 ** they contain the string ``\fTFrom \fP'' (note the trailing space)
579 ** in the beginning of a line. Useful to avoid the tampering certain mail
580 ** delivery and transport agents tend to do with messages.
582 {"envelope_from", DT_BOOL, R_NONE, OPTENVFROM, 0},
585 ** When \fIset\fP, Mutt-ng will try to derive the message's \fIenvelope\fP
586 ** sender from the ``\fTFrom:\fP'' header field. Note that this information is passed
587 ** to the sendmail command using the ``\fT-f\fP" command line switch, so don't set this
588 ** option if you are using that switch in $$sendmail yourself,
589 ** or if the sendmail on your machine doesn't support that command
592 {"escape", DT_STR, R_NONE, UL &EscChar, UL "~"},
595 ** Escape character to use for functions in the builtin editor.
597 {"fast_reply", DT_BOOL, R_NONE, OPTFASTREPLY, 0},
600 ** When \fIset\fP, the initial prompt for recipients and subject are skipped
601 ** when replying to messages, and the initial prompt for subject is
602 ** skipped when forwarding messages.
604 ** \fBNote:\fP this variable has no effect when the ``$$autoedit''
605 ** variable is \fIset\fP.
607 {"fcc_attach", DT_BOOL, R_NONE, OPTFCCATTACH, 1},
610 ** This variable controls whether or not attachments on outgoing messages
611 ** are saved along with the main body of your message.
613 {"fcc_clear", DT_BOOL, R_NONE, OPTFCCCLEAR, 0},
616 ** When this variable is \fIset\fP, FCCs will be stored unencrypted and
617 ** unsigned, even when the actual message is encrypted and/or
621 {"file_charset", DT_STR, R_NONE, UL &FileCharset, UL 0},
624 ** This variable is a colon-separated list of character encoding
625 ** schemes for text file attatchments.
626 ** If \fIunset\fP, $$charset value will be used instead.
627 ** For example, the following configuration would work for Japanese
630 ** \fTset file_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"\fP
632 ** Note: ``\fTiso-2022-*\fP'' must be put at the head of the value as shown above
635 {"folder", DT_PATH, R_NONE, UL &Maildir, UL "~/Mail"},
638 ** Specifies the default location of your mailboxes. A ``\fT+\fP'' or ``\fT=\fP'' at the
639 ** beginning of a pathname will be expanded to the value of this
640 ** variable. Note that if you change this variable from the default
641 ** value you need to make sure that the assignment occurs \fIbefore\fP
642 ** you use ``+'' or ``='' for any other variables since expansion takes place
643 ** during the ``set'' command.
645 {"folder_format", DT_STR, R_INDEX, UL &FolderFormat, UL "%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f"},
648 ** This variable allows you to customize the file browser display to your
649 ** personal taste. This string is similar to ``$$index_format'', but has
650 ** its own set of \fTprintf(3)\fP-like sequences:
653 ** .dt %C .dd current file number
654 ** .dt %d .dd date/time folder was last modified
655 ** .dt %f .dd filename
656 ** .dt %F .dd file permissions
657 ** .dt %g .dd group name (or numeric gid, if missing)
658 ** .dt %l .dd number of hard links
659 ** .dt %N .dd N if folder has new mail, blank otherwise
660 ** .dt %s .dd size in bytes
661 ** .dt %t .dd * if the file is tagged, blank otherwise
662 ** .dt %u .dd owner name (or numeric uid, if missing)
663 ** .dt %>X .dd right justify the rest of the string and pad with character "X"
664 ** .dt %|X .dd pad to the end of the line with character "X"
667 {"followup_to", DT_BOOL, R_NONE, OPTFOLLOWUPTO, 1},
670 ** Controls whether or not the \fTMail-Followup-To:\fP header field is
671 ** generated when sending mail. When \fIset\fP, Mutt-ng will generate this
672 ** field when you are replying to a known mailing list, specified with
673 ** the ``subscribe'' or ``$lists'' commands or detected by common mailing list
676 ** This field has two purposes. First, preventing you from
677 ** receiving duplicate copies of replies to messages which you send
678 ** to mailing lists. Second, ensuring that you do get a reply
679 ** separately for any messages sent to known lists to which you are
680 ** not subscribed. The header will contain only the list's address
681 ** for subscribed lists, and both the list address and your own
682 ** email address for unsubscribed lists. Without this header, a
683 ** group reply to your message sent to a subscribed list will be
684 ** sent to both the list and your address, resulting in two copies
685 ** of the same email for you.
688 {"followup_to_poster", DT_SYN, R_NONE, UL "nntp_followup_to_poster", 0},
689 {"nntp_followup_to_poster", DT_QUAD, R_NONE, OPT_FOLLOWUPTOPOSTER, M_ASKYES},
692 ** Availability: NNTP
695 ** If this variable is \fIset\fP and the keyword "\fTposter\fP" is present in
696 ** the \fTFollowup-To:\fP header field, a follow-up to the newsgroup is not
697 ** permitted. The message will be mailed to the submitter of the
701 {"force_name", DT_BOOL, R_NONE, OPTFORCENAME, 0},
704 ** This variable is similar to ``$$save_name'', except that Mutt-ng will
705 ** store a copy of your outgoing message by the username of the address
706 ** you are sending to even if that mailbox does not exist.
708 ** Also see the ``$$record'' variable.
710 {"force_buffy_check", DT_BOOL, R_NONE, OPTFORCEBUFFYCHECK, 0},
713 ** When \fIset\fP, it causes Mutt-ng to check for new mail when the
714 ** \fIbuffy-list\fP command is invoked. When \fIunset\fP, \fIbuffy_list\fP
715 ** will just list all mailboxes which are already known to have new mail.
717 ** Also see the following variables: ``$$timeout'', ``$$mail_check'' and
718 ** ``$$imap_mail_check''.
720 {"forward_decode", DT_BOOL, R_NONE, OPTFORWDECODE, 1},
723 ** Controls the decoding of complex MIME messages into \fTtext/plain\fP when
724 ** forwarding a message. The message header is also RFC2047 decoded.
725 ** This variable is only used, if ``$$mime_forward'' is \fIunset\fP,
726 ** otherwise ``$$mime_forward_decode'' is used instead.
728 {"forward_edit", DT_QUAD, R_NONE, OPT_FORWEDIT, M_YES},
731 ** This quadoption controls whether or not the user is automatically
732 ** placed in the editor when forwarding messages. For those who always want
733 ** to forward with no modification, use a setting of \fIno\fP.
735 {"forward_format", DT_STR, R_NONE, UL &ForwFmt, UL "[%a: %s]"},
738 ** This variable controls the default subject when forwarding a message.
739 ** It uses the same format sequences as the ``$$index_format'' variable.
741 {"forward_quote", DT_BOOL, R_NONE, OPTFORWQUOTE, 0},
744 ** When \fIset\fP forwarded messages included in the main body of the
745 ** message (when ``$$mime_forward'' is \fIunset\fP) will be quoted using
746 ** ``$$indent_string''.
748 {"from", DT_ADDR, R_NONE, UL &From, UL 0},
751 ** This variable contains a default from address. It
752 ** can be overridden using my_hdr (including from send-hooks) and
753 ** ``$$reverse_name''. This variable is ignored if ``$$use_from''
757 ** \fTsend-hook Mutt-ng-devel@lists.berlios.de 'my_hdr From: Foo Bar <foo@bar.fb>'\fP
758 ** when replying to the mutt-ng developer's mailing list and Mutt-ng takes this email address.
760 ** Defaults to the contents of the environment variable \fT$$$EMAIL\fP.
762 {"gecos_mask", DT_RX, R_NONE, UL &GecosMask, UL "^[^,]*"},
765 ** A regular expression used by Mutt-ng to parse the GECOS field of a password
766 ** entry when expanding the alias. By default the regular expression is set
767 ** to ``\fT^[^,]*\fP'' which will return the string up to the first ``\fT,\fP'' encountered.
768 ** If the GECOS field contains a string like "lastname, firstname" then you
769 ** should do: \fTset gecos_mask=".*"\fP.
771 ** This can be useful if you see the following behavior: you address a e-mail
772 ** to user ID stevef whose full name is Steve Franklin. If Mutt-ng expands
773 ** stevef to ``Franklin'' stevef@foo.bar then you should set the gecos_mask to
774 ** a regular expression that will match the whole name so Mutt-ng will expand
775 ** ``Franklin'' to ``Franklin, Steve''.
778 {"group_index_format", DT_SYN, R_NONE, UL "nntp_group_index_format", 0},
779 {"nntp_group_index_format", DT_STR, R_BOTH, UL &GroupFormat, UL "%4C %M%N %5s %-45.45f %d"},
782 ** Availability: NNTP
785 ** This variable allows you to customize the newsgroup browser display to
786 ** your personal taste. This string is similar to ``$index_format'', but
787 ** has its own set of \fTprintf(3)\fP-like sequences:
790 ** %C current newsgroup number
791 ** %d description of newsgroup (retrieved from server)
793 ** %M ``-'' if newsgroup not allowed for direct post (moderated for example)
794 ** %N ``N'' if newsgroup is new, ``u'' if unsubscribed, blank otherwise
795 ** %n number of new articles in newsgroup
796 ** %s number of unread articles in newsgroup
797 ** %>X right justify the rest of the string and pad with character "X"
798 ** %|X pad to the end of the line with character "X"
802 {"hdrs", DT_BOOL, R_NONE, OPTHDRS, 1},
805 ** When \fIunset\fP, the header fields normally added by the ``$my_hdr''
806 ** command are not created. This variable \fImust\fP be \fIunset\fP before
807 ** composing a new message or replying in order to take effect. If \fIset\fP,
808 ** the user defined header fields are added to every new message.
810 {"header", DT_BOOL, R_NONE, OPTHEADER, 0},
813 ** When \fIset\fP, this variable causes Mutt-ng to include the header
814 ** of the message you are replying to into the edit buffer.
815 ** The ``$$weed'' setting applies.
817 {"help", DT_BOOL, R_BOTH, OPTHELP, 1},
820 ** When \fIset\fP, help lines describing the bindings for the major functions
821 ** provided by each menu are displayed on the first line of the screen.
823 ** \fBNote:\fP The binding will not be displayed correctly if the
824 ** function is bound to a sequence rather than a single keystroke. Also,
825 ** the help line may not be updated if a binding is changed while Mutt-ng is
826 ** running. Since this variable is primarily aimed at new users, neither
827 ** of these should present a major problem.
829 {"hidden_host", DT_BOOL, R_NONE, OPTHIDDENHOST, 0},
832 ** When \fIset\fP, Mutt-ng will skip the host name part of ``$$hostname'' variable
833 ** when adding the domain part to addresses. This variable does not
834 ** affect the generation of \fTMessage-ID:\fP header fields, and it will not lead to the
835 ** cut-off of first-level domains.
837 {"hide_limited", DT_BOOL, R_TREE|R_INDEX, OPTHIDELIMITED, 0},
840 ** When \fIset\fP, Mutt-ng will not show the presence of messages that are hidden
841 ** by limiting, in the thread tree.
843 {"hide_missing", DT_BOOL, R_TREE|R_INDEX, OPTHIDEMISSING, 1},
846 ** When \fIset\fP, Mutt-ng will not show the presence of missing messages in the
849 {"hide_thread_subject", DT_BOOL, R_TREE|R_INDEX, OPTHIDETHREADSUBJECT, 1},
852 ** When \fIset\fP, Mutt-ng will not show the subject of messages in the thread
853 ** tree that have the same subject as their parent or closest previously
854 ** displayed sibling.
856 {"hide_top_limited", DT_BOOL, R_TREE|R_INDEX, OPTHIDETOPLIMITED, 0},
859 ** When \fIset\fP, Mutt-ng will not show the presence of messages that are hidden
860 ** by limiting, at the top of threads in the thread tree. Note that when
861 ** $$hide_missing is set, this option will have no effect.
863 {"hide_top_missing", DT_BOOL, R_TREE|R_INDEX, OPTHIDETOPMISSING, 1},
866 ** When \fIset\fP, Mutt-ng will not show the presence of missing messages at the
867 ** top of threads in the thread tree. Note that when $$hide_limited is
868 ** \fIset\fP, this option will have no effect.
870 {"history", DT_NUM, R_NONE, UL &HistSize, 10},
873 ** This variable controls the size (in number of strings remembered) of
874 ** the string history buffer. The buffer is cleared each time the
875 ** variable is changed.
877 {"honor_followup_to", DT_QUAD, R_NONE, OPT_MFUPTO, M_YES},
880 ** This variable controls whether or not a \fTMail-Followup-To:\fP header field is
881 ** honored when group-replying to a message.
883 {"hostname", DT_STR, R_NONE, UL &Fqdn, 0},
886 ** Specifies the hostname to use after the ``\fT@\fP'' in local e-mail
887 ** addresses and during generation of \fTMessage-Id:\fP headers.
889 ** Please be sure to really know what you are doing when changing this variable
890 ** to configure a custom domain part of Message-IDs.
892 {"ignore_list_reply_to", DT_BOOL, R_NONE, OPTIGNORELISTREPLYTO, 0},
895 ** Affects the behaviour of the \fIreply\fP function when replying to
896 ** messages from mailing lists. When \fIset\fP, if the ``\fTReply-To:\fP'' header field is
897 ** set to the same value as the ``\fTTo:\fP'' header field, Mutt-ng assumes that the
898 ** ``\fTReply-To:\fP'' header field was set by the mailing list to automate responses
899 ** to the list, and will ignore this field. To direct a response to the
900 ** mailing list when this option is set, use the \fIlist-reply\fP
901 ** function; \fIgroup-reply\fP will reply to both the sender and the
905 {"imap_authenticators", DT_STR, R_NONE, UL &ImapAuthenticators, UL 0},
908 ** Availability: IMAP
911 ** This is a colon-delimited list of authentication methods Mutt-ng may
912 ** attempt to use to log in to an IMAP server, in the order Mutt-ng should
913 ** try them. Authentication methods are either ``\fTlogin\fP'' or the right
914 ** side of an IMAP ``\fTAUTH=\fP'' capability string, e.g. ``\fTdigest-md5\fP'',
915 ** ``\fTgssapi\fP'' or ``\fTcram-md5\fP''. This parameter is case-insensitive.
918 ** parameter is \fIunset\fP (the default) Mutt-ng will try all available methods,
919 ** in order from most-secure to least-secure.
921 ** Example: \fTset imap_authenticators="gssapi:cram-md5:login"\fP
923 ** \fBNote:\fP Mutt-ng will only fall back to other authentication methods if
924 ** the previous methods are unavailable. If a method is available but
925 ** authentication fails, Mutt-ng will not connect to the IMAP server.
927 {"imap_delim_chars", DT_STR, R_NONE, UL &ImapDelimChars, UL "/."},
930 ** Availability: IMAP
933 ** This contains the list of characters which you would like to treat
934 ** as folder separators for displaying IMAP paths. In particular it
935 ** helps in using the '\fT=\fP' shortcut for your $$folder variable.
937 # if defined(USE_SSL) || defined(USE_GNUTLS)
938 {"imap_force_ssl", DT_BOOL, R_NONE, OPTIMAPFORCESSL, 0},
941 ** Availability: IMAP and SSL or IMAP and GNUTLS
944 ** If this variable is \fIset\fP, Mutt-ng will always use SSL when
945 ** connecting to IMAP servers.
948 {"imap_headers", DT_STR, R_INDEX, UL &ImapHeaders, UL 0},
951 ** Availability: IMAP
954 ** Mutt-ng requests these header fields in addition to the default headers
955 ** (``DATE FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE
956 ** CONTENT-DESCRIPTION IN-REPLY-TO REPLY-TO LINES X-LABEL'') from IMAP
957 ** servers before displaying the ``index'' menu. You may want to add more
958 ** headers for spam detection.
960 ** \fBNote:\fP This is a space separated list.
962 {"imap_home_namespace", DT_STR, R_NONE, UL &ImapHomeNamespace, UL 0},
965 ** Availability: IMAP
968 ** You normally want to see your personal folders alongside
969 ** your \fTINBOX\fP in the IMAP browser. If you see something else, you may set
970 ** this variable to the IMAP path to your folders.
972 {"imap_keepalive", DT_NUM, R_NONE, UL &ImapKeepalive, 900},
975 ** Availability: IMAP
978 ** This variable specifies the maximum amount of time in seconds that Mutt-ng
979 ** will wait before polling open IMAP connections, to prevent the server
980 ** from closing them before Mutt-ng has finished with them.
983 ** well within the RFC-specified minimum amount of time (30 minutes) before
984 ** a server is allowed to do this, but in practice the RFC does get
985 ** violated every now and then.
987 ** Reduce this number if you find yourself
988 ** getting disconnected from your IMAP server due to inactivity.
990 {"imap_login", DT_STR, R_NONE, UL &ImapLogin, 0 },
993 ** Availability: IMAP
996 ** Your login name on the IMAP server.
998 ** This variable defaults to the value of ``$$imap_user.''
1000 {"imap_list_subscribed", DT_BOOL, R_NONE, OPTIMAPLSUB, 0},
1003 ** Availability: IMAP
1006 ** This variable configures whether IMAP folder browsing will look for
1007 ** only subscribed folders or all folders. This can be toggled in the
1008 ** IMAP browser with the \fItoggle-subscribed\fP function.
1010 {"imap_mail_check", DT_NUM, R_NONE, UL &ImapBuffyTimeout, 300},
1013 ** This variable configures how often (in seconds) Mutt-ng should look for
1014 ** new mail in IMAP folders. This is split from the ``$mail_check'' variable
1015 ** to generate less traffic and get more accurate information for local folders.
1017 {"imap_pass", DT_STR, R_NONE, UL &ImapPass, UL 0},
1020 ** Availability: IMAP
1023 ** Specifies the password for your IMAP account. If \fIunset\fP, Mutt-ng will
1024 ** prompt you for your password when you invoke the fetch-mail function.
1026 ** \fBWarning\fP: you should only use this option when you are on a
1027 ** fairly secure machine, because the superuser can read your configuration even
1028 ** if you are the only one who can read the file.
1030 {"imap_passive", DT_BOOL, R_NONE, OPTIMAPPASSIVE, 1},
1033 ** Availability: IMAP
1036 ** When \fIset\fP, Mutt-ng will not open new IMAP connections to check for new
1037 ** mail. Mutt-ng will only check for new mail over existing IMAP
1038 ** connections. This is useful if you don't want to be prompted to
1039 ** user/password pairs on Mutt-ng invocation, or if opening the connection
1042 {"imap_peek", DT_BOOL, R_NONE, OPTIMAPPEEK, 1},
1045 ** Availability: IMAP
1048 ** If \fIset\fP, Mutt-ng will avoid implicitly marking your mail as read whenever
1049 ** you fetch a message from the server. This is generally a good thing,
1050 ** but can make closing an IMAP folder somewhat slower. This option
1051 ** exists to appease speed freaks.
1053 {"imap_reconnect", DT_QUAD, R_NONE, OPT_IMAPRECONNECT, M_ASKYES},
1056 ** Availability: IMAP
1059 ** Controls whether or not Mutt-ng will try to reconnect to IMAP server when
1060 ** the connection is lost.
1062 {"imap_servernoise", DT_BOOL, R_NONE, OPTIMAPSERVERNOISE, 1},
1065 ** Availability: IMAP
1068 ** When \fIset\fP, Mutt-ng will display warning messages from the IMAP
1069 ** server as error messages. Since these messages are often
1070 ** harmless, or generated due to configuration problems on the
1071 ** server which are out of the users' hands, you may wish to suppress
1072 ** them at some point.
1074 {"imap_user", DT_STR, R_NONE, UL &ImapUser, UL 0},
1077 ** Availability: IMAP
1080 ** The name of the user whose mail you intend to access on the IMAP
1083 ** This variable defaults to your user name on the local machine.
1086 {"implicit_autoview", DT_BOOL, R_NONE, OPTIMPLICITAUTOVIEW, 0},
1089 ** If \fIset\fP, Mutt-ng will look for a mailcap entry with the
1090 ** ``\fTcopiousoutput\fP'' flag set for \fIevery\fP MIME attachment it doesn't have
1091 ** an internal viewer defined for. If such an entry is found, Mutt-ng will
1092 ** use the viewer defined in that entry to convert the body part to text
1095 {"include", DT_QUAD, R_NONE, OPT_INCLUDE, M_ASKYES},
1098 ** Controls whether or not a copy of the message(s) you are replying to
1099 ** is included in your reply.
1101 {"include_onlyfirst", DT_BOOL, R_NONE, OPTINCLUDEONLYFIRST, 0},
1104 ** Controls whether or not Mutt-ng includes only the first attachment
1105 ** of the message you are replying.
1107 {"indent_string", DT_STR, R_NONE, UL &Prefix, UL "> "},
1110 ** Specifies the string to prepend to each line of text quoted in a
1111 ** message to which you are replying. You are strongly encouraged not to
1112 ** change this value, as it tends to agitate the more fanatical netizens.
1114 {"index_format", DT_STR, R_BOTH, UL &HdrFmt, UL "%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s"},
1117 ** This variable allows you to customize the message index display to
1118 ** your personal taste.
1120 ** ``Format strings'' are similar to the strings used in the ``C''
1121 ** function \fTprintf(3)\fP to format output (see the man page for more detail).
1122 ** The following sequences are defined in Mutt-ng:
1125 ** .dt %a .dd address of the author
1126 ** .dt %A .dd reply-to address (if present; otherwise: address of author)
1127 ** .dt %b .dd filename of the original message folder (think mailBox)
1128 ** .dt %B .dd the list to which the letter was sent, or else the folder name (%b).
1129 ** .dt %c .dd number of characters (bytes) in the message
1130 ** .dt %C .dd current message number
1131 ** .dt %d .dd date and time of the message in the format specified by
1132 ** ``date_format'' converted to sender's time zone
1133 ** .dt %D .dd date and time of the message in the format specified by
1134 ** ``date_format'' converted to the local time zone
1135 ** .dt %e .dd current message number in thread
1136 ** .dt %E .dd number of messages in current thread
1137 ** .dt %f .dd entire From: line (address + real name)
1138 ** .dt %F .dd author name, or recipient name if the message is from you
1139 ** .dt %H .dd spam attribute(s) of this message
1140 ** .dt %g .dd newsgroup name (if compiled with nntp support)
1141 ** .dt %i .dd message-id of the current message
1142 ** .dt %l .dd number of lines in the message (does not work with maildir,
1143 ** mh, and possibly IMAP folders)
1144 ** .dt %L .dd If an address in the To or CC header field matches an address
1145 ** defined by the users ``subscribe'' command, this displays
1146 ** "To <list-name>", otherwise the same as %F.
1147 ** .dt %m .dd total number of message in the mailbox
1148 ** .dt %M .dd number of hidden messages if the thread is collapsed.
1149 ** .dt %N .dd message score
1150 ** .dt %n .dd author's real name (or address if missing)
1151 ** .dt %O .dd (_O_riginal save folder) Where Mutt-ng would formerly have
1152 ** stashed the message: list name or recipient name if no list
1153 ** .dt %s .dd subject of the message
1154 ** .dt %S .dd status of the message (N/D/d/!/r/\(as)
1155 ** .dt %t .dd `to:' field (recipients)
1156 ** .dt %T .dd the appropriate character from the $$to_chars string
1157 ** .dt %u .dd user (login) name of the author
1158 ** .dt %v .dd first name of the author, or the recipient if the message is from you
1159 ** .dt %W .dd name of organization of author (`organization:' field)
1160 ** .dt %y .dd `x-label:' field, if present
1161 ** .dt %Y .dd `x-label' field, if present, and (1) not at part of a thread tree,
1162 ** (2) at the top of a thread, or (3) `x-label' is different from
1163 ** preceding message's `x-label'.
1164 ** .dt %Z .dd message status flags
1165 ** .dt %{fmt} .dd the date and time of the message is converted to sender's
1166 ** time zone, and ``fmt'' is expanded by the library function
1167 ** ``strftime''; a leading bang disables locales
1168 ** .dt %[fmt] .dd the date and time of the message is converted to the local
1169 ** time zone, and ``fmt'' is expanded by the library function
1170 ** ``strftime''; a leading bang disables locales
1171 ** .dt %(fmt) .dd the local date and time when the message was received.
1172 ** ``fmt'' is expanded by the library function ``strftime'';
1173 ** a leading bang disables locales
1174 ** .dt %<fmt> .dd the current local time. ``fmt'' is expanded by the library
1175 ** function ``strftime''; a leading bang disables locales.
1176 ** .dt %>X .dd right justify the rest of the string and pad with character "X"
1177 ** .dt %|X .dd pad to the end of the line with character "X"
1180 ** See also: ``$$to_chars''.
1183 {"inews", DT_SYN, R_NONE, UL "nntp_inews", 0},
1184 {"nntp_inews", DT_PATH, R_NONE, UL &Inews, UL ""},
1187 ** Availability: NNTP
1190 ** If \fIset\fP, specifies the program and arguments used to deliver news posted
1191 ** by Mutt-ng. Otherwise, Mutt-ng posts article using current connection.
1192 ** The following \fTprintf(3)\fP-style sequence is understood:
1195 ** %s newsserver name
1198 ** Example: \fTset inews="/usr/local/bin/inews -hS"\fP
1201 {"ispell", DT_PATH, R_NONE, UL &Ispell, UL ISPELL},
1204 ** How to invoke ispell (GNU's spell-checking software).
1206 {"keep_flagged", DT_BOOL, R_NONE, OPTKEEPFLAGGED, 0},
1209 ** If \fIset\fP, read messages marked as flagged will not be moved
1210 ** from your spool mailbox to your ``$$mbox'' mailbox, or as a result of
1211 ** a ``$mbox-hook'' command.
1213 {"locale", DT_STR, R_BOTH, UL &Locale, UL "C"},
1216 ** The locale used by \fTstrftime(3)\fP to format dates. Legal values are
1217 ** the strings your system accepts for the locale variable \fTLC_TIME\fP.
1219 {"list_reply", DT_QUAD, R_NONE, OPT_LISTREPLY, M_NO},
1222 ** When \fIset\fP, address replies to the mailing list the original message came
1223 ** from (instead to the author only). Setting this option to ``\fIask-yes\fP'' or
1224 ** ``\fIask-no\fP'' will ask if you really intended to reply to the author only.
1226 {"max_line_length", DT_NUM, R_NONE, UL &MaxLineLength, 0},
1229 ** When \fIset\fP, the maximum line length for displaying ``format = flowed'' messages is limited
1230 ** to this length. A value of 0 (which is also the default) means that the
1231 ** maximum line length is determined by the terminal width and $$wrapmargin.
1233 {"mail_check", DT_NUM, R_NONE, UL &BuffyTimeout, 5},
1236 ** This variable configures how often (in seconds) Mutt-ng should look for
1239 ** \fBNote:\fP This does not apply to IMAP mailboxes, see $$imap_mail_check.
1241 {"mailcap_path", DT_STR, R_NONE, UL &MailcapPath, 0},
1244 ** This variable specifies which files to consult when attempting to
1245 ** display MIME bodies not directly supported by Mutt-ng.
1247 {"mailcap_sanitize", DT_BOOL, R_NONE, OPTMAILCAPSANITIZE, 1},
1250 ** If \fIset\fP, Mutt-ng will restrict possible characters in mailcap \fT%\fP expandos
1251 ** to a well-defined set of safe characters. This is the safe setting,
1252 ** but we are not sure it doesn't break some more advanced MIME stuff.
1254 ** \fBDON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE
1259 {"header_cache", DT_PATH, R_NONE, UL &HeaderCache, 0},
1262 ** Availability: Header Cache
1265 ** The $$header_cache variable points to the header cache database.
1267 ** If $$header_cache points to a directory it will contain a header cache
1268 ** database per folder. If $$header_cache points to a file that file will
1269 ** be a single global header cache. By default it is \fIunset\fP so no
1270 ** header caching will be used.
1272 {"maildir_header_cache_verify", DT_BOOL, R_NONE, OPTHCACHEVERIFY, 1},
1275 ** Availability: Header Cache
1278 ** Check for Maildir unaware programs other than Mutt-ng having modified maildir
1279 ** files when the header cache is in use. This incurs one \fTstat(2)\fP per
1280 ** message every time the folder is opened.
1282 #if HAVE_GDBM || HAVE_DB4
1283 {"header_cache_pagesize", DT_STR, R_NONE, UL &HeaderCachePageSize, UL "16384"},
1286 ** Availability: Header Cache
1289 ** Change the maildir header cache database page size.
1292 ** or too small of a page size for the common header can waste
1293 ** space, memory effectiveness, or CPU time. The default should be more or
1294 ** less the best you can get. For details google for mutt header
1295 ** cache (first hit).
1297 #endif /* HAVE_GDBM || HAVE_DB 4 */
1299 { "header_cache_compress", DT_BOOL, R_NONE, OPTHCACHECOMPRESS, 0 },
1302 ** If enabled the header cache will be compressed. So only one fifth of the usual
1303 ** diskspace is used, but the uncompression can result in a slower open of the
1306 #endif /* HAVE_QDBM */
1307 #endif /* USE_HCACHE */
1308 {"maildir_trash", DT_BOOL, R_NONE, OPTMAILDIRTRASH, 0},
1311 ** If \fIset\fP, messages marked as deleted will be saved with the maildir
1312 ** (T)rashed flag instead of physically deleted.
1314 ** \fBNOTE:\fP this only applies
1315 ** to maildir-style mailboxes. Setting it will have no effect on other
1318 ** It is similiar to the trash option.
1320 {"mark_old", DT_BOOL, R_BOTH, OPTMARKOLD, 1},
1323 ** Controls whether or not Mutt-ng marks \fInew\fP \fBunread\fP
1324 ** messages as \fIold\fP if you exit a mailbox without reading them.
1326 ** With this option \fIset\fP, the next time you start Mutt-ng, the messages
1327 ** will show up with an "O" next to them in the ``index'' menu,
1328 ** indicating that they are old.
1330 {"markers", DT_BOOL, R_PAGER, OPTMARKERS, 1},
1333 ** Controls the display of wrapped lines in the internal pager. If set, a
1334 ** ``\fT+\fP'' marker is displayed at the beginning of wrapped lines. Also see
1335 ** the ``$$smart_wrap'' variable.
1337 {"mask", DT_RX, R_NONE, UL &Mask, UL "!^\\.[^.]"},
1340 ** A regular expression used in the file browser, optionally preceded by
1341 ** the \fInot\fP operator ``\fT!\fP''. Only files whose names match this mask
1342 ** will be shown. The match is always case-sensitive.
1344 {"mbox", DT_PATH, R_BOTH, UL &Inbox, UL "~/mbox"},
1347 ** This specifies the folder into which read mail in your ``$$spoolfile''
1348 ** folder will be appended.
1350 {"operating_system", DT_STR, R_NONE, UL &OperatingSystem, 0},
1353 ** This specifies the operating system name for the \fTUser-Agent:\fP header field. If
1354 ** this is \fIunset\fP, it will be set to the operating system name that \fTuname(2)\fP
1355 ** returns. If \fTuname(2)\fP fails, ``UNIX'' will be used.
1357 ** It may, for example, look as: ``\fTmutt-ng 1.5.9i (Linux)\fP''.
1359 {"sidebar_boundary", DT_STR, R_BOTH, UL &SidebarBoundary, UL "." },
1362 ** When the sidebar is displayed and $$sidebar_shorten_hierarchy is \fIset\fP, this
1363 ** variable specifies the characters at which to split a folder name into
1364 ** ``hierarchy items.''
1366 {"sidebar_delim", DT_STR, R_BOTH, UL &SidebarDelim, UL "|"},
1369 ** This specifies the delimiter between the sidebar (if visible) and
1372 {"sidebar_visible", DT_BOOL, R_BOTH, OPTMBOXPANE, 0},
1375 ** This specifies whether or not to show the sidebar (a list of folders specified
1376 ** with the ``mailboxes'' command).
1378 {"sidebar_width", DT_NUM, R_BOTH, UL &SidebarWidth, 0},
1381 ** The width of the sidebar.
1383 {"sidebar_newmail_only", DT_BOOL, R_BOTH, OPTSIDEBARNEWMAILONLY, 0},
1386 ** If \fIset\fP, only folders with new mail will be shown in the sidebar.
1388 {"sidebar_number_format", DT_STR, R_BOTH, UL &SidebarNumberFormat, UL "%c%?n?(%n)?%?f?[%f]?"},
1391 ** This variable controls how message counts are printed when the sidebar
1392 ** is enabled. If this variable is \fIempty\fP (\fIand only if\fP), no numbers
1393 ** will be printed \fIand\fP mutt-ng won't frequently count mail (which
1394 ** may be a great speedup esp. with mbox-style mailboxes.)
1396 ** The following \fTprintf(3)\fP-like sequences are supported:
1399 ** .dt %c .dd Total number of messages.
1400 ** .dt %f .dd Number of flagged messages.
1401 ** .dt %n .dd Number of new messages.
1404 ** The \fT%f\fP and \fT%n\fP expandos may optionally be printed non-zero.
1406 {"sidebar_shorten_hierarchy", DT_BOOL, R_NONE, OPTSHORTENHIERARCHY, 0},
1409 ** When \fIset\fP, the ``hierarchy'' of the sidebar entries will be shortened
1410 ** only if they cannot be printed in full length (because ``$$sidebar_width''
1411 ** is set to a too low value). For example, if the newsgroup name
1412 ** ``de.alt.sysadmin.recovery'' doesn't fit on the screen, it'll get shortened
1413 ** ``d.a.s.recovery'' while ``de.alt.d0'' still would and thus will not get
1416 ** At which characters this compression is done is controled via the
1417 ** $$sidebar_boundary variable.
1419 {"mbox_type", DT_MAGIC, R_NONE, UL &DefaultMagic, M_MBOX},
1422 ** The default mailbox type used when creating new folders. May be any of
1423 ** \fTmbox\fP, \fTMMDF\fP, \fTMH\fP and \fTMaildir\fP.
1425 {"metoo", DT_BOOL, R_NONE, OPTMETOO, 0},
1428 ** If \fIunset\fP, Mutt-ng will remove your address (see the ``alternates''
1429 ** command) from the list of recipients when replying to a message.
1431 {"menu_context", DT_NUM, R_NONE, UL &MenuContext, 0},
1434 ** This variable controls the number of lines of context that are given
1435 ** when scrolling through menus. (Similar to ``$$pager_context''.)
1437 {"menu_move_off", DT_BOOL, R_NONE, OPTMENUMOVEOFF, 0},
1440 ** When \fIunset\fP, the bottom entry of menus will never scroll up past
1441 ** the bottom of the screen, unless there are less entries than lines.
1442 ** When \fIset\fP, the bottom entry may move off the bottom.
1444 {"menu_scroll", DT_BOOL, R_NONE, OPTMENUSCROLL, 0},
1447 ** When \fIset\fP, menus will be scrolled up or down one line when you
1448 ** attempt to move across a screen boundary. If \fIunset\fP, the screen
1449 ** is cleared and the next or previous page of the menu is displayed
1450 ** (useful for slow links to avoid many redraws).
1452 {"meta_key", DT_BOOL, R_NONE, OPTMETAKEY, 0},
1455 ** If \fIset\fP, forces Mutt-ng to interpret keystrokes with the high bit (bit 8)
1456 ** set as if the user had pressed the \fTESC\fP key and whatever key remains
1457 ** after having the high bit removed. For example, if the key pressed
1458 ** has an ASCII value of \fT0xf4\fP, then this is treated as if the user had
1459 ** pressed \fTESC\fP then ``\fTx\fP''. This is because the result of removing the
1460 ** high bit from ``\fT0xf4\fP'' is ``\fT0x74\fP'', which is the ASCII character
1463 {"mh_purge", DT_BOOL, R_NONE, OPTMHPURGE, 0},
1466 ** When \fIunset\fP, Mutt-ng will mimic mh's behaviour and rename deleted messages
1467 ** to \fI,<old file name>\fP in mh folders instead of really deleting
1468 ** them. If the variable is set, the message files will simply be
1471 {"mh_seq_flagged", DT_STR, R_NONE, UL &MhFlagged, UL "flagged"},
1474 ** The name of the MH sequence used for flagged messages.
1476 {"mh_seq_replied", DT_STR, R_NONE, UL &MhReplied, UL "replied"},
1479 ** The name of the MH sequence used to tag replied messages.
1481 {"mh_seq_unseen", DT_STR, R_NONE, UL &MhUnseen, UL "unseen"},
1484 ** The name of the MH sequence used for unseen messages.
1486 {"mime_forward", DT_QUAD, R_NONE, OPT_MIMEFWD, M_NO},
1489 ** When \fIset\fP, the message you are forwarding will be attached as a
1490 ** separate MIME part instead of included in the main body of the
1493 ** This is useful for forwarding MIME messages so the receiver
1494 ** can properly view the message as it was delivered to you. If you like
1495 ** to switch between MIME and not MIME from mail to mail, set this
1496 ** variable to ask-no or ask-yes.
1498 ** Also see ``$$forward_decode'' and ``$$mime_forward_decode''.
1500 {"mime_forward_decode", DT_BOOL, R_NONE, OPTMIMEFORWDECODE, 0},
1503 ** Controls the decoding of complex MIME messages into \fTtext/plain\fP when
1504 ** forwarding a message while ``$$mime_forward'' is \fIset\fP. Otherwise
1505 ** ``$$forward_decode'' is used instead.
1507 {"mime_forward_rest", DT_QUAD, R_NONE, OPT_MIMEFWDREST, M_YES},
1510 ** When forwarding multiple attachments of a MIME message from the recvattach
1511 ** menu, attachments which cannot be decoded in a reasonable manner will
1512 ** be attached to the newly composed message if this option is set.
1516 {"mime_subject", DT_SYN, R_NONE, UL "nntp_mime_subject", 0},
1517 {"nntp_mime_subject", DT_BOOL, R_NONE, OPTMIMESUBJECT, 1},
1520 ** Availability: NNTP
1523 ** If \fIunset\fP, an 8-bit ``\fTSubject:\fP'' header field in a news article
1524 ** will not be encoded according to RFC2047.
1526 ** \fBNote:\fP Only change this setting if you know what you are doing.
1531 {"mix_entry_format", DT_STR, R_NONE, UL &MixEntryFormat, UL "%4n %c %-16s %a"},
1534 ** Availability: Mixmaster
1537 ** This variable describes the format of a remailer line on the mixmaster
1538 ** chain selection screen. The following \fTprintf(3)\fP-like sequences are
1542 ** .dt %n .dd The running number on the menu.
1543 ** .dt %c .dd Remailer capabilities.
1544 ** .dt %s .dd The remailer's short name.
1545 ** .dt %a .dd The remailer's e-mail address.
1548 {"mixmaster", DT_PATH, R_NONE, UL &Mixmaster, UL MIXMASTER},
1551 ** Availability: Mixmaster
1554 ** This variable contains the path to the Mixmaster binary on your
1555 ** system. It is used with various sets of parameters to gather the
1556 ** list of known remailers, and to finally send a message through the
1560 {"move", DT_QUAD, R_NONE, OPT_MOVE, M_ASKNO},
1563 ** Controls whether or not Mutt-ng will move read messages
1564 ** from your spool mailbox to your ``$$mbox'' mailbox, or as a result of
1565 ** a ``$mbox-hook'' command.
1567 {"message_format", DT_STR, R_NONE, UL &MsgFmt, UL "%s"},
1570 ** This is the string displayed in the ``attachment'' menu for
1571 ** attachments of type \fTmessage/rfc822\fP. For a full listing of defined
1572 ** \fTprintf(3)\fP-like sequences see the section on ``$$index_format''.
1574 {"msgid_format", DT_STR, R_NONE, UL &MsgIdFormat, UL "%Y%m%d%h%M%s.G%P%p"},
1577 ** This is the format for the ``local part'' of the \fTMessage-Id:\fP header
1578 ** field generated by Mutt-ng. If this variable is empty, no \fTMessage-Id:\fP
1579 ** headers will be generated. The '%'
1580 ** character marks that certain data will be added to the string, similar to
1581 ** \fTprintf(3)\fP. The following characters are allowed:
1584 ** .dt %d .dd the current day of month
1585 ** .dt %h .dd the current hour
1586 ** .dt %m .dd the current month
1587 ** .dt %M .dd the current minute
1588 ** .dt %O .dd the current UNIX timestamp (octal)
1589 ** .dt %p .dd the process ID
1590 ** .dt %P .dd the current Message-ID prefix (a character rotating with
1591 ** every Message-ID being generated)
1592 ** .dt %r .dd a random integer value (decimal)
1593 ** .dt %R .dd a random integer value (hexadecimal)
1594 ** .dt %s .dd the current second
1595 ** .dt %T .dd the current UNIX timestamp (decimal)
1596 ** .dt %X .dd the current UNIX timestamp (hexadecimal)
1597 ** .dt %Y .dd the current year (Y2K compliant)
1598 ** .dt %% .dd the '%' character
1601 ** \fBNote:\fP Please only change this setting if you know what you are doing.
1602 ** Also make sure to consult RFC2822 to produce technically \fIvalid\fP strings.
1604 {"narrow_tree", DT_BOOL, R_TREE|R_INDEX, OPTNARROWTREE, 0},
1607 ** This variable, when \fIset\fP, makes the thread tree narrower, allowing
1608 ** deeper threads to fit on the screen.
1611 {"news_cache_dir", DT_SYN, R_NONE, UL "nntp_cache_dir", 0},
1612 {"nntp_cache_dir", DT_PATH, R_NONE, UL &NewsCacheDir, UL "~/.muttng"},
1615 ** Availability: NNTP
1618 ** This variable points to directory where Mutt-ng will cache news
1619 ** article headers. If \fIunset\fP, headers will not be saved at all
1620 ** and will be reloaded each time when you enter a newsgroup.
1622 ** As for the header caching in connection with IMAP and/or Maildir,
1623 ** this drastically increases speed and lowers traffic.
1625 {"news_server", DT_SYN, R_NONE, UL "nntp_host", 0},
1626 {"nntp_host", DT_STR, R_NONE, UL &NewsServer, 0},
1629 ** Availability: NNTP
1632 ** This variable specifies the name (or address) of the NNTP server to be used.
1635 ** defaults to the value specified via the environment variable
1636 ** \fT$$$NNTPSERVER\fP or contained in the file \fT/etc/nntpserver\fP.
1639 ** specify a username and an alternative port for each newsserver, e.g.
1641 ** \fT[nntp[s]://][username[:password]@]newsserver[:port]\fP
1643 ** \fBNote:\fP Using a password as shown and stored in a configuration file
1644 ** presents a security risk since the superuser of your machine may read it
1645 ** regardless of the file's permissions.
1647 {"newsrc", DT_SYN, R_NONE, UL "nntp_newsrc", 0},
1648 {"nntp_newsrc", DT_PATH, R_NONE, UL &NewsRc, UL "~/.newsrc"},
1651 ** Availability: NNTP
1654 ** This file contains information about subscribed newsgroup and
1655 ** articles read so far.
1657 ** To ease the use of multiple news servers, the following \fTprintf(3)\fP-style
1658 ** sequence is understood:
1661 ** %s newsserver name
1664 {"nntp_context", DT_NUM, R_NONE, UL &NntpContext, 1000},
1667 ** Availability: NNTP
1670 ** This variable controls how many news articles to cache per newsgroup
1671 ** (if caching is enabled, see $$news_cache_dir) and how many news articles
1672 ** to show in the ``index'' menu.
1674 ** If there're more articles than defined with $$nntp_context, all older ones
1675 ** will be removed/not shown in the index.
1677 {"nntp_load_description", DT_BOOL, R_NONE, OPTLOADDESC, 1},
1680 ** Availability: NNTP
1683 ** This variable controls whether or not descriptions for newsgroups
1684 ** are to be loaded when subscribing to a newsgroup.
1686 {"nntp_user", DT_STR, R_NONE, UL &NntpUser, UL ""},
1689 ** Availability: NNTP
1692 ** Your login name on the NNTP server. If \fIunset\fP and the server requires
1693 ** authentification, Mutt-ng will prompt you for your account name.
1695 {"nntp_pass", DT_STR, R_NONE, UL &NntpPass, UL ""},
1698 ** Availability: NNTP
1701 ** Your password for NNTP account.
1703 ** \fBNote:\fP Storing passwords in a configuration file
1704 ** presents a security risk since the superuser of your machine may read it
1705 ** regardless of the file's permissions.
1707 {"nntp_poll", DT_SYN, R_NONE, UL "nntp_mail_check", 0},
1708 {"nntp_mail_check", DT_NUM, R_NONE, UL &NewsPollTimeout, 60},
1711 ** Availability: NNTP
1714 ** The time in seconds until any operations on a newsgroup except posting a new
1715 ** article will cause a recheck for new news. If set to 0, Mutt-ng will
1716 ** recheck on each operation in index (stepping, read article, etc.).
1718 {"nntp_reconnect", DT_QUAD, R_NONE, OPT_NNTPRECONNECT, M_ASKYES},
1721 ** Availability: NNTP
1724 ** Controls whether or not Mutt-ng will try to reconnect to a newsserver when the
1725 ** was connection lost.
1728 {"pager", DT_PATH, R_NONE, UL &Pager, UL "builtin"},
1731 ** This variable specifies which pager you would like to use to view
1732 ** messages. ``builtin'' means to use the builtin pager, otherwise this
1733 ** variable should specify the pathname of the external pager you would
1736 ** Using an external pager may have some disadvantages: Additional
1737 ** keystrokes are necessary because you can't call Mutt-ng functions
1738 ** directly from the pager, and screen resizes cause lines longer than
1739 ** the screen width to be badly formatted in the help menu.
1741 {"pager_context", DT_NUM, R_NONE, UL &PagerContext, 0},
1744 ** This variable controls the number of lines of context that are given
1745 ** when displaying the next or previous page in the internal pager. By
1746 ** default, Mutt-ng will display the line after the last one on the screen
1747 ** at the top of the next page (0 lines of context).
1749 {"pager_format", DT_STR, R_PAGER, UL &PagerFmt, UL "-%Z- %C/%m: %-20.20n %s"},
1752 ** This variable controls the format of the one-line message ``status''
1753 ** displayed before each message in either the internal or an external
1754 ** pager. The valid sequences are listed in the ``$$index_format''
1757 {"pager_index_lines", DT_NUM, R_PAGER, UL &PagerIndexLines, 0},
1760 ** Determines the number of lines of a mini-index which is shown when in
1761 ** the pager. The current message, unless near the top or bottom of the
1762 ** folder, will be roughly one third of the way down this mini-index,
1763 ** giving the reader the context of a few messages before and after the
1764 ** message. This is useful, for example, to determine how many messages
1765 ** remain to be read in the current thread. One of the lines is reserved
1766 ** for the status bar from the index, so a \fIpager_index_lines\fP of 6
1767 ** will only show 5 lines of the actual index. A value of 0 results in
1768 ** no index being shown. If the number of messages in the current folder
1769 ** is less than \fIpager_index_lines\fP, then the index will only use as
1770 ** many lines as it needs.
1772 {"pager_stop", DT_BOOL, R_NONE, OPTPAGERSTOP, 0},
1775 ** When \fIset\fP, the internal-pager will \fBnot\fP move to the next message
1776 ** when you are at the end of a message and invoke the \fInext-page\fP
1779 {"crypt_autosign", DT_BOOL, R_NONE, OPTCRYPTAUTOSIGN, 0},
1782 ** Setting this variable will cause Mutt-ng to always attempt to
1783 ** cryptographically sign outgoing messages. This can be overridden
1784 ** by use of the \fIpgp-menu\fP, when signing is not required or
1785 ** encryption is requested as well. If ``$$smime_is_default'' is \fIset\fP,
1786 ** then OpenSSL is used instead to create S/MIME messages and settings can
1787 ** be overridden by use of the \fIsmime-menu\fP.
1790 {"crypt_autoencrypt", DT_BOOL, R_NONE, OPTCRYPTAUTOENCRYPT, 0},
1793 ** Setting this variable will cause Mutt-ng to always attempt to PGP
1794 ** encrypt outgoing messages. This is probably only useful in
1795 ** connection to the \fIsend-hook\fP command. It can be overridden
1796 ** by use of the \fIpgp-menu\fP, when encryption is not required or
1797 ** signing is requested as well. If ``$$smime_is_default'' is \fIset\fP,
1798 ** then OpenSSL is used instead to create S/MIME messages and
1799 ** settings can be overridden by use of the \fIsmime-menu\fP.
1802 {"pgp_ignore_subkeys", DT_BOOL, R_NONE, OPTPGPIGNORESUB, 1},
1805 ** Setting this variable will cause Mutt-ng to ignore OpenPGP subkeys. Instead,
1806 ** the principal key will inherit the subkeys' capabilities. \fIUnset\fP this
1807 ** if you want to play interesting key selection games.
1810 {"crypt_replyencrypt", DT_BOOL, R_NONE, OPTCRYPTREPLYENCRYPT, 1},
1813 ** If \fIset\fP, automatically PGP or OpenSSL encrypt replies to messages which are
1817 {"crypt_replysign", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGN, 0},
1820 ** If \fIset\fP, automatically PGP or OpenSSL sign replies to messages which are
1823 ** \fBNote:\fP this does not work on messages that are encrypted \fBand\fP signed!
1826 {"crypt_replysignencrypted", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGNENCRYPTED, 0},
1829 ** If \fIset\fP, automatically PGP or OpenSSL sign replies to messages
1830 ** which are encrypted. This makes sense in combination with
1831 ** ``$$crypt_replyencrypt'', because it allows you to sign all
1832 ** messages which are automatically encrypted. This works around
1833 ** the problem noted in ``$$crypt_replysign'', that Mutt-ng is not able
1834 ** to find out whether an encrypted message is also signed.
1837 {"crypt_timestamp", DT_BOOL, R_NONE, OPTCRYPTTIMESTAMP, 1},
1840 ** If \fIset\fP, Mutt-ng will include a time stamp in the lines surrounding
1841 ** PGP or S/MIME output, so spoofing such lines is more difficult.
1842 ** If you are using colors to mark these lines, and rely on these,
1843 ** you may \fIunset\fP this setting.
1846 {"pgp_use_gpg_agent", DT_BOOL, R_NONE, OPTUSEGPGAGENT, 0},
1849 ** If \fIset\fP, Mutt-ng will use a possibly-running gpg-agent process.
1852 {"crypt_verify_sig", DT_QUAD, R_NONE, OPT_VERIFYSIG, M_YES},
1855 ** If ``\fIyes\fP'', always attempt to verify PGP or S/MIME signatures.
1856 ** If ``\fIask\fP'', ask whether or not to verify the signature.
1857 ** If ``\fIno\fP'', never attempt to verify cryptographic signatures.
1860 {"smime_is_default", DT_BOOL, R_NONE, OPTSMIMEISDEFAULT, 0},
1863 ** The default behaviour of Mutt-ng is to use PGP on all auto-sign/encryption
1864 ** operations. To override and to use OpenSSL instead this must be \fIset\fP.
1866 ** However, this has no effect while replying, since Mutt-ng will automatically
1867 ** select the same application that was used to sign/encrypt the original
1870 ** (Note that this variable can be overridden by unsetting $$crypt_autosmime.)
1873 {"smime_ask_cert_label", DT_BOOL, R_NONE, OPTASKCERTLABEL, 1},
1876 ** This flag controls whether you want to be asked to enter a label
1877 ** for a certificate about to be added to the database or not. It is
1878 ** \fIset\fP by default.
1881 {"smime_decrypt_use_default_key", DT_BOOL, R_NONE, OPTSDEFAULTDECRYPTKEY, 1},
1884 ** If \fIset\fP (default) this tells Mutt-ng to use the default key for decryption. Otherwise,
1885 ** if manage multiple certificate-key-pairs, Mutt-ng will try to use the mailbox-address
1886 ** to determine the key to use. It will ask you to supply a key, if it can't find one.
1889 {"pgp_entry_format", DT_STR, R_NONE, UL &PgpEntryFormat, UL "%4n %t%f %4l/0x%k %-4a %2c %u"},
1892 ** This variable allows you to customize the PGP key selection menu to
1893 ** your personal taste. This string is similar to ``$$index_format'', but
1894 ** has its own set of \fTprintf(3)\fP-like sequences:
1897 ** .dt %n .dd number
1898 ** .dt %k .dd key id
1899 ** .dt %u .dd user id
1900 ** .dt %a .dd algorithm
1901 ** .dt %l .dd key length
1903 ** .dt %c .dd capabilities
1904 ** .dt %t .dd trust/validity of the key-uid association
1905 ** .dt %[<s>] .dd date of the key where <s> is an \fTstrftime(3)\fP expression
1910 {"pgp_good_sign", DT_RX, R_NONE, UL &PgpGoodSign, 0},
1913 ** If you assign a text to this variable, then a PGP signature is only
1914 ** considered verified if the output from $$pgp_verify_command contains
1915 ** the text. Use this variable if the exit code from the command is 0
1916 ** even for bad signatures.
1919 {"pgp_check_exit", DT_BOOL, R_NONE, OPTPGPCHECKEXIT, 1},
1922 ** If \fIset\fP, Mutt-ng will check the exit code of the PGP subprocess when
1923 ** signing or encrypting. A non-zero exit code means that the
1924 ** subprocess failed.
1927 {"pgp_long_ids", DT_BOOL, R_NONE, OPTPGPLONGIDS, 0},
1930 ** If \fIset\fP, use 64 bit PGP key IDs. \fIUnset\fP uses the normal 32 bit Key IDs.
1933 {"pgp_retainable_sigs", DT_BOOL, R_NONE, OPTPGPRETAINABLESIG, 0},
1936 ** If \fIset\fP, signed and encrypted messages will consist of nested
1937 ** multipart/signed and multipart/encrypted body parts.
1939 ** This is useful for applications like encrypted and signed mailing
1940 ** lists, where the outer layer (multipart/encrypted) can be easily
1941 ** removed, while the inner multipart/signed part is retained.
1944 {"pgp_autoinline", DT_BOOL, R_NONE, OPTPGPAUTOINLINE, 0},
1947 ** This option controls whether Mutt-ng generates old-style inline
1948 ** (traditional) PGP encrypted or signed messages under certain
1949 ** circumstances. This can be overridden by use of the \fIpgp-menu\fP,
1950 ** when inline is not required.
1952 ** Note that Mutt-ng might automatically use PGP/MIME for messages
1953 ** which consist of more than a single MIME part. Mutt-ng can be
1954 ** configured to ask before sending PGP/MIME messages when inline
1955 ** (traditional) would not work.
1956 ** See also: ``$$pgp_mime_auto''.
1958 ** Also note that using the old-style PGP message format is \fBstrongly\fP
1959 ** \fBdeprecated\fP.
1962 {"pgp_replyinline", DT_BOOL, R_NONE, OPTPGPREPLYINLINE, 0},
1965 ** Setting this variable will cause Mutt-ng to always attempt to
1966 ** create an inline (traditional) message when replying to a
1967 ** message which is PGP encrypted/signed inline. This can be
1968 ** overridden by use of the \fIpgp-menu\fP, when inline is not
1969 ** required. This option does not automatically detect if the
1970 ** (replied-to) message is inline; instead it relies on Mutt-ng
1971 ** internals for previously checked/flagged messages.
1973 ** Note that Mutt-ng might automatically use PGP/MIME for messages
1974 ** which consist of more than a single MIME part. Mutt-ng can be
1975 ** configured to ask before sending PGP/MIME messages when inline
1976 ** (traditional) would not work.
1977 ** See also: ``$$pgp_mime_auto''.
1979 ** Also note that using the old-style PGP message format is \fBstrongly\fP
1980 ** \fBdeprecated\fP.
1984 {"pgp_show_unusable", DT_BOOL, R_NONE, OPTPGPSHOWUNUSABLE, 1},
1987 ** If \fIset\fP, Mutt-ng will display non-usable keys on the PGP key selection
1988 ** menu. This includes keys which have been revoked, have expired, or
1989 ** have been marked as ``disabled'' by the user.
1992 {"pgp_sign_as", DT_STR, R_NONE, UL &PgpSignAs, 0},
1995 ** If you have more than one key pair, this option allows you to specify
1996 ** which of your private keys to use. It is recommended that you use the
1997 ** keyid form to specify your key (e.g., ``\fT0x00112233\fP'').
2000 {"pgp_strict_enc", DT_BOOL, R_NONE, OPTPGPSTRICTENC, 1},
2003 ** If \fIset\fP, Mutt-ng will automatically encode PGP/MIME signed messages as
2004 ** \fTquoted-printable\fP. Please note that unsetting this variable may
2005 ** lead to problems with non-verifyable PGP signatures, so only change
2006 ** this if you know what you are doing.
2009 {"pgp_timeout", DT_NUM, R_NONE, UL &PgpTimeout, 300},
2012 ** The number of seconds after which a cached passphrase will expire if
2013 ** not used. Default: 300.
2016 {"pgp_sort_keys", DT_SORT|DT_SORT_KEYS, R_NONE, UL &PgpSortKeys, SORT_ADDRESS},
2019 ** Specifies how the entries in the ``pgp keys'' menu are sorted. The
2020 ** following are legal values:
2023 ** .dt address .dd sort alphabetically by user id
2024 ** .dt keyid .dd sort alphabetically by key id
2025 ** .dt date .dd sort by key creation date
2026 ** .dt trust .dd sort by the trust of the key
2029 ** If you prefer reverse order of the above values, prefix it with
2033 {"pgp_mime_auto", DT_QUAD, R_NONE, OPT_PGPMIMEAUTO, M_ASKYES},
2036 ** This option controls whether Mutt-ng will prompt you for
2037 ** automatically sending a (signed/encrypted) message using
2038 ** PGP/MIME when inline (traditional) fails (for any reason).
2040 ** Also note that using the old-style PGP message format is \fBstrongly\fP
2041 ** \fBdeprecated\fP.
2044 {"pgp_auto_decode", DT_BOOL, R_NONE, OPTPGPAUTODEC, 0},
2047 ** If \fIset\fP, Mutt-ng will automatically attempt to decrypt traditional PGP
2048 ** messages whenever the user performs an operation which ordinarily would
2049 ** result in the contents of the message being operated on. For example,
2050 ** if the user displays a pgp-traditional message which has not been manually
2051 ** checked with the check-traditional-pgp function, Mutt-ng will automatically
2052 ** check the message for traditional pgp.
2055 /* XXX Default values! */
2057 {"pgp_decode_command", DT_STR, R_NONE, UL &PgpDecodeCommand, 0},
2060 ** This format strings specifies a command which is used to decode
2061 ** application/pgp attachments.
2063 ** The PGP command formats have their own set of \fTprintf(3)\fP-like sequences:
2066 ** .dt %p .dd Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
2067 ** string otherwise. Note: This may be used with a %? construct.
2068 ** .dt %f .dd Expands to the name of a file containing a message.
2069 ** .dt %s .dd Expands to the name of a file containing the signature part
2070 ** . of a multipart/signed attachment when verifying it.
2071 ** .dt %a .dd The value of $$pgp_sign_as.
2072 ** .dt %r .dd One or more key IDs.
2075 ** For examples on how to configure these formats for the various versions
2076 ** of PGP which are floating around, see the pgp*.rc and gpg.rc files in
2077 ** the \fTsamples/\fP subdirectory which has been installed on your system
2078 ** alongside the documentation.
2081 {"pgp_getkeys_command", DT_STR, R_NONE, UL &PgpGetkeysCommand, 0},
2084 ** This command is invoked whenever Mutt-ng will need public key information.
2085 ** \fT%r\fP is the only \fTprintf(3)\fP-like sequence used with this format.
2088 {"pgp_verify_command", DT_STR, R_NONE, UL &PgpVerifyCommand, 0},
2091 ** This command is used to verify PGP signatures.
2094 {"pgp_decrypt_command", DT_STR, R_NONE, UL &PgpDecryptCommand, 0},
2097 ** This command is used to decrypt a PGP encrypted message.
2100 {"pgp_clearsign_command", DT_STR, R_NONE, UL &PgpClearSignCommand, 0},
2103 ** This format is used to create a old-style ``clearsigned'' PGP message.
2105 ** Note that the use of this format is \fBstrongly\fP \fBdeprecated\fP.
2108 {"pgp_sign_command", DT_STR, R_NONE, UL &PgpSignCommand, 0},
2111 ** This command is used to create the detached PGP signature for a
2112 ** multipart/signed PGP/MIME body part.
2115 {"pgp_encrypt_sign_command", DT_STR, R_NONE, UL &PgpEncryptSignCommand, 0},
2118 ** This command is used to both sign and encrypt a body part.
2121 {"pgp_encrypt_only_command", DT_STR, R_NONE, UL &PgpEncryptOnlyCommand, 0},
2124 ** This command is used to encrypt a body part without signing it.
2127 {"pgp_import_command", DT_STR, R_NONE, UL &PgpImportCommand, 0},
2130 ** This command is used to import a key from a message into
2131 ** the user's public key ring.
2134 {"pgp_export_command", DT_STR, R_NONE, UL &PgpExportCommand, 0},
2137 ** This command is used to export a public key from the user's
2141 {"pgp_verify_key_command", DT_STR, R_NONE, UL &PgpVerifyKeyCommand, 0},
2144 ** This command is used to verify key information from the key selection
2148 {"pgp_list_secring_command", DT_STR, R_NONE, UL &PgpListSecringCommand, 0},
2151 ** This command is used to list the secret key ring's contents. The
2152 ** output format must be analogous to the one used by
2153 ** \fTgpg --list-keys --with-colons\fP.
2155 ** This format is also generated by the \fTpgpring\fP utility which comes
2159 {"pgp_list_pubring_command", DT_STR, R_NONE, UL &PgpListPubringCommand, 0},
2162 ** This command is used to list the public key ring's contents. The
2163 ** output format must be analogous to the one used by
2164 ** \fTgpg --list-keys --with-colons\fP.
2166 ** This format is also generated by the \fTpgpring\fP utility which comes
2170 {"forward_decrypt", DT_BOOL, R_NONE, OPTFORWDECRYPT, 1},
2173 ** Controls the handling of encrypted messages when forwarding a message.
2174 ** When \fIset\fP, the outer layer of encryption is stripped off. This
2175 ** variable is only used if ``$$mime_forward'' is \fIset\fP and
2176 ** ``$$mime_forward_decode'' is \fIunset\fP.
2179 {"smime_timeout", DT_NUM, R_NONE, UL &SmimeTimeout, 300},
2182 ** The number of seconds after which a cached passphrase will expire if
2186 {"smime_encrypt_with", DT_STR, R_NONE, UL &SmimeCryptAlg, 0},
2189 ** This sets the algorithm that should be used for encryption.
2190 ** Valid choices are ``\fTdes\fP'', ``\fTdes3\fP'', ``\fTrc2-40\fP'',
2191 ** ``\fTrc2-64\fP'', ``\frc2-128\fP''.
2193 ** If \fIunset\fP ``\fI3des\fP'' (TripleDES) is used.
2196 {"smime_keys", DT_PATH, R_NONE, UL &SmimeKeys, 0},
2199 ** Since there is no pubring/secring as with PGP, Mutt-ng has to handle
2200 ** storage ad retrieval of keys/certs by itself. This is very basic right now,
2201 ** and stores keys and certificates in two different directories, both
2202 ** named as the hash-value retrieved from OpenSSL. There is an index file
2203 ** which contains mailbox-address keyid pair, and which can be manually
2204 ** edited. This one points to the location of the private keys.
2207 {"smime_ca_location", DT_PATH, R_NONE, UL &SmimeCALocation, 0},
2210 ** This variable contains the name of either a directory, or a file which
2211 ** contains trusted certificates for use with OpenSSL.
2214 {"smime_certificates", DT_PATH, R_NONE, UL &SmimeCertificates, 0},
2217 ** Since there is no pubring/secring as with PGP, Mutt-ng has to handle
2218 ** storage and retrieval of keys by itself. This is very basic right
2219 ** now, and keys and certificates are stored in two different
2220 ** directories, both named as the hash-value retrieved from
2221 ** OpenSSL. There is an index file which contains mailbox-address
2222 ** keyid pairs, and which can be manually edited. This one points to
2223 ** the location of the certificates.
2226 {"smime_decrypt_command", DT_STR, R_NONE, UL &SmimeDecryptCommand, 0},
2229 ** This format string specifies a command which is used to decrypt
2230 ** \fTapplication/x-pkcs7-mime\fP attachments.
2232 ** The OpenSSL command formats have their own set of \fTprintf(3)\fP-like sequences
2233 ** similar to PGP's:
2236 ** .dt %f .dd Expands to the name of a file containing a message.
2237 ** .dt %s .dd Expands to the name of a file containing the signature part
2238 ** . of a multipart/signed attachment when verifying it.
2239 ** .dt %k .dd The key-pair specified with $$smime_default_key
2240 ** .dt %c .dd One or more certificate IDs.
2241 ** .dt %a .dd The algorithm used for encryption.
2242 ** .dt %C .dd CA location: Depending on whether $$smime_ca_location
2243 ** . points to a directory or file, this expands to
2244 ** . "-CApath $$smime_ca_location" or "-CAfile $$smime_ca_location".
2247 ** For examples on how to configure these formats, see the smime.rc in
2248 ** the \fTsamples/\fP subdirectory which has been installed on your system
2249 ** alongside the documentation.
2252 {"smime_verify_command", DT_STR, R_NONE, UL &SmimeVerifyCommand, 0},
2255 ** This command is used to verify S/MIME signatures of type \fTmultipart/signed\fP.
2258 {"smime_verify_opaque_command", DT_STR, R_NONE, UL &SmimeVerifyOpaqueCommand, 0},
2261 ** This command is used to verify S/MIME signatures of type
2262 ** \fTapplication/x-pkcs7-mime\fP.
2265 {"smime_sign_command", DT_STR, R_NONE, UL &SmimeSignCommand, 0},
2268 ** This command is used to created S/MIME signatures of type
2269 ** \fTmultipart/signed\fP, which can be read by all mail clients.
2272 {"smime_sign_opaque_command", DT_STR, R_NONE, UL &SmimeSignOpaqueCommand, 0},
2275 ** This command is used to created S/MIME signatures of type
2276 ** \fTapplication/x-pkcs7-signature\fP, which can only be handled by mail
2277 ** clients supporting the S/MIME extension.
2280 {"smime_encrypt_command", DT_STR, R_NONE, UL &SmimeEncryptCommand, 0},
2283 ** This command is used to create encrypted S/MIME messages.
2286 {"smime_pk7out_command", DT_STR, R_NONE, UL &SmimePk7outCommand, 0},
2289 ** This command is used to extract PKCS7 structures of S/MIME signatures,
2290 ** in order to extract the public X509 certificate(s).
2293 {"smime_get_cert_command", DT_STR, R_NONE, UL &SmimeGetCertCommand, 0},
2296 ** This command is used to extract X509 certificates from a PKCS7 structure.
2299 {"smime_get_signer_cert_command", DT_STR, R_NONE, UL &SmimeGetSignerCertCommand, 0},
2302 ** This command is used to extract only the signers X509 certificate from a S/MIME
2303 ** signature, so that the certificate's owner may get compared to the
2304 ** email's ``\fTFrom:\fP'' header field.
2307 {"smime_import_cert_command", DT_STR, R_NONE, UL &SmimeImportCertCommand, 0},
2310 ** This command is used to import a certificate via \fTsmime_keysng\fP.
2313 {"smime_get_cert_email_command", DT_STR, R_NONE, UL &SmimeGetCertEmailCommand, 0},
2316 ** This command is used to extract the mail address(es) used for storing
2317 ** X509 certificates, and for verification purposes (to check whether the
2318 ** certificate was issued for the sender's mailbox).
2321 {"smime_default_key", DT_STR, R_NONE, UL &SmimeDefaultKey, 0},
2324 ** This is the default key-pair to use for signing. This must be set to the
2325 ** keyid (the hash-value that OpenSSL generates) to work properly
2328 #if defined(USE_LIBESMTP)
2329 {"smtp_auth_username", DT_STR, R_NONE, UL &SmtpAuthUser, 0},
2332 ** Availability: SMTP
2335 ** Defines the username to use with SMTP AUTH. Setting this variable will
2336 ** cause Mutt-ng to attempt to use SMTP AUTH when sending.
2338 {"smtp_auth_password", DT_STR, R_NONE, UL &SmtpAuthPass, 0},
2341 ** Availability: SMTP
2344 ** Defines the password to use with SMTP AUTH. If ``$$smtp_auth_username''
2345 ** is set, but this variable is not, you will be prompted for a password
2348 ** \fBNote:\fP Storing passwords in a configuration file
2349 ** presents a security risk since the superuser of your machine may read it
2350 ** regardless of the file's permissions.
2352 {"smtp_host", DT_STR, R_NONE, UL &SmtpHost, 0},
2355 ** Availability: SMTP
2358 ** Defines the SMTP host which will be used to deliver mail, as opposed
2359 ** to invoking the sendmail binary. Setting this variable overrides the
2360 ** value of ``$$sendmail'', and any associated variables.
2362 {"smtp_port", DT_NUM, R_NONE, UL &SmtpPort, 25},
2365 ** Availability: SMTP
2368 ** Defines the port that the SMTP host is listening on for mail delivery.
2369 ** Must be specified as a number.
2371 ** Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP
2372 ** servers will probably desire 587, the mail submission port.
2375 #if defined(USE_SSL)||defined(USE_NSS)||defined(USE_GNUTLS)
2377 {"ssl_client_cert", DT_PATH, R_NONE, UL &SslClientCert, 0},
2380 ** Availability: SSL
2383 ** The file containing a client certificate and its associated private
2387 # if defined(USE_SSL)||defined(USE_GNUTLS)
2388 {"ssl_starttls", DT_QUAD, R_NONE, OPT_SSLSTARTTLS, M_YES},
2391 ** Availability: SSL or GNUTLS
2394 ** If \fIset\fP (the default), Mutt-ng will attempt to use STARTTLS on servers
2395 ** advertising the capability. When \fIunset\fP, Mutt-ng will not attempt to
2396 ** use STARTTLS regardless of the server's capabilities.
2399 {"certificate_file", DT_PATH, R_NONE, UL &SslCertFile, UL "~/.mutt_certificates"},
2402 ** Availability: SSL or NSS or GNUTLS
2405 ** This variable specifies the file where the certificates you trust
2406 ** are saved. When an unknown certificate is encountered, you are asked
2407 ** if you accept it or not. If you accept it, the certificate can also
2408 ** be saved in this file and further connections are automatically
2411 ** You can also manually add CA certificates in this file. Any server
2412 ** certificate that is signed with one of these CA certificates are
2413 ** also automatically accepted.
2415 ** Example: \fTset certificate_file=~/.muttng/certificates\fP
2418 {"ssl_usesystemcerts", DT_BOOL, R_NONE, OPTSSLSYSTEMCERTS, 1},
2421 ** Availability: SSL or NSS
2424 ** If set to \fIyes\fP, Mutt-ng will use CA certificates in the
2425 ** system-wide certificate store when checking if server certificate
2426 ** is signed by a trusted CA.
2428 {"entropy_file", DT_PATH, R_NONE, UL &SslEntropyFile, 0},
2431 ** Availability: SSL or NSS
2434 ** The file which includes random data that is used to initialize SSL
2435 ** library functions.
2437 {"ssl_use_sslv2", DT_BOOL, R_NONE, OPTSSLV2, 1},
2440 ** Availability: SSL or NSS
2443 ** This variables specifies whether to attempt to use SSLv2 in the
2444 ** SSL authentication process.
2447 {"ssl_use_sslv3", DT_BOOL, R_NONE, OPTSSLV3, 1},
2450 ** Availability: SSL or NSS or GNUTLS
2453 ** This variables specifies whether to attempt to use SSLv3 in the
2454 ** SSL authentication process.
2456 {"ssl_use_tlsv1", DT_BOOL, R_NONE, OPTTLSV1, 1},
2459 ** Availability: SSL or NSS or GNUTLS
2462 ** This variables specifies whether to attempt to use TLSv1 in the
2463 ** SSL authentication process.
2466 {"ssl_min_dh_prime_bits", DT_NUM, R_NONE, UL &SslDHPrimeBits, 0},
2469 ** Availability: GNUTLS
2472 ** This variable specifies the minimum acceptable prime size (in bits)
2473 ** for use in any Diffie-Hellman key exchange. A value of 0 will use
2474 ** the default from the GNUTLS library.
2476 {"ssl_ca_certificates_file", DT_PATH, R_NONE, UL &SslCACertFile, 0},
2479 ** This variable specifies a file containing trusted CA certificates.
2480 ** Any server certificate that is signed with one of these CA
2481 ** certificates are also automatically accepted.
2483 ** Example: \fTset ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt\fP
2487 {"pipe_split", DT_BOOL, R_NONE, OPTPIPESPLIT, 0},
2490 ** Used in connection with the \fIpipe-message\fP command and the ``tag-
2491 ** prefix'' or ``tag-prefix-cond'' operators.
2492 ** If this variable is \fIunset\fP, when piping a list of
2493 ** tagged messages Mutt-ng will concatenate the messages and will pipe them
2494 ** as a single folder. When \fIset\fP, Mutt-ng will pipe the messages one by one.
2495 ** In both cases the messages are piped in the current sorted order,
2496 ** and the ``$$pipe_sep'' separator is added after each message.
2498 {"pipe_decode", DT_BOOL, R_NONE, OPTPIPEDECODE, 0},
2501 ** Used in connection with the \fIpipe-message\fP command. When \fIunset\fP,
2502 ** Mutt-ng will pipe the messages without any preprocessing. When \fIset\fP, Mutt-ng
2503 ** will weed headers and will attempt to PGP/MIME decode the messages
2506 {"pipe_sep", DT_STR, R_NONE, UL &PipeSep, UL "\n"},
2509 ** The separator to add between messages when piping a list of tagged
2510 ** messages to an external Unix command.
2513 {"pop_authenticators", DT_STR, R_NONE, UL &PopAuthenticators, UL 0},
2516 ** Availability: POP
2519 ** This is a colon-delimited list of authentication methods Mutt-ng may
2520 ** attempt to use to log in to an POP server, in the order Mutt-ng should
2521 ** try them. Authentication methods are either ``\fTuser\fP'', ``\fTapop\fP''
2522 ** or any SASL mechanism, eg ``\fTdigest-md5\fP'', ``\fTgssapi\fP'' or ``\fTcram-md5\fP''.
2524 ** This parameter is case-insensitive. If this parameter is \fIunset\fP
2525 ** (the default) Mutt-ng will try all available methods, in order from
2526 ** most-secure to least-secure.
2528 ** Example: \fTset pop_authenticators="digest-md5:apop:user"\fP
2530 {"pop_auth_try_all", DT_BOOL, R_NONE, OPTPOPAUTHTRYALL, 1},
2533 ** Availability: POP
2536 ** If \fIset\fP, Mutt-ng will try all available methods. When \fIunset\fP, Mutt-ng will
2537 ** only fall back to other authentication methods if the previous
2538 ** methods are unavailable. If a method is available but authentication
2539 ** fails, Mutt-ng will not connect to the POP server.
2541 {"pop_checkinterval", DT_SYN, R_NONE, UL "pop_mail_check", 0},
2542 {"pop_mail_check", DT_NUM, R_NONE, UL &PopCheckTimeout, 60},
2545 ** Availability: POP
2548 ** This variable configures how often (in seconds) POP should look for
2551 {"pop_delete", DT_QUAD, R_NONE, OPT_POPDELETE, M_ASKNO},
2554 ** Availability: POP
2557 ** If \fIset\fP, Mutt-ng will delete successfully downloaded messages from the POP
2558 ** server when using the ``fetch-mail'' function. When \fIunset\fP, Mutt-ng will
2559 ** download messages but also leave them on the POP server.
2561 {"pop_host", DT_STR, R_NONE, UL &PopHost, UL ""},
2564 ** Availability: POP
2567 ** The name of your POP server for the ``fetch-mail'' function. You
2568 ** can also specify an alternative port, username and password, i.e.:
2570 ** \fT[pop[s]://][username[:password]@]popserver[:port]\fP
2572 ** \fBNote:\fP Storing passwords in a configuration file
2573 ** presents a security risk since the superuser of your machine may read it
2574 ** regardless of the file's permissions.
2576 {"pop_last", DT_BOOL, R_NONE, OPTPOPLAST, 0},
2579 ** Availability: POP
2582 ** If this variable is \fIset\fP, Mutt-ng will try to use the ``\fTLAST\fP'' POP command
2583 ** for retrieving only unread messages from the POP server when using
2584 ** the ``fetch-mail'' function.
2586 {"pop_reconnect", DT_QUAD, R_NONE, OPT_POPRECONNECT, M_ASKYES},
2589 ** Availability: POP
2592 ** Controls whether or not Mutt-ng will try to reconnect to a POP server when the
2593 ** connection is lost.
2595 {"pop_user", DT_STR, R_NONE, UL &PopUser, 0},
2598 ** Availability: POP
2601 ** Your login name on the POP server.
2603 ** This variable defaults to your user name on the local machine.
2605 {"pop_pass", DT_STR, R_NONE, UL &PopPass, UL ""},
2608 ** Availability: POP
2611 ** Specifies the password for your POP account. If \fIunset\fP, Mutt-ng will
2612 ** prompt you for your password when you open POP mailbox.
2614 ** \fBNote:\fP Storing passwords in a configuration file
2615 ** presents a security risk since the superuser of your machine may read it
2616 ** regardless of the file's permissions.
2618 #endif /* USE_POP */
2619 {"post_indent_string", DT_STR, R_NONE, UL &PostIndentString, UL ""},
2622 ** Similar to the ``$$attribution'' variable, Mutt-ng will append this
2623 ** string after the inclusion of a message which is being replied to.
2626 {"post_moderated", DT_SYN, R_NONE, UL "nntp_post_moderated", 0 },
2627 {"nntp_post_moderated", DT_QUAD, R_NONE, OPT_TOMODERATED, M_ASKYES},
2630 ** Availability: NNTP
2633 ** If set to \fIyes\fP, Mutt-ng will post articles to newsgroup that have
2634 ** not permissions to post (e.g. moderated).
2636 ** \fBNote:\fP if the newsserver
2637 ** does not support posting to that newsgroup or a group is totally read-only, that
2638 ** posting will not have any effect.
2641 {"postpone", DT_QUAD, R_NONE, OPT_POSTPONE, M_ASKYES},
2644 ** Controls whether or not messages are saved in the ``$$postponed''
2645 ** mailbox when you elect not to send immediately.
2647 {"postponed", DT_PATH, R_NONE, UL &Postponed, UL "~/postponed"},
2650 ** Mutt-ng allows you to indefinitely ``$postpone sending a message'' which
2651 ** you are editing. When you choose to postpone a message, Mutt-ng saves it
2652 ** in the mailbox specified by this variable. Also see the ``$$postpone''
2656 {"preconnect", DT_STR, R_NONE, UL &Preconnect, UL 0},
2659 ** If \fIset\fP, a shell command to be executed if Mutt-ng fails to establish
2660 ** a connection to the server. This is useful for setting up secure
2661 ** connections, e.g. with \fTssh(1)\fP. If the command returns a nonzero
2662 ** status, Mutt-ng gives up opening the server. Example:
2664 ** \fTpreconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net
2665 ** sleep 20 < /dev/null > /dev/null"\fP
2667 ** Mailbox ``foo'' on mailhost.net can now be reached
2668 ** as ``{localhost:1234}foo''.
2670 ** \fBNote:\fP For this example to work, you must be able to log in to the
2671 ** remote machine without having to enter a password.
2673 #endif /* USE_SOCKET */
2674 {"print", DT_QUAD, R_NONE, OPT_PRINT, M_ASKNO},
2677 ** Controls whether or not Mutt-ng really prints messages.
2678 ** This is set to \fIask-no\fP by default, because some people
2679 ** accidentally hit ``p'' often.
2681 {"print_command", DT_PATH, R_NONE, UL &PrintCmd, UL "lpr"},
2684 ** This specifies the command pipe that should be used to print messages.
2686 {"print_decode", DT_BOOL, R_NONE, OPTPRINTDECODE, 1},
2689 ** Used in connection with the print-message command. If this
2690 ** option is \fIset\fP, the message is decoded before it is passed to the
2691 ** external command specified by $$print_command. If this option
2692 ** is \fIunset\fP, no processing will be applied to the message when
2693 ** printing it. The latter setting may be useful if you are using
2694 ** some advanced printer filter which is able to properly format
2695 ** e-mail messages for printing.
2697 {"print_split", DT_BOOL, R_NONE, OPTPRINTSPLIT, 0},
2700 ** Used in connection with the print-message command. If this option
2701 ** is \fIset\fP, the command specified by $$print_command is executed once for
2702 ** each message which is to be printed. If this option is \fIunset\fP,
2703 ** the command specified by $$print_command is executed only once, and
2704 ** all the messages are concatenated, with a form feed as the message
2707 ** Those who use the \fTenscript(1)\fP program's mail-printing mode will
2708 ** most likely want to set this option.
2710 {"prompt_after", DT_BOOL, R_NONE, OPTPROMPTAFTER, 1},
2713 ** If you use an \fIexternal\fP ``$$pager'', setting this variable will
2714 ** cause Mutt-ng to prompt you for a command when the pager exits rather
2715 ** than returning to the index menu. If \fIunset\fP, Mutt-ng will return to the
2716 ** index menu when the external pager exits.
2718 {"query_command", DT_PATH, R_NONE, UL &QueryCmd, UL ""},
2721 ** This specifies the command that Mutt-ng will use to make external address
2722 ** queries. The string should contain a \fT%s\fP, which will be substituted
2723 ** with the query string the user types. See ``$query'' for more
2726 {"quit", DT_QUAD, R_NONE, OPT_QUIT, M_YES},
2729 ** This variable controls whether ``quit'' and ``exit'' actually quit
2730 ** from Mutt-ng. If it set to \fIyes\fP, they do quit, if it is set to \fIno\fP, they
2731 ** have no effect, and if it is set to \fIask-yes\fP or \fIask-no\fP, you are
2732 ** prompted for confirmation when you try to quit.
2734 {"quote_empty", DT_BOOL, R_NONE, OPTQUOTEEMPTY, 1},
2737 ** Controls whether or not empty lines will be quoted using
2738 ** ``$indent_string''.
2740 {"quote_quoted", DT_BOOL, R_NONE, OPTQUOTEQUOTED, 0},
2743 ** Controls how quoted lines will be quoted. If \fIset\fP, one quote
2744 ** character will be added to the end of existing prefix. Otherwise,
2745 ** quoted lines will be prepended by ``$indent_string''.
2747 {"quote_regexp", DT_RX, R_PAGER, UL &QuoteRegexp, UL "^([ \t]*[|>:}#])+"},
2750 ** A regular expression used in the internal-pager to determine quoted
2751 ** sections of text in the body of a message.
2753 ** \fBNote:\fP In order to use the \fIquoted\fP\fBx\fP patterns in the
2754 ** internal pager, you need to set this to a regular expression that
2755 ** matches \fIexactly\fP the quote characters at the beginning of quoted
2758 {"read_inc", DT_NUM, R_NONE, UL &ReadInc, 10},
2761 ** If set to a value greater than 0, Mutt-ng will display which message it
2762 ** is currently on when reading a mailbox. The message is printed after
2763 ** \fIread_inc\fP messages have been read (e.g., if set to 25, Mutt-ng will
2764 ** print a message when it reads message 25, and then again when it gets
2765 ** to message 50). This variable is meant to indicate progress when
2766 ** reading large mailboxes which may take some time.
2767 ** When set to 0, only a single message will appear before the reading
2770 ** Also see the ``$$write_inc'' variable.
2772 {"read_only", DT_BOOL, R_NONE, OPTREADONLY, 0},
2775 ** If set, all folders are opened in read-only mode.
2777 {"realname", DT_STR, R_BOTH, UL &Realname, 0},
2780 ** This variable specifies what ``real'' or ``personal'' name should be used
2781 ** when sending messages.
2783 ** By default, this is the GECOS field from \fT/etc/passwd\fP.
2786 ** variable will \fInot\fP be used when the user has set a real name
2787 ** in the $$from variable.
2789 {"recall", DT_QUAD, R_NONE, OPT_RECALL, M_ASKYES},
2792 ** Controls whether or not Mutt-ng recalls postponed messages
2793 ** when composing a new message. Also see ``$$postponed''.
2795 ** Setting this variable to \fIyes\fP is not generally useful, and thus not
2798 {"record", DT_PATH, R_NONE, UL &Outbox, UL ""},
2801 ** This specifies the file into which your outgoing messages should be
2802 ** appended. (This is meant as the primary method for saving a copy of
2803 ** your messages, but another way to do this is using the ``$my_hdr''
2804 ** command to create a \fTBcc:\fP header field with your email address in it.)
2806 ** The value of \fI$$record\fP is overridden by the ``$$force_name'' and
2807 ** ``$$save_name'' variables, and the ``$fcc-hook'' command.
2809 {"reply_regexp", DT_RX, R_INDEX|R_RESORT, UL &ReplyRegexp, UL "^(re([\\[0-9\\]+])*|aw):[ \t]*"},
2812 ** A regular expression used to recognize reply messages when threading
2813 ** and replying. The default value corresponds to the English ``Re:'' and
2814 ** the German ``Aw:''.
2816 {"reply_self", DT_BOOL, R_NONE, OPTREPLYSELF, 0},
2819 ** If \fIunset\fP and you are replying to a message sent by you, Mutt-ng will
2820 ** assume that you want to reply to the recipients of that message rather
2821 ** than to yourself.
2823 {"reply_to", DT_QUAD, R_NONE, OPT_REPLYTO, M_ASKYES},
2826 ** If \fIset\fP, when replying to a message, Mutt-ng will use the address listed
2827 ** in the ``\fTReply-To:\fP'' header field as the recipient of the reply. If \fIunset\fP,
2828 ** it will use the address in the ``\fTFrom:\fP'' header field instead.
2831 ** option is useful for reading a mailing list that sets the ``\fTReply-To:\fP''
2832 ** header field to the list address and you want to send a private
2833 ** message to the author of a message.
2835 {"resolve", DT_BOOL, R_NONE, OPTRESOLVE, 1},
2838 ** When set, the cursor will be automatically advanced to the next
2839 ** (possibly undeleted) message whenever a command that modifies the
2840 ** current message is executed.
2842 {"reverse_alias", DT_BOOL, R_BOTH, OPTREVALIAS, 0},
2845 ** This variable controls whether or not Mutt-ng will display the ``personal''
2846 ** name from your aliases in the index menu if it finds an alias that
2847 ** matches the message's sender. For example, if you have the following
2850 ** \fTalias juser abd30425@somewhere.net (Joe User)\fP
2852 ** and then you receive mail which contains the following header:
2854 ** \fTFrom: abd30425@somewhere.net\fP
2856 ** It would be displayed in the index menu as ``Joe User'' instead of
2857 ** ``abd30425@somewhere.net.'' This is useful when the person's e-mail
2858 ** address is not human friendly (like CompuServe addresses).
2860 {"reverse_name", DT_BOOL, R_BOTH, OPTREVNAME, 0},
2863 ** It may sometimes arrive that you receive mail to a certain machine,
2864 ** move the messages to another machine, and reply to some the messages
2865 ** from there. If this variable is \fIset\fP, the default \fTFrom:\fP line of
2866 ** the reply messages is built using the address where you received the
2867 ** messages you are replying to \fBif\fP that address matches your
2868 ** alternates. If the variable is \fIunset\fP, or the address that would be
2869 ** used doesn't match your alternates, the \fTFrom:\fP line will use
2870 ** your address on the current machine.
2872 {"reverse_realname", DT_BOOL, R_BOTH, OPTREVREAL, 1},
2875 ** This variable fine-tunes the behaviour of the $reverse_name feature.
2876 ** When it is \fIset\fP, Mutt-ng will use the address from incoming messages as-is,
2877 ** possibly including eventual real names. When it is \fIunset\fP, Mutt-ng will
2878 ** override any such real names with the setting of the $realname variable.
2880 {"rfc2047_parameters", DT_BOOL, R_NONE, OPTRFC2047PARAMS, 0},
2883 ** When this variable is \fIset\fP, Mutt-ng will decode RFC-2047-encoded MIME
2884 ** parameters. You want to set this variable when Mutt-ng suggests you
2885 ** to save attachments to files named like this:
2887 ** \fT=?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=\fP
2889 ** When this variable is \fIset\fP interactively, the change doesn't have
2890 ** the desired effect before you have changed folders.
2892 ** Note that this use of RFC 2047's encoding is explicitly,
2893 ** prohibited by the standard, but nevertheless encountered in the
2896 ** Also note that setting this parameter will \fInot\fP have the effect
2897 ** that Mutt-ng \fIgenerates\fP this kind of encoding. Instead, Mutt-ng will
2898 ** unconditionally use the encoding specified in RFC 2231.
2900 {"save_address", DT_BOOL, R_NONE, OPTSAVEADDRESS, 0},
2903 ** If \fIset\fP, Mutt-ng will take the sender's full address when choosing a
2904 ** default folder for saving a mail. If ``$$save_name'' or ``$$force_name''
2905 ** is \fIset\fP too, the selection of the fcc folder will be changed as well.
2907 {"save_empty", DT_BOOL, R_NONE, OPTSAVEEMPTY, 1},
2910 ** When \fIunset\fP, mailboxes which contain no saved messages will be removed
2911 ** when closed (the exception is ``$$spoolfile'' which is never removed).
2912 ** If \fIset\fP, mailboxes are never removed.
2914 ** \fBNote:\fP This only applies to mbox and MMDF folders, Mutt-ng does not
2915 ** delete MH and Maildir directories.
2917 {"save_name", DT_BOOL, R_NONE, OPTSAVENAME, 0},
2920 ** This variable controls how copies of outgoing messages are saved.
2921 ** When set, a check is made to see if a mailbox specified by the
2922 ** recipient address exists (this is done by searching for a mailbox in
2923 ** the ``$$folder'' directory with the \fIusername\fP part of the
2924 ** recipient address). If the mailbox exists, the outgoing message will
2925 ** be saved to that mailbox, otherwise the message is saved to the
2926 ** ``$$record'' mailbox.
2928 ** Also see the ``$$force_name'' variable.
2930 {"score", DT_BOOL, R_NONE, OPTSCORE, 1},
2933 ** When this variable is \fIunset\fP, scoring is turned off. This can
2934 ** be useful to selectively disable scoring for certain folders when the
2935 ** ``$$score_threshold_delete'' variable and friends are used.
2938 {"score_threshold_delete", DT_NUM, R_NONE, UL &ScoreThresholdDelete, UL -1},
2941 ** Messages which have been assigned a score equal to or lower than the value
2942 ** of this variable are automatically marked for deletion by Mutt-ng. Since
2943 ** Mutt-ng scores are always greater than or equal to zero, the default setting
2944 ** of this variable will never mark a message for deletion.
2946 {"score_threshold_flag", DT_NUM, R_NONE, UL &ScoreThresholdFlag, 9999},
2949 ** Messages which have been assigned a score greater than or equal to this
2950 ** variable's value are automatically marked ``flagged''.
2952 {"score_threshold_read", DT_NUM, R_NONE, UL &ScoreThresholdRead, UL -1},
2955 ** Messages which have been assigned a score equal to or lower than the value
2956 ** of this variable are automatically marked as read by Mutt-ng. Since
2957 ** Mutt-ng scores are always greater than or equal to zero, the default setting
2958 ** of this variable will never mark a message read.
2960 {"send_charset", DT_STR, R_NONE, UL &SendCharset, UL "us-ascii:iso-8859-1:utf-8"},
2963 ** A list of character sets for outgoing messages. Mutt-ng will use the
2964 ** first character set into which the text can be converted exactly.
2965 ** If your ``$$charset'' is not \fTiso-8859-1\fP and recipients may not
2966 ** understand \fTUTF-8\fP, it is advisable to include in the list an
2967 ** appropriate widely used standard character set (such as
2968 ** \fTiso-8859-2\fP, \fTkoi8-r\fP or \fTiso-2022-jp\fP) either
2969 ** instead of or after \fTiso-8859-1\fP.
2971 {"sendmail", DT_PATH, R_NONE, UL &Sendmail, UL SENDMAIL " -oem -oi"},
2974 ** Specifies the program and arguments used to deliver mail sent by Mutt-ng.
2975 ** Mutt-ng expects that the specified program interprets additional
2976 ** arguments as recipient addresses.
2978 {"sendmail_wait", DT_NUM, R_NONE, UL &SendmailWait, 0},
2981 ** Specifies the number of seconds to wait for the ``$$sendmail'' process
2982 ** to finish before giving up and putting delivery in the background.
2984 ** Mutt-ng interprets the value of this variable as follows:
2986 ** .dt >0 .dd number of seconds to wait for sendmail to finish before continuing
2987 ** .dt 0 .dd wait forever for sendmail to finish
2988 ** .dt <0 .dd always put sendmail in the background without waiting
2991 ** Note that if you specify a value other than 0, the output of the child
2992 ** process will be put in a temporary file. If there is some error, you
2993 ** will be informed as to where to find the output.
2995 {"shell", DT_PATH, R_NONE, UL &Shell, 0},
2998 ** Command to use when spawning a subshell. By default, the user's login
2999 ** shell from \fT/etc/passwd\fP is used.
3002 {"save_unsubscribed", DT_SYN, R_NONE, UL "nntp_save_unsubscribed", 0 },
3003 {"nntp_save_unsubscribed", DT_BOOL, R_NONE, OPTSAVEUNSUB, 0},
3006 ** Availability: NNTP
3009 ** When \fIset\fP, info about unsubscribed newsgroups will be saved into the
3010 ** ``newsrc'' file and into the news cache.
3014 {"show_new_news", DT_SYN, R_NONE, UL "nntp_show_new_news", 0 },
3015 {"nntp_show_new_news", DT_BOOL, R_NONE, OPTSHOWNEWNEWS, 1},
3018 ** Availability: NNTP
3021 ** If \fIset\fP, the newsserver will be asked for new newsgroups on entering
3022 ** the browser. Otherwise, it will be done only once for a newsserver.
3023 ** Also controls whether or not the number of new articles of subscribed
3024 ** newsgroups will be checked.
3026 {"show_only_unread", DT_SYN, R_NONE, UL "nntp_show_only_unread", 0 },
3027 {"nntp_show_only_unread", DT_BOOL, R_NONE, OPTSHOWONLYUNREAD, 0},
3030 ** Availability: NNTP
3033 ** If \fIset\fP, only subscribed newsgroups that contain unread articles
3034 ** will be displayed in the newsgroup browser.
3037 {"sig_dashes", DT_BOOL, R_NONE, OPTSIGDASHES, 1},
3040 ** If set, a line containing ``\fT-- \fP'' (dash, dash, space)
3041 ** will be inserted before your ``$$signature''. It is \fBstrongly\fP
3042 ** recommended that you not unset this variable unless your ``signature''
3043 ** contains just your name. The reason for this is because many software
3044 ** packages use ``\fT-- \n\fP'' to detect your signature.
3046 ** For example, Mutt-ng has the ability to highlight
3047 ** the signature in a different color in the builtin pager.
3049 {"sig_on_top", DT_BOOL, R_NONE, OPTSIGONTOP, 0},
3052 ** If \fIset\fP, the signature will be included before any quoted or forwarded
3053 ** text. It is \fBstrongly\fP recommended that you do not set this variable
3054 ** unless you really know what you are doing, and are prepared to take
3055 ** some heat from netiquette guardians.
3057 {"signature", DT_PATH, R_NONE, UL &Signature, UL "~/.signature"},
3060 ** Specifies the filename of your signature, which is appended to all
3061 ** outgoing messages. If the filename ends with a pipe (``\fT|\fP''), it is
3062 ** assumed that filename is a shell command and input should be read from
3065 {"signoff_string", DT_STR, R_NONE, UL &SignOffString, UL 0},
3068 ** If \fIset\fP, this string will be inserted before the signature. This is useful
3069 ** for people that want to sign off every message they send with their name.
3071 ** If you want to insert your website's URL, additional contact information or
3072 ** witty quotes into your mails, better use a signature file instead of
3073 ** the signoff string.
3075 {"simple_search", DT_STR, R_NONE, UL &SimpleSearch, UL "~f %s | ~s %s"},
3078 ** Specifies how Mutt-ng should expand a simple search into a real search
3079 ** pattern. A simple search is one that does not contain any of the ~
3080 ** operators. See ``$patterns'' for more information on search patterns.
3082 ** For example, if you simply type ``joe'' at a search or limit prompt, Mutt-ng
3083 ** will automatically expand it to the value specified by this variable.
3084 ** For the default value it would be:
3086 ** \fT~f joe | ~s joe\fP
3088 {"smart_wrap", DT_BOOL, R_PAGER, OPTWRAP, 1},
3091 ** Controls the display of lines longer than the screen width in the
3092 ** internal pager. If \fIset\fP, long lines are wrapped at a word boundary.
3093 ** If \fIunset\fP, lines are simply wrapped at the screen edge. Also see the
3094 ** ``$$markers'' variable.
3096 {"smileys", DT_RX, R_PAGER, UL &Smileys, UL "(>From )|(:[-^]?[][)(><}{|/DP])"},
3099 ** The \fIpager\fP uses this variable to catch some common false
3100 ** positives of ``$$quote_regexp'', most notably smileys in the beginning
3103 {"sleep_time", DT_NUM, R_NONE, UL &SleepTime, 1},
3106 ** Specifies time, in seconds, to pause while displaying certain informational
3107 ** messages, while moving from folder to folder and after expunging
3108 ** messages from the current folder. The default is to pause one second, so
3109 ** a value of zero for this option suppresses the pause.
3111 {"sort", DT_SORT, R_INDEX|R_RESORT, UL &Sort, SORT_DATE},
3114 ** Specifies how to sort messages in the \fIindex\fP menu. Valid values
3118 ** . date or date-sent
3121 ** . mailbox-order (unsorted)
3130 ** You may optionally use the ``reverse-'' prefix to specify reverse sorting
3131 ** order (example: \fTset sort=reverse-date-sent\fP).
3133 {"sort_alias", DT_SORT|DT_SORT_ALIAS, R_NONE, UL &SortAlias, SORT_ALIAS},
3136 ** Specifies how the entries in the ``alias'' menu are sorted. The
3137 ** following are legal values:
3140 ** . address (sort alphabetically by email address)
3141 ** . alias (sort alphabetically by alias name)
3142 ** . unsorted (leave in order specified in .muttrc)
3145 {"sort_aux", DT_SORT|DT_SORT_AUX, R_INDEX|R_RESORT_BOTH, UL &SortAux, SORT_DATE},
3148 ** When sorting by threads, this variable controls how threads are sorted
3149 ** in relation to other threads, and how the branches of the thread trees
3150 ** are sorted. This can be set to any value that ``$$sort'' can, except
3151 ** threads (in that case, Mutt-ng will just use date-sent). You can also
3152 ** specify the ``last-'' prefix in addition to ``reverse-'' prefix, but last-
3153 ** must come after reverse-. The last- prefix causes messages to be
3154 ** sorted against its siblings by which has the last descendant, using
3155 ** the rest of sort_aux as an ordering.
3157 ** For instance, \fTset sort_aux=last-date-received\fP would mean that if
3158 ** a new message is received in a thread, that thread becomes the last one
3159 ** displayed (or the first, if you have \fTset sort=reverse-threads\fP.)
3161 ** \fBNote:\fP For reversed ``$$sort'' order $$sort_aux is reversed again
3162 ** (which is not the right thing to do, but kept to not break any existing
3163 ** configuration setting).
3165 {"sort_browser", DT_SORT|DT_SORT_BROWSER, R_NONE, UL &BrowserSort, SORT_ALPHA},
3168 ** Specifies how to sort entries in the file browser. By default, the
3169 ** entries are sorted alphabetically. Valid values:
3172 ** . alpha (alphabetically)
3178 ** You may optionally use the ``reverse-'' prefix to specify reverse sorting
3179 ** order (example: \fTset sort_browser=reverse-date\fP).
3181 {"sort_re", DT_BOOL, R_INDEX|R_RESORT|R_RESORT_INIT, OPTSORTRE, 1},
3184 ** This variable is only useful when sorting by threads with
3185 ** ``$$strict_threads'' \fIunset\fP. In that case, it changes the heuristic
3186 ** Mutt-ng uses to thread messages by subject. With $$sort_re \fIset\fP,
3187 ** Mutt-ng will only attach a message as the child of another message by
3188 ** subject if the subject of the child message starts with a substring
3189 ** matching the setting of ``$$reply_regexp''. With $$sort_re \fIunset\fP,
3190 ** Mutt-ng will attach the message whether or not this is the case,
3191 ** as long as the non-``$$reply_regexp'' parts of both messages are identical.
3193 {"spam_separator", DT_STR, R_NONE, UL &SpamSep, UL ","},
3196 ** ``$spam_separator'' controls what happens when multiple spam headers
3197 ** are matched: if \fIunset\fP, each successive header will overwrite any
3198 ** previous matches value for the spam label. If \fIset\fP, each successive
3199 ** match will append to the previous, using ``$spam_separator'' as a
3202 {"spoolfile", DT_PATH, R_NONE, UL &Spoolfile, 0},
3205 ** If your spool mailbox is in a non-default place where Mutt-ng cannot find
3206 ** it, you can specify its location with this variable. Mutt-ng will
3207 ** automatically set this variable to the value of the environment
3208 ** variable $$$MAIL if it is not set.
3210 {"status_chars", DT_STR, R_BOTH, UL &StChars, UL "-*%A"},
3213 ** Controls the characters used by the ``\fT%r\fP'' indicator in
3214 ** ``$$status_format''. The first character is used when the mailbox is
3215 ** unchanged. The second is used when the mailbox has been changed, and
3216 ** it needs to be resynchronized. The third is used if the mailbox is in
3217 ** read-only mode, or if the mailbox will not be written when exiting
3218 ** that mailbox (You can toggle whether to write changes to a mailbox
3219 ** with the toggle-write operation, bound by default to ``\fT%\fP'').
3220 ** The fourth is used to indicate that the current folder has been
3221 ** opened in attach-message mode (Certain operations like composing
3222 ** a new mail, replying, forwarding, etc. are not permitted in this mode).
3224 {"status_format", DT_STR, R_BOTH, UL &Status, UL "-%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)---"},
3227 ** Controls the format of the status line displayed in the \fIindex\fP
3228 ** menu. This string is similar to ``$$index_format'', but has its own
3229 ** set of \fTprintf(3)\fP-like sequences:
3232 ** .dt %b .dd number of mailboxes with new mail *
3233 ** .dt %B .dd the short pathname of the current mailbox
3234 ** .dt %d .dd number of deleted messages *
3235 ** .dt %f .dd the full pathname of the current mailbox
3236 ** .dt %F .dd number of flagged messages *
3237 ** .dt %h .dd local hostname
3238 ** .dt %l .dd size (in bytes) of the current mailbox *
3239 ** .dt %L .dd size (in bytes) of the messages shown
3240 ** (i.e., which match the current limit) *
3241 ** .dt %m .dd the number of messages in the mailbox *
3242 ** .dt %M .dd the number of messages shown (i.e., which match the current limit) *
3243 ** .dt %n .dd number of new messages in the mailbox *
3244 ** .dt %o .dd number of old unread messages *
3245 ** .dt %p .dd number of postponed messages *
3246 ** .dt %P .dd percentage of the way through the index
3247 ** .dt %r .dd modified/read-only/won't-write/attach-message indicator,
3248 ** according to $$status_chars
3249 ** .dt %s .dd current sorting mode ($$sort)
3250 ** .dt %S .dd current aux sorting method ($$sort_aux)
3251 ** .dt %t .dd number of tagged messages *
3252 ** .dt %u .dd number of unread messages *
3253 ** .dt %v .dd Mutt-ng version string
3254 ** .dt %V .dd currently active limit pattern, if any *
3255 ** .dt %>X .dd right justify the rest of the string and pad with "X"
3256 ** .dt %|X .dd pad to the end of the line with "X"
3259 ** * = can be optionally printed if nonzero
3261 ** Some of the above sequences can be used to optionally print a string
3262 ** if their value is nonzero. For example, you may only want to see the
3263 ** number of flagged messages if such messages exist, since zero is not
3264 ** particularly meaningful. To optionally print a string based upon one
3265 ** of the above sequences, the following construct is used
3267 ** \fT%?<sequence_char>?<optional_string>?\fP
3269 ** where \fIsequence_char\fP is a character from the table above, and
3270 ** \fIoptional_string\fP is the string you would like printed if
3271 ** \fIsequence_char\fP is nonzero. \fIoptional_string\fP \fBmay\fP contain
3272 ** other sequences as well as normal text, but you may \fBnot\fP nest
3273 ** optional strings.
3275 ** Here is an example illustrating how to optionally print the number of
3276 ** new messages in a mailbox:
3278 ** \fT%?n?%n new messages.?\fP
3280 ** Additionally you can switch between two strings, the first one, if a
3281 ** value is zero, the second one, if the value is nonzero, by using the
3282 ** following construct:
3284 ** \fT%?<sequence_char>?<if_string>&<else_string>?\fP
3286 ** You can additionally force the result of any \fTprintf(3)\fP-like sequence
3287 ** to be lowercase by prefixing the sequence character with an underscore
3288 ** (\fT_\fP) sign. For example, if you want to display the local hostname in
3289 ** lowercase, you would use:
3293 ** If you prefix the sequence character with a colon (\fT:\fP) character, Mutt-ng
3294 ** will replace any dots in the expansion by underscores. This might be helpful
3295 ** with IMAP folders that don't like dots in folder names.
3297 {"status_on_top", DT_BOOL, R_BOTH, OPTSTATUSONTOP, 0},
3300 ** Setting this variable causes the ``status bar'' to be displayed on
3301 ** the first line of the screen rather than near the bottom.
3303 {"strict_mailto", DT_BOOL, R_NONE, OPTSTRICTMAILTO, 1},
3307 ** With mailto: style links, a body as well as arbitrary header information
3308 ** may be embedded. This may lead to (user) headers being overwriten without note
3309 ** if ``$$edit_headers'' is unset.
3312 ** If this variable is \fIset\fP, mutt-ng is strict and allows anything to be
3313 ** changed. If it's \fIunset\fP, all headers given will be prefixed with
3314 ** ``X-Mailto-'' and the message including headers will be shown in the editor
3315 ** regardless of what ``$$edit_headers'' is set to.
3317 {"strict_mime", DT_BOOL, R_NONE, OPTSTRICTMIME, 1},
3320 ** When \fIunset\fP, non MIME-compliant messages that doesn't have any
3321 ** charset indication in the ``\fTContent-Type:\fP'' header field can
3322 ** be displayed (non MIME-compliant messages are often generated by old
3323 ** mailers or buggy mailers like MS Outlook Express).
3324 ** See also $$assumed_charset.
3326 ** This option also replaces linear-white-space between encoded-word
3327 ** and *text to a single space to prevent the display of MIME-encoded
3328 ** ``\fTSubject:\fP'' header field from being devided into multiple lines.
3330 {"strict_threads", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTSTRICTTHREADS, 0},
3333 ** If \fIset\fP, threading will only make use of the ``\fTIn-Reply-To:\fP'' and
3334 ** ``\fTReferences:\fP'' header fields when you ``$$sort'' by message threads. By
3335 ** default, messages with the same subject are grouped together in
3336 ** ``pseudo threads.'' This may not always be desirable, such as in a
3337 ** personal mailbox where you might have several unrelated messages with
3338 ** the subject ``hi'' which will get grouped together.
3340 {"strip_was", DT_BOOL, R_NONE, OPTSTRIPWAS, 0},
3343 ** When \fIset\fP, mutt-ng will remove the trailing part of the ``\fTSubject:\fP''
3344 ** line which matches $$strip_was_regex when replying. This is useful to
3345 ** properly react on subject changes and reduce ``subject noise.'' (esp. in Usenet)
3347 {"strip_was_regex", DT_RX, R_NONE, UL &StripWasRegexp, UL "\\([Ww][Aa][RrSs]: .*\\)[ ]*$"},
3350 ** When non-empty and $$strip_was is \fIset\fP, mutt-ng will remove this
3351 ** trailing part of the ``Subject'' line when replying if it won't be empty
3354 {"stuff_quoted", DT_BOOL, R_BOTH, OPTSTUFFQUOTED, 0},
3357 ** If \fIset\fP, attachments with flowed format will have their quoting ``stuffed'',
3358 ** i.e. a space will be inserted between the quote characters and the actual
3361 {"suspend", DT_BOOL, R_NONE, OPTSUSPEND, 1},
3364 ** When \fIunset\fP, Mutt-ng won't stop when the user presses the terminal's
3365 ** \fIsusp\fP key, usually \fTCTRL+Z\fP. This is useful if you run Mutt-ng
3366 ** inside an xterm using a command like ``\fTxterm -e muttng\fP.''
3368 {"text_flowed", DT_BOOL, R_NONE, OPTTEXTFLOWED, 0},
3371 ** When \fIset\fP, Mutt-ng will generate \fTtext/plain; format=flowed\fP attachments.
3372 ** This format is easier to handle for some mailing software, and generally
3373 ** just looks like ordinary text. To actually make use of this format's
3374 ** features, you'll need support in your editor.
3376 ** Note that $$indent_string is ignored when this option is set.
3378 {"thread_received", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTTHREADRECEIVED, 0},
3381 ** When \fIset\fP, Mutt-ng uses the date received rather than the date sent
3382 ** to thread messages by subject.
3384 {"thorough_search", DT_BOOL, R_NONE, OPTTHOROUGHSRC, 0},
3387 ** Affects the \fT~b\fP and \fT~h\fP search operations described in
3388 ** section ``$patterns'' above. If \fIset\fP, the headers and attachments of
3389 ** messages to be searched are decoded before searching. If \fIunset\fP,
3390 ** messages are searched as they appear in the folder.
3392 {"tilde", DT_BOOL, R_PAGER, OPTTILDE, 0},
3395 ** When \fIset\fP, the internal-pager will pad blank lines to the bottom of the
3396 ** screen with a tilde (~).
3398 {"timeout", DT_NUM, R_NONE, UL &Timeout, 600},
3401 ** This variable controls the \fInumber of seconds\fP Mutt-ng will wait
3402 ** for a key to be pressed in the main menu before timing out and
3403 ** checking for new mail. A value of zero or less will cause Mutt-ng
3404 ** to never time out.
3406 {"tmpdir", DT_PATH, R_NONE, UL &Tempdir, 0},
3409 ** This variable allows you to specify where Mutt-ng will place its
3410 ** temporary files needed for displaying and composing messages. If
3411 ** this variable is not set, the environment variable \fT$$$TMPDIR\fP is
3412 ** used. If \fT$$$TMPDIR\fP is not set then "\fT/tmp\fP" is used.
3414 {"to_chars", DT_STR, R_BOTH, UL &Tochars, UL " +TCFL"},
3417 ** Controls the character used to indicate mail addressed to you. The
3418 ** first character is the one used when the mail is NOT addressed to your
3419 ** address (default: space). The second is used when you are the only
3420 ** recipient of the message (default: +). The third is when your address
3421 ** appears in the ``\fTTo:\fP'' header field, but you are not the only recipient of
3422 ** the message (default: T). The fourth character is used when your
3423 ** address is specified in the ``\fTCc:\fP'' header field, but you are not the only
3424 ** recipient. The fifth character is used to indicate mail that was sent
3425 ** by \fIyou\fP. The sixth character is used to indicate when a mail
3426 ** was sent to a mailing-list you're subscribe to (default: L).
3428 {"trash", DT_PATH, R_NONE, UL &TrashPath, 0},
3431 ** If \fIset\fP, this variable specifies the path of the trash folder where the
3432 ** mails marked for deletion will be moved, instead of being irremediably
3435 ** \fBNote\fP: When you delete a message in the trash folder, it is really
3436 ** deleted, so that there is no way to recover mail.
3439 {"tunnel", DT_STR, R_NONE, UL &Tunnel, UL 0},
3442 ** Setting this variable will cause Mutt-ng to open a pipe to a command
3443 ** instead of a raw socket. You may be able to use this to set up
3444 ** preauthenticated connections to your IMAP/POP3 server. Example:
3446 ** \fTtunnel="ssh -q mailhost.net /usr/local/libexec/imapd"\fP
3448 ** \fBNote:\fP For this example to work you must be able to log in to the remote
3449 ** machine without having to enter a password.
3452 {"umask", DT_NUM, R_NONE, UL &Umask, 0077},
3455 ** This sets the umask that will be used by Mutt-ng when creating all
3456 ** kinds of files. If \fIunset\fP, the default value is \fT077\fP.
3458 {"use_8bitmime", DT_BOOL, R_NONE, OPTUSE8BITMIME, 0},
3461 ** \fBWarning:\fP do not set this variable unless you are using a version
3462 ** of sendmail which supports the \fT-B8BITMIME\fP flag (such as sendmail
3463 ** 8.8.x) or you may not be able to send mail.
3465 ** When \fIset\fP, Mutt-ng will invoke ``$$sendmail'' with the \fT-B8BITMIME\fP
3466 ** flag when sending 8-bit messages to enable ESMTP negotiation.
3468 {"use_domain", DT_BOOL, R_NONE, OPTUSEDOMAIN, 1},
3471 ** When \fIset\fP, Mutt-ng will qualify all local addresses (ones without the
3472 ** @host portion) with the value of ``$$hostname''. If \fIunset\fP, no
3473 ** addresses will be qualified.
3475 {"use_from", DT_BOOL, R_NONE, OPTUSEFROM, 1},
3478 ** When \fIset\fP, Mutt-ng will generate the ``\fTFrom:\fP'' header field when
3479 ** sending messages. If \fIunset\fP, no ``\fTFrom:\fP'' header field will be
3480 ** generated unless the user explicitly sets one using the ``$my_hdr''
3484 {"use_idn", DT_BOOL, R_BOTH, OPTUSEIDN, 1},
3487 ** Availability: IDN
3490 ** When \fIset\fP, Mutt-ng will show you international domain names decoded.
3492 ** \fBNote:\fP You can use IDNs for addresses even if this is \fIunset\fP.
3493 ** This variable only affects decoding.
3495 #endif /* HAVE_LIBIDN */
3496 #ifdef HAVE_GETADDRINFO
3497 {"use_ipv6", DT_BOOL, R_NONE, OPTUSEIPV6, 1},
3500 ** When \fIset\fP, Mutt-ng will look for IPv6 addresses of hosts it tries to
3501 ** contact. If this option is \fIunset\fP, Mutt-ng will restrict itself to IPv4 addresses.
3502 ** Normally, the default should work.
3504 #endif /* HAVE_GETADDRINFO */
3505 {"user_agent", DT_BOOL, R_NONE, OPTXMAILER, 1},
3508 ** When \fIset\fP, Mutt-ng will add a ``\fTUser-Agent:\fP'' header to outgoing
3509 ** messages, indicating which version of Mutt-ng was used for composing
3512 {"visual", DT_PATH, R_NONE, UL &Visual, 0},
3515 ** Specifies the visual editor to invoke when the \fI~v\fP command is
3516 ** given in the builtin editor.
3518 {"wait_key", DT_BOOL, R_NONE, OPTWAITKEY, 1},
3521 ** Controls whether Mutt-ng will ask you to press a key after \fIshell-
3522 ** escape\fP, \fIpipe-message\fP, \fIpipe-entry\fP, \fIprint-message\fP,
3523 ** and \fIprint-entry\fP commands.
3525 ** It is also used when viewing attachments with ``$auto_view'', provided
3526 ** that the corresponding mailcap entry has a \fTneedsterminal\fP flag,
3527 ** and the external program is interactive.
3529 ** When \fIset\fP, Mutt-ng will always ask for a key. When \fIunset\fP, Mutt-ng will wait
3530 ** for a key only if the external command returned a non-zero status.
3532 {"weed", DT_BOOL, R_NONE, OPTWEED, 1},
3535 ** When \fIset\fP, Mutt-ng will weed headers when displaying, forwarding,
3536 ** printing, or replying to messages.
3538 {"wrap_search", DT_BOOL, R_NONE, OPTWRAPSEARCH, 1},
3541 ** Controls whether searches wrap around the end of the mailbox.
3543 ** When \fIset\fP, searches will wrap around the first (or last) message. When
3544 ** \fIunset\fP, searches will not wrap.
3546 {"wrapmargin", DT_NUM, R_PAGER, UL &WrapMargin, 0},
3549 ** Controls the size of the margin remaining at the right side of
3550 ** the terminal when Mutt-ng's pager does smart wrapping.
3552 {"write_inc", DT_NUM, R_NONE, UL &WriteInc, 10},
3555 ** When writing a mailbox, a message will be printed every
3556 ** \fIwrite_inc\fP messages to indicate progress. If set to 0, only a
3557 ** single message will be displayed before writing a mailbox.
3559 ** Also see the ``$$read_inc'' variable.
3561 {"write_bcc", DT_BOOL, R_NONE, OPTWRITEBCC, 1},
3564 ** Controls whether Mutt-ng writes out the Bcc header when preparing
3565 ** messages to be sent. Exim users may wish to \fIunset\fP this.
3567 {"xterm_icon", DT_STR, R_BOTH, UL &XtermIcon, UL "M%?n?AIL&ail?"},
3570 ** Controls the format of the X11 icon title, as long as $$xterm_set_titles
3571 ** is \fIset\fP. This string is identical in formatting to the one used by
3572 ** ``$$status_format''.
3574 {"xterm_set_titles", DT_BOOL, R_BOTH, OPTXTERMSETTITLES, 0},
3577 ** Controls whether Mutt-ng sets the xterm title bar and icon name
3578 ** (as long as you're in an appropriate terminal). The default must
3579 ** be \fIunset\fP to force in the validity checking.
3581 {"xterm_leave", DT_STR, R_BOTH, UL &XtermLeave, UL "" },
3584 ** If $$xterm_set_titles is \fIset\fP, this string will be used to
3585 ** set the title when leaving mutt-ng. For terminal-based programs,
3586 ** there's no easy and portable way to read the current title so mutt-ng
3587 ** cannot read it upon startup and restore it when exiting.
3590 ** Based on the xterm FAQ, the following might work:
3593 ** \fTset xterm_leave = "`test x$$$DISPLAY != x && xprop -id $$$WINDOWID | grep WM_NAME | cut -d '"' -f 2`"\fP
3595 {"xterm_title", DT_STR, R_BOTH, UL &XtermTitle, UL "Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?"},
3598 ** Controls the format of the title bar of the xterm provided that
3599 ** $$xterm_set_titles has been \fIset\fP. This string is identical in formatting
3600 ** to the one used by ``$$status_format''.
3603 {"x_comment_to", DT_SYN, R_NONE, UL "nntp_x_comment_to", 0},
3604 {"nntp_x_comment_to", DT_BOOL, R_NONE, OPTXCOMMENTTO, 0},
3607 ** Availability: NNTP
3610 ** If \fIset\fP, Mutt-ng will add a ``\fTX-Comment-To:\fP'' header field
3611 ** (that contains full name of the original article author) to articles that
3619 const struct feature_t Features[] = {
3621 #ifdef NCURSES_VERSION
3627 #ifdef USE_SLANG_CURSES
3633 #ifdef _LIBICONV_VERSION
3651 #ifdef DL_STANDALONE
3705 #ifdef USE_COMPRESSED
3717 #ifdef CRYPT_BACKEND_CLASSIC_PGP
3722 }, {"classic_smime",
3723 #ifdef CRYPT_BACKEND_CLASSIC_SMIME
3729 #ifdef CRYPT_BACKEND_GPGME
3763 const struct mapping_t SortMethods[] = {
3764 {"date", SORT_DATE},
3765 {"date-sent", SORT_DATE},
3766 {"date-received", SORT_RECEIVED},
3767 {"mailbox-order", SORT_ORDER},
3768 {"subject", SORT_SUBJECT},
3769 {"from", SORT_FROM},
3770 {"size", SORT_SIZE},
3771 {"threads", SORT_THREADS},
3773 {"score", SORT_SCORE},
3774 {"spam", SORT_SPAM},
3778 /* same as SortMethods, but with "threads" replaced by "date" */
3780 const struct mapping_t SortAuxMethods[] = {
3781 {"date", SORT_DATE},
3782 {"date-sent", SORT_DATE},
3783 {"date-received", SORT_RECEIVED},
3784 {"mailbox-order", SORT_ORDER},
3785 {"subject", SORT_SUBJECT},
3786 {"from", SORT_FROM},
3787 {"size", SORT_SIZE},
3788 {"threads", SORT_DATE}, /* note: sort_aux == threads
3792 {"score", SORT_SCORE},
3793 {"spam", SORT_SPAM},
3798 const struct mapping_t SortBrowserMethods[] = {
3799 {"alpha", SORT_SUBJECT},
3800 {"date", SORT_DATE},
3801 {"size", SORT_SIZE},
3802 {"unsorted", SORT_ORDER},
3806 const struct mapping_t SortAliasMethods[] = {
3807 {"alias", SORT_ALIAS},
3808 {"address", SORT_ADDRESS},
3809 {"unsorted", SORT_ORDER},
3813 const struct mapping_t SortKeyMethods[] = {
3814 {"address", SORT_ADDRESS},
3815 {"date", SORT_DATE},
3816 {"keyid", SORT_KEYID},
3817 {"trust", SORT_TRUST},
3822 /* functions used to parse commands in a rc file */
3824 static int parse_list (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3825 static int parse_spam_list (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3826 static int parse_unlist (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3828 static int parse_lists (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3829 static int parse_unlists (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3830 static int parse_alias (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3831 static int parse_unalias (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3832 static int parse_ifdef (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3833 static int parse_ignore (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3834 static int parse_unignore (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3835 static int parse_source (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3836 static int parse_set (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3837 static int parse_my_hdr (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3838 static int parse_unmy_hdr (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3839 static int parse_subscribe (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3840 static int parse_unsubscribe (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3842 static int parse_alternates (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3843 static int parse_unalternates (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3847 int (*func) (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3849 unsigned long data1;
3852 struct command_t Commands[] = {
3853 {"alternates", parse_alternates, 0},
3854 {"unalternates", parse_unalternates, 0},
3856 {"account-hook", mutt_parse_hook, M_ACCOUNTHOOK},
3858 {"alias", parse_alias, 0},
3859 {"auto_view", parse_list, UL &AutoViewList},
3860 {"alternative_order", parse_list, UL &AlternativeOrderList},
3861 {"bind", mutt_parse_bind, 0},
3862 {"charset-hook", mutt_parse_hook, M_CHARSETHOOK},
3864 {"color", mutt_parse_color, 0},
3865 {"uncolor", mutt_parse_uncolor, 0},
3867 {"exec", mutt_parse_exec, 0},
3868 {"fcc-hook", mutt_parse_hook, M_FCCHOOK},
3869 {"fcc-save-hook", mutt_parse_hook, M_FCCHOOK|M_SAVEHOOK},
3870 {"folder-hook", mutt_parse_hook, M_FOLDERHOOK},
3871 #ifdef USE_COMPRESSED
3872 {"open-hook", mutt_parse_hook, M_OPENHOOK},
3873 {"close-hook", mutt_parse_hook, M_CLOSEHOOK},
3874 {"append-hook", mutt_parse_hook, M_APPENDHOOK},
3876 {"hdr_order", parse_list, UL &HeaderOrderList},
3877 {"ifdef", parse_ifdef, 1},
3878 {"ifndef", parse_ifdef, 0},
3880 {"iconv-hook", mutt_parse_hook, M_ICONVHOOK},
3882 {"ignore", parse_ignore, 0},
3883 {"lists", parse_lists, 0},
3884 {"macro", mutt_parse_macro, 0},
3885 {"mailboxes", buffy_parse_mailboxes, M_MAILBOXES},
3886 {"unmailboxes", buffy_parse_mailboxes, M_UNMAILBOXES},
3887 {"message-hook", mutt_parse_hook, M_MESSAGEHOOK},
3888 {"mbox-hook", mutt_parse_hook, M_MBOXHOOK},
3889 {"mime_lookup", parse_list, UL &MimeLookupList},
3890 {"unmime_lookup", parse_unlist, UL &MimeLookupList},
3891 {"mono", mutt_parse_mono, 0},
3892 {"my_hdr", parse_my_hdr, 0},
3893 {"pgp-hook", mutt_parse_hook, M_CRYPTHOOK},
3894 {"crypt-hook", mutt_parse_hook, M_CRYPTHOOK},
3895 {"push", mutt_parse_push, 0},
3896 {"reply-hook", mutt_parse_hook, M_REPLYHOOK},
3897 {"reset", parse_set, M_SET_RESET},
3898 {"save-hook", mutt_parse_hook, M_SAVEHOOK},
3899 {"score", mutt_parse_score, 0},
3900 {"send-hook", mutt_parse_hook, M_SENDHOOK},
3901 {"send2-hook", mutt_parse_hook, M_SEND2HOOK},
3902 {"set", parse_set, 0},
3903 {"source", parse_source, 0},
3904 {"spam", parse_spam_list, M_SPAM},
3905 {"nospam", parse_spam_list, M_NOSPAM},
3906 {"subscribe", parse_subscribe, 0},
3907 {"toggle", parse_set, M_SET_INV},
3908 {"unalias", parse_unalias, 0},
3909 {"unalternative_order", parse_unlist, UL &AlternativeOrderList},
3910 {"unauto_view", parse_unlist, UL &AutoViewList},
3911 {"unhdr_order", parse_unlist, UL &HeaderOrderList},
3912 {"unhook", mutt_parse_unhook, 0},
3913 {"unignore", parse_unignore, 0},
3914 {"unlists", parse_unlists, 0},
3915 {"unmono", mutt_parse_unmono, 0},
3916 {"unmy_hdr", parse_unmy_hdr, 0},
3917 {"unscore", mutt_parse_unscore, 0},
3918 {"unset", parse_set, M_SET_UNSET},
3919 {"unsubscribe", parse_unsubscribe, 0},