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_space", DT_BOOL, R_NONE, OPTDELSP, 0},
513 ** When sending messages with \fTformat=flowed\fP by \fIsetting\fP the
514 ** $$$text_flowed variable, this variable specifies whether to also
515 ** set the \fTDelSp\fP parameter to \fTyes\fP. If this is \fIunset\fP,
516 ** no additional parameter will be send as a value of \fTno\fP already
517 ** is the default behavior.
520 ** \fBNote:\fP this variable only has an effect on \fIoutgoing\fP messages
521 ** (if $$$text_flowed is \fIset\fP) but not on incomming.
523 {"delete_untag", DT_BOOL, R_NONE, OPTDELETEUNTAG, 1},
526 ** If this option is \fIset\fP, Mutt-ng will untag messages when marking them
527 ** for deletion. This applies when you either explicitly delete a message,
528 ** or when you save it to another folder.
530 {"digest_collapse", DT_BOOL, R_NONE, OPTDIGESTCOLLAPSE, 1},
533 ** If this option is \fIset\fP, Mutt-ng's received-attachments menu will not show the subparts of
534 ** individual messages in a multipart/digest. To see these subparts, press 'v' on that menu.
536 {"display_filter", DT_PATH, R_PAGER, UL &DisplayFilter, UL ""},
539 ** When \fIset\fP, specifies a command used to filter messages. When a message
540 ** is viewed it is passed as standard input to $$display_filter, and the
541 ** filtered message is read from the standard output.
543 #if defined(DL_STANDALONE) && defined(USE_DOTLOCK)
544 {"dotlock_program", DT_PATH, R_NONE, UL &MuttDotlock, UL BINDIR "/muttng_dotlock"},
547 ** Availability: Standalone and Dotlock
550 ** Contains the path of the \fTmuttng_dotlock(1)\fP binary to be used by
554 {"dsn_notify", DT_STR, R_NONE, UL &DsnNotify, UL ""},
557 ** \fBNote:\fP you should not enable this unless you are using Sendmail
558 ** 8.8.x or greater or in connection with the SMTP support via libESMTP.
560 ** This variable sets the request for when notification is returned. The
561 ** string consists of a comma separated list (no spaces!) of one or more
562 ** of the following: \fInever\fP, to never request notification,
563 ** \fIfailure\fP, to request notification on transmission failure,
564 ** \fIdelay\fP, to be notified of message delays, \fIsuccess\fP, to be
565 ** notified of successful transmission.
567 ** Example: \fTset dsn_notify="failure,delay"\fP
569 {"dsn_return", DT_STR, R_NONE, UL &DsnReturn, UL ""},
572 ** \fBNote:\fP you should not enable this unless you are using Sendmail
573 ** 8.8.x or greater or in connection with the SMTP support via libESMTP.
575 ** This variable controls how much of your message is returned in DSN
576 ** messages. It may be set to either \fIhdrs\fP to return just the
577 ** message header, or \fIfull\fP to return the full message.
579 ** Example: \fTset dsn_return=hdrs\fP
581 {"duplicate_threads", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTDUPTHREADS, 1},
584 ** This variable controls whether Mutt-ng, when sorting by threads, threads
585 ** messages with the same \fTMessage-Id:\fP header field together.
586 ** If it is \fIset\fP, it will indicate that it thinks they are duplicates
587 ** of each other with an equals sign in the thread diagram.
589 {"edit_headers", DT_BOOL, R_NONE, OPTEDITHDRS, 0},
592 ** This option allows you to edit the header of your outgoing messages
593 ** along with the body of your message.
595 {"editor", DT_PATH, R_NONE, UL &Editor, 0},
598 ** This variable specifies which editor is used by Mutt-ng.
599 ** It defaults to the value of the \fT$$$VISUAL\fP, or \fT$$$EDITOR\fP, environment
600 ** variable, or to the string "\fTvi\fP" if neither of those are set.
602 {"encode_from", DT_BOOL, R_NONE, OPTENCODEFROM, 0},
605 ** When \fIset\fP, Mutt-ng will \fTquoted-printable\fP encode messages when
606 ** they contain the string ``\fTFrom \fP'' (note the trailing space)
607 ** in the beginning of a line. Useful to avoid the tampering certain mail
608 ** delivery and transport agents tend to do with messages.
611 ** \fBNote:\fP as mutt-ng currently violates RfC3676 defining
612 ** \fTformat=flowed\fP, it's <em/strongly/ advised to \fIset\fP
613 ** this option although discouraged by the standard. Alternatively,
614 ** you must take care of space-stuffing <tt/From / lines (with a trailing
617 {"envelope_from", DT_BOOL, R_NONE, OPTENVFROM, 0},
620 ** When \fIset\fP, Mutt-ng will try to derive the message's \fIenvelope\fP
621 ** sender from the ``\fTFrom:\fP'' header field. Note that this information is passed
622 ** to the sendmail command using the ``\fT-f\fP" command line switch, so don't set this
623 ** option if you are using that switch in $$sendmail yourself,
624 ** or if the sendmail on your machine doesn't support that command
627 {"escape", DT_STR, R_NONE, UL &EscChar, UL "~"},
630 ** Escape character to use for functions in the builtin editor.
632 {"fast_reply", DT_BOOL, R_NONE, OPTFASTREPLY, 0},
635 ** When \fIset\fP, the initial prompt for recipients and subject are skipped
636 ** when replying to messages, and the initial prompt for subject is
637 ** skipped when forwarding messages.
639 ** \fBNote:\fP this variable has no effect when the ``$$autoedit''
640 ** variable is \fIset\fP.
642 {"fcc_attach", DT_BOOL, R_NONE, OPTFCCATTACH, 1},
645 ** This variable controls whether or not attachments on outgoing messages
646 ** are saved along with the main body of your message.
648 {"fcc_clear", DT_BOOL, R_NONE, OPTFCCCLEAR, 0},
651 ** When this variable is \fIset\fP, FCCs will be stored unencrypted and
652 ** unsigned, even when the actual message is encrypted and/or
656 {"file_charset", DT_STR, R_NONE, UL &FileCharset, UL 0},
659 ** This variable is a colon-separated list of character encoding
660 ** schemes for text file attatchments.
661 ** If \fIunset\fP, $$charset value will be used instead.
662 ** For example, the following configuration would work for Japanese
665 ** \fTset file_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"\fP
667 ** Note: ``\fTiso-2022-*\fP'' must be put at the head of the value as shown above
670 {"folder", DT_PATH, R_NONE, UL &Maildir, UL "~/Mail"},
673 ** Specifies the default location of your mailboxes. A ``\fT+\fP'' or ``\fT=\fP'' at the
674 ** beginning of a pathname will be expanded to the value of this
675 ** variable. Note that if you change this variable from the default
676 ** value you need to make sure that the assignment occurs \fIbefore\fP
677 ** you use ``+'' or ``='' for any other variables since expansion takes place
678 ** during the ``set'' command.
680 {"folder_format", DT_STR, R_INDEX, UL &FolderFormat, UL "%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f"},
683 ** This variable allows you to customize the file browser display to your
684 ** personal taste. This string is similar to ``$$index_format'', but has
685 ** its own set of \fTprintf(3)\fP-like sequences:
688 ** .dt %C .dd current file number
689 ** .dt %d .dd date/time folder was last modified
690 ** .dt %f .dd filename
691 ** .dt %F .dd file permissions
692 ** .dt %g .dd group name (or numeric gid, if missing)
693 ** .dt %l .dd number of hard links
694 ** .dt %N .dd N if folder has new mail, blank otherwise
695 ** .dt %s .dd size in bytes
696 ** .dt %t .dd * if the file is tagged, blank otherwise
697 ** .dt %u .dd owner name (or numeric uid, if missing)
698 ** .dt %>X .dd right justify the rest of the string and pad with character "X"
699 ** .dt %|X .dd pad to the end of the line with character "X"
702 {"followup_to", DT_BOOL, R_NONE, OPTFOLLOWUPTO, 1},
705 ** Controls whether or not the \fTMail-Followup-To:\fP header field is
706 ** generated when sending mail. When \fIset\fP, Mutt-ng will generate this
707 ** field when you are replying to a known mailing list, specified with
708 ** the ``subscribe'' or ``$lists'' commands or detected by common mailing list
711 ** This field has two purposes. First, preventing you from
712 ** receiving duplicate copies of replies to messages which you send
713 ** to mailing lists. Second, ensuring that you do get a reply
714 ** separately for any messages sent to known lists to which you are
715 ** not subscribed. The header will contain only the list's address
716 ** for subscribed lists, and both the list address and your own
717 ** email address for unsubscribed lists. Without this header, a
718 ** group reply to your message sent to a subscribed list will be
719 ** sent to both the list and your address, resulting in two copies
720 ** of the same email for you.
723 {"followup_to_poster", DT_SYN, R_NONE, UL "nntp_followup_to_poster", 0},
724 {"nntp_followup_to_poster", DT_QUAD, R_NONE, OPT_FOLLOWUPTOPOSTER, M_ASKYES},
727 ** Availability: NNTP
730 ** If this variable is \fIset\fP and the keyword "\fTposter\fP" is present in
731 ** the \fTFollowup-To:\fP header field, a follow-up to the newsgroup is not
732 ** permitted. The message will be mailed to the submitter of the
736 {"force_name", DT_BOOL, R_NONE, OPTFORCENAME, 0},
739 ** This variable is similar to ``$$save_name'', except that Mutt-ng will
740 ** store a copy of your outgoing message by the username of the address
741 ** you are sending to even if that mailbox does not exist.
743 ** Also see the ``$$record'' variable.
745 {"force_buffy_check", DT_BOOL, R_NONE, OPTFORCEBUFFYCHECK, 0},
748 ** When \fIset\fP, it causes Mutt-ng to check for new mail when the
749 ** \fIbuffy-list\fP command is invoked. When \fIunset\fP, \fIbuffy_list\fP
750 ** will just list all mailboxes which are already known to have new mail.
752 ** Also see the following variables: ``$$timeout'', ``$$mail_check'' and
753 ** ``$$imap_mail_check''.
755 {"forward_decode", DT_BOOL, R_NONE, OPTFORWDECODE, 1},
758 ** Controls the decoding of complex MIME messages into \fTtext/plain\fP when
759 ** forwarding a message. The message header is also RFC2047 decoded.
760 ** This variable is only used, if ``$$mime_forward'' is \fIunset\fP,
761 ** otherwise ``$$mime_forward_decode'' is used instead.
763 {"forward_edit", DT_QUAD, R_NONE, OPT_FORWEDIT, M_YES},
766 ** This quadoption controls whether or not the user is automatically
767 ** placed in the editor when forwarding messages. For those who always want
768 ** to forward with no modification, use a setting of \fIno\fP.
770 {"forward_format", DT_STR, R_NONE, UL &ForwFmt, UL "[%a: %s]"},
773 ** This variable controls the default subject when forwarding a message.
774 ** It uses the same format sequences as the ``$$index_format'' variable.
776 {"forward_quote", DT_BOOL, R_NONE, OPTFORWQUOTE, 0},
779 ** When \fIset\fP forwarded messages included in the main body of the
780 ** message (when ``$$mime_forward'' is \fIunset\fP) will be quoted using
781 ** ``$$indent_string''.
783 {"from", DT_ADDR, R_NONE, UL &From, UL 0},
786 ** This variable contains a default from address. It
787 ** can be overridden using my_hdr (including from send-hooks) and
788 ** ``$$reverse_name''. This variable is ignored if ``$$use_from''
792 ** \fTsend-hook Mutt-ng-devel@lists.berlios.de 'my_hdr From: Foo Bar <foo@bar.fb>'\fP
793 ** when replying to the mutt-ng developer's mailing list and Mutt-ng takes this email address.
795 ** Defaults to the contents of the environment variable \fT$$$EMAIL\fP.
797 {"gecos_mask", DT_RX, R_NONE, UL &GecosMask, UL "^[^,]*"},
800 ** A regular expression used by Mutt-ng to parse the GECOS field of a password
801 ** entry when expanding the alias. By default the regular expression is set
802 ** to ``\fT^[^,]*\fP'' which will return the string up to the first ``\fT,\fP'' encountered.
803 ** If the GECOS field contains a string like "lastname, firstname" then you
804 ** should do: \fTset gecos_mask=".*"\fP.
806 ** This can be useful if you see the following behavior: you address a e-mail
807 ** to user ID stevef whose full name is Steve Franklin. If Mutt-ng expands
808 ** stevef to ``Franklin'' stevef@foo.bar then you should set the gecos_mask to
809 ** a regular expression that will match the whole name so Mutt-ng will expand
810 ** ``Franklin'' to ``Franklin, Steve''.
813 {"group_index_format", DT_SYN, R_NONE, UL "nntp_group_index_format", 0},
814 {"nntp_group_index_format", DT_STR, R_BOTH, UL &GroupFormat, UL "%4C %M%N %5s %-45.45f %d"},
817 ** Availability: NNTP
820 ** This variable allows you to customize the newsgroup browser display to
821 ** your personal taste. This string is similar to ``$index_format'', but
822 ** has its own set of \fTprintf(3)\fP-like sequences:
825 ** %C current newsgroup number
826 ** %d description of newsgroup (retrieved from server)
828 ** %M ``-'' if newsgroup not allowed for direct post (moderated for example)
829 ** %N ``N'' if newsgroup is new, ``u'' if unsubscribed, blank otherwise
830 ** %n number of new articles in newsgroup
831 ** %s number of unread articles in newsgroup
832 ** %>X right justify the rest of the string and pad with character "X"
833 ** %|X pad to the end of the line with character "X"
837 {"hdrs", DT_BOOL, R_NONE, OPTHDRS, 1},
840 ** When \fIunset\fP, the header fields normally added by the ``$my_hdr''
841 ** command are not created. This variable \fImust\fP be \fIunset\fP before
842 ** composing a new message or replying in order to take effect. If \fIset\fP,
843 ** the user defined header fields are added to every new message.
845 {"header", DT_BOOL, R_NONE, OPTHEADER, 0},
848 ** When \fIset\fP, this variable causes Mutt-ng to include the header
849 ** of the message you are replying to into the edit buffer.
850 ** The ``$$weed'' setting applies.
852 {"help", DT_BOOL, R_BOTH, OPTHELP, 1},
855 ** When \fIset\fP, help lines describing the bindings for the major functions
856 ** provided by each menu are displayed on the first line of the screen.
858 ** \fBNote:\fP The binding will not be displayed correctly if the
859 ** function is bound to a sequence rather than a single keystroke. Also,
860 ** the help line may not be updated if a binding is changed while Mutt-ng is
861 ** running. Since this variable is primarily aimed at new users, neither
862 ** of these should present a major problem.
864 {"hidden_host", DT_BOOL, R_NONE, OPTHIDDENHOST, 0},
867 ** When \fIset\fP, Mutt-ng will skip the host name part of ``$$hostname'' variable
868 ** when adding the domain part to addresses. This variable does not
869 ** affect the generation of \fTMessage-ID:\fP header fields, and it will not lead to the
870 ** cut-off of first-level domains.
872 {"hide_limited", DT_BOOL, R_TREE|R_INDEX, OPTHIDELIMITED, 0},
875 ** When \fIset\fP, Mutt-ng will not show the presence of messages that are hidden
876 ** by limiting, in the thread tree.
878 {"hide_missing", DT_BOOL, R_TREE|R_INDEX, OPTHIDEMISSING, 1},
881 ** When \fIset\fP, Mutt-ng will not show the presence of missing messages in the
884 {"hide_thread_subject", DT_BOOL, R_TREE|R_INDEX, OPTHIDETHREADSUBJECT, 1},
887 ** When \fIset\fP, Mutt-ng will not show the subject of messages in the thread
888 ** tree that have the same subject as their parent or closest previously
889 ** displayed sibling.
891 {"hide_top_limited", DT_BOOL, R_TREE|R_INDEX, OPTHIDETOPLIMITED, 0},
894 ** When \fIset\fP, Mutt-ng will not show the presence of messages that are hidden
895 ** by limiting, at the top of threads in the thread tree. Note that when
896 ** $$hide_missing is set, this option will have no effect.
898 {"hide_top_missing", DT_BOOL, R_TREE|R_INDEX, OPTHIDETOPMISSING, 1},
901 ** When \fIset\fP, Mutt-ng will not show the presence of missing messages at the
902 ** top of threads in the thread tree. Note that when $$hide_limited is
903 ** \fIset\fP, this option will have no effect.
905 {"history", DT_NUM, R_NONE, UL &HistSize, 10},
908 ** This variable controls the size (in number of strings remembered) of
909 ** the string history buffer. The buffer is cleared each time the
910 ** variable is changed.
912 {"honor_followup_to", DT_QUAD, R_NONE, OPT_MFUPTO, M_YES},
915 ** This variable controls whether or not a \fTMail-Followup-To:\fP header field is
916 ** honored when group-replying to a message.
918 {"hostname", DT_STR, R_NONE, UL &Fqdn, 0},
921 ** Specifies the hostname to use after the ``\fT@\fP'' in local e-mail
922 ** addresses and during generation of \fTMessage-Id:\fP headers.
924 ** Please be sure to really know what you are doing when changing this variable
925 ** to configure a custom domain part of Message-IDs.
927 {"ignore_list_reply_to", DT_BOOL, R_NONE, OPTIGNORELISTREPLYTO, 0},
930 ** Affects the behaviour of the \fIreply\fP function when replying to
931 ** messages from mailing lists. When \fIset\fP, if the ``\fTReply-To:\fP'' header field is
932 ** set to the same value as the ``\fTTo:\fP'' header field, Mutt-ng assumes that the
933 ** ``\fTReply-To:\fP'' header field was set by the mailing list to automate responses
934 ** to the list, and will ignore this field. To direct a response to the
935 ** mailing list when this option is set, use the \fIlist-reply\fP
936 ** function; \fIgroup-reply\fP will reply to both the sender and the
940 {"imap_authenticators", DT_STR, R_NONE, UL &ImapAuthenticators, UL 0},
943 ** Availability: IMAP
946 ** This is a colon-delimited list of authentication methods Mutt-ng may
947 ** attempt to use to log in to an IMAP server, in the order Mutt-ng should
948 ** try them. Authentication methods are either ``\fTlogin\fP'' or the right
949 ** side of an IMAP ``\fTAUTH=\fP'' capability string, e.g. ``\fTdigest-md5\fP'',
950 ** ``\fTgssapi\fP'' or ``\fTcram-md5\fP''. This parameter is case-insensitive.
953 ** parameter is \fIunset\fP (the default) Mutt-ng will try all available methods,
954 ** in order from most-secure to least-secure.
956 ** Example: \fTset imap_authenticators="gssapi:cram-md5:login"\fP
958 ** \fBNote:\fP Mutt-ng will only fall back to other authentication methods if
959 ** the previous methods are unavailable. If a method is available but
960 ** authentication fails, Mutt-ng will not connect to the IMAP server.
962 { "imap_check_subscribed", DT_BOOL, R_NONE, OPTIMAPCHECKSUBSCRIBED, 0 },
965 ** When \fIset\fP, mutt will fetch the set of subscribed folders from
966 ** your server on connection, and add them to the set of mailboxes
967 ** it polls for new mail. See also the ``$mailboxes'' command.
970 {"imap_delim_chars", DT_STR, R_NONE, UL &ImapDelimChars, UL "/."},
973 ** Availability: IMAP
976 ** This contains the list of characters which you would like to treat
977 ** as folder separators for displaying IMAP paths. In particular it
978 ** helps in using the '\fT=\fP' shortcut for your $$folder variable.
980 {"imap_headers", DT_STR, R_INDEX, UL &ImapHeaders, UL 0},
983 ** Availability: IMAP
986 ** Mutt-ng requests these header fields in addition to the default headers
987 ** (``DATE FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE
988 ** CONTENT-DESCRIPTION IN-REPLY-TO REPLY-TO LINES X-LABEL'') from IMAP
989 ** servers before displaying the ``index'' menu. You may want to add more
990 ** headers for spam detection.
992 ** \fBNote:\fP This is a space separated list.
994 {"imap_home_namespace", DT_STR, R_NONE, UL &ImapHomeNamespace, UL 0},
997 ** Availability: IMAP
1000 ** You normally want to see your personal folders alongside
1001 ** your \fTINBOX\fP in the IMAP browser. If you see something else, you may set
1002 ** this variable to the IMAP path to your folders.
1004 {"imap_keepalive", DT_NUM, R_NONE, UL &ImapKeepalive, 900},
1007 ** Availability: IMAP
1010 ** This variable specifies the maximum amount of time in seconds that Mutt-ng
1011 ** will wait before polling open IMAP connections, to prevent the server
1012 ** from closing them before Mutt-ng has finished with them.
1015 ** well within the RFC-specified minimum amount of time (30 minutes) before
1016 ** a server is allowed to do this, but in practice the RFC does get
1017 ** violated every now and then.
1019 ** Reduce this number if you find yourself
1020 ** getting disconnected from your IMAP server due to inactivity.
1022 {"imap_login", DT_STR, R_NONE, UL &ImapLogin, 0 },
1025 ** Availability: IMAP
1028 ** Your login name on the IMAP server.
1030 ** This variable defaults to the value of ``$$imap_user.''
1032 {"imap_list_subscribed", DT_BOOL, R_NONE, OPTIMAPLSUB, 0},
1035 ** Availability: IMAP
1038 ** This variable configures whether IMAP folder browsing will look for
1039 ** only subscribed folders or all folders. This can be toggled in the
1040 ** IMAP browser with the \fItoggle-subscribed\fP function.
1042 {"imap_mail_check", DT_NUM, R_NONE, UL &ImapBuffyTimeout, 300},
1045 ** This variable configures how often (in seconds) Mutt-ng should look for
1046 ** new mail in IMAP folders. This is split from the ``$mail_check'' variable
1047 ** to generate less traffic and get more accurate information for local folders.
1049 {"imap_pass", DT_STR, R_NONE, UL &ImapPass, UL 0},
1052 ** Availability: IMAP
1055 ** Specifies the password for your IMAP account. If \fIunset\fP, Mutt-ng will
1056 ** prompt you for your password when you invoke the fetch-mail function.
1058 ** \fBWarning\fP: you should only use this option when you are on a
1059 ** fairly secure machine, because the superuser can read your configuration even
1060 ** if you are the only one who can read the file.
1062 {"imap_passive", DT_BOOL, R_NONE, OPTIMAPPASSIVE, 1},
1065 ** Availability: IMAP
1068 ** When \fIset\fP, Mutt-ng will not open new IMAP connections to check for new
1069 ** mail. Mutt-ng will only check for new mail over existing IMAP
1070 ** connections. This is useful if you don't want to be prompted to
1071 ** user/password pairs on Mutt-ng invocation, or if opening the connection
1074 {"imap_peek", DT_BOOL, R_NONE, OPTIMAPPEEK, 1},
1077 ** Availability: IMAP
1080 ** If \fIset\fP, Mutt-ng will avoid implicitly marking your mail as read whenever
1081 ** you fetch a message from the server. This is generally a good thing,
1082 ** but can make closing an IMAP folder somewhat slower. This option
1083 ** exists to appease speed freaks.
1085 {"imap_reconnect", DT_QUAD, R_NONE, OPT_IMAPRECONNECT, M_ASKYES},
1088 ** Availability: IMAP
1091 ** Controls whether or not Mutt-ng will try to reconnect to IMAP server when
1092 ** the connection is lost.
1094 {"imap_servernoise", DT_BOOL, R_NONE, OPTIMAPSERVERNOISE, 1},
1097 ** Availability: IMAP
1100 ** When \fIset\fP, Mutt-ng will display warning messages from the IMAP
1101 ** server as error messages. Since these messages are often
1102 ** harmless, or generated due to configuration problems on the
1103 ** server which are out of the users' hands, you may wish to suppress
1104 ** them at some point.
1106 {"imap_user", DT_STR, R_NONE, UL &ImapUser, UL 0},
1109 ** Availability: IMAP
1112 ** The name of the user whose mail you intend to access on the IMAP
1115 ** This variable defaults to your user name on the local machine.
1118 {"implicit_autoview", DT_BOOL, R_NONE, OPTIMPLICITAUTOVIEW, 0},
1121 ** If \fIset\fP, Mutt-ng will look for a mailcap entry with the
1122 ** ``\fTcopiousoutput\fP'' flag set for \fIevery\fP MIME attachment it doesn't have
1123 ** an internal viewer defined for. If such an entry is found, Mutt-ng will
1124 ** use the viewer defined in that entry to convert the body part to text
1127 {"include", DT_QUAD, R_NONE, OPT_INCLUDE, M_ASKYES},
1130 ** Controls whether or not a copy of the message(s) you are replying to
1131 ** is included in your reply.
1133 {"include_onlyfirst", DT_BOOL, R_NONE, OPTINCLUDEONLYFIRST, 0},
1136 ** Controls whether or not Mutt-ng includes only the first attachment
1137 ** of the message you are replying.
1139 {"indent_string", DT_STR, R_NONE, UL &Prefix, UL "> "},
1142 ** Specifies the string to prepend to each line of text quoted in a
1143 ** message to which you are replying. You are strongly encouraged not to
1144 ** change this value, as it tends to agitate the more fanatical netizens.
1146 {"index_format", DT_STR, R_BOTH, UL &HdrFmt, UL "%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s"},
1149 ** This variable allows you to customize the message index display to
1150 ** your personal taste.
1152 ** ``Format strings'' are similar to the strings used in the ``C''
1153 ** function \fTprintf(3)\fP to format output (see the man page for more detail).
1154 ** The following sequences are defined in Mutt-ng:
1157 ** .dt %a .dd address of the author
1158 ** .dt %A .dd reply-to address (if present; otherwise: address of author)
1159 ** .dt %b .dd filename of the original message folder (think mailBox)
1160 ** .dt %B .dd the list to which the letter was sent, or else the folder name (%b).
1161 ** .dt %c .dd number of characters (bytes) in the message
1162 ** .dt %C .dd current message number
1163 ** .dt %d .dd date and time of the message in the format specified by
1164 ** ``date_format'' converted to sender's time zone
1165 ** .dt %D .dd date and time of the message in the format specified by
1166 ** ``date_format'' converted to the local time zone
1167 ** .dt %e .dd current message number in thread
1168 ** .dt %E .dd number of messages in current thread
1169 ** .dt %f .dd entire From: line (address + real name)
1170 ** .dt %F .dd author name, or recipient name if the message is from you
1171 ** .dt %H .dd spam attribute(s) of this message
1172 ** .dt %g .dd newsgroup name (if compiled with nntp support)
1173 ** .dt %i .dd message-id of the current message
1174 ** .dt %l .dd number of lines in the message (does not work with maildir,
1175 ** mh, and possibly IMAP folders)
1176 ** .dt %L .dd If an address in the To or CC header field matches an address
1177 ** defined by the users ``subscribe'' command, this displays
1178 ** "To <list-name>", otherwise the same as %F.
1179 ** .dt %m .dd total number of message in the mailbox
1180 ** .dt %M .dd number of hidden messages if the thread is collapsed.
1181 ** .dt %N .dd message score
1182 ** .dt %n .dd author's real name (or address if missing)
1183 ** .dt %O .dd (_O_riginal save folder) Where Mutt-ng would formerly have
1184 ** stashed the message: list name or recipient name if no list
1185 ** .dt %s .dd subject of the message
1186 ** .dt %S .dd status of the message (N/D/d/!/r/\(as)
1187 ** .dt %t .dd `to:' field (recipients)
1188 ** .dt %T .dd the appropriate character from the $$to_chars string
1189 ** .dt %u .dd user (login) name of the author
1190 ** .dt %v .dd first name of the author, or the recipient if the message is from you
1191 ** .dt %W .dd name of organization of author (`organization:' field)
1192 ** .dt %y .dd `x-label:' field, if present
1193 ** .dt %Y .dd `x-label' field, if present, and (1) not at part of a thread tree,
1194 ** (2) at the top of a thread, or (3) `x-label' is different from
1195 ** preceding message's `x-label'.
1196 ** .dt %Z .dd message status flags
1197 ** .dt %{fmt} .dd the date and time of the message is converted to sender's
1198 ** time zone, and ``fmt'' is expanded by the library function
1199 ** ``strftime''; a leading bang disables locales
1200 ** .dt %[fmt] .dd the date and time of the message is converted to the local
1201 ** time zone, and ``fmt'' is expanded by the library function
1202 ** ``strftime''; a leading bang disables locales
1203 ** .dt %(fmt) .dd the local date and time when the message was received.
1204 ** ``fmt'' is expanded by the library function ``strftime'';
1205 ** a leading bang disables locales
1206 ** .dt %<fmt> .dd the current local time. ``fmt'' is expanded by the library
1207 ** function ``strftime''; a leading bang disables locales.
1208 ** .dt %>X .dd right justify the rest of the string and pad with character "X"
1209 ** .dt %|X .dd pad to the end of the line with character "X"
1212 ** See also: ``$$to_chars''.
1215 {"inews", DT_SYN, R_NONE, UL "nntp_inews", 0},
1216 {"nntp_inews", DT_PATH, R_NONE, UL &Inews, UL ""},
1219 ** Availability: NNTP
1222 ** If \fIset\fP, specifies the program and arguments used to deliver news posted
1223 ** by Mutt-ng. Otherwise, Mutt-ng posts article using current connection.
1224 ** The following \fTprintf(3)\fP-style sequence is understood:
1227 ** %s newsserver name
1230 ** Example: \fTset inews="/usr/local/bin/inews -hS"\fP
1233 {"ispell", DT_PATH, R_NONE, UL &Ispell, UL ISPELL},
1236 ** How to invoke ispell (GNU's spell-checking software).
1238 {"keep_flagged", DT_BOOL, R_NONE, OPTKEEPFLAGGED, 0},
1241 ** If \fIset\fP, read messages marked as flagged will not be moved
1242 ** from your spool mailbox to your ``$$mbox'' mailbox, or as a result of
1243 ** a ``$mbox-hook'' command.
1245 {"locale", DT_STR, R_BOTH, UL &Locale, UL "C"},
1248 ** The locale used by \fTstrftime(3)\fP to format dates. Legal values are
1249 ** the strings your system accepts for the locale variable \fTLC_TIME\fP.
1251 {"list_reply", DT_QUAD, R_NONE, OPT_LISTREPLY, M_NO},
1254 ** When \fIset\fP, address replies to the mailing list the original message came
1255 ** from (instead to the author only). Setting this option to ``\fIask-yes\fP'' or
1256 ** ``\fIask-no\fP'' will ask if you really intended to reply to the author only.
1258 {"max_display_recips", DT_NUM, R_PAGER, UL &MaxDispRecips, 0},
1261 ** When set non-zero, this specifies the maximum number of recipient header
1262 ** lines (\fTTo:\fP, \fTCc:\fP and \fTBcc:\fP) to display in the pager if header
1263 ** weeding is turned on. In case the number of lines exeeds its value, the
1264 ** last line will have 3 dots appended.
1266 {"max_line_length", DT_NUM, R_PAGER, UL &MaxLineLength, 0},
1269 ** When \fIset\fP, the maximum line length for displaying ``format = flowed'' messages is limited
1270 ** to this length. A value of 0 (which is also the default) means that the
1271 ** maximum line length is determined by the terminal width and $$wrapmargin.
1273 {"mail_check", DT_NUM, R_NONE, UL &BuffyTimeout, 5},
1276 ** This variable configures how often (in seconds) Mutt-ng should look for
1279 ** \fBNote:\fP This does not apply to IMAP mailboxes, see $$imap_mail_check.
1281 {"mailcap_path", DT_STR, R_NONE, UL &MailcapPath, 0},
1284 ** This variable specifies which files to consult when attempting to
1285 ** display MIME bodies not directly supported by Mutt-ng.
1287 {"mailcap_sanitize", DT_BOOL, R_NONE, OPTMAILCAPSANITIZE, 1},
1290 ** If \fIset\fP, Mutt-ng will restrict possible characters in mailcap \fT%\fP expandos
1291 ** to a well-defined set of safe characters. This is the safe setting,
1292 ** but we are not sure it doesn't break some more advanced MIME stuff.
1294 ** \fBDON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE
1299 {"header_cache", DT_PATH, R_NONE, UL &HeaderCache, 0},
1302 ** Availability: Header Cache
1305 ** The $$header_cache variable points to the header cache database.
1307 ** If $$header_cache points to a directory it will contain a header cache
1308 ** database per folder. If $$header_cache points to a file that file will
1309 ** be a single global header cache. By default it is \fIunset\fP so no
1310 ** header caching will be used.
1312 {"maildir_header_cache_verify", DT_BOOL, R_NONE, OPTHCACHEVERIFY, 1},
1315 ** Availability: Header Cache
1318 ** Check for Maildir unaware programs other than Mutt-ng having modified maildir
1319 ** files when the header cache is in use. This incurs one \fTstat(2)\fP per
1320 ** message every time the folder is opened.
1322 #if HAVE_GDBM || HAVE_DB4
1323 {"header_cache_pagesize", DT_STR, R_NONE, UL &HeaderCachePageSize, UL "16384"},
1326 ** Availability: Header Cache
1329 ** Change the maildir header cache database page size.
1332 ** or too small of a page size for the common header can waste
1333 ** space, memory effectiveness, or CPU time. The default should be more or
1334 ** less the best you can get. For details google for mutt header
1335 ** cache (first hit).
1337 #endif /* HAVE_GDBM || HAVE_DB 4 */
1339 { "header_cache_compress", DT_BOOL, R_NONE, OPTHCACHECOMPRESS, 0 },
1342 ** If enabled the header cache will be compressed. So only one fifth of the usual
1343 ** diskspace is used, but the uncompression can result in a slower open of the
1346 #endif /* HAVE_QDBM */
1347 #endif /* USE_HCACHE */
1348 {"maildir_trash", DT_BOOL, R_NONE, OPTMAILDIRTRASH, 0},
1351 ** If \fIset\fP, messages marked as deleted will be saved with the maildir
1352 ** (T)rashed flag instead of physically deleted.
1354 ** \fBNOTE:\fP this only applies
1355 ** to maildir-style mailboxes. Setting it will have no effect on other
1358 ** It is similiar to the trash option.
1360 {"mark_old", DT_BOOL, R_BOTH, OPTMARKOLD, 1},
1363 ** Controls whether or not Mutt-ng marks \fInew\fP \fBunread\fP
1364 ** messages as \fIold\fP if you exit a mailbox without reading them.
1366 ** With this option \fIset\fP, the next time you start Mutt-ng, the messages
1367 ** will show up with an "O" next to them in the ``index'' menu,
1368 ** indicating that they are old.
1370 {"markers", DT_BOOL, R_PAGER, OPTMARKERS, 1},
1373 ** Controls the display of wrapped lines in the internal pager. If set, a
1374 ** ``\fT+\fP'' marker is displayed at the beginning of wrapped lines. Also see
1375 ** the ``$$smart_wrap'' variable.
1377 {"mask", DT_RX, R_NONE, UL &Mask, UL "!^\\.[^.]"},
1380 ** A regular expression used in the file browser, optionally preceded by
1381 ** the \fInot\fP operator ``\fT!\fP''. Only files whose names match this mask
1382 ** will be shown. The match is always case-sensitive.
1384 {"mbox", DT_PATH, R_BOTH, UL &Inbox, UL "~/mbox"},
1387 ** This specifies the folder into which read mail in your ``$$spoolfile''
1388 ** folder will be appended.
1390 {"operating_system", DT_STR, R_NONE, UL &OperatingSystem, 0},
1393 ** This specifies the operating system name for the \fTUser-Agent:\fP header field. If
1394 ** this is \fIunset\fP, it will be set to the operating system name that \fTuname(2)\fP
1395 ** returns. If \fTuname(2)\fP fails, ``UNIX'' will be used.
1397 ** It may, for example, look as: ``\fTmutt-ng 1.5.9i (Linux)\fP''.
1399 {"sidebar_boundary", DT_STR, R_BOTH, UL &SidebarBoundary, UL "." },
1402 ** When the sidebar is displayed and $$sidebar_shorten_hierarchy is \fIset\fP, this
1403 ** variable specifies the characters at which to split a folder name into
1404 ** ``hierarchy items.''
1406 {"sidebar_delim", DT_STR, R_BOTH, UL &SidebarDelim, UL "|"},
1409 ** This specifies the delimiter between the sidebar (if visible) and
1412 {"sidebar_visible", DT_BOOL, R_BOTH, OPTMBOXPANE, 0},
1415 ** This specifies whether or not to show the sidebar (a list of folders specified
1416 ** with the ``mailboxes'' command).
1418 {"sidebar_width", DT_NUM, R_BOTH, UL &SidebarWidth, 0},
1421 ** The width of the sidebar.
1423 {"sidebar_newmail_only", DT_BOOL, R_BOTH, OPTSIDEBARNEWMAILONLY, 0},
1426 ** If \fIset\fP, only folders with new mail will be shown in the sidebar.
1428 {"sidebar_number_format", DT_STR, R_BOTH, UL &SidebarNumberFormat, UL "%m%?n?(%n)?%?f?[%f]?"},
1431 ** This variable controls how message counts are printed when the sidebar
1432 ** is enabled. If this variable is \fIempty\fP (\fIand only if\fP), no numbers
1433 ** will be printed \fIand\fP mutt-ng won't frequently count mail (which
1434 ** may be a great speedup esp. with mbox-style mailboxes.)
1436 ** The following \fTprintf(3)\fP-like sequences are supported all of which
1437 ** may be printed non-zero:
1440 ** .dt %d .dd Number of deleted messages. 1)
1441 ** .dt %F .dd Number of flagged messages.
1442 ** .dt %m .dd Total number of messages.
1443 ** .dt %M .dd Total number of messages shown, i.e. not hidden by a limit. 1)
1444 ** .dt %n .dd Number of new messages.
1445 ** .dt %t .dd Number of tagged messages. 1)
1448 ** 1) These expandos only have a non-zero value for the current mailbox and
1449 ** will always be zero otherwise.
1451 {"sidebar_shorten_hierarchy", DT_BOOL, R_NONE, OPTSHORTENHIERARCHY, 0},
1454 ** When \fIset\fP, the ``hierarchy'' of the sidebar entries will be shortened
1455 ** only if they cannot be printed in full length (because ``$$sidebar_width''
1456 ** is set to a too low value). For example, if the newsgroup name
1457 ** ``de.alt.sysadmin.recovery'' doesn't fit on the screen, it'll get shortened
1458 ** ``d.a.s.recovery'' while ``de.alt.d0'' still would and thus will not get
1461 ** At which characters this compression is done is controled via the
1462 ** $$sidebar_boundary variable.
1464 {"mbox_type", DT_MAGIC, R_NONE, UL &DefaultMagic, M_MBOX},
1467 ** The default mailbox type used when creating new folders. May be any of
1468 ** \fTmbox\fP, \fTMMDF\fP, \fTMH\fP and \fTMaildir\fP.
1470 {"metoo", DT_BOOL, R_NONE, OPTMETOO, 0},
1473 ** If \fIunset\fP, Mutt-ng will remove your address (see the ``alternates''
1474 ** command) from the list of recipients when replying to a message.
1476 {"menu_context", DT_NUM, R_NONE, UL &MenuContext, 0},
1479 ** This variable controls the number of lines of context that are given
1480 ** when scrolling through menus. (Similar to ``$$pager_context''.)
1482 {"menu_move_off", DT_BOOL, R_NONE, OPTMENUMOVEOFF, 1},
1485 ** When \fIunset\fP, the bottom entry of menus will never scroll up past
1486 ** the bottom of the screen, unless there are less entries than lines.
1487 ** When \fIset\fP, the bottom entry may move off the bottom.
1489 {"menu_scroll", DT_BOOL, R_NONE, OPTMENUSCROLL, 0},
1492 ** When \fIset\fP, menus will be scrolled up or down one line when you
1493 ** attempt to move across a screen boundary. If \fIunset\fP, the screen
1494 ** is cleared and the next or previous page of the menu is displayed
1495 ** (useful for slow links to avoid many redraws).
1497 {"meta_key", DT_BOOL, R_NONE, OPTMETAKEY, 0},
1500 ** If \fIset\fP, forces Mutt-ng to interpret keystrokes with the high bit (bit 8)
1501 ** set as if the user had pressed the \fTESC\fP key and whatever key remains
1502 ** after having the high bit removed. For example, if the key pressed
1503 ** has an ASCII value of \fT0xf4\fP, then this is treated as if the user had
1504 ** pressed \fTESC\fP then ``\fTx\fP''. This is because the result of removing the
1505 ** high bit from ``\fT0xf4\fP'' is ``\fT0x74\fP'', which is the ASCII character
1508 {"mh_purge", DT_BOOL, R_NONE, OPTMHPURGE, 0},
1511 ** When \fIunset\fP, Mutt-ng will mimic mh's behaviour and rename deleted messages
1512 ** to \fI,<old file name>\fP in mh folders instead of really deleting
1513 ** them. If the variable is set, the message files will simply be
1516 {"mh_seq_flagged", DT_STR, R_NONE, UL &MhFlagged, UL "flagged"},
1519 ** The name of the MH sequence used for flagged messages.
1521 {"mh_seq_replied", DT_STR, R_NONE, UL &MhReplied, UL "replied"},
1524 ** The name of the MH sequence used to tag replied messages.
1526 {"mh_seq_unseen", DT_STR, R_NONE, UL &MhUnseen, UL "unseen"},
1529 ** The name of the MH sequence used for unseen messages.
1531 {"mime_forward", DT_QUAD, R_NONE, OPT_MIMEFWD, M_NO},
1534 ** When \fIset\fP, the message you are forwarding will be attached as a
1535 ** separate MIME part instead of included in the main body of the
1538 ** This is useful for forwarding MIME messages so the receiver
1539 ** can properly view the message as it was delivered to you. If you like
1540 ** to switch between MIME and not MIME from mail to mail, set this
1541 ** variable to ask-no or ask-yes.
1543 ** Also see ``$$forward_decode'' and ``$$mime_forward_decode''.
1545 {"mime_forward_decode", DT_BOOL, R_NONE, OPTMIMEFORWDECODE, 0},
1548 ** Controls the decoding of complex MIME messages into \fTtext/plain\fP when
1549 ** forwarding a message while ``$$mime_forward'' is \fIset\fP. Otherwise
1550 ** ``$$forward_decode'' is used instead.
1552 {"mime_forward_rest", DT_QUAD, R_NONE, OPT_MIMEFWDREST, M_YES},
1555 ** When forwarding multiple attachments of a MIME message from the recvattach
1556 ** menu, attachments which cannot be decoded in a reasonable manner will
1557 ** be attached to the newly composed message if this option is set.
1561 {"mime_subject", DT_SYN, R_NONE, UL "nntp_mime_subject", 0},
1562 {"nntp_mime_subject", DT_BOOL, R_NONE, OPTMIMESUBJECT, 1},
1565 ** Availability: NNTP
1568 ** If \fIunset\fP, an 8-bit ``\fTSubject:\fP'' header field in a news article
1569 ** will not be encoded according to RFC2047.
1571 ** \fBNote:\fP Only change this setting if you know what you are doing.
1576 {"mix_entry_format", DT_STR, R_NONE, UL &MixEntryFormat, UL "%4n %c %-16s %a"},
1579 ** Availability: Mixmaster
1582 ** This variable describes the format of a remailer line on the mixmaster
1583 ** chain selection screen. The following \fTprintf(3)\fP-like sequences are
1587 ** .dt %n .dd The running number on the menu.
1588 ** .dt %c .dd Remailer capabilities.
1589 ** .dt %s .dd The remailer's short name.
1590 ** .dt %a .dd The remailer's e-mail address.
1593 {"mixmaster", DT_PATH, R_NONE, UL &Mixmaster, UL MIXMASTER},
1596 ** Availability: Mixmaster
1599 ** This variable contains the path to the Mixmaster binary on your
1600 ** system. It is used with various sets of parameters to gather the
1601 ** list of known remailers, and to finally send a message through the
1605 {"move", DT_QUAD, R_NONE, OPT_MOVE, M_ASKNO},
1608 ** Controls whether or not Mutt-ng will move read messages
1609 ** from your spool mailbox to your ``$$mbox'' mailbox, or as a result of
1610 ** a ``$mbox-hook'' command.
1612 {"message_format", DT_STR, R_NONE, UL &MsgFmt, UL "%s"},
1615 ** This is the string displayed in the ``attachment'' menu for
1616 ** attachments of type \fTmessage/rfc822\fP. For a full listing of defined
1617 ** \fTprintf(3)\fP-like sequences see the section on ``$$index_format''.
1619 {"msgid_format", DT_STR, R_NONE, UL &MsgIdFormat, UL "%Y%m%d%h%M%s.G%P%p"},
1622 ** This is the format for the ``local part'' of the \fTMessage-Id:\fP header
1623 ** field generated by Mutt-ng. If this variable is empty, no \fTMessage-Id:\fP
1624 ** headers will be generated. The '%'
1625 ** character marks that certain data will be added to the string, similar to
1626 ** \fTprintf(3)\fP. The following characters are allowed:
1629 ** .dt %d .dd the current day of month
1630 ** .dt %h .dd the current hour
1631 ** .dt %m .dd the current month
1632 ** .dt %M .dd the current minute
1633 ** .dt %O .dd the current UNIX timestamp (octal)
1634 ** .dt %p .dd the process ID
1635 ** .dt %P .dd the current Message-ID prefix (a character rotating with
1636 ** every Message-ID being generated)
1637 ** .dt %r .dd a random integer value (decimal)
1638 ** .dt %R .dd a random integer value (hexadecimal)
1639 ** .dt %s .dd the current second
1640 ** .dt %T .dd the current UNIX timestamp (decimal)
1641 ** .dt %X .dd the current UNIX timestamp (hexadecimal)
1642 ** .dt %Y .dd the current year (Y2K compliant)
1643 ** .dt %% .dd the '%' character
1646 ** \fBNote:\fP Please only change this setting if you know what you are doing.
1647 ** Also make sure to consult RFC2822 to produce technically \fIvalid\fP strings.
1649 {"narrow_tree", DT_BOOL, R_TREE|R_INDEX, OPTNARROWTREE, 0},
1652 ** This variable, when \fIset\fP, makes the thread tree narrower, allowing
1653 ** deeper threads to fit on the screen.
1656 {"news_cache_dir", DT_SYN, R_NONE, UL "nntp_cache_dir", 0},
1657 {"nntp_cache_dir", DT_PATH, R_NONE, UL &NewsCacheDir, UL "~/.muttng"},
1660 ** Availability: NNTP
1663 ** This variable points to directory where Mutt-ng will cache news
1664 ** article headers. If \fIunset\fP, headers will not be saved at all
1665 ** and will be reloaded each time when you enter a newsgroup.
1667 ** As for the header caching in connection with IMAP and/or Maildir,
1668 ** this drastically increases speed and lowers traffic.
1670 {"news_server", DT_SYN, R_NONE, UL "nntp_host", 0},
1671 {"nntp_host", DT_STR, R_NONE, UL &NewsServer, 0},
1674 ** Availability: NNTP
1677 ** This variable specifies the name (or address) of the NNTP server to be used.
1680 ** defaults to the value specified via the environment variable
1681 ** \fT$$$NNTPSERVER\fP or contained in the file \fT/etc/nntpserver\fP.
1684 ** specify a username and an alternative port for each newsserver, e.g.
1686 ** \fT[nntp[s]://][username[:password]@]newsserver[:port]\fP
1688 ** \fBNote:\fP Using a password as shown and stored in a configuration file
1689 ** presents a security risk since the superuser of your machine may read it
1690 ** regardless of the file's permissions.
1692 {"newsrc", DT_SYN, R_NONE, UL "nntp_newsrc", 0},
1693 {"nntp_newsrc", DT_PATH, R_NONE, UL &NewsRc, UL "~/.newsrc"},
1696 ** Availability: NNTP
1699 ** This file contains information about subscribed newsgroup and
1700 ** articles read so far.
1702 ** To ease the use of multiple news servers, the following \fTprintf(3)\fP-style
1703 ** sequence is understood:
1706 ** %s newsserver name
1709 {"nntp_context", DT_NUM, R_NONE, UL &NntpContext, 1000},
1712 ** Availability: NNTP
1715 ** This variable controls how many news articles to cache per newsgroup
1716 ** (if caching is enabled, see $$nntp_cache_dir) and how many news articles
1717 ** to show in the ``index'' menu.
1719 ** If there're more articles than defined with $$nntp_context, all older ones
1720 ** will be removed/not shown in the index.
1722 {"nntp_load_description", DT_BOOL, R_NONE, OPTLOADDESC, 1},
1725 ** Availability: NNTP
1728 ** This variable controls whether or not descriptions for newsgroups
1729 ** are to be loaded when subscribing to a newsgroup.
1731 {"nntp_user", DT_STR, R_NONE, UL &NntpUser, UL ""},
1734 ** Availability: NNTP
1737 ** Your login name on the NNTP server. If \fIunset\fP and the server requires
1738 ** authentification, Mutt-ng will prompt you for your account name.
1740 {"nntp_pass", DT_STR, R_NONE, UL &NntpPass, UL ""},
1743 ** Availability: NNTP
1746 ** Your password for NNTP account.
1748 ** \fBNote:\fP Storing passwords in a configuration file
1749 ** presents a security risk since the superuser of your machine may read it
1750 ** regardless of the file's permissions.
1752 {"nntp_poll", DT_SYN, R_NONE, UL "nntp_mail_check", 0},
1753 {"nntp_mail_check", DT_NUM, R_NONE, UL &NewsPollTimeout, 60},
1756 ** Availability: NNTP
1759 ** The time in seconds until any operations on a newsgroup except posting a new
1760 ** article will cause a recheck for new news. If set to 0, Mutt-ng will
1761 ** recheck on each operation in index (stepping, read article, etc.).
1763 {"nntp_reconnect", DT_QUAD, R_NONE, OPT_NNTPRECONNECT, M_ASKYES},
1766 ** Availability: NNTP
1769 ** Controls whether or not Mutt-ng will try to reconnect to a newsserver when the
1770 ** was connection lost.
1773 {"pager", DT_PATH, R_NONE, UL &Pager, UL "builtin"},
1776 ** This variable specifies which pager you would like to use to view
1777 ** messages. ``builtin'' means to use the builtin pager, otherwise this
1778 ** variable should specify the pathname of the external pager you would
1781 ** Using an external pager may have some disadvantages: Additional
1782 ** keystrokes are necessary because you can't call Mutt-ng functions
1783 ** directly from the pager, and screen resizes cause lines longer than
1784 ** the screen width to be badly formatted in the help menu.
1786 {"pager_context", DT_NUM, R_NONE, UL &PagerContext, 0},
1789 ** This variable controls the number of lines of context that are given
1790 ** when displaying the next or previous page in the internal pager. By
1791 ** default, Mutt-ng will display the line after the last one on the screen
1792 ** at the top of the next page (0 lines of context).
1794 {"pager_format", DT_STR, R_PAGER, UL &PagerFmt, UL "-%Z- %C/%m: %-20.20n %s"},
1797 ** This variable controls the format of the one-line message ``status''
1798 ** displayed before each message in either the internal or an external
1799 ** pager. The valid sequences are listed in the ``$$index_format''
1802 {"pager_index_lines", DT_NUM, R_PAGER, UL &PagerIndexLines, 0},
1805 ** Determines the number of lines of a mini-index which is shown when in
1806 ** the pager. The current message, unless near the top or bottom of the
1807 ** folder, will be roughly one third of the way down this mini-index,
1808 ** giving the reader the context of a few messages before and after the
1809 ** message. This is useful, for example, to determine how many messages
1810 ** remain to be read in the current thread. One of the lines is reserved
1811 ** for the status bar from the index, so a \fIpager_index_lines\fP of 6
1812 ** will only show 5 lines of the actual index. A value of 0 results in
1813 ** no index being shown. If the number of messages in the current folder
1814 ** is less than \fIpager_index_lines\fP, then the index will only use as
1815 ** many lines as it needs.
1817 {"pager_stop", DT_BOOL, R_NONE, OPTPAGERSTOP, 0},
1820 ** When \fIset\fP, the internal-pager will \fBnot\fP move to the next message
1821 ** when you are at the end of a message and invoke the \fInext-page\fP
1824 {"crypt_autosign", DT_BOOL, R_NONE, OPTCRYPTAUTOSIGN, 0},
1827 ** Setting this variable will cause Mutt-ng to always attempt to
1828 ** cryptographically sign outgoing messages. This can be overridden
1829 ** by use of the \fIpgp-menu\fP, when signing is not required or
1830 ** encryption is requested as well. If ``$$smime_is_default'' is \fIset\fP,
1831 ** then OpenSSL is used instead to create S/MIME messages and settings can
1832 ** be overridden by use of the \fIsmime-menu\fP.
1835 {"crypt_autoencrypt", DT_BOOL, R_NONE, OPTCRYPTAUTOENCRYPT, 0},
1838 ** Setting this variable will cause Mutt-ng to always attempt to PGP
1839 ** encrypt outgoing messages. This is probably only useful in
1840 ** connection to the \fIsend-hook\fP command. It can be overridden
1841 ** by use of the \fIpgp-menu\fP, when encryption is not required or
1842 ** signing is requested as well. If ``$$smime_is_default'' is \fIset\fP,
1843 ** then OpenSSL is used instead to create S/MIME messages and
1844 ** settings can be overridden by use of the \fIsmime-menu\fP.
1847 {"pgp_ignore_subkeys", DT_BOOL, R_NONE, OPTPGPIGNORESUB, 1},
1850 ** Setting this variable will cause Mutt-ng to ignore OpenPGP subkeys. Instead,
1851 ** the principal key will inherit the subkeys' capabilities. \fIUnset\fP this
1852 ** if you want to play interesting key selection games.
1855 {"crypt_replyencrypt", DT_BOOL, R_NONE, OPTCRYPTREPLYENCRYPT, 1},
1858 ** If \fIset\fP, automatically PGP or OpenSSL encrypt replies to messages which are
1862 {"crypt_replysign", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGN, 0},
1865 ** If \fIset\fP, automatically PGP or OpenSSL sign replies to messages which are
1868 ** \fBNote:\fP this does not work on messages that are encrypted \fBand\fP signed!
1871 {"crypt_replysignencrypted", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGNENCRYPTED, 0},
1874 ** If \fIset\fP, automatically PGP or OpenSSL sign replies to messages
1875 ** which are encrypted. This makes sense in combination with
1876 ** ``$$crypt_replyencrypt'', because it allows you to sign all
1877 ** messages which are automatically encrypted. This works around
1878 ** the problem noted in ``$$crypt_replysign'', that Mutt-ng is not able
1879 ** to find out whether an encrypted message is also signed.
1882 {"crypt_timestamp", DT_BOOL, R_NONE, OPTCRYPTTIMESTAMP, 1},
1885 ** If \fIset\fP, Mutt-ng will include a time stamp in the lines surrounding
1886 ** PGP or S/MIME output, so spoofing such lines is more difficult.
1887 ** If you are using colors to mark these lines, and rely on these,
1888 ** you may \fIunset\fP this setting.
1891 {"pgp_use_gpg_agent", DT_BOOL, R_NONE, OPTUSEGPGAGENT, 0},
1894 ** If \fIset\fP, Mutt-ng will use a possibly-running gpg-agent process.
1897 {"crypt_verify_sig", DT_QUAD, R_NONE, OPT_VERIFYSIG, M_YES},
1900 ** If ``\fIyes\fP'', always attempt to verify PGP or S/MIME signatures.
1901 ** If ``\fIask\fP'', ask whether or not to verify the signature.
1902 ** If ``\fIno\fP'', never attempt to verify cryptographic signatures.
1905 {"smime_is_default", DT_BOOL, R_NONE, OPTSMIMEISDEFAULT, 0},
1908 ** The default behaviour of Mutt-ng is to use PGP on all auto-sign/encryption
1909 ** operations. To override and to use OpenSSL instead this must be \fIset\fP.
1911 ** However, this has no effect while replying, since Mutt-ng will automatically
1912 ** select the same application that was used to sign/encrypt the original
1915 ** (Note that this variable can be overridden by unsetting $$crypt_autosmime.)
1918 {"smime_ask_cert_label", DT_BOOL, R_NONE, OPTASKCERTLABEL, 1},
1921 ** This flag controls whether you want to be asked to enter a label
1922 ** for a certificate about to be added to the database or not. It is
1923 ** \fIset\fP by default.
1926 {"smime_decrypt_use_default_key", DT_BOOL, R_NONE, OPTSDEFAULTDECRYPTKEY, 1},
1929 ** If \fIset\fP (default) this tells Mutt-ng to use the default key for decryption. Otherwise,
1930 ** if manage multiple certificate-key-pairs, Mutt-ng will try to use the mailbox-address
1931 ** to determine the key to use. It will ask you to supply a key, if it can't find one.
1934 {"pgp_entry_format", DT_STR, R_NONE, UL &PgpEntryFormat, UL "%4n %t%f %4l/0x%k %-4a %2c %u"},
1937 ** This variable allows you to customize the PGP key selection menu to
1938 ** your personal taste. This string is similar to ``$$index_format'', but
1939 ** has its own set of \fTprintf(3)\fP-like sequences:
1942 ** .dt %n .dd number
1943 ** .dt %k .dd key id
1944 ** .dt %u .dd user id
1945 ** .dt %a .dd algorithm
1946 ** .dt %l .dd key length
1948 ** .dt %c .dd capabilities
1949 ** .dt %t .dd trust/validity of the key-uid association
1950 ** .dt %[<s>] .dd date of the key where <s> is an \fTstrftime(3)\fP expression
1955 {"pgp_good_sign", DT_RX, R_NONE, UL &PgpGoodSign, 0},
1958 ** If you assign a text to this variable, then a PGP signature is only
1959 ** considered verified if the output from $$pgp_verify_command contains
1960 ** the text. Use this variable if the exit code from the command is 0
1961 ** even for bad signatures.
1964 {"pgp_check_exit", DT_BOOL, R_NONE, OPTPGPCHECKEXIT, 1},
1967 ** If \fIset\fP, Mutt-ng will check the exit code of the PGP subprocess when
1968 ** signing or encrypting. A non-zero exit code means that the
1969 ** subprocess failed.
1972 {"pgp_long_ids", DT_BOOL, R_NONE, OPTPGPLONGIDS, 0},
1975 ** If \fIset\fP, use 64 bit PGP key IDs. \fIUnset\fP uses the normal 32 bit Key IDs.
1978 {"pgp_retainable_sigs", DT_BOOL, R_NONE, OPTPGPRETAINABLESIG, 0},
1981 ** If \fIset\fP, signed and encrypted messages will consist of nested
1982 ** multipart/signed and multipart/encrypted body parts.
1984 ** This is useful for applications like encrypted and signed mailing
1985 ** lists, where the outer layer (multipart/encrypted) can be easily
1986 ** removed, while the inner multipart/signed part is retained.
1989 {"pgp_autoinline", DT_BOOL, R_NONE, OPTPGPAUTOINLINE, 0},
1992 ** This option controls whether Mutt-ng generates old-style inline
1993 ** (traditional) PGP encrypted or signed messages under certain
1994 ** circumstances. This can be overridden by use of the \fIpgp-menu\fP,
1995 ** when inline is not required.
1997 ** Note that Mutt-ng might automatically use PGP/MIME for messages
1998 ** which consist of more than a single MIME part. Mutt-ng can be
1999 ** configured to ask before sending PGP/MIME messages when inline
2000 ** (traditional) would not work.
2001 ** See also: ``$$pgp_mime_auto''.
2003 ** Also note that using the old-style PGP message format is \fBstrongly\fP
2004 ** \fBdeprecated\fP.
2007 {"pgp_replyinline", DT_BOOL, R_NONE, OPTPGPREPLYINLINE, 0},
2010 ** Setting this variable will cause Mutt-ng to always attempt to
2011 ** create an inline (traditional) message when replying to a
2012 ** message which is PGP encrypted/signed inline. This can be
2013 ** overridden by use of the \fIpgp-menu\fP, when inline is not
2014 ** required. This option does not automatically detect if the
2015 ** (replied-to) message is inline; instead it relies on Mutt-ng
2016 ** internals for previously checked/flagged messages.
2018 ** Note that Mutt-ng might automatically use PGP/MIME for messages
2019 ** which consist of more than a single MIME part. Mutt-ng can be
2020 ** configured to ask before sending PGP/MIME messages when inline
2021 ** (traditional) would not work.
2022 ** See also: ``$$pgp_mime_auto''.
2024 ** Also note that using the old-style PGP message format is \fBstrongly\fP
2025 ** \fBdeprecated\fP.
2029 {"pgp_show_unusable", DT_BOOL, R_NONE, OPTPGPSHOWUNUSABLE, 1},
2032 ** If \fIset\fP, Mutt-ng will display non-usable keys on the PGP key selection
2033 ** menu. This includes keys which have been revoked, have expired, or
2034 ** have been marked as ``disabled'' by the user.
2037 {"pgp_sign_as", DT_STR, R_NONE, UL &PgpSignAs, 0},
2040 ** If you have more than one key pair, this option allows you to specify
2041 ** which of your private keys to use. It is recommended that you use the
2042 ** keyid form to specify your key (e.g., ``\fT0x00112233\fP'').
2045 {"pgp_strict_enc", DT_BOOL, R_NONE, OPTPGPSTRICTENC, 1},
2048 ** If \fIset\fP, Mutt-ng will automatically encode PGP/MIME signed messages as
2049 ** \fTquoted-printable\fP. Please note that unsetting this variable may
2050 ** lead to problems with non-verifyable PGP signatures, so only change
2051 ** this if you know what you are doing.
2054 {"pgp_timeout", DT_NUM, R_NONE, UL &PgpTimeout, 300},
2057 ** The number of seconds after which a cached passphrase will expire if
2058 ** not used. Default: 300.
2061 {"pgp_sort_keys", DT_SORT|DT_SORT_KEYS, R_NONE, UL &PgpSortKeys, SORT_ADDRESS},
2064 ** Specifies how the entries in the ``pgp keys'' menu are sorted. The
2065 ** following are legal values:
2068 ** .dt address .dd sort alphabetically by user id
2069 ** .dt keyid .dd sort alphabetically by key id
2070 ** .dt date .dd sort by key creation date
2071 ** .dt trust .dd sort by the trust of the key
2074 ** If you prefer reverse order of the above values, prefix it with
2078 {"pgp_mime_auto", DT_QUAD, R_NONE, OPT_PGPMIMEAUTO, M_ASKYES},
2081 ** This option controls whether Mutt-ng will prompt you for
2082 ** automatically sending a (signed/encrypted) message using
2083 ** PGP/MIME when inline (traditional) fails (for any reason).
2085 ** Also note that using the old-style PGP message format is \fBstrongly\fP
2086 ** \fBdeprecated\fP.
2089 {"pgp_auto_decode", DT_BOOL, R_NONE, OPTPGPAUTODEC, 0},
2092 ** If \fIset\fP, Mutt-ng will automatically attempt to decrypt traditional PGP
2093 ** messages whenever the user performs an operation which ordinarily would
2094 ** result in the contents of the message being operated on. For example,
2095 ** if the user displays a pgp-traditional message which has not been manually
2096 ** checked with the check-traditional-pgp function, Mutt-ng will automatically
2097 ** check the message for traditional pgp.
2100 /* XXX Default values! */
2102 {"pgp_decode_command", DT_STR, R_NONE, UL &PgpDecodeCommand, 0},
2105 ** This format strings specifies a command which is used to decode
2106 ** application/pgp attachments.
2108 ** The PGP command formats have their own set of \fTprintf(3)\fP-like sequences:
2111 ** .dt %p .dd Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
2112 ** string otherwise. Note: This may be used with a %? construct.
2113 ** .dt %f .dd Expands to the name of a file containing a message.
2114 ** .dt %s .dd Expands to the name of a file containing the signature part
2115 ** . of a multipart/signed attachment when verifying it.
2116 ** .dt %a .dd The value of $$pgp_sign_as.
2117 ** .dt %r .dd One or more key IDs.
2120 ** For examples on how to configure these formats for the various versions
2121 ** of PGP which are floating around, see the pgp*.rc and gpg.rc files in
2122 ** the \fTsamples/\fP subdirectory which has been installed on your system
2123 ** alongside the documentation.
2126 {"pgp_getkeys_command", DT_STR, R_NONE, UL &PgpGetkeysCommand, 0},
2129 ** This command is invoked whenever Mutt-ng will need public key information.
2130 ** \fT%r\fP is the only \fTprintf(3)\fP-like sequence used with this format.
2133 {"pgp_verify_command", DT_STR, R_NONE, UL &PgpVerifyCommand, 0},
2136 ** This command is used to verify PGP signatures.
2139 {"pgp_decrypt_command", DT_STR, R_NONE, UL &PgpDecryptCommand, 0},
2142 ** This command is used to decrypt a PGP encrypted message.
2145 {"pgp_clearsign_command", DT_STR, R_NONE, UL &PgpClearSignCommand, 0},
2148 ** This format is used to create a old-style ``clearsigned'' PGP message.
2150 ** Note that the use of this format is \fBstrongly\fP \fBdeprecated\fP.
2153 {"pgp_sign_command", DT_STR, R_NONE, UL &PgpSignCommand, 0},
2156 ** This command is used to create the detached PGP signature for a
2157 ** multipart/signed PGP/MIME body part.
2160 {"pgp_encrypt_sign_command", DT_STR, R_NONE, UL &PgpEncryptSignCommand, 0},
2163 ** This command is used to both sign and encrypt a body part.
2166 {"pgp_encrypt_only_command", DT_STR, R_NONE, UL &PgpEncryptOnlyCommand, 0},
2169 ** This command is used to encrypt a body part without signing it.
2172 {"pgp_import_command", DT_STR, R_NONE, UL &PgpImportCommand, 0},
2175 ** This command is used to import a key from a message into
2176 ** the user's public key ring.
2179 {"pgp_export_command", DT_STR, R_NONE, UL &PgpExportCommand, 0},
2182 ** This command is used to export a public key from the user's
2186 {"pgp_verify_key_command", DT_STR, R_NONE, UL &PgpVerifyKeyCommand, 0},
2189 ** This command is used to verify key information from the key selection
2193 {"pgp_list_secring_command", DT_STR, R_NONE, UL &PgpListSecringCommand, 0},
2196 ** This command is used to list the secret key ring's contents. The
2197 ** output format must be analogous to the one used by
2198 ** \fTgpg --list-keys --with-colons\fP.
2200 ** This format is also generated by the \fTpgpring\fP utility which comes
2204 {"pgp_list_pubring_command", DT_STR, R_NONE, UL &PgpListPubringCommand, 0},
2207 ** This command is used to list the public key ring's contents. The
2208 ** output format must be analogous to the one used by
2209 ** \fTgpg --list-keys --with-colons\fP.
2211 ** This format is also generated by the \fTpgpring\fP utility which comes
2215 {"forward_decrypt", DT_BOOL, R_NONE, OPTFORWDECRYPT, 1},
2218 ** Controls the handling of encrypted messages when forwarding a message.
2219 ** When \fIset\fP, the outer layer of encryption is stripped off. This
2220 ** variable is only used if ``$$mime_forward'' is \fIset\fP and
2221 ** ``$$mime_forward_decode'' is \fIunset\fP.
2224 {"smime_timeout", DT_NUM, R_NONE, UL &SmimeTimeout, 300},
2227 ** The number of seconds after which a cached passphrase will expire if
2231 {"smime_encrypt_with", DT_STR, R_NONE, UL &SmimeCryptAlg, 0},
2234 ** This sets the algorithm that should be used for encryption.
2235 ** Valid choices are ``\fTdes\fP'', ``\fTdes3\fP'', ``\fTrc2-40\fP'',
2236 ** ``\fTrc2-64\fP'', ``\frc2-128\fP''.
2238 ** If \fIunset\fP ``\fI3des\fP'' (TripleDES) is used.
2241 {"smime_keys", DT_PATH, R_NONE, UL &SmimeKeys, 0},
2244 ** Since there is no pubring/secring as with PGP, Mutt-ng has to handle
2245 ** storage ad retrieval of keys/certs by itself. This is very basic right now,
2246 ** and stores keys and certificates in two different directories, both
2247 ** named as the hash-value retrieved from OpenSSL. There is an index file
2248 ** which contains mailbox-address keyid pair, and which can be manually
2249 ** edited. This one points to the location of the private keys.
2252 {"smime_ca_location", DT_PATH, R_NONE, UL &SmimeCALocation, 0},
2255 ** This variable contains the name of either a directory, or a file which
2256 ** contains trusted certificates for use with OpenSSL.
2259 {"smime_certificates", DT_PATH, R_NONE, UL &SmimeCertificates, 0},
2262 ** Since there is no pubring/secring as with PGP, Mutt-ng has to handle
2263 ** storage and retrieval of keys by itself. This is very basic right
2264 ** now, and keys and certificates are stored in two different
2265 ** directories, both named as the hash-value retrieved from
2266 ** OpenSSL. There is an index file which contains mailbox-address
2267 ** keyid pairs, and which can be manually edited. This one points to
2268 ** the location of the certificates.
2271 {"smime_decrypt_command", DT_STR, R_NONE, UL &SmimeDecryptCommand, 0},
2274 ** This format string specifies a command which is used to decrypt
2275 ** \fTapplication/x-pkcs7-mime\fP attachments.
2277 ** The OpenSSL command formats have their own set of \fTprintf(3)\fP-like sequences
2278 ** similar to PGP's:
2281 ** .dt %f .dd Expands to the name of a file containing a message.
2282 ** .dt %s .dd Expands to the name of a file containing the signature part
2283 ** . of a multipart/signed attachment when verifying it.
2284 ** .dt %k .dd The key-pair specified with $$smime_default_key
2285 ** .dt %c .dd One or more certificate IDs.
2286 ** .dt %a .dd The algorithm used for encryption.
2287 ** .dt %C .dd CA location: Depending on whether $$smime_ca_location
2288 ** . points to a directory or file, this expands to
2289 ** . "-CApath $$smime_ca_location" or "-CAfile $$smime_ca_location".
2292 ** For examples on how to configure these formats, see the smime.rc in
2293 ** the \fTsamples/\fP subdirectory which has been installed on your system
2294 ** alongside the documentation.
2297 {"smime_verify_command", DT_STR, R_NONE, UL &SmimeVerifyCommand, 0},
2300 ** This command is used to verify S/MIME signatures of type \fTmultipart/signed\fP.
2303 {"smime_verify_opaque_command", DT_STR, R_NONE, UL &SmimeVerifyOpaqueCommand, 0},
2306 ** This command is used to verify S/MIME signatures of type
2307 ** \fTapplication/x-pkcs7-mime\fP.
2310 {"smime_sign_command", DT_STR, R_NONE, UL &SmimeSignCommand, 0},
2313 ** This command is used to created S/MIME signatures of type
2314 ** \fTmultipart/signed\fP, which can be read by all mail clients.
2317 {"smime_sign_opaque_command", DT_STR, R_NONE, UL &SmimeSignOpaqueCommand, 0},
2320 ** This command is used to created S/MIME signatures of type
2321 ** \fTapplication/x-pkcs7-signature\fP, which can only be handled by mail
2322 ** clients supporting the S/MIME extension.
2325 {"smime_encrypt_command", DT_STR, R_NONE, UL &SmimeEncryptCommand, 0},
2328 ** This command is used to create encrypted S/MIME messages.
2331 {"smime_pk7out_command", DT_STR, R_NONE, UL &SmimePk7outCommand, 0},
2334 ** This command is used to extract PKCS7 structures of S/MIME signatures,
2335 ** in order to extract the public X509 certificate(s).
2338 {"smime_get_cert_command", DT_STR, R_NONE, UL &SmimeGetCertCommand, 0},
2341 ** This command is used to extract X509 certificates from a PKCS7 structure.
2344 {"smime_get_signer_cert_command", DT_STR, R_NONE, UL &SmimeGetSignerCertCommand, 0},
2347 ** This command is used to extract only the signers X509 certificate from a S/MIME
2348 ** signature, so that the certificate's owner may get compared to the
2349 ** email's ``\fTFrom:\fP'' header field.
2352 {"smime_import_cert_command", DT_STR, R_NONE, UL &SmimeImportCertCommand, 0},
2355 ** This command is used to import a certificate via \fTsmime_keysng\fP.
2358 {"smime_get_cert_email_command", DT_STR, R_NONE, UL &SmimeGetCertEmailCommand, 0},
2361 ** This command is used to extract the mail address(es) used for storing
2362 ** X509 certificates, and for verification purposes (to check whether the
2363 ** certificate was issued for the sender's mailbox).
2366 {"smime_default_key", DT_STR, R_NONE, UL &SmimeDefaultKey, 0},
2369 ** This is the default key-pair to use for signing. This must be set to the
2370 ** keyid (the hash-value that OpenSSL generates) to work properly
2373 #if defined(USE_LIBESMTP)
2374 {"smtp_auth_username", DT_SYN, R_NONE, UL "smtp_user", 0},
2375 {"smtp_user", DT_STR, R_NONE, UL &SmtpAuthUser, 0},
2378 ** Availability: SMTP
2381 ** Defines the username to use with SMTP AUTH. Setting this variable will
2382 ** cause Mutt-ng to attempt to use SMTP AUTH when sending.
2384 {"smtp_auth_password", DT_SYN, R_NONE, UL "smtp_pass", 0},
2385 {"smtp_pass", DT_STR, R_NONE, UL &SmtpAuthPass, 0},
2388 ** Availability: SMTP
2391 ** Defines the password to use with SMTP AUTH. If ``$$smtp_user''
2392 ** is set, but this variable is not, you will be prompted for a password
2395 ** \fBNote:\fP Storing passwords in a configuration file
2396 ** presents a security risk since the superuser of your machine may read it
2397 ** regardless of the file's permissions.
2399 {"smtp_envelope", DT_STR, R_NONE, UL &SmtpEnvFrom, 0},
2402 ** Availability: SMTP
2405 ** If this variable is non-empty, it'll be used as the envelope sender. If it's empty
2406 ** (the default), the value of the regular \fTFrom:\fP header will be used.
2409 ** This may be necessary as some providers don't allow for arbitrary values
2410 ** as the envelope sender but only a particular one which may not be the same as the
2411 ** user's desired \fTFrom:\fP header.
2413 {"smtp_host", DT_STR, R_NONE, UL &SmtpHost, 0},
2416 ** Availability: SMTP
2419 ** Defines the SMTP host which will be used to deliver mail, as opposed
2420 ** to invoking the sendmail binary. Setting this variable overrides the
2421 ** value of ``$$sendmail'', and any associated variables.
2423 {"smtp_port", DT_NUM, R_NONE, UL &SmtpPort, 25},
2426 ** Availability: SMTP
2429 ** Defines the port that the SMTP host is listening on for mail delivery.
2430 ** Must be specified as a number.
2432 ** Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP
2433 ** servers will probably desire 587, the mail submission port.
2435 {"smtp_use_tls", DT_STR, R_NONE, UL &SmtpUseTLS, 0},
2438 ** Availability: SMTP (and SSL)
2441 ** Defines wether to use STARTTLS. If this option is set to ``\fIrequired\fP''
2442 ** and the server does not support STARTTLS or there is an error in the
2443 ** TLS Handshake, the connection will fail. Setting this to ``\fIenabled\fP''
2444 ** will try to start TLS and continue without TLS in case of an error.
2447 ** Muttng still needs to have SSL support enabled in order to use it.
2450 #if defined(USE_SSL) || defined(USE_GNUTLS)
2452 {"ssl_client_cert", DT_PATH, R_NONE, UL &SslClientCert, 0},
2455 ** Availability: SSL
2458 ** The file containing a client certificate and its associated private
2461 #endif /* USE_SSL */
2462 {"ssl_force_tls", DT_BOOL, R_NONE, OPTSSLFORCETLS, 0 },
2465 ** If this variable is \fIset\fP, mutt-ng will require that all connections
2466 ** to remote servers be encrypted. Furthermore it will attempt to
2467 ** negotiate TLS even if the server does not advertise the capability,
2468 ** since it would otherwise have to abort the connection anyway. This
2469 ** option supersedes ``$$ssl_starttls''.
2471 {"ssl_starttls", DT_QUAD, R_NONE, OPT_SSLSTARTTLS, M_YES},
2474 ** Availability: SSL or GNUTLS
2477 ** If \fIset\fP (the default), Mutt-ng will attempt to use STARTTLS on servers
2478 ** advertising the capability. When \fIunset\fP, Mutt-ng will not attempt to
2479 ** use STARTTLS regardless of the server's capabilities.
2481 {"certificate_file", DT_PATH, R_NONE, UL &SslCertFile, UL "~/.mutt_certificates"},
2484 ** Availability: SSL or GNUTLS
2487 ** This variable specifies the file where the certificates you trust
2488 ** are saved. When an unknown certificate is encountered, you are asked
2489 ** if you accept it or not. If you accept it, the certificate can also
2490 ** be saved in this file and further connections are automatically
2493 ** You can also manually add CA certificates in this file. Any server
2494 ** certificate that is signed with one of these CA certificates are
2495 ** also automatically accepted.
2497 ** Example: \fTset certificate_file=~/.muttng/certificates\fP
2499 # if defined(_MAKEDOC) || !defined (USE_GNUTLS)
2500 {"ssl_usesystemcerts", DT_BOOL, R_NONE, OPTSSLSYSTEMCERTS, 1},
2503 ** Availability: SSL
2506 ** If set to \fIyes\fP, Mutt-ng will use CA certificates in the
2507 ** system-wide certificate store when checking if server certificate
2508 ** is signed by a trusted CA.
2510 {"entropy_file", DT_PATH, R_NONE, UL &SslEntropyFile, 0},
2513 ** Availability: SSL
2516 ** The file which includes random data that is used to initialize SSL
2517 ** library functions.
2519 {"ssl_use_sslv2", DT_BOOL, R_NONE, OPTSSLV2, 1},
2522 ** Availability: SSL
2525 ** This variables specifies whether to attempt to use SSLv2 in the
2526 ** SSL authentication process.
2528 # endif /* _MAKEDOC || !USE_GNUTLS */
2529 {"ssl_use_sslv3", DT_BOOL, R_NONE, OPTSSLV3, 1},
2532 ** Availability: SSL or GNUTLS
2535 ** This variables specifies whether to attempt to use SSLv3 in the
2536 ** SSL authentication process.
2538 {"ssl_use_tlsv1", DT_BOOL, R_NONE, OPTTLSV1, 1},
2541 ** Availability: SSL or GNUTLS
2544 ** This variables specifies whether to attempt to use TLSv1 in the
2545 ** SSL authentication process.
2548 {"ssl_min_dh_prime_bits", DT_NUM, R_NONE, UL &SslDHPrimeBits, 0},
2551 ** Availability: GNUTLS
2554 ** This variable specifies the minimum acceptable prime size (in bits)
2555 ** for use in any Diffie-Hellman key exchange. A value of 0 will use
2556 ** the default from the GNUTLS library.
2558 {"ssl_ca_certificates_file", DT_PATH, R_NONE, UL &SslCACertFile, 0},
2561 ** This variable specifies a file containing trusted CA certificates.
2562 ** Any server certificate that is signed with one of these CA
2563 ** certificates are also automatically accepted.
2565 ** Example: \fTset ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt\fP
2567 # endif /* USE_GNUTLS */
2568 # endif /* USE_SSL || USE_GNUTLS */
2569 {"pipe_split", DT_BOOL, R_NONE, OPTPIPESPLIT, 0},
2572 ** Used in connection with the \fIpipe-message\fP command and the ``tag-
2573 ** prefix'' or ``tag-prefix-cond'' operators.
2574 ** If this variable is \fIunset\fP, when piping a list of
2575 ** tagged messages Mutt-ng will concatenate the messages and will pipe them
2576 ** as a single folder. When \fIset\fP, Mutt-ng will pipe the messages one by one.
2577 ** In both cases the messages are piped in the current sorted order,
2578 ** and the ``$$pipe_sep'' separator is added after each message.
2580 {"pipe_decode", DT_BOOL, R_NONE, OPTPIPEDECODE, 0},
2583 ** Used in connection with the \fIpipe-message\fP command. When \fIunset\fP,
2584 ** Mutt-ng will pipe the messages without any preprocessing. When \fIset\fP, Mutt-ng
2585 ** will weed headers and will attempt to PGP/MIME decode the messages
2588 {"pipe_sep", DT_STR, R_NONE, UL &PipeSep, UL "\n"},
2591 ** The separator to add between messages when piping a list of tagged
2592 ** messages to an external Unix command.
2595 {"pop_authenticators", DT_STR, R_NONE, UL &PopAuthenticators, UL 0},
2598 ** Availability: POP
2601 ** This is a colon-delimited list of authentication methods Mutt-ng may
2602 ** attempt to use to log in to an POP server, in the order Mutt-ng should
2603 ** try them. Authentication methods are either ``\fTuser\fP'', ``\fTapop\fP''
2604 ** or any SASL mechanism, eg ``\fTdigest-md5\fP'', ``\fTgssapi\fP'' or ``\fTcram-md5\fP''.
2606 ** This parameter is case-insensitive. If this parameter is \fIunset\fP
2607 ** (the default) Mutt-ng will try all available methods, in order from
2608 ** most-secure to least-secure.
2610 ** Example: \fTset pop_authenticators="digest-md5:apop:user"\fP
2612 {"pop_auth_try_all", DT_BOOL, R_NONE, OPTPOPAUTHTRYALL, 1},
2615 ** Availability: POP
2618 ** If \fIset\fP, Mutt-ng will try all available methods. When \fIunset\fP, Mutt-ng will
2619 ** only fall back to other authentication methods if the previous
2620 ** methods are unavailable. If a method is available but authentication
2621 ** fails, Mutt-ng will not connect to the POP server.
2623 {"pop_checkinterval", DT_SYN, R_NONE, UL "pop_mail_check", 0},
2624 {"pop_mail_check", DT_NUM, R_NONE, UL &PopCheckTimeout, 60},
2627 ** Availability: POP
2630 ** This variable configures how often (in seconds) POP should look for
2633 {"pop_delete", DT_QUAD, R_NONE, OPT_POPDELETE, M_ASKNO},
2636 ** Availability: POP
2639 ** If \fIset\fP, Mutt-ng will delete successfully downloaded messages from the POP
2640 ** server when using the ``fetch-mail'' function. When \fIunset\fP, Mutt-ng will
2641 ** download messages but also leave them on the POP server.
2643 {"pop_host", DT_STR, R_NONE, UL &PopHost, UL ""},
2646 ** Availability: POP
2649 ** The name of your POP server for the ``fetch-mail'' function. You
2650 ** can also specify an alternative port, username and password, i.e.:
2652 ** \fT[pop[s]://][username[:password]@]popserver[:port]\fP
2654 ** \fBNote:\fP Storing passwords in a configuration file
2655 ** presents a security risk since the superuser of your machine may read it
2656 ** regardless of the file's permissions.
2658 {"pop_last", DT_BOOL, R_NONE, OPTPOPLAST, 0},
2661 ** Availability: POP
2664 ** If this variable is \fIset\fP, Mutt-ng will try to use the ``\fTLAST\fP'' POP command
2665 ** for retrieving only unread messages from the POP server when using
2666 ** the ``fetch-mail'' function.
2668 {"pop_reconnect", DT_QUAD, R_NONE, OPT_POPRECONNECT, M_ASKYES},
2671 ** Availability: POP
2674 ** Controls whether or not Mutt-ng will try to reconnect to a POP server when the
2675 ** connection is lost.
2677 {"pop_user", DT_STR, R_NONE, UL &PopUser, 0},
2680 ** Availability: POP
2683 ** Your login name on the POP server.
2685 ** This variable defaults to your user name on the local machine.
2687 {"pop_pass", DT_STR, R_NONE, UL &PopPass, UL ""},
2690 ** Availability: POP
2693 ** Specifies the password for your POP account. If \fIunset\fP, Mutt-ng will
2694 ** prompt you for your password when you open POP mailbox.
2696 ** \fBNote:\fP Storing passwords in a configuration file
2697 ** presents a security risk since the superuser of your machine may read it
2698 ** regardless of the file's permissions.
2700 #endif /* USE_POP */
2701 {"post_indent_string", DT_STR, R_NONE, UL &PostIndentString, UL ""},
2704 ** Similar to the ``$$attribution'' variable, Mutt-ng will append this
2705 ** string after the inclusion of a message which is being replied to.
2708 {"post_moderated", DT_SYN, R_NONE, UL "nntp_post_moderated", 0 },
2709 {"nntp_post_moderated", DT_QUAD, R_NONE, OPT_TOMODERATED, M_ASKYES},
2712 ** Availability: NNTP
2715 ** If set to \fIyes\fP, Mutt-ng will post articles to newsgroup that have
2716 ** not permissions to post (e.g. moderated).
2718 ** \fBNote:\fP if the newsserver
2719 ** does not support posting to that newsgroup or a group is totally read-only, that
2720 ** posting will not have any effect.
2723 {"postpone", DT_QUAD, R_NONE, OPT_POSTPONE, M_ASKYES},
2726 ** Controls whether or not messages are saved in the ``$$postponed''
2727 ** mailbox when you elect not to send immediately.
2729 {"postponed", DT_PATH, R_NONE, UL &Postponed, UL "~/postponed"},
2732 ** Mutt-ng allows you to indefinitely ``$postpone sending a message'' which
2733 ** you are editing. When you choose to postpone a message, Mutt-ng saves it
2734 ** in the mailbox specified by this variable. Also see the ``$$postpone''
2738 {"preconnect", DT_STR, R_NONE, UL &Preconnect, UL 0},
2741 ** If \fIset\fP, a shell command to be executed if Mutt-ng fails to establish
2742 ** a connection to the server. This is useful for setting up secure
2743 ** connections, e.g. with \fTssh(1)\fP. If the command returns a nonzero
2744 ** status, Mutt-ng gives up opening the server. Example:
2746 ** \fTpreconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net
2747 ** sleep 20 < /dev/null > /dev/null"\fP
2749 ** Mailbox ``foo'' on mailhost.net can now be reached
2750 ** as ``{localhost:1234}foo''.
2752 ** \fBNote:\fP For this example to work, you must be able to log in to the
2753 ** remote machine without having to enter a password.
2755 #endif /* USE_SOCKET */
2756 {"print", DT_QUAD, R_NONE, OPT_PRINT, M_ASKNO},
2759 ** Controls whether or not Mutt-ng really prints messages.
2760 ** This is set to \fIask-no\fP by default, because some people
2761 ** accidentally hit ``p'' often.
2763 {"print_command", DT_PATH, R_NONE, UL &PrintCmd, UL "lpr"},
2766 ** This specifies the command pipe that should be used to print messages.
2768 {"print_decode", DT_BOOL, R_NONE, OPTPRINTDECODE, 1},
2771 ** Used in connection with the print-message command. If this
2772 ** option is \fIset\fP, the message is decoded before it is passed to the
2773 ** external command specified by $$print_command. If this option
2774 ** is \fIunset\fP, no processing will be applied to the message when
2775 ** printing it. The latter setting may be useful if you are using
2776 ** some advanced printer filter which is able to properly format
2777 ** e-mail messages for printing.
2779 {"print_split", DT_BOOL, R_NONE, OPTPRINTSPLIT, 0},
2782 ** Used in connection with the print-message command. If this option
2783 ** is \fIset\fP, the command specified by $$print_command is executed once for
2784 ** each message which is to be printed. If this option is \fIunset\fP,
2785 ** the command specified by $$print_command is executed only once, and
2786 ** all the messages are concatenated, with a form feed as the message
2789 ** Those who use the \fTenscript(1)\fP program's mail-printing mode will
2790 ** most likely want to set this option.
2792 {"prompt_after", DT_BOOL, R_NONE, OPTPROMPTAFTER, 1},
2795 ** If you use an \fIexternal\fP ``$$pager'', setting this variable will
2796 ** cause Mutt-ng to prompt you for a command when the pager exits rather
2797 ** than returning to the index menu. If \fIunset\fP, Mutt-ng will return to the
2798 ** index menu when the external pager exits.
2800 {"query_command", DT_PATH, R_NONE, UL &QueryCmd, UL ""},
2803 ** This specifies the command that Mutt-ng will use to make external address
2804 ** queries. The string should contain a \fT%s\fP, which will be substituted
2805 ** with the query string the user types. See ``$query'' for more
2808 {"quit", DT_QUAD, R_NONE, OPT_QUIT, M_YES},
2811 ** This variable controls whether ``quit'' and ``exit'' actually quit
2812 ** from Mutt-ng. If it set to \fIyes\fP, they do quit, if it is set to \fIno\fP, they
2813 ** have no effect, and if it is set to \fIask-yes\fP or \fIask-no\fP, you are
2814 ** prompted for confirmation when you try to quit.
2816 {"quote_empty", DT_BOOL, R_NONE, OPTQUOTEEMPTY, 1},
2819 ** Controls whether or not empty lines will be quoted using
2820 ** ``$indent_string''.
2822 {"quote_quoted", DT_BOOL, R_NONE, OPTQUOTEQUOTED, 0},
2825 ** Controls how quoted lines will be quoted. If \fIset\fP, one quote
2826 ** character will be added to the end of existing prefix. Otherwise,
2827 ** quoted lines will be prepended by ``$indent_string''.
2829 {"quote_regexp", DT_RX, R_PAGER, UL &QuoteRegexp, UL "^([ \t]*[|>:}#])+"},
2832 ** A regular expression used in the internal-pager to determine quoted
2833 ** sections of text in the body of a message.
2835 ** \fBNote:\fP In order to use the \fIquoted\fP\fBx\fP patterns in the
2836 ** internal pager, you need to set this to a regular expression that
2837 ** matches \fIexactly\fP the quote characters at the beginning of quoted
2840 {"read_inc", DT_NUM, R_NONE, UL &ReadInc, 10},
2843 ** If set to a value greater than 0, Mutt-ng will display which message it
2844 ** is currently on when reading a mailbox. The message is printed after
2845 ** \fIread_inc\fP messages have been read (e.g., if set to 25, Mutt-ng will
2846 ** print a message when it reads message 25, and then again when it gets
2847 ** to message 50). This variable is meant to indicate progress when
2848 ** reading large mailboxes which may take some time.
2849 ** When set to 0, only a single message will appear before the reading
2852 ** Also see the ``$$write_inc'' variable.
2854 {"read_only", DT_BOOL, R_NONE, OPTREADONLY, 0},
2857 ** If set, all folders are opened in read-only mode.
2859 {"realname", DT_STR, R_BOTH, UL &Realname, 0},
2862 ** This variable specifies what ``real'' or ``personal'' name should be used
2863 ** when sending messages.
2865 ** By default, this is the GECOS field from \fT/etc/passwd\fP.
2868 ** variable will \fInot\fP be used when the user has set a real name
2869 ** in the $$from variable.
2871 {"recall", DT_QUAD, R_NONE, OPT_RECALL, M_ASKYES},
2874 ** Controls whether or not Mutt-ng recalls postponed messages
2875 ** when composing a new message. Also see ``$$postponed''.
2877 ** Setting this variable to \fIyes\fP is not generally useful, and thus not
2880 {"record", DT_PATH, R_NONE, UL &Outbox, UL ""},
2883 ** This specifies the file into which your outgoing messages should be
2884 ** appended. (This is meant as the primary method for saving a copy of
2885 ** your messages, but another way to do this is using the ``$my_hdr''
2886 ** command to create a \fTBcc:\fP header field with your email address in it.)
2888 ** The value of \fI$$record\fP is overridden by the ``$$force_name'' and
2889 ** ``$$save_name'' variables, and the ``$fcc-hook'' command.
2891 {"reply_regexp", DT_RX, R_INDEX|R_RESORT, UL &ReplyRegexp, UL "^(re([\\[0-9\\]+])*|aw):[ \t]*"},
2894 ** A regular expression used to recognize reply messages when threading
2895 ** and replying. The default value corresponds to the English ``Re:'' and
2896 ** the German ``Aw:''.
2898 {"reply_self", DT_BOOL, R_NONE, OPTREPLYSELF, 0},
2901 ** If \fIunset\fP and you are replying to a message sent by you, Mutt-ng will
2902 ** assume that you want to reply to the recipients of that message rather
2903 ** than to yourself.
2905 {"reply_to", DT_QUAD, R_NONE, OPT_REPLYTO, M_ASKYES},
2908 ** If \fIset\fP, when replying to a message, Mutt-ng will use the address listed
2909 ** in the ``\fTReply-To:\fP'' header field as the recipient of the reply. If \fIunset\fP,
2910 ** it will use the address in the ``\fTFrom:\fP'' header field instead.
2913 ** option is useful for reading a mailing list that sets the ``\fTReply-To:\fP''
2914 ** header field to the list address and you want to send a private
2915 ** message to the author of a message.
2917 {"resolve", DT_BOOL, R_NONE, OPTRESOLVE, 1},
2920 ** When set, the cursor will be automatically advanced to the next
2921 ** (possibly undeleted) message whenever a command that modifies the
2922 ** current message is executed.
2924 {"reverse_alias", DT_BOOL, R_BOTH, OPTREVALIAS, 0},
2927 ** This variable controls whether or not Mutt-ng will display the ``personal''
2928 ** name from your aliases in the index menu if it finds an alias that
2929 ** matches the message's sender. For example, if you have the following
2932 ** \fTalias juser abd30425@somewhere.net (Joe User)\fP
2934 ** and then you receive mail which contains the following header:
2936 ** \fTFrom: abd30425@somewhere.net\fP
2938 ** It would be displayed in the index menu as ``Joe User'' instead of
2939 ** ``abd30425@somewhere.net.'' This is useful when the person's e-mail
2940 ** address is not human friendly (like CompuServe addresses).
2942 {"reverse_name", DT_BOOL, R_BOTH, OPTREVNAME, 0},
2945 ** It may sometimes arrive that you receive mail to a certain machine,
2946 ** move the messages to another machine, and reply to some the messages
2947 ** from there. If this variable is \fIset\fP, the default \fTFrom:\fP line of
2948 ** the reply messages is built using the address where you received the
2949 ** messages you are replying to \fBif\fP that address matches your
2950 ** alternates. If the variable is \fIunset\fP, or the address that would be
2951 ** used doesn't match your alternates, the \fTFrom:\fP line will use
2952 ** your address on the current machine.
2954 {"reverse_realname", DT_BOOL, R_BOTH, OPTREVREAL, 1},
2957 ** This variable fine-tunes the behaviour of the $reverse_name feature.
2958 ** When it is \fIset\fP, Mutt-ng will use the address from incoming messages as-is,
2959 ** possibly including eventual real names. When it is \fIunset\fP, Mutt-ng will
2960 ** override any such real names with the setting of the $realname variable.
2962 {"rfc2047_parameters", DT_BOOL, R_NONE, OPTRFC2047PARAMS, 0},
2965 ** When this variable is \fIset\fP, Mutt-ng will decode RFC-2047-encoded MIME
2966 ** parameters. You want to set this variable when Mutt-ng suggests you
2967 ** to save attachments to files named like this:
2969 ** \fT=?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=\fP
2971 ** When this variable is \fIset\fP interactively, the change doesn't have
2972 ** the desired effect before you have changed folders.
2974 ** Note that this use of RFC 2047's encoding is explicitly,
2975 ** prohibited by the standard, but nevertheless encountered in the
2978 ** Also note that setting this parameter will \fInot\fP have the effect
2979 ** that Mutt-ng \fIgenerates\fP this kind of encoding. Instead, Mutt-ng will
2980 ** unconditionally use the encoding specified in RFC 2231.
2982 {"save_address", DT_BOOL, R_NONE, OPTSAVEADDRESS, 0},
2985 ** If \fIset\fP, Mutt-ng will take the sender's full address when choosing a
2986 ** default folder for saving a mail. If ``$$save_name'' or ``$$force_name''
2987 ** is \fIset\fP too, the selection of the fcc folder will be changed as well.
2989 {"save_empty", DT_BOOL, R_NONE, OPTSAVEEMPTY, 1},
2992 ** When \fIunset\fP, mailboxes which contain no saved messages will be removed
2993 ** when closed (the exception is ``$$spoolfile'' which is never removed).
2994 ** If \fIset\fP, mailboxes are never removed.
2996 ** \fBNote:\fP This only applies to mbox and MMDF folders, Mutt-ng does not
2997 ** delete MH and Maildir directories.
2999 {"save_name", DT_BOOL, R_NONE, OPTSAVENAME, 0},
3002 ** This variable controls how copies of outgoing messages are saved.
3003 ** When set, a check is made to see if a mailbox specified by the
3004 ** recipient address exists (this is done by searching for a mailbox in
3005 ** the ``$$folder'' directory with the \fIusername\fP part of the
3006 ** recipient address). If the mailbox exists, the outgoing message will
3007 ** be saved to that mailbox, otherwise the message is saved to the
3008 ** ``$$record'' mailbox.
3010 ** Also see the ``$$force_name'' variable.
3012 {"score", DT_BOOL, R_NONE, OPTSCORE, 1},
3015 ** When this variable is \fIunset\fP, scoring is turned off. This can
3016 ** be useful to selectively disable scoring for certain folders when the
3017 ** ``$$score_threshold_delete'' variable and friends are used.
3020 {"score_threshold_delete", DT_NUM, R_NONE, UL &ScoreThresholdDelete, UL -1},
3023 ** Messages which have been assigned a score equal to or lower than the value
3024 ** of this variable are automatically marked for deletion by Mutt-ng. Since
3025 ** Mutt-ng scores are always greater than or equal to zero, the default setting
3026 ** of this variable will never mark a message for deletion.
3028 {"score_threshold_flag", DT_NUM, R_NONE, UL &ScoreThresholdFlag, 9999},
3031 ** Messages which have been assigned a score greater than or equal to this
3032 ** variable's value are automatically marked ``flagged''.
3034 {"score_threshold_read", DT_NUM, R_NONE, UL &ScoreThresholdRead, UL -1},
3037 ** Messages which have been assigned a score equal to or lower than the value
3038 ** of this variable are automatically marked as read by Mutt-ng. Since
3039 ** Mutt-ng scores are always greater than or equal to zero, the default setting
3040 ** of this variable will never mark a message read.
3042 {"send_charset", DT_STR, R_NONE, UL &SendCharset, UL "us-ascii:iso-8859-1:utf-8"},
3045 ** A list of character sets for outgoing messages. Mutt-ng will use the
3046 ** first character set into which the text can be converted exactly.
3047 ** If your ``$$charset'' is not \fTiso-8859-1\fP and recipients may not
3048 ** understand \fTUTF-8\fP, it is advisable to include in the list an
3049 ** appropriate widely used standard character set (such as
3050 ** \fTiso-8859-2\fP, \fTkoi8-r\fP or \fTiso-2022-jp\fP) either
3051 ** instead of or after \fTiso-8859-1\fP.
3053 {"sendmail", DT_PATH, R_NONE, UL &Sendmail, UL SENDMAIL " -oem -oi"},
3056 ** Specifies the program and arguments used to deliver mail sent by Mutt-ng.
3057 ** Mutt-ng expects that the specified program interprets additional
3058 ** arguments as recipient addresses.
3060 {"sendmail_wait", DT_NUM, R_NONE, UL &SendmailWait, 0},
3063 ** Specifies the number of seconds to wait for the ``$$sendmail'' process
3064 ** to finish before giving up and putting delivery in the background.
3066 ** Mutt-ng interprets the value of this variable as follows:
3068 ** .dt >0 .dd number of seconds to wait for sendmail to finish before continuing
3069 ** .dt 0 .dd wait forever for sendmail to finish
3070 ** .dt <0 .dd always put sendmail in the background without waiting
3073 ** Note that if you specify a value other than 0, the output of the child
3074 ** process will be put in a temporary file. If there is some error, you
3075 ** will be informed as to where to find the output.
3077 {"shell", DT_PATH, R_NONE, UL &Shell, 0},
3080 ** Command to use when spawning a subshell. By default, the user's login
3081 ** shell from \fT/etc/passwd\fP is used.
3084 {"save_unsubscribed", DT_SYN, R_NONE, UL "nntp_save_unsubscribed", 0 },
3085 {"nntp_save_unsubscribed", DT_BOOL, R_NONE, OPTSAVEUNSUB, 0},
3088 ** Availability: NNTP
3091 ** When \fIset\fP, info about unsubscribed newsgroups will be saved into the
3092 ** ``newsrc'' file and into the news cache.
3096 {"show_new_news", DT_SYN, R_NONE, UL "nntp_show_new_news", 0 },
3097 {"nntp_show_new_news", DT_BOOL, R_NONE, OPTSHOWNEWNEWS, 1},
3100 ** Availability: NNTP
3103 ** If \fIset\fP, the newsserver will be asked for new newsgroups on entering
3104 ** the browser. Otherwise, it will be done only once for a newsserver.
3105 ** Also controls whether or not the number of new articles of subscribed
3106 ** newsgroups will be checked.
3108 {"show_only_unread", DT_SYN, R_NONE, UL "nntp_show_only_unread", 0 },
3109 {"nntp_show_only_unread", DT_BOOL, R_NONE, OPTSHOWONLYUNREAD, 0},
3112 ** Availability: NNTP
3115 ** If \fIset\fP, only subscribed newsgroups that contain unread articles
3116 ** will be displayed in the newsgroup browser.
3119 {"sig_dashes", DT_BOOL, R_NONE, OPTSIGDASHES, 1},
3122 ** If set, a line containing ``\fT-- \fP'' (dash, dash, space)
3123 ** will be inserted before your ``$$signature''. It is \fBstrongly\fP
3124 ** recommended that you not unset this variable unless your ``signature''
3125 ** contains just your name. The reason for this is because many software
3126 ** packages use ``\fT-- \n\fP'' to detect your signature.
3128 ** For example, Mutt-ng has the ability to highlight
3129 ** the signature in a different color in the builtin pager.
3131 {"sig_on_top", DT_BOOL, R_NONE, OPTSIGONTOP, 0},
3134 ** If \fIset\fP, the signature will be included before any quoted or forwarded
3135 ** text. It is \fBstrongly\fP recommended that you do not set this variable
3136 ** unless you really know what you are doing, and are prepared to take
3137 ** some heat from netiquette guardians.
3139 {"signature", DT_PATH, R_NONE, UL &Signature, UL "~/.signature"},
3142 ** Specifies the filename of your signature, which is appended to all
3143 ** outgoing messages. If the filename ends with a pipe (``\fT|\fP''), it is
3144 ** assumed that filename is a shell command and input should be read from
3147 {"signoff_string", DT_STR, R_NONE, UL &SignOffString, UL 0},
3150 ** If \fIset\fP, this string will be inserted before the signature. This is useful
3151 ** for people that want to sign off every message they send with their name.
3153 ** If you want to insert your website's URL, additional contact information or
3154 ** witty quotes into your mails, better use a signature file instead of
3155 ** the signoff string.
3157 {"simple_search", DT_STR, R_NONE, UL &SimpleSearch, UL "~f %s | ~s %s"},
3160 ** Specifies how Mutt-ng should expand a simple search into a real search
3161 ** pattern. A simple search is one that does not contain any of the ~
3162 ** operators. See ``$patterns'' for more information on search patterns.
3164 ** For example, if you simply type ``joe'' at a search or limit prompt, Mutt-ng
3165 ** will automatically expand it to the value specified by this variable.
3166 ** For the default value it would be:
3168 ** \fT~f joe | ~s joe\fP
3170 {"smart_wrap", DT_BOOL, R_PAGER, OPTWRAP, 1},
3173 ** Controls the display of lines longer than the screen width in the
3174 ** internal pager. If \fIset\fP, long lines are wrapped at a word boundary.
3175 ** If \fIunset\fP, lines are simply wrapped at the screen edge. Also see the
3176 ** ``$$markers'' variable.
3178 {"smileys", DT_RX, R_PAGER, UL &Smileys, UL "(>From )|(:[-^]?[][)(><}{|/DP])"},
3181 ** The \fIpager\fP uses this variable to catch some common false
3182 ** positives of ``$$quote_regexp'', most notably smileys in the beginning
3185 {"sleep_time", DT_NUM, R_NONE, UL &SleepTime, 1},
3188 ** Specifies time, in seconds, to pause while displaying certain informational
3189 ** messages, while moving from folder to folder and after expunging
3190 ** messages from the current folder. The default is to pause one second, so
3191 ** a value of zero for this option suppresses the pause.
3193 {"sort", DT_SORT, R_INDEX|R_RESORT, UL &Sort, SORT_DATE},
3196 ** Specifies how to sort messages in the \fIindex\fP menu. Valid values
3200 ** . date or date-sent
3203 ** . mailbox-order (unsorted)
3212 ** You may optionally use the ``reverse-'' prefix to specify reverse sorting
3213 ** order (example: \fTset sort=reverse-date-sent\fP).
3215 {"sort_alias", DT_SORT|DT_SORT_ALIAS, R_NONE, UL &SortAlias, SORT_ALIAS},
3218 ** Specifies how the entries in the ``alias'' menu are sorted. The
3219 ** following are legal values:
3222 ** . address (sort alphabetically by email address)
3223 ** . alias (sort alphabetically by alias name)
3224 ** . unsorted (leave in order specified in .muttrc)
3227 {"sort_aux", DT_SORT|DT_SORT_AUX, R_INDEX|R_RESORT_BOTH, UL &SortAux, SORT_DATE},
3230 ** When sorting by threads, this variable controls how threads are sorted
3231 ** in relation to other threads, and how the branches of the thread trees
3232 ** are sorted. This can be set to any value that ``$$sort'' can, except
3233 ** threads (in that case, Mutt-ng will just use date-sent). You can also
3234 ** specify the ``last-'' prefix in addition to ``reverse-'' prefix, but last-
3235 ** must come after reverse-. The last- prefix causes messages to be
3236 ** sorted against its siblings by which has the last descendant, using
3237 ** the rest of sort_aux as an ordering.
3239 ** For instance, \fTset sort_aux=last-date-received\fP would mean that if
3240 ** a new message is received in a thread, that thread becomes the last one
3241 ** displayed (or the first, if you have \fTset sort=reverse-threads\fP.)
3243 ** \fBNote:\fP For reversed ``$$sort'' order $$sort_aux is reversed again
3244 ** (which is not the right thing to do, but kept to not break any existing
3245 ** configuration setting).
3247 {"sort_browser", DT_SORT|DT_SORT_BROWSER, R_NONE, UL &BrowserSort, SORT_ALPHA},
3250 ** Specifies how to sort entries in the file browser. By default, the
3251 ** entries are sorted alphabetically. Valid values:
3254 ** . alpha (alphabetically)
3260 ** You may optionally use the ``reverse-'' prefix to specify reverse sorting
3261 ** order (example: \fTset sort_browser=reverse-date\fP).
3263 {"sort_re", DT_BOOL, R_INDEX|R_RESORT|R_RESORT_INIT, OPTSORTRE, 1},
3266 ** This variable is only useful when sorting by threads with
3267 ** ``$$strict_threads'' \fIunset\fP. In that case, it changes the heuristic
3268 ** Mutt-ng uses to thread messages by subject. With $$sort_re \fIset\fP,
3269 ** Mutt-ng will only attach a message as the child of another message by
3270 ** subject if the subject of the child message starts with a substring
3271 ** matching the setting of ``$$reply_regexp''. With $$sort_re \fIunset\fP,
3272 ** Mutt-ng will attach the message whether or not this is the case,
3273 ** as long as the non-``$$reply_regexp'' parts of both messages are identical.
3275 {"spam_separator", DT_STR, R_NONE, UL &SpamSep, UL ","},
3278 ** ``$spam_separator'' controls what happens when multiple spam headers
3279 ** are matched: if \fIunset\fP, each successive header will overwrite any
3280 ** previous matches value for the spam label. If \fIset\fP, each successive
3281 ** match will append to the previous, using ``$spam_separator'' as a
3284 {"spoolfile", DT_PATH, R_NONE, UL &Spoolfile, 0},
3287 ** If your spool mailbox is in a non-default place where Mutt-ng cannot find
3288 ** it, you can specify its location with this variable. Mutt-ng will
3289 ** automatically set this variable to the value of the environment
3290 ** variable $$$MAIL if it is not set.
3292 {"status_chars", DT_STR, R_BOTH, UL &StChars, UL "-*%A"},
3295 ** Controls the characters used by the ``\fT%r\fP'' indicator in
3296 ** ``$$status_format''. The first character is used when the mailbox is
3297 ** unchanged. The second is used when the mailbox has been changed, and
3298 ** it needs to be resynchronized. The third is used if the mailbox is in
3299 ** read-only mode, or if the mailbox will not be written when exiting
3300 ** that mailbox (You can toggle whether to write changes to a mailbox
3301 ** with the toggle-write operation, bound by default to ``\fT%\fP'').
3302 ** The fourth is used to indicate that the current folder has been
3303 ** opened in attach-message mode (Certain operations like composing
3304 ** a new mail, replying, forwarding, etc. are not permitted in this mode).
3306 {"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)---"},
3309 ** Controls the format of the status line displayed in the \fIindex\fP
3310 ** menu. This string is similar to ``$$index_format'', but has its own
3311 ** set of \fTprintf(3)\fP-like sequences:
3314 ** .dt %b .dd number of mailboxes with new mail *
3315 ** .dt %B .dd the short pathname of the current mailbox
3316 ** .dt %d .dd number of deleted messages *
3317 ** .dt %f .dd the full pathname of the current mailbox
3318 ** .dt %F .dd number of flagged messages *
3319 ** .dt %h .dd local hostname
3320 ** .dt %l .dd size (in bytes) of the current mailbox *
3321 ** .dt %L .dd size (in bytes) of the messages shown
3322 ** (i.e., which match the current limit) *
3323 ** .dt %m .dd the number of messages in the mailbox *
3324 ** .dt %M .dd the number of messages shown (i.e., which match the current limit) *
3325 ** .dt %n .dd number of new messages in the mailbox *
3326 ** .dt %o .dd number of old unread messages *
3327 ** .dt %p .dd number of postponed messages *
3328 ** .dt %P .dd percentage of the way through the index
3329 ** .dt %r .dd modified/read-only/won't-write/attach-message indicator,
3330 ** according to $$status_chars
3331 ** .dt %s .dd current sorting mode ($$sort)
3332 ** .dt %S .dd current aux sorting method ($$sort_aux)
3333 ** .dt %t .dd number of tagged messages *
3334 ** .dt %u .dd number of unread messages *
3335 ** .dt %v .dd Mutt-ng version string
3336 ** .dt %V .dd currently active limit pattern, if any *
3337 ** .dt %>X .dd right justify the rest of the string and pad with "X"
3338 ** .dt %|X .dd pad to the end of the line with "X"
3341 ** * = can be optionally printed if nonzero
3343 ** Some of the above sequences can be used to optionally print a string
3344 ** if their value is nonzero. For example, you may only want to see the
3345 ** number of flagged messages if such messages exist, since zero is not
3346 ** particularly meaningful. To optionally print a string based upon one
3347 ** of the above sequences, the following construct is used
3349 ** \fT%?<sequence_char>?<optional_string>?\fP
3351 ** where \fIsequence_char\fP is a character from the table above, and
3352 ** \fIoptional_string\fP is the string you would like printed if
3353 ** \fIsequence_char\fP is nonzero. \fIoptional_string\fP \fBmay\fP contain
3354 ** other sequences as well as normal text, but you may \fBnot\fP nest
3355 ** optional strings.
3357 ** Here is an example illustrating how to optionally print the number of
3358 ** new messages in a mailbox:
3360 ** \fT%?n?%n new messages.?\fP
3362 ** Additionally you can switch between two strings, the first one, if a
3363 ** value is zero, the second one, if the value is nonzero, by using the
3364 ** following construct:
3366 ** \fT%?<sequence_char>?<if_string>&<else_string>?\fP
3368 ** You can additionally force the result of any \fTprintf(3)\fP-like sequence
3369 ** to be lowercase by prefixing the sequence character with an underscore
3370 ** (\fT_\fP) sign. For example, if you want to display the local hostname in
3371 ** lowercase, you would use:
3375 ** If you prefix the sequence character with a colon (\fT:\fP) character, Mutt-ng
3376 ** will replace any dots in the expansion by underscores. This might be helpful
3377 ** with IMAP folders that don't like dots in folder names.
3379 {"status_on_top", DT_BOOL, R_BOTH, OPTSTATUSONTOP, 0},
3382 ** Setting this variable causes the ``status bar'' to be displayed on
3383 ** the first line of the screen rather than near the bottom.
3385 {"strict_mailto", DT_BOOL, R_NONE, OPTSTRICTMAILTO, 1},
3389 ** With mailto: style links, a body as well as arbitrary header information
3390 ** may be embedded. This may lead to (user) headers being overwriten without note
3391 ** if ``$$edit_headers'' is unset.
3394 ** If this variable is \fIset\fP, mutt-ng is strict and allows anything to be
3395 ** changed. If it's \fIunset\fP, all headers given will be prefixed with
3396 ** ``X-Mailto-'' and the message including headers will be shown in the editor
3397 ** regardless of what ``$$edit_headers'' is set to.
3399 {"strict_mime", DT_BOOL, R_NONE, OPTSTRICTMIME, 1},
3402 ** When \fIunset\fP, non MIME-compliant messages that doesn't have any
3403 ** charset indication in the ``\fTContent-Type:\fP'' header field can
3404 ** be displayed (non MIME-compliant messages are often generated by old
3405 ** mailers or buggy mailers like MS Outlook Express).
3406 ** See also $$assumed_charset.
3408 ** This option also replaces linear-white-space between encoded-word
3409 ** and *text to a single space to prevent the display of MIME-encoded
3410 ** ``\fTSubject:\fP'' header field from being devided into multiple lines.
3412 {"strict_threads", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTSTRICTTHREADS, 0},
3415 ** If \fIset\fP, threading will only make use of the ``\fTIn-Reply-To:\fP'' and
3416 ** ``\fTReferences:\fP'' header fields when you ``$$sort'' by message threads. By
3417 ** default, messages with the same subject are grouped together in
3418 ** ``pseudo threads.'' This may not always be desirable, such as in a
3419 ** personal mailbox where you might have several unrelated messages with
3420 ** the subject ``hi'' which will get grouped together.
3422 {"strip_was", DT_BOOL, R_NONE, OPTSTRIPWAS, 0},
3425 ** When \fIset\fP, mutt-ng will remove the trailing part of the ``\fTSubject:\fP''
3426 ** line which matches $$strip_was_regex when replying. This is useful to
3427 ** properly react on subject changes and reduce ``subject noise.'' (esp. in Usenet)
3429 {"strip_was_regex", DT_RX, R_NONE, UL &StripWasRegexp, UL "\\([Ww][Aa][RrSs]: .*\\)[ ]*$"},
3432 ** When non-empty and $$strip_was is \fIset\fP, mutt-ng will remove this
3433 ** trailing part of the ``Subject'' line when replying if it won't be empty
3436 {"stuff_quoted", DT_BOOL, R_BOTH, OPTSTUFFQUOTED, 0},
3439 ** If \fIset\fP, attachments with flowed format will have their quoting ``stuffed'',
3440 ** i.e. a space will be inserted between the quote characters and the actual
3443 {"suspend", DT_BOOL, R_NONE, OPTSUSPEND, 1},
3446 ** When \fIunset\fP, Mutt-ng won't stop when the user presses the terminal's
3447 ** \fIsusp\fP key, usually \fTCTRL+Z\fP. This is useful if you run Mutt-ng
3448 ** inside an xterm using a command like ``\fTxterm -e muttng\fP.''
3450 {"text_flowed", DT_BOOL, R_NONE, OPTTEXTFLOWED, 0},
3453 ** When \fIset\fP, Mutt-ng will generate \fTtext/plain; format=flowed\fP attachments.
3454 ** This format is easier to handle for some mailing software, and generally
3455 ** just looks like ordinary text. To actually make use of this format's
3456 ** features, you'll need support in your editor.
3458 ** Note that $$indent_string is ignored when this option is set.
3460 {"thread_received", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTTHREADRECEIVED, 0},
3463 ** When \fIset\fP, Mutt-ng uses the date received rather than the date sent
3464 ** to thread messages by subject.
3466 {"thorough_search", DT_BOOL, R_NONE, OPTTHOROUGHSRC, 0},
3469 ** Affects the \fT~b\fP and \fT~h\fP search operations described in
3470 ** section ``$patterns'' above. If \fIset\fP, the headers and attachments of
3471 ** messages to be searched are decoded before searching. If \fIunset\fP,
3472 ** messages are searched as they appear in the folder.
3474 {"tilde", DT_BOOL, R_PAGER, OPTTILDE, 0},
3477 ** When \fIset\fP, the internal-pager will pad blank lines to the bottom of the
3478 ** screen with a tilde (~).
3480 {"timeout", DT_NUM, R_NONE, UL &Timeout, 600},
3483 ** This variable controls the \fInumber of seconds\fP Mutt-ng will wait
3484 ** for a key to be pressed in the main menu before timing out and
3485 ** checking for new mail. A value of zero or less will cause Mutt-ng
3486 ** to never time out.
3488 {"tmpdir", DT_PATH, R_NONE, UL &Tempdir, 0},
3491 ** This variable allows you to specify where Mutt-ng will place its
3492 ** temporary files needed for displaying and composing messages. If
3493 ** this variable is not set, the environment variable \fT$$$TMPDIR\fP is
3494 ** used. If \fT$$$TMPDIR\fP is not set then "\fT/tmp\fP" is used.
3496 {"to_chars", DT_STR, R_BOTH, UL &Tochars, UL " +TCFL"},
3499 ** Controls the character used to indicate mail addressed to you. The
3500 ** first character is the one used when the mail is NOT addressed to your
3501 ** address (default: space). The second is used when you are the only
3502 ** recipient of the message (default: +). The third is when your address
3503 ** appears in the ``\fTTo:\fP'' header field, but you are not the only recipient of
3504 ** the message (default: T). The fourth character is used when your
3505 ** address is specified in the ``\fTCc:\fP'' header field, but you are not the only
3506 ** recipient. The fifth character is used to indicate mail that was sent
3507 ** by \fIyou\fP. The sixth character is used to indicate when a mail
3508 ** was sent to a mailing-list you're subscribe to (default: L).
3510 {"trash", DT_PATH, R_NONE, UL &TrashPath, 0},
3513 ** If \fIset\fP, this variable specifies the path of the trash folder where the
3514 ** mails marked for deletion will be moved, instead of being irremediably
3517 ** \fBNote\fP: When you delete a message in the trash folder, it is really
3518 ** deleted, so that there is no way to recover mail.
3521 {"tunnel", DT_STR, R_NONE, UL &Tunnel, UL 0},
3524 ** Setting this variable will cause Mutt-ng to open a pipe to a command
3525 ** instead of a raw socket. You may be able to use this to set up
3526 ** preauthenticated connections to your IMAP/POP3 server. Example:
3528 ** \fTtunnel="ssh -q mailhost.net /usr/local/libexec/imapd"\fP
3530 ** \fBNote:\fP For this example to work you must be able to log in to the remote
3531 ** machine without having to enter a password.
3534 {"umask", DT_NUM, R_NONE, UL &Umask, 0077},
3537 ** This sets the umask that will be used by Mutt-ng when creating all
3538 ** kinds of files. If \fIunset\fP, the default value is \fT077\fP.
3540 {"use_8bitmime", DT_BOOL, R_NONE, OPTUSE8BITMIME, 0},
3543 ** \fBWarning:\fP do not set this variable unless you are using a version
3544 ** of sendmail which supports the \fT-B8BITMIME\fP flag (such as sendmail
3545 ** 8.8.x) or in connection with the SMTP support via libESMTP.
3546 ** Otherwise you may not be able to send mail.
3548 ** When \fIset\fP, Mutt-ng will either invoke ``$$sendmail'' with the \fT-B8BITMIME\fP
3549 ** flag when sending 8-bit messages to enable ESMTP negotiation or tell
3550 ** libESMTP to do so.
3552 {"use_domain", DT_BOOL, R_NONE, OPTUSEDOMAIN, 1},
3555 ** When \fIset\fP, Mutt-ng will qualify all local addresses (ones without the
3556 ** @host portion) with the value of ``$$hostname''. If \fIunset\fP, no
3557 ** addresses will be qualified.
3559 {"use_from", DT_BOOL, R_NONE, OPTUSEFROM, 1},
3562 ** When \fIset\fP, Mutt-ng will generate the ``\fTFrom:\fP'' header field when
3563 ** sending messages. If \fIunset\fP, no ``\fTFrom:\fP'' header field will be
3564 ** generated unless the user explicitly sets one using the ``$my_hdr''
3568 {"use_idn", DT_BOOL, R_BOTH, OPTUSEIDN, 1},
3571 ** Availability: IDN
3574 ** When \fIset\fP, Mutt-ng will show you international domain names decoded.
3576 ** \fBNote:\fP You can use IDNs for addresses even if this is \fIunset\fP.
3577 ** This variable only affects decoding.
3579 #endif /* HAVE_LIBIDN */
3580 #ifdef HAVE_GETADDRINFO
3581 {"use_ipv6", DT_BOOL, R_NONE, OPTUSEIPV6, 1},
3584 ** When \fIset\fP, Mutt-ng will look for IPv6 addresses of hosts it tries to
3585 ** contact. If this option is \fIunset\fP, Mutt-ng will restrict itself to IPv4 addresses.
3586 ** Normally, the default should work.
3588 #endif /* HAVE_GETADDRINFO */
3589 {"user_agent", DT_BOOL, R_NONE, OPTXMAILER, 1},
3592 ** When \fIset\fP, Mutt-ng will add a ``\fTUser-Agent:\fP'' header to outgoing
3593 ** messages, indicating which version of Mutt-ng was used for composing
3596 {"visual", DT_PATH, R_NONE, UL &Visual, 0},
3599 ** Specifies the visual editor to invoke when the \fI~v\fP command is
3600 ** given in the builtin editor.
3602 {"wait_key", DT_BOOL, R_NONE, OPTWAITKEY, 1},
3605 ** Controls whether Mutt-ng will ask you to press a key after \fIshell-
3606 ** escape\fP, \fIpipe-message\fP, \fIpipe-entry\fP, \fIprint-message\fP,
3607 ** and \fIprint-entry\fP commands.
3609 ** It is also used when viewing attachments with ``$auto_view'', provided
3610 ** that the corresponding mailcap entry has a \fTneedsterminal\fP flag,
3611 ** and the external program is interactive.
3613 ** When \fIset\fP, Mutt-ng will always ask for a key. When \fIunset\fP, Mutt-ng will wait
3614 ** for a key only if the external command returned a non-zero status.
3616 {"weed", DT_BOOL, R_NONE, OPTWEED, 1},
3619 ** When \fIset\fP, Mutt-ng will weed headers when displaying, forwarding,
3620 ** printing, or replying to messages.
3622 {"wrap_search", DT_BOOL, R_NONE, OPTWRAPSEARCH, 1},
3625 ** Controls whether searches wrap around the end of the mailbox.
3627 ** When \fIset\fP, searches will wrap around the first (or last) message. When
3628 ** \fIunset\fP, searches will not wrap.
3630 {"wrapmargin", DT_NUM, R_PAGER, UL &WrapMargin, 0},
3633 ** Controls the size of the margin remaining at the right side of
3634 ** the terminal when Mutt-ng's pager does smart wrapping.
3636 {"write_inc", DT_NUM, R_NONE, UL &WriteInc, 10},
3639 ** When writing a mailbox, a message will be printed every
3640 ** \fIwrite_inc\fP messages to indicate progress. If set to 0, only a
3641 ** single message will be displayed before writing a mailbox.
3643 ** Also see the ``$$read_inc'' variable.
3645 {"write_bcc", DT_BOOL, R_NONE, OPTWRITEBCC, 1},
3648 ** Controls whether Mutt-ng writes out the Bcc header when preparing
3649 ** messages to be sent. Exim users may wish to \fIunset\fP this.
3651 {"xterm_icon", DT_STR, R_BOTH, UL &XtermIcon, UL "M%?n?AIL&ail?"},
3654 ** Controls the format of the X11 icon title, as long as $$xterm_set_titles
3655 ** is \fIset\fP. This string is identical in formatting to the one used by
3656 ** ``$$status_format''.
3658 {"xterm_set_titles", DT_BOOL, R_BOTH, OPTXTERMSETTITLES, 0},
3661 ** Controls whether Mutt-ng sets the xterm title bar and icon name
3662 ** (as long as you're in an appropriate terminal). The default must
3663 ** be \fIunset\fP to force in the validity checking.
3665 {"xterm_leave", DT_STR, R_BOTH, UL &XtermLeave, UL "" },
3668 ** If $$xterm_set_titles is \fIset\fP, this string will be used to
3669 ** set the title when leaving mutt-ng. For terminal-based programs,
3670 ** there's no easy and portable way to read the current title so mutt-ng
3671 ** cannot read it upon startup and restore it when exiting.
3674 ** Based on the xterm FAQ, the following might work:
3677 ** \fTset xterm_leave = "`test x$$$DISPLAY != x && xprop -id $$$WINDOWID | grep WM_NAME | cut -d '"' -f 2`"\fP
3679 {"xterm_title", DT_STR, R_BOTH, UL &XtermTitle, UL "Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?"},
3682 ** Controls the format of the title bar of the xterm provided that
3683 ** $$xterm_set_titles has been \fIset\fP. This string is identical in formatting
3684 ** to the one used by ``$$status_format''.
3687 {"x_comment_to", DT_SYN, R_NONE, UL "nntp_x_comment_to", 0},
3688 {"nntp_x_comment_to", DT_BOOL, R_NONE, OPTXCOMMENTTO, 0},
3691 ** Availability: NNTP
3694 ** If \fIset\fP, Mutt-ng will add a ``\fTX-Comment-To:\fP'' header field
3695 ** (that contains full name of the original article author) to articles that
3703 const struct feature_t Features[] = {
3705 #ifdef NCURSES_VERSION
3711 #ifdef USE_SLANG_CURSES
3717 #ifdef _LIBICONV_VERSION
3735 #ifdef DL_STANDALONE
3789 #ifdef USE_COMPRESSED
3801 #ifdef CRYPT_BACKEND_CLASSIC_PGP
3806 }, {"classic_smime",
3807 #ifdef CRYPT_BACKEND_CLASSIC_SMIME
3813 #ifdef CRYPT_BACKEND_GPGME
3847 const struct mapping_t SortMethods[] = {
3848 {"date", SORT_DATE},
3849 {"date-sent", SORT_DATE},
3850 {"date-received", SORT_RECEIVED},
3851 {"mailbox-order", SORT_ORDER},
3852 {"subject", SORT_SUBJECT},
3853 {"from", SORT_FROM},
3854 {"size", SORT_SIZE},
3855 {"threads", SORT_THREADS},
3857 {"score", SORT_SCORE},
3858 {"spam", SORT_SPAM},
3862 /* same as SortMethods, but with "threads" replaced by "date" */
3864 const struct mapping_t SortAuxMethods[] = {
3865 {"date", SORT_DATE},
3866 {"date-sent", SORT_DATE},
3867 {"date-received", SORT_RECEIVED},
3868 {"mailbox-order", SORT_ORDER},
3869 {"subject", SORT_SUBJECT},
3870 {"from", SORT_FROM},
3871 {"size", SORT_SIZE},
3872 {"threads", SORT_DATE}, /* note: sort_aux == threads
3876 {"score", SORT_SCORE},
3877 {"spam", SORT_SPAM},
3882 const struct mapping_t SortBrowserMethods[] = {
3883 {"alpha", SORT_SUBJECT},
3884 {"date", SORT_DATE},
3885 {"size", SORT_SIZE},
3886 {"unsorted", SORT_ORDER},
3890 const struct mapping_t SortAliasMethods[] = {
3891 {"alias", SORT_ALIAS},
3892 {"address", SORT_ADDRESS},
3893 {"unsorted", SORT_ORDER},
3897 const struct mapping_t SortKeyMethods[] = {
3898 {"address", SORT_ADDRESS},
3899 {"date", SORT_DATE},
3900 {"keyid", SORT_KEYID},
3901 {"trust", SORT_TRUST},
3906 /* functions used to parse commands in a rc file */
3908 static int parse_list (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3909 static int parse_spam_list (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3910 static int parse_unlist (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3912 static int parse_lists (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3913 static int parse_unlists (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3914 static int parse_alias (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3915 static int parse_unalias (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3916 static int parse_ifdef (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3917 static int parse_ignore (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3918 static int parse_unignore (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3919 static int parse_source (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3920 static int parse_set (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3921 static int parse_my_hdr (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3922 static int parse_unmy_hdr (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3923 static int parse_subscribe (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3924 static int parse_unsubscribe (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3926 static int parse_alternates (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3927 static int parse_unalternates (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3931 int (*func) (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3933 unsigned long data1;
3936 struct command_t Commands[] = {
3937 {"alternates", parse_alternates, 0},
3938 {"unalternates", parse_unalternates, 0},
3940 {"account-hook", mutt_parse_hook, M_ACCOUNTHOOK},
3942 {"alias", parse_alias, 0},
3943 {"auto_view", parse_list, UL &AutoViewList},
3944 {"alternative_order", parse_list, UL &AlternativeOrderList},
3945 {"bind", mutt_parse_bind, 0},
3946 {"charset-hook", mutt_parse_hook, M_CHARSETHOOK},
3948 {"color", mutt_parse_color, 0},
3949 {"uncolor", mutt_parse_uncolor, 0},
3951 {"exec", mutt_parse_exec, 0},
3952 {"fcc-hook", mutt_parse_hook, M_FCCHOOK},
3953 {"fcc-save-hook", mutt_parse_hook, M_FCCHOOK|M_SAVEHOOK},
3954 {"folder-hook", mutt_parse_hook, M_FOLDERHOOK},
3955 #ifdef USE_COMPRESSED
3956 {"open-hook", mutt_parse_hook, M_OPENHOOK},
3957 {"close-hook", mutt_parse_hook, M_CLOSEHOOK},
3958 {"append-hook", mutt_parse_hook, M_APPENDHOOK},
3960 {"hdr_order", parse_list, UL &HeaderOrderList},
3961 {"ifdef", parse_ifdef, 1},
3962 {"ifndef", parse_ifdef, 0},
3964 {"iconv-hook", mutt_parse_hook, M_ICONVHOOK},
3966 {"ignore", parse_ignore, 0},
3967 {"lists", parse_lists, 0},
3968 {"macro", mutt_parse_macro, 0},
3969 {"mailboxes", buffy_parse_mailboxes, M_MAILBOXES},
3970 {"unmailboxes", buffy_parse_mailboxes, M_UNMAILBOXES},
3971 {"message-hook", mutt_parse_hook, M_MESSAGEHOOK},
3972 {"mbox-hook", mutt_parse_hook, M_MBOXHOOK},
3973 {"mime_lookup", parse_list, UL &MimeLookupList},
3974 {"unmime_lookup", parse_unlist, UL &MimeLookupList},
3975 {"mono", mutt_parse_mono, 0},
3976 {"my_hdr", parse_my_hdr, 0},
3977 {"pgp-hook", mutt_parse_hook, M_CRYPTHOOK},
3978 {"crypt-hook", mutt_parse_hook, M_CRYPTHOOK},
3979 {"push", mutt_parse_push, 0},
3980 {"reply-hook", mutt_parse_hook, M_REPLYHOOK},
3981 {"reset", parse_set, M_SET_RESET},
3982 {"save-hook", mutt_parse_hook, M_SAVEHOOK},
3983 {"score", mutt_parse_score, 0},
3984 {"send-hook", mutt_parse_hook, M_SENDHOOK},
3985 {"send2-hook", mutt_parse_hook, M_SEND2HOOK},
3986 {"set", parse_set, 0},
3987 {"source", parse_source, 0},
3988 {"spam", parse_spam_list, M_SPAM},
3989 {"nospam", parse_spam_list, M_NOSPAM},
3990 {"subscribe", parse_subscribe, 0},
3991 {"toggle", parse_set, M_SET_INV},
3992 {"unalias", parse_unalias, 0},
3993 {"unalternative_order", parse_unlist, UL &AlternativeOrderList},
3994 {"unauto_view", parse_unlist, UL &AutoViewList},
3995 {"unhdr_order", parse_unlist, UL &HeaderOrderList},
3996 {"unhook", mutt_parse_unhook, 0},
3997 {"unignore", parse_unignore, 0},
3998 {"unlists", parse_unlists, 0},
3999 {"unmono", mutt_parse_unmono, 0},
4000 {"unmy_hdr", parse_unmy_hdr, 0},
4001 {"unscore", mutt_parse_unscore, 0},
4002 {"unset", parse_set, M_SET_UNSET},
4003 {"unsubscribe", parse_unsubscribe, 0},