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
111 # ifndef DL_STANDALONE
112 # define DL_STANDALONE
120 # ifndef HAVE_GETADDRINFO
121 # define HAVE_GETADDRINFO
125 struct option_t MuttVars[] = {
127 {"abort_nosubject", DT_QUAD, R_NONE, OPT_SUBJECT, M_ASKYES},
130 ** If set to \fIyes\fP, when composing messages and no subject is given
131 ** at the subject prompt, composition will be aborted. If set to
132 ** \fIno\fP, composing messages with no subject given at the subject
133 ** prompt will never be aborted.
135 {"abort_unmodified", DT_QUAD, R_NONE, OPT_ABORT, M_YES},
138 ** If set to \fIyes\fP, composition will automatically abort after
139 ** editing the message body if no changes are made to the file (this
140 ** check only happens after the \fIfirst\fP edit of the file). When set
141 ** to \fIno\fP, composition will never be aborted.
143 {"alias_file", DT_PATH, R_NONE, UL &AliasFile, UL "~/.muttngrc"},
146 ** The default file in which to save aliases created by the
147 ** ``$create-alias'' function.
149 ** \fBNote:\fP Mutt-ng will not automatically source this file; you must
150 ** explicitly use the ``$source'' command for it to be executed.
152 {"alias_format", DT_STR, R_NONE, UL &AliasFmt, UL "%4n %2f %t %-10a %r"},
155 ** Specifies the format of the data displayed for the ``alias'' menu. The
156 ** following \fTprintf(3)\fP-style sequences are available:
159 ** .dt %a .dd alias name
160 ** .dt %f .dd flags - currently, a "d" for an alias marked for deletion
161 ** .dt %n .dd index number
162 ** .dt %r .dd address which alias expands to
163 ** .dt %t .dd character which indicates if the alias is tagged for inclusion
166 {"allow_8bit", DT_BOOL, R_NONE, OPTALLOW8BIT, 1},
169 ** Controls whether 8-bit data is converted to 7-bit using either
170 ** \fTquoted-printable\fP or \fTbase64\fP encoding when sending mail.
172 {"allow_ansi", DT_BOOL, R_NONE, OPTALLOWANSI, 0},
175 ** Controls whether ANSI color codes in messages (and color tags in
176 ** rich text messages) are to be interpreted.
177 ** Messages containing these codes are rare, but if this option is set,
178 ** their text will be colored accordingly. Note that this may override
179 ** your color choices, and even present a security problem, since a
180 ** message could include a line like ``\fT[-- PGP output follows ...\fP" and
181 ** give it the same color as your attachment color.
183 {"arrow_cursor", DT_BOOL, R_BOTH, OPTARROWCURSOR, 0},
186 ** When \fIset\fP, an arrow (``\fT->\fP'') will be used to indicate the current entry
187 ** in menus instead of highlighting the whole line. On slow network or modem
188 ** links this will make response faster because there is less that has to
189 ** be redrawn on the screen when moving to the next or previous entries
192 {"ascii_chars", DT_BOOL, R_BOTH, OPTASCIICHARS, 0},
195 ** If \fIset\fP, Mutt-ng will use plain ASCII characters when displaying thread
196 ** and attachment trees, instead of the default \fTACS\fP characters.
198 {"askbcc", DT_BOOL, R_NONE, OPTASKBCC, 0},
201 ** If \fIset\fP, Mutt-ng will prompt you for blind-carbon-copy (Bcc) recipients
202 ** before editing an outgoing message.
204 {"askcc", DT_BOOL, R_NONE, OPTASKCC, 0},
207 ** If \fIset\fP, Mutt-ng will prompt you for carbon-copy (Cc) recipients before
208 ** editing the body of an outgoing message.
210 {"assumed_charset", DT_STR, R_NONE, UL &AssumedCharset, UL "us-ascii"},
213 ** This variable is a colon-separated list of character encoding
214 ** schemes for messages without character encoding indication.
215 ** Header field values and message body content without character encoding
216 ** indication would be assumed that they are written in one of this list.
217 ** By default, all the header fields and message body without any charset
218 ** indication are assumed to be in \fTus-ascii\fP.
220 ** For example, Japanese users might prefer this:
222 ** \fTset assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"\fP
224 ** However, only the first content is valid for the message body.
225 ** This variable is valid only if $$strict_mime is unset.
228 {"ask_followup_to", DT_SYN, R_NONE, UL "nntp_ask_followup_to", 0},
229 {"nntp_ask_followup_to", DT_BOOL, R_NONE, OPTASKFOLLOWUP, 0},
232 ** Availability: NNTP
235 ** If \fIset\fP, Mutt-ng will prompt you for the \fTFollowup-To:\fP header
236 ** field before editing the body of an outgoing news article.
238 {"ask_x_comment_to", DT_SYN, R_NONE, UL "nntp_ask_x_comment_to", 0},
239 {"nntp_ask_x_comment_to", DT_BOOL, R_NONE, OPTASKXCOMMENTTO, 0},
242 ** Availability: NNTP
245 ** If \fIset\fP, Mutt-ng will prompt you for the \fTX-Comment-To:\fP header
246 ** field before editing the body of an outgoing news article.
249 {"attach_format", DT_STR, R_NONE, UL &AttachFormat, UL "%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] "},
252 ** This variable describes the format of the ``attachment'' menu. The
253 ** following \fTprintf(3)\fP-style sequences are understood:
256 ** .dt %C .dd charset
257 ** .dt %c .dd requires charset conversion (n or c)
258 ** .dt %D .dd deleted flag
259 ** .dt %d .dd description
260 ** .dt %e .dd MIME \fTContent-Transfer-Encoding:\fP header field
261 ** .dt %f .dd filename
262 ** .dt %I .dd MIME \fTContent-Disposition:\fP header field (\fTI\fP=inline, \fTA\fP=attachment)
263 ** .dt %m .dd major MIME type
264 ** .dt %M .dd MIME subtype
265 ** .dt %n .dd attachment number
267 ** .dt %t .dd tagged flag
268 ** .dt %T .dd graphic tree characters
269 ** .dt %u .dd unlink (=to delete) flag
270 ** .dt %>X .dd right justify the rest of the string and pad with character "X"
271 ** .dt %|X .dd pad to the end of the line with character "X"
274 {"attach_sep", DT_STR, R_NONE, UL &AttachSep, UL "\n"},
277 ** The separator to add between attachments when operating (saving,
278 ** printing, piping, etc) on a list of tagged attachments.
280 {"attach_split", DT_BOOL, R_NONE, OPTATTACHSPLIT, 1},
283 ** If this variable is \fIunset\fP, when operating (saving, printing, piping,
284 ** etc) on a list of tagged attachments, Mutt-ng will concatenate the
285 ** attachments and will operate on them as a single attachment. The
286 ** ``$$attach_sep'' separator is added after each attachment. When \fIset\fP,
287 ** Mutt-ng will operate on the attachments one by one.
289 {"attribution", DT_STR, R_NONE, UL &Attribution, UL "On %d, %n wrote:"},
292 ** This is the string that will precede a message which has been included
293 ** in a reply. For a full listing of defined \fTprintf(3)\fP-like sequences see
294 ** the section on ``$$index_format''.
296 {"autoedit", DT_BOOL, R_NONE, OPTAUTOEDIT, 0},
299 ** When \fIset\fP along with ``$$edit_headers'', Mutt-ng will skip the initial
300 ** send-menu and allow you to immediately begin editing the body of your
301 ** message. The send-menu may still be accessed once you have finished
302 ** editing the body of your message.
304 ** Also see ``$$fast_reply''.
306 {"auto_tag", DT_BOOL, R_NONE, OPTAUTOTAG, 0},
309 ** When \fIset\fP, functions in the \fIindex\fP menu which affect a message
310 ** will be applied to all tagged messages (if there are any). When
311 ** unset, you must first use the ``tag-prefix'' function (default: "\fT;\fP") to
312 ** make the next function apply to all tagged messages.
314 {"beep", DT_BOOL, R_NONE, OPTBEEP, 1},
317 ** When this variable is \fIset\fP, Mutt-ng will beep when an error occurs.
319 {"beep_new", DT_BOOL, R_NONE, OPTBEEPNEW, 0},
322 ** When this variable is \fIset\fP, Mutt-ng will beep whenever it prints a message
323 ** notifying you of new mail. This is independent of the setting of the
324 ** ``$$beep'' variable.
326 {"bounce", DT_QUAD, R_NONE, OPT_BOUNCE, M_ASKYES},
329 ** Controls whether you will be asked to confirm bouncing messages.
330 ** If set to \fIyes\fP you don't get asked if you want to bounce a
331 ** message. Setting this variable to \fIno\fP is not generally useful,
332 ** and thus not recommended, because you are unable to bounce messages.
334 {"bounce_delivered", DT_BOOL, R_NONE, OPTBOUNCEDELIVERED, 1},
337 ** When this variable is \fIset\fP, Mutt-ng will include
338 ** \fTDelivered-To:\fP header fields when bouncing messages.
339 ** Postfix users may wish to \fIunset\fP this variable.
341 { "braille_friendly", DT_BOOL, R_NONE, OPTBRAILLEFRIENDLY, 0 },
344 ** When this variable is set, mutt will place the cursor at the beginning
345 ** of the current line in menus, even when the arrow_cursor variable
346 ** is unset, making it easier for blind persons using Braille displays to
347 ** follow these menus. The option is disabled by default because many
348 ** visual terminals don't permit making the cursor invisible.
351 {"catchup_newsgroup", DT_SYN, R_NONE, UL "nntp_catchup", 0},
352 {"nntp_catchup", DT_QUAD, R_NONE, OPT_CATCHUP, M_ASKYES},
355 ** Availability: NNTP
358 ** If this variable is \fIset\fP, Mutt-ng will mark all articles in a newsgroup
359 ** as read when you leaving it.
362 {"charset", DT_STR, R_NONE, UL &Charset, UL 0},
365 ** Character set your terminal uses to display and enter textual data.
367 {"check_new", DT_BOOL, R_NONE, OPTCHECKNEW, 1},
370 ** \fBNote:\fP this option only affects \fImaildir\fP and \fIMH\fP style
373 ** When \fIset\fP, Mutt-ng will check for new mail delivered while the
374 ** mailbox is open. Especially with MH mailboxes, this operation can
375 ** take quite some time since it involves scanning the directory and
376 ** checking each file to see if it has already been looked at. If it's
377 ** \fIunset\fP, no check for new mail is performed while the mailbox is open.
379 {"collapse_unread", DT_BOOL, R_NONE, OPTCOLLAPSEUNREAD, 1},
382 ** When \fIunset\fP, Mutt-ng will not collapse a thread if it contains any
385 {"uncollapse_jump", DT_BOOL, R_NONE, OPTUNCOLLAPSEJUMP, 0},
388 ** When \fIset\fP, Mutt-ng will jump to the next unread message, if any,
389 ** when the current thread is \fIun\fPcollapsed.
391 {"compose_format", DT_STR, R_BOTH, UL &ComposeFormat, UL "-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-"},
394 ** Controls the format of the status line displayed in the ``compose''
395 ** menu. This string is similar to ``$$status_format'', but has its own
396 ** set of \fTprintf(3)\fP-like sequences:
399 ** .dt %a .dd total number of attachments
400 ** .dt %h .dd local hostname
401 ** .dt %l .dd approximate size (in bytes) of the current message
402 ** .dt %v .dd Mutt-ng version string
405 ** See the text describing the ``$$status_format'' option for more
406 ** information on how to set ``$$compose_format''.
408 {"config_charset", DT_STR, R_NONE, UL &ConfigCharset, UL 0},
411 ** When defined, Mutt-ng will recode commands in rc files from this
414 {"confirmappend", DT_BOOL, R_NONE, OPTCONFIRMAPPEND, 1},
417 ** When \fIset\fP, Mutt-ng will prompt for confirmation when appending messages to
418 ** an existing mailbox.
420 {"confirmcreate", DT_BOOL, R_NONE, OPTCONFIRMCREATE, 1},
423 ** When \fIset\fP, Mutt-ng will prompt for confirmation when saving messages to a
424 ** mailbox which does not yet exist before creating it.
426 {"connect_timeout", DT_NUM, R_NONE, UL &ConnectTimeout, 30},
429 ** Causes Mutt-ng to timeout a network connection (for IMAP or POP) after this
430 ** many seconds if the connection is not able to be established. A negative
431 ** value causes Mutt-ng to wait indefinitely for the connection to succeed.
433 {"content_type", DT_STR, R_NONE, UL &ContentType, UL "text/plain"},
436 ** Sets the default \fTContent-Type:\fP header field for the body
437 ** of newly composed messages.
439 {"copy", DT_QUAD, R_NONE, OPT_COPY, M_YES},
442 ** This variable controls whether or not copies of your outgoing messages
443 ** will be saved for later references. Also see ``$$record'',
444 ** ``$$save_name'', ``$$force_name'' and ``$fcc-hook''.
447 {"crypt_use_gpgme", DT_BOOL, R_NONE, OPTCRYPTUSEGPGME, 0},
450 ** This variable controls the use the GPGME enabled crypto backends.
451 ** If it is \fIset\fP and Mutt-ng was build with gpgme support, the gpgme code for
452 ** S/MIME and PGP will be used instead of the classic code.
454 ** \fBNote\fP: You need to use this option in your \fT.muttngrc\fP configuration
455 ** file as it won't have any effect when used interactively.
458 {"crypt_autopgp", DT_BOOL, R_NONE, OPTCRYPTAUTOPGP, 1},
461 ** This variable controls whether or not Mutt-ng may automatically enable
462 ** PGP encryption/signing for messages. See also ``$$crypt_autoencrypt'',
463 ** ``$$crypt_replyencrypt'',
464 ** ``$$crypt_autosign'', ``$$crypt_replysign'' and ``$$smime_is_default''.
466 {"crypt_autosmime", DT_BOOL, R_NONE, OPTCRYPTAUTOSMIME, 1},
469 ** This variable controls whether or not Mutt-ng may automatically enable
470 ** S/MIME encryption/signing for messages. See also ``$$crypt_autoencrypt'',
471 ** ``$$crypt_replyencrypt'',
472 ** ``$$crypt_autosign'', ``$$crypt_replysign'' and ``$$smime_is_default''.
474 {"date_format", DT_STR, R_BOTH, UL &DateFmt, UL "!%a, %b %d, %Y at %I:%M:%S%p %Z"},
477 ** This variable controls the format of the date printed by the ``\fT%d\fP''
478 ** sequence in ``$$index_format''. This is passed to \fTstrftime(3)\fP
479 ** to process the date.
481 ** Unless the first character in the string is a bang (``\fT!\fP''), the month
482 ** and week day names are expanded according to the locale specified in
483 ** the variable ``$$locale''. If the first character in the string is a
484 ** bang, the bang is discarded, and the month and week day names in the
485 ** rest of the string are expanded in the \fIC\fP locale (that is in US
488 {"default_hook", DT_STR, R_NONE, UL &DefaultHook, UL "~f %s !~P | (~P ~C %s)"},
491 ** This variable controls how send-hooks, message-hooks, save-hooks,
492 ** and fcc-hooks will
493 ** be interpreted if they are specified with only a simple regexp,
494 ** instead of a matching pattern. The hooks are expanded when they are
495 ** declared, so a hook will be interpreted according to the value of this
496 ** variable at the time the hook is declared. The default value matches
497 ** if the message is either from a user matching the regular expression
498 ** given, or if it is from you (if the from address matches
499 ** ``alternates'') and is to or cc'ed to a user matching the given
500 ** regular expression.
502 {"delete", DT_QUAD, R_NONE, OPT_DELETE, M_ASKYES},
505 ** Controls whether or not messages are really deleted when closing or
506 ** synchronizing a mailbox. If set to \fIyes\fP, messages marked for
507 ** deleting will automatically be purged without prompting. If set to
508 ** \fIno\fP, messages marked for deletion will be kept in the mailbox.
510 {"delete_untag", DT_BOOL, R_NONE, OPTDELETEUNTAG, 1},
513 ** If this option is \fIset\fP, Mutt-ng will untag messages when marking them
514 ** for deletion. This applies when you either explicitly delete a message,
515 ** or when you save it to another folder.
517 {"digest_collapse", DT_BOOL, R_NONE, OPTDIGESTCOLLAPSE, 1},
520 ** If this option is \fIset\fP, Mutt-ng's received-attachments menu will not show the subparts of
521 ** individual messages in a multipart/digest. To see these subparts, press 'v' on that menu.
523 {"display_filter", DT_PATH, R_PAGER, UL &DisplayFilter, UL ""},
526 ** When \fIset\fP, specifies a command used to filter messages. When a message
527 ** is viewed it is passed as standard input to $$display_filter, and the
528 ** filtered message is read from the standard output.
530 #if defined(DL_STANDALONE) && defined(USE_DOTLOCK)
531 {"dotlock_program", DT_PATH, R_NONE, UL &MuttDotlock, UL BINDIR "/muttng_dotlock"},
534 ** Availability: Standalone and Dotlock
537 ** Contains the path of the \fTmuttng_dotlock(1)\fP binary to be used by
541 {"dsn_notify", DT_STR, R_NONE, UL &DsnNotify, UL ""},
544 ** \fBNote:\fP you should not enable this unless you are using Sendmail
545 ** 8.8.x or greater or in connection with the SMTP support via libESMTP.
547 ** This variable sets the request for when notification is returned. The
548 ** string consists of a comma separated list (no spaces!) of one or more
549 ** of the following: \fInever\fP, to never request notification,
550 ** \fIfailure\fP, to request notification on transmission failure,
551 ** \fIdelay\fP, to be notified of message delays, \fIsuccess\fP, to be
552 ** notified of successful transmission.
554 ** Example: \fTset dsn_notify="failure,delay"\fP
556 {"dsn_return", DT_STR, R_NONE, UL &DsnReturn, UL ""},
559 ** \fBNote:\fP you should not enable this unless you are using Sendmail
560 ** 8.8.x or greater or in connection with the SMTP support via libESMTP.
562 ** This variable controls how much of your message is returned in DSN
563 ** messages. It may be set to either \fIhdrs\fP to return just the
564 ** message header, or \fIfull\fP to return the full message.
566 ** Example: \fTset dsn_return=hdrs\fP
568 {"duplicate_threads", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTDUPTHREADS, 1},
571 ** This variable controls whether Mutt-ng, when sorting by threads, threads
572 ** messages with the same \fTMessage-Id:\fP header field together.
573 ** If it is \fIset\fP, it will indicate that it thinks they are duplicates
574 ** of each other with an equals sign in the thread diagram.
576 {"edit_headers", DT_BOOL, R_NONE, OPTEDITHDRS, 0},
579 ** This option allows you to edit the header of your outgoing messages
580 ** along with the body of your message.
582 {"editor", DT_PATH, R_NONE, UL &Editor, 0},
585 ** This variable specifies which editor is used by Mutt-ng.
586 ** It defaults to the value of the \fT$$$VISUAL\fP, or \fT$$$EDITOR\fP, environment
587 ** variable, or to the string "\fTvi\fP" if neither of those are set.
589 {"encode_from", DT_BOOL, R_NONE, OPTENCODEFROM, 0},
592 ** When \fIset\fP, Mutt-ng will \fTquoted-printable\fP encode messages when
593 ** they contain the string ``\fTFrom \fP'' (note the trailing space)
594 ** in the beginning of a line. Useful to avoid the tampering certain mail
595 ** delivery and transport agents tend to do with messages.
597 {"envelope_from", DT_BOOL, R_NONE, OPTENVFROM, 0},
600 ** When \fIset\fP, Mutt-ng will try to derive the message's \fIenvelope\fP
601 ** sender from the ``\fTFrom:\fP'' header field. Note that this information is passed
602 ** to the sendmail command using the ``\fT-f\fP" command line switch, so don't set this
603 ** option if you are using that switch in $$sendmail yourself,
604 ** or if the sendmail on your machine doesn't support that command
607 {"escape", DT_STR, R_NONE, UL &EscChar, UL "~"},
610 ** Escape character to use for functions in the builtin editor.
612 {"fast_reply", DT_BOOL, R_NONE, OPTFASTREPLY, 0},
615 ** When \fIset\fP, the initial prompt for recipients and subject are skipped
616 ** when replying to messages, and the initial prompt for subject is
617 ** skipped when forwarding messages.
619 ** \fBNote:\fP this variable has no effect when the ``$$autoedit''
620 ** variable is \fIset\fP.
622 {"fcc_attach", DT_BOOL, R_NONE, OPTFCCATTACH, 1},
625 ** This variable controls whether or not attachments on outgoing messages
626 ** are saved along with the main body of your message.
628 {"fcc_clear", DT_BOOL, R_NONE, OPTFCCCLEAR, 0},
631 ** When this variable is \fIset\fP, FCCs will be stored unencrypted and
632 ** unsigned, even when the actual message is encrypted and/or
636 {"file_charset", DT_STR, R_NONE, UL &FileCharset, UL 0},
639 ** This variable is a colon-separated list of character encoding
640 ** schemes for text file attatchments.
641 ** If \fIunset\fP, $$charset value will be used instead.
642 ** For example, the following configuration would work for Japanese
645 ** \fTset file_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"\fP
647 ** Note: ``\fTiso-2022-*\fP'' must be put at the head of the value as shown above
650 {"folder", DT_PATH, R_NONE, UL &Maildir, UL "~/Mail"},
653 ** Specifies the default location of your mailboxes. A ``\fT+\fP'' or ``\fT=\fP'' at the
654 ** beginning of a pathname will be expanded to the value of this
655 ** variable. Note that if you change this variable from the default
656 ** value you need to make sure that the assignment occurs \fIbefore\fP
657 ** you use ``+'' or ``='' for any other variables since expansion takes place
658 ** during the ``set'' command.
660 {"folder_format", DT_STR, R_INDEX, UL &FolderFormat, UL "%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f"},
663 ** This variable allows you to customize the file browser display to your
664 ** personal taste. This string is similar to ``$$index_format'', but has
665 ** its own set of \fTprintf(3)\fP-like sequences:
668 ** .dt %C .dd current file number
669 ** .dt %d .dd date/time folder was last modified
670 ** .dt %f .dd filename
671 ** .dt %F .dd file permissions
672 ** .dt %g .dd group name (or numeric gid, if missing)
673 ** .dt %l .dd number of hard links
674 ** .dt %N .dd N if folder has new mail, blank otherwise
675 ** .dt %s .dd size in bytes
676 ** .dt %t .dd * if the file is tagged, blank otherwise
677 ** .dt %u .dd owner name (or numeric uid, if missing)
678 ** .dt %>X .dd right justify the rest of the string and pad with character "X"
679 ** .dt %|X .dd pad to the end of the line with character "X"
682 {"followup_to", DT_BOOL, R_NONE, OPTFOLLOWUPTO, 1},
685 ** Controls whether or not the \fTMail-Followup-To:\fP header field is
686 ** generated when sending mail. When \fIset\fP, Mutt-ng will generate this
687 ** field when you are replying to a known mailing list, specified with
688 ** the ``subscribe'' or ``$lists'' commands or detected by common mailing list
691 ** This field has two purposes. First, preventing you from
692 ** receiving duplicate copies of replies to messages which you send
693 ** to mailing lists. Second, ensuring that you do get a reply
694 ** separately for any messages sent to known lists to which you are
695 ** not subscribed. The header will contain only the list's address
696 ** for subscribed lists, and both the list address and your own
697 ** email address for unsubscribed lists. Without this header, a
698 ** group reply to your message sent to a subscribed list will be
699 ** sent to both the list and your address, resulting in two copies
700 ** of the same email for you.
703 {"followup_to_poster", DT_SYN, R_NONE, UL "nntp_followup_to_poster", 0},
704 {"nntp_followup_to_poster", DT_QUAD, R_NONE, OPT_FOLLOWUPTOPOSTER, M_ASKYES},
707 ** Availability: NNTP
710 ** If this variable is \fIset\fP and the keyword "\fTposter\fP" is present in
711 ** the \fTFollowup-To:\fP header field, a follow-up to the newsgroup is not
712 ** permitted. The message will be mailed to the submitter of the
716 {"force_name", DT_BOOL, R_NONE, OPTFORCENAME, 0},
719 ** This variable is similar to ``$$save_name'', except that Mutt-ng will
720 ** store a copy of your outgoing message by the username of the address
721 ** you are sending to even if that mailbox does not exist.
723 ** Also see the ``$$record'' variable.
725 {"force_buffy_check", DT_BOOL, R_NONE, OPTFORCEBUFFYCHECK, 0},
728 ** When \fIset\fP, it causes Mutt-ng to check for new mail when the
729 ** \fIbuffy-list\fP command is invoked. When \fIunset\fP, \fIbuffy_list\fP
730 ** will just list all mailboxes which are already known to have new mail.
732 ** Also see the following variables: ``$$timeout'', ``$$mail_check'' and
733 ** ``$$imap_mail_check''.
735 {"forward_decode", DT_BOOL, R_NONE, OPTFORWDECODE, 1},
738 ** Controls the decoding of complex MIME messages into \fTtext/plain\fP when
739 ** forwarding a message. The message header is also RFC2047 decoded.
740 ** This variable is only used, if ``$$mime_forward'' is \fIunset\fP,
741 ** otherwise ``$$mime_forward_decode'' is used instead.
743 {"forward_edit", DT_QUAD, R_NONE, OPT_FORWEDIT, M_YES},
746 ** This quadoption controls whether or not the user is automatically
747 ** placed in the editor when forwarding messages. For those who always want
748 ** to forward with no modification, use a setting of \fIno\fP.
750 {"forward_format", DT_STR, R_NONE, UL &ForwFmt, UL "[%a: %s]"},
753 ** This variable controls the default subject when forwarding a message.
754 ** It uses the same format sequences as the ``$$index_format'' variable.
756 {"forward_quote", DT_BOOL, R_NONE, OPTFORWQUOTE, 0},
759 ** When \fIset\fP forwarded messages included in the main body of the
760 ** message (when ``$$mime_forward'' is \fIunset\fP) will be quoted using
761 ** ``$$indent_string''.
763 {"from", DT_ADDR, R_NONE, UL &From, UL 0},
766 ** This variable contains a default from address. It
767 ** can be overridden using my_hdr (including from send-hooks) and
768 ** ``$$reverse_name''. This variable is ignored if ``$$use_from''
772 ** \fTsend-hook Mutt-ng-devel@lists.berlios.de 'my_hdr From: Foo Bar <foo@bar.fb>'\fP
773 ** when replying to the mutt-ng developer's mailing list and Mutt-ng takes this email address.
775 ** Defaults to the contents of the environment variable \fT$$$EMAIL\fP.
777 {"gecos_mask", DT_RX, R_NONE, UL &GecosMask, UL "^[^,]*"},
780 ** A regular expression used by Mutt-ng to parse the GECOS field of a password
781 ** entry when expanding the alias. By default the regular expression is set
782 ** to ``\fT^[^,]*\fP'' which will return the string up to the first ``\fT,\fP'' encountered.
783 ** If the GECOS field contains a string like "lastname, firstname" then you
784 ** should do: \fTset gecos_mask=".*"\fP.
786 ** This can be useful if you see the following behavior: you address a e-mail
787 ** to user ID stevef whose full name is Steve Franklin. If Mutt-ng expands
788 ** stevef to ``Franklin'' stevef@foo.bar then you should set the gecos_mask to
789 ** a regular expression that will match the whole name so Mutt-ng will expand
790 ** ``Franklin'' to ``Franklin, Steve''.
793 {"group_index_format", DT_SYN, R_NONE, UL "nntp_group_index_format", 0},
794 {"nntp_group_index_format", DT_STR, R_BOTH, UL &GroupFormat, UL "%4C %M%N %5s %-45.45f %d"},
797 ** Availability: NNTP
800 ** This variable allows you to customize the newsgroup browser display to
801 ** your personal taste. This string is similar to ``$index_format'', but
802 ** has its own set of \fTprintf(3)\fP-like sequences:
805 ** %C current newsgroup number
806 ** %d description of newsgroup (retrieved from server)
808 ** %M ``-'' if newsgroup not allowed for direct post (moderated for example)
809 ** %N ``N'' if newsgroup is new, ``u'' if unsubscribed, blank otherwise
810 ** %n number of new articles in newsgroup
811 ** %s number of unread articles in newsgroup
812 ** %>X right justify the rest of the string and pad with character "X"
813 ** %|X pad to the end of the line with character "X"
817 {"hdrs", DT_BOOL, R_NONE, OPTHDRS, 1},
820 ** When \fIunset\fP, the header fields normally added by the ``$my_hdr''
821 ** command are not created. This variable \fImust\fP be \fIunset\fP before
822 ** composing a new message or replying in order to take effect. If \fIset\fP,
823 ** the user defined header fields are added to every new message.
825 {"header", DT_BOOL, R_NONE, OPTHEADER, 0},
828 ** When \fIset\fP, this variable causes Mutt-ng to include the header
829 ** of the message you are replying to into the edit buffer.
830 ** The ``$$weed'' setting applies.
832 {"help", DT_BOOL, R_BOTH, OPTHELP, 1},
835 ** When \fIset\fP, help lines describing the bindings for the major functions
836 ** provided by each menu are displayed on the first line of the screen.
838 ** \fBNote:\fP The binding will not be displayed correctly if the
839 ** function is bound to a sequence rather than a single keystroke. Also,
840 ** the help line may not be updated if a binding is changed while Mutt-ng is
841 ** running. Since this variable is primarily aimed at new users, neither
842 ** of these should present a major problem.
844 {"hidden_host", DT_BOOL, R_NONE, OPTHIDDENHOST, 0},
847 ** When \fIset\fP, Mutt-ng will skip the host name part of ``$$hostname'' variable
848 ** when adding the domain part to addresses. This variable does not
849 ** affect the generation of \fTMessage-ID:\fP header fields, and it will not lead to the
850 ** cut-off of first-level domains.
852 {"hide_limited", DT_BOOL, R_TREE|R_INDEX, OPTHIDELIMITED, 0},
855 ** When \fIset\fP, Mutt-ng will not show the presence of messages that are hidden
856 ** by limiting, in the thread tree.
858 {"hide_missing", DT_BOOL, R_TREE|R_INDEX, OPTHIDEMISSING, 1},
861 ** When \fIset\fP, Mutt-ng will not show the presence of missing messages in the
864 {"hide_thread_subject", DT_BOOL, R_TREE|R_INDEX, OPTHIDETHREADSUBJECT, 1},
867 ** When \fIset\fP, Mutt-ng will not show the subject of messages in the thread
868 ** tree that have the same subject as their parent or closest previously
869 ** displayed sibling.
871 {"hide_top_limited", DT_BOOL, R_TREE|R_INDEX, OPTHIDETOPLIMITED, 0},
874 ** When \fIset\fP, Mutt-ng will not show the presence of messages that are hidden
875 ** by limiting, at the top of threads in the thread tree. Note that when
876 ** $$hide_missing is set, this option will have no effect.
878 {"hide_top_missing", DT_BOOL, R_TREE|R_INDEX, OPTHIDETOPMISSING, 1},
881 ** When \fIset\fP, Mutt-ng will not show the presence of missing messages at the
882 ** top of threads in the thread tree. Note that when $$hide_limited is
883 ** \fIset\fP, this option will have no effect.
885 {"history", DT_NUM, R_NONE, UL &HistSize, 10},
888 ** This variable controls the size (in number of strings remembered) of
889 ** the string history buffer. The buffer is cleared each time the
890 ** variable is changed.
892 {"honor_followup_to", DT_QUAD, R_NONE, OPT_MFUPTO, M_YES},
895 ** This variable controls whether or not a \fTMail-Followup-To:\fP header field is
896 ** honored when group-replying to a message.
898 {"hostname", DT_STR, R_NONE, UL &Fqdn, 0},
901 ** Specifies the hostname to use after the ``\fT@\fP'' in local e-mail
902 ** addresses and during generation of \fTMessage-Id:\fP headers.
904 ** Please be sure to really know what you are doing when changing this variable
905 ** to configure a custom domain part of Message-IDs.
907 {"ignore_list_reply_to", DT_BOOL, R_NONE, OPTIGNORELISTREPLYTO, 0},
910 ** Affects the behaviour of the \fIreply\fP function when replying to
911 ** messages from mailing lists. When \fIset\fP, if the ``\fTReply-To:\fP'' header field is
912 ** set to the same value as the ``\fTTo:\fP'' header field, Mutt-ng assumes that the
913 ** ``\fTReply-To:\fP'' header field was set by the mailing list to automate responses
914 ** to the list, and will ignore this field. To direct a response to the
915 ** mailing list when this option is set, use the \fIlist-reply\fP
916 ** function; \fIgroup-reply\fP will reply to both the sender and the
920 {"imap_authenticators", DT_STR, R_NONE, UL &ImapAuthenticators, UL 0},
923 ** Availability: IMAP
926 ** This is a colon-delimited list of authentication methods Mutt-ng may
927 ** attempt to use to log in to an IMAP server, in the order Mutt-ng should
928 ** try them. Authentication methods are either ``\fTlogin\fP'' or the right
929 ** side of an IMAP ``\fTAUTH=\fP'' capability string, e.g. ``\fTdigest-md5\fP'',
930 ** ``\fTgssapi\fP'' or ``\fTcram-md5\fP''. This parameter is case-insensitive.
933 ** parameter is \fIunset\fP (the default) Mutt-ng will try all available methods,
934 ** in order from most-secure to least-secure.
936 ** Example: \fTset imap_authenticators="gssapi:cram-md5:login"\fP
938 ** \fBNote:\fP Mutt-ng will only fall back to other authentication methods if
939 ** the previous methods are unavailable. If a method is available but
940 ** authentication fails, Mutt-ng will not connect to the IMAP server.
942 { "imap_check_subscribed", DT_BOOL, R_NONE, OPTIMAPCHECKSUBSCRIBED, 0 },
945 ** When \fIset\fP, mutt will fetch the set of subscribed folders from
946 ** your server on connection, and add them to the set of mailboxes
947 ** it polls for new mail. See also the ``$mailboxes'' command.
950 {"imap_delim_chars", DT_STR, R_NONE, UL &ImapDelimChars, UL "/."},
953 ** Availability: IMAP
956 ** This contains the list of characters which you would like to treat
957 ** as folder separators for displaying IMAP paths. In particular it
958 ** helps in using the '\fT=\fP' shortcut for your $$folder variable.
960 {"imap_headers", DT_STR, R_INDEX, UL &ImapHeaders, UL 0},
963 ** Availability: IMAP
966 ** Mutt-ng requests these header fields in addition to the default headers
967 ** (``DATE FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE
968 ** CONTENT-DESCRIPTION IN-REPLY-TO REPLY-TO LINES X-LABEL'') from IMAP
969 ** servers before displaying the ``index'' menu. You may want to add more
970 ** headers for spam detection.
972 ** \fBNote:\fP This is a space separated list.
974 {"imap_home_namespace", DT_STR, R_NONE, UL &ImapHomeNamespace, UL 0},
977 ** Availability: IMAP
980 ** You normally want to see your personal folders alongside
981 ** your \fTINBOX\fP in the IMAP browser. If you see something else, you may set
982 ** this variable to the IMAP path to your folders.
984 {"imap_keepalive", DT_NUM, R_NONE, UL &ImapKeepalive, 900},
987 ** Availability: IMAP
990 ** This variable specifies the maximum amount of time in seconds that Mutt-ng
991 ** will wait before polling open IMAP connections, to prevent the server
992 ** from closing them before Mutt-ng has finished with them.
995 ** well within the RFC-specified minimum amount of time (30 minutes) before
996 ** a server is allowed to do this, but in practice the RFC does get
997 ** violated every now and then.
999 ** Reduce this number if you find yourself
1000 ** getting disconnected from your IMAP server due to inactivity.
1002 {"imap_login", DT_STR, R_NONE, UL &ImapLogin, 0 },
1005 ** Availability: IMAP
1008 ** Your login name on the IMAP server.
1010 ** This variable defaults to the value of ``$$imap_user.''
1012 {"imap_list_subscribed", DT_BOOL, R_NONE, OPTIMAPLSUB, 0},
1015 ** Availability: IMAP
1018 ** This variable configures whether IMAP folder browsing will look for
1019 ** only subscribed folders or all folders. This can be toggled in the
1020 ** IMAP browser with the \fItoggle-subscribed\fP function.
1022 {"imap_mail_check", DT_NUM, R_NONE, UL &ImapBuffyTimeout, 300},
1025 ** This variable configures how often (in seconds) Mutt-ng should look for
1026 ** new mail in IMAP folders. This is split from the ``$mail_check'' variable
1027 ** to generate less traffic and get more accurate information for local folders.
1029 {"imap_pass", DT_STR, R_NONE, UL &ImapPass, UL 0},
1032 ** Availability: IMAP
1035 ** Specifies the password for your IMAP account. If \fIunset\fP, Mutt-ng will
1036 ** prompt you for your password when you invoke the fetch-mail function.
1038 ** \fBWarning\fP: you should only use this option when you are on a
1039 ** fairly secure machine, because the superuser can read your configuration even
1040 ** if you are the only one who can read the file.
1042 {"imap_passive", DT_BOOL, R_NONE, OPTIMAPPASSIVE, 1},
1045 ** Availability: IMAP
1048 ** When \fIset\fP, Mutt-ng will not open new IMAP connections to check for new
1049 ** mail. Mutt-ng will only check for new mail over existing IMAP
1050 ** connections. This is useful if you don't want to be prompted to
1051 ** user/password pairs on Mutt-ng invocation, or if opening the connection
1054 {"imap_peek", DT_BOOL, R_NONE, OPTIMAPPEEK, 1},
1057 ** Availability: IMAP
1060 ** If \fIset\fP, Mutt-ng will avoid implicitly marking your mail as read whenever
1061 ** you fetch a message from the server. This is generally a good thing,
1062 ** but can make closing an IMAP folder somewhat slower. This option
1063 ** exists to appease speed freaks.
1065 {"imap_reconnect", DT_QUAD, R_NONE, OPT_IMAPRECONNECT, M_ASKYES},
1068 ** Availability: IMAP
1071 ** Controls whether or not Mutt-ng will try to reconnect to IMAP server when
1072 ** the connection is lost.
1074 {"imap_servernoise", DT_BOOL, R_NONE, OPTIMAPSERVERNOISE, 1},
1077 ** Availability: IMAP
1080 ** When \fIset\fP, Mutt-ng will display warning messages from the IMAP
1081 ** server as error messages. Since these messages are often
1082 ** harmless, or generated due to configuration problems on the
1083 ** server which are out of the users' hands, you may wish to suppress
1084 ** them at some point.
1086 {"imap_user", DT_STR, R_NONE, UL &ImapUser, UL 0},
1089 ** Availability: IMAP
1092 ** The name of the user whose mail you intend to access on the IMAP
1095 ** This variable defaults to your user name on the local machine.
1098 {"implicit_autoview", DT_BOOL, R_NONE, OPTIMPLICITAUTOVIEW, 0},
1101 ** If \fIset\fP, Mutt-ng will look for a mailcap entry with the
1102 ** ``\fTcopiousoutput\fP'' flag set for \fIevery\fP MIME attachment it doesn't have
1103 ** an internal viewer defined for. If such an entry is found, Mutt-ng will
1104 ** use the viewer defined in that entry to convert the body part to text
1107 {"include", DT_QUAD, R_NONE, OPT_INCLUDE, M_ASKYES},
1110 ** Controls whether or not a copy of the message(s) you are replying to
1111 ** is included in your reply.
1113 {"include_onlyfirst", DT_BOOL, R_NONE, OPTINCLUDEONLYFIRST, 0},
1116 ** Controls whether or not Mutt-ng includes only the first attachment
1117 ** of the message you are replying.
1119 {"indent_string", DT_STR, R_NONE, UL &Prefix, UL "> "},
1122 ** Specifies the string to prepend to each line of text quoted in a
1123 ** message to which you are replying. You are strongly encouraged not to
1124 ** change this value, as it tends to agitate the more fanatical netizens.
1126 {"index_format", DT_STR, R_BOTH, UL &HdrFmt, UL "%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s"},
1129 ** This variable allows you to customize the message index display to
1130 ** your personal taste.
1132 ** ``Format strings'' are similar to the strings used in the ``C''
1133 ** function \fTprintf(3)\fP to format output (see the man page for more detail).
1134 ** The following sequences are defined in Mutt-ng:
1137 ** .dt %a .dd address of the author
1138 ** .dt %A .dd reply-to address (if present; otherwise: address of author)
1139 ** .dt %b .dd filename of the original message folder (think mailBox)
1140 ** .dt %B .dd the list to which the letter was sent, or else the folder name (%b).
1141 ** .dt %c .dd number of characters (bytes) in the message
1142 ** .dt %C .dd current message number
1143 ** .dt %d .dd date and time of the message in the format specified by
1144 ** ``date_format'' converted to sender's time zone
1145 ** .dt %D .dd date and time of the message in the format specified by
1146 ** ``date_format'' converted to the local time zone
1147 ** .dt %e .dd current message number in thread
1148 ** .dt %E .dd number of messages in current thread
1149 ** .dt %f .dd entire From: line (address + real name)
1150 ** .dt %F .dd author name, or recipient name if the message is from you
1151 ** .dt %H .dd spam attribute(s) of this message
1152 ** .dt %g .dd newsgroup name (if compiled with nntp support)
1153 ** .dt %i .dd message-id of the current message
1154 ** .dt %l .dd number of lines in the message (does not work with maildir,
1155 ** mh, and possibly IMAP folders)
1156 ** .dt %L .dd If an address in the To or CC header field matches an address
1157 ** defined by the users ``subscribe'' command, this displays
1158 ** "To <list-name>", otherwise the same as %F.
1159 ** .dt %m .dd total number of message in the mailbox
1160 ** .dt %M .dd number of hidden messages if the thread is collapsed.
1161 ** .dt %N .dd message score
1162 ** .dt %n .dd author's real name (or address if missing)
1163 ** .dt %O .dd (_O_riginal save folder) Where Mutt-ng would formerly have
1164 ** stashed the message: list name or recipient name if no list
1165 ** .dt %s .dd subject of the message
1166 ** .dt %S .dd status of the message (N/D/d/!/r/\(as)
1167 ** .dt %t .dd `to:' field (recipients)
1168 ** .dt %T .dd the appropriate character from the $$to_chars string
1169 ** .dt %u .dd user (login) name of the author
1170 ** .dt %v .dd first name of the author, or the recipient if the message is from you
1171 ** .dt %W .dd name of organization of author (`organization:' field)
1172 ** .dt %y .dd `x-label:' field, if present
1173 ** .dt %Y .dd `x-label' field, if present, and (1) not at part of a thread tree,
1174 ** (2) at the top of a thread, or (3) `x-label' is different from
1175 ** preceding message's `x-label'.
1176 ** .dt %Z .dd message status flags
1177 ** .dt %{fmt} .dd the date and time of the message is converted to sender's
1178 ** time zone, and ``fmt'' is expanded by the library function
1179 ** ``strftime''; a leading bang disables locales
1180 ** .dt %[fmt] .dd the date and time of the message is converted to the local
1181 ** time zone, and ``fmt'' is expanded by the library function
1182 ** ``strftime''; a leading bang disables locales
1183 ** .dt %(fmt) .dd the local date and time when the message was received.
1184 ** ``fmt'' is expanded by the library function ``strftime'';
1185 ** a leading bang disables locales
1186 ** .dt %<fmt> .dd the current local time. ``fmt'' is expanded by the library
1187 ** function ``strftime''; a leading bang disables locales.
1188 ** .dt %>X .dd right justify the rest of the string and pad with character "X"
1189 ** .dt %|X .dd pad to the end of the line with character "X"
1192 ** See also: ``$$to_chars''.
1195 {"inews", DT_SYN, R_NONE, UL "nntp_inews", 0},
1196 {"nntp_inews", DT_PATH, R_NONE, UL &Inews, UL ""},
1199 ** Availability: NNTP
1202 ** If \fIset\fP, specifies the program and arguments used to deliver news posted
1203 ** by Mutt-ng. Otherwise, Mutt-ng posts article using current connection.
1204 ** The following \fTprintf(3)\fP-style sequence is understood:
1207 ** %s newsserver name
1210 ** Example: \fTset inews="/usr/local/bin/inews -hS"\fP
1213 {"ispell", DT_PATH, R_NONE, UL &Ispell, UL ISPELL},
1216 ** How to invoke ispell (GNU's spell-checking software).
1218 {"keep_flagged", DT_BOOL, R_NONE, OPTKEEPFLAGGED, 0},
1221 ** If \fIset\fP, read messages marked as flagged will not be moved
1222 ** from your spool mailbox to your ``$$mbox'' mailbox, or as a result of
1223 ** a ``$mbox-hook'' command.
1225 {"locale", DT_STR, R_BOTH, UL &Locale, UL "C"},
1228 ** The locale used by \fTstrftime(3)\fP to format dates. Legal values are
1229 ** the strings your system accepts for the locale variable \fTLC_TIME\fP.
1231 {"list_reply", DT_QUAD, R_NONE, OPT_LISTREPLY, M_NO},
1234 ** When \fIset\fP, address replies to the mailing list the original message came
1235 ** from (instead to the author only). Setting this option to ``\fIask-yes\fP'' or
1236 ** ``\fIask-no\fP'' will ask if you really intended to reply to the author only.
1238 {"max_display_recips", DT_NUM, R_PAGER, UL &MaxDispRecips, 0},
1241 ** When set non-zero, this specifies the maximum number of recipient header
1242 ** lines (\fTTo:\fP, \fTCc:\fP and \fTBcc:\fP) to display in the pager if header
1243 ** weeding is turned on. In case the number of lines exeeds its value, the
1244 ** last line will have 3 dots appended.
1246 {"max_line_length", DT_NUM, R_PAGER, UL &MaxLineLength, 0},
1249 ** When \fIset\fP, the maximum line length for displaying ``format = flowed'' messages is limited
1250 ** to this length. A value of 0 (which is also the default) means that the
1251 ** maximum line length is determined by the terminal width and $$wrapmargin.
1253 {"mail_check", DT_NUM, R_NONE, UL &BuffyTimeout, 5},
1256 ** This variable configures how often (in seconds) Mutt-ng should look for
1259 ** \fBNote:\fP This does not apply to IMAP mailboxes, see $$imap_mail_check.
1261 {"mailcap_path", DT_STR, R_NONE, UL &MailcapPath, 0},
1264 ** This variable specifies which files to consult when attempting to
1265 ** display MIME bodies not directly supported by Mutt-ng.
1267 {"mailcap_sanitize", DT_BOOL, R_NONE, OPTMAILCAPSANITIZE, 1},
1270 ** If \fIset\fP, Mutt-ng will restrict possible characters in mailcap \fT%\fP expandos
1271 ** to a well-defined set of safe characters. This is the safe setting,
1272 ** but we are not sure it doesn't break some more advanced MIME stuff.
1274 ** \fBDON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE
1279 {"header_cache", DT_PATH, R_NONE, UL &HeaderCache, 0},
1282 ** Availability: Header Cache
1285 ** The $$header_cache variable points to the header cache database.
1287 ** If $$header_cache points to a directory it will contain a header cache
1288 ** database per folder. If $$header_cache points to a file that file will
1289 ** be a single global header cache. By default it is \fIunset\fP so no
1290 ** header caching will be used.
1292 {"maildir_header_cache_verify", DT_BOOL, R_NONE, OPTHCACHEVERIFY, 1},
1295 ** Availability: Header Cache
1298 ** Check for Maildir unaware programs other than Mutt-ng having modified maildir
1299 ** files when the header cache is in use. This incurs one \fTstat(2)\fP per
1300 ** message every time the folder is opened.
1302 #if HAVE_GDBM || HAVE_DB4
1303 {"header_cache_pagesize", DT_STR, R_NONE, UL &HeaderCachePageSize, UL "16384"},
1306 ** Availability: Header Cache
1309 ** Change the maildir header cache database page size.
1312 ** or too small of a page size for the common header can waste
1313 ** space, memory effectiveness, or CPU time. The default should be more or
1314 ** less the best you can get. For details google for mutt header
1315 ** cache (first hit).
1317 #endif /* HAVE_GDBM || HAVE_DB 4 */
1319 { "header_cache_compress", DT_BOOL, R_NONE, OPTHCACHECOMPRESS, 0 },
1322 ** If enabled the header cache will be compressed. So only one fifth of the usual
1323 ** diskspace is used, but the uncompression can result in a slower open of the
1326 #endif /* HAVE_QDBM */
1327 #endif /* USE_HCACHE */
1328 {"maildir_trash", DT_BOOL, R_NONE, OPTMAILDIRTRASH, 0},
1331 ** If \fIset\fP, messages marked as deleted will be saved with the maildir
1332 ** (T)rashed flag instead of physically deleted.
1334 ** \fBNOTE:\fP this only applies
1335 ** to maildir-style mailboxes. Setting it will have no effect on other
1338 ** It is similiar to the trash option.
1340 {"mark_old", DT_BOOL, R_BOTH, OPTMARKOLD, 1},
1343 ** Controls whether or not Mutt-ng marks \fInew\fP \fBunread\fP
1344 ** messages as \fIold\fP if you exit a mailbox without reading them.
1346 ** With this option \fIset\fP, the next time you start Mutt-ng, the messages
1347 ** will show up with an "O" next to them in the ``index'' menu,
1348 ** indicating that they are old.
1350 {"markers", DT_BOOL, R_PAGER, OPTMARKERS, 1},
1353 ** Controls the display of wrapped lines in the internal pager. If set, a
1354 ** ``\fT+\fP'' marker is displayed at the beginning of wrapped lines. Also see
1355 ** the ``$$smart_wrap'' variable.
1357 {"mask", DT_RX, R_NONE, UL &Mask, UL "!^\\.[^.]"},
1360 ** A regular expression used in the file browser, optionally preceded by
1361 ** the \fInot\fP operator ``\fT!\fP''. Only files whose names match this mask
1362 ** will be shown. The match is always case-sensitive.
1364 {"mbox", DT_PATH, R_BOTH, UL &Inbox, UL "~/mbox"},
1367 ** This specifies the folder into which read mail in your ``$$spoolfile''
1368 ** folder will be appended.
1370 {"operating_system", DT_STR, R_NONE, UL &OperatingSystem, 0},
1373 ** This specifies the operating system name for the \fTUser-Agent:\fP header field. If
1374 ** this is \fIunset\fP, it will be set to the operating system name that \fTuname(2)\fP
1375 ** returns. If \fTuname(2)\fP fails, ``UNIX'' will be used.
1377 ** It may, for example, look as: ``\fTmutt-ng 1.5.9i (Linux)\fP''.
1379 {"sidebar_boundary", DT_STR, R_BOTH, UL &SidebarBoundary, UL "." },
1382 ** When the sidebar is displayed and $$sidebar_shorten_hierarchy is \fIset\fP, this
1383 ** variable specifies the characters at which to split a folder name into
1384 ** ``hierarchy items.''
1386 {"sidebar_delim", DT_STR, R_BOTH, UL &SidebarDelim, UL "|"},
1389 ** This specifies the delimiter between the sidebar (if visible) and
1392 {"sidebar_visible", DT_BOOL, R_BOTH, OPTMBOXPANE, 0},
1395 ** This specifies whether or not to show the sidebar (a list of folders specified
1396 ** with the ``mailboxes'' command).
1398 {"sidebar_width", DT_NUM, R_BOTH, UL &SidebarWidth, 0},
1401 ** The width of the sidebar.
1403 {"sidebar_newmail_only", DT_BOOL, R_BOTH, OPTSIDEBARNEWMAILONLY, 0},
1406 ** If \fIset\fP, only folders with new mail will be shown in the sidebar.
1408 {"sidebar_number_format", DT_STR, R_BOTH, UL &SidebarNumberFormat, UL "%m%?n?(%n)?%?f?[%f]?"},
1411 ** This variable controls how message counts are printed when the sidebar
1412 ** is enabled. If this variable is \fIempty\fP (\fIand only if\fP), no numbers
1413 ** will be printed \fIand\fP mutt-ng won't frequently count mail (which
1414 ** may be a great speedup esp. with mbox-style mailboxes.)
1416 ** The following \fTprintf(3)\fP-like sequences are supported all of which
1417 ** may be printed non-zero:
1420 ** .dt %d .dd Number of deleted messages. 1)
1421 ** .dt %F .dd Number of flagged messages.
1422 ** .dt %m .dd Total number of messages.
1423 ** .dt %M .dd Total number of messages shown, i.e. not hidden by a limit. 1)
1424 ** .dt %n .dd Number of new messages.
1425 ** .dt %t .dd Number of tagged messages. 1)
1428 ** 1) These expandos only have a non-zero value for the current mailbox and
1429 ** will always be zero otherwise.
1431 {"sidebar_shorten_hierarchy", DT_BOOL, R_NONE, OPTSHORTENHIERARCHY, 0},
1434 ** When \fIset\fP, the ``hierarchy'' of the sidebar entries will be shortened
1435 ** only if they cannot be printed in full length (because ``$$sidebar_width''
1436 ** is set to a too low value). For example, if the newsgroup name
1437 ** ``de.alt.sysadmin.recovery'' doesn't fit on the screen, it'll get shortened
1438 ** ``d.a.s.recovery'' while ``de.alt.d0'' still would and thus will not get
1441 ** At which characters this compression is done is controled via the
1442 ** $$sidebar_boundary variable.
1444 {"mbox_type", DT_MAGIC, R_NONE, UL &DefaultMagic, M_MBOX},
1447 ** The default mailbox type used when creating new folders. May be any of
1448 ** \fTmbox\fP, \fTMMDF\fP, \fTMH\fP and \fTMaildir\fP.
1450 {"metoo", DT_BOOL, R_NONE, OPTMETOO, 0},
1453 ** If \fIunset\fP, Mutt-ng will remove your address (see the ``alternates''
1454 ** command) from the list of recipients when replying to a message.
1456 {"menu_context", DT_NUM, R_NONE, UL &MenuContext, 0},
1459 ** This variable controls the number of lines of context that are given
1460 ** when scrolling through menus. (Similar to ``$$pager_context''.)
1462 {"menu_move_off", DT_BOOL, R_NONE, OPTMENUMOVEOFF, 1},
1465 ** When \fIunset\fP, the bottom entry of menus will never scroll up past
1466 ** the bottom of the screen, unless there are less entries than lines.
1467 ** When \fIset\fP, the bottom entry may move off the bottom.
1469 {"menu_scroll", DT_BOOL, R_NONE, OPTMENUSCROLL, 0},
1472 ** When \fIset\fP, menus will be scrolled up or down one line when you
1473 ** attempt to move across a screen boundary. If \fIunset\fP, the screen
1474 ** is cleared and the next or previous page of the menu is displayed
1475 ** (useful for slow links to avoid many redraws).
1477 {"meta_key", DT_BOOL, R_NONE, OPTMETAKEY, 0},
1480 ** If \fIset\fP, forces Mutt-ng to interpret keystrokes with the high bit (bit 8)
1481 ** set as if the user had pressed the \fTESC\fP key and whatever key remains
1482 ** after having the high bit removed. For example, if the key pressed
1483 ** has an ASCII value of \fT0xf4\fP, then this is treated as if the user had
1484 ** pressed \fTESC\fP then ``\fTx\fP''. This is because the result of removing the
1485 ** high bit from ``\fT0xf4\fP'' is ``\fT0x74\fP'', which is the ASCII character
1488 {"mh_purge", DT_BOOL, R_NONE, OPTMHPURGE, 0},
1491 ** When \fIunset\fP, Mutt-ng will mimic mh's behaviour and rename deleted messages
1492 ** to \fI,<old file name>\fP in mh folders instead of really deleting
1493 ** them. If the variable is set, the message files will simply be
1496 {"mh_seq_flagged", DT_STR, R_NONE, UL &MhFlagged, UL "flagged"},
1499 ** The name of the MH sequence used for flagged messages.
1501 {"mh_seq_replied", DT_STR, R_NONE, UL &MhReplied, UL "replied"},
1504 ** The name of the MH sequence used to tag replied messages.
1506 {"mh_seq_unseen", DT_STR, R_NONE, UL &MhUnseen, UL "unseen"},
1509 ** The name of the MH sequence used for unseen messages.
1511 {"mime_forward", DT_QUAD, R_NONE, OPT_MIMEFWD, M_NO},
1514 ** When \fIset\fP, the message you are forwarding will be attached as a
1515 ** separate MIME part instead of included in the main body of the
1518 ** This is useful for forwarding MIME messages so the receiver
1519 ** can properly view the message as it was delivered to you. If you like
1520 ** to switch between MIME and not MIME from mail to mail, set this
1521 ** variable to ask-no or ask-yes.
1523 ** Also see ``$$forward_decode'' and ``$$mime_forward_decode''.
1525 {"mime_forward_decode", DT_BOOL, R_NONE, OPTMIMEFORWDECODE, 0},
1528 ** Controls the decoding of complex MIME messages into \fTtext/plain\fP when
1529 ** forwarding a message while ``$$mime_forward'' is \fIset\fP. Otherwise
1530 ** ``$$forward_decode'' is used instead.
1532 {"mime_forward_rest", DT_QUAD, R_NONE, OPT_MIMEFWDREST, M_YES},
1535 ** When forwarding multiple attachments of a MIME message from the recvattach
1536 ** menu, attachments which cannot be decoded in a reasonable manner will
1537 ** be attached to the newly composed message if this option is set.
1541 {"mime_subject", DT_SYN, R_NONE, UL "nntp_mime_subject", 0},
1542 {"nntp_mime_subject", DT_BOOL, R_NONE, OPTMIMESUBJECT, 1},
1545 ** Availability: NNTP
1548 ** If \fIunset\fP, an 8-bit ``\fTSubject:\fP'' header field in a news article
1549 ** will not be encoded according to RFC2047.
1551 ** \fBNote:\fP Only change this setting if you know what you are doing.
1556 {"mix_entry_format", DT_STR, R_NONE, UL &MixEntryFormat, UL "%4n %c %-16s %a"},
1559 ** Availability: Mixmaster
1562 ** This variable describes the format of a remailer line on the mixmaster
1563 ** chain selection screen. The following \fTprintf(3)\fP-like sequences are
1567 ** .dt %n .dd The running number on the menu.
1568 ** .dt %c .dd Remailer capabilities.
1569 ** .dt %s .dd The remailer's short name.
1570 ** .dt %a .dd The remailer's e-mail address.
1573 {"mixmaster", DT_PATH, R_NONE, UL &Mixmaster, UL MIXMASTER},
1576 ** Availability: Mixmaster
1579 ** This variable contains the path to the Mixmaster binary on your
1580 ** system. It is used with various sets of parameters to gather the
1581 ** list of known remailers, and to finally send a message through the
1585 {"move", DT_QUAD, R_NONE, OPT_MOVE, M_ASKNO},
1588 ** Controls whether or not Mutt-ng will move read messages
1589 ** from your spool mailbox to your ``$$mbox'' mailbox, or as a result of
1590 ** a ``$mbox-hook'' command.
1592 {"message_format", DT_STR, R_NONE, UL &MsgFmt, UL "%s"},
1595 ** This is the string displayed in the ``attachment'' menu for
1596 ** attachments of type \fTmessage/rfc822\fP. For a full listing of defined
1597 ** \fTprintf(3)\fP-like sequences see the section on ``$$index_format''.
1599 {"msgid_format", DT_STR, R_NONE, UL &MsgIdFormat, UL "%Y%m%d%h%M%s.G%P%p"},
1602 ** This is the format for the ``local part'' of the \fTMessage-Id:\fP header
1603 ** field generated by Mutt-ng. If this variable is empty, no \fTMessage-Id:\fP
1604 ** headers will be generated. The '%'
1605 ** character marks that certain data will be added to the string, similar to
1606 ** \fTprintf(3)\fP. The following characters are allowed:
1609 ** .dt %d .dd the current day of month
1610 ** .dt %h .dd the current hour
1611 ** .dt %m .dd the current month
1612 ** .dt %M .dd the current minute
1613 ** .dt %O .dd the current UNIX timestamp (octal)
1614 ** .dt %p .dd the process ID
1615 ** .dt %P .dd the current Message-ID prefix (a character rotating with
1616 ** every Message-ID being generated)
1617 ** .dt %r .dd a random integer value (decimal)
1618 ** .dt %R .dd a random integer value (hexadecimal)
1619 ** .dt %s .dd the current second
1620 ** .dt %T .dd the current UNIX timestamp (decimal)
1621 ** .dt %X .dd the current UNIX timestamp (hexadecimal)
1622 ** .dt %Y .dd the current year (Y2K compliant)
1623 ** .dt %% .dd the '%' character
1626 ** \fBNote:\fP Please only change this setting if you know what you are doing.
1627 ** Also make sure to consult RFC2822 to produce technically \fIvalid\fP strings.
1629 {"narrow_tree", DT_BOOL, R_TREE|R_INDEX, OPTNARROWTREE, 0},
1632 ** This variable, when \fIset\fP, makes the thread tree narrower, allowing
1633 ** deeper threads to fit on the screen.
1636 {"news_cache_dir", DT_SYN, R_NONE, UL "nntp_cache_dir", 0},
1637 {"nntp_cache_dir", DT_PATH, R_NONE, UL &NewsCacheDir, UL "~/.muttng"},
1640 ** Availability: NNTP
1643 ** This variable points to directory where Mutt-ng will cache news
1644 ** article headers. If \fIunset\fP, headers will not be saved at all
1645 ** and will be reloaded each time when you enter a newsgroup.
1647 ** As for the header caching in connection with IMAP and/or Maildir,
1648 ** this drastically increases speed and lowers traffic.
1650 {"news_server", DT_SYN, R_NONE, UL "nntp_host", 0},
1651 {"nntp_host", DT_STR, R_NONE, UL &NewsServer, 0},
1654 ** Availability: NNTP
1657 ** This variable specifies the name (or address) of the NNTP server to be used.
1660 ** defaults to the value specified via the environment variable
1661 ** \fT$$$NNTPSERVER\fP or contained in the file \fT/etc/nntpserver\fP.
1664 ** specify a username and an alternative port for each newsserver, e.g.
1666 ** \fT[nntp[s]://][username[:password]@]newsserver[:port]\fP
1668 ** \fBNote:\fP Using a password as shown and stored in a configuration file
1669 ** presents a security risk since the superuser of your machine may read it
1670 ** regardless of the file's permissions.
1672 {"newsrc", DT_SYN, R_NONE, UL "nntp_newsrc", 0},
1673 {"nntp_newsrc", DT_PATH, R_NONE, UL &NewsRc, UL "~/.newsrc"},
1676 ** Availability: NNTP
1679 ** This file contains information about subscribed newsgroup and
1680 ** articles read so far.
1682 ** To ease the use of multiple news servers, the following \fTprintf(3)\fP-style
1683 ** sequence is understood:
1686 ** %s newsserver name
1689 {"nntp_context", DT_NUM, R_NONE, UL &NntpContext, 1000},
1692 ** Availability: NNTP
1695 ** This variable controls how many news articles to cache per newsgroup
1696 ** (if caching is enabled, see $$nntp_cache_dir) and how many news articles
1697 ** to show in the ``index'' menu.
1699 ** If there're more articles than defined with $$nntp_context, all older ones
1700 ** will be removed/not shown in the index.
1702 {"nntp_load_description", DT_BOOL, R_NONE, OPTLOADDESC, 1},
1705 ** Availability: NNTP
1708 ** This variable controls whether or not descriptions for newsgroups
1709 ** are to be loaded when subscribing to a newsgroup.
1711 {"nntp_user", DT_STR, R_NONE, UL &NntpUser, UL ""},
1714 ** Availability: NNTP
1717 ** Your login name on the NNTP server. If \fIunset\fP and the server requires
1718 ** authentification, Mutt-ng will prompt you for your account name.
1720 {"nntp_pass", DT_STR, R_NONE, UL &NntpPass, UL ""},
1723 ** Availability: NNTP
1726 ** Your password for NNTP account.
1728 ** \fBNote:\fP Storing passwords in a configuration file
1729 ** presents a security risk since the superuser of your machine may read it
1730 ** regardless of the file's permissions.
1732 {"nntp_poll", DT_SYN, R_NONE, UL "nntp_mail_check", 0},
1733 {"nntp_mail_check", DT_NUM, R_NONE, UL &NewsPollTimeout, 60},
1736 ** Availability: NNTP
1739 ** The time in seconds until any operations on a newsgroup except posting a new
1740 ** article will cause a recheck for new news. If set to 0, Mutt-ng will
1741 ** recheck on each operation in index (stepping, read article, etc.).
1743 {"nntp_reconnect", DT_QUAD, R_NONE, OPT_NNTPRECONNECT, M_ASKYES},
1746 ** Availability: NNTP
1749 ** Controls whether or not Mutt-ng will try to reconnect to a newsserver when the
1750 ** was connection lost.
1753 {"pager", DT_PATH, R_NONE, UL &Pager, UL "builtin"},
1756 ** This variable specifies which pager you would like to use to view
1757 ** messages. ``builtin'' means to use the builtin pager, otherwise this
1758 ** variable should specify the pathname of the external pager you would
1761 ** Using an external pager may have some disadvantages: Additional
1762 ** keystrokes are necessary because you can't call Mutt-ng functions
1763 ** directly from the pager, and screen resizes cause lines longer than
1764 ** the screen width to be badly formatted in the help menu.
1766 {"pager_context", DT_NUM, R_NONE, UL &PagerContext, 0},
1769 ** This variable controls the number of lines of context that are given
1770 ** when displaying the next or previous page in the internal pager. By
1771 ** default, Mutt-ng will display the line after the last one on the screen
1772 ** at the top of the next page (0 lines of context).
1774 {"pager_format", DT_STR, R_PAGER, UL &PagerFmt, UL "-%Z- %C/%m: %-20.20n %s"},
1777 ** This variable controls the format of the one-line message ``status''
1778 ** displayed before each message in either the internal or an external
1779 ** pager. The valid sequences are listed in the ``$$index_format''
1782 {"pager_index_lines", DT_NUM, R_PAGER, UL &PagerIndexLines, 0},
1785 ** Determines the number of lines of a mini-index which is shown when in
1786 ** the pager. The current message, unless near the top or bottom of the
1787 ** folder, will be roughly one third of the way down this mini-index,
1788 ** giving the reader the context of a few messages before and after the
1789 ** message. This is useful, for example, to determine how many messages
1790 ** remain to be read in the current thread. One of the lines is reserved
1791 ** for the status bar from the index, so a \fIpager_index_lines\fP of 6
1792 ** will only show 5 lines of the actual index. A value of 0 results in
1793 ** no index being shown. If the number of messages in the current folder
1794 ** is less than \fIpager_index_lines\fP, then the index will only use as
1795 ** many lines as it needs.
1797 {"pager_stop", DT_BOOL, R_NONE, OPTPAGERSTOP, 0},
1800 ** When \fIset\fP, the internal-pager will \fBnot\fP move to the next message
1801 ** when you are at the end of a message and invoke the \fInext-page\fP
1804 {"crypt_autosign", DT_BOOL, R_NONE, OPTCRYPTAUTOSIGN, 0},
1807 ** Setting this variable will cause Mutt-ng to always attempt to
1808 ** cryptographically sign outgoing messages. This can be overridden
1809 ** by use of the \fIpgp-menu\fP, when signing is not required or
1810 ** encryption is requested as well. If ``$$smime_is_default'' is \fIset\fP,
1811 ** then OpenSSL is used instead to create S/MIME messages and settings can
1812 ** be overridden by use of the \fIsmime-menu\fP.
1815 {"crypt_autoencrypt", DT_BOOL, R_NONE, OPTCRYPTAUTOENCRYPT, 0},
1818 ** Setting this variable will cause Mutt-ng to always attempt to PGP
1819 ** encrypt outgoing messages. This is probably only useful in
1820 ** connection to the \fIsend-hook\fP command. It can be overridden
1821 ** by use of the \fIpgp-menu\fP, when encryption is not required or
1822 ** signing is requested as well. If ``$$smime_is_default'' is \fIset\fP,
1823 ** then OpenSSL is used instead to create S/MIME messages and
1824 ** settings can be overridden by use of the \fIsmime-menu\fP.
1827 {"pgp_ignore_subkeys", DT_BOOL, R_NONE, OPTPGPIGNORESUB, 1},
1830 ** Setting this variable will cause Mutt-ng to ignore OpenPGP subkeys. Instead,
1831 ** the principal key will inherit the subkeys' capabilities. \fIUnset\fP this
1832 ** if you want to play interesting key selection games.
1835 {"crypt_replyencrypt", DT_BOOL, R_NONE, OPTCRYPTREPLYENCRYPT, 1},
1838 ** If \fIset\fP, automatically PGP or OpenSSL encrypt replies to messages which are
1842 {"crypt_replysign", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGN, 0},
1845 ** If \fIset\fP, automatically PGP or OpenSSL sign replies to messages which are
1848 ** \fBNote:\fP this does not work on messages that are encrypted \fBand\fP signed!
1851 {"crypt_replysignencrypted", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGNENCRYPTED, 0},
1854 ** If \fIset\fP, automatically PGP or OpenSSL sign replies to messages
1855 ** which are encrypted. This makes sense in combination with
1856 ** ``$$crypt_replyencrypt'', because it allows you to sign all
1857 ** messages which are automatically encrypted. This works around
1858 ** the problem noted in ``$$crypt_replysign'', that Mutt-ng is not able
1859 ** to find out whether an encrypted message is also signed.
1862 {"crypt_timestamp", DT_BOOL, R_NONE, OPTCRYPTTIMESTAMP, 1},
1865 ** If \fIset\fP, Mutt-ng will include a time stamp in the lines surrounding
1866 ** PGP or S/MIME output, so spoofing such lines is more difficult.
1867 ** If you are using colors to mark these lines, and rely on these,
1868 ** you may \fIunset\fP this setting.
1871 {"pgp_use_gpg_agent", DT_BOOL, R_NONE, OPTUSEGPGAGENT, 0},
1874 ** If \fIset\fP, Mutt-ng will use a possibly-running gpg-agent process.
1877 {"crypt_verify_sig", DT_QUAD, R_NONE, OPT_VERIFYSIG, M_YES},
1880 ** If ``\fIyes\fP'', always attempt to verify PGP or S/MIME signatures.
1881 ** If ``\fIask\fP'', ask whether or not to verify the signature.
1882 ** If ``\fIno\fP'', never attempt to verify cryptographic signatures.
1885 {"smime_is_default", DT_BOOL, R_NONE, OPTSMIMEISDEFAULT, 0},
1888 ** The default behaviour of Mutt-ng is to use PGP on all auto-sign/encryption
1889 ** operations. To override and to use OpenSSL instead this must be \fIset\fP.
1891 ** However, this has no effect while replying, since Mutt-ng will automatically
1892 ** select the same application that was used to sign/encrypt the original
1895 ** (Note that this variable can be overridden by unsetting $$crypt_autosmime.)
1898 {"smime_ask_cert_label", DT_BOOL, R_NONE, OPTASKCERTLABEL, 1},
1901 ** This flag controls whether you want to be asked to enter a label
1902 ** for a certificate about to be added to the database or not. It is
1903 ** \fIset\fP by default.
1906 {"smime_decrypt_use_default_key", DT_BOOL, R_NONE, OPTSDEFAULTDECRYPTKEY, 1},
1909 ** If \fIset\fP (default) this tells Mutt-ng to use the default key for decryption. Otherwise,
1910 ** if manage multiple certificate-key-pairs, Mutt-ng will try to use the mailbox-address
1911 ** to determine the key to use. It will ask you to supply a key, if it can't find one.
1914 {"pgp_entry_format", DT_STR, R_NONE, UL &PgpEntryFormat, UL "%4n %t%f %4l/0x%k %-4a %2c %u"},
1917 ** This variable allows you to customize the PGP key selection menu to
1918 ** your personal taste. This string is similar to ``$$index_format'', but
1919 ** has its own set of \fTprintf(3)\fP-like sequences:
1922 ** .dt %n .dd number
1923 ** .dt %k .dd key id
1924 ** .dt %u .dd user id
1925 ** .dt %a .dd algorithm
1926 ** .dt %l .dd key length
1928 ** .dt %c .dd capabilities
1929 ** .dt %t .dd trust/validity of the key-uid association
1930 ** .dt %[<s>] .dd date of the key where <s> is an \fTstrftime(3)\fP expression
1935 {"pgp_good_sign", DT_RX, R_NONE, UL &PgpGoodSign, 0},
1938 ** If you assign a text to this variable, then a PGP signature is only
1939 ** considered verified if the output from $$pgp_verify_command contains
1940 ** the text. Use this variable if the exit code from the command is 0
1941 ** even for bad signatures.
1944 {"pgp_check_exit", DT_BOOL, R_NONE, OPTPGPCHECKEXIT, 1},
1947 ** If \fIset\fP, Mutt-ng will check the exit code of the PGP subprocess when
1948 ** signing or encrypting. A non-zero exit code means that the
1949 ** subprocess failed.
1952 {"pgp_long_ids", DT_BOOL, R_NONE, OPTPGPLONGIDS, 0},
1955 ** If \fIset\fP, use 64 bit PGP key IDs. \fIUnset\fP uses the normal 32 bit Key IDs.
1958 {"pgp_retainable_sigs", DT_BOOL, R_NONE, OPTPGPRETAINABLESIG, 0},
1961 ** If \fIset\fP, signed and encrypted messages will consist of nested
1962 ** multipart/signed and multipart/encrypted body parts.
1964 ** This is useful for applications like encrypted and signed mailing
1965 ** lists, where the outer layer (multipart/encrypted) can be easily
1966 ** removed, while the inner multipart/signed part is retained.
1969 {"pgp_autoinline", DT_BOOL, R_NONE, OPTPGPAUTOINLINE, 0},
1972 ** This option controls whether Mutt-ng generates old-style inline
1973 ** (traditional) PGP encrypted or signed messages under certain
1974 ** circumstances. This can be overridden by use of the \fIpgp-menu\fP,
1975 ** when inline is not required.
1977 ** Note that Mutt-ng might automatically use PGP/MIME for messages
1978 ** which consist of more than a single MIME part. Mutt-ng can be
1979 ** configured to ask before sending PGP/MIME messages when inline
1980 ** (traditional) would not work.
1981 ** See also: ``$$pgp_mime_auto''.
1983 ** Also note that using the old-style PGP message format is \fBstrongly\fP
1984 ** \fBdeprecated\fP.
1987 {"pgp_replyinline", DT_BOOL, R_NONE, OPTPGPREPLYINLINE, 0},
1990 ** Setting this variable will cause Mutt-ng to always attempt to
1991 ** create an inline (traditional) message when replying to a
1992 ** message which is PGP encrypted/signed inline. This can be
1993 ** overridden by use of the \fIpgp-menu\fP, when inline is not
1994 ** required. This option does not automatically detect if the
1995 ** (replied-to) message is inline; instead it relies on Mutt-ng
1996 ** internals for previously checked/flagged messages.
1998 ** Note that Mutt-ng might automatically use PGP/MIME for messages
1999 ** which consist of more than a single MIME part. Mutt-ng can be
2000 ** configured to ask before sending PGP/MIME messages when inline
2001 ** (traditional) would not work.
2002 ** See also: ``$$pgp_mime_auto''.
2004 ** Also note that using the old-style PGP message format is \fBstrongly\fP
2005 ** \fBdeprecated\fP.
2009 {"pgp_show_unusable", DT_BOOL, R_NONE, OPTPGPSHOWUNUSABLE, 1},
2012 ** If \fIset\fP, Mutt-ng will display non-usable keys on the PGP key selection
2013 ** menu. This includes keys which have been revoked, have expired, or
2014 ** have been marked as ``disabled'' by the user.
2017 {"pgp_sign_as", DT_STR, R_NONE, UL &PgpSignAs, 0},
2020 ** If you have more than one key pair, this option allows you to specify
2021 ** which of your private keys to use. It is recommended that you use the
2022 ** keyid form to specify your key (e.g., ``\fT0x00112233\fP'').
2025 {"pgp_strict_enc", DT_BOOL, R_NONE, OPTPGPSTRICTENC, 1},
2028 ** If \fIset\fP, Mutt-ng will automatically encode PGP/MIME signed messages as
2029 ** \fTquoted-printable\fP. Please note that unsetting this variable may
2030 ** lead to problems with non-verifyable PGP signatures, so only change
2031 ** this if you know what you are doing.
2034 {"pgp_timeout", DT_NUM, R_NONE, UL &PgpTimeout, 300},
2037 ** The number of seconds after which a cached passphrase will expire if
2038 ** not used. Default: 300.
2041 {"pgp_sort_keys", DT_SORT|DT_SORT_KEYS, R_NONE, UL &PgpSortKeys, SORT_ADDRESS},
2044 ** Specifies how the entries in the ``pgp keys'' menu are sorted. The
2045 ** following are legal values:
2048 ** .dt address .dd sort alphabetically by user id
2049 ** .dt keyid .dd sort alphabetically by key id
2050 ** .dt date .dd sort by key creation date
2051 ** .dt trust .dd sort by the trust of the key
2054 ** If you prefer reverse order of the above values, prefix it with
2058 {"pgp_mime_auto", DT_QUAD, R_NONE, OPT_PGPMIMEAUTO, M_ASKYES},
2061 ** This option controls whether Mutt-ng will prompt you for
2062 ** automatically sending a (signed/encrypted) message using
2063 ** PGP/MIME when inline (traditional) fails (for any reason).
2065 ** Also note that using the old-style PGP message format is \fBstrongly\fP
2066 ** \fBdeprecated\fP.
2069 {"pgp_auto_decode", DT_BOOL, R_NONE, OPTPGPAUTODEC, 0},
2072 ** If \fIset\fP, Mutt-ng will automatically attempt to decrypt traditional PGP
2073 ** messages whenever the user performs an operation which ordinarily would
2074 ** result in the contents of the message being operated on. For example,
2075 ** if the user displays a pgp-traditional message which has not been manually
2076 ** checked with the check-traditional-pgp function, Mutt-ng will automatically
2077 ** check the message for traditional pgp.
2080 /* XXX Default values! */
2082 {"pgp_decode_command", DT_STR, R_NONE, UL &PgpDecodeCommand, 0},
2085 ** This format strings specifies a command which is used to decode
2086 ** application/pgp attachments.
2088 ** The PGP command formats have their own set of \fTprintf(3)\fP-like sequences:
2091 ** .dt %p .dd Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
2092 ** string otherwise. Note: This may be used with a %? construct.
2093 ** .dt %f .dd Expands to the name of a file containing a message.
2094 ** .dt %s .dd Expands to the name of a file containing the signature part
2095 ** . of a multipart/signed attachment when verifying it.
2096 ** .dt %a .dd The value of $$pgp_sign_as.
2097 ** .dt %r .dd One or more key IDs.
2100 ** For examples on how to configure these formats for the various versions
2101 ** of PGP which are floating around, see the pgp*.rc and gpg.rc files in
2102 ** the \fTsamples/\fP subdirectory which has been installed on your system
2103 ** alongside the documentation.
2106 {"pgp_getkeys_command", DT_STR, R_NONE, UL &PgpGetkeysCommand, 0},
2109 ** This command is invoked whenever Mutt-ng will need public key information.
2110 ** \fT%r\fP is the only \fTprintf(3)\fP-like sequence used with this format.
2113 {"pgp_verify_command", DT_STR, R_NONE, UL &PgpVerifyCommand, 0},
2116 ** This command is used to verify PGP signatures.
2119 {"pgp_decrypt_command", DT_STR, R_NONE, UL &PgpDecryptCommand, 0},
2122 ** This command is used to decrypt a PGP encrypted message.
2125 {"pgp_clearsign_command", DT_STR, R_NONE, UL &PgpClearSignCommand, 0},
2128 ** This format is used to create a old-style ``clearsigned'' PGP message.
2130 ** Note that the use of this format is \fBstrongly\fP \fBdeprecated\fP.
2133 {"pgp_sign_command", DT_STR, R_NONE, UL &PgpSignCommand, 0},
2136 ** This command is used to create the detached PGP signature for a
2137 ** multipart/signed PGP/MIME body part.
2140 {"pgp_encrypt_sign_command", DT_STR, R_NONE, UL &PgpEncryptSignCommand, 0},
2143 ** This command is used to both sign and encrypt a body part.
2146 {"pgp_encrypt_only_command", DT_STR, R_NONE, UL &PgpEncryptOnlyCommand, 0},
2149 ** This command is used to encrypt a body part without signing it.
2152 {"pgp_import_command", DT_STR, R_NONE, UL &PgpImportCommand, 0},
2155 ** This command is used to import a key from a message into
2156 ** the user's public key ring.
2159 {"pgp_export_command", DT_STR, R_NONE, UL &PgpExportCommand, 0},
2162 ** This command is used to export a public key from the user's
2166 {"pgp_verify_key_command", DT_STR, R_NONE, UL &PgpVerifyKeyCommand, 0},
2169 ** This command is used to verify key information from the key selection
2173 {"pgp_list_secring_command", DT_STR, R_NONE, UL &PgpListSecringCommand, 0},
2176 ** This command is used to list the secret key ring's contents. The
2177 ** output format must be analogous to the one used by
2178 ** \fTgpg --list-keys --with-colons\fP.
2180 ** This format is also generated by the \fTpgpring\fP utility which comes
2184 {"pgp_list_pubring_command", DT_STR, R_NONE, UL &PgpListPubringCommand, 0},
2187 ** This command is used to list the public key ring's contents. The
2188 ** output format must be analogous to the one used by
2189 ** \fTgpg --list-keys --with-colons\fP.
2191 ** This format is also generated by the \fTpgpring\fP utility which comes
2195 {"forward_decrypt", DT_BOOL, R_NONE, OPTFORWDECRYPT, 1},
2198 ** Controls the handling of encrypted messages when forwarding a message.
2199 ** When \fIset\fP, the outer layer of encryption is stripped off. This
2200 ** variable is only used if ``$$mime_forward'' is \fIset\fP and
2201 ** ``$$mime_forward_decode'' is \fIunset\fP.
2204 {"smime_timeout", DT_NUM, R_NONE, UL &SmimeTimeout, 300},
2207 ** The number of seconds after which a cached passphrase will expire if
2211 {"smime_encrypt_with", DT_STR, R_NONE, UL &SmimeCryptAlg, 0},
2214 ** This sets the algorithm that should be used for encryption.
2215 ** Valid choices are ``\fTdes\fP'', ``\fTdes3\fP'', ``\fTrc2-40\fP'',
2216 ** ``\fTrc2-64\fP'', ``\frc2-128\fP''.
2218 ** If \fIunset\fP ``\fI3des\fP'' (TripleDES) is used.
2221 {"smime_keys", DT_PATH, R_NONE, UL &SmimeKeys, 0},
2224 ** Since there is no pubring/secring as with PGP, Mutt-ng has to handle
2225 ** storage ad retrieval of keys/certs by itself. This is very basic right now,
2226 ** and stores keys and certificates in two different directories, both
2227 ** named as the hash-value retrieved from OpenSSL. There is an index file
2228 ** which contains mailbox-address keyid pair, and which can be manually
2229 ** edited. This one points to the location of the private keys.
2232 {"smime_ca_location", DT_PATH, R_NONE, UL &SmimeCALocation, 0},
2235 ** This variable contains the name of either a directory, or a file which
2236 ** contains trusted certificates for use with OpenSSL.
2239 {"smime_certificates", DT_PATH, R_NONE, UL &SmimeCertificates, 0},
2242 ** Since there is no pubring/secring as with PGP, Mutt-ng has to handle
2243 ** storage and retrieval of keys by itself. This is very basic right
2244 ** now, and keys and certificates are stored in two different
2245 ** directories, both named as the hash-value retrieved from
2246 ** OpenSSL. There is an index file which contains mailbox-address
2247 ** keyid pairs, and which can be manually edited. This one points to
2248 ** the location of the certificates.
2251 {"smime_decrypt_command", DT_STR, R_NONE, UL &SmimeDecryptCommand, 0},
2254 ** This format string specifies a command which is used to decrypt
2255 ** \fTapplication/x-pkcs7-mime\fP attachments.
2257 ** The OpenSSL command formats have their own set of \fTprintf(3)\fP-like sequences
2258 ** similar to PGP's:
2261 ** .dt %f .dd Expands to the name of a file containing a message.
2262 ** .dt %s .dd Expands to the name of a file containing the signature part
2263 ** . of a multipart/signed attachment when verifying it.
2264 ** .dt %k .dd The key-pair specified with $$smime_default_key
2265 ** .dt %c .dd One or more certificate IDs.
2266 ** .dt %a .dd The algorithm used for encryption.
2267 ** .dt %C .dd CA location: Depending on whether $$smime_ca_location
2268 ** . points to a directory or file, this expands to
2269 ** . "-CApath $$smime_ca_location" or "-CAfile $$smime_ca_location".
2272 ** For examples on how to configure these formats, see the smime.rc in
2273 ** the \fTsamples/\fP subdirectory which has been installed on your system
2274 ** alongside the documentation.
2277 {"smime_verify_command", DT_STR, R_NONE, UL &SmimeVerifyCommand, 0},
2280 ** This command is used to verify S/MIME signatures of type \fTmultipart/signed\fP.
2283 {"smime_verify_opaque_command", DT_STR, R_NONE, UL &SmimeVerifyOpaqueCommand, 0},
2286 ** This command is used to verify S/MIME signatures of type
2287 ** \fTapplication/x-pkcs7-mime\fP.
2290 {"smime_sign_command", DT_STR, R_NONE, UL &SmimeSignCommand, 0},
2293 ** This command is used to created S/MIME signatures of type
2294 ** \fTmultipart/signed\fP, which can be read by all mail clients.
2297 {"smime_sign_opaque_command", DT_STR, R_NONE, UL &SmimeSignOpaqueCommand, 0},
2300 ** This command is used to created S/MIME signatures of type
2301 ** \fTapplication/x-pkcs7-signature\fP, which can only be handled by mail
2302 ** clients supporting the S/MIME extension.
2305 {"smime_encrypt_command", DT_STR, R_NONE, UL &SmimeEncryptCommand, 0},
2308 ** This command is used to create encrypted S/MIME messages.
2311 {"smime_pk7out_command", DT_STR, R_NONE, UL &SmimePk7outCommand, 0},
2314 ** This command is used to extract PKCS7 structures of S/MIME signatures,
2315 ** in order to extract the public X509 certificate(s).
2318 {"smime_get_cert_command", DT_STR, R_NONE, UL &SmimeGetCertCommand, 0},
2321 ** This command is used to extract X509 certificates from a PKCS7 structure.
2324 {"smime_get_signer_cert_command", DT_STR, R_NONE, UL &SmimeGetSignerCertCommand, 0},
2327 ** This command is used to extract only the signers X509 certificate from a S/MIME
2328 ** signature, so that the certificate's owner may get compared to the
2329 ** email's ``\fTFrom:\fP'' header field.
2332 {"smime_import_cert_command", DT_STR, R_NONE, UL &SmimeImportCertCommand, 0},
2335 ** This command is used to import a certificate via \fTsmime_keysng\fP.
2338 {"smime_get_cert_email_command", DT_STR, R_NONE, UL &SmimeGetCertEmailCommand, 0},
2341 ** This command is used to extract the mail address(es) used for storing
2342 ** X509 certificates, and for verification purposes (to check whether the
2343 ** certificate was issued for the sender's mailbox).
2346 {"smime_default_key", DT_STR, R_NONE, UL &SmimeDefaultKey, 0},
2349 ** This is the default key-pair to use for signing. This must be set to the
2350 ** keyid (the hash-value that OpenSSL generates) to work properly
2353 #if defined(USE_LIBESMTP)
2354 {"smtp_auth_username", DT_SYN, R_NONE, UL "smtp_user", 0},
2355 {"smtp_user", DT_STR, R_NONE, UL &SmtpAuthUser, 0},
2358 ** Availability: SMTP
2361 ** Defines the username to use with SMTP AUTH. Setting this variable will
2362 ** cause Mutt-ng to attempt to use SMTP AUTH when sending.
2364 {"smtp_auth_password", DT_SYN, R_NONE, UL "smtp_pass", 0},
2365 {"smtp_pass", DT_STR, R_NONE, UL &SmtpAuthPass, 0},
2368 ** Availability: SMTP
2371 ** Defines the password to use with SMTP AUTH. If ``$$smtp_user''
2372 ** is set, but this variable is not, you will be prompted for a password
2375 ** \fBNote:\fP Storing passwords in a configuration file
2376 ** presents a security risk since the superuser of your machine may read it
2377 ** regardless of the file's permissions.
2379 {"smtp_envelope", DT_STR, R_NONE, UL &SmtpEnvFrom, 0},
2382 ** Availability: SMTP
2385 ** If this variable is non-empty, it'll be used as the envelope sender. If it's empty
2386 ** (the default), the value of the regular \fTFrom:\fP header will be used.
2389 ** This may be necessary as some providers don't allow for arbitrary values
2390 ** as the envelope sender but only a particular one which may not be the same as the
2391 ** user's desired \fTFrom:\fP header.
2393 {"smtp_host", DT_STR, R_NONE, UL &SmtpHost, 0},
2396 ** Availability: SMTP
2399 ** Defines the SMTP host which will be used to deliver mail, as opposed
2400 ** to invoking the sendmail binary. Setting this variable overrides the
2401 ** value of ``$$sendmail'', and any associated variables.
2403 {"smtp_port", DT_NUM, R_NONE, UL &SmtpPort, 25},
2406 ** Availability: SMTP
2409 ** Defines the port that the SMTP host is listening on for mail delivery.
2410 ** Must be specified as a number.
2412 ** Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP
2413 ** servers will probably desire 587, the mail submission port.
2415 {"smtp_use_tls", DT_STR, R_NONE, UL &SmtpUseTLS, 0},
2418 ** Availability: SMTP (and SSL)
2421 ** Defines wether to use STARTTLS. If this option is set to ``\fIrequired\fP''
2422 ** and the server does not support STARTTLS or there is an error in the
2423 ** TLS Handshake, the connection will fail. Setting this to ``\fIenabled\fP''
2424 ** will try to start TLS and continue without TLS in case of an error.
2427 ** Muttng still needs to have SSL support enabled in order to use it.
2430 #if defined(USE_SSL) || defined(USE_GNUTLS)
2432 {"ssl_client_cert", DT_PATH, R_NONE, UL &SslClientCert, 0},
2435 ** Availability: SSL
2438 ** The file containing a client certificate and its associated private
2441 #endif /* USE_SSL */
2442 {"ssl_force_tls", DT_BOOL, R_NONE, OPTSSLFORCETLS, 0 },
2445 ** If this variable is \fIset\fP, mutt-ng will require that all connections
2446 ** to remote servers be encrypted. Furthermore it will attempt to
2447 ** negotiate TLS even if the server does not advertise the capability,
2448 ** since it would otherwise have to abort the connection anyway. This
2449 ** option supersedes ``$$ssl_starttls''.
2451 {"ssl_starttls", DT_QUAD, R_NONE, OPT_SSLSTARTTLS, M_YES},
2454 ** Availability: SSL or GNUTLS
2457 ** If \fIset\fP (the default), Mutt-ng will attempt to use STARTTLS on servers
2458 ** advertising the capability. When \fIunset\fP, Mutt-ng will not attempt to
2459 ** use STARTTLS regardless of the server's capabilities.
2461 {"certificate_file", DT_PATH, R_NONE, UL &SslCertFile, UL "~/.mutt_certificates"},
2464 ** Availability: SSL or GNUTLS
2467 ** This variable specifies the file where the certificates you trust
2468 ** are saved. When an unknown certificate is encountered, you are asked
2469 ** if you accept it or not. If you accept it, the certificate can also
2470 ** be saved in this file and further connections are automatically
2473 ** You can also manually add CA certificates in this file. Any server
2474 ** certificate that is signed with one of these CA certificates are
2475 ** also automatically accepted.
2477 ** Example: \fTset certificate_file=~/.muttng/certificates\fP
2479 # if defined(_MAKEDOC) || !defined (USE_GNUTLS)
2480 {"ssl_usesystemcerts", DT_BOOL, R_NONE, OPTSSLSYSTEMCERTS, 1},
2483 ** Availability: SSL
2486 ** If set to \fIyes\fP, Mutt-ng will use CA certificates in the
2487 ** system-wide certificate store when checking if server certificate
2488 ** is signed by a trusted CA.
2490 {"entropy_file", DT_PATH, R_NONE, UL &SslEntropyFile, 0},
2493 ** Availability: SSL
2496 ** The file which includes random data that is used to initialize SSL
2497 ** library functions.
2499 {"ssl_use_sslv2", DT_BOOL, R_NONE, OPTSSLV2, 1},
2502 ** Availability: SSL
2505 ** This variables specifies whether to attempt to use SSLv2 in the
2506 ** SSL authentication process.
2508 # endif /* _MAKEDOC || !USE_GNUTLS */
2509 {"ssl_use_sslv3", DT_BOOL, R_NONE, OPTSSLV3, 1},
2512 ** Availability: SSL or GNUTLS
2515 ** This variables specifies whether to attempt to use SSLv3 in the
2516 ** SSL authentication process.
2518 {"ssl_use_tlsv1", DT_BOOL, R_NONE, OPTTLSV1, 1},
2521 ** Availability: SSL or GNUTLS
2524 ** This variables specifies whether to attempt to use TLSv1 in the
2525 ** SSL authentication process.
2528 {"ssl_min_dh_prime_bits", DT_NUM, R_NONE, UL &SslDHPrimeBits, 0},
2531 ** Availability: GNUTLS
2534 ** This variable specifies the minimum acceptable prime size (in bits)
2535 ** for use in any Diffie-Hellman key exchange. A value of 0 will use
2536 ** the default from the GNUTLS library.
2538 {"ssl_ca_certificates_file", DT_PATH, R_NONE, UL &SslCACertFile, 0},
2541 ** This variable specifies a file containing trusted CA certificates.
2542 ** Any server certificate that is signed with one of these CA
2543 ** certificates are also automatically accepted.
2545 ** Example: \fTset ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt\fP
2547 # endif /* USE_GNUTLS */
2548 # endif /* USE_SSL || USE_GNUTLS */
2549 {"pipe_split", DT_BOOL, R_NONE, OPTPIPESPLIT, 0},
2552 ** Used in connection with the \fIpipe-message\fP command and the ``tag-
2553 ** prefix'' or ``tag-prefix-cond'' operators.
2554 ** If this variable is \fIunset\fP, when piping a list of
2555 ** tagged messages Mutt-ng will concatenate the messages and will pipe them
2556 ** as a single folder. When \fIset\fP, Mutt-ng will pipe the messages one by one.
2557 ** In both cases the messages are piped in the current sorted order,
2558 ** and the ``$$pipe_sep'' separator is added after each message.
2560 {"pipe_decode", DT_BOOL, R_NONE, OPTPIPEDECODE, 0},
2563 ** Used in connection with the \fIpipe-message\fP command. When \fIunset\fP,
2564 ** Mutt-ng will pipe the messages without any preprocessing. When \fIset\fP, Mutt-ng
2565 ** will weed headers and will attempt to PGP/MIME decode the messages
2568 {"pipe_sep", DT_STR, R_NONE, UL &PipeSep, UL "\n"},
2571 ** The separator to add between messages when piping a list of tagged
2572 ** messages to an external Unix command.
2575 {"pop_authenticators", DT_STR, R_NONE, UL &PopAuthenticators, UL 0},
2578 ** Availability: POP
2581 ** This is a colon-delimited list of authentication methods Mutt-ng may
2582 ** attempt to use to log in to an POP server, in the order Mutt-ng should
2583 ** try them. Authentication methods are either ``\fTuser\fP'', ``\fTapop\fP''
2584 ** or any SASL mechanism, eg ``\fTdigest-md5\fP'', ``\fTgssapi\fP'' or ``\fTcram-md5\fP''.
2586 ** This parameter is case-insensitive. If this parameter is \fIunset\fP
2587 ** (the default) Mutt-ng will try all available methods, in order from
2588 ** most-secure to least-secure.
2590 ** Example: \fTset pop_authenticators="digest-md5:apop:user"\fP
2592 {"pop_auth_try_all", DT_BOOL, R_NONE, OPTPOPAUTHTRYALL, 1},
2595 ** Availability: POP
2598 ** If \fIset\fP, Mutt-ng will try all available methods. When \fIunset\fP, Mutt-ng will
2599 ** only fall back to other authentication methods if the previous
2600 ** methods are unavailable. If a method is available but authentication
2601 ** fails, Mutt-ng will not connect to the POP server.
2603 {"pop_checkinterval", DT_SYN, R_NONE, UL "pop_mail_check", 0},
2604 {"pop_mail_check", DT_NUM, R_NONE, UL &PopCheckTimeout, 60},
2607 ** Availability: POP
2610 ** This variable configures how often (in seconds) POP should look for
2613 {"pop_delete", DT_QUAD, R_NONE, OPT_POPDELETE, M_ASKNO},
2616 ** Availability: POP
2619 ** If \fIset\fP, Mutt-ng will delete successfully downloaded messages from the POP
2620 ** server when using the ``fetch-mail'' function. When \fIunset\fP, Mutt-ng will
2621 ** download messages but also leave them on the POP server.
2623 {"pop_host", DT_STR, R_NONE, UL &PopHost, UL ""},
2626 ** Availability: POP
2629 ** The name of your POP server for the ``fetch-mail'' function. You
2630 ** can also specify an alternative port, username and password, i.e.:
2632 ** \fT[pop[s]://][username[:password]@]popserver[:port]\fP
2634 ** \fBNote:\fP Storing passwords in a configuration file
2635 ** presents a security risk since the superuser of your machine may read it
2636 ** regardless of the file's permissions.
2638 {"pop_last", DT_BOOL, R_NONE, OPTPOPLAST, 0},
2641 ** Availability: POP
2644 ** If this variable is \fIset\fP, Mutt-ng will try to use the ``\fTLAST\fP'' POP command
2645 ** for retrieving only unread messages from the POP server when using
2646 ** the ``fetch-mail'' function.
2648 {"pop_reconnect", DT_QUAD, R_NONE, OPT_POPRECONNECT, M_ASKYES},
2651 ** Availability: POP
2654 ** Controls whether or not Mutt-ng will try to reconnect to a POP server when the
2655 ** connection is lost.
2657 {"pop_user", DT_STR, R_NONE, UL &PopUser, 0},
2660 ** Availability: POP
2663 ** Your login name on the POP server.
2665 ** This variable defaults to your user name on the local machine.
2667 {"pop_pass", DT_STR, R_NONE, UL &PopPass, UL ""},
2670 ** Availability: POP
2673 ** Specifies the password for your POP account. If \fIunset\fP, Mutt-ng will
2674 ** prompt you for your password when you open POP mailbox.
2676 ** \fBNote:\fP Storing passwords in a configuration file
2677 ** presents a security risk since the superuser of your machine may read it
2678 ** regardless of the file's permissions.
2680 #endif /* USE_POP */
2681 {"post_indent_string", DT_STR, R_NONE, UL &PostIndentString, UL ""},
2684 ** Similar to the ``$$attribution'' variable, Mutt-ng will append this
2685 ** string after the inclusion of a message which is being replied to.
2688 {"post_moderated", DT_SYN, R_NONE, UL "nntp_post_moderated", 0 },
2689 {"nntp_post_moderated", DT_QUAD, R_NONE, OPT_TOMODERATED, M_ASKYES},
2692 ** Availability: NNTP
2695 ** If set to \fIyes\fP, Mutt-ng will post articles to newsgroup that have
2696 ** not permissions to post (e.g. moderated).
2698 ** \fBNote:\fP if the newsserver
2699 ** does not support posting to that newsgroup or a group is totally read-only, that
2700 ** posting will not have any effect.
2703 {"postpone", DT_QUAD, R_NONE, OPT_POSTPONE, M_ASKYES},
2706 ** Controls whether or not messages are saved in the ``$$postponed''
2707 ** mailbox when you elect not to send immediately.
2709 {"postponed", DT_PATH, R_NONE, UL &Postponed, UL "~/postponed"},
2712 ** Mutt-ng allows you to indefinitely ``$postpone sending a message'' which
2713 ** you are editing. When you choose to postpone a message, Mutt-ng saves it
2714 ** in the mailbox specified by this variable. Also see the ``$$postpone''
2718 {"preconnect", DT_STR, R_NONE, UL &Preconnect, UL 0},
2721 ** If \fIset\fP, a shell command to be executed if Mutt-ng fails to establish
2722 ** a connection to the server. This is useful for setting up secure
2723 ** connections, e.g. with \fTssh(1)\fP. If the command returns a nonzero
2724 ** status, Mutt-ng gives up opening the server. Example:
2726 ** \fTpreconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net
2727 ** sleep 20 < /dev/null > /dev/null"\fP
2729 ** Mailbox ``foo'' on mailhost.net can now be reached
2730 ** as ``{localhost:1234}foo''.
2732 ** \fBNote:\fP For this example to work, you must be able to log in to the
2733 ** remote machine without having to enter a password.
2735 #endif /* USE_SOCKET */
2736 {"print", DT_QUAD, R_NONE, OPT_PRINT, M_ASKNO},
2739 ** Controls whether or not Mutt-ng really prints messages.
2740 ** This is set to \fIask-no\fP by default, because some people
2741 ** accidentally hit ``p'' often.
2743 {"print_command", DT_PATH, R_NONE, UL &PrintCmd, UL "lpr"},
2746 ** This specifies the command pipe that should be used to print messages.
2748 {"print_decode", DT_BOOL, R_NONE, OPTPRINTDECODE, 1},
2751 ** Used in connection with the print-message command. If this
2752 ** option is \fIset\fP, the message is decoded before it is passed to the
2753 ** external command specified by $$print_command. If this option
2754 ** is \fIunset\fP, no processing will be applied to the message when
2755 ** printing it. The latter setting may be useful if you are using
2756 ** some advanced printer filter which is able to properly format
2757 ** e-mail messages for printing.
2759 {"print_split", DT_BOOL, R_NONE, OPTPRINTSPLIT, 0},
2762 ** Used in connection with the print-message command. If this option
2763 ** is \fIset\fP, the command specified by $$print_command is executed once for
2764 ** each message which is to be printed. If this option is \fIunset\fP,
2765 ** the command specified by $$print_command is executed only once, and
2766 ** all the messages are concatenated, with a form feed as the message
2769 ** Those who use the \fTenscript(1)\fP program's mail-printing mode will
2770 ** most likely want to set this option.
2772 {"prompt_after", DT_BOOL, R_NONE, OPTPROMPTAFTER, 1},
2775 ** If you use an \fIexternal\fP ``$$pager'', setting this variable will
2776 ** cause Mutt-ng to prompt you for a command when the pager exits rather
2777 ** than returning to the index menu. If \fIunset\fP, Mutt-ng will return to the
2778 ** index menu when the external pager exits.
2780 {"query_command", DT_PATH, R_NONE, UL &QueryCmd, UL ""},
2783 ** This specifies the command that Mutt-ng will use to make external address
2784 ** queries. The string should contain a \fT%s\fP, which will be substituted
2785 ** with the query string the user types. See ``$query'' for more
2788 {"quit", DT_QUAD, R_NONE, OPT_QUIT, M_YES},
2791 ** This variable controls whether ``quit'' and ``exit'' actually quit
2792 ** from Mutt-ng. If it set to \fIyes\fP, they do quit, if it is set to \fIno\fP, they
2793 ** have no effect, and if it is set to \fIask-yes\fP or \fIask-no\fP, you are
2794 ** prompted for confirmation when you try to quit.
2796 {"quote_empty", DT_BOOL, R_NONE, OPTQUOTEEMPTY, 1},
2799 ** Controls whether or not empty lines will be quoted using
2800 ** ``$indent_string''.
2802 {"quote_quoted", DT_BOOL, R_NONE, OPTQUOTEQUOTED, 0},
2805 ** Controls how quoted lines will be quoted. If \fIset\fP, one quote
2806 ** character will be added to the end of existing prefix. Otherwise,
2807 ** quoted lines will be prepended by ``$indent_string''.
2809 {"quote_regexp", DT_RX, R_PAGER, UL &QuoteRegexp, UL "^([ \t]*[|>:}#])+"},
2812 ** A regular expression used in the internal-pager to determine quoted
2813 ** sections of text in the body of a message.
2815 ** \fBNote:\fP In order to use the \fIquoted\fP\fBx\fP patterns in the
2816 ** internal pager, you need to set this to a regular expression that
2817 ** matches \fIexactly\fP the quote characters at the beginning of quoted
2820 {"read_inc", DT_NUM, R_NONE, UL &ReadInc, 10},
2823 ** If set to a value greater than 0, Mutt-ng will display which message it
2824 ** is currently on when reading a mailbox. The message is printed after
2825 ** \fIread_inc\fP messages have been read (e.g., if set to 25, Mutt-ng will
2826 ** print a message when it reads message 25, and then again when it gets
2827 ** to message 50). This variable is meant to indicate progress when
2828 ** reading large mailboxes which may take some time.
2829 ** When set to 0, only a single message will appear before the reading
2832 ** Also see the ``$$write_inc'' variable.
2834 {"read_only", DT_BOOL, R_NONE, OPTREADONLY, 0},
2837 ** If set, all folders are opened in read-only mode.
2839 {"realname", DT_STR, R_BOTH, UL &Realname, 0},
2842 ** This variable specifies what ``real'' or ``personal'' name should be used
2843 ** when sending messages.
2845 ** By default, this is the GECOS field from \fT/etc/passwd\fP.
2848 ** variable will \fInot\fP be used when the user has set a real name
2849 ** in the $$from variable.
2851 {"recall", DT_QUAD, R_NONE, OPT_RECALL, M_ASKYES},
2854 ** Controls whether or not Mutt-ng recalls postponed messages
2855 ** when composing a new message. Also see ``$$postponed''.
2857 ** Setting this variable to \fIyes\fP is not generally useful, and thus not
2860 {"record", DT_PATH, R_NONE, UL &Outbox, UL ""},
2863 ** This specifies the file into which your outgoing messages should be
2864 ** appended. (This is meant as the primary method for saving a copy of
2865 ** your messages, but another way to do this is using the ``$my_hdr''
2866 ** command to create a \fTBcc:\fP header field with your email address in it.)
2868 ** The value of \fI$$record\fP is overridden by the ``$$force_name'' and
2869 ** ``$$save_name'' variables, and the ``$fcc-hook'' command.
2871 {"reply_regexp", DT_RX, R_INDEX|R_RESORT, UL &ReplyRegexp, UL "^(re([\\[0-9\\]+])*|aw):[ \t]*"},
2874 ** A regular expression used to recognize reply messages when threading
2875 ** and replying. The default value corresponds to the English ``Re:'' and
2876 ** the German ``Aw:''.
2878 {"reply_self", DT_BOOL, R_NONE, OPTREPLYSELF, 0},
2881 ** If \fIunset\fP and you are replying to a message sent by you, Mutt-ng will
2882 ** assume that you want to reply to the recipients of that message rather
2883 ** than to yourself.
2885 {"reply_to", DT_QUAD, R_NONE, OPT_REPLYTO, M_ASKYES},
2888 ** If \fIset\fP, when replying to a message, Mutt-ng will use the address listed
2889 ** in the ``\fTReply-To:\fP'' header field as the recipient of the reply. If \fIunset\fP,
2890 ** it will use the address in the ``\fTFrom:\fP'' header field instead.
2893 ** option is useful for reading a mailing list that sets the ``\fTReply-To:\fP''
2894 ** header field to the list address and you want to send a private
2895 ** message to the author of a message.
2897 {"resolve", DT_BOOL, R_NONE, OPTRESOLVE, 1},
2900 ** When set, the cursor will be automatically advanced to the next
2901 ** (possibly undeleted) message whenever a command that modifies the
2902 ** current message is executed.
2904 {"reverse_alias", DT_BOOL, R_BOTH, OPTREVALIAS, 0},
2907 ** This variable controls whether or not Mutt-ng will display the ``personal''
2908 ** name from your aliases in the index menu if it finds an alias that
2909 ** matches the message's sender. For example, if you have the following
2912 ** \fTalias juser abd30425@somewhere.net (Joe User)\fP
2914 ** and then you receive mail which contains the following header:
2916 ** \fTFrom: abd30425@somewhere.net\fP
2918 ** It would be displayed in the index menu as ``Joe User'' instead of
2919 ** ``abd30425@somewhere.net.'' This is useful when the person's e-mail
2920 ** address is not human friendly (like CompuServe addresses).
2922 {"reverse_name", DT_BOOL, R_BOTH, OPTREVNAME, 0},
2925 ** It may sometimes arrive that you receive mail to a certain machine,
2926 ** move the messages to another machine, and reply to some the messages
2927 ** from there. If this variable is \fIset\fP, the default \fTFrom:\fP line of
2928 ** the reply messages is built using the address where you received the
2929 ** messages you are replying to \fBif\fP that address matches your
2930 ** alternates. If the variable is \fIunset\fP, or the address that would be
2931 ** used doesn't match your alternates, the \fTFrom:\fP line will use
2932 ** your address on the current machine.
2934 {"reverse_realname", DT_BOOL, R_BOTH, OPTREVREAL, 1},
2937 ** This variable fine-tunes the behaviour of the $reverse_name feature.
2938 ** When it is \fIset\fP, Mutt-ng will use the address from incoming messages as-is,
2939 ** possibly including eventual real names. When it is \fIunset\fP, Mutt-ng will
2940 ** override any such real names with the setting of the $realname variable.
2942 {"rfc2047_parameters", DT_BOOL, R_NONE, OPTRFC2047PARAMS, 0},
2945 ** When this variable is \fIset\fP, Mutt-ng will decode RFC-2047-encoded MIME
2946 ** parameters. You want to set this variable when Mutt-ng suggests you
2947 ** to save attachments to files named like this:
2949 ** \fT=?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=\fP
2951 ** When this variable is \fIset\fP interactively, the change doesn't have
2952 ** the desired effect before you have changed folders.
2954 ** Note that this use of RFC 2047's encoding is explicitly,
2955 ** prohibited by the standard, but nevertheless encountered in the
2958 ** Also note that setting this parameter will \fInot\fP have the effect
2959 ** that Mutt-ng \fIgenerates\fP this kind of encoding. Instead, Mutt-ng will
2960 ** unconditionally use the encoding specified in RFC 2231.
2962 {"save_address", DT_BOOL, R_NONE, OPTSAVEADDRESS, 0},
2965 ** If \fIset\fP, Mutt-ng will take the sender's full address when choosing a
2966 ** default folder for saving a mail. If ``$$save_name'' or ``$$force_name''
2967 ** is \fIset\fP too, the selection of the fcc folder will be changed as well.
2969 {"save_empty", DT_BOOL, R_NONE, OPTSAVEEMPTY, 1},
2972 ** When \fIunset\fP, mailboxes which contain no saved messages will be removed
2973 ** when closed (the exception is ``$$spoolfile'' which is never removed).
2974 ** If \fIset\fP, mailboxes are never removed.
2976 ** \fBNote:\fP This only applies to mbox and MMDF folders, Mutt-ng does not
2977 ** delete MH and Maildir directories.
2979 {"save_name", DT_BOOL, R_NONE, OPTSAVENAME, 0},
2982 ** This variable controls how copies of outgoing messages are saved.
2983 ** When set, a check is made to see if a mailbox specified by the
2984 ** recipient address exists (this is done by searching for a mailbox in
2985 ** the ``$$folder'' directory with the \fIusername\fP part of the
2986 ** recipient address). If the mailbox exists, the outgoing message will
2987 ** be saved to that mailbox, otherwise the message is saved to the
2988 ** ``$$record'' mailbox.
2990 ** Also see the ``$$force_name'' variable.
2992 {"score", DT_BOOL, R_NONE, OPTSCORE, 1},
2995 ** When this variable is \fIunset\fP, scoring is turned off. This can
2996 ** be useful to selectively disable scoring for certain folders when the
2997 ** ``$$score_threshold_delete'' variable and friends are used.
3000 {"score_threshold_delete", DT_NUM, R_NONE, UL &ScoreThresholdDelete, UL -1},
3003 ** Messages which have been assigned a score equal to or lower than the value
3004 ** of this variable are automatically marked for deletion by Mutt-ng. Since
3005 ** Mutt-ng scores are always greater than or equal to zero, the default setting
3006 ** of this variable will never mark a message for deletion.
3008 {"score_threshold_flag", DT_NUM, R_NONE, UL &ScoreThresholdFlag, 9999},
3011 ** Messages which have been assigned a score greater than or equal to this
3012 ** variable's value are automatically marked ``flagged''.
3014 {"score_threshold_read", DT_NUM, R_NONE, UL &ScoreThresholdRead, UL -1},
3017 ** Messages which have been assigned a score equal to or lower than the value
3018 ** of this variable are automatically marked as read by Mutt-ng. Since
3019 ** Mutt-ng scores are always greater than or equal to zero, the default setting
3020 ** of this variable will never mark a message read.
3022 {"send_charset", DT_STR, R_NONE, UL &SendCharset, UL "us-ascii:iso-8859-1:utf-8"},
3025 ** A list of character sets for outgoing messages. Mutt-ng will use the
3026 ** first character set into which the text can be converted exactly.
3027 ** If your ``$$charset'' is not \fTiso-8859-1\fP and recipients may not
3028 ** understand \fTUTF-8\fP, it is advisable to include in the list an
3029 ** appropriate widely used standard character set (such as
3030 ** \fTiso-8859-2\fP, \fTkoi8-r\fP or \fTiso-2022-jp\fP) either
3031 ** instead of or after \fTiso-8859-1\fP.
3033 {"sendmail", DT_PATH, R_NONE, UL &Sendmail, UL SENDMAIL " -oem -oi"},
3036 ** Specifies the program and arguments used to deliver mail sent by Mutt-ng.
3037 ** Mutt-ng expects that the specified program interprets additional
3038 ** arguments as recipient addresses.
3040 {"sendmail_wait", DT_NUM, R_NONE, UL &SendmailWait, 0},
3043 ** Specifies the number of seconds to wait for the ``$$sendmail'' process
3044 ** to finish before giving up and putting delivery in the background.
3046 ** Mutt-ng interprets the value of this variable as follows:
3048 ** .dt >0 .dd number of seconds to wait for sendmail to finish before continuing
3049 ** .dt 0 .dd wait forever for sendmail to finish
3050 ** .dt <0 .dd always put sendmail in the background without waiting
3053 ** Note that if you specify a value other than 0, the output of the child
3054 ** process will be put in a temporary file. If there is some error, you
3055 ** will be informed as to where to find the output.
3057 {"shell", DT_PATH, R_NONE, UL &Shell, 0},
3060 ** Command to use when spawning a subshell. By default, the user's login
3061 ** shell from \fT/etc/passwd\fP is used.
3064 {"save_unsubscribed", DT_SYN, R_NONE, UL "nntp_save_unsubscribed", 0 },
3065 {"nntp_save_unsubscribed", DT_BOOL, R_NONE, OPTSAVEUNSUB, 0},
3068 ** Availability: NNTP
3071 ** When \fIset\fP, info about unsubscribed newsgroups will be saved into the
3072 ** ``newsrc'' file and into the news cache.
3076 {"show_new_news", DT_SYN, R_NONE, UL "nntp_show_new_news", 0 },
3077 {"nntp_show_new_news", DT_BOOL, R_NONE, OPTSHOWNEWNEWS, 1},
3080 ** Availability: NNTP
3083 ** If \fIset\fP, the newsserver will be asked for new newsgroups on entering
3084 ** the browser. Otherwise, it will be done only once for a newsserver.
3085 ** Also controls whether or not the number of new articles of subscribed
3086 ** newsgroups will be checked.
3088 {"show_only_unread", DT_SYN, R_NONE, UL "nntp_show_only_unread", 0 },
3089 {"nntp_show_only_unread", DT_BOOL, R_NONE, OPTSHOWONLYUNREAD, 0},
3092 ** Availability: NNTP
3095 ** If \fIset\fP, only subscribed newsgroups that contain unread articles
3096 ** will be displayed in the newsgroup browser.
3099 {"sig_dashes", DT_BOOL, R_NONE, OPTSIGDASHES, 1},
3102 ** If set, a line containing ``\fT-- \fP'' (dash, dash, space)
3103 ** will be inserted before your ``$$signature''. It is \fBstrongly\fP
3104 ** recommended that you not unset this variable unless your ``signature''
3105 ** contains just your name. The reason for this is because many software
3106 ** packages use ``\fT-- \n\fP'' to detect your signature.
3108 ** For example, Mutt-ng has the ability to highlight
3109 ** the signature in a different color in the builtin pager.
3111 {"sig_on_top", DT_BOOL, R_NONE, OPTSIGONTOP, 0},
3114 ** If \fIset\fP, the signature will be included before any quoted or forwarded
3115 ** text. It is \fBstrongly\fP recommended that you do not set this variable
3116 ** unless you really know what you are doing, and are prepared to take
3117 ** some heat from netiquette guardians.
3119 {"signature", DT_PATH, R_NONE, UL &Signature, UL "~/.signature"},
3122 ** Specifies the filename of your signature, which is appended to all
3123 ** outgoing messages. If the filename ends with a pipe (``\fT|\fP''), it is
3124 ** assumed that filename is a shell command and input should be read from
3127 {"signoff_string", DT_STR, R_NONE, UL &SignOffString, UL 0},
3130 ** If \fIset\fP, this string will be inserted before the signature. This is useful
3131 ** for people that want to sign off every message they send with their name.
3133 ** If you want to insert your website's URL, additional contact information or
3134 ** witty quotes into your mails, better use a signature file instead of
3135 ** the signoff string.
3137 {"simple_search", DT_STR, R_NONE, UL &SimpleSearch, UL "~f %s | ~s %s"},
3140 ** Specifies how Mutt-ng should expand a simple search into a real search
3141 ** pattern. A simple search is one that does not contain any of the ~
3142 ** operators. See ``$patterns'' for more information on search patterns.
3144 ** For example, if you simply type ``joe'' at a search or limit prompt, Mutt-ng
3145 ** will automatically expand it to the value specified by this variable.
3146 ** For the default value it would be:
3148 ** \fT~f joe | ~s joe\fP
3150 {"smart_wrap", DT_BOOL, R_PAGER, OPTWRAP, 1},
3153 ** Controls the display of lines longer than the screen width in the
3154 ** internal pager. If \fIset\fP, long lines are wrapped at a word boundary.
3155 ** If \fIunset\fP, lines are simply wrapped at the screen edge. Also see the
3156 ** ``$$markers'' variable.
3158 {"smileys", DT_RX, R_PAGER, UL &Smileys, UL "(>From )|(:[-^]?[][)(><}{|/DP])"},
3161 ** The \fIpager\fP uses this variable to catch some common false
3162 ** positives of ``$$quote_regexp'', most notably smileys in the beginning
3165 {"sleep_time", DT_NUM, R_NONE, UL &SleepTime, 1},
3168 ** Specifies time, in seconds, to pause while displaying certain informational
3169 ** messages, while moving from folder to folder and after expunging
3170 ** messages from the current folder. The default is to pause one second, so
3171 ** a value of zero for this option suppresses the pause.
3173 {"sort", DT_SORT, R_INDEX|R_RESORT, UL &Sort, SORT_DATE},
3176 ** Specifies how to sort messages in the \fIindex\fP menu. Valid values
3180 ** . date or date-sent
3183 ** . mailbox-order (unsorted)
3192 ** You may optionally use the ``reverse-'' prefix to specify reverse sorting
3193 ** order (example: \fTset sort=reverse-date-sent\fP).
3195 {"sort_alias", DT_SORT|DT_SORT_ALIAS, R_NONE, UL &SortAlias, SORT_ALIAS},
3198 ** Specifies how the entries in the ``alias'' menu are sorted. The
3199 ** following are legal values:
3202 ** . address (sort alphabetically by email address)
3203 ** . alias (sort alphabetically by alias name)
3204 ** . unsorted (leave in order specified in .muttrc)
3207 {"sort_aux", DT_SORT|DT_SORT_AUX, R_INDEX|R_RESORT_BOTH, UL &SortAux, SORT_DATE},
3210 ** When sorting by threads, this variable controls how threads are sorted
3211 ** in relation to other threads, and how the branches of the thread trees
3212 ** are sorted. This can be set to any value that ``$$sort'' can, except
3213 ** threads (in that case, Mutt-ng will just use date-sent). You can also
3214 ** specify the ``last-'' prefix in addition to ``reverse-'' prefix, but last-
3215 ** must come after reverse-. The last- prefix causes messages to be
3216 ** sorted against its siblings by which has the last descendant, using
3217 ** the rest of sort_aux as an ordering.
3219 ** For instance, \fTset sort_aux=last-date-received\fP would mean that if
3220 ** a new message is received in a thread, that thread becomes the last one
3221 ** displayed (or the first, if you have \fTset sort=reverse-threads\fP.)
3223 ** \fBNote:\fP For reversed ``$$sort'' order $$sort_aux is reversed again
3224 ** (which is not the right thing to do, but kept to not break any existing
3225 ** configuration setting).
3227 {"sort_browser", DT_SORT|DT_SORT_BROWSER, R_NONE, UL &BrowserSort, SORT_ALPHA},
3230 ** Specifies how to sort entries in the file browser. By default, the
3231 ** entries are sorted alphabetically. Valid values:
3234 ** . alpha (alphabetically)
3240 ** You may optionally use the ``reverse-'' prefix to specify reverse sorting
3241 ** order (example: \fTset sort_browser=reverse-date\fP).
3243 {"sort_re", DT_BOOL, R_INDEX|R_RESORT|R_RESORT_INIT, OPTSORTRE, 1},
3246 ** This variable is only useful when sorting by threads with
3247 ** ``$$strict_threads'' \fIunset\fP. In that case, it changes the heuristic
3248 ** Mutt-ng uses to thread messages by subject. With $$sort_re \fIset\fP,
3249 ** Mutt-ng will only attach a message as the child of another message by
3250 ** subject if the subject of the child message starts with a substring
3251 ** matching the setting of ``$$reply_regexp''. With $$sort_re \fIunset\fP,
3252 ** Mutt-ng will attach the message whether or not this is the case,
3253 ** as long as the non-``$$reply_regexp'' parts of both messages are identical.
3255 {"spam_separator", DT_STR, R_NONE, UL &SpamSep, UL ","},
3258 ** ``$spam_separator'' controls what happens when multiple spam headers
3259 ** are matched: if \fIunset\fP, each successive header will overwrite any
3260 ** previous matches value for the spam label. If \fIset\fP, each successive
3261 ** match will append to the previous, using ``$spam_separator'' as a
3264 {"spoolfile", DT_PATH, R_NONE, UL &Spoolfile, 0},
3267 ** If your spool mailbox is in a non-default place where Mutt-ng cannot find
3268 ** it, you can specify its location with this variable. Mutt-ng will
3269 ** automatically set this variable to the value of the environment
3270 ** variable $$$MAIL if it is not set.
3272 {"status_chars", DT_STR, R_BOTH, UL &StChars, UL "-*%A"},
3275 ** Controls the characters used by the ``\fT%r\fP'' indicator in
3276 ** ``$$status_format''. The first character is used when the mailbox is
3277 ** unchanged. The second is used when the mailbox has been changed, and
3278 ** it needs to be resynchronized. The third is used if the mailbox is in
3279 ** read-only mode, or if the mailbox will not be written when exiting
3280 ** that mailbox (You can toggle whether to write changes to a mailbox
3281 ** with the toggle-write operation, bound by default to ``\fT%\fP'').
3282 ** The fourth is used to indicate that the current folder has been
3283 ** opened in attach-message mode (Certain operations like composing
3284 ** a new mail, replying, forwarding, etc. are not permitted in this mode).
3286 {"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)---"},
3289 ** Controls the format of the status line displayed in the \fIindex\fP
3290 ** menu. This string is similar to ``$$index_format'', but has its own
3291 ** set of \fTprintf(3)\fP-like sequences:
3294 ** .dt %b .dd number of mailboxes with new mail *
3295 ** .dt %B .dd the short pathname of the current mailbox
3296 ** .dt %d .dd number of deleted messages *
3297 ** .dt %f .dd the full pathname of the current mailbox
3298 ** .dt %F .dd number of flagged messages *
3299 ** .dt %h .dd local hostname
3300 ** .dt %l .dd size (in bytes) of the current mailbox *
3301 ** .dt %L .dd size (in bytes) of the messages shown
3302 ** (i.e., which match the current limit) *
3303 ** .dt %m .dd the number of messages in the mailbox *
3304 ** .dt %M .dd the number of messages shown (i.e., which match the current limit) *
3305 ** .dt %n .dd number of new messages in the mailbox *
3306 ** .dt %o .dd number of old unread messages *
3307 ** .dt %p .dd number of postponed messages *
3308 ** .dt %P .dd percentage of the way through the index
3309 ** .dt %r .dd modified/read-only/won't-write/attach-message indicator,
3310 ** according to $$status_chars
3311 ** .dt %s .dd current sorting mode ($$sort)
3312 ** .dt %S .dd current aux sorting method ($$sort_aux)
3313 ** .dt %t .dd number of tagged messages *
3314 ** .dt %u .dd number of unread messages *
3315 ** .dt %v .dd Mutt-ng version string
3316 ** .dt %V .dd currently active limit pattern, if any *
3317 ** .dt %>X .dd right justify the rest of the string and pad with "X"
3318 ** .dt %|X .dd pad to the end of the line with "X"
3321 ** * = can be optionally printed if nonzero
3323 ** Some of the above sequences can be used to optionally print a string
3324 ** if their value is nonzero. For example, you may only want to see the
3325 ** number of flagged messages if such messages exist, since zero is not
3326 ** particularly meaningful. To optionally print a string based upon one
3327 ** of the above sequences, the following construct is used
3329 ** \fT%?<sequence_char>?<optional_string>?\fP
3331 ** where \fIsequence_char\fP is a character from the table above, and
3332 ** \fIoptional_string\fP is the string you would like printed if
3333 ** \fIsequence_char\fP is nonzero. \fIoptional_string\fP \fBmay\fP contain
3334 ** other sequences as well as normal text, but you may \fBnot\fP nest
3335 ** optional strings.
3337 ** Here is an example illustrating how to optionally print the number of
3338 ** new messages in a mailbox:
3340 ** \fT%?n?%n new messages.?\fP
3342 ** Additionally you can switch between two strings, the first one, if a
3343 ** value is zero, the second one, if the value is nonzero, by using the
3344 ** following construct:
3346 ** \fT%?<sequence_char>?<if_string>&<else_string>?\fP
3348 ** You can additionally force the result of any \fTprintf(3)\fP-like sequence
3349 ** to be lowercase by prefixing the sequence character with an underscore
3350 ** (\fT_\fP) sign. For example, if you want to display the local hostname in
3351 ** lowercase, you would use:
3355 ** If you prefix the sequence character with a colon (\fT:\fP) character, Mutt-ng
3356 ** will replace any dots in the expansion by underscores. This might be helpful
3357 ** with IMAP folders that don't like dots in folder names.
3359 {"status_on_top", DT_BOOL, R_BOTH, OPTSTATUSONTOP, 0},
3362 ** Setting this variable causes the ``status bar'' to be displayed on
3363 ** the first line of the screen rather than near the bottom.
3365 {"strict_mailto", DT_BOOL, R_NONE, OPTSTRICTMAILTO, 1},
3369 ** With mailto: style links, a body as well as arbitrary header information
3370 ** may be embedded. This may lead to (user) headers being overwriten without note
3371 ** if ``$$edit_headers'' is unset.
3374 ** If this variable is \fIset\fP, mutt-ng is strict and allows anything to be
3375 ** changed. If it's \fIunset\fP, all headers given will be prefixed with
3376 ** ``X-Mailto-'' and the message including headers will be shown in the editor
3377 ** regardless of what ``$$edit_headers'' is set to.
3379 {"strict_mime", DT_BOOL, R_NONE, OPTSTRICTMIME, 1},
3382 ** When \fIunset\fP, non MIME-compliant messages that doesn't have any
3383 ** charset indication in the ``\fTContent-Type:\fP'' header field can
3384 ** be displayed (non MIME-compliant messages are often generated by old
3385 ** mailers or buggy mailers like MS Outlook Express).
3386 ** See also $$assumed_charset.
3388 ** This option also replaces linear-white-space between encoded-word
3389 ** and *text to a single space to prevent the display of MIME-encoded
3390 ** ``\fTSubject:\fP'' header field from being devided into multiple lines.
3392 {"strict_threads", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTSTRICTTHREADS, 0},
3395 ** If \fIset\fP, threading will only make use of the ``\fTIn-Reply-To:\fP'' and
3396 ** ``\fTReferences:\fP'' header fields when you ``$$sort'' by message threads. By
3397 ** default, messages with the same subject are grouped together in
3398 ** ``pseudo threads.'' This may not always be desirable, such as in a
3399 ** personal mailbox where you might have several unrelated messages with
3400 ** the subject ``hi'' which will get grouped together.
3402 {"strip_was", DT_BOOL, R_NONE, OPTSTRIPWAS, 0},
3405 ** When \fIset\fP, mutt-ng will remove the trailing part of the ``\fTSubject:\fP''
3406 ** line which matches $$strip_was_regex when replying. This is useful to
3407 ** properly react on subject changes and reduce ``subject noise.'' (esp. in Usenet)
3409 {"strip_was_regex", DT_RX, R_NONE, UL &StripWasRegexp, UL "\\([Ww][Aa][RrSs]: .*\\)[ ]*$"},
3412 ** When non-empty and $$strip_was is \fIset\fP, mutt-ng will remove this
3413 ** trailing part of the ``Subject'' line when replying if it won't be empty
3416 {"stuff_quoted", DT_BOOL, R_BOTH, OPTSTUFFQUOTED, 0},
3419 ** If \fIset\fP, attachments with flowed format will have their quoting ``stuffed'',
3420 ** i.e. a space will be inserted between the quote characters and the actual
3423 {"suspend", DT_BOOL, R_NONE, OPTSUSPEND, 1},
3426 ** When \fIunset\fP, Mutt-ng won't stop when the user presses the terminal's
3427 ** \fIsusp\fP key, usually \fTCTRL+Z\fP. This is useful if you run Mutt-ng
3428 ** inside an xterm using a command like ``\fTxterm -e muttng\fP.''
3430 {"text_flowed", DT_BOOL, R_NONE, OPTTEXTFLOWED, 0},
3433 ** When \fIset\fP, Mutt-ng will generate \fTtext/plain; format=flowed\fP attachments.
3434 ** This format is easier to handle for some mailing software, and generally
3435 ** just looks like ordinary text. To actually make use of this format's
3436 ** features, you'll need support in your editor.
3438 ** Note that $$indent_string is ignored when this option is set.
3440 {"thread_received", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTTHREADRECEIVED, 0},
3443 ** When \fIset\fP, Mutt-ng uses the date received rather than the date sent
3444 ** to thread messages by subject.
3446 {"thorough_search", DT_BOOL, R_NONE, OPTTHOROUGHSRC, 0},
3449 ** Affects the \fT~b\fP and \fT~h\fP search operations described in
3450 ** section ``$patterns'' above. If \fIset\fP, the headers and attachments of
3451 ** messages to be searched are decoded before searching. If \fIunset\fP,
3452 ** messages are searched as they appear in the folder.
3454 {"tilde", DT_BOOL, R_PAGER, OPTTILDE, 0},
3457 ** When \fIset\fP, the internal-pager will pad blank lines to the bottom of the
3458 ** screen with a tilde (~).
3460 {"timeout", DT_NUM, R_NONE, UL &Timeout, 600},
3463 ** This variable controls the \fInumber of seconds\fP Mutt-ng will wait
3464 ** for a key to be pressed in the main menu before timing out and
3465 ** checking for new mail. A value of zero or less will cause Mutt-ng
3466 ** to never time out.
3468 {"tmpdir", DT_PATH, R_NONE, UL &Tempdir, 0},
3471 ** This variable allows you to specify where Mutt-ng will place its
3472 ** temporary files needed for displaying and composing messages. If
3473 ** this variable is not set, the environment variable \fT$$$TMPDIR\fP is
3474 ** used. If \fT$$$TMPDIR\fP is not set then "\fT/tmp\fP" is used.
3476 {"to_chars", DT_STR, R_BOTH, UL &Tochars, UL " +TCFL"},
3479 ** Controls the character used to indicate mail addressed to you. The
3480 ** first character is the one used when the mail is NOT addressed to your
3481 ** address (default: space). The second is used when you are the only
3482 ** recipient of the message (default: +). The third is when your address
3483 ** appears in the ``\fTTo:\fP'' header field, but you are not the only recipient of
3484 ** the message (default: T). The fourth character is used when your
3485 ** address is specified in the ``\fTCc:\fP'' header field, but you are not the only
3486 ** recipient. The fifth character is used to indicate mail that was sent
3487 ** by \fIyou\fP. The sixth character is used to indicate when a mail
3488 ** was sent to a mailing-list you're subscribe to (default: L).
3490 {"trash", DT_PATH, R_NONE, UL &TrashPath, 0},
3493 ** If \fIset\fP, this variable specifies the path of the trash folder where the
3494 ** mails marked for deletion will be moved, instead of being irremediably
3497 ** \fBNote\fP: When you delete a message in the trash folder, it is really
3498 ** deleted, so that there is no way to recover mail.
3501 {"tunnel", DT_STR, R_NONE, UL &Tunnel, UL 0},
3504 ** Setting this variable will cause Mutt-ng to open a pipe to a command
3505 ** instead of a raw socket. You may be able to use this to set up
3506 ** preauthenticated connections to your IMAP/POP3 server. Example:
3508 ** \fTtunnel="ssh -q mailhost.net /usr/local/libexec/imapd"\fP
3510 ** \fBNote:\fP For this example to work you must be able to log in to the remote
3511 ** machine without having to enter a password.
3514 {"umask", DT_NUM, R_NONE, UL &Umask, 0077},
3517 ** This sets the umask that will be used by Mutt-ng when creating all
3518 ** kinds of files. If \fIunset\fP, the default value is \fT077\fP.
3520 {"use_8bitmime", DT_BOOL, R_NONE, OPTUSE8BITMIME, 0},
3523 ** \fBWarning:\fP do not set this variable unless you are using a version
3524 ** of sendmail which supports the \fT-B8BITMIME\fP flag (such as sendmail
3525 ** 8.8.x) or in connection with the SMTP support via libESMTP.
3526 ** Otherwise you may not be able to send mail.
3528 ** When \fIset\fP, Mutt-ng will either invoke ``$$sendmail'' with the \fT-B8BITMIME\fP
3529 ** flag when sending 8-bit messages to enable ESMTP negotiation or tell
3530 ** libESMTP to do so.
3532 {"use_domain", DT_BOOL, R_NONE, OPTUSEDOMAIN, 1},
3535 ** When \fIset\fP, Mutt-ng will qualify all local addresses (ones without the
3536 ** @host portion) with the value of ``$$hostname''. If \fIunset\fP, no
3537 ** addresses will be qualified.
3539 {"use_from", DT_BOOL, R_NONE, OPTUSEFROM, 1},
3542 ** When \fIset\fP, Mutt-ng will generate the ``\fTFrom:\fP'' header field when
3543 ** sending messages. If \fIunset\fP, no ``\fTFrom:\fP'' header field will be
3544 ** generated unless the user explicitly sets one using the ``$my_hdr''
3548 {"use_idn", DT_BOOL, R_BOTH, OPTUSEIDN, 1},
3551 ** Availability: IDN
3554 ** When \fIset\fP, Mutt-ng will show you international domain names decoded.
3556 ** \fBNote:\fP You can use IDNs for addresses even if this is \fIunset\fP.
3557 ** This variable only affects decoding.
3559 #endif /* HAVE_LIBIDN */
3560 #ifdef HAVE_GETADDRINFO
3561 {"use_ipv6", DT_BOOL, R_NONE, OPTUSEIPV6, 1},
3564 ** When \fIset\fP, Mutt-ng will look for IPv6 addresses of hosts it tries to
3565 ** contact. If this option is \fIunset\fP, Mutt-ng will restrict itself to IPv4 addresses.
3566 ** Normally, the default should work.
3568 #endif /* HAVE_GETADDRINFO */
3569 {"user_agent", DT_BOOL, R_NONE, OPTXMAILER, 1},
3572 ** When \fIset\fP, Mutt-ng will add a ``\fTUser-Agent:\fP'' header to outgoing
3573 ** messages, indicating which version of Mutt-ng was used for composing
3576 {"visual", DT_PATH, R_NONE, UL &Visual, 0},
3579 ** Specifies the visual editor to invoke when the \fI~v\fP command is
3580 ** given in the builtin editor.
3582 {"wait_key", DT_BOOL, R_NONE, OPTWAITKEY, 1},
3585 ** Controls whether Mutt-ng will ask you to press a key after \fIshell-
3586 ** escape\fP, \fIpipe-message\fP, \fIpipe-entry\fP, \fIprint-message\fP,
3587 ** and \fIprint-entry\fP commands.
3589 ** It is also used when viewing attachments with ``$auto_view'', provided
3590 ** that the corresponding mailcap entry has a \fTneedsterminal\fP flag,
3591 ** and the external program is interactive.
3593 ** When \fIset\fP, Mutt-ng will always ask for a key. When \fIunset\fP, Mutt-ng will wait
3594 ** for a key only if the external command returned a non-zero status.
3596 {"weed", DT_BOOL, R_NONE, OPTWEED, 1},
3599 ** When \fIset\fP, Mutt-ng will weed headers when displaying, forwarding,
3600 ** printing, or replying to messages.
3602 {"wrap_search", DT_BOOL, R_NONE, OPTWRAPSEARCH, 1},
3605 ** Controls whether searches wrap around the end of the mailbox.
3607 ** When \fIset\fP, searches will wrap around the first (or last) message. When
3608 ** \fIunset\fP, searches will not wrap.
3610 {"wrapmargin", DT_NUM, R_PAGER, UL &WrapMargin, 0},
3613 ** Controls the size of the margin remaining at the right side of
3614 ** the terminal when Mutt-ng's pager does smart wrapping.
3616 {"write_inc", DT_NUM, R_NONE, UL &WriteInc, 10},
3619 ** When writing a mailbox, a message will be printed every
3620 ** \fIwrite_inc\fP messages to indicate progress. If set to 0, only a
3621 ** single message will be displayed before writing a mailbox.
3623 ** Also see the ``$$read_inc'' variable.
3625 {"write_bcc", DT_BOOL, R_NONE, OPTWRITEBCC, 1},
3628 ** Controls whether Mutt-ng writes out the Bcc header when preparing
3629 ** messages to be sent. Exim users may wish to \fIunset\fP this.
3631 {"xterm_icon", DT_STR, R_BOTH, UL &XtermIcon, UL "M%?n?AIL&ail?"},
3634 ** Controls the format of the X11 icon title, as long as $$xterm_set_titles
3635 ** is \fIset\fP. This string is identical in formatting to the one used by
3636 ** ``$$status_format''.
3638 {"xterm_set_titles", DT_BOOL, R_BOTH, OPTXTERMSETTITLES, 0},
3641 ** Controls whether Mutt-ng sets the xterm title bar and icon name
3642 ** (as long as you're in an appropriate terminal). The default must
3643 ** be \fIunset\fP to force in the validity checking.
3645 {"xterm_leave", DT_STR, R_BOTH, UL &XtermLeave, UL "" },
3648 ** If $$xterm_set_titles is \fIset\fP, this string will be used to
3649 ** set the title when leaving mutt-ng. For terminal-based programs,
3650 ** there's no easy and portable way to read the current title so mutt-ng
3651 ** cannot read it upon startup and restore it when exiting.
3654 ** Based on the xterm FAQ, the following might work:
3657 ** \fTset xterm_leave = "`test x$$$DISPLAY != x && xprop -id $$$WINDOWID | grep WM_NAME | cut -d '"' -f 2`"\fP
3659 {"xterm_title", DT_STR, R_BOTH, UL &XtermTitle, UL "Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?"},
3662 ** Controls the format of the title bar of the xterm provided that
3663 ** $$xterm_set_titles has been \fIset\fP. This string is identical in formatting
3664 ** to the one used by ``$$status_format''.
3667 {"x_comment_to", DT_SYN, R_NONE, UL "nntp_x_comment_to", 0},
3668 {"nntp_x_comment_to", DT_BOOL, R_NONE, OPTXCOMMENTTO, 0},
3671 ** Availability: NNTP
3674 ** If \fIset\fP, Mutt-ng will add a ``\fTX-Comment-To:\fP'' header field
3675 ** (that contains full name of the original article author) to articles that
3683 const struct feature_t Features[] = {
3685 #ifdef NCURSES_VERSION
3691 #ifdef USE_SLANG_CURSES
3697 #ifdef _LIBICONV_VERSION
3715 #ifdef DL_STANDALONE
3769 #ifdef USE_COMPRESSED
3781 #ifdef CRYPT_BACKEND_CLASSIC_PGP
3786 }, {"classic_smime",
3787 #ifdef CRYPT_BACKEND_CLASSIC_SMIME
3793 #ifdef CRYPT_BACKEND_GPGME
3827 const struct mapping_t SortMethods[] = {
3828 {"date", SORT_DATE},
3829 {"date-sent", SORT_DATE},
3830 {"date-received", SORT_RECEIVED},
3831 {"mailbox-order", SORT_ORDER},
3832 {"subject", SORT_SUBJECT},
3833 {"from", SORT_FROM},
3834 {"size", SORT_SIZE},
3835 {"threads", SORT_THREADS},
3837 {"score", SORT_SCORE},
3838 {"spam", SORT_SPAM},
3842 /* same as SortMethods, but with "threads" replaced by "date" */
3844 const struct mapping_t SortAuxMethods[] = {
3845 {"date", SORT_DATE},
3846 {"date-sent", SORT_DATE},
3847 {"date-received", SORT_RECEIVED},
3848 {"mailbox-order", SORT_ORDER},
3849 {"subject", SORT_SUBJECT},
3850 {"from", SORT_FROM},
3851 {"size", SORT_SIZE},
3852 {"threads", SORT_DATE}, /* note: sort_aux == threads
3856 {"score", SORT_SCORE},
3857 {"spam", SORT_SPAM},
3862 const struct mapping_t SortBrowserMethods[] = {
3863 {"alpha", SORT_SUBJECT},
3864 {"date", SORT_DATE},
3865 {"size", SORT_SIZE},
3866 {"unsorted", SORT_ORDER},
3870 const struct mapping_t SortAliasMethods[] = {
3871 {"alias", SORT_ALIAS},
3872 {"address", SORT_ADDRESS},
3873 {"unsorted", SORT_ORDER},
3877 const struct mapping_t SortKeyMethods[] = {
3878 {"address", SORT_ADDRESS},
3879 {"date", SORT_DATE},
3880 {"keyid", SORT_KEYID},
3881 {"trust", SORT_TRUST},
3886 /* functions used to parse commands in a rc file */
3888 static int parse_list (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3889 static int parse_spam_list (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3890 static int parse_unlist (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3892 static int parse_lists (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3893 static int parse_unlists (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3894 static int parse_alias (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3895 static int parse_unalias (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3896 static int parse_ifdef (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3897 static int parse_ignore (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3898 static int parse_unignore (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3899 static int parse_source (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3900 static int parse_set (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3901 static int parse_my_hdr (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3902 static int parse_unmy_hdr (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3903 static int parse_subscribe (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3904 static int parse_unsubscribe (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3906 static int parse_alternates (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3907 static int parse_unalternates (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3911 int (*func) (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3913 unsigned long data1;
3916 struct command_t Commands[] = {
3917 {"alternates", parse_alternates, 0},
3918 {"unalternates", parse_unalternates, 0},
3920 {"account-hook", mutt_parse_hook, M_ACCOUNTHOOK},
3922 {"alias", parse_alias, 0},
3923 {"auto_view", parse_list, UL &AutoViewList},
3924 {"alternative_order", parse_list, UL &AlternativeOrderList},
3925 {"bind", mutt_parse_bind, 0},
3926 {"charset-hook", mutt_parse_hook, M_CHARSETHOOK},
3928 {"color", mutt_parse_color, 0},
3929 {"uncolor", mutt_parse_uncolor, 0},
3931 {"exec", mutt_parse_exec, 0},
3932 {"fcc-hook", mutt_parse_hook, M_FCCHOOK},
3933 {"fcc-save-hook", mutt_parse_hook, M_FCCHOOK|M_SAVEHOOK},
3934 {"folder-hook", mutt_parse_hook, M_FOLDERHOOK},
3935 #ifdef USE_COMPRESSED
3936 {"open-hook", mutt_parse_hook, M_OPENHOOK},
3937 {"close-hook", mutt_parse_hook, M_CLOSEHOOK},
3938 {"append-hook", mutt_parse_hook, M_APPENDHOOK},
3940 {"hdr_order", parse_list, UL &HeaderOrderList},
3941 {"ifdef", parse_ifdef, 1},
3942 {"ifndef", parse_ifdef, 0},
3944 {"iconv-hook", mutt_parse_hook, M_ICONVHOOK},
3946 {"ignore", parse_ignore, 0},
3947 {"lists", parse_lists, 0},
3948 {"macro", mutt_parse_macro, 0},
3949 {"mailboxes", buffy_parse_mailboxes, M_MAILBOXES},
3950 {"unmailboxes", buffy_parse_mailboxes, M_UNMAILBOXES},
3951 {"message-hook", mutt_parse_hook, M_MESSAGEHOOK},
3952 {"mbox-hook", mutt_parse_hook, M_MBOXHOOK},
3953 {"mime_lookup", parse_list, UL &MimeLookupList},
3954 {"unmime_lookup", parse_unlist, UL &MimeLookupList},
3955 {"mono", mutt_parse_mono, 0},
3956 {"my_hdr", parse_my_hdr, 0},
3957 {"pgp-hook", mutt_parse_hook, M_CRYPTHOOK},
3958 {"crypt-hook", mutt_parse_hook, M_CRYPTHOOK},
3959 {"push", mutt_parse_push, 0},
3960 {"reply-hook", mutt_parse_hook, M_REPLYHOOK},
3961 {"reset", parse_set, M_SET_RESET},
3962 {"save-hook", mutt_parse_hook, M_SAVEHOOK},
3963 {"score", mutt_parse_score, 0},
3964 {"send-hook", mutt_parse_hook, M_SENDHOOK},
3965 {"send2-hook", mutt_parse_hook, M_SEND2HOOK},
3966 {"set", parse_set, 0},
3967 {"source", parse_source, 0},
3968 {"spam", parse_spam_list, M_SPAM},
3969 {"nospam", parse_spam_list, M_NOSPAM},
3970 {"subscribe", parse_subscribe, 0},
3971 {"toggle", parse_set, M_SET_INV},
3972 {"unalias", parse_unalias, 0},
3973 {"unalternative_order", parse_unlist, UL &AlternativeOrderList},
3974 {"unauto_view", parse_unlist, UL &AutoViewList},
3975 {"unhdr_order", parse_unlist, UL &HeaderOrderList},
3976 {"unhook", mutt_parse_unhook, 0},
3977 {"unignore", parse_unignore, 0},
3978 {"unlists", parse_unlists, 0},
3979 {"unmono", mutt_parse_unmono, 0},
3980 {"unmy_hdr", parse_unmy_hdr, 0},
3981 {"unscore", mutt_parse_unscore, 0},
3982 {"unset", parse_set, M_SET_UNSET},
3983 {"unsubscribe", parse_unsubscribe, 0},