2 * Copyright notice from original mutt:
3 * Copyright (C) 1996-2002 Michael R. Elkins <me@mutt.org>
4 * Copyright (C) 2004 g10 Code GmbH
6 * Parts were writte/modified by:
7 * Nico Golde <nico@ngolde.de>
9 * This file is part of mutt-ng, see http://www.muttng.org/.
10 * It's licensed under the GNU General Public License,
11 * please see the file GPL in the top level source directory.
24 #define DT_BOOL 1 /* boolean option */
25 #define DT_NUM 2 /* a number */
26 #define DT_STR 3 /* a string */
27 #define DT_PATH 4 /* a pathname */
28 #define DT_QUAD 5 /* quad-option (yes/no/ask-yes/ask-no) */
29 #define DT_SORT 6 /* sorting methods */
30 #define DT_RX 7 /* regular expressions */
31 #define DT_MAGIC 8 /* mailbox type */
32 #define DT_SYN 9 /* synonym for another variable */
33 #define DT_ADDR 10 /* e-mail address */
35 #define DTYPE(x) ((x) & DT_MASK)
38 #define DT_SUBTYPE_MASK 0xf0
39 #define DT_SORT_ALIAS 0x10
40 #define DT_SORT_BROWSER 0x20
41 #define DT_SORT_KEYS 0x40
42 #define DT_SORT_AUX 0x80
44 /* flags to parse_set() */
45 #define M_SET_INV (1<<0) /* default is to invert all vars */
46 #define M_SET_UNSET (1<<1) /* default is to unset all vars */
47 #define M_SET_RESET (1<<2) /* default is to reset all vars to default */
49 /* forced redraw/resort types */
51 #define R_INDEX (1<<0)
52 #define R_PAGER (1<<1)
53 #define R_RESORT (1<<2) /* resort the mailbox */
54 #define R_RESORT_SUB (1<<3) /* resort subthreads */
55 #define R_RESORT_INIT (1<<4) /* resort from scratch */
56 #define R_TREE (1<<5) /* redraw the thread tree */
57 #define R_BOTH (R_INDEX|R_PAGER)
58 #define R_RESORT_BOTH (R_RESORT|R_RESORT_SUB)
65 unsigned long init; /* initial value */
73 #define UL (unsigned long)
78 #define ISPELL "ispell"
81 /* build complete documentation */
88 # define MIXMASTER "mixmaster"
100 # define USE_LIBESMTP
110 struct option_t MuttVars[] = {
112 {"abort_nosubject", DT_QUAD, R_NONE, OPT_SUBJECT, M_ASKYES},
115 ** If set to \fIyes\fP, when composing messages and no subject is given
116 ** at the subject prompt, composition will be aborted. If set to
117 ** \fIno\fP, composing messages with no subject given at the subject
118 ** prompt will never be aborted.
120 {"abort_unmodified", DT_QUAD, R_NONE, OPT_ABORT, M_YES},
123 ** If set to \fIyes\fP, composition will automatically abort after
124 ** editing the message body if no changes are made to the file (this
125 ** check only happens after the \fIfirst\fP edit of the file). When set
126 ** to \fIno\fP, composition will never be aborted.
128 {"alias_file", DT_PATH, R_NONE, UL &AliasFile, UL "~/.muttngrc"},
131 ** The default file in which to save aliases created by the
132 ** ``$create-alias'' function.
134 ** \fBNote:\fP Mutt-ng will not automatically source this file; you must
135 ** explicitly use the ``$source'' command for it to be executed.
137 {"alias_format", DT_STR, R_NONE, UL &AliasFmt, UL "%4n %2f %t %-10a %r"},
140 ** Specifies the format of the data displayed for the ``alias'' menu. The
141 ** following \fTprintf(3)\fP-style sequences are available:
144 ** .dt %a .dd alias name
145 ** .dt %f .dd flags - currently, a "d" for an alias marked for deletion
146 ** .dt %n .dd index number
147 ** .dt %r .dd address which alias expands to
148 ** .dt %t .dd character which indicates if the alias is tagged for inclusion
151 {"allow_8bit", DT_BOOL, R_NONE, OPTALLOW8BIT, 1},
154 ** Controls whether 8-bit data is converted to 7-bit using either
155 ** \fTquoted-printable\fP or \fTbase64\fP encoding when sending mail.
157 {"allow_ansi", DT_BOOL, R_NONE, OPTALLOWANSI, 0},
160 ** Controls whether ANSI color codes in messages (and color tags in
161 ** rich text messages) are to be interpreted.
162 ** Messages containing these codes are rare, but if this option is set,
163 ** their text will be colored accordingly. Note that this may override
164 ** your color choices, and even present a security problem, since a
165 ** message could include a line like ``\fT[-- PGP output follows ...\fP" and
166 ** give it the same color as your attachment color.
168 {"arrow_cursor", DT_BOOL, R_BOTH, OPTARROWCURSOR, 0},
171 ** When \fIset\fP, an arrow (``\fT->\fP'') will be used to indicate the current entry
172 ** in menus instead of highlighting the whole line. On slow network or modem
173 ** links this will make response faster because there is less that has to
174 ** be redrawn on the screen when moving to the next or previous entries
177 {"ascii_chars", DT_BOOL, R_BOTH, OPTASCIICHARS, 0},
180 ** If \fIset\fP, Mutt-ng will use plain ASCII characters when displaying thread
181 ** and attachment trees, instead of the default \fTACS\fP characters.
183 {"askbcc", DT_BOOL, R_NONE, OPTASKBCC, 0},
186 ** If \fIset\fP, Mutt-ng will prompt you for blind-carbon-copy (Bcc) recipients
187 ** before editing an outgoing message.
189 {"askcc", DT_BOOL, R_NONE, OPTASKCC, 0},
192 ** If \fIset\fP, Mutt-ng will prompt you for carbon-copy (Cc) recipients before
193 ** editing the body of an outgoing message.
195 {"assumed_charset", DT_STR, R_NONE, UL &AssumedCharset, UL "us-ascii"},
198 ** This variable is a colon-separated list of character encoding
199 ** schemes for messages without character encoding indication.
200 ** Header field values and message body content without character encoding
201 ** indication would be assumed that they are written in one of this list.
202 ** By default, all the header fields and message body without any charset
203 ** indication are assumed to be in \fTus-ascii\fP.
205 ** For example, Japanese users might prefer this:
207 ** \fTset assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"\fP
209 ** However, only the first content is valid for the message body.
210 ** This variable is valid only if $$strict_mime is unset.
213 {"ask_follow_up", DT_BOOL, R_NONE, OPTASKFOLLOWUP, 0},
216 ** Availability: NNTP
219 ** If \fIset\fP, Mutt-ng will prompt you for the \fTFollowup-To:\fP header
220 ** field before editing the body of an outgoing news article.
222 {"ask_x_comment_to", DT_BOOL, R_NONE, OPTASKXCOMMENTTO, 0},
225 ** Availability: NNTP
228 ** If \fIset\fP, Mutt-ng will prompt you for the \fTX-Comment-To:\fP header
229 ** field before editing the body of an outgoing news article.
232 {"attach_format", DT_STR, R_NONE, UL &AttachFormat, UL "%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] "},
235 ** This variable describes the format of the ``attachment'' menu. The
236 ** following \fTprintf(3)\fP-style sequences are understood:
239 ** .dt %C .dd charset
240 ** .dt %c .dd requires charset conversion (n or c)
241 ** .dt %D .dd deleted flag
242 ** .dt %d .dd description
243 ** .dt %e .dd MIME \fTContent-Transfer-Encoding:\fP header field
244 ** .dt %f .dd filename
245 ** .dt %I .dd MIME \fTContent-Disposition:\fP header field (\fTI\fP=inline, \fTA\fP=attachment)
246 ** .dt %m .dd major MIME type
247 ** .dt %M .dd MIME subtype
248 ** .dt %n .dd attachment number
250 ** .dt %t .dd tagged flag
251 ** .dt %T .dd graphic tree characters
252 ** .dt %u .dd unlink (=to delete) flag
253 ** .dt %>X .dd right justify the rest of the string and pad with character "X"
254 ** .dt %|X .dd pad to the end of the line with character "X"
257 {"attach_sep", DT_STR, R_NONE, UL &AttachSep, UL "\n"},
260 ** The separator to add between attachments when operating (saving,
261 ** printing, piping, etc) on a list of tagged attachments.
263 {"attach_split", DT_BOOL, R_NONE, OPTATTACHSPLIT, 1},
266 ** If this variable is \fIunset\fP, when operating (saving, printing, piping,
267 ** etc) on a list of tagged attachments, Mutt-ng will concatenate the
268 ** attachments and will operate on them as a single attachment. The
269 ** ``$$attach_sep'' separator is added after each attachment. When \fIset\fP,
270 ** Mutt-ng will operate on the attachments one by one.
272 {"attribution", DT_STR, R_NONE, UL &Attribution, UL "On %d, %n wrote:"},
275 ** This is the string that will precede a message which has been included
276 ** in a reply. For a full listing of defined \fTprintf(3)\fP-like sequences see
277 ** the section on ``$$index_format''.
279 {"autoedit", DT_BOOL, R_NONE, OPTAUTOEDIT, 0},
282 ** When \fIset\fP along with ``$$edit_headers'', Mutt-ng will skip the initial
283 ** send-menu and allow you to immediately begin editing the body of your
284 ** message. The send-menu may still be accessed once you have finished
285 ** editing the body of your message.
287 ** Also see ``$$fast_reply''.
289 {"auto_tag", DT_BOOL, R_NONE, OPTAUTOTAG, 0},
292 ** When \fIset\fP, functions in the \fIindex\fP menu which affect a message
293 ** will be applied to all tagged messages (if there are any). When
294 ** unset, you must first use the ``tag-prefix'' function (default: "\fT;\fP") to
295 ** make the next function apply to all tagged messages.
297 {"beep", DT_BOOL, R_NONE, OPTBEEP, 1},
300 ** When this variable is \fIset\fP, Mutt-ng will beep when an error occurs.
302 {"beep_new", DT_BOOL, R_NONE, OPTBEEPNEW, 0},
305 ** When this variable is \fIset\fP, Mutt-ng will beep whenever it prints a message
306 ** notifying you of new mail. This is independent of the setting of the
307 ** ``$$beep'' variable.
309 {"bounce", DT_QUAD, R_NONE, OPT_BOUNCE, M_ASKYES},
312 ** Controls whether you will be asked to confirm bouncing messages.
313 ** If set to \fIyes\fP you don't get asked if you want to bounce a
314 ** message. Setting this variable to \fIno\fP is not generally useful,
315 ** and thus not recommended, because you are unable to bounce messages.
317 {"bounce_delivered", DT_BOOL, R_NONE, OPTBOUNCEDELIVERED, 1},
320 ** When this variable is \fIset\fP, Mutt-ng will include
321 ** \fTDelivered-To:\fP header fields when bouncing messages.
322 ** Postfix users may wish to \fIunset\fP this variable.
324 { "braille_friendly", DT_BOOL, R_NONE, OPTBRAILLEFRIENDLY, 0 },
327 ** When this variable is set, mutt will place the cursor at the beginning
328 ** of the current line in menus, even when the arrow_cursor variable
329 ** is unset, making it easier for blind persons using Braille displays to
330 ** follow these menus. The option is disabled by default because many
331 ** visual terminals don't permit making the cursor invisible.
334 {"catchup_newsgroup", DT_QUAD, R_NONE, OPT_CATCHUP, M_ASKYES},
337 ** Availability: NNTP
340 ** If this variable is \fIset\fP, Mutt-ng will mark all articles in a newsgroup
341 ** as read when you leaving it.
344 {"charset", DT_STR, R_NONE, UL &Charset, UL 0},
347 ** Character set your terminal uses to display and enter textual data.
349 {"check_new", DT_BOOL, R_NONE, OPTCHECKNEW, 1},
352 ** \fBNote:\fP this option only affects \fImaildir\fP and \fIMH\fP style
355 ** When \fIset\fP, Mutt-ng will check for new mail delivered while the
356 ** mailbox is open. Especially with MH mailboxes, this operation can
357 ** take quite some time since it involves scanning the directory and
358 ** checking each file to see if it has already been looked at. If it's
359 ** \fIunset\fP, no check for new mail is performed while the mailbox is open.
361 {"collapse_unread", DT_BOOL, R_NONE, OPTCOLLAPSEUNREAD, 1},
364 ** When \fIunset\fP, Mutt-ng will not collapse a thread if it contains any
367 {"uncollapse_jump", DT_BOOL, R_NONE, OPTUNCOLLAPSEJUMP, 0},
370 ** When \fIset\fP, Mutt-ng will jump to the next unread message, if any,
371 ** when the current thread is \fIun\fPcollapsed.
373 {"compose_format", DT_STR, R_BOTH, UL &ComposeFormat, UL "-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-"},
376 ** Controls the format of the status line displayed in the ``compose''
377 ** menu. This string is similar to ``$$status_format'', but has its own
378 ** set of \fTprintf(3)\fP-like sequences:
381 ** .dt %a .dd total number of attachments
382 ** .dt %h .dd local hostname
383 ** .dt %l .dd approximate size (in bytes) of the current message
384 ** .dt %v .dd Mutt-ng version string
387 ** See the text describing the ``$$status_format'' option for more
388 ** information on how to set ``$$compose_format''.
390 {"config_charset", DT_STR, R_NONE, UL &ConfigCharset, UL 0},
393 ** When defined, Mutt-ng will recode commands in rc files from this
396 {"confirmappend", DT_BOOL, R_NONE, OPTCONFIRMAPPEND, 1},
399 ** When \fIset\fP, Mutt-ng will prompt for confirmation when appending messages to
400 ** an existing mailbox.
402 {"confirmcreate", DT_BOOL, R_NONE, OPTCONFIRMCREATE, 1},
405 ** When \fIset\fP, Mutt-ng will prompt for confirmation when saving messages to a
406 ** mailbox which does not yet exist before creating it.
408 {"connect_timeout", DT_NUM, R_NONE, UL &ConnectTimeout, 30},
411 ** Causes Mutt-ng to timeout a network connection (for IMAP or POP) after this
412 ** many seconds if the connection is not able to be established. A negative
413 ** value causes Mutt-ng to wait indefinitely for the connection to succeed.
415 {"content_type", DT_STR, R_NONE, UL &ContentType, UL "text/plain"},
418 ** Sets the default \fTContent-Type:\fP header field for the body
419 ** of newly composed messages.
421 {"copy", DT_QUAD, R_NONE, OPT_COPY, M_YES},
424 ** This variable controls whether or not copies of your outgoing messages
425 ** will be saved for later references. Also see ``$$record'',
426 ** ``$$save_name'', ``$$force_name'' and ``$fcc-hook''.
429 {"crypt_use_gpgme", DT_BOOL, R_NONE, OPTCRYPTUSEGPGME, 0},
432 ** This variable controls the use the GPGME enabled crypto backends.
433 ** If it is \fIset\fP and Mutt-ng was build with gpgme support, the gpgme code for
434 ** S/MIME and PGP will be used instead of the classic code.
436 ** \fBNote\fP: You need to use this option in your \fT.muttngrc\fP configuration
437 ** file as it won't have any effect when used interactively.
440 {"crypt_autopgp", DT_BOOL, R_NONE, OPTCRYPTAUTOPGP, 1},
443 ** This variable controls whether or not Mutt-ng may automatically enable
444 ** PGP encryption/signing for messages. See also ``$$crypt_autoencrypt'',
445 ** ``$$crypt_replyencrypt'',
446 ** ``$$crypt_autosign'', ``$$crypt_replysign'' and ``$$smime_is_default''.
448 {"crypt_autosmime", DT_BOOL, R_NONE, OPTCRYPTAUTOSMIME, 1},
451 ** This variable controls whether or not Mutt-ng may automatically enable
452 ** S/MIME encryption/signing for messages. See also ``$$crypt_autoencrypt'',
453 ** ``$$crypt_replyencrypt'',
454 ** ``$$crypt_autosign'', ``$$crypt_replysign'' and ``$$smime_is_default''.
456 {"date_format", DT_STR, R_BOTH, UL &DateFmt, UL "!%a, %b %d, %Y at %I:%M:%S%p %Z"},
459 ** This variable controls the format of the date printed by the ``\fT%d\fP''
460 ** sequence in ``$$index_format''. This is passed to \fTstrftime(3)\fP
461 ** to process the date.
463 ** Unless the first character in the string is a bang (``\fT!\fP''), the month
464 ** and week day names are expanded according to the locale specified in
465 ** the variable ``$$locale''. If the first character in the string is a
466 ** bang, the bang is discarded, and the month and week day names in the
467 ** rest of the string are expanded in the \fIC\fP locale (that is in US
470 {"default_hook", DT_STR, R_NONE, UL &DefaultHook, UL "~f %s !~P | (~P ~C %s)"},
473 ** This variable controls how send-hooks, message-hooks, save-hooks,
474 ** and fcc-hooks will
475 ** be interpreted if they are specified with only a simple regexp,
476 ** instead of a matching pattern. The hooks are expanded when they are
477 ** declared, so a hook will be interpreted according to the value of this
478 ** variable at the time the hook is declared. The default value matches
479 ** if the message is either from a user matching the regular expression
480 ** given, or if it is from you (if the from address matches
481 ** ``alternates'') and is to or cc'ed to a user matching the given
482 ** regular expression.
484 {"delete", DT_QUAD, R_NONE, OPT_DELETE, M_ASKYES},
487 ** Controls whether or not messages are really deleted when closing or
488 ** synchronizing a mailbox. If set to \fIyes\fP, messages marked for
489 ** deleting will automatically be purged without prompting. If set to
490 ** \fIno\fP, messages marked for deletion will be kept in the mailbox.
492 {"delete_untag", DT_BOOL, R_NONE, OPTDELETEUNTAG, 1},
495 ** If this option is \fIset\fP, Mutt-ng will untag messages when marking them
496 ** for deletion. This applies when you either explicitly delete a message,
497 ** or when you save it to another folder.
499 {"digest_collapse", DT_BOOL, R_NONE, OPTDIGESTCOLLAPSE, 1},
502 ** If this option is \fIset\fP, Mutt-ng's received-attachments menu will not show the subparts of
503 ** individual messages in a multipart/digest. To see these subparts, press 'v' on that menu.
505 {"display_filter", DT_PATH, R_PAGER, UL &DisplayFilter, UL ""},
508 ** When \fIset\fP, specifies a command used to filter messages. When a message
509 ** is viewed it is passed as standard input to $$display_filter, and the
510 ** filtered message is read from the standard output.
512 #if defined(DL_STANDALONE) && defined(USE_DOTLOCK)
513 {"dotlock_program", DT_PATH, R_NONE, UL &MuttDotlock, UL BINDIR "/muttng_dotlock"},
516 ** Availability: Standalone and Dotlock
519 ** Contains the path of the \fTmuttng_dotlock(1)\fP binary to be used by
523 {"dsn_notify", DT_STR, R_NONE, UL &DsnNotify, UL ""},
526 ** \fBNote:\fP you should not enable this unless you are using Sendmail
529 ** This variable sets the request for when notification is returned. The
530 ** string consists of a comma separated list (no spaces!) of one or more
531 ** of the following: \fInever\fP, to never request notification,
532 ** \fIfailure\fP, to request notification on transmission failure,
533 ** \fIdelay\fP, to be notified of message delays, \fIsuccess\fP, to be
534 ** notified of successful transmission.
536 ** Example: \fTset dsn_notify="failure,delay"\fP
538 {"dsn_return", DT_STR, R_NONE, UL &DsnReturn, UL ""},
541 ** \fBNote:\fP you should not enable this unless you are using Sendmail
544 ** This variable controls how much of your message is returned in DSN
545 ** messages. It may be set to either \fIhdrs\fP to return just the
546 ** message header, or \fIfull\fP to return the full message.
548 ** Example: \fTset dsn_return=hdrs\fP
550 {"duplicate_threads", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTDUPTHREADS, 1},
553 ** This variable controls whether Mutt-ng, when sorting by threads, threads
554 ** messages with the same \fTMessage-Id:\fP header field together.
555 ** If it is \fIset\fP, it will indicate that it thinks they are duplicates
556 ** of each other with an equals sign in the thread diagram.
558 {"edit_headers", DT_BOOL, R_NONE, OPTEDITHDRS, 0},
561 ** This option allows you to edit the header of your outgoing messages
562 ** along with the body of your message.
564 {"edit_hdrs", DT_SYN, R_NONE, UL "edit_headers", 0},
567 {"editor", DT_PATH, R_NONE, UL &Editor, 0},
570 ** This variable specifies which editor is used by Mutt-ng.
571 ** It defaults to the value of the \fT$$$VISUAL\fP, or \fT$$$EDITOR\fP, environment
572 ** variable, or to the string "\fTvi\fP" if neither of those are set.
574 {"encode_from", DT_BOOL, R_NONE, OPTENCODEFROM, 0},
577 ** When \fIset\fP, Mutt-ng will \fTquoted-printable\fP encode messages when
578 ** they contain the string ``\fTFrom \fP'' (note the trailing space)
579 ** in the beginning of a line. Useful to avoid the tampering certain mail
580 ** delivery and transport agents tend to do with messages.
582 {"envelope_from", DT_BOOL, R_NONE, OPTENVFROM, 0},
585 ** When \fIset\fP, Mutt-ng will try to derive the message's \fIenvelope\fP
586 ** sender from the ``\fTFrom:\fP'' header field. Note that this information is passed
587 ** to the sendmail command using the ``\fT-f\fP" command line switch, so don't set this
588 ** option if you are using that switch in $$sendmail yourself,
589 ** or if the sendmail on your machine doesn't support that command
592 {"escape", DT_STR, R_NONE, UL &EscChar, UL "~"},
595 ** Escape character to use for functions in the builtin editor.
597 {"fast_reply", DT_BOOL, R_NONE, OPTFASTREPLY, 0},
600 ** When \fIset\fP, the initial prompt for recipients and subject are skipped
601 ** when replying to messages, and the initial prompt for subject is
602 ** skipped when forwarding messages.
604 ** \fBNote:\fP this variable has no effect when the ``$$autoedit''
605 ** variable is \fIset\fP.
607 {"fcc_attach", DT_BOOL, R_NONE, OPTFCCATTACH, 1},
610 ** This variable controls whether or not attachments on outgoing messages
611 ** are saved along with the main body of your message.
613 {"fcc_clear", DT_BOOL, R_NONE, OPTFCCCLEAR, 0},
616 ** When this variable is \fIset\fP, FCCs will be stored unencrypted and
617 ** unsigned, even when the actual message is encrypted and/or
621 {"file_charset", DT_STR, R_NONE, UL &FileCharset, UL 0},
624 ** This variable is a colon-separated list of character encoding
625 ** schemes for text file attatchments.
626 ** If \fIunset\fP, $$charset value will be used instead.
627 ** For example, the following configuration would work for Japanese
630 ** \fTset file_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"\fP
632 ** Note: ``\fTiso-2022-*\fP'' must be put at the head of the value as shown above
635 {"folder", DT_PATH, R_NONE, UL &Maildir, UL "~/Mail"},
638 ** Specifies the default location of your mailboxes. A ``\fT+\fP'' or ``\fT=\fP'' at the
639 ** beginning of a pathname will be expanded to the value of this
640 ** variable. Note that if you change this variable from the default
641 ** value you need to make sure that the assignment occurs \fIbefore\fP
642 ** you use ``+'' or ``='' for any other variables since expansion takes place
643 ** during the ``set'' command.
645 {"folder_format", DT_STR, R_INDEX, UL &FolderFormat, UL "%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f"},
648 ** This variable allows you to customize the file browser display to your
649 ** personal taste. This string is similar to ``$$index_format'', but has
650 ** its own set of \fTprintf(3)\fP-like sequences:
653 ** .dt %C .dd current file number
654 ** .dt %d .dd date/time folder was last modified
655 ** .dt %f .dd filename
656 ** .dt %F .dd file permissions
657 ** .dt %g .dd group name (or numeric gid, if missing)
658 ** .dt %l .dd number of hard links
659 ** .dt %N .dd N if folder has new mail, blank otherwise
660 ** .dt %s .dd size in bytes
661 ** .dt %t .dd * if the file is tagged, blank otherwise
662 ** .dt %u .dd owner name (or numeric uid, if missing)
663 ** .dt %>X .dd right justify the rest of the string and pad with character "X"
664 ** .dt %|X .dd pad to the end of the line with character "X"
667 {"followup_to", DT_BOOL, R_NONE, OPTFOLLOWUPTO, 1},
670 ** Controls whether or not the \fTMail-Followup-To:\fP header field is
671 ** generated when sending mail. When \fIset\fP, Mutt-ng will generate this
672 ** field when you are replying to a known mailing list, specified with
673 ** the ``subscribe'' or ``$lists'' commands or detected by common mailing list
676 ** This field has two purposes. First, preventing you from
677 ** receiving duplicate copies of replies to messages which you send
678 ** to mailing lists. Second, ensuring that you do get a reply
679 ** separately for any messages sent to known lists to which you are
680 ** not subscribed. The header will contain only the list's address
681 ** for subscribed lists, and both the list address and your own
682 ** email address for unsubscribed lists. Without this header, a
683 ** group reply to your message sent to a subscribed list will be
684 ** sent to both the list and your address, resulting in two copies
685 ** of the same email for you.
688 {"followup_to_poster", DT_QUAD, R_NONE, OPT_FOLLOWUPTOPOSTER, M_ASKYES},
691 ** Availability: NNTP
694 ** If this variable is \fIset\fP and the keyword "\fTposter\fP" is present in
695 ** the \fTFollowup-To:\fP header field, a follow-up to the newsgroup is not
696 ** permitted. The message will be mailed to the submitter of the
700 {"force_name", DT_BOOL, R_NONE, OPTFORCENAME, 0},
703 ** This variable is similar to ``$$save_name'', except that Mutt-ng will
704 ** store a copy of your outgoing message by the username of the address
705 ** you are sending to even if that mailbox does not exist.
707 ** Also see the ``$$record'' variable.
709 {"force_buffy_check", DT_BOOL, R_NONE, OPTFORCEBUFFYCHECK, 0},
712 ** When \fIset\fP, it causes Mutt-ng to check for new mail when the
713 ** \fIbuffy-list\fP command is invoked. When \fIunset\fP, \fIbuffy_list\fP
714 ** will just list all mailboxes which are already known to have new mail.
716 ** Also see the following variables: ``$$timeout'', ``$$mail_check'' and
717 ** ``$$imap_mail_check''.
719 {"forward_decode", DT_BOOL, R_NONE, OPTFORWDECODE, 1},
722 ** Controls the decoding of complex MIME messages into \fTtext/plain\fP when
723 ** forwarding a message. The message header is also RFC2047 decoded.
724 ** This variable is only used, if ``$$mime_forward'' is \fIunset\fP,
725 ** otherwise ``$$mime_forward_decode'' is used instead.
727 {"forw_decode", DT_SYN, R_NONE, UL "forward_decode", 0},
730 {"forward_edit", DT_QUAD, R_NONE, OPT_FORWEDIT, M_YES},
733 ** This quadoption controls whether or not the user is automatically
734 ** placed in the editor when forwarding messages. For those who always want
735 ** to forward with no modification, use a setting of \fIno\fP.
737 {"forward_format", DT_STR, R_NONE, UL &ForwFmt, UL "[%a: %s]"},
740 ** This variable controls the default subject when forwarding a message.
741 ** It uses the same format sequences as the ``$$index_format'' variable.
743 {"forw_format", DT_SYN, R_NONE, UL "forward_format", 0},
746 {"forward_quote", DT_BOOL, R_NONE, OPTFORWQUOTE, 0},
749 ** When \fIset\fP forwarded messages included in the main body of the
750 ** message (when ``$$mime_forward'' is \fIunset\fP) will be quoted using
751 ** ``$$indent_string''.
753 {"forw_quote", DT_SYN, R_NONE, UL "forward_quote", 0},
756 {"from", DT_ADDR, R_NONE, UL &From, UL 0},
759 ** This variable contains a default from address. It
760 ** can be overridden using my_hdr (including from send-hooks) and
761 ** ``$$reverse_name''. This variable is ignored if ``$$use_from''
765 ** \fTsend-hook Mutt-ng-devel@lists.berlios.de 'my_hdr From: Foo Bar <foo@bar.fb>'\fP
766 ** when replying to the mutt-ng developer's mailing list and Mutt-ng takes this email address.
768 ** Defaults to the contents of the environment variable \fT$$$EMAIL\fP.
770 {"gecos_mask", DT_RX, R_NONE, UL &GecosMask, UL "^[^,]*"},
773 ** A regular expression used by Mutt-ng to parse the GECOS field of a password
774 ** entry when expanding the alias. By default the regular expression is set
775 ** to ``\fT^[^,]*\fP'' which will return the string up to the first ``\fT,\fP'' encountered.
776 ** If the GECOS field contains a string like "lastname, firstname" then you
777 ** should do: \fTset gecos_mask=".*"\fP.
779 ** This can be useful if you see the following behavior: you address a e-mail
780 ** to user ID stevef whose full name is Steve Franklin. If Mutt-ng expands
781 ** stevef to ``Franklin'' stevef@foo.bar then you should set the gecos_mask to
782 ** a regular expression that will match the whole name so Mutt-ng will expand
783 ** ``Franklin'' to ``Franklin, Steve''.
786 {"group_index_format", DT_STR, R_BOTH, UL &GroupFormat, UL "%4C %M%N %5s %-45.45f %d"},
789 ** Availability: NNTP
792 ** This variable allows you to customize the newsgroup browser display to
793 ** your personal taste. This string is similar to ``$index_format'', but
794 ** has its own set of \fTprintf(3)\fP-like sequences:
797 ** %C current newsgroup number
798 ** %d description of newsgroup (retrieved from server)
800 ** %M ``-'' if newsgroup not allowed for direct post (moderated for example)
801 ** %N ``N'' if newsgroup is new, ``u'' if unsubscribed, blank otherwise
802 ** %n number of new articles in newsgroup
803 ** %s number of unread articles in newsgroup
804 ** %>X right justify the rest of the string and pad with character "X"
805 ** %|X pad to the end of the line with character "X"
809 {"hdr_format", DT_SYN, R_NONE, UL "index_format", 0},
812 {"hdrs", DT_BOOL, R_NONE, OPTHDRS, 1},
815 ** When \fIunset\fP, the header fields normally added by the ``$my_hdr''
816 ** command are not created. This variable \fImust\fP be \fIunset\fP before
817 ** composing a new message or replying in order to take effect. If \fIset\fP,
818 ** the user defined header fields are added to every new message.
820 {"header", DT_BOOL, R_NONE, OPTHEADER, 0},
823 ** When \fIset\fP, this variable causes Mutt-ng to include the header
824 ** of the message you are replying to into the edit buffer.
825 ** The ``$$weed'' setting applies.
827 {"help", DT_BOOL, R_BOTH, OPTHELP, 1},
830 ** When \fIset\fP, help lines describing the bindings for the major functions
831 ** provided by each menu are displayed on the first line of the screen.
833 ** \fBNote:\fP The binding will not be displayed correctly if the
834 ** function is bound to a sequence rather than a single keystroke. Also,
835 ** the help line may not be updated if a binding is changed while Mutt-ng is
836 ** running. Since this variable is primarily aimed at new users, neither
837 ** of these should present a major problem.
839 {"hidden_host", DT_BOOL, R_NONE, OPTHIDDENHOST, 0},
842 ** When \fIset\fP, Mutt-ng will skip the host name part of ``$$hostname'' variable
843 ** when adding the domain part to addresses. This variable does not
844 ** affect the generation of \fTMessage-ID:\fP header fields, and it will not lead to the
845 ** cut-off of first-level domains.
847 {"hide_limited", DT_BOOL, R_TREE|R_INDEX, OPTHIDELIMITED, 0},
850 ** When \fIset\fP, Mutt-ng will not show the presence of messages that are hidden
851 ** by limiting, in the thread tree.
853 {"hide_missing", DT_BOOL, R_TREE|R_INDEX, OPTHIDEMISSING, 1},
856 ** When \fIset\fP, Mutt-ng will not show the presence of missing messages in the
859 {"hide_thread_subject", DT_BOOL, R_TREE|R_INDEX, OPTHIDETHREADSUBJECT, 1},
862 ** When \fIset\fP, Mutt-ng will not show the subject of messages in the thread
863 ** tree that have the same subject as their parent or closest previously
864 ** displayed sibling.
866 {"hide_top_limited", DT_BOOL, R_TREE|R_INDEX, OPTHIDETOPLIMITED, 0},
869 ** When \fIset\fP, Mutt-ng will not show the presence of messages that are hidden
870 ** by limiting, at the top of threads in the thread tree. Note that when
871 ** $$hide_missing is set, this option will have no effect.
873 {"hide_top_missing", DT_BOOL, R_TREE|R_INDEX, OPTHIDETOPMISSING, 1},
876 ** When \fIset\fP, Mutt-ng will not show the presence of missing messages at the
877 ** top of threads in the thread tree. Note that when $$hide_limited is
878 ** \fIset\fP, this option will have no effect.
880 {"history", DT_NUM, R_NONE, UL &HistSize, 10},
883 ** This variable controls the size (in number of strings remembered) of
884 ** the string history buffer. The buffer is cleared each time the
885 ** variable is changed.
887 {"honor_followup_to", DT_QUAD, R_NONE, OPT_MFUPTO, M_YES},
890 ** This variable controls whether or not a \fTMail-Followup-To:\fP header field is
891 ** honored when group-replying to a message.
893 {"hostname", DT_STR, R_NONE, UL &Fqdn, 0},
896 ** Specifies the hostname to use after the ``\fT@\fP'' in local e-mail
897 ** addresses and during generation of \fTMessage-Id:\fP headers.
899 ** Please be sure to really know what you are doing when changing this variable
900 ** to configure a custom domain part of Message-IDs.
902 {"ignore_list_reply_to", DT_BOOL, R_NONE, OPTIGNORELISTREPLYTO, 0},
905 ** Affects the behaviour of the \fIreply\fP function when replying to
906 ** messages from mailing lists. When \fIset\fP, if the ``\fTReply-To:\fP'' header field is
907 ** set to the same value as the ``\fTTo:\fP'' header field, Mutt-ng assumes that the
908 ** ``\fTReply-To:\fP'' header field was set by the mailing list to automate responses
909 ** to the list, and will ignore this field. To direct a response to the
910 ** mailing list when this option is set, use the \fIlist-reply\fP
911 ** function; \fIgroup-reply\fP will reply to both the sender and the
915 {"imap_authenticators", DT_STR, R_NONE, UL &ImapAuthenticators, UL 0},
918 ** Availability: IMAP
921 ** This is a colon-delimited list of authentication methods Mutt-ng may
922 ** attempt to use to log in to an IMAP server, in the order Mutt-ng should
923 ** try them. Authentication methods are either ``\fTlogin\fP'' or the right
924 ** side of an IMAP ``\fTAUTH=\fP'' capability string, e.g. ``\fTdigest-md5\fP'',
925 ** ``\fTgssapi\fP'' or ``\fTcram-md5\fP''. This parameter is case-insensitive.
928 ** parameter is \fIunset\fP (the default) Mutt-ng will try all available methods,
929 ** in order from most-secure to least-secure.
931 ** Example: \fTset imap_authenticators="gssapi:cram-md5:login"\fP
933 ** \fBNote:\fP Mutt-ng will only fall back to other authentication methods if
934 ** the previous methods are unavailable. If a method is available but
935 ** authentication fails, Mutt-ng will not connect to the IMAP server.
937 {"imap_delim_chars", DT_STR, R_NONE, UL &ImapDelimChars, UL "/."},
940 ** Availability: IMAP
943 ** This contains the list of characters which you would like to treat
944 ** as folder separators for displaying IMAP paths. In particular it
945 ** helps in using the '\fT=\fP' shortcut for your $$folder variable.
947 # if defined(USE_SSL) || defined(USE_GNUTLS)
948 {"imap_force_ssl", DT_BOOL, R_NONE, OPTIMAPFORCESSL, 0},
951 ** Availability: IMAP and SSL or IMAP and GNUTLS
954 ** If this variable is \fIset\fP, Mutt-ng will always use SSL when
955 ** connecting to IMAP servers.
958 {"imap_headers", DT_STR, R_INDEX, UL &ImapHeaders, UL 0},
961 ** Availability: IMAP
964 ** Mutt-ng requests these header fields in addition to the default headers
965 ** (``DATE FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE
966 ** CONTENT-DESCRIPTION IN-REPLY-TO REPLY-TO LINES X-LABEL'') from IMAP
967 ** servers before displaying the ``index'' menu. You may want to add more
968 ** headers for spam detection.
970 ** \fBNote:\fP This is a space separated list.
972 {"imap_home_namespace", DT_STR, R_NONE, UL &ImapHomeNamespace, UL 0},
975 ** Availability: IMAP
978 ** You normally want to see your personal folders alongside
979 ** your \fTINBOX\fP in the IMAP browser. If you see something else, you may set
980 ** this variable to the IMAP path to your folders.
982 {"imap_keepalive", DT_NUM, R_NONE, UL &ImapKeepalive, 900},
985 ** Availability: IMAP
988 ** This variable specifies the maximum amount of time in seconds that Mutt-ng
989 ** will wait before polling open IMAP connections, to prevent the server
990 ** from closing them before Mutt-ng has finished with them.
993 ** well within the RFC-specified minimum amount of time (30 minutes) before
994 ** a server is allowed to do this, but in practice the RFC does get
995 ** violated every now and then.
997 ** Reduce this number if you find yourself
998 ** getting disconnected from your IMAP server due to inactivity.
1000 {"imap_list_subscribed", DT_BOOL, R_NONE, OPTIMAPLSUB, 0},
1003 ** Availability: IMAP
1006 ** This variable configures whether IMAP folder browsing will look for
1007 ** only subscribed folders or all folders. This can be toggled in the
1008 ** IMAP browser with the \fItoggle-subscribed\fP function.
1010 {"imap_mail_check", DT_NUM, R_NONE, UL &ImapBuffyTimeout, 5},
1013 ** This variable configures how often (in seconds) Mutt-ng should look for
1014 ** new mail in IMAP folders. This is split from the ``$mail_check'' variable
1015 ** to generate less traffic and get more accurate information for local folders.
1017 ** It defaults to the default value of ``$mail_check'' which is 5 seconds. But
1018 ** you may want to increase it.
1020 {"imap_pass", DT_STR, R_NONE, UL &ImapPass, UL 0},
1023 ** Availability: IMAP
1026 ** Specifies the password for your IMAP account. If \fIunset\fP, Mutt-ng will
1027 ** prompt you for your password when you invoke the fetch-mail function.
1029 ** \fBWarning\fP: you should only use this option when you are on a
1030 ** fairly secure machine, because the superuser can read your configuration even
1031 ** if you are the only one who can read the file.
1033 {"imap_passive", DT_BOOL, R_NONE, OPTIMAPPASSIVE, 1},
1036 ** Availability: IMAP
1039 ** When \fIset\fP, Mutt-ng will not open new IMAP connections to check for new
1040 ** mail. Mutt-ng will only check for new mail over existing IMAP
1041 ** connections. This is useful if you don't want to be prompted to
1042 ** user/password pairs on Mutt-ng invocation, or if opening the connection
1045 {"imap_peek", DT_BOOL, R_NONE, OPTIMAPPEEK, 1},
1048 ** Availability: IMAP
1051 ** If \fIset\fP, Mutt-ng will avoid implicitly marking your mail as read whenever
1052 ** you fetch a message from the server. This is generally a good thing,
1053 ** but can make closing an IMAP folder somewhat slower. This option
1054 ** exists to appease speed freaks.
1056 {"imap_reconnect", DT_QUAD, R_NONE, OPT_IMAPRECONNECT, M_ASKYES},
1059 ** Availability: IMAP
1062 ** Controls whether or not Mutt-ng will try to reconnect to IMAP server when
1063 ** the connection is lost.
1065 {"imap_servernoise", DT_BOOL, R_NONE, OPTIMAPSERVERNOISE, 1},
1068 ** Availability: IMAP
1071 ** When \fIset\fP, Mutt-ng will display warning messages from the IMAP
1072 ** server as error messages. Since these messages are often
1073 ** harmless, or generated due to configuration problems on the
1074 ** server which are out of the users' hands, you may wish to suppress
1075 ** them at some point.
1077 {"imap_user", DT_STR, R_NONE, UL &ImapUser, UL 0},
1080 ** Availability: IMAP
1083 ** Your login name on the IMAP server.
1085 ** This variable defaults to your user name on the local machine.
1088 {"implicit_autoview", DT_BOOL, R_NONE, OPTIMPLICITAUTOVIEW, 0},
1091 ** If \fIset\fP, Mutt-ng will look for a mailcap entry with the
1092 ** ``\fTcopiousoutput\fP'' flag set for \fIevery\fP MIME attachment it doesn't have
1093 ** an internal viewer defined for. If such an entry is found, Mutt-ng will
1094 ** use the viewer defined in that entry to convert the body part to text
1097 {"include", DT_QUAD, R_NONE, OPT_INCLUDE, M_ASKYES},
1100 ** Controls whether or not a copy of the message(s) you are replying to
1101 ** is included in your reply.
1103 {"include_onlyfirst", DT_BOOL, R_NONE, OPTINCLUDEONLYFIRST, 0},
1106 ** Controls whether or not Mutt-ng includes only the first attachment
1107 ** of the message you are replying.
1109 {"indent_string", DT_STR, R_NONE, UL &Prefix, UL "> "},
1112 ** Specifies the string to prepend to each line of text quoted in a
1113 ** message to which you are replying. You are strongly encouraged not to
1114 ** change this value, as it tends to agitate the more fanatical netizens.
1116 {"indent_str", DT_SYN, R_NONE, UL "indent_string", 0},
1119 {"index_format", DT_STR, R_BOTH, UL &HdrFmt, UL "%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s"},
1122 ** This variable allows you to customize the message index display to
1123 ** your personal taste.
1125 ** ``Format strings'' are similar to the strings used in the ``C''
1126 ** function \fTprintf(3)\fP to format output (see the man page for more detail).
1127 ** The following sequences are defined in Mutt-ng:
1130 ** .dt %a .dd address of the author
1131 ** .dt %A .dd reply-to address (if present; otherwise: address of author)
1132 ** .dt %b .dd filename of the original message folder (think mailBox)
1133 ** .dt %B .dd the list to which the letter was sent, or else the folder name (%b).
1134 ** .dt %c .dd number of characters (bytes) in the message
1135 ** .dt %C .dd current message number
1136 ** .dt %d .dd date and time of the message in the format specified by
1137 ** ``date_format'' converted to sender's time zone
1138 ** .dt %D .dd date and time of the message in the format specified by
1139 ** ``date_format'' converted to the local time zone
1140 ** .dt %e .dd current message number in thread
1141 ** .dt %E .dd number of messages in current thread
1142 ** .dt %f .dd entire From: line (address + real name)
1143 ** .dt %F .dd author name, or recipient name if the message is from you
1144 ** .dt %H .dd spam attribute(s) of this message
1145 ** .dt %g .dd newsgroup name (if compiled with nntp support)
1146 ** .dt %i .dd message-id of the current message
1147 ** .dt %l .dd number of lines in the message (does not work with maildir,
1148 ** mh, and possibly IMAP folders)
1149 ** .dt %L .dd If an address in the To or CC header field matches an address
1150 ** defined by the users ``subscribe'' command, this displays
1151 ** "To <list-name>", otherwise the same as %F.
1152 ** .dt %m .dd total number of message in the mailbox
1153 ** .dt %M .dd number of hidden messages if the thread is collapsed.
1154 ** .dt %N .dd message score
1155 ** .dt %n .dd author's real name (or address if missing)
1156 ** .dt %O .dd (_O_riginal save folder) Where Mutt-ng would formerly have
1157 ** stashed the message: list name or recipient name if no list
1158 ** .dt %s .dd subject of the message
1159 ** .dt %S .dd status of the message (N/D/d/!/r/\(as)
1160 ** .dt %t .dd `to:' field (recipients)
1161 ** .dt %T .dd the appropriate character from the $$to_chars string
1162 ** .dt %u .dd user (login) name of the author
1163 ** .dt %v .dd first name of the author, or the recipient if the message is from you
1164 ** .dt %W .dd name of organization of author (`organization:' field)
1165 ** .dt %y .dd `x-label:' field, if present
1166 ** .dt %Y .dd `x-label' field, if present, and (1) not at part of a thread tree,
1167 ** (2) at the top of a thread, or (3) `x-label' is different from
1168 ** preceding message's `x-label'.
1169 ** .dt %Z .dd message status flags
1170 ** .dt %{fmt} .dd the date and time of the message is converted to sender's
1171 ** time zone, and ``fmt'' is expanded by the library function
1172 ** ``strftime''; a leading bang disables locales
1173 ** .dt %[fmt] .dd the date and time of the message is converted to the local
1174 ** time zone, and ``fmt'' is expanded by the library function
1175 ** ``strftime''; a leading bang disables locales
1176 ** .dt %(fmt) .dd the local date and time when the message was received.
1177 ** ``fmt'' is expanded by the library function ``strftime'';
1178 ** a leading bang disables locales
1179 ** .dt %<fmt> .dd the current local time. ``fmt'' is expanded by the library
1180 ** function ``strftime''; a leading bang disables locales.
1181 ** .dt %>X .dd right justify the rest of the string and pad with character "X"
1182 ** .dt %|X .dd pad to the end of the line with character "X"
1185 ** See also: ``$$to_chars''.
1188 {"inews", DT_PATH, R_NONE, UL &Inews, UL ""},
1191 ** Availability: NNTP
1194 ** If \fIset\fP, specifies the program and arguments used to deliver news posted
1195 ** by Mutt-ng. Otherwise, Mutt-ng posts article using current connection.
1196 ** The following \fTprintf(3)\fP-style sequence is understood:
1199 ** %s newsserver name
1202 ** Example: \fTset inews="/usr/local/bin/inews -hS"\fP
1205 {"ispell", DT_PATH, R_NONE, UL &Ispell, UL ISPELL},
1208 ** How to invoke ispell (GNU's spell-checking software).
1210 {"keep_flagged", DT_BOOL, R_NONE, OPTKEEPFLAGGED, 0},
1213 ** If \fIset\fP, read messages marked as flagged will not be moved
1214 ** from your spool mailbox to your ``$$mbox'' mailbox, or as a result of
1215 ** a ``$mbox-hook'' command.
1217 {"locale", DT_STR, R_BOTH, UL &Locale, UL "C"},
1220 ** The locale used by \fTstrftime(3)\fP to format dates. Legal values are
1221 ** the strings your system accepts for the locale variable \fTLC_TIME\fP.
1223 {"list_reply", DT_QUAD, R_NONE, OPT_LISTREPLY, M_NO},
1226 ** When \fIset\fP, address replies to the mailing list the original message came
1227 ** from (instead to the author only). Setting this option to ``\fIask-yes\fP'' or
1228 ** ``\fIask-no\fP'' will ask if you really intended to reply to the author only.
1230 {"max_line_length", DT_NUM, R_NONE, UL &MaxLineLength, 0},
1233 ** When \fIset\fP, the maximum line length for displaying ``format = flowed'' messages is limited
1234 ** to this length. A value of 0 (which is also the default) means that the
1235 ** maximum line length is determined by the terminal width and $$wrapmargin.
1237 {"mail_check", DT_NUM, R_NONE, UL &BuffyTimeout, 5},
1240 ** This variable configures how often (in seconds) Mutt-ng should look for
1243 ** \fBNote:\fP This does not apply to IMAP mailboxes, see $$imap_mail_check.
1245 {"mailcap_path", DT_STR, R_NONE, UL &MailcapPath, 0},
1248 ** This variable specifies which files to consult when attempting to
1249 ** display MIME bodies not directly supported by Mutt-ng.
1251 {"mailcap_sanitize", DT_BOOL, R_NONE, OPTMAILCAPSANITIZE, 1},
1254 ** If \fIset\fP, Mutt-ng will restrict possible characters in mailcap \fT%\fP expandos
1255 ** to a well-defined set of safe characters. This is the safe setting,
1256 ** but we are not sure it doesn't break some more advanced MIME stuff.
1258 ** \fBDON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE
1263 {"header_cache", DT_PATH, R_NONE, UL &HeaderCache, 0},
1266 ** Availability: Header Cache
1269 ** The $$header_cache variable points to the header cache database.
1271 ** If $$header_cache points to a directory it will contain a header cache
1272 ** database per folder. If $$header_cache points to a file that file will
1273 ** be a single global header cache. By default it is \fIunset\fP so no
1274 ** header caching will be used.
1276 {"maildir_header_cache_verify", DT_BOOL, R_NONE, OPTHCACHEVERIFY, 1},
1279 ** Availability: Header Cache
1282 ** Check for Maildir unaware programs other than Mutt-ng having modified maildir
1283 ** files when the header cache is in use. This incurs one \fTstat(2)\fP per
1284 ** message every time the folder is opened.
1286 #if HAVE_GDBM || HAVE_DB4
1287 {"header_cache_pagesize", DT_STR, R_NONE, UL &HeaderCachePageSize, UL "16384"},
1290 ** Availability: Header Cache
1293 ** Change the maildir header cache database page size.
1296 ** or too small of a page size for the common header can waste
1297 ** space, memory effectiveness, or CPU time. The default should be more or
1298 ** less the best you can get. For details google for mutt header
1299 ** cache (first hit).
1301 #endif /* HAVE_GDBM || HAVE_DB 4 */
1303 { "header_cache_compress", DT_BOOL, R_NONE, OPTHCACHECOMPRESS, 0 },
1306 ** If enabled the header cache will be compressed. So only one fifth of the usual
1307 ** diskspace is used, but the uncompression can result in a slower open of the
1310 #endif /* HAVE_QDBM */
1311 #endif /* USE_HCACHE */
1312 {"maildir_trash", DT_BOOL, R_NONE, OPTMAILDIRTRASH, 0},
1315 ** If \fIset\fP, messages marked as deleted will be saved with the maildir
1316 ** (T)rashed flag instead of physically deleted.
1318 ** \fBNOTE:\fP this only applies
1319 ** to maildir-style mailboxes. Setting it will have no effect on other
1322 ** It is similiar to the trash option.
1324 {"mark_old", DT_BOOL, R_BOTH, OPTMARKOLD, 1},
1327 ** Controls whether or not Mutt-ng marks \fInew\fP \fBunread\fP
1328 ** messages as \fIold\fP if you exit a mailbox without reading them.
1330 ** With this option \fIset\fP, the next time you start Mutt-ng, the messages
1331 ** will show up with an "O" next to them in the ``index'' menu,
1332 ** indicating that they are old.
1334 {"markers", DT_BOOL, R_PAGER, OPTMARKERS, 1},
1337 ** Controls the display of wrapped lines in the internal pager. If set, a
1338 ** ``\fT+\fP'' marker is displayed at the beginning of wrapped lines. Also see
1339 ** the ``$$smart_wrap'' variable.
1341 {"mask", DT_RX, R_NONE, UL &Mask, UL "!^\\.[^.]"},
1344 ** A regular expression used in the file browser, optionally preceded by
1345 ** the \fInot\fP operator ``\fT!\fP''. Only files whose names match this mask
1346 ** will be shown. The match is always case-sensitive.
1348 {"mbox", DT_PATH, R_BOTH, UL &Inbox, UL "~/mbox"},
1351 ** This specifies the folder into which read mail in your ``$$spoolfile''
1352 ** folder will be appended.
1354 {"operating_system", DT_STR, R_NONE, UL &OperatingSystem, 0},
1357 ** This specifies the operating system name for the \fTUser-Agent:\fP header field. If
1358 ** this is \fIunset\fP, it will be set to the operating system name that \fTuname(2)\fP
1359 ** returns. If \fTuname(2)\fP fails, ``UNIX'' will be used.
1361 ** It may, for example, look as: ``\fTmutt-ng 1.5.9i (Linux)\fP''.
1363 {"sidebar_boundary", DT_STR, R_BOTH, UL &SidebarBoundary, UL "." },
1366 ** When the sidebar is displayed and $$sidebar_shorten_hierarchy is \fIset\fP, this
1367 ** variable specifies the characters at which to split a folder name into
1368 ** ``hierarchy items.''
1370 {"sidebar_delim", DT_STR, R_BOTH, UL &SidebarDelim, UL "|"},
1373 ** This specifies the delimiter between the sidebar (if visible) and
1376 {"sidebar_visible", DT_BOOL, R_BOTH, OPTMBOXPANE, 0},
1379 ** This specifies whether or not to show the sidebar (a list of folders specified
1380 ** with the ``mailboxes'' command).
1382 {"sidebar_width", DT_NUM, R_BOTH, UL &SidebarWidth, 0},
1385 ** The width of the sidebar.
1387 {"sidebar_newmail_only", DT_BOOL, R_BOTH, OPTSIDEBARNEWMAILONLY, 0},
1390 ** If \fIset\fP, only folders with new mail will be shown in the sidebar.
1392 {"sidebar_number_format", DT_STR, R_BOTH, UL &SidebarNumberFormat, UL "%c%?n?(%n)?%?f?[%f]?"},
1395 ** This variable controls how message counts are printed when the sidebar
1396 ** is enabled. If this variable is \fIempty\fP (\fIand only if\fP), no numbers
1397 ** will be printed \fIand\fP mutt-ng won't frequently count mail (which
1398 ** may be a great speedup esp. with mbox-style mailboxes.)
1400 ** The following \fTprintf(3)\fP-like sequences are supported:
1403 ** .dt %c .dd Total number of messages.
1404 ** .dt %f .dd Number of flagged messages.
1405 ** .dt %n .dd Number of new messages.
1408 ** The \fT%f\fP and \fT%n\fP expandos may optionally be printed non-zero.
1410 {"sidebar_shorten_hierarchy", DT_BOOL, R_NONE, OPTSHORTENHIERARCHY, 0},
1413 ** When \fIset\fP, the ``hierarchy'' of the sidebar entries will be shortened
1414 ** only if they cannot be printed in full length (because ``$$sidebar_width''
1415 ** is set to a too low value). For example, if the newsgroup name
1416 ** ``de.alt.sysadmin.recovery'' doesn't fit on the screen, it'll get shortened
1417 ** ``d.a.s.recovery'' while ``de.alt.d0'' still would and thus will not get
1420 ** At which characters this compression is done is controled via the
1421 ** $$sidebar_boundary variable.
1423 {"mbox_type", DT_MAGIC, R_NONE, UL &DefaultMagic, M_MBOX},
1426 ** The default mailbox type used when creating new folders. May be any of
1427 ** \fTmbox\fP, \fTMMDF\fP, \fTMH\fP and \fTMaildir\fP.
1429 {"metoo", DT_BOOL, R_NONE, OPTMETOO, 0},
1432 ** If \fIunset\fP, Mutt-ng will remove your address (see the ``alternates''
1433 ** command) from the list of recipients when replying to a message.
1435 {"menu_context", DT_NUM, R_NONE, UL &MenuContext, 0},
1438 ** This variable controls the number of lines of context that are given
1439 ** when scrolling through menus. (Similar to ``$$pager_context''.)
1441 {"menu_move_off", DT_BOOL, R_NONE, OPTMENUMOVEOFF, 0},
1444 ** When \fIunset\fP, the bottom entry of menus will never scroll up past
1445 ** the bottom of the screen, unless there are less entries than lines.
1446 ** When \fIset\fP, the bottom entry may move off the bottom.
1448 {"menu_scroll", DT_BOOL, R_NONE, OPTMENUSCROLL, 0},
1451 ** When \fIset\fP, menus will be scrolled up or down one line when you
1452 ** attempt to move across a screen boundary. If \fIunset\fP, the screen
1453 ** is cleared and the next or previous page of the menu is displayed
1454 ** (useful for slow links to avoid many redraws).
1456 {"meta_key", DT_BOOL, R_NONE, OPTMETAKEY, 0},
1459 ** If \fIset\fP, forces Mutt-ng to interpret keystrokes with the high bit (bit 8)
1460 ** set as if the user had pressed the \fTESC\fP key and whatever key remains
1461 ** after having the high bit removed. For example, if the key pressed
1462 ** has an ASCII value of \fT0xf4\fP, then this is treated as if the user had
1463 ** pressed \fTESC\fP then ``\fTx\fP''. This is because the result of removing the
1464 ** high bit from ``\fT0xf4\fP'' is ``\fT0x74\fP'', which is the ASCII character
1467 {"mh_purge", DT_BOOL, R_NONE, OPTMHPURGE, 0},
1470 ** When \fIunset\fP, Mutt-ng will mimic mh's behaviour and rename deleted messages
1471 ** to \fI,<old file name>\fP in mh folders instead of really deleting
1472 ** them. If the variable is set, the message files will simply be
1475 {"mh_seq_flagged", DT_STR, R_NONE, UL &MhFlagged, UL "flagged"},
1478 ** The name of the MH sequence used for flagged messages.
1480 {"mh_seq_replied", DT_STR, R_NONE, UL &MhReplied, UL "replied"},
1483 ** The name of the MH sequence used to tag replied messages.
1485 {"mh_seq_unseen", DT_STR, R_NONE, UL &MhUnseen, UL "unseen"},
1488 ** The name of the MH sequence used for unseen messages.
1490 {"mime_forward", DT_QUAD, R_NONE, OPT_MIMEFWD, M_NO},
1493 ** When \fIset\fP, the message you are forwarding will be attached as a
1494 ** separate MIME part instead of included in the main body of the
1497 ** This is useful for forwarding MIME messages so the receiver
1498 ** can properly view the message as it was delivered to you. If you like
1499 ** to switch between MIME and not MIME from mail to mail, set this
1500 ** variable to ask-no or ask-yes.
1502 ** Also see ``$$forward_decode'' and ``$$mime_forward_decode''.
1504 {"mime_forward_decode", DT_BOOL, R_NONE, OPTMIMEFORWDECODE, 0},
1507 ** Controls the decoding of complex MIME messages into \fTtext/plain\fP when
1508 ** forwarding a message while ``$$mime_forward'' is \fIset\fP. Otherwise
1509 ** ``$$forward_decode'' is used instead.
1511 {"mime_fwd", DT_SYN, R_NONE, UL "mime_forward", 0},
1515 {"mime_forward_rest", DT_QUAD, R_NONE, OPT_MIMEFWDREST, M_YES},
1518 ** When forwarding multiple attachments of a MIME message from the recvattach
1519 ** menu, attachments which cannot be decoded in a reasonable manner will
1520 ** be attached to the newly composed message if this option is set.
1524 {"mime_subject", DT_BOOL, R_NONE, OPTMIMESUBJECT, 1},
1527 ** Availability: NNTP
1530 ** If \fIunset\fP, an 8-bit ``\fTSubject:\fP'' header field in a news article
1531 ** will not be encoded according to RFC2047.
1533 ** \fBNote:\fP Only change this setting if you know what you are doing.
1538 {"mix_entry_format", DT_STR, R_NONE, UL &MixEntryFormat, UL "%4n %c %-16s %a"},
1541 ** Availability: Mixmaster
1544 ** This variable describes the format of a remailer line on the mixmaster
1545 ** chain selection screen. The following \fTprintf(3)\fP-like sequences are
1549 ** .dt %n .dd The running number on the menu.
1550 ** .dt %c .dd Remailer capabilities.
1551 ** .dt %s .dd The remailer's short name.
1552 ** .dt %a .dd The remailer's e-mail address.
1555 {"mixmaster", DT_PATH, R_NONE, UL &Mixmaster, UL MIXMASTER},
1558 ** Availability: Mixmaster
1561 ** This variable contains the path to the Mixmaster binary on your
1562 ** system. It is used with various sets of parameters to gather the
1563 ** list of known remailers, and to finally send a message through the
1567 {"move", DT_QUAD, R_NONE, OPT_MOVE, M_ASKNO},
1570 ** Controls whether or not Mutt-ng will move read messages
1571 ** from your spool mailbox to your ``$$mbox'' mailbox, or as a result of
1572 ** a ``$mbox-hook'' command.
1574 {"message_format", DT_STR, R_NONE, UL &MsgFmt, UL "%s"},
1577 ** This is the string displayed in the ``attachment'' menu for
1578 ** attachments of type \fTmessage/rfc822\fP. For a full listing of defined
1579 ** \fTprintf(3)\fP-like sequences see the section on ``$$index_format''.
1581 {"msg_format", DT_SYN, R_NONE, UL "message_format", 0},
1584 {"msgid_format", DT_STR, R_NONE, UL &MsgIdFormat, UL "%Y%m%d%h%M%s.G%P%p"},
1587 ** This is the format for the ``local part'' of the \fTMessage-Id:\fP header
1588 ** field generated by Mutt-ng. If this variable is empty, no \fTMessage-Id:\fP
1589 ** headers will be generated. The '%'
1590 ** character marks that certain data will be added to the string, similar to
1591 ** \fTprintf(3)\fP. The following characters are allowed:
1594 ** .dt %d .dd the current day of month
1595 ** .dt %h .dd the current hour
1596 ** .dt %m .dd the current month
1597 ** .dt %M .dd the current minute
1598 ** .dt %O .dd the current UNIX timestamp (octal)
1599 ** .dt %p .dd the process ID
1600 ** .dt %P .dd the current Message-ID prefix (a character rotating with
1601 ** every Message-ID being generated)
1602 ** .dt %r .dd a random integer value (decimal)
1603 ** .dt %R .dd a random integer value (hexadecimal)
1604 ** .dt %s .dd the current second
1605 ** .dt %T .dd the current UNIX timestamp (decimal)
1606 ** .dt %X .dd the current UNIX timestamp (hexadecimal)
1607 ** .dt %Y .dd the current year (Y2K compliant)
1608 ** .dt %% .dd the '%' character
1611 ** \fBNote:\fP Please only change this setting if you know what you are doing.
1612 ** Also make sure to consult RFC2822 to produce technically \fIvalid\fP strings.
1614 {"narrow_tree", DT_BOOL, R_TREE|R_INDEX, OPTNARROWTREE, 0},
1617 ** This variable, when \fIset\fP, makes the thread tree narrower, allowing
1618 ** deeper threads to fit on the screen.
1621 {"news_cache_dir", DT_PATH, R_NONE, UL &NewsCacheDir, UL "~/.muttng"},
1624 ** Availability: NNTP
1627 ** This variable points to directory where Mutt-ng will cache news
1628 ** article headers. If \fIunset\fP, headers will not be saved at all
1629 ** and will be reloaded each time when you enter a newsgroup.
1631 ** As for the header caching in connection with IMAP and/or Maildir,
1632 ** this drastically increases speed and lowers traffic.
1634 {"news_server", DT_STR, R_NONE, UL &NewsServer, 0},
1637 ** Availability: NNTP
1640 ** This variable specifies the name (or address) of the NNTP server to be used.
1643 ** defaults to the value specified via the environment variable
1644 ** \fT$$$NNTPSERVER\fP or contained in the file \fT/etc/nntpserver\fP.
1647 ** specify a username and an alternative port for each newsserver, e.g.
1649 ** \fT[nntp[s]://][username[:password]@]newsserver[:port]\fP
1651 ** \fBNote:\fP Using a password as shown and stored in a configuration file
1652 ** presents a security risk since the superuser of your machine may read it
1653 ** regardless of the file's permissions.
1655 {"newsrc", DT_PATH, R_NONE, UL &NewsRc, UL "~/.newsrc"},
1658 ** Availability: NNTP
1661 ** This file contains information about subscribed newsgroup and
1662 ** articles read so far.
1664 ** To ease the use of multiple news servers, the following \fTprintf(3)\fP-style
1665 ** sequence is understood:
1668 ** %s newsserver name
1671 {"nntp_context", DT_NUM, R_NONE, UL &NntpContext, 1000},
1674 ** Availability: NNTP
1677 ** This variable controls how many news articles to cache per newsgroup
1678 ** (if caching is enabled, see $$news_cache_dir) and how many news articles
1679 ** to show in the ``index'' menu.
1681 ** If there're more articles than defined with $$nntp_context, all older ones
1682 ** will be removed/not shown in the index.
1684 {"nntp_load_description", DT_BOOL, R_NONE, OPTLOADDESC, 1},
1687 ** Availability: NNTP
1690 ** This variable controls whether or not descriptions for newsgroups
1691 ** are to be loaded when subscribing to a newsgroup.
1693 {"nntp_user", DT_STR, R_NONE, UL &NntpUser, UL ""},
1696 ** Availability: NNTP
1699 ** Your login name on the NNTP server. If \fIunset\fP and the server requires
1700 ** authentification, Mutt-ng will prompt you for your account name.
1702 {"nntp_pass", DT_STR, R_NONE, UL &NntpPass, UL ""},
1705 ** Availability: NNTP
1708 ** Your password for NNTP account.
1710 ** \fBNote:\fP Storing passwords in a configuration file
1711 ** presents a security risk since the superuser of your machine may read it
1712 ** regardless of the file's permissions.
1714 {"nntp_poll", DT_NUM, R_NONE, UL &NewsPollTimeout, 60},
1717 ** Availability: NNTP
1720 ** The time in seconds until any operations on a newsgroup except posting a new
1721 ** article will cause a recheck for new news. If set to 0, Mutt-ng will
1722 ** recheck on each operation in index (stepping, read article, etc.).
1724 {"nntp_reconnect", DT_QUAD, R_NONE, OPT_NNTPRECONNECT, M_ASKYES},
1727 ** Availability: NNTP
1730 ** Controls whether or not Mutt-ng will try to reconnect to a newsserver when the
1731 ** was connection lost.
1734 {"pager", DT_PATH, R_NONE, UL &Pager, UL "builtin"},
1737 ** This variable specifies which pager you would like to use to view
1738 ** messages. ``builtin'' means to use the builtin pager, otherwise this
1739 ** variable should specify the pathname of the external pager you would
1742 ** Using an external pager may have some disadvantages: Additional
1743 ** keystrokes are necessary because you can't call Mutt-ng functions
1744 ** directly from the pager, and screen resizes cause lines longer than
1745 ** the screen width to be badly formatted in the help menu.
1747 {"pager_context", DT_NUM, R_NONE, UL &PagerContext, 0},
1750 ** This variable controls the number of lines of context that are given
1751 ** when displaying the next or previous page in the internal pager. By
1752 ** default, Mutt-ng will display the line after the last one on the screen
1753 ** at the top of the next page (0 lines of context).
1755 {"pager_format", DT_STR, R_PAGER, UL &PagerFmt, UL "-%Z- %C/%m: %-20.20n %s"},
1758 ** This variable controls the format of the one-line message ``status''
1759 ** displayed before each message in either the internal or an external
1760 ** pager. The valid sequences are listed in the ``$$index_format''
1763 {"pager_index_lines", DT_NUM, R_PAGER, UL &PagerIndexLines, 0},
1766 ** Determines the number of lines of a mini-index which is shown when in
1767 ** the pager. The current message, unless near the top or bottom of the
1768 ** folder, will be roughly one third of the way down this mini-index,
1769 ** giving the reader the context of a few messages before and after the
1770 ** message. This is useful, for example, to determine how many messages
1771 ** remain to be read in the current thread. One of the lines is reserved
1772 ** for the status bar from the index, so a \fIpager_index_lines\fP of 6
1773 ** will only show 5 lines of the actual index. A value of 0 results in
1774 ** no index being shown. If the number of messages in the current folder
1775 ** is less than \fIpager_index_lines\fP, then the index will only use as
1776 ** many lines as it needs.
1778 {"pager_stop", DT_BOOL, R_NONE, OPTPAGERSTOP, 0},
1781 ** When \fIset\fP, the internal-pager will \fBnot\fP move to the next message
1782 ** when you are at the end of a message and invoke the \fInext-page\fP
1785 {"pgp_autosign", DT_SYN, R_NONE, UL "crypt_autosign", 0},
1786 {"crypt_autosign", DT_BOOL, R_NONE, OPTCRYPTAUTOSIGN, 0},
1789 ** Setting this variable will cause Mutt-ng to always attempt to
1790 ** cryptographically sign outgoing messages. This can be overridden
1791 ** by use of the \fIpgp-menu\fP, when signing is not required or
1792 ** encryption is requested as well. If ``$$smime_is_default'' is \fIset\fP,
1793 ** then OpenSSL is used instead to create S/MIME messages and settings can
1794 ** be overridden by use of the \fIsmime-menu\fP.
1797 {"pgp_autoencrypt", DT_SYN, R_NONE, UL "crypt_autoencrypt", 0},
1798 {"crypt_autoencrypt", DT_BOOL, R_NONE, OPTCRYPTAUTOENCRYPT, 0},
1801 ** Setting this variable will cause Mutt-ng to always attempt to PGP
1802 ** encrypt outgoing messages. This is probably only useful in
1803 ** connection to the \fIsend-hook\fP command. It can be overridden
1804 ** by use of the \fIpgp-menu\fP, when encryption is not required or
1805 ** signing is requested as well. If ``$$smime_is_default'' is \fIset\fP,
1806 ** then OpenSSL is used instead to create S/MIME messages and
1807 ** settings can be overridden by use of the \fIsmime-menu\fP.
1810 {"pgp_ignore_subkeys", DT_BOOL, R_NONE, OPTPGPIGNORESUB, 1},
1813 ** Setting this variable will cause Mutt-ng to ignore OpenPGP subkeys. Instead,
1814 ** the principal key will inherit the subkeys' capabilities. \fIUnset\fP this
1815 ** if you want to play interesting key selection games.
1818 {"pgp_replyencrypt", DT_SYN, R_NONE, UL "crypt_replyencrypt", 1},
1819 {"crypt_replyencrypt", DT_BOOL, R_NONE, OPTCRYPTREPLYENCRYPT, 1},
1822 ** If \fIset\fP, automatically PGP or OpenSSL encrypt replies to messages which are
1826 {"pgp_replysign", DT_SYN, R_NONE, UL "crypt_replysign", 0},
1827 {"crypt_replysign", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGN, 0},
1830 ** If \fIset\fP, automatically PGP or OpenSSL sign replies to messages which are
1833 ** \fBNote:\fP this does not work on messages that are encrypted \fBand\fP signed!
1836 {"pgp_replysignencrypted", DT_SYN, R_NONE, UL "crypt_replysignencrypted", 0},
1837 {"crypt_replysignencrypted", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGNENCRYPTED, 0},
1840 ** If \fIset\fP, automatically PGP or OpenSSL sign replies to messages
1841 ** which are encrypted. This makes sense in combination with
1842 ** ``$$crypt_replyencrypt'', because it allows you to sign all
1843 ** messages which are automatically encrypted. This works around
1844 ** the problem noted in ``$$crypt_replysign'', that Mutt-ng is not able
1845 ** to find out whether an encrypted message is also signed.
1848 {"crypt_timestamp", DT_BOOL, R_NONE, OPTCRYPTTIMESTAMP, 1},
1851 ** If \fIset\fP, Mutt-ng will include a time stamp in the lines surrounding
1852 ** PGP or S/MIME output, so spoofing such lines is more difficult.
1853 ** If you are using colors to mark these lines, and rely on these,
1854 ** you may \fIunset\fP this setting.
1857 {"pgp_use_gpg_agent", DT_BOOL, R_NONE, OPTUSEGPGAGENT, 0},
1860 ** If \fIset\fP, Mutt-ng will use a possibly-running gpg-agent process.
1863 {"pgp_verify_sig", DT_SYN, R_NONE, UL "crypt_verify_sig", 0},
1864 {"crypt_verify_sig", DT_QUAD, R_NONE, OPT_VERIFYSIG, M_YES},
1867 ** If ``\fIyes\fP'', always attempt to verify PGP or S/MIME signatures.
1868 ** If ``\fIask\fP'', ask whether or not to verify the signature.
1869 ** If ``\fIno\fP'', never attempt to verify cryptographic signatures.
1872 {"smime_is_default", DT_BOOL, R_NONE, OPTSMIMEISDEFAULT, 0},
1875 ** The default behaviour of Mutt-ng is to use PGP on all auto-sign/encryption
1876 ** operations. To override and to use OpenSSL instead this must be \fIset\fP.
1878 ** However, this has no effect while replying, since Mutt-ng will automatically
1879 ** select the same application that was used to sign/encrypt the original
1882 ** (Note that this variable can be overridden by unsetting $$crypt_autosmime.)
1885 {"smime_ask_cert_label", DT_BOOL, R_NONE, OPTASKCERTLABEL, 1},
1888 ** This flag controls whether you want to be asked to enter a label
1889 ** for a certificate about to be added to the database or not. It is
1890 ** \fIset\fP by default.
1893 {"smime_decrypt_use_default_key", DT_BOOL, R_NONE, OPTSDEFAULTDECRYPTKEY, 1},
1896 ** If \fIset\fP (default) this tells Mutt-ng to use the default key for decryption. Otherwise,
1897 ** if manage multiple certificate-key-pairs, Mutt-ng will try to use the mailbox-address
1898 ** to determine the key to use. It will ask you to supply a key, if it can't find one.
1901 {"pgp_entry_format", DT_STR, R_NONE, UL &PgpEntryFormat, UL "%4n %t%f %4l/0x%k %-4a %2c %u"},
1904 ** This variable allows you to customize the PGP key selection menu to
1905 ** your personal taste. This string is similar to ``$$index_format'', but
1906 ** has its own set of \fTprintf(3)\fP-like sequences:
1909 ** .dt %n .dd number
1910 ** .dt %k .dd key id
1911 ** .dt %u .dd user id
1912 ** .dt %a .dd algorithm
1913 ** .dt %l .dd key length
1915 ** .dt %c .dd capabilities
1916 ** .dt %t .dd trust/validity of the key-uid association
1917 ** .dt %[<s>] .dd date of the key where <s> is an \fTstrftime(3)\fP expression
1922 {"pgp_good_sign", DT_RX, R_NONE, UL &PgpGoodSign, 0},
1925 ** If you assign a text to this variable, then a PGP signature is only
1926 ** considered verified if the output from $$pgp_verify_command contains
1927 ** the text. Use this variable if the exit code from the command is 0
1928 ** even for bad signatures.
1931 {"pgp_check_exit", DT_BOOL, R_NONE, OPTPGPCHECKEXIT, 1},
1934 ** If \fIset\fP, Mutt-ng will check the exit code of the PGP subprocess when
1935 ** signing or encrypting. A non-zero exit code means that the
1936 ** subprocess failed.
1939 {"pgp_long_ids", DT_BOOL, R_NONE, OPTPGPLONGIDS, 0},
1942 ** If \fIset\fP, use 64 bit PGP key IDs. \fIUnset\fP uses the normal 32 bit Key IDs.
1945 {"pgp_retainable_sigs", DT_BOOL, R_NONE, OPTPGPRETAINABLESIG, 0},
1948 ** If \fIset\fP, signed and encrypted messages will consist of nested
1949 ** multipart/signed and multipart/encrypted body parts.
1951 ** This is useful for applications like encrypted and signed mailing
1952 ** lists, where the outer layer (multipart/encrypted) can be easily
1953 ** removed, while the inner multipart/signed part is retained.
1956 {"pgp_create_traditional", DT_SYN, R_NONE, UL "pgp_autoinline", 0},
1957 {"pgp_autoinline", DT_BOOL, R_NONE, OPTPGPAUTOINLINE, 0},
1960 ** This option controls whether Mutt-ng generates old-style inline
1961 ** (traditional) PGP encrypted or signed messages under certain
1962 ** circumstances. This can be overridden by use of the \fIpgp-menu\fP,
1963 ** when inline is not required.
1965 ** Note that Mutt-ng might automatically use PGP/MIME for messages
1966 ** which consist of more than a single MIME part. Mutt-ng can be
1967 ** configured to ask before sending PGP/MIME messages when inline
1968 ** (traditional) would not work.
1969 ** See also: ``$$pgp_mime_auto''.
1971 ** Also note that using the old-style PGP message format is \fBstrongly\fP
1972 ** \fBdeprecated\fP.
1975 {"pgp_auto_traditional", DT_SYN, R_NONE, UL "pgp_replyinline", 0},
1976 {"pgp_replyinline", DT_BOOL, R_NONE, OPTPGPREPLYINLINE, 0},
1979 ** Setting this variable will cause Mutt-ng to always attempt to
1980 ** create an inline (traditional) message when replying to a
1981 ** message which is PGP encrypted/signed inline. This can be
1982 ** overridden by use of the \fIpgp-menu\fP, when inline is not
1983 ** required. This option does not automatically detect if the
1984 ** (replied-to) message is inline; instead it relies on Mutt-ng
1985 ** internals for previously checked/flagged messages.
1987 ** Note that Mutt-ng might automatically use PGP/MIME for messages
1988 ** which consist of more than a single MIME part. Mutt-ng can be
1989 ** configured to ask before sending PGP/MIME messages when inline
1990 ** (traditional) would not work.
1991 ** See also: ``$$pgp_mime_auto''.
1993 ** Also note that using the old-style PGP message format is \fBstrongly\fP
1994 ** \fBdeprecated\fP.
1998 {"pgp_show_unusable", DT_BOOL, R_NONE, OPTPGPSHOWUNUSABLE, 1},
2001 ** If \fIset\fP, Mutt-ng will display non-usable keys on the PGP key selection
2002 ** menu. This includes keys which have been revoked, have expired, or
2003 ** have been marked as ``disabled'' by the user.
2006 {"pgp_sign_as", DT_STR, R_NONE, UL &PgpSignAs, 0},
2009 ** If you have more than one key pair, this option allows you to specify
2010 ** which of your private keys to use. It is recommended that you use the
2011 ** keyid form to specify your key (e.g., ``\fT0x00112233\fP'').
2014 {"pgp_strict_enc", DT_BOOL, R_NONE, OPTPGPSTRICTENC, 1},
2017 ** If \fIset\fP, Mutt-ng will automatically encode PGP/MIME signed messages as
2018 ** \fTquoted-printable\fP. Please note that unsetting this variable may
2019 ** lead to problems with non-verifyable PGP signatures, so only change
2020 ** this if you know what you are doing.
2023 {"pgp_timeout", DT_NUM, R_NONE, UL &PgpTimeout, 300},
2026 ** The number of seconds after which a cached passphrase will expire if
2027 ** not used. Default: 300.
2030 {"pgp_sort_keys", DT_SORT|DT_SORT_KEYS, R_NONE, UL &PgpSortKeys, SORT_ADDRESS},
2033 ** Specifies how the entries in the ``pgp keys'' menu are sorted. The
2034 ** following are legal values:
2037 ** .dt address .dd sort alphabetically by user id
2038 ** .dt keyid .dd sort alphabetically by key id
2039 ** .dt date .dd sort by key creation date
2040 ** .dt trust .dd sort by the trust of the key
2043 ** If you prefer reverse order of the above values, prefix it with
2047 {"pgp_mime_auto", DT_QUAD, R_NONE, OPT_PGPMIMEAUTO, M_ASKYES},
2050 ** This option controls whether Mutt-ng will prompt you for
2051 ** automatically sending a (signed/encrypted) message using
2052 ** PGP/MIME when inline (traditional) fails (for any reason).
2054 ** Also note that using the old-style PGP message format is \fBstrongly\fP
2055 ** \fBdeprecated\fP.
2058 {"pgp_auto_decode", DT_BOOL, R_NONE, OPTPGPAUTODEC, 0},
2061 ** If \fIset\fP, Mutt-ng will automatically attempt to decrypt traditional PGP
2062 ** messages whenever the user performs an operation which ordinarily would
2063 ** result in the contents of the message being operated on. For example,
2064 ** if the user displays a pgp-traditional message which has not been manually
2065 ** checked with the check-traditional-pgp function, Mutt-ng will automatically
2066 ** check the message for traditional pgp.
2069 /* XXX Default values! */
2071 {"pgp_decode_command", DT_STR, R_NONE, UL &PgpDecodeCommand, 0},
2074 ** This format strings specifies a command which is used to decode
2075 ** application/pgp attachments.
2077 ** The PGP command formats have their own set of \fTprintf(3)\fP-like sequences:
2080 ** .dt %p .dd Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
2081 ** string otherwise. Note: This may be used with a %? construct.
2082 ** .dt %f .dd Expands to the name of a file containing a message.
2083 ** .dt %s .dd Expands to the name of a file containing the signature part
2084 ** . of a multipart/signed attachment when verifying it.
2085 ** .dt %a .dd The value of $$pgp_sign_as.
2086 ** .dt %r .dd One or more key IDs.
2089 ** For examples on how to configure these formats for the various versions
2090 ** of PGP which are floating around, see the pgp*.rc and gpg.rc files in
2091 ** the \fTsamples/\fP subdirectory which has been installed on your system
2092 ** alongside the documentation.
2095 {"pgp_getkeys_command", DT_STR, R_NONE, UL &PgpGetkeysCommand, 0},
2098 ** This command is invoked whenever Mutt-ng will need public key information.
2099 ** \fT%r\fP is the only \fTprintf(3)\fP-like sequence used with this format.
2102 {"pgp_verify_command", DT_STR, R_NONE, UL &PgpVerifyCommand, 0},
2105 ** This command is used to verify PGP signatures.
2108 {"pgp_decrypt_command", DT_STR, R_NONE, UL &PgpDecryptCommand, 0},
2111 ** This command is used to decrypt a PGP encrypted message.
2114 {"pgp_clearsign_command", DT_STR, R_NONE, UL &PgpClearSignCommand, 0},
2117 ** This format is used to create a old-style ``clearsigned'' PGP message.
2119 ** Note that the use of this format is \fBstrongly\fP \fBdeprecated\fP.
2122 {"pgp_sign_command", DT_STR, R_NONE, UL &PgpSignCommand, 0},
2125 ** This command is used to create the detached PGP signature for a
2126 ** multipart/signed PGP/MIME body part.
2129 {"pgp_encrypt_sign_command", DT_STR, R_NONE, UL &PgpEncryptSignCommand, 0},
2132 ** This command is used to both sign and encrypt a body part.
2135 {"pgp_encrypt_only_command", DT_STR, R_NONE, UL &PgpEncryptOnlyCommand, 0},
2138 ** This command is used to encrypt a body part without signing it.
2141 {"pgp_import_command", DT_STR, R_NONE, UL &PgpImportCommand, 0},
2144 ** This command is used to import a key from a message into
2145 ** the user's public key ring.
2148 {"pgp_export_command", DT_STR, R_NONE, UL &PgpExportCommand, 0},
2151 ** This command is used to export a public key from the user's
2155 {"pgp_verify_key_command", DT_STR, R_NONE, UL &PgpVerifyKeyCommand, 0},
2158 ** This command is used to verify key information from the key selection
2162 {"pgp_list_secring_command", DT_STR, R_NONE, UL &PgpListSecringCommand, 0},
2165 ** This command is used to list the secret key ring's contents. The
2166 ** output format must be analogous to the one used by
2167 ** \fTgpg --list-keys --with-colons\fP.
2169 ** This format is also generated by the \fTpgpring\fP utility which comes
2173 {"pgp_list_pubring_command", DT_STR, R_NONE, UL &PgpListPubringCommand, 0},
2176 ** This command is used to list the public key ring's contents. The
2177 ** output format must be analogous to the one used by
2178 ** \fTgpg --list-keys --with-colons\fP.
2180 ** This format is also generated by the \fTpgpring\fP utility which comes
2184 {"forward_decrypt", DT_BOOL, R_NONE, OPTFORWDECRYPT, 1},
2187 ** Controls the handling of encrypted messages when forwarding a message.
2188 ** When \fIset\fP, the outer layer of encryption is stripped off. This
2189 ** variable is only used if ``$$mime_forward'' is \fIset\fP and
2190 ** ``$$mime_forward_decode'' is \fIunset\fP.
2193 {"forw_decrypt", DT_SYN, R_NONE, UL "forward_decrypt", 0},
2197 {"smime_timeout", DT_NUM, R_NONE, UL &SmimeTimeout, 300},
2200 ** The number of seconds after which a cached passphrase will expire if
2204 {"smime_encrypt_with", DT_STR, R_NONE, UL &SmimeCryptAlg, 0},
2207 ** This sets the algorithm that should be used for encryption.
2208 ** Valid choices are ``\fTdes\fP'', ``\fTdes3\fP'', ``\fTrc2-40\fP'',
2209 ** ``\fTrc2-64\fP'', ``\frc2-128\fP''.
2211 ** If \fIunset\fP ``\fI3des\fP'' (TripleDES) is used.
2214 {"smime_keys", DT_PATH, R_NONE, UL &SmimeKeys, 0},
2217 ** Since there is no pubring/secring as with PGP, Mutt-ng has to handle
2218 ** storage ad retrieval of keys/certs by itself. This is very basic right now,
2219 ** and stores keys and certificates in two different directories, both
2220 ** named as the hash-value retrieved from OpenSSL. There is an index file
2221 ** which contains mailbox-address keyid pair, and which can be manually
2222 ** edited. This one points to the location of the private keys.
2225 {"smime_ca_location", DT_PATH, R_NONE, UL &SmimeCALocation, 0},
2228 ** This variable contains the name of either a directory, or a file which
2229 ** contains trusted certificates for use with OpenSSL.
2232 {"smime_certificates", DT_PATH, R_NONE, UL &SmimeCertificates, 0},
2235 ** Since there is no pubring/secring as with PGP, Mutt-ng has to handle
2236 ** storage and retrieval of keys by itself. This is very basic right
2237 ** now, and keys and certificates are stored in two different
2238 ** directories, both named as the hash-value retrieved from
2239 ** OpenSSL. There is an index file which contains mailbox-address
2240 ** keyid pairs, and which can be manually edited. This one points to
2241 ** the location of the certificates.
2244 {"smime_decrypt_command", DT_STR, R_NONE, UL &SmimeDecryptCommand, 0},
2247 ** This format string specifies a command which is used to decrypt
2248 ** \fTapplication/x-pkcs7-mime\fP attachments.
2250 ** The OpenSSL command formats have their own set of \fTprintf(3)\fP-like sequences
2251 ** similar to PGP's:
2254 ** .dt %f .dd Expands to the name of a file containing a message.
2255 ** .dt %s .dd Expands to the name of a file containing the signature part
2256 ** . of a multipart/signed attachment when verifying it.
2257 ** .dt %k .dd The key-pair specified with $$smime_default_key
2258 ** .dt %c .dd One or more certificate IDs.
2259 ** .dt %a .dd The algorithm used for encryption.
2260 ** .dt %C .dd CA location: Depending on whether $$smime_ca_location
2261 ** . points to a directory or file, this expands to
2262 ** . "-CApath $$smime_ca_location" or "-CAfile $$smime_ca_location".
2265 ** For examples on how to configure these formats, see the smime.rc in
2266 ** the \fTsamples/\fP subdirectory which has been installed on your system
2267 ** alongside the documentation.
2270 {"smime_verify_command", DT_STR, R_NONE, UL &SmimeVerifyCommand, 0},
2273 ** This command is used to verify S/MIME signatures of type \fTmultipart/signed\fP.
2276 {"smime_verify_opaque_command", DT_STR, R_NONE, UL &SmimeVerifyOpaqueCommand, 0},
2279 ** This command is used to verify S/MIME signatures of type
2280 ** \fTapplication/x-pkcs7-mime\fP.
2283 {"smime_sign_command", DT_STR, R_NONE, UL &SmimeSignCommand, 0},
2286 ** This command is used to created S/MIME signatures of type
2287 ** \fTmultipart/signed\fP, which can be read by all mail clients.
2290 {"smime_sign_opaque_command", DT_STR, R_NONE, UL &SmimeSignOpaqueCommand, 0},
2293 ** This command is used to created S/MIME signatures of type
2294 ** \fTapplication/x-pkcs7-signature\fP, which can only be handled by mail
2295 ** clients supporting the S/MIME extension.
2298 {"smime_encrypt_command", DT_STR, R_NONE, UL &SmimeEncryptCommand, 0},
2301 ** This command is used to create encrypted S/MIME messages.
2304 {"smime_pk7out_command", DT_STR, R_NONE, UL &SmimePk7outCommand, 0},
2307 ** This command is used to extract PKCS7 structures of S/MIME signatures,
2308 ** in order to extract the public X509 certificate(s).
2311 {"smime_get_cert_command", DT_STR, R_NONE, UL &SmimeGetCertCommand, 0},
2314 ** This command is used to extract X509 certificates from a PKCS7 structure.
2317 {"smime_get_signer_cert_command", DT_STR, R_NONE, UL &SmimeGetSignerCertCommand, 0},
2320 ** This command is used to extract only the signers X509 certificate from a S/MIME
2321 ** signature, so that the certificate's owner may get compared to the
2322 ** email's ``\fTFrom:\fP'' header field.
2325 {"smime_import_cert_command", DT_STR, R_NONE, UL &SmimeImportCertCommand, 0},
2328 ** This command is used to import a certificate via \fTsmime_keysng\fP.
2331 {"smime_get_cert_email_command", DT_STR, R_NONE, UL &SmimeGetCertEmailCommand, 0},
2334 ** This command is used to extract the mail address(es) used for storing
2335 ** X509 certificates, and for verification purposes (to check whether the
2336 ** certificate was issued for the sender's mailbox).
2339 {"smime_sign_as", DT_SYN, R_NONE, UL "smime_default_key", 0},
2340 {"smime_default_key", DT_STR, R_NONE, UL &SmimeDefaultKey, 0},
2343 ** This is the default key-pair to use for signing. This must be set to the
2344 ** keyid (the hash-value that OpenSSL generates) to work properly
2347 #if defined(USE_LIBESMTP)
2348 {"smtp_auth_username", DT_STR, R_NONE, UL &SmtpAuthUser, 0},
2351 ** Availability: SMTP
2354 ** Defines the username to use with SMTP AUTH. Setting this variable will
2355 ** cause Mutt-ng to attempt to use SMTP AUTH when sending.
2357 {"smtp_auth_password", DT_STR, R_NONE, UL &SmtpAuthPass, 0},
2360 ** Availability: SMTP
2363 ** Defines the password to use with SMTP AUTH. If ``$$smtp_auth_username''
2364 ** is set, but this variable is not, you will be prompted for a password
2367 ** \fBNote:\fP Storing passwords in a configuration file
2368 ** presents a security risk since the superuser of your machine may read it
2369 ** regardless of the file's permissions.
2371 {"smtp_host", DT_STR, R_NONE, UL &SmtpHost, 0},
2374 ** Availability: SMTP
2377 ** Defines the SMTP host which will be used to deliver mail, as opposed
2378 ** to invoking the sendmail binary. Setting this variable overrides the
2379 ** value of ``$$sendmail'', and any associated variables.
2381 {"smtp_port", DT_NUM, R_NONE, UL &SmtpPort, 25},
2384 ** Availability: SMTP
2387 ** Defines the port that the SMTP host is listening on for mail delivery.
2388 ** Must be specified as a number.
2390 ** Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP
2391 ** servers will probably desire 587, the mail submission port.
2394 #if defined(USE_SSL)||defined(USE_NSS)||defined(USE_GNUTLS)
2396 {"ssl_client_cert", DT_PATH, R_NONE, UL &SslClientCert, 0},
2399 ** Availability: SSL
2402 ** The file containing a client certificate and its associated private
2406 # if defined(USE_SSL)||defined(USE_GNUTLS)
2407 {"ssl_starttls", DT_QUAD, R_NONE, OPT_SSLSTARTTLS, M_YES},
2410 ** Availability: SSL or GNUTLS
2413 ** If \fIset\fP (the default), Mutt-ng will attempt to use STARTTLS on servers
2414 ** advertising the capability. When \fIunset\fP, Mutt-ng will not attempt to
2415 ** use STARTTLS regardless of the server's capabilities.
2418 {"certificate_file", DT_PATH, R_NONE, UL &SslCertFile, UL "~/.mutt_certificates"},
2421 ** Availability: SSL or NSS or GNUTLS
2424 ** This variable specifies the file where the certificates you trust
2425 ** are saved. When an unknown certificate is encountered, you are asked
2426 ** if you accept it or not. If you accept it, the certificate can also
2427 ** be saved in this file and further connections are automatically
2430 ** You can also manually add CA certificates in this file. Any server
2431 ** certificate that is signed with one of these CA certificates are
2432 ** also automatically accepted.
2434 ** Example: \fTset certificate_file=~/.muttng/certificates\fP
2437 {"ssl_usesystemcerts", DT_BOOL, R_NONE, OPTSSLSYSTEMCERTS, 1},
2440 ** Availability: SSL or NSS
2443 ** If set to \fIyes\fP, Mutt-ng will use CA certificates in the
2444 ** system-wide certificate store when checking if server certificate
2445 ** is signed by a trusted CA.
2447 {"entropy_file", DT_PATH, R_NONE, UL &SslEntropyFile, 0},
2450 ** Availability: SSL or NSS
2453 ** The file which includes random data that is used to initialize SSL
2454 ** library functions.
2456 {"ssl_use_sslv2", DT_BOOL, R_NONE, OPTSSLV2, 1},
2459 ** Availability: SSL or NSS
2462 ** This variables specifies whether to attempt to use SSLv2 in the
2463 ** SSL authentication process.
2466 {"ssl_use_sslv3", DT_BOOL, R_NONE, OPTSSLV3, 1},
2469 ** Availability: SSL or NSS or GNUTLS
2472 ** This variables specifies whether to attempt to use SSLv3 in the
2473 ** SSL authentication process.
2475 {"ssl_use_tlsv1", DT_BOOL, R_NONE, OPTTLSV1, 1},
2478 ** Availability: SSL or NSS or GNUTLS
2481 ** This variables specifies whether to attempt to use TLSv1 in the
2482 ** SSL authentication process.
2485 {"ssl_min_dh_prime_bits", DT_NUM, R_NONE, UL &SslDHPrimeBits, 0},
2488 ** Availability: GNUTLS
2491 ** This variable specifies the minimum acceptable prime size (in bits)
2492 ** for use in any Diffie-Hellman key exchange. A value of 0 will use
2493 ** the default from the GNUTLS library.
2495 {"ssl_ca_certificates_file", DT_PATH, R_NONE, UL &SslCACertFile, 0},
2498 ** This variable specifies a file containing trusted CA certificates.
2499 ** Any server certificate that is signed with one of these CA
2500 ** certificates are also automatically accepted.
2502 ** Example: \fTset ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt\fP
2506 {"pipe_split", DT_BOOL, R_NONE, OPTPIPESPLIT, 0},
2509 ** Used in connection with the \fIpipe-message\fP command and the ``tag-
2510 ** prefix'' or ``tag-prefix-cond'' operators.
2511 ** If this variable is \fIunset\fP, when piping a list of
2512 ** tagged messages Mutt-ng will concatenate the messages and will pipe them
2513 ** as a single folder. When \fIset\fP, Mutt-ng will pipe the messages one by one.
2514 ** In both cases the messages are piped in the current sorted order,
2515 ** and the ``$$pipe_sep'' separator is added after each message.
2517 {"pipe_decode", DT_BOOL, R_NONE, OPTPIPEDECODE, 0},
2520 ** Used in connection with the \fIpipe-message\fP command. When \fIunset\fP,
2521 ** Mutt-ng will pipe the messages without any preprocessing. When \fIset\fP, Mutt-ng
2522 ** will weed headers and will attempt to PGP/MIME decode the messages
2525 {"pipe_sep", DT_STR, R_NONE, UL &PipeSep, UL "\n"},
2528 ** The separator to add between messages when piping a list of tagged
2529 ** messages to an external Unix command.
2532 {"pop_authenticators", DT_STR, R_NONE, UL &PopAuthenticators, UL 0},
2535 ** Availability: POP
2538 ** This is a colon-delimited list of authentication methods Mutt-ng may
2539 ** attempt to use to log in to an POP server, in the order Mutt-ng should
2540 ** try them. Authentication methods are either ``\fTuser\fP'', ``\fTapop\fP''
2541 ** or any SASL mechanism, eg ``\fTdigest-md5\fP'', ``\fTgssapi\fP'' or ``\fTcram-md5\fP''.
2543 ** This parameter is case-insensitive. If this parameter is \fIunset\fP
2544 ** (the default) Mutt-ng will try all available methods, in order from
2545 ** most-secure to least-secure.
2547 ** Example: \fTset pop_authenticators="digest-md5:apop:user"\fP
2549 {"pop_auth_try_all", DT_BOOL, R_NONE, OPTPOPAUTHTRYALL, 1},
2552 ** Availability: POP
2555 ** If \fIset\fP, Mutt-ng will try all available methods. When \fIunset\fP, Mutt-ng will
2556 ** only fall back to other authentication methods if the previous
2557 ** methods are unavailable. If a method is available but authentication
2558 ** fails, Mutt-ng will not connect to the POP server.
2560 {"pop_checkinterval", DT_NUM, R_NONE, UL &PopCheckTimeout, 60},
2563 ** Availability: POP
2566 ** This variable configures how often (in seconds) POP should look for
2569 {"pop_delete", DT_QUAD, R_NONE, OPT_POPDELETE, M_ASKNO},
2572 ** Availability: POP
2575 ** If \fIset\fP, Mutt-ng will delete successfully downloaded messages from the POP
2576 ** server when using the ``fetch-mail'' function. When \fIunset\fP, Mutt-ng will
2577 ** download messages but also leave them on the POP server.
2579 {"pop_host", DT_STR, R_NONE, UL &PopHost, UL ""},
2582 ** Availability: POP
2585 ** The name of your POP server for the ``fetch-mail'' function. You
2586 ** can also specify an alternative port, username and password, i.e.:
2588 ** \fT[pop[s]://][username[:password]@]popserver[:port]\fP
2590 ** \fBNote:\fP Storing passwords in a configuration file
2591 ** presents a security risk since the superuser of your machine may read it
2592 ** regardless of the file's permissions.
2594 {"pop_last", DT_BOOL, R_NONE, OPTPOPLAST, 0},
2597 ** Availability: POP
2600 ** If this variable is \fIset\fP, Mutt-ng will try to use the ``\fTLAST\fP'' POP command
2601 ** for retrieving only unread messages from the POP server when using
2602 ** the ``fetch-mail'' function.
2604 {"pop_reconnect", DT_QUAD, R_NONE, OPT_POPRECONNECT, M_ASKYES},
2607 ** Availability: POP
2610 ** Controls whether or not Mutt-ng will try to reconnect to a POP server when the
2611 ** connection is lost.
2613 {"pop_user", DT_STR, R_NONE, UL &PopUser, 0},
2616 ** Availability: POP
2619 ** Your login name on the POP server.
2621 ** This variable defaults to your user name on the local machine.
2623 {"pop_pass", DT_STR, R_NONE, UL &PopPass, UL ""},
2626 ** Availability: POP
2629 ** Specifies the password for your POP account. If \fIunset\fP, Mutt-ng will
2630 ** prompt you for your password when you open POP mailbox.
2632 ** \fBNote:\fP Storing passwords in a configuration file
2633 ** presents a security risk since the superuser of your machine may read it
2634 ** regardless of the file's permissions.
2636 #endif /* USE_POP */
2637 {"post_indent_string", DT_STR, R_NONE, UL &PostIndentString, UL ""},
2640 ** Similar to the ``$$attribution'' variable, Mutt-ng will append this
2641 ** string after the inclusion of a message which is being replied to.
2643 {"post_indent_str", DT_SYN, R_NONE, UL "post_indent_string", 0},
2647 {"post_moderated", DT_QUAD, R_NONE, OPT_TOMODERATED, M_ASKYES},
2650 ** Availability: NNTP
2653 ** If set to \fIyes\fP, Mutt-ng will post articles to newsgroup that have
2654 ** not permissions to post (e.g. moderated).
2656 ** \fBNote:\fP if the newsserver
2657 ** does not support posting to that newsgroup or a group is totally read-only, that
2658 ** posting will not have any effect.
2661 {"postpone", DT_QUAD, R_NONE, OPT_POSTPONE, M_ASKYES},
2664 ** Controls whether or not messages are saved in the ``$$postponed''
2665 ** mailbox when you elect not to send immediately.
2667 {"postponed", DT_PATH, R_NONE, UL &Postponed, UL "~/postponed"},
2670 ** Mutt-ng allows you to indefinitely ``$postpone sending a message'' which
2671 ** you are editing. When you choose to postpone a message, Mutt-ng saves it
2672 ** in the mailbox specified by this variable. Also see the ``$$postpone''
2676 {"preconnect", DT_STR, R_NONE, UL &Preconnect, UL 0},
2679 ** If \fIset\fP, a shell command to be executed if Mutt-ng fails to establish
2680 ** a connection to the server. This is useful for setting up secure
2681 ** connections, e.g. with \fTssh(1)\fP. If the command returns a nonzero
2682 ** status, Mutt-ng gives up opening the server. Example:
2684 ** \fTpreconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net
2685 ** sleep 20 < /dev/null > /dev/null"\fP
2687 ** Mailbox ``foo'' on mailhost.net can now be reached
2688 ** as ``{localhost:1234}foo''.
2690 ** \fBNote:\fP For this example to work, you must be able to log in to the
2691 ** remote machine without having to enter a password.
2693 #endif /* USE_SOCKET */
2694 {"print", DT_QUAD, R_NONE, OPT_PRINT, M_ASKNO},
2697 ** Controls whether or not Mutt-ng really prints messages.
2698 ** This is set to \fIask-no\fP by default, because some people
2699 ** accidentally hit ``p'' often.
2701 {"print_command", DT_PATH, R_NONE, UL &PrintCmd, UL "lpr"},
2704 ** This specifies the command pipe that should be used to print messages.
2706 {"print_cmd", DT_SYN, R_NONE, UL "print_command", 0},
2709 {"print_decode", DT_BOOL, R_NONE, OPTPRINTDECODE, 1},
2712 ** Used in connection with the print-message command. If this
2713 ** option is \fIset\fP, the message is decoded before it is passed to the
2714 ** external command specified by $$print_command. If this option
2715 ** is \fIunset\fP, no processing will be applied to the message when
2716 ** printing it. The latter setting may be useful if you are using
2717 ** some advanced printer filter which is able to properly format
2718 ** e-mail messages for printing.
2720 {"print_split", DT_BOOL, R_NONE, OPTPRINTSPLIT, 0},
2723 ** Used in connection with the print-message command. If this option
2724 ** is \fIset\fP, the command specified by $$print_command is executed once for
2725 ** each message which is to be printed. If this option is \fIunset\fP,
2726 ** the command specified by $$print_command is executed only once, and
2727 ** all the messages are concatenated, with a form feed as the message
2730 ** Those who use the \fTenscript(1)\fP program's mail-printing mode will
2731 ** most likely want to set this option.
2733 {"prompt_after", DT_BOOL, R_NONE, OPTPROMPTAFTER, 1},
2736 ** If you use an \fIexternal\fP ``$$pager'', setting this variable will
2737 ** cause Mutt-ng to prompt you for a command when the pager exits rather
2738 ** than returning to the index menu. If \fIunset\fP, Mutt-ng will return to the
2739 ** index menu when the external pager exits.
2741 {"query_command", DT_PATH, R_NONE, UL &QueryCmd, UL ""},
2744 ** This specifies the command that Mutt-ng will use to make external address
2745 ** queries. The string should contain a \fT%s\fP, which will be substituted
2746 ** with the query string the user types. See ``$query'' for more
2749 {"quit", DT_QUAD, R_NONE, OPT_QUIT, M_YES},
2752 ** This variable controls whether ``quit'' and ``exit'' actually quit
2753 ** from Mutt-ng. If it set to \fIyes\fP, they do quit, if it is set to \fIno\fP, they
2754 ** have no effect, and if it is set to \fIask-yes\fP or \fIask-no\fP, you are
2755 ** prompted for confirmation when you try to quit.
2757 {"quote_empty", DT_BOOL, R_NONE, OPTQUOTEEMPTY, 1},
2760 ** Controls whether or not empty lines will be quoted using
2761 ** ``$indent_string''.
2763 {"quote_quoted", DT_BOOL, R_NONE, OPTQUOTEQUOTED, 0},
2766 ** Controls how quoted lines will be quoted. If \fIset\fP, one quote
2767 ** character will be added to the end of existing prefix. Otherwise,
2768 ** quoted lines will be prepended by ``$indent_string''.
2770 {"quote_regexp", DT_RX, R_PAGER, UL &QuoteRegexp, UL "^([ \t]*[|>:}#])+"},
2773 ** A regular expression used in the internal-pager to determine quoted
2774 ** sections of text in the body of a message.
2776 ** \fBNote:\fP In order to use the \fIquoted\fP\fBx\fP patterns in the
2777 ** internal pager, you need to set this to a regular expression that
2778 ** matches \fIexactly\fP the quote characters at the beginning of quoted
2781 {"read_inc", DT_NUM, R_NONE, UL &ReadInc, 10},
2784 ** If set to a value greater than 0, Mutt-ng will display which message it
2785 ** is currently on when reading a mailbox. The message is printed after
2786 ** \fIread_inc\fP messages have been read (e.g., if set to 25, Mutt-ng will
2787 ** print a message when it reads message 25, and then again when it gets
2788 ** to message 50). This variable is meant to indicate progress when
2789 ** reading large mailboxes which may take some time.
2790 ** When set to 0, only a single message will appear before the reading
2793 ** Also see the ``$$write_inc'' variable.
2795 {"read_only", DT_BOOL, R_NONE, OPTREADONLY, 0},
2798 ** If set, all folders are opened in read-only mode.
2800 {"realname", DT_STR, R_BOTH, UL &Realname, 0},
2803 ** This variable specifies what ``real'' or ``personal'' name should be used
2804 ** when sending messages.
2806 ** By default, this is the GECOS field from \fT/etc/passwd\fP.
2809 ** variable will \fInot\fP be used when the user has set a real name
2810 ** in the $$from variable.
2812 {"recall", DT_QUAD, R_NONE, OPT_RECALL, M_ASKYES},
2815 ** Controls whether or not Mutt-ng recalls postponed messages
2816 ** when composing a new message. Also see ``$$postponed''.
2818 ** Setting this variable to \fIyes\fP is not generally useful, and thus not
2821 {"record", DT_PATH, R_NONE, UL &Outbox, UL ""},
2824 ** This specifies the file into which your outgoing messages should be
2825 ** appended. (This is meant as the primary method for saving a copy of
2826 ** your messages, but another way to do this is using the ``$my_hdr''
2827 ** command to create a \fTBcc:\fP header field with your email address in it.)
2829 ** The value of \fI$$record\fP is overridden by the ``$$force_name'' and
2830 ** ``$$save_name'' variables, and the ``$fcc-hook'' command.
2832 {"reply_regexp", DT_RX, R_INDEX|R_RESORT, UL &ReplyRegexp, UL "^(re([\\[0-9\\]+])*|aw):[ \t]*"},
2835 ** A regular expression used to recognize reply messages when threading
2836 ** and replying. The default value corresponds to the English ``Re:'' and
2837 ** the German ``Aw:''.
2839 {"reply_self", DT_BOOL, R_NONE, OPTREPLYSELF, 0},
2842 ** If \fIunset\fP and you are replying to a message sent by you, Mutt-ng will
2843 ** assume that you want to reply to the recipients of that message rather
2844 ** than to yourself.
2846 {"reply_to", DT_QUAD, R_NONE, OPT_REPLYTO, M_ASKYES},
2849 ** If \fIset\fP, when replying to a message, Mutt-ng will use the address listed
2850 ** in the ``\fTReply-To:\fP'' header field as the recipient of the reply. If \fIunset\fP,
2851 ** it will use the address in the ``\fTFrom:\fP'' header field instead.
2854 ** option is useful for reading a mailing list that sets the ``\fTReply-To:\fP''
2855 ** header field to the list address and you want to send a private
2856 ** message to the author of a message.
2858 {"resolve", DT_BOOL, R_NONE, OPTRESOLVE, 1},
2861 ** When set, the cursor will be automatically advanced to the next
2862 ** (possibly undeleted) message whenever a command that modifies the
2863 ** current message is executed.
2865 {"reverse_alias", DT_BOOL, R_BOTH, OPTREVALIAS, 0},
2868 ** This variable controls whether or not Mutt-ng will display the ``personal''
2869 ** name from your aliases in the index menu if it finds an alias that
2870 ** matches the message's sender. For example, if you have the following
2873 ** \fTalias juser abd30425@somewhere.net (Joe User)\fP
2875 ** and then you receive mail which contains the following header:
2877 ** \fTFrom: abd30425@somewhere.net\fP
2879 ** It would be displayed in the index menu as ``Joe User'' instead of
2880 ** ``abd30425@somewhere.net.'' This is useful when the person's e-mail
2881 ** address is not human friendly (like CompuServe addresses).
2883 {"reverse_name", DT_BOOL, R_BOTH, OPTREVNAME, 0},
2886 ** It may sometimes arrive that you receive mail to a certain machine,
2887 ** move the messages to another machine, and reply to some the messages
2888 ** from there. If this variable is \fIset\fP, the default \fTFrom:\fP line of
2889 ** the reply messages is built using the address where you received the
2890 ** messages you are replying to \fBif\fP that address matches your
2891 ** alternates. If the variable is \fIunset\fP, or the address that would be
2892 ** used doesn't match your alternates, the \fTFrom:\fP line will use
2893 ** your address on the current machine.
2895 {"reverse_realname", DT_BOOL, R_BOTH, OPTREVREAL, 1},
2898 ** This variable fine-tunes the behaviour of the $reverse_name feature.
2899 ** When it is \fIset\fP, Mutt-ng will use the address from incoming messages as-is,
2900 ** possibly including eventual real names. When it is \fIunset\fP, Mutt-ng will
2901 ** override any such real names with the setting of the $realname variable.
2903 {"rfc2047_parameters", DT_BOOL, R_NONE, OPTRFC2047PARAMS, 0},
2906 ** When this variable is \fIset\fP, Mutt-ng will decode RFC-2047-encoded MIME
2907 ** parameters. You want to set this variable when Mutt-ng suggests you
2908 ** to save attachments to files named like this:
2910 ** \fT=?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=\fP
2912 ** When this variable is \fIset\fP interactively, the change doesn't have
2913 ** the desired effect before you have changed folders.
2915 ** Note that this use of RFC 2047's encoding is explicitly,
2916 ** prohibited by the standard, but nevertheless encountered in the
2919 ** Also note that setting this parameter will \fInot\fP have the effect
2920 ** that Mutt-ng \fIgenerates\fP this kind of encoding. Instead, Mutt-ng will
2921 ** unconditionally use the encoding specified in RFC 2231.
2923 {"save_address", DT_BOOL, R_NONE, OPTSAVEADDRESS, 0},
2926 ** If \fIset\fP, Mutt-ng will take the sender's full address when choosing a
2927 ** default folder for saving a mail. If ``$$save_name'' or ``$$force_name''
2928 ** is \fIset\fP too, the selection of the fcc folder will be changed as well.
2930 {"save_empty", DT_BOOL, R_NONE, OPTSAVEEMPTY, 1},
2933 ** When \fIunset\fP, mailboxes which contain no saved messages will be removed
2934 ** when closed (the exception is ``$$spoolfile'' which is never removed).
2935 ** If \fIset\fP, mailboxes are never removed.
2937 ** \fBNote:\fP This only applies to mbox and MMDF folders, Mutt-ng does not
2938 ** delete MH and Maildir directories.
2940 {"save_name", DT_BOOL, R_NONE, OPTSAVENAME, 0},
2943 ** This variable controls how copies of outgoing messages are saved.
2944 ** When set, a check is made to see if a mailbox specified by the
2945 ** recipient address exists (this is done by searching for a mailbox in
2946 ** the ``$$folder'' directory with the \fIusername\fP part of the
2947 ** recipient address). If the mailbox exists, the outgoing message will
2948 ** be saved to that mailbox, otherwise the message is saved to the
2949 ** ``$$record'' mailbox.
2951 ** Also see the ``$$force_name'' variable.
2953 {"score", DT_BOOL, R_NONE, OPTSCORE, 1},
2956 ** When this variable is \fIunset\fP, scoring is turned off. This can
2957 ** be useful to selectively disable scoring for certain folders when the
2958 ** ``$$score_threshold_delete'' variable and friends are used.
2961 {"score_threshold_delete", DT_NUM, R_NONE, UL &ScoreThresholdDelete, UL -1},
2964 ** Messages which have been assigned a score equal to or lower than the value
2965 ** of this variable are automatically marked for deletion by Mutt-ng. Since
2966 ** Mutt-ng scores are always greater than or equal to zero, the default setting
2967 ** of this variable will never mark a message for deletion.
2969 {"score_threshold_flag", DT_NUM, R_NONE, UL &ScoreThresholdFlag, 9999},
2972 ** Messages which have been assigned a score greater than or equal to this
2973 ** variable's value are automatically marked ``flagged''.
2975 {"score_threshold_read", DT_NUM, R_NONE, UL &ScoreThresholdRead, UL -1},
2978 ** Messages which have been assigned a score equal to or lower than the value
2979 ** of this variable are automatically marked as read by Mutt-ng. Since
2980 ** Mutt-ng scores are always greater than or equal to zero, the default setting
2981 ** of this variable will never mark a message read.
2983 {"send_charset", DT_STR, R_NONE, UL &SendCharset, UL "us-ascii:iso-8859-1:utf-8"},
2986 ** A list of character sets for outgoing messages. Mutt-ng will use the
2987 ** first character set into which the text can be converted exactly.
2988 ** If your ``$$charset'' is not \fTiso-8859-1\fP and recipients may not
2989 ** understand \fTUTF-8\fP, it is advisable to include in the list an
2990 ** appropriate widely used standard character set (such as
2991 ** \fTiso-8859-2\fP, \fTkoi8-r\fP or \fTiso-2022-jp\fP) either
2992 ** instead of or after \fTiso-8859-1\fP.
2994 {"sendmail", DT_PATH, R_NONE, UL &Sendmail, UL SENDMAIL " -oem -oi"},
2997 ** Specifies the program and arguments used to deliver mail sent by Mutt-ng.
2998 ** Mutt-ng expects that the specified program interprets additional
2999 ** arguments as recipient addresses.
3001 {"sendmail_wait", DT_NUM, R_NONE, UL &SendmailWait, 0},
3004 ** Specifies the number of seconds to wait for the ``$$sendmail'' process
3005 ** to finish before giving up and putting delivery in the background.
3007 ** Mutt-ng interprets the value of this variable as follows:
3009 ** .dt >0 .dd number of seconds to wait for sendmail to finish before continuing
3010 ** .dt 0 .dd wait forever for sendmail to finish
3011 ** .dt <0 .dd always put sendmail in the background without waiting
3014 ** Note that if you specify a value other than 0, the output of the child
3015 ** process will be put in a temporary file. If there is some error, you
3016 ** will be informed as to where to find the output.
3018 {"shell", DT_PATH, R_NONE, UL &Shell, 0},
3021 ** Command to use when spawning a subshell. By default, the user's login
3022 ** shell from \fT/etc/passwd\fP is used.
3025 {"save_unsubscribed", DT_BOOL, R_NONE, OPTSAVEUNSUB, 0},
3028 ** Availability: NNTP
3031 ** When \fIset\fP, info about unsubscribed newsgroups will be saved into the
3032 ** ``newsrc'' file and into the news cache.
3035 {"shorten_hierarchy", DT_SYN, R_NONE, UL "sidebar_shorten_hierarchy", 0 },
3037 {"show_new_news", DT_BOOL, R_NONE, OPTSHOWNEWNEWS, 1},
3040 ** Availability: NNTP
3043 ** If \fIset\fP, the newsserver will be asked for new newsgroups on entering
3044 ** the browser. Otherwise, it will be done only once for a newsserver.
3045 ** Also controls whether or not the number of new articles of subscribed
3046 ** newsgroups will be checked.
3048 {"show_only_unread", DT_BOOL, R_NONE, OPTSHOWONLYUNREAD, 0},
3051 ** Availability: NNTP
3054 ** If \fIset\fP, only subscribed newsgroups that contain unread articles
3055 ** will be displayed in the newsgroup browser.
3058 {"sig_dashes", DT_BOOL, R_NONE, OPTSIGDASHES, 1},
3061 ** If set, a line containing ``\fT-- \fP'' (dash, dash, space)
3062 ** will be inserted before your ``$$signature''. It is \fBstrongly\fP
3063 ** recommended that you not unset this variable unless your ``signature''
3064 ** contains just your name. The reason for this is because many software
3065 ** packages use ``\fT-- \n\fP'' to detect your signature.
3067 ** For example, Mutt-ng has the ability to highlight
3068 ** the signature in a different color in the builtin pager.
3070 {"sig_on_top", DT_BOOL, R_NONE, OPTSIGONTOP, 0},
3073 ** If \fIset\fP, the signature will be included before any quoted or forwarded
3074 ** text. It is \fBstrongly\fP recommended that you do not set this variable
3075 ** unless you really know what you are doing, and are prepared to take
3076 ** some heat from netiquette guardians.
3078 {"signature", DT_PATH, R_NONE, UL &Signature, UL "~/.signature"},
3081 ** Specifies the filename of your signature, which is appended to all
3082 ** outgoing messages. If the filename ends with a pipe (``\fT|\fP''), it is
3083 ** assumed that filename is a shell command and input should be read from
3086 {"signoff_string", DT_STR, R_NONE, UL &SignOffString, UL 0},
3089 ** If \fIset\fP, this string will be inserted before the signature. This is useful
3090 ** for people that want to sign off every message they send with their name.
3092 ** If you want to insert your website's URL, additional contact information or
3093 ** witty quotes into your mails, better use a signature file instead of
3094 ** the signoff string.
3096 {"simple_search", DT_STR, R_NONE, UL &SimpleSearch, UL "~f %s | ~s %s"},
3099 ** Specifies how Mutt-ng should expand a simple search into a real search
3100 ** pattern. A simple search is one that does not contain any of the ~
3101 ** operators. See ``$patterns'' for more information on search patterns.
3103 ** For example, if you simply type ``joe'' at a search or limit prompt, Mutt-ng
3104 ** will automatically expand it to the value specified by this variable.
3105 ** For the default value it would be:
3107 ** \fT~f joe | ~s joe\fP
3109 {"smart_wrap", DT_BOOL, R_PAGER, OPTWRAP, 1},
3112 ** Controls the display of lines longer than the screen width in the
3113 ** internal pager. If \fIset\fP, long lines are wrapped at a word boundary.
3114 ** If \fIunset\fP, lines are simply wrapped at the screen edge. Also see the
3115 ** ``$$markers'' variable.
3117 {"smileys", DT_RX, R_PAGER, UL &Smileys, UL "(>From )|(:[-^]?[][)(><}{|/DP])"},
3120 ** The \fIpager\fP uses this variable to catch some common false
3121 ** positives of ``$$quote_regexp'', most notably smileys in the beginning
3124 {"sleep_time", DT_NUM, R_NONE, UL &SleepTime, 1},
3127 ** Specifies time, in seconds, to pause while displaying certain informational
3128 ** messages, while moving from folder to folder and after expunging
3129 ** messages from the current folder. The default is to pause one second, so
3130 ** a value of zero for this option suppresses the pause.
3132 {"sort", DT_SORT, R_INDEX|R_RESORT, UL &Sort, SORT_DATE},
3135 ** Specifies how to sort messages in the \fIindex\fP menu. Valid values
3139 ** . date or date-sent
3142 ** . mailbox-order (unsorted)
3151 ** You may optionally use the ``reverse-'' prefix to specify reverse sorting
3152 ** order (example: \fTset sort=reverse-date-sent\fP).
3154 {"sort_alias", DT_SORT|DT_SORT_ALIAS, R_NONE, UL &SortAlias, SORT_ALIAS},
3157 ** Specifies how the entries in the ``alias'' menu are sorted. The
3158 ** following are legal values:
3161 ** . address (sort alphabetically by email address)
3162 ** . alias (sort alphabetically by alias name)
3163 ** . unsorted (leave in order specified in .muttrc)
3166 {"sort_aux", DT_SORT|DT_SORT_AUX, R_INDEX|R_RESORT_BOTH, UL &SortAux, SORT_DATE},
3169 ** When sorting by threads, this variable controls how threads are sorted
3170 ** in relation to other threads, and how the branches of the thread trees
3171 ** are sorted. This can be set to any value that ``$$sort'' can, except
3172 ** threads (in that case, Mutt-ng will just use date-sent). You can also
3173 ** specify the ``last-'' prefix in addition to ``reverse-'' prefix, but last-
3174 ** must come after reverse-. The last- prefix causes messages to be
3175 ** sorted against its siblings by which has the last descendant, using
3176 ** the rest of sort_aux as an ordering.
3178 ** For instance, \fTset sort_aux=last-date-received\fP would mean that if
3179 ** a new message is received in a thread, that thread becomes the last one
3180 ** displayed (or the first, if you have \fTset sort=reverse-threads\fP.)
3182 ** \fBNote:\fP For reversed ``$$sort'' order $$sort_aux is reversed again
3183 ** (which is not the right thing to do, but kept to not break any existing
3184 ** configuration setting).
3186 {"sort_browser", DT_SORT|DT_SORT_BROWSER, R_NONE, UL &BrowserSort, SORT_ALPHA},
3189 ** Specifies how to sort entries in the file browser. By default, the
3190 ** entries are sorted alphabetically. Valid values:
3193 ** . alpha (alphabetically)
3199 ** You may optionally use the ``reverse-'' prefix to specify reverse sorting
3200 ** order (example: \fTset sort_browser=reverse-date\fP).
3202 {"sort_re", DT_BOOL, R_INDEX|R_RESORT|R_RESORT_INIT, OPTSORTRE, 1},
3205 ** This variable is only useful when sorting by threads with
3206 ** ``$$strict_threads'' \fIunset\fP. In that case, it changes the heuristic
3207 ** Mutt-ng uses to thread messages by subject. With $$sort_re \fIset\fP,
3208 ** Mutt-ng will only attach a message as the child of another message by
3209 ** subject if the subject of the child message starts with a substring
3210 ** matching the setting of ``$$reply_regexp''. With $$sort_re \fIunset\fP,
3211 ** Mutt-ng will attach the message whether or not this is the case,
3212 ** as long as the non-``$$reply_regexp'' parts of both messages are identical.
3214 {"spam_separator", DT_STR, R_NONE, UL &SpamSep, UL ","},
3217 ** ``$spam_separator'' controls what happens when multiple spam headers
3218 ** are matched: if \fIunset\fP, each successive header will overwrite any
3219 ** previous matches value for the spam label. If \fIset\fP, each successive
3220 ** match will append to the previous, using ``$spam_separator'' as a
3223 {"spoolfile", DT_PATH, R_NONE, UL &Spoolfile, 0},
3226 ** If your spool mailbox is in a non-default place where Mutt-ng cannot find
3227 ** it, you can specify its location with this variable. Mutt-ng will
3228 ** automatically set this variable to the value of the environment
3229 ** variable $$$MAIL if it is not set.
3231 {"status_chars", DT_STR, R_BOTH, UL &StChars, UL "-*%A"},
3234 ** Controls the characters used by the ``\fT%r\fP'' indicator in
3235 ** ``$$status_format''. The first character is used when the mailbox is
3236 ** unchanged. The second is used when the mailbox has been changed, and
3237 ** it needs to be resynchronized. The third is used if the mailbox is in
3238 ** read-only mode, or if the mailbox will not be written when exiting
3239 ** that mailbox (You can toggle whether to write changes to a mailbox
3240 ** with the toggle-write operation, bound by default to ``\fT%\fP'').
3241 ** The fourth is used to indicate that the current folder has been
3242 ** opened in attach-message mode (Certain operations like composing
3243 ** a new mail, replying, forwarding, etc. are not permitted in this mode).
3245 {"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)---"},
3248 ** Controls the format of the status line displayed in the \fIindex\fP
3249 ** menu. This string is similar to ``$$index_format'', but has its own
3250 ** set of \fTprintf(3)\fP-like sequences:
3253 ** .dt %b .dd number of mailboxes with new mail *
3254 ** .dt %B .dd the short pathname of the current mailbox
3255 ** .dt %d .dd number of deleted messages *
3256 ** .dt %f .dd the full pathname of the current mailbox
3257 ** .dt %F .dd number of flagged messages *
3258 ** .dt %h .dd local hostname
3259 ** .dt %l .dd size (in bytes) of the current mailbox *
3260 ** .dt %L .dd size (in bytes) of the messages shown
3261 ** (i.e., which match the current limit) *
3262 ** .dt %m .dd the number of messages in the mailbox *
3263 ** .dt %M .dd the number of messages shown (i.e., which match the current limit) *
3264 ** .dt %n .dd number of new messages in the mailbox *
3265 ** .dt %o .dd number of old unread messages *
3266 ** .dt %p .dd number of postponed messages *
3267 ** .dt %P .dd percentage of the way through the index
3268 ** .dt %r .dd modified/read-only/won't-write/attach-message indicator,
3269 ** according to $$status_chars
3270 ** .dt %s .dd current sorting mode ($$sort)
3271 ** .dt %S .dd current aux sorting method ($$sort_aux)
3272 ** .dt %t .dd number of tagged messages *
3273 ** .dt %u .dd number of unread messages *
3274 ** .dt %v .dd Mutt-ng version string
3275 ** .dt %V .dd currently active limit pattern, if any *
3276 ** .dt %>X .dd right justify the rest of the string and pad with "X"
3277 ** .dt %|X .dd pad to the end of the line with "X"
3280 ** * = can be optionally printed if nonzero
3282 ** Some of the above sequences can be used to optionally print a string
3283 ** if their value is nonzero. For example, you may only want to see the
3284 ** number of flagged messages if such messages exist, since zero is not
3285 ** particularly meaningful. To optionally print a string based upon one
3286 ** of the above sequences, the following construct is used
3288 ** \fT%?<sequence_char>?<optional_string>?\fP
3290 ** where \fIsequence_char\fP is a character from the table above, and
3291 ** \fIoptional_string\fP is the string you would like printed if
3292 ** \fIsequence_char\fP is nonzero. \fIoptional_string\fP \fBmay\fP contain
3293 ** other sequences as well as normal text, but you may \fBnot\fP nest
3294 ** optional strings.
3296 ** Here is an example illustrating how to optionally print the number of
3297 ** new messages in a mailbox:
3299 ** \fT%?n?%n new messages.?\fP
3301 ** Additionally you can switch between two strings, the first one, if a
3302 ** value is zero, the second one, if the value is nonzero, by using the
3303 ** following construct:
3305 ** \fT%?<sequence_char>?<if_string>&<else_string>?\fP
3307 ** You can additionally force the result of any \fTprintf(3)\fP-like sequence
3308 ** to be lowercase by prefixing the sequence character with an underscore
3309 ** (\fT_\fP) sign. For example, if you want to display the local hostname in
3310 ** lowercase, you would use:
3314 ** If you prefix the sequence character with a colon (\fT:\fP) character, Mutt-ng
3315 ** will replace any dots in the expansion by underscores. This might be helpful
3316 ** with IMAP folders that don't like dots in folder names.
3318 {"status_on_top", DT_BOOL, R_BOTH, OPTSTATUSONTOP, 0},
3321 ** Setting this variable causes the ``status bar'' to be displayed on
3322 ** the first line of the screen rather than near the bottom.
3324 {"strict_mime", DT_BOOL, R_NONE, OPTSTRICTMIME, 1},
3327 ** When \fIunset\fP, non MIME-compliant messages that doesn't have any
3328 ** charset indication in the ``\fTContent-Type:\fP'' header field can
3329 ** be displayed (non MIME-compliant messages are often generated by old
3330 ** mailers or buggy mailers like MS Outlook Express).
3331 ** See also $$assumed_charset.
3333 ** This option also replaces linear-white-space between encoded-word
3334 ** and *text to a single space to prevent the display of MIME-encoded
3335 ** ``\fTSubject:\fP'' header field from being devided into multiple lines.
3337 {"strict_threads", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTSTRICTTHREADS, 0},
3340 ** If \fIset\fP, threading will only make use of the ``\fTIn-Reply-To:\fP'' and
3341 ** ``\fTReferences:\fP'' header fields when you ``$$sort'' by message threads. By
3342 ** default, messages with the same subject are grouped together in
3343 ** ``pseudo threads.'' This may not always be desirable, such as in a
3344 ** personal mailbox where you might have several unrelated messages with
3345 ** the subject ``hi'' which will get grouped together.
3347 {"strip_was", DT_BOOL, R_NONE, OPTSTRIPWAS, 0},
3350 ** When \fIset\fP, mutt-ng will remove the trailing part of the ``\fTSubject:\fP''
3351 ** line which matches $$strip_was_regex when replying. This is useful to
3352 ** properly react on subject changes and reduce ``subject noise.'' (esp. in Usenet)
3354 {"strip_was_regex", DT_RX, R_NONE, UL &StripWasRegexp, UL "\\([Ww][Aa][RrSs]: .*\\)[ ]*$"},
3357 ** When non-empty and $$strip_was is \fIset\fP, mutt-ng will remove this
3358 ** trailing part of the ``Subject'' line when replying if it won't be empty
3361 {"stuff_quoted", DT_BOOL, R_BOTH, OPTSTUFFQUOTED, 0},
3364 ** If \fIset\fP, attachments with flowed format will have their quoting ``stuffed'',
3365 ** i.e. a space will be inserted between the quote characters and the actual
3368 {"suspend", DT_BOOL, R_NONE, OPTSUSPEND, 1},
3371 ** When \fIunset\fP, Mutt-ng won't stop when the user presses the terminal's
3372 ** \fIsusp\fP key, usually \fTCTRL+Z\fP. This is useful if you run Mutt-ng
3373 ** inside an xterm using a command like ``\fTxterm -e muttng\fP.''
3375 {"text_flowed", DT_BOOL, R_NONE, OPTTEXTFLOWED, 0},
3378 ** When \fIset\fP, Mutt-ng will generate \fTtext/plain; format=flowed\fP attachments.
3379 ** This format is easier to handle for some mailing software, and generally
3380 ** just looks like ordinary text. To actually make use of this format's
3381 ** features, you'll need support in your editor.
3383 ** Note that $$indent_string is ignored when this option is set.
3385 {"thread_received", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTTHREADRECEIVED, 0},
3388 ** When \fIset\fP, Mutt-ng uses the date received rather than the date sent
3389 ** to thread messages by subject.
3391 {"thorough_search", DT_BOOL, R_NONE, OPTTHOROUGHSRC, 0},
3394 ** Affects the \fT~b\fP and \fT~h\fP search operations described in
3395 ** section ``$patterns'' above. If \fIset\fP, the headers and attachments of
3396 ** messages to be searched are decoded before searching. If \fIunset\fP,
3397 ** messages are searched as they appear in the folder.
3399 {"tilde", DT_BOOL, R_PAGER, OPTTILDE, 0},
3402 ** When \fIset\fP, the internal-pager will pad blank lines to the bottom of the
3403 ** screen with a tilde (~).
3405 {"timeout", DT_NUM, R_NONE, UL &Timeout, 600},
3408 ** This variable controls the \fInumber of seconds\fP Mutt-ng will wait
3409 ** for a key to be pressed in the main menu before timing out and
3410 ** checking for new mail. A value of zero or less will cause Mutt-ng
3411 ** to never time out.
3413 {"tmpdir", DT_PATH, R_NONE, UL &Tempdir, 0},
3416 ** This variable allows you to specify where Mutt-ng will place its
3417 ** temporary files needed for displaying and composing messages. If
3418 ** this variable is not set, the environment variable \fT$$$TMPDIR\fP is
3419 ** used. If \fT$$$TMPDIR\fP is not set then "\fT/tmp\fP" is used.
3421 {"to_chars", DT_STR, R_BOTH, UL &Tochars, UL " +TCFL"},
3424 ** Controls the character used to indicate mail addressed to you. The
3425 ** first character is the one used when the mail is NOT addressed to your
3426 ** address (default: space). The second is used when you are the only
3427 ** recipient of the message (default: +). The third is when your address
3428 ** appears in the ``\fTTo:\fP'' header field, but you are not the only recipient of
3429 ** the message (default: T). The fourth character is used when your
3430 ** address is specified in the ``\fTCc:\fP'' header field, but you are not the only
3431 ** recipient. The fifth character is used to indicate mail that was sent
3432 ** by \fIyou\fP. The sixth character is used to indicate when a mail
3433 ** was sent to a mailing-list you're subscribe to (default: L).
3435 {"trash", DT_PATH, R_NONE, UL &TrashPath, 0},
3438 ** If \fIset\fP, this variable specifies the path of the trash folder where the
3439 ** mails marked for deletion will be moved, instead of being irremediably
3442 ** \fBNote\fP: When you delete a message in the trash folder, it is really
3443 ** deleted, so that there is no way to recover mail.
3446 {"tunnel", DT_STR, R_NONE, UL &Tunnel, UL 0},
3449 ** Setting this variable will cause Mutt-ng to open a pipe to a command
3450 ** instead of a raw socket. You may be able to use this to set up
3451 ** preauthenticated connections to your IMAP/POP3 server. Example:
3453 ** \fTtunnel="ssh -q mailhost.net /usr/local/libexec/imapd"\fP
3455 ** \fBNote:\fP For this example to work you must be able to log in to the remote
3456 ** machine without having to enter a password.
3459 {"umask", DT_NUM, R_NONE, UL &Umask, 0077},
3462 ** This sets the umask that will be used by Mutt-ng when creating all
3463 ** kinds of files. If \fIunset\fP, the default value is \fT077\fP.
3465 {"use_8bitmime", DT_BOOL, R_NONE, OPTUSE8BITMIME, 0},
3468 ** \fBWarning:\fP do not set this variable unless you are using a version
3469 ** of sendmail which supports the \fT-B8BITMIME\fP flag (such as sendmail
3470 ** 8.8.x) or you may not be able to send mail.
3472 ** When \fIset\fP, Mutt-ng will invoke ``$$sendmail'' with the \fT-B8BITMIME\fP
3473 ** flag when sending 8-bit messages to enable ESMTP negotiation.
3475 {"use_domain", DT_BOOL, R_NONE, OPTUSEDOMAIN, 1},
3478 ** When \fIset\fP, Mutt-ng will qualify all local addresses (ones without the
3479 ** @host portion) with the value of ``$$hostname''. If \fIunset\fP, no
3480 ** addresses will be qualified.
3482 {"use_from", DT_BOOL, R_NONE, OPTUSEFROM, 1},
3485 ** When \fIset\fP, Mutt-ng will generate the ``\fTFrom:\fP'' header field when
3486 ** sending messages. If \fIunset\fP, no ``\fTFrom:\fP'' header field will be
3487 ** generated unless the user explicitly sets one using the ``$my_hdr''
3491 {"use_idn", DT_BOOL, R_BOTH, OPTUSEIDN, 1},
3494 ** Availability: IDN
3497 ** When \fIset\fP, Mutt-ng will show you international domain names decoded.
3499 ** \fBNote:\fP You can use IDNs for addresses even if this is \fIunset\fP.
3500 ** This variable only affects decoding.
3502 #endif /* HAVE_LIBIDN */
3503 #ifdef HAVE_GETADDRINFO
3504 {"use_ipv6", DT_BOOL, R_NONE, OPTUSEIPV6, 1},
3507 ** When \fIset\fP, Mutt-ng will look for IPv6 addresses of hosts it tries to
3508 ** contact. If this option is \fIunset\fP, Mutt-ng will restrict itself to IPv4 addresses.
3509 ** Normally, the default should work.
3511 #endif /* HAVE_GETADDRINFO */
3512 {"user_agent", DT_BOOL, R_NONE, OPTXMAILER, 1},
3515 ** When \fIset\fP, Mutt-ng will add a ``\fTUser-Agent:\fP'' header to outgoing
3516 ** messages, indicating which version of Mutt-ng was used for composing
3519 {"visual", DT_PATH, R_NONE, UL &Visual, 0},
3522 ** Specifies the visual editor to invoke when the \fI~v\fP command is
3523 ** given in the builtin editor.
3525 {"wait_key", DT_BOOL, R_NONE, OPTWAITKEY, 1},
3528 ** Controls whether Mutt-ng will ask you to press a key after \fIshell-
3529 ** escape\fP, \fIpipe-message\fP, \fIpipe-entry\fP, \fIprint-message\fP,
3530 ** and \fIprint-entry\fP commands.
3532 ** It is also used when viewing attachments with ``$auto_view'', provided
3533 ** that the corresponding mailcap entry has a \fTneedsterminal\fP flag,
3534 ** and the external program is interactive.
3536 ** When \fIset\fP, Mutt-ng will always ask for a key. When \fIunset\fP, Mutt-ng will wait
3537 ** for a key only if the external command returned a non-zero status.
3539 {"weed", DT_BOOL, R_NONE, OPTWEED, 1},
3542 ** When \fIset\fP, Mutt-ng will weed headers when displaying, forwarding,
3543 ** printing, or replying to messages.
3545 {"wrap_search", DT_BOOL, R_NONE, OPTWRAPSEARCH, 1},
3548 ** Controls whether searches wrap around the end of the mailbox.
3550 ** When \fIset\fP, searches will wrap around the first (or last) message. When
3551 ** \fIunset\fP, searches will not wrap.
3553 {"wrapmargin", DT_NUM, R_PAGER, UL &WrapMargin, 0},
3556 ** Controls the size of the margin remaining at the right side of
3557 ** the terminal when Mutt-ng's pager does smart wrapping.
3559 {"write_inc", DT_NUM, R_NONE, UL &WriteInc, 10},
3562 ** When writing a mailbox, a message will be printed every
3563 ** \fIwrite_inc\fP messages to indicate progress. If set to 0, only a
3564 ** single message will be displayed before writing a mailbox.
3566 ** Also see the ``$$read_inc'' variable.
3568 {"write_bcc", DT_BOOL, R_NONE, OPTWRITEBCC, 1},
3571 ** Controls whether Mutt-ng writes out the Bcc header when preparing
3572 ** messages to be sent. Exim users may wish to \fIunset\fP this.
3574 {"xterm_icon", DT_STR, R_BOTH, UL &XtermIcon, UL "M%?n?AIL&ail?"},
3577 ** Controls the format of the X11 icon title, as long as $$xterm_set_titles
3578 ** is \fIset\fP. This string is identical in formatting to the one used by
3579 ** ``$$status_format''.
3581 {"xterm_set_titles", DT_BOOL, R_BOTH, OPTXTERMSETTITLES, 0},
3584 ** Controls whether Mutt-ng sets the xterm title bar and icon name
3585 ** (as long as you're in an appropriate terminal). The default must
3586 ** be \fIunset\fP to force in the validity checking.
3588 {"xterm_title", DT_STR, R_BOTH, UL &XtermTitle, UL "Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?"},
3591 ** Controls the format of the title bar of the xterm provided that
3592 ** $$xterm_set_titles has been \fIset\fP. This string is identical in formatting
3593 ** to the one used by ``$$status_format''.
3596 {"x_comment_to", DT_BOOL, R_NONE, OPTXCOMMENTTO, 0},
3599 ** Availability: NNTP
3602 ** If \fIset\fP, Mutt-ng will add a ``\fTX-Comment-To:\fP'' header field
3603 ** (that contains full name of the original article author) to articles that
3611 const struct feature_t Features[] = {
3613 #ifdef NCURSES_VERSION
3619 #ifdef USE_SLANG_CURSES
3625 #ifdef _LIBICONV_VERSION
3643 #ifdef DL_STANDALONE
3697 #ifdef USE_COMPRESSED
3709 #ifdef CRYPT_BACKEND_CLASSIC_PGP
3714 }, {"classic_smime",
3715 #ifdef CRYPT_BACKEND_CLASSIC_SMIME
3721 #ifdef CRYPT_BACKEND_GPGME
3755 const struct mapping_t SortMethods[] = {
3756 {"date", SORT_DATE},
3757 {"date-sent", SORT_DATE},
3758 {"date-received", SORT_RECEIVED},
3759 {"mailbox-order", SORT_ORDER},
3760 {"subject", SORT_SUBJECT},
3761 {"from", SORT_FROM},
3762 {"size", SORT_SIZE},
3763 {"threads", SORT_THREADS},
3765 {"score", SORT_SCORE},
3766 {"spam", SORT_SPAM},
3770 /* same as SortMethods, but with "threads" replaced by "date" */
3772 const struct mapping_t SortAuxMethods[] = {
3773 {"date", SORT_DATE},
3774 {"date-sent", SORT_DATE},
3775 {"date-received", SORT_RECEIVED},
3776 {"mailbox-order", SORT_ORDER},
3777 {"subject", SORT_SUBJECT},
3778 {"from", SORT_FROM},
3779 {"size", SORT_SIZE},
3780 {"threads", SORT_DATE}, /* note: sort_aux == threads
3784 {"score", SORT_SCORE},
3785 {"spam", SORT_SPAM},
3790 const struct mapping_t SortBrowserMethods[] = {
3791 {"alpha", SORT_SUBJECT},
3792 {"date", SORT_DATE},
3793 {"size", SORT_SIZE},
3794 {"unsorted", SORT_ORDER},
3798 const struct mapping_t SortAliasMethods[] = {
3799 {"alias", SORT_ALIAS},
3800 {"address", SORT_ADDRESS},
3801 {"unsorted", SORT_ORDER},
3805 const struct mapping_t SortKeyMethods[] = {
3806 {"address", SORT_ADDRESS},
3807 {"date", SORT_DATE},
3808 {"keyid", SORT_KEYID},
3809 {"trust", SORT_TRUST},
3814 /* functions used to parse commands in a rc file */
3816 static int parse_list (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3817 static int parse_spam_list (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3818 static int parse_unlist (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3820 static int parse_lists (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3821 static int parse_unlists (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3822 static int parse_alias (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3823 static int parse_unalias (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3824 static int parse_ifdef (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3825 static int parse_ignore (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3826 static int parse_unignore (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3827 static int parse_source (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3828 static int parse_set (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3829 static int parse_my_hdr (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3830 static int parse_unmy_hdr (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3831 static int parse_subscribe (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3832 static int parse_unsubscribe (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3834 static int parse_alternates (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3835 static int parse_unalternates (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3839 int (*func) (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3841 unsigned long data1;
3844 struct command_t Commands[] = {
3845 {"alternates", parse_alternates, 0},
3846 {"unalternates", parse_unalternates, 0},
3848 {"account-hook", mutt_parse_hook, M_ACCOUNTHOOK},
3850 {"alias", parse_alias, 0},
3851 {"auto_view", parse_list, UL &AutoViewList},
3852 {"alternative_order", parse_list, UL &AlternativeOrderList},
3853 {"bind", mutt_parse_bind, 0},
3854 {"charset-hook", mutt_parse_hook, M_CHARSETHOOK},
3856 {"color", mutt_parse_color, 0},
3857 {"uncolor", mutt_parse_uncolor, 0},
3859 {"exec", mutt_parse_exec, 0},
3860 {"fcc-hook", mutt_parse_hook, M_FCCHOOK},
3861 {"fcc-save-hook", mutt_parse_hook, M_FCCHOOK|M_SAVEHOOK},
3862 {"folder-hook", mutt_parse_hook, M_FOLDERHOOK},
3863 #ifdef USE_COMPRESSED
3864 {"open-hook", mutt_parse_hook, M_OPENHOOK},
3865 {"close-hook", mutt_parse_hook, M_CLOSEHOOK},
3866 {"append-hook", mutt_parse_hook, M_APPENDHOOK},
3868 {"hdr_order", parse_list, UL &HeaderOrderList},
3869 {"ifdef", parse_ifdef, 1},
3870 {"ifndef", parse_ifdef, 0},
3872 {"iconv-hook", mutt_parse_hook, M_ICONVHOOK},
3874 {"ignore", parse_ignore, 0},
3875 {"lists", parse_lists, 0},
3876 {"macro", mutt_parse_macro, 0},
3877 {"mailboxes", buffy_parse_mailboxes, M_MAILBOXES},
3878 {"unmailboxes", buffy_parse_mailboxes, M_UNMAILBOXES},
3879 {"message-hook", mutt_parse_hook, M_MESSAGEHOOK},
3880 {"mbox-hook", mutt_parse_hook, M_MBOXHOOK},
3881 {"mime_lookup", parse_list, UL &MimeLookupList},
3882 {"unmime_lookup", parse_unlist, UL &MimeLookupList},
3883 {"mono", mutt_parse_mono, 0},
3884 {"my_hdr", parse_my_hdr, 0},
3885 {"pgp-hook", mutt_parse_hook, M_CRYPTHOOK},
3886 {"crypt-hook", mutt_parse_hook, M_CRYPTHOOK},
3887 {"push", mutt_parse_push, 0},
3888 {"reply-hook", mutt_parse_hook, M_REPLYHOOK},
3889 {"reset", parse_set, M_SET_RESET},
3890 {"save-hook", mutt_parse_hook, M_SAVEHOOK},
3891 {"score", mutt_parse_score, 0},
3892 {"send-hook", mutt_parse_hook, M_SENDHOOK},
3893 {"send2-hook", mutt_parse_hook, M_SEND2HOOK},
3894 {"set", parse_set, 0},
3895 {"source", parse_source, 0},
3896 {"spam", parse_spam_list, M_SPAM},
3897 {"nospam", parse_spam_list, M_NOSPAM},
3898 {"subscribe", parse_subscribe, 0},
3899 {"toggle", parse_set, M_SET_INV},
3900 {"unalias", parse_unalias, 0},
3901 {"unalternative_order", parse_unlist, UL &AlternativeOrderList},
3902 {"unauto_view", parse_unlist, UL &AutoViewList},
3903 {"unhdr_order", parse_unlist, UL &HeaderOrderList},
3904 {"unhook", mutt_parse_unhook, 0},
3905 {"unignore", parse_unignore, 0},
3906 {"unlists", parse_unlists, 0},
3907 {"unmono", mutt_parse_unmono, 0},
3908 {"unmy_hdr", parse_unmy_hdr, 0},
3909 {"unscore", mutt_parse_unscore, 0},
3910 {"unset", parse_set, M_SET_UNSET},
3911 {"unsubscribe", parse_unsubscribe, 0},