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.
23 #include "lib/debug.h"
27 #define DT_BOOL 1 /* boolean option */
28 #define DT_NUM 2 /* a number */
29 #define DT_STR 3 /* a string */
30 #define DT_PATH 4 /* a pathname */
31 #define DT_QUAD 5 /* quad-option (yes/no/ask-yes/ask-no) */
32 #define DT_SORT 6 /* sorting methods */
33 #define DT_RX 7 /* regular expressions */
34 #define DT_MAGIC 8 /* mailbox type */
35 #define DT_SYN 9 /* synonym for another variable */
36 #define DT_ADDR 10 /* e-mail address */
37 #define DT_USER 11 /* user defined via $user_ */
38 #define DT_SYS 12 /* pre-defined via $muttng_ */
40 #define DTYPE(x) ((x) & DT_MASK)
43 #define DT_SUBTYPE_MASK 0xf0
44 #define DT_SORT_ALIAS 0x10
45 #define DT_SORT_BROWSER 0x20
46 #define DT_SORT_KEYS 0x40
47 #define DT_SORT_AUX 0x80
49 /* flags to parse_set() */
50 #define M_SET_INV (1<<0) /* default is to invert all vars */
51 #define M_SET_UNSET (1<<1) /* default is to unset all vars */
52 #define M_SET_RESET (1<<2) /* default is to reset all vars to default */
54 /* forced redraw/resort types */
56 #define R_INDEX (1<<0)
57 #define R_PAGER (1<<1)
58 #define R_RESORT (1<<2) /* resort the mailbox */
59 #define R_RESORT_SUB (1<<3) /* resort subthreads */
60 #define R_RESORT_INIT (1<<4) /* resort from scratch */
61 #define R_TREE (1<<5) /* redraw the thread tree */
62 #define R_BOTH (R_INDEX|R_PAGER)
63 #define R_RESORT_BOTH (R_RESORT|R_RESORT_SUB)
73 #define UL (unsigned long)
78 #define ISPELL "ispell"
81 /* build complete documentation */
88 # define MIXMASTER "mixmaster"
100 # define USE_LIBESMTP
111 # ifndef DL_STANDALONE
112 # define DL_STANDALONE
120 # ifndef HAVE_GETADDRINFO
121 # define HAVE_GETADDRINFO
125 struct option_t MuttVars[] = {
127 {"abort_noattach", DT_QUAD, R_NONE, OPT_ATTACH, "no" },
130 ** This variable specifies whether to abort sending if no attachment
131 ** was made but the content references them, i.e. the content
132 ** matches the regular expression given in
133 ** $$attach_remind_regexp. If a match was found and this
134 ** variable is set to \fIyes\fP, message sending will be aborted
135 ** but the mail will be send nevertheless if set to \fIno\fP.
138 ** This variable and $$attach_remind_regexp are intended to
139 ** remind the user to attach files if the message's text
143 ** See also the $$attach_remind_regexp variable.
145 {"abort_nosubject", DT_QUAD, R_NONE, OPT_SUBJECT, "ask-yes" },
148 ** If set to \fIyes\fP, when composing messages and no subject is given
149 ** at the subject prompt, composition will be aborted. If set to
150 ** \fIno\fP, composing messages with no subject given at the subject
151 ** prompt will never be aborted.
153 {"abort_unmodified", DT_QUAD, R_NONE, OPT_ABORT, "yes" },
156 ** If set to \fIyes\fP, composition will automatically abort after
157 ** editing the message body if no changes are made to the file (this
158 ** check only happens after the \fIfirst\fP edit of the file). When set
159 ** to \fIno\fP, composition will never be aborted.
161 {"alias_file", DT_PATH, R_NONE, UL &AliasFile, "~/.muttngrc"},
164 ** The default file in which to save aliases created by the
165 ** ``$create-alias'' function.
167 ** \fBNote:\fP Mutt-ng will not automatically source this file; you must
168 ** explicitly use the ``$source'' command for it to be executed.
170 {"alias_format", DT_STR, R_NONE, UL &AliasFmt, "%4n %2f %t %-10a %r"},
173 ** Specifies the format of the data displayed for the ``alias'' menu. The
174 ** following \fTprintf(3)\fP-style sequences are available:
177 ** .dt %a .dd alias name
178 ** .dt %f .dd flags - currently, a "d" for an alias marked for deletion
179 ** .dt %n .dd index number
180 ** .dt %r .dd address which alias expands to
181 ** .dt %t .dd character which indicates if the alias is tagged for inclusion
184 {"allow_8bit", DT_BOOL, R_NONE, OPTALLOW8BIT, "yes" },
187 ** Controls whether 8-bit data is converted to 7-bit using either
188 ** \fTquoted-printable\fP or \fTbase64\fP encoding when sending mail.
190 {"allow_ansi", DT_BOOL, R_NONE, OPTALLOWANSI, "no" },
193 ** Controls whether ANSI color codes in messages (and color tags in
194 ** rich text messages) are to be interpreted.
195 ** Messages containing these codes are rare, but if this option is set,
196 ** their text will be colored accordingly. Note that this may override
197 ** your color choices, and even present a security problem, since a
198 ** message could include a line like ``\fT[-- PGP output follows ...\fP" and
199 ** give it the same color as your attachment color.
201 {"arrow_cursor", DT_BOOL, R_BOTH, OPTARROWCURSOR, "no" },
204 ** When \fIset\fP, an arrow (``\fT->\fP'') will be used to indicate the current entry
205 ** in menus instead of highlighting the whole line. On slow network or modem
206 ** links this will make response faster because there is less that has to
207 ** be redrawn on the screen when moving to the next or previous entries
210 {"ascii_chars", DT_BOOL, R_BOTH, OPTASCIICHARS, "no" },
213 ** If \fIset\fP, Mutt-ng will use plain ASCII characters when displaying thread
214 ** and attachment trees, instead of the default \fTACS\fP characters.
216 {"askbcc", DT_BOOL, R_NONE, OPTASKBCC, "no" },
219 ** If \fIset\fP, Mutt-ng will prompt you for blind-carbon-copy (Bcc) recipients
220 ** before editing an outgoing message.
222 {"askcc", DT_BOOL, R_NONE, OPTASKCC, "no" },
225 ** If \fIset\fP, Mutt-ng will prompt you for carbon-copy (Cc) recipients before
226 ** editing the body of an outgoing message.
228 {"assumed_charset", DT_STR, R_NONE, UL &AssumedCharset, "us-ascii"},
231 ** This variable is a colon-separated list of character encoding
232 ** schemes for messages without character encoding indication.
233 ** Header field values and message body content without character encoding
234 ** indication would be assumed that they are written in one of this list.
235 ** By default, all the header fields and message body without any charset
236 ** indication are assumed to be in \fTus-ascii\fP.
238 ** For example, Japanese users might prefer this:
240 ** \fTset assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"\fP
242 ** However, only the first content is valid for the message body.
243 ** This variable is valid only if $$strict_mime is unset.
246 {"nntp_ask_followup_to", DT_BOOL, R_NONE, OPTASKFOLLOWUP, "no" },
249 ** Availability: NNTP
252 ** If \fIset\fP, Mutt-ng will prompt you for the \fTFollowup-To:\fP header
253 ** field before editing the body of an outgoing news article.
255 {"nntp_ask_x_comment_to", DT_BOOL, R_NONE, OPTASKXCOMMENTTO, "no" },
258 ** Availability: NNTP
261 ** If \fIset\fP, Mutt-ng will prompt you for the \fTX-Comment-To:\fP header
262 ** field before editing the body of an outgoing news article.
265 {"attach_format", DT_STR, R_NONE, UL &AttachFormat, "%u%D%I %t%4n %T%.40d%> [%.7m/%.10M, %.6e%?C?, %C?, %s] "},
268 ** This variable describes the format of the ``attachment'' menu. The
269 ** following \fTprintf(3)\fP-style sequences are understood:
272 ** .dt %C .dd charset
273 ** .dt %c .dd requires charset conversion (n or c)
274 ** .dt %D .dd deleted flag
275 ** .dt %d .dd description
276 ** .dt %e .dd MIME \fTContent-Transfer-Encoding:\fP header field
277 ** .dt %f .dd filename
278 ** .dt %I .dd MIME \fTContent-Disposition:\fP header field (\fTI\fP=inline, \fTA\fP=attachment)
279 ** .dt %m .dd major MIME type
280 ** .dt %M .dd MIME subtype
281 ** .dt %n .dd attachment number
283 ** .dt %t .dd tagged flag
284 ** .dt %T .dd graphic tree characters
285 ** .dt %u .dd unlink (=to delete) flag
286 ** .dt %>X .dd right justify the rest of the string and pad with character "X"
287 ** .dt %|X .dd pad to the end of the line with character "X"
290 {"attach_remind_regexp", DT_RX, R_NONE, UL &AttachRemindRegexp, "attach"},
293 ** If this variable is non-empty, muttng will scan a message's contents
294 ** before sending for this regular expression. If it is found, it will
295 ** ask for what to do depending on the setting of $$abort_noattach.
297 ** This variable and $$abort_noattach are intended to remind the user
298 ** to attach files if the message's text references them.
300 {"attach_sep", DT_STR, R_NONE, UL &AttachSep, "\n"},
303 ** The separator to add between attachments when operating (saving,
304 ** printing, piping, etc) on a list of tagged attachments.
306 {"attach_split", DT_BOOL, R_NONE, OPTATTACHSPLIT, "yes" },
309 ** If this variable is \fIunset\fP, when operating (saving, printing, piping,
310 ** etc) on a list of tagged attachments, Mutt-ng will concatenate the
311 ** attachments and will operate on them as a single attachment. The
312 ** ``$$attach_sep'' separator is added after each attachment. When \fIset\fP,
313 ** Mutt-ng will operate on the attachments one by one.
315 {"attribution", DT_STR, R_NONE, UL &Attribution, "On %d, %n wrote:"},
318 ** This is the string that will precede a message which has been included
319 ** in a reply. For a full listing of defined \fTprintf(3)\fP-like sequences see
320 ** the section on ``$$index_format''.
322 {"autoedit", DT_BOOL, R_NONE, OPTAUTOEDIT, "no" },
325 ** When \fIset\fP along with ``$$edit_headers'', Mutt-ng will skip the initial
326 ** send-menu and allow you to immediately begin editing the body of your
327 ** message. The send-menu may still be accessed once you have finished
328 ** editing the body of your message.
330 ** Also see ``$$fast_reply''.
332 {"auto_tag", DT_BOOL, R_NONE, OPTAUTOTAG, "no" },
335 ** When \fIset\fP, functions in the \fIindex\fP menu which affect a message
336 ** will be applied to all tagged messages (if there are any). When
337 ** unset, you must first use the ``tag-prefix'' function (default: "\fT;\fP") to
338 ** make the next function apply to all tagged messages.
340 {"beep", DT_BOOL, R_NONE, OPTBEEP, "yes" },
343 ** When this variable is \fIset\fP, Mutt-ng will beep when an error occurs.
345 {"beep_new", DT_BOOL, R_NONE, OPTBEEPNEW, "no" },
348 ** When this variable is \fIset\fP, Mutt-ng will beep whenever it prints a message
349 ** notifying you of new mail. This is independent of the setting of the
350 ** ``$$beep'' variable.
352 {"bounce", DT_QUAD, R_NONE, OPT_BOUNCE, "ask-yes" },
355 ** Controls whether you will be asked to confirm bouncing messages.
356 ** If set to \fIyes\fP you don't get asked if you want to bounce a
357 ** message. Setting this variable to \fIno\fP is not generally useful,
358 ** and thus not recommended, because you are unable to bounce messages.
360 {"bounce_delivered", DT_BOOL, R_NONE, OPTBOUNCEDELIVERED, "yes" },
363 ** When this variable is \fIset\fP, Mutt-ng will include
364 ** \fTDelivered-To:\fP header fields when bouncing messages.
365 ** Postfix users may wish to \fIunset\fP this variable.
367 { "braille_friendly", DT_BOOL, R_NONE, OPTBRAILLEFRIENDLY, "no" },
370 ** When this variable is set, mutt will place the cursor at the beginning
371 ** of the current line in menus, even when the arrow_cursor variable
372 ** is unset, making it easier for blind persons using Braille displays to
373 ** follow these menus. The option is disabled by default because many
374 ** visual terminals don't permit making the cursor invisible.
377 {"nntp_catchup", DT_QUAD, R_NONE, OPT_CATCHUP, "ask-yes" },
380 ** Availability: NNTP
383 ** If this variable is \fIset\fP, Mutt-ng will mark all articles in a newsgroup
384 ** as read when you leaving it.
387 {"charset", DT_STR, R_NONE, UL &Charset, "" },
390 ** Character set your terminal uses to display and enter textual data.
392 {"check_new", DT_BOOL, R_NONE, OPTCHECKNEW, "yes" },
395 ** \fBNote:\fP this option only affects \fImaildir\fP and \fIMH\fP style
398 ** When \fIset\fP, Mutt-ng will check for new mail delivered while the
399 ** mailbox is open. Especially with MH mailboxes, this operation can
400 ** take quite some time since it involves scanning the directory and
401 ** checking each file to see if it has already been looked at. If it's
402 ** \fIunset\fP, no check for new mail is performed while the mailbox is open.
404 {"collapse_unread", DT_BOOL, R_NONE, OPTCOLLAPSEUNREAD, "yes" },
407 ** When \fIunset\fP, Mutt-ng will not collapse a thread if it contains any
410 {"uncollapse_jump", DT_BOOL, R_NONE, OPTUNCOLLAPSEJUMP, "no" },
413 ** When \fIset\fP, Mutt-ng will jump to the next unread message, if any,
414 ** when the current thread is \fIun\fPcollapsed.
416 {"compose_format", DT_STR, R_BOTH, UL &ComposeFormat, "-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-"},
419 ** Controls the format of the status line displayed in the ``compose''
420 ** menu. This string is similar to ``$$status_format'', but has its own
421 ** set of \fTprintf(3)\fP-like sequences:
424 ** .dt %a .dd total number of attachments
425 ** .dt %h .dd local hostname
426 ** .dt %l .dd approximate size (in bytes) of the current message
427 ** .dt %v .dd Mutt-ng version string
430 ** See the text describing the ``$$status_format'' option for more
431 ** information on how to set ``$$compose_format''.
433 {"config_charset", DT_STR, R_NONE, UL &ConfigCharset, "" },
436 ** When defined, Mutt-ng will recode commands in rc files from this
439 {"confirmappend", DT_BOOL, R_NONE, OPTCONFIRMAPPEND, "yes" },
442 ** When \fIset\fP, Mutt-ng will prompt for confirmation when appending messages to
443 ** an existing mailbox.
445 {"confirmcreate", DT_BOOL, R_NONE, OPTCONFIRMCREATE, "yes" },
448 ** When \fIset\fP, Mutt-ng will prompt for confirmation when saving messages to a
449 ** mailbox which does not yet exist before creating it.
451 {"connect_timeout", DT_NUM, R_NONE, UL &ConnectTimeout, "30" },
454 ** Causes Mutt-ng to timeout a network connection (for IMAP or POP) after this
455 ** many seconds if the connection is not able to be established. A negative
456 ** value causes Mutt-ng to wait indefinitely for the connection to succeed.
458 {"content_type", DT_STR, R_NONE, UL &ContentType, "text/plain"},
461 ** Sets the default \fTContent-Type:\fP header field for the body
462 ** of newly composed messages.
464 {"copy", DT_QUAD, R_NONE, OPT_COPY, "yes" },
467 ** This variable controls whether or not copies of your outgoing messages
468 ** will be saved for later references. Also see ``$$record'',
469 ** ``$$save_name'', ``$$force_name'' and ``$fcc-hook''.
472 {"crypt_use_gpgme", DT_BOOL, R_NONE, OPTCRYPTUSEGPGME, "no" },
475 ** This variable controls the use the GPGME enabled crypto backends.
476 ** If it is \fIset\fP and Mutt-ng was build with gpgme support, the gpgme code for
477 ** S/MIME and PGP will be used instead of the classic code.
479 ** \fBNote\fP: You need to use this option in your \fT.muttngrc\fP configuration
480 ** file as it won't have any effect when used interactively.
483 {"crypt_autopgp", DT_BOOL, R_NONE, OPTCRYPTAUTOPGP, "yes" },
486 ** This variable controls whether or not Mutt-ng may automatically enable
487 ** PGP encryption/signing for messages. See also ``$$crypt_autoencrypt'',
488 ** ``$$crypt_replyencrypt'',
489 ** ``$$crypt_autosign'', ``$$crypt_replysign'' and ``$$smime_is_default''.
491 {"crypt_autosmime", DT_BOOL, R_NONE, OPTCRYPTAUTOSMIME, "yes" },
494 ** This variable controls whether or not Mutt-ng may automatically enable
495 ** S/MIME encryption/signing for messages. See also ``$$crypt_autoencrypt'',
496 ** ``$$crypt_replyencrypt'',
497 ** ``$$crypt_autosign'', ``$$crypt_replysign'' and ``$$smime_is_default''.
499 {"date_format", DT_STR, R_BOTH, UL &DateFmt, "!%a, %b %d, %Y at %I:%M:%S%p %Z"},
502 ** This variable controls the format of the date printed by the ``\fT%d\fP''
503 ** sequence in ``$$index_format''. This is passed to \fTstrftime(3)\fP
504 ** to process the date.
506 ** Unless the first character in the string is a bang (``\fT!\fP''), the month
507 ** and week day names are expanded according to the locale specified in
508 ** the variable ``$$locale''. If the first character in the string is a
509 ** bang, the bang is discarded, and the month and week day names in the
510 ** rest of the string are expanded in the \fIC\fP locale (that is in US
514 {"debug_level", DT_NUM, R_NONE, UL &DebugLevel, "0" },
517 ** Availability: debug
520 ** This variable specifies the current debug level and
521 ** may be used to increase or decrease the verbosity level
522 ** during runtime. It overrides the level given with the
523 ** \fT-d\fP command line option.
526 ** Currently, this number must be >= 0 and <= 5 and muttng
527 ** must be started with \fT-d\fP to enable debugging at all;
528 ** enabling at runtime is not possible.
531 {"default_hook", DT_STR, R_NONE, UL &DefaultHook, "~f %s !~P | (~P ~C %s)"},
534 ** This variable controls how send-hooks, message-hooks, save-hooks,
535 ** and fcc-hooks will
536 ** be interpreted if they are specified with only a simple regexp,
537 ** instead of a matching pattern. The hooks are expanded when they are
538 ** declared, so a hook will be interpreted according to the value of this
539 ** variable at the time the hook is declared. The default value matches
540 ** if the message is either from a user matching the regular expression
541 ** given, or if it is from you (if the from address matches
542 ** ``alternates'') and is to or cc'ed to a user matching the given
543 ** regular expression.
545 {"delete", DT_QUAD, R_NONE, OPT_DELETE, "ask-yes" },
548 ** Controls whether or not messages are really deleted when closing or
549 ** synchronizing a mailbox. If set to \fIyes\fP, messages marked for
550 ** deleting will automatically be purged without prompting. If set to
551 ** \fIno\fP, messages marked for deletion will be kept in the mailbox.
553 {"delete_space", DT_BOOL, R_NONE, OPTDELSP, "no" },
556 ** When sending messages with \fTformat=flowed\fP by \fIsetting\fP the
557 ** $$text_flowed variable, this variable specifies whether to also
558 ** set the \fTDelSp\fP parameter to \fTyes\fP. If this is \fIunset\fP,
559 ** no additional parameter will be send as a value of \fTno\fP already
560 ** is the default behavior.
563 ** \fBNote:\fP this variable only has an effect on \fIoutgoing\fP messages
564 ** (if $$text_flowed is \fIset\fP) but not on incomming.
566 {"delete_untag", DT_BOOL, R_NONE, OPTDELETEUNTAG, "yes" },
569 ** If this option is \fIset\fP, Mutt-ng will untag messages when marking them
570 ** for deletion. This applies when you either explicitly delete a message,
571 ** or when you save it to another folder.
573 {"digest_collapse", DT_BOOL, R_NONE, OPTDIGESTCOLLAPSE, "yes" },
576 ** If this option is \fIset\fP, Mutt-ng's received-attachments menu will not show the subparts of
577 ** individual messages in a multipart/digest. To see these subparts, press 'v' on that menu.
579 {"display_filter", DT_PATH, R_PAGER, UL &DisplayFilter, ""},
582 ** When \fIset\fP, specifies a command used to filter messages. When a message
583 ** is viewed it is passed as standard input to $$display_filter, and the
584 ** filtered message is read from the standard output.
586 #if defined(DL_STANDALONE) && defined(USE_DOTLOCK)
587 {"dotlock_program", DT_PATH, R_NONE, UL &MuttDotlock, "$muttng_bindir/muttng_dotlock"},
590 ** Availability: Standalone and Dotlock
593 ** Contains the path of the \fTmuttng_dotlock(1)\fP binary to be used by
597 {"dsn_notify", DT_STR, R_NONE, UL &DsnNotify, ""},
600 ** \fBNote:\fP you should not enable this unless you are using Sendmail
601 ** 8.8.x or greater or in connection with the SMTP support via libESMTP.
603 ** This variable sets the request for when notification is returned. The
604 ** string consists of a comma separated list (no spaces!) of one or more
605 ** of the following: \fInever\fP, to never request notification,
606 ** \fIfailure\fP, to request notification on transmission failure,
607 ** \fIdelay\fP, to be notified of message delays, \fIsuccess\fP, to be
608 ** notified of successful transmission.
610 ** Example: \fTset dsn_notify="failure,delay"\fP
612 {"dsn_return", DT_STR, R_NONE, UL &DsnReturn, ""},
615 ** \fBNote:\fP you should not enable this unless you are using Sendmail
616 ** 8.8.x or greater or in connection with the SMTP support via libESMTP.
618 ** This variable controls how much of your message is returned in DSN
619 ** messages. It may be set to either \fIhdrs\fP to return just the
620 ** message header, or \fIfull\fP to return the full message.
622 ** Example: \fTset dsn_return=hdrs\fP
624 {"duplicate_threads", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTDUPTHREADS, "yes" },
627 ** This variable controls whether Mutt-ng, when sorting by threads, threads
628 ** messages with the same \fTMessage-Id:\fP header field together.
629 ** If it is \fIset\fP, it will indicate that it thinks they are duplicates
630 ** of each other with an equals sign in the thread diagram.
632 {"edit_headers", DT_BOOL, R_NONE, OPTEDITHDRS, "no" },
635 ** This option allows you to edit the header of your outgoing messages
636 ** along with the body of your message.
639 ** Which empty header fields to show is controlled by the
640 ** $$editor_headers option.
643 {"editor_headers", DT_STR, R_NONE, UL &EditorHeaders, "From: To: Cc: Bcc: Subject: Reply-To: Newsgroups: Followup-To: X-Comment-To:" },
645 {"editor_headers", DT_STR, R_NONE, UL &EditorHeaders, "From: To: Cc: Bcc: Subject: Reply-To:" },
649 ** If $$edit_headers is \fIset\fP, this space-separated list specifies
650 ** which \fInon-empty\fP header fields to edit in addition to
651 ** user-defined headers.
654 ** Note: if $$edit_headers had to be turned on by force because
655 ** $$strict_mailto is \fIunset\fP, this option has no effect.
657 {"editor", DT_PATH, R_NONE, UL &Editor, "" },
660 ** This variable specifies which editor is used by Mutt-ng.
661 ** It defaults to the value of the \fT$$$VISUAL\fP, or \fT$$$EDITOR\fP, environment
662 ** variable, or to the string "\fTvi\fP" if neither of those are set.
664 {"encode_from", DT_BOOL, R_NONE, OPTENCODEFROM, "no" },
667 ** When \fIset\fP, Mutt-ng will \fTquoted-printable\fP encode messages when
668 ** they contain the string ``\fTFrom \fP'' (note the trailing space)
669 ** in the beginning of a line. Useful to avoid the tampering certain mail
670 ** delivery and transport agents tend to do with messages.
673 ** \fBNote:\fP as mutt-ng currently violates RfC3676 defining
674 ** \fTformat=flowed\fP, it's <em/strongly/ advised to \fIset\fP
675 ** this option although discouraged by the standard. Alternatively,
676 ** you must take care of space-stuffing <tt/From / lines (with a trailing
679 {"envelope_from", DT_BOOL, R_NONE, OPTENVFROM, "no" },
682 ** When \fIset\fP, Mutt-ng will try to derive the message's \fIenvelope\fP
683 ** sender from the ``\fTFrom:\fP'' header field. Note that this information is passed
684 ** to the sendmail command using the ``\fT-f\fP" command line switch, so don't set this
685 ** option if you are using that switch in $$sendmail yourself,
686 ** or if the sendmail on your machine doesn't support that command
689 {"escape", DT_STR, R_NONE, UL &EscChar, "~"},
692 ** Escape character to use for functions in the builtin editor.
694 {"fast_reply", DT_BOOL, R_NONE, OPTFASTREPLY, "no" },
697 ** When \fIset\fP, the initial prompt for recipients and subject are skipped
698 ** when replying to messages, and the initial prompt for subject is
699 ** skipped when forwarding messages.
701 ** \fBNote:\fP this variable has no effect when the ``$$autoedit''
702 ** variable is \fIset\fP.
704 {"fcc_attach", DT_BOOL, R_NONE, OPTFCCATTACH, "yes" },
707 ** This variable controls whether or not attachments on outgoing messages
708 ** are saved along with the main body of your message.
710 {"fcc_clear", DT_BOOL, R_NONE, OPTFCCCLEAR, "no" },
713 ** When this variable is \fIset\fP, FCCs will be stored unencrypted and
714 ** unsigned, even when the actual message is encrypted and/or
718 {"file_charset", DT_STR, R_NONE, UL &FileCharset, "" },
721 ** This variable is a colon-separated list of character encoding
722 ** schemes for text file attatchments.
723 ** If \fIunset\fP, $$charset value will be used instead.
724 ** For example, the following configuration would work for Japanese
727 ** \fTset file_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"\fP
729 ** Note: ``\fTiso-2022-*\fP'' must be put at the head of the value as shown above
732 {"folder", DT_PATH, R_NONE, UL &Maildir, "~/Mail"},
735 ** Specifies the default location of your mailboxes. A ``\fT+\fP'' or ``\fT=\fP'' at the
736 ** beginning of a pathname will be expanded to the value of this
737 ** variable. Note that if you change this variable from the default
738 ** value you need to make sure that the assignment occurs \fIbefore\fP
739 ** you use ``+'' or ``='' for any other variables since expansion takes place
740 ** during the ``set'' command.
742 {"folder_format", DT_STR, R_INDEX, UL &FolderFormat, "%2C %t %N %F %2l %-8.8u %-8.8g %8s %d %f"},
745 ** This variable allows you to customize the file browser display to your
746 ** personal taste. This string is similar to ``$$index_format'', but has
747 ** its own set of \fTprintf(3)\fP-like sequences:
750 ** .dt %C .dd current file number
751 ** .dt %d .dd date/time folder was last modified
752 ** .dt %f .dd filename
753 ** .dt %F .dd file permissions
754 ** .dt %g .dd group name (or numeric gid, if missing)
755 ** .dt %l .dd number of hard links
756 ** .dt %N .dd N if folder has new mail, blank otherwise
757 ** .dt %s .dd size in bytes
758 ** .dt %t .dd * if the file is tagged, blank otherwise
759 ** .dt %u .dd owner name (or numeric uid, if missing)
760 ** .dt %>X .dd right justify the rest of the string and pad with character "X"
761 ** .dt %|X .dd pad to the end of the line with character "X"
764 {"followup_to", DT_BOOL, R_NONE, OPTFOLLOWUPTO, "yes" },
767 ** Controls whether or not the \fTMail-Followup-To:\fP header field is
768 ** generated when sending mail. When \fIset\fP, Mutt-ng will generate this
769 ** field when you are replying to a known mailing list, specified with
770 ** the ``subscribe'' or ``$lists'' commands or detected by common mailing list
773 ** This field has two purposes. First, preventing you from
774 ** receiving duplicate copies of replies to messages which you send
775 ** to mailing lists. Second, ensuring that you do get a reply
776 ** separately for any messages sent to known lists to which you are
777 ** not subscribed. The header will contain only the list's address
778 ** for subscribed lists, and both the list address and your own
779 ** email address for unsubscribed lists. Without this header, a
780 ** group reply to your message sent to a subscribed list will be
781 ** sent to both the list and your address, resulting in two copies
782 ** of the same email for you.
785 {"nntp_followup_to_poster", DT_QUAD, R_NONE, OPT_FOLLOWUPTOPOSTER, "ask-yes" },
788 ** Availability: NNTP
791 ** If this variable is \fIset\fP and the keyword "\fTposter\fP" is present in
792 ** the \fTFollowup-To:\fP header field, a follow-up to the newsgroup is not
793 ** permitted. The message will be mailed to the submitter of the
797 {"force_name", DT_BOOL, R_NONE, OPTFORCENAME, "no" },
800 ** This variable is similar to ``$$save_name'', except that Mutt-ng will
801 ** store a copy of your outgoing message by the username of the address
802 ** you are sending to even if that mailbox does not exist.
804 ** Also see the ``$$record'' variable.
806 {"force_buffy_check", DT_BOOL, R_NONE, OPTFORCEBUFFYCHECK, "no" },
809 ** When \fIset\fP, it causes Mutt-ng to check for new mail when the
810 ** \fIbuffy-list\fP command is invoked. When \fIunset\fP, \fIbuffy_list\fP
811 ** will just list all mailboxes which are already known to have new mail.
813 ** Also see the following variables: ``$$timeout'', ``$$mail_check'' and
814 ** ``$$imap_mail_check''.
816 {"forward_decode", DT_BOOL, R_NONE, OPTFORWDECODE, "yes" },
819 ** Controls the decoding of complex MIME messages into \fTtext/plain\fP when
820 ** forwarding a message. The message header is also RFC2047 decoded.
821 ** This variable is only used, if ``$$mime_forward'' is \fIunset\fP,
822 ** otherwise ``$$mime_forward_decode'' is used instead.
824 {"forward_edit", DT_QUAD, R_NONE, OPT_FORWEDIT, "yes" },
827 ** This quadoption controls whether or not the user is automatically
828 ** placed in the editor when forwarding messages. For those who always want
829 ** to forward with no modification, use a setting of \fIno\fP.
831 {"forward_format", DT_STR, R_NONE, UL &ForwFmt, "[%a: %s]"},
834 ** This variable controls the default subject when forwarding a message.
835 ** It uses the same format sequences as the ``$$index_format'' variable.
837 {"forward_quote", DT_BOOL, R_NONE, OPTFORWQUOTE, "no" },
840 ** When \fIset\fP forwarded messages included in the main body of the
841 ** message (when ``$$mime_forward'' is \fIunset\fP) will be quoted using
842 ** ``$$indent_string''.
844 {"from", DT_ADDR, R_NONE, UL &From, "" },
847 ** This variable contains a default from address. It
848 ** can be overridden using my_hdr (including from send-hooks) and
849 ** ``$$reverse_name''. This variable is ignored if ``$$use_from''
853 ** \fTsend-hook Mutt-ng-devel@lists.berlios.de 'my_hdr From: Foo Bar <foo@bar.fb>'\fP
854 ** when replying to the mutt-ng developer's mailing list and Mutt-ng takes this email address.
856 ** Defaults to the contents of the environment variable \fT$$$EMAIL\fP.
858 {"gecos_mask", DT_RX, R_NONE, UL &GecosMask, "^[^,]*"},
861 ** A regular expression used by Mutt-ng to parse the GECOS field of a password
862 ** entry when expanding the alias. By default the regular expression is set
863 ** to ``\fT^[^,]*\fP'' which will return the string up to the first ``\fT,\fP'' encountered.
864 ** If the GECOS field contains a string like "lastname, firstname" then you
865 ** should do: \fTset gecos_mask=".*"\fP.
867 ** This can be useful if you see the following behavior: you address a e-mail
868 ** to user ID stevef whose full name is Steve Franklin. If Mutt-ng expands
869 ** stevef to ``Franklin'' stevef@foo.bar then you should set the gecos_mask to
870 ** a regular expression that will match the whole name so Mutt-ng will expand
871 ** ``Franklin'' to ``Franklin, Steve''.
874 {"nntp_group_index_format", DT_STR, R_BOTH, UL &GroupFormat, "%4C %M%N %5s %-45.45f %d"},
877 ** Availability: NNTP
880 ** This variable allows you to customize the newsgroup browser display to
881 ** your personal taste. This string is similar to ``$index_format'', but
882 ** has its own set of \fTprintf(3)\fP-like sequences:
885 ** %C current newsgroup number
886 ** %d description of newsgroup (retrieved from server)
888 ** %M ``-'' if newsgroup not allowed for direct post (moderated for example)
889 ** %N ``N'' if newsgroup is new, ``u'' if unsubscribed, blank otherwise
890 ** %n number of new articles in newsgroup
891 ** %s number of unread articles in newsgroup
892 ** %>X right justify the rest of the string and pad with character "X"
893 ** %|X pad to the end of the line with character "X"
897 {"hdrs", DT_BOOL, R_NONE, OPTHDRS, "yes" },
900 ** When \fIunset\fP, the header fields normally added by the ``$my_hdr''
901 ** command are not created. This variable \fImust\fP be \fIunset\fP before
902 ** composing a new message or replying in order to take effect. If \fIset\fP,
903 ** the user defined header fields are added to every new message.
905 {"header", DT_BOOL, R_NONE, OPTHEADER, "no" },
908 ** When \fIset\fP, this variable causes Mutt-ng to include the header
909 ** of the message you are replying to into the edit buffer.
910 ** The ``$$weed'' setting applies.
912 {"help", DT_BOOL, R_BOTH, OPTHELP, "yes" },
915 ** When \fIset\fP, help lines describing the bindings for the major functions
916 ** provided by each menu are displayed on the first line of the screen.
918 ** \fBNote:\fP The binding will not be displayed correctly if the
919 ** function is bound to a sequence rather than a single keystroke. Also,
920 ** the help line may not be updated if a binding is changed while Mutt-ng is
921 ** running. Since this variable is primarily aimed at new users, neither
922 ** of these should present a major problem.
924 {"hidden_host", DT_BOOL, R_NONE, OPTHIDDENHOST, "no" },
927 ** When \fIset\fP, Mutt-ng will skip the host name part of ``$$hostname'' variable
928 ** when adding the domain part to addresses. This variable does not
929 ** affect the generation of \fTMessage-ID:\fP header fields, and it will not lead to the
930 ** cut-off of first-level domains.
932 {"hide_limited", DT_BOOL, R_TREE|R_INDEX, OPTHIDELIMITED, "no" },
935 ** When \fIset\fP, Mutt-ng will not show the presence of messages that are hidden
936 ** by limiting, in the thread tree.
938 {"hide_missing", DT_BOOL, R_TREE|R_INDEX, OPTHIDEMISSING, "yes" },
941 ** When \fIset\fP, Mutt-ng will not show the presence of missing messages in the
944 {"hide_thread_subject", DT_BOOL, R_TREE|R_INDEX, OPTHIDETHREADSUBJECT, "yes" },
947 ** When \fIset\fP, Mutt-ng will not show the subject of messages in the thread
948 ** tree that have the same subject as their parent or closest previously
949 ** displayed sibling.
951 {"hide_top_limited", DT_BOOL, R_TREE|R_INDEX, OPTHIDETOPLIMITED, "no" },
954 ** When \fIset\fP, Mutt-ng will not show the presence of messages that are hidden
955 ** by limiting, at the top of threads in the thread tree. Note that when
956 ** $$hide_missing is set, this option will have no effect.
958 {"hide_top_missing", DT_BOOL, R_TREE|R_INDEX, OPTHIDETOPMISSING, "yes" },
961 ** When \fIset\fP, Mutt-ng will not show the presence of missing messages at the
962 ** top of threads in the thread tree. Note that when $$hide_limited is
963 ** \fIset\fP, this option will have no effect.
965 {"history", DT_NUM, R_NONE, UL &HistSize, "10" },
968 ** This variable controls the size (in number of strings remembered) of
969 ** the string history buffer. The buffer is cleared each time the
970 ** variable is changed.
972 {"honor_followup_to", DT_QUAD, R_NONE, OPT_MFUPTO, "yes" },
975 ** This variable controls whether or not a \fTMail-Followup-To:\fP header field is
976 ** honored when group-replying to a message.
978 {"hostname", DT_STR, R_NONE, UL &Fqdn, "" },
981 ** Specifies the hostname to use after the ``\fT@\fP'' in local e-mail
982 ** addresses and during generation of \fTMessage-Id:\fP headers.
984 ** Please be sure to really know what you are doing when changing this variable
985 ** to configure a custom domain part of Message-IDs.
987 {"ignore_list_reply_to", DT_BOOL, R_NONE, OPTIGNORELISTREPLYTO, "no" },
990 ** Affects the behaviour of the \fIreply\fP function when replying to
991 ** messages from mailing lists. When \fIset\fP, if the ``\fTReply-To:\fP'' header field is
992 ** set to the same value as the ``\fTTo:\fP'' header field, Mutt-ng assumes that the
993 ** ``\fTReply-To:\fP'' header field was set by the mailing list to automate responses
994 ** to the list, and will ignore this field. To direct a response to the
995 ** mailing list when this option is set, use the \fIlist-reply\fP
996 ** function; \fIgroup-reply\fP will reply to both the sender and the
1000 {"imap_authenticators", DT_STR, R_NONE, UL &ImapAuthenticators, "" },
1003 ** Availability: IMAP
1006 ** This is a colon-delimited list of authentication methods Mutt-ng may
1007 ** attempt to use to log in to an IMAP server, in the order Mutt-ng should
1008 ** try them. Authentication methods are either ``\fTlogin\fP'' or the right
1009 ** side of an IMAP ``\fTAUTH=\fP'' capability string, e.g. ``\fTdigest-md5\fP'',
1010 ** ``\fTgssapi\fP'' or ``\fTcram-md5\fP''. This parameter is case-insensitive.
1013 ** parameter is \fIunset\fP (the default) Mutt-ng will try all available methods,
1014 ** in order from most-secure to least-secure.
1016 ** Example: \fTset imap_authenticators="gssapi:cram-md5:login"\fP
1018 ** \fBNote:\fP Mutt-ng will only fall back to other authentication methods if
1019 ** the previous methods are unavailable. If a method is available but
1020 ** authentication fails, Mutt-ng will not connect to the IMAP server.
1022 { "imap_check_subscribed", DT_BOOL, R_NONE, OPTIMAPCHECKSUBSCRIBED, "no" },
1025 ** When \fIset\fP, mutt will fetch the set of subscribed folders from
1026 ** your server on connection, and add them to the set of mailboxes
1027 ** it polls for new mail. See also the ``$mailboxes'' command.
1030 {"imap_delim_chars", DT_STR, R_NONE, UL &ImapDelimChars, "/."},
1033 ** Availability: IMAP
1036 ** This contains the list of characters which you would like to treat
1037 ** as folder separators for displaying IMAP paths. In particular it
1038 ** helps in using the '\fT=\fP' shortcut for your $$folder variable.
1040 {"imap_headers", DT_STR, R_INDEX, UL &ImapHeaders, "" },
1043 ** Availability: IMAP
1046 ** Mutt-ng requests these header fields in addition to the default headers
1047 ** (``DATE FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE
1048 ** CONTENT-DESCRIPTION IN-REPLY-TO REPLY-TO LINES X-LABEL'') from IMAP
1049 ** servers before displaying the ``index'' menu. You may want to add more
1050 ** headers for spam detection.
1052 ** \fBNote:\fP This is a space separated list.
1054 {"imap_home_namespace", DT_STR, R_NONE, UL &ImapHomeNamespace, "" },
1057 ** Availability: IMAP
1060 ** You normally want to see your personal folders alongside
1061 ** your \fTINBOX\fP in the IMAP browser. If you see something else, you may set
1062 ** this variable to the IMAP path to your folders.
1064 {"imap_keepalive", DT_NUM, R_NONE, UL &ImapKeepalive, "900" },
1067 ** Availability: IMAP
1070 ** This variable specifies the maximum amount of time in seconds that Mutt-ng
1071 ** will wait before polling open IMAP connections, to prevent the server
1072 ** from closing them before Mutt-ng has finished with them.
1075 ** well within the RFC-specified minimum amount of time (30 minutes) before
1076 ** a server is allowed to do this, but in practice the RFC does get
1077 ** violated every now and then.
1079 ** Reduce this number if you find yourself
1080 ** getting disconnected from your IMAP server due to inactivity.
1082 {"imap_login", DT_STR, R_NONE, UL &ImapLogin, "" },
1085 ** Availability: IMAP
1088 ** Your login name on the IMAP server.
1090 ** This variable defaults to the value of ``$$imap_user.''
1092 {"imap_list_subscribed", DT_BOOL, R_NONE, OPTIMAPLSUB, "no" },
1095 ** Availability: IMAP
1098 ** This variable configures whether IMAP folder browsing will look for
1099 ** only subscribed folders or all folders. This can be toggled in the
1100 ** IMAP browser with the \fItoggle-subscribed\fP function.
1102 {"imap_mail_check", DT_NUM, R_NONE, UL &ImapBuffyTimeout, "300" },
1105 ** This variable configures how often (in seconds) Mutt-ng should look for
1106 ** new mail in IMAP folders. This is split from the ``$mail_check'' variable
1107 ** to generate less traffic and get more accurate information for local folders.
1109 {"imap_pass", DT_STR, R_NONE, UL &ImapPass, "" },
1112 ** Availability: IMAP
1115 ** Specifies the password for your IMAP account. If \fIunset\fP, Mutt-ng will
1116 ** prompt you for your password when you invoke the fetch-mail function.
1118 ** \fBWarning\fP: you should only use this option when you are on a
1119 ** fairly secure machine, because the superuser can read your configuration even
1120 ** if you are the only one who can read the file.
1122 {"imap_passive", DT_BOOL, R_NONE, OPTIMAPPASSIVE, "yes" },
1125 ** Availability: IMAP
1128 ** When \fIset\fP, Mutt-ng will not open new IMAP connections to check for new
1129 ** mail. Mutt-ng will only check for new mail over existing IMAP
1130 ** connections. This is useful if you don't want to be prompted to
1131 ** user/password pairs on Mutt-ng invocation, or if opening the connection
1134 {"imap_peek", DT_BOOL, R_NONE, OPTIMAPPEEK, "yes" },
1137 ** Availability: IMAP
1140 ** If \fIset\fP, Mutt-ng will avoid implicitly marking your mail as read whenever
1141 ** you fetch a message from the server. This is generally a good thing,
1142 ** but can make closing an IMAP folder somewhat slower. This option
1143 ** exists to appease speed freaks.
1145 {"imap_reconnect", DT_QUAD, R_NONE, OPT_IMAPRECONNECT, "ask-yes" },
1148 ** Availability: IMAP
1151 ** Controls whether or not Mutt-ng will try to reconnect to IMAP server when
1152 ** the connection is lost.
1154 {"imap_servernoise", DT_BOOL, R_NONE, OPTIMAPSERVERNOISE, "yes" },
1157 ** Availability: IMAP
1160 ** When \fIset\fP, Mutt-ng will display warning messages from the IMAP
1161 ** server as error messages. Since these messages are often
1162 ** harmless, or generated due to configuration problems on the
1163 ** server which are out of the users' hands, you may wish to suppress
1164 ** them at some point.
1166 {"imap_user", DT_STR, R_NONE, UL &ImapUser, "" },
1169 ** Availability: IMAP
1172 ** The name of the user whose mail you intend to access on the IMAP
1175 ** This variable defaults to your user name on the local machine.
1178 {"implicit_autoview", DT_BOOL, R_NONE, OPTIMPLICITAUTOVIEW, "no" },
1181 ** If \fIset\fP, Mutt-ng will look for a mailcap entry with the
1182 ** ``\fTcopiousoutput\fP'' flag set for \fIevery\fP MIME attachment it doesn't have
1183 ** an internal viewer defined for. If such an entry is found, Mutt-ng will
1184 ** use the viewer defined in that entry to convert the body part to text
1187 {"include", DT_QUAD, R_NONE, OPT_INCLUDE, "ask-yes" },
1190 ** Controls whether or not a copy of the message(s) you are replying to
1191 ** is included in your reply.
1193 {"include_onlyfirst", DT_BOOL, R_NONE, OPTINCLUDEONLYFIRST, "no" },
1196 ** Controls whether or not Mutt-ng includes only the first attachment
1197 ** of the message you are replying.
1199 {"indent_string", DT_STR, R_NONE, UL &Prefix, "> "},
1202 ** Specifies the string to prepend to each line of text quoted in a
1203 ** message to which you are replying. You are strongly encouraged not to
1204 ** change this value, as it tends to agitate the more fanatical netizens.
1206 {"index_format", DT_STR, R_BOTH, UL &HdrFmt, "%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s"},
1209 ** This variable allows you to customize the message index display to
1210 ** your personal taste.
1212 ** ``Format strings'' are similar to the strings used in the ``C''
1213 ** function \fTprintf(3)\fP to format output (see the man page for more detail).
1214 ** The following sequences are defined in Mutt-ng:
1217 ** .dt %a .dd address of the author
1218 ** .dt %A .dd reply-to address (if present; otherwise: address of author)
1219 ** .dt %b .dd filename of the original message folder (think mailBox)
1220 ** .dt %B .dd the list to which the letter was sent, or else the folder name (%b).
1221 ** .dt %c .dd number of characters (bytes) in the message
1222 ** .dt %C .dd current message number
1223 ** .dt %d .dd date and time of the message in the format specified by
1224 ** ``date_format'' converted to sender's time zone
1225 ** .dt %D .dd date and time of the message in the format specified by
1226 ** ``date_format'' converted to the local time zone
1227 ** .dt %e .dd current message number in thread
1228 ** .dt %E .dd number of messages in current thread
1229 ** .dt %f .dd entire From: line (address + real name)
1230 ** .dt %F .dd author name, or recipient name if the message is from you
1231 ** .dt %H .dd spam attribute(s) of this message
1232 ** .dt %g .dd newsgroup name (if compiled with nntp support)
1233 ** .dt %i .dd message-id of the current message
1234 ** .dt %l .dd number of lines in the message (does not work with maildir,
1235 ** mh, and possibly IMAP folders)
1236 ** .dt %L .dd If an address in the To or CC header field matches an address
1237 ** defined by the users ``subscribe'' command, this displays
1238 ** "To <list-name>", otherwise the same as %F.
1239 ** .dt %m .dd total number of message in the mailbox
1240 ** .dt %M .dd number of hidden messages if the thread is collapsed.
1241 ** .dt %N .dd message score
1242 ** .dt %n .dd author's real name (or address if missing)
1243 ** .dt %O .dd (_O_riginal save folder) Where Mutt-ng would formerly have
1244 ** stashed the message: list name or recipient name if no list
1245 ** .dt %s .dd subject of the message
1246 ** .dt %S .dd status of the message (N/D/d/!/r/\(as)
1247 ** .dt %t .dd `to:' field (recipients)
1248 ** .dt %T .dd the appropriate character from the $$to_chars string
1249 ** .dt %u .dd user (login) name of the author
1250 ** .dt %v .dd first name of the author, or the recipient if the message is from you
1251 ** .dt %W .dd name of organization of author (`organization:' field)
1252 ** .dt %y .dd `x-label:' field, if present
1253 ** .dt %Y .dd `x-label' field, if present, and (1) not at part of a thread tree,
1254 ** (2) at the top of a thread, or (3) `x-label' is different from
1255 ** preceding message's `x-label'.
1256 ** .dt %Z .dd message status flags
1257 ** .dt %{fmt} .dd the date and time of the message is converted to sender's
1258 ** time zone, and ``fmt'' is expanded by the library function
1259 ** ``strftime''; a leading bang disables locales
1260 ** .dt %[fmt] .dd the date and time of the message is converted to the local
1261 ** time zone, and ``fmt'' is expanded by the library function
1262 ** ``strftime''; a leading bang disables locales
1263 ** .dt %(fmt) .dd the local date and time when the message was received.
1264 ** ``fmt'' is expanded by the library function ``strftime'';
1265 ** a leading bang disables locales
1266 ** .dt %<fmt> .dd the current local time. ``fmt'' is expanded by the library
1267 ** function ``strftime''; a leading bang disables locales.
1268 ** .dt %>X .dd right justify the rest of the string and pad with character "X"
1269 ** .dt %|X .dd pad to the end of the line with character "X"
1272 ** See also: ``$$to_chars''.
1275 {"nntp_inews", DT_PATH, R_NONE, UL &Inews, ""},
1278 ** Availability: NNTP
1281 ** If \fIset\fP, specifies the program and arguments used to deliver news posted
1282 ** by Mutt-ng. Otherwise, Mutt-ng posts article using current connection.
1283 ** The following \fTprintf(3)\fP-style sequence is understood:
1286 ** %s newsserver name
1289 ** Example: \fTset inews="/usr/local/bin/inews -hS"\fP
1292 {"ispell", DT_PATH, R_NONE, UL &Ispell, ISPELL},
1295 ** How to invoke ispell (GNU's spell-checking software).
1297 {"keep_flagged", DT_BOOL, R_NONE, OPTKEEPFLAGGED, "no" },
1300 ** If \fIset\fP, read messages marked as flagged will not be moved
1301 ** from your spool mailbox to your ``$$mbox'' mailbox, or as a result of
1302 ** a ``$mbox-hook'' command.
1304 {"locale", DT_STR, R_BOTH, UL &Locale, "C"},
1307 ** The locale used by \fTstrftime(3)\fP to format dates. Legal values are
1308 ** the strings your system accepts for the locale variable \fTLC_TIME\fP.
1310 {"list_reply", DT_QUAD, R_NONE, OPT_LISTREPLY, "no" },
1313 ** When \fIset\fP, address replies to the mailing list the original message came
1314 ** from (instead to the author only). Setting this option to ``\fIask-yes\fP'' or
1315 ** ``\fIask-no\fP'' will ask if you really intended to reply to the author only.
1317 {"max_display_recips", DT_NUM, R_PAGER, UL &MaxDispRecips, "0" },
1320 ** When set non-zero, this specifies the maximum number of recipient header
1321 ** lines (\fTTo:\fP, \fTCc:\fP and \fTBcc:\fP) to display in the pager if header
1322 ** weeding is turned on. In case the number of lines exeeds its value, the
1323 ** last line will have 3 dots appended.
1325 {"max_line_length", DT_NUM, R_PAGER, UL &MaxLineLength, "0" },
1328 ** When \fIset\fP, the maximum line length for displaying ``format = flowed'' messages is limited
1329 ** to this length. A value of 0 (which is also the default) means that the
1330 ** maximum line length is determined by the terminal width and $$wrapmargin.
1332 {"mail_check", DT_NUM, R_NONE, UL &BuffyTimeout, "5" },
1335 ** This variable configures how often (in seconds) Mutt-ng should look for
1338 ** \fBNote:\fP This does not apply to IMAP mailboxes, see $$imap_mail_check.
1340 {"mailcap_path", DT_STR, R_NONE, UL &MailcapPath, "" },
1343 ** This variable specifies which files to consult when attempting to
1344 ** display MIME bodies not directly supported by Mutt-ng.
1346 {"mailcap_sanitize", DT_BOOL, R_NONE, OPTMAILCAPSANITIZE, "yes" },
1349 ** If \fIset\fP, Mutt-ng will restrict possible characters in mailcap \fT%\fP expandos
1350 ** to a well-defined set of safe characters. This is the safe setting,
1351 ** but we are not sure it doesn't break some more advanced MIME stuff.
1353 ** \fBDON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE
1358 {"header_cache", DT_PATH, R_NONE, UL &HeaderCache, "" },
1361 ** Availability: Header Cache
1364 ** The $$header_cache variable points to the header cache database.
1366 ** If $$header_cache points to a directory it will contain a header cache
1367 ** database per folder. If $$header_cache points to a file that file will
1368 ** be a single global header cache. By default it is \fIunset\fP so no
1369 ** header caching will be used.
1371 {"maildir_header_cache_verify", DT_BOOL, R_NONE, OPTHCACHEVERIFY, "yes" },
1374 ** Availability: Header Cache
1377 ** Check for Maildir unaware programs other than Mutt-ng having modified maildir
1378 ** files when the header cache is in use. This incurs one \fTstat(2)\fP per
1379 ** message every time the folder is opened.
1381 #if HAVE_GDBM || HAVE_DB4
1382 {"header_cache_pagesize", DT_STR, R_NONE, UL &HeaderCachePageSize, "16384"},
1385 ** Availability: Header Cache
1388 ** Change the maildir header cache database page size.
1391 ** or too small of a page size for the common header can waste
1392 ** space, memory effectiveness, or CPU time. The default should be more or
1393 ** less the best you can get. For details google for mutt header
1394 ** cache (first hit).
1396 #endif /* HAVE_GDBM || HAVE_DB 4 */
1398 { "header_cache_compress", DT_BOOL, R_NONE, OPTHCACHECOMPRESS, "no" },
1401 ** If enabled the header cache will be compressed. So only one fifth of the usual
1402 ** diskspace is used, but the uncompression can result in a slower open of the
1405 #endif /* HAVE_QDBM */
1406 #endif /* USE_HCACHE */
1407 {"maildir_trash", DT_BOOL, R_NONE, OPTMAILDIRTRASH, "no" },
1410 ** If \fIset\fP, messages marked as deleted will be saved with the maildir
1411 ** (T)rashed flag instead of physically deleted.
1413 ** \fBNOTE:\fP this only applies
1414 ** to maildir-style mailboxes. Setting it will have no effect on other
1417 ** It is similiar to the trash option.
1419 {"mark_old", DT_BOOL, R_BOTH, OPTMARKOLD, "yes" },
1422 ** Controls whether or not Mutt-ng marks \fInew\fP \fBunread\fP
1423 ** messages as \fIold\fP if you exit a mailbox without reading them.
1425 ** With this option \fIset\fP, the next time you start Mutt-ng, the messages
1426 ** will show up with an "O" next to them in the ``index'' menu,
1427 ** indicating that they are old.
1429 {"markers", DT_BOOL, R_PAGER, OPTMARKERS, "yes" },
1432 ** Controls the display of wrapped lines in the internal pager. If set, a
1433 ** ``\fT+\fP'' marker is displayed at the beginning of wrapped lines. Also see
1434 ** the ``$$smart_wrap'' variable.
1436 {"mask", DT_RX, R_NONE, UL &Mask, "!^\\.[^.]"},
1439 ** A regular expression used in the file browser, optionally preceded by
1440 ** the \fInot\fP operator ``\fT!\fP''. Only files whose names match this mask
1441 ** will be shown. The match is always case-sensitive.
1443 {"mbox", DT_PATH, R_BOTH, UL &Inbox, "~/mbox"},
1446 ** This specifies the folder into which read mail in your ``$$spoolfile''
1447 ** folder will be appended.
1449 {"muttng_version", DT_SYS, R_NONE, 0, VERSION },
1452 ** \fIThis is a read-only system property and specifies muttng's
1453 ** version string.\fP
1455 {"muttng_revision", DT_SYS, R_NONE, 0, MUTT_REVISION },
1458 ** \fIThis is a read-only system property and specifies muttng's
1459 ** subversion revision string.\fP
1461 {"muttng_sysconfdir", DT_SYS, R_NONE, 0, SYSCONFDIR },
1464 ** \fIThis is a read-only system property and specifies the
1465 ** directory containing the muttng system-wide configuration.\fP
1467 {"muttng_bindir", DT_SYS, R_NONE, 0, BINDIR },
1470 ** \fIThis is a read-only system property and specifies the
1471 ** directory containing the muttng binary.
1473 {"muttng_docdir", DT_SYS, R_NONE, 0, PKGDOCDIR },
1476 ** \fIThis is a read-only system property and specifies the
1477 ** directory containing the muttng documentation.\fP
1481 {"muttng_hcache_backend", DT_SYS, R_NONE, 0, "qdbm" },
1483 {"muttng_hcache_backend", DT_SYS, R_NONE, 0, "gdbm" },
1485 {"muttng_hcache_backend", DT_SYS, R_NONE, 0, "db4" },
1487 {"muttng_hcache_backend", DT_SYS, R_NONE, 0, "unknown" },
1491 ** \fIThis is a read-only system property and specifies the
1492 ** header chaching's database backend.\fP
1495 {"operating_system", DT_STR, R_NONE, UL &OperatingSystem, "" },
1498 ** This specifies the operating system name for the \fTUser-Agent:\fP header field. If
1499 ** this is \fIunset\fP, it will be set to the operating system name that \fTuname(2)\fP
1500 ** returns. If \fTuname(2)\fP fails, ``UNIX'' will be used.
1502 ** It may, for example, look as: ``\fTmutt-ng 1.5.9i (Linux)\fP''.
1504 {"sidebar_boundary", DT_STR, R_BOTH, UL &SidebarBoundary, "." },
1507 ** When the sidebar is displayed and $$sidebar_shorten_hierarchy is \fIset\fP, this
1508 ** variable specifies the characters at which to split a folder name into
1509 ** ``hierarchy items.''
1511 {"sidebar_delim", DT_STR, R_BOTH, UL &SidebarDelim, "|"},
1514 ** This specifies the delimiter between the sidebar (if visible) and
1517 {"sidebar_visible", DT_BOOL, R_BOTH, OPTMBOXPANE, "no" },
1520 ** This specifies whether or not to show the sidebar (a list of folders specified
1521 ** with the ``mailboxes'' command).
1523 {"sidebar_width", DT_NUM, R_BOTH, UL &SidebarWidth, "0" },
1526 ** The width of the sidebar.
1528 {"sidebar_newmail_only", DT_BOOL, R_BOTH, OPTSIDEBARNEWMAILONLY, "no" },
1531 ** If \fIset\fP, only folders with new mail will be shown in the sidebar.
1533 {"sidebar_number_format", DT_STR, R_BOTH, UL &SidebarNumberFormat, "%m%?n?(%n)?%?f?[%f]?"},
1536 ** This variable controls how message counts are printed when the sidebar
1537 ** is enabled. If this variable is \fIempty\fP (\fIand only if\fP), no numbers
1538 ** will be printed \fIand\fP mutt-ng won't frequently count mail (which
1539 ** may be a great speedup esp. with mbox-style mailboxes.)
1541 ** The following \fTprintf(3)\fP-like sequences are supported all of which
1542 ** may be printed non-zero:
1545 ** .dt %d .dd Number of deleted messages. 1)
1546 ** .dt %F .dd Number of flagged messages.
1547 ** .dt %m .dd Total number of messages.
1548 ** .dt %M .dd Total number of messages shown, i.e. not hidden by a limit. 1)
1549 ** .dt %n .dd Number of new messages.
1550 ** .dt %t .dd Number of tagged messages. 1)
1553 ** 1) These expandos only have a non-zero value for the current mailbox and
1554 ** will always be zero otherwise.
1556 {"sidebar_shorten_hierarchy", DT_BOOL, R_NONE, OPTSHORTENHIERARCHY, "no" },
1559 ** When \fIset\fP, the ``hierarchy'' of the sidebar entries will be shortened
1560 ** only if they cannot be printed in full length (because ``$$sidebar_width''
1561 ** is set to a too low value). For example, if the newsgroup name
1562 ** ``de.alt.sysadmin.recovery'' doesn't fit on the screen, it'll get shortened
1563 ** ``d.a.s.recovery'' while ``de.alt.d0'' still would and thus will not get
1566 ** At which characters this compression is done is controled via the
1567 ** $$sidebar_boundary variable.
1569 {"mbox_type", DT_MAGIC, R_NONE, UL &DefaultMagic, "mbox" },
1572 ** The default mailbox type used when creating new folders. May be any of
1573 ** \fTmbox\fP, \fTMMDF\fP, \fTMH\fP and \fTMaildir\fP.
1575 {"metoo", DT_BOOL, R_NONE, OPTMETOO, "no" },
1578 ** If \fIunset\fP, Mutt-ng will remove your address (see the ``alternates''
1579 ** command) from the list of recipients when replying to a message.
1581 {"menu_context", DT_NUM, R_NONE, UL &MenuContext, "0" },
1584 ** This variable controls the number of lines of context that are given
1585 ** when scrolling through menus. (Similar to ``$$pager_context''.)
1587 {"menu_move_off", DT_BOOL, R_NONE, OPTMENUMOVEOFF, "yes" },
1590 ** When \fIunset\fP, the bottom entry of menus will never scroll up past
1591 ** the bottom of the screen, unless there are less entries than lines.
1592 ** When \fIset\fP, the bottom entry may move off the bottom.
1594 {"menu_scroll", DT_BOOL, R_NONE, OPTMENUSCROLL, "no" },
1597 ** When \fIset\fP, menus will be scrolled up or down one line when you
1598 ** attempt to move across a screen boundary. If \fIunset\fP, the screen
1599 ** is cleared and the next or previous page of the menu is displayed
1600 ** (useful for slow links to avoid many redraws).
1602 {"meta_key", DT_BOOL, R_NONE, OPTMETAKEY, "no" },
1605 ** If \fIset\fP, forces Mutt-ng to interpret keystrokes with the high bit (bit 8)
1606 ** set as if the user had pressed the \fTESC\fP key and whatever key remains
1607 ** after having the high bit removed. For example, if the key pressed
1608 ** has an ASCII value of \fT0xf4\fP, then this is treated as if the user had
1609 ** pressed \fTESC\fP then ``\fTx\fP''. This is because the result of removing the
1610 ** high bit from ``\fT0xf4\fP'' is ``\fT0x74\fP'', which is the ASCII character
1613 {"mh_purge", DT_BOOL, R_NONE, OPTMHPURGE, "no" },
1616 ** When \fIunset\fP, Mutt-ng will mimic mh's behaviour and rename deleted messages
1617 ** to \fI,<old file name>\fP in mh folders instead of really deleting
1618 ** them. If the variable is set, the message files will simply be
1621 {"mh_seq_flagged", DT_STR, R_NONE, UL &MhFlagged, "flagged"},
1624 ** The name of the MH sequence used for flagged messages.
1626 {"mh_seq_replied", DT_STR, R_NONE, UL &MhReplied, "replied"},
1629 ** The name of the MH sequence used to tag replied messages.
1631 {"mh_seq_unseen", DT_STR, R_NONE, UL &MhUnseen, "unseen"},
1634 ** The name of the MH sequence used for unseen messages.
1636 {"mime_forward", DT_QUAD, R_NONE, OPT_MIMEFWD, "no" },
1639 ** When \fIset\fP, the message you are forwarding will be attached as a
1640 ** separate MIME part instead of included in the main body of the
1643 ** This is useful for forwarding MIME messages so the receiver
1644 ** can properly view the message as it was delivered to you. If you like
1645 ** to switch between MIME and not MIME from mail to mail, set this
1646 ** variable to ask-no or ask-yes.
1648 ** Also see ``$$forward_decode'' and ``$$mime_forward_decode''.
1650 {"mime_forward_decode", DT_BOOL, R_NONE, OPTMIMEFORWDECODE, "no" },
1653 ** Controls the decoding of complex MIME messages into \fTtext/plain\fP when
1654 ** forwarding a message while ``$$mime_forward'' is \fIset\fP. Otherwise
1655 ** ``$$forward_decode'' is used instead.
1657 {"mime_forward_rest", DT_QUAD, R_NONE, OPT_MIMEFWDREST, "yes" },
1660 ** When forwarding multiple attachments of a MIME message from the recvattach
1661 ** menu, attachments which cannot be decoded in a reasonable manner will
1662 ** be attached to the newly composed message if this option is set.
1666 {"nntp_mime_subject", DT_BOOL, R_NONE, OPTMIMESUBJECT, "yes" },
1669 ** Availability: NNTP
1672 ** If \fIunset\fP, an 8-bit ``\fTSubject:\fP'' header field in a news article
1673 ** will not be encoded according to RFC2047.
1675 ** \fBNote:\fP Only change this setting if you know what you are doing.
1680 {"mix_entry_format", DT_STR, R_NONE, UL &MixEntryFormat, "%4n %c %-16s %a"},
1683 ** Availability: Mixmaster
1686 ** This variable describes the format of a remailer line on the mixmaster
1687 ** chain selection screen. The following \fTprintf(3)\fP-like sequences are
1691 ** .dt %n .dd The running number on the menu.
1692 ** .dt %c .dd Remailer capabilities.
1693 ** .dt %s .dd The remailer's short name.
1694 ** .dt %a .dd The remailer's e-mail address.
1697 {"mixmaster", DT_PATH, R_NONE, UL &Mixmaster, MIXMASTER},
1700 ** Availability: Mixmaster
1703 ** This variable contains the path to the Mixmaster binary on your
1704 ** system. It is used with various sets of parameters to gather the
1705 ** list of known remailers, and to finally send a message through the
1709 {"move", DT_QUAD, R_NONE, OPT_MOVE, "ask-no" },
1712 ** Controls whether or not Mutt-ng will move read messages
1713 ** from your spool mailbox to your ``$$mbox'' mailbox, or as a result of
1714 ** a ``$mbox-hook'' command.
1716 {"message_format", DT_STR, R_NONE, UL &MsgFmt, "%s"},
1719 ** This is the string displayed in the ``attachment'' menu for
1720 ** attachments of type \fTmessage/rfc822\fP. For a full listing of defined
1721 ** \fTprintf(3)\fP-like sequences see the section on ``$$index_format''.
1723 {"msgid_format", DT_STR, R_NONE, UL &MsgIdFormat, "%Y%m%d%h%M%s.G%P%p"},
1726 ** This is the format for the ``local part'' of the \fTMessage-Id:\fP header
1727 ** field generated by Mutt-ng. If this variable is empty, no \fTMessage-Id:\fP
1728 ** headers will be generated. The '%'
1729 ** character marks that certain data will be added to the string, similar to
1730 ** \fTprintf(3)\fP. The following characters are allowed:
1733 ** .dt %d .dd the current day of month
1734 ** .dt %h .dd the current hour
1735 ** .dt %m .dd the current month
1736 ** .dt %M .dd the current minute
1737 ** .dt %O .dd the current UNIX timestamp (octal)
1738 ** .dt %p .dd the process ID
1739 ** .dt %P .dd the current Message-ID prefix (a character rotating with
1740 ** every Message-ID being generated)
1741 ** .dt %r .dd a random integer value (decimal)
1742 ** .dt %R .dd a random integer value (hexadecimal)
1743 ** .dt %s .dd the current second
1744 ** .dt %T .dd the current UNIX timestamp (decimal)
1745 ** .dt %X .dd the current UNIX timestamp (hexadecimal)
1746 ** .dt %Y .dd the current year (Y2K compliant)
1747 ** .dt %% .dd the '%' character
1750 ** \fBNote:\fP Please only change this setting if you know what you are doing.
1751 ** Also make sure to consult RFC2822 to produce technically \fIvalid\fP strings.
1753 {"narrow_tree", DT_BOOL, R_TREE|R_INDEX, OPTNARROWTREE, "no" },
1756 ** This variable, when \fIset\fP, makes the thread tree narrower, allowing
1757 ** deeper threads to fit on the screen.
1760 {"nntp_cache_dir", DT_PATH, R_NONE, UL &NewsCacheDir, "~/.muttng"},
1763 ** Availability: NNTP
1766 ** This variable points to directory where Mutt-ng will cache news
1767 ** article headers. If \fIunset\fP, headers will not be saved at all
1768 ** and will be reloaded each time when you enter a newsgroup.
1770 ** As for the header caching in connection with IMAP and/or Maildir,
1771 ** this drastically increases speed and lowers traffic.
1773 {"nntp_host", DT_STR, R_NONE, UL &NewsServer, "" },
1776 ** Availability: NNTP
1779 ** This variable specifies the name (or address) of the NNTP server to be used.
1782 ** defaults to the value specified via the environment variable
1783 ** \fT$$$NNTPSERVER\fP or contained in the file \fT/etc/nntpserver\fP.
1786 ** specify a username and an alternative port for each newsserver, e.g.
1788 ** \fT[nntp[s]://][username[:password]@]newsserver[:port]\fP
1790 ** \fBNote:\fP Using a password as shown and stored in a configuration file
1791 ** presents a security risk since the superuser of your machine may read it
1792 ** regardless of the file's permissions.
1794 {"nntp_newsrc", DT_PATH, R_NONE, UL &NewsRc, "~/.newsrc"},
1797 ** Availability: NNTP
1800 ** This file contains information about subscribed newsgroup and
1801 ** articles read so far.
1803 ** To ease the use of multiple news servers, the following \fTprintf(3)\fP-style
1804 ** sequence is understood:
1807 ** %s newsserver name
1810 {"nntp_context", DT_NUM, R_NONE, UL &NntpContext, "1000" },
1813 ** Availability: NNTP
1816 ** This variable controls how many news articles to cache per newsgroup
1817 ** (if caching is enabled, see $$nntp_cache_dir) and how many news articles
1818 ** to show in the ``index'' menu.
1820 ** If there're more articles than defined with $$nntp_context, all older ones
1821 ** will be removed/not shown in the index.
1823 {"nntp_load_description", DT_BOOL, R_NONE, OPTLOADDESC, "yes" },
1826 ** Availability: NNTP
1829 ** This variable controls whether or not descriptions for newsgroups
1830 ** are to be loaded when subscribing to a newsgroup.
1832 {"nntp_user", DT_STR, R_NONE, UL &NntpUser, ""},
1835 ** Availability: NNTP
1838 ** Your login name on the NNTP server. If \fIunset\fP and the server requires
1839 ** authentification, Mutt-ng will prompt you for your account name.
1841 {"nntp_pass", DT_STR, R_NONE, UL &NntpPass, ""},
1844 ** Availability: NNTP
1847 ** Your password for NNTP account.
1849 ** \fBNote:\fP Storing passwords in a configuration file
1850 ** presents a security risk since the superuser of your machine may read it
1851 ** regardless of the file's permissions.
1853 {"nntp_mail_check", DT_NUM, R_NONE, UL &NewsPollTimeout, "60" },
1856 ** Availability: NNTP
1859 ** The time in seconds until any operations on a newsgroup except posting a new
1860 ** article will cause a recheck for new news. If set to 0, Mutt-ng will
1861 ** recheck on each operation in index (stepping, read article, etc.).
1863 {"nntp_reconnect", DT_QUAD, R_NONE, OPT_NNTPRECONNECT, "ask-yes" },
1866 ** Availability: NNTP
1869 ** Controls whether or not Mutt-ng will try to reconnect to a newsserver when the
1870 ** was connection lost.
1873 {"pager", DT_PATH, R_NONE, UL &Pager, "builtin"},
1876 ** This variable specifies which pager you would like to use to view
1877 ** messages. ``builtin'' means to use the builtin pager, otherwise this
1878 ** variable should specify the pathname of the external pager you would
1881 ** Using an external pager may have some disadvantages: Additional
1882 ** keystrokes are necessary because you can't call Mutt-ng functions
1883 ** directly from the pager, and screen resizes cause lines longer than
1884 ** the screen width to be badly formatted in the help menu.
1886 {"pager_context", DT_NUM, R_NONE, UL &PagerContext, "0" },
1889 ** This variable controls the number of lines of context that are given
1890 ** when displaying the next or previous page in the internal pager. By
1891 ** default, Mutt-ng will display the line after the last one on the screen
1892 ** at the top of the next page (0 lines of context).
1894 {"pager_format", DT_STR, R_PAGER, UL &PagerFmt, "-%Z- %C/%m: %-20.20n %s"},
1897 ** This variable controls the format of the one-line message ``status''
1898 ** displayed before each message in either the internal or an external
1899 ** pager. The valid sequences are listed in the ``$$index_format''
1902 {"pager_index_lines", DT_NUM, R_PAGER, UL &PagerIndexLines, "0" },
1905 ** Determines the number of lines of a mini-index which is shown when in
1906 ** the pager. The current message, unless near the top or bottom of the
1907 ** folder, will be roughly one third of the way down this mini-index,
1908 ** giving the reader the context of a few messages before and after the
1909 ** message. This is useful, for example, to determine how many messages
1910 ** remain to be read in the current thread. One of the lines is reserved
1911 ** for the status bar from the index, so a \fIpager_index_lines\fP of 6
1912 ** will only show 5 lines of the actual index. A value of 0 results in
1913 ** no index being shown. If the number of messages in the current folder
1914 ** is less than \fIpager_index_lines\fP, then the index will only use as
1915 ** many lines as it needs.
1917 {"pager_stop", DT_BOOL, R_NONE, OPTPAGERSTOP, "no" },
1920 ** When \fIset\fP, the internal-pager will \fBnot\fP move to the next message
1921 ** when you are at the end of a message and invoke the \fInext-page\fP
1924 {"crypt_autosign", DT_BOOL, R_NONE, OPTCRYPTAUTOSIGN, "no" },
1927 ** Setting this variable will cause Mutt-ng to always attempt to
1928 ** cryptographically sign outgoing messages. This can be overridden
1929 ** by use of the \fIpgp-menu\fP, when signing is not required or
1930 ** encryption is requested as well. If ``$$smime_is_default'' is \fIset\fP,
1931 ** then OpenSSL is used instead to create S/MIME messages and settings can
1932 ** be overridden by use of the \fIsmime-menu\fP.
1935 {"crypt_autoencrypt", DT_BOOL, R_NONE, OPTCRYPTAUTOENCRYPT, "no" },
1938 ** Setting this variable will cause Mutt-ng to always attempt to PGP
1939 ** encrypt outgoing messages. This is probably only useful in
1940 ** connection to the \fIsend-hook\fP command. It can be overridden
1941 ** by use of the \fIpgp-menu\fP, when encryption is not required or
1942 ** signing is requested as well. If ``$$smime_is_default'' is \fIset\fP,
1943 ** then OpenSSL is used instead to create S/MIME messages and
1944 ** settings can be overridden by use of the \fIsmime-menu\fP.
1947 {"pgp_ignore_subkeys", DT_BOOL, R_NONE, OPTPGPIGNORESUB, "yes" },
1950 ** Setting this variable will cause Mutt-ng to ignore OpenPGP subkeys. Instead,
1951 ** the principal key will inherit the subkeys' capabilities. \fIUnset\fP this
1952 ** if you want to play interesting key selection games.
1955 {"crypt_replyencrypt", DT_BOOL, R_NONE, OPTCRYPTREPLYENCRYPT, "yes" },
1958 ** If \fIset\fP, automatically PGP or OpenSSL encrypt replies to messages which are
1962 {"crypt_replysign", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGN, "no" },
1965 ** If \fIset\fP, automatically PGP or OpenSSL sign replies to messages which are
1968 ** \fBNote:\fP this does not work on messages that are encrypted \fBand\fP signed!
1971 {"crypt_replysignencrypted", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGNENCRYPTED, "no" },
1974 ** If \fIset\fP, automatically PGP or OpenSSL sign replies to messages
1975 ** which are encrypted. This makes sense in combination with
1976 ** ``$$crypt_replyencrypt'', because it allows you to sign all
1977 ** messages which are automatically encrypted. This works around
1978 ** the problem noted in ``$$crypt_replysign'', that Mutt-ng is not able
1979 ** to find out whether an encrypted message is also signed.
1982 {"crypt_timestamp", DT_BOOL, R_NONE, OPTCRYPTTIMESTAMP, "yes" },
1985 ** If \fIset\fP, Mutt-ng will include a time stamp in the lines surrounding
1986 ** PGP or S/MIME output, so spoofing such lines is more difficult.
1987 ** If you are using colors to mark these lines, and rely on these,
1988 ** you may \fIunset\fP this setting.
1991 {"pgp_use_gpg_agent", DT_BOOL, R_NONE, OPTUSEGPGAGENT, "no" },
1994 ** If \fIset\fP, Mutt-ng will use a possibly-running gpg-agent process.
1997 {"crypt_verify_sig", DT_QUAD, R_NONE, OPT_VERIFYSIG, "yes" },
2000 ** If ``\fIyes\fP'', always attempt to verify PGP or S/MIME signatures.
2001 ** If ``\fIask\fP'', ask whether or not to verify the signature.
2002 ** If ``\fIno\fP'', never attempt to verify cryptographic signatures.
2005 {"smime_is_default", DT_BOOL, R_NONE, OPTSMIMEISDEFAULT, "no" },
2008 ** The default behaviour of Mutt-ng is to use PGP on all auto-sign/encryption
2009 ** operations. To override and to use OpenSSL instead this must be \fIset\fP.
2011 ** However, this has no effect while replying, since Mutt-ng will automatically
2012 ** select the same application that was used to sign/encrypt the original
2015 ** (Note that this variable can be overridden by unsetting $$crypt_autosmime.)
2018 {"smime_ask_cert_label", DT_BOOL, R_NONE, OPTASKCERTLABEL, "yes" },
2021 ** This flag controls whether you want to be asked to enter a label
2022 ** for a certificate about to be added to the database or not. It is
2023 ** \fIset\fP by default.
2026 {"smime_decrypt_use_default_key", DT_BOOL, R_NONE, OPTSDEFAULTDECRYPTKEY, "yes" },
2029 ** If \fIset\fP (default) this tells Mutt-ng to use the default key for decryption. Otherwise,
2030 ** if manage multiple certificate-key-pairs, Mutt-ng will try to use the mailbox-address
2031 ** to determine the key to use. It will ask you to supply a key, if it can't find one.
2034 {"pgp_entry_format", DT_STR, R_NONE, UL &PgpEntryFormat, "%4n %t%f %4l/0x%k %-4a %2c %u"},
2037 ** This variable allows you to customize the PGP key selection menu to
2038 ** your personal taste. This string is similar to ``$$index_format'', but
2039 ** has its own set of \fTprintf(3)\fP-like sequences:
2042 ** .dt %n .dd number
2043 ** .dt %k .dd key id
2044 ** .dt %u .dd user id
2045 ** .dt %a .dd algorithm
2046 ** .dt %l .dd key length
2048 ** .dt %c .dd capabilities
2049 ** .dt %t .dd trust/validity of the key-uid association
2050 ** .dt %[<s>] .dd date of the key where <s> is an \fTstrftime(3)\fP expression
2055 {"pgp_good_sign", DT_RX, R_NONE, UL &PgpGoodSign, "" },
2058 ** If you assign a text to this variable, then a PGP signature is only
2059 ** considered verified if the output from $$pgp_verify_command contains
2060 ** the text. Use this variable if the exit code from the command is 0
2061 ** even for bad signatures.
2064 {"pgp_check_exit", DT_BOOL, R_NONE, OPTPGPCHECKEXIT, "yes" },
2067 ** If \fIset\fP, Mutt-ng will check the exit code of the PGP subprocess when
2068 ** signing or encrypting. A non-zero exit code means that the
2069 ** subprocess failed.
2072 {"pgp_long_ids", DT_BOOL, R_NONE, OPTPGPLONGIDS, "no" },
2075 ** If \fIset\fP, use 64 bit PGP key IDs. \fIUnset\fP uses the normal 32 bit Key IDs.
2078 {"pgp_retainable_sigs", DT_BOOL, R_NONE, OPTPGPRETAINABLESIG, "no" },
2081 ** If \fIset\fP, signed and encrypted messages will consist of nested
2082 ** multipart/signed and multipart/encrypted body parts.
2084 ** This is useful for applications like encrypted and signed mailing
2085 ** lists, where the outer layer (multipart/encrypted) can be easily
2086 ** removed, while the inner multipart/signed part is retained.
2089 {"pgp_autoinline", DT_BOOL, R_NONE, OPTPGPAUTOINLINE, "no" },
2092 ** This option controls whether Mutt-ng generates old-style inline
2093 ** (traditional) PGP encrypted or signed messages under certain
2094 ** circumstances. This can be overridden by use of the \fIpgp-menu\fP,
2095 ** when inline is not required.
2097 ** Note that Mutt-ng might automatically use PGP/MIME for messages
2098 ** which consist of more than a single MIME part. Mutt-ng can be
2099 ** configured to ask before sending PGP/MIME messages when inline
2100 ** (traditional) would not work.
2101 ** See also: ``$$pgp_mime_auto''.
2103 ** Also note that using the old-style PGP message format is \fBstrongly\fP
2104 ** \fBdeprecated\fP.
2107 {"pgp_replyinline", DT_BOOL, R_NONE, OPTPGPREPLYINLINE, "no" },
2110 ** Setting this variable will cause Mutt-ng to always attempt to
2111 ** create an inline (traditional) message when replying to a
2112 ** message which is PGP encrypted/signed inline. This can be
2113 ** overridden by use of the \fIpgp-menu\fP, when inline is not
2114 ** required. This option does not automatically detect if the
2115 ** (replied-to) message is inline; instead it relies on Mutt-ng
2116 ** internals for previously checked/flagged messages.
2118 ** Note that Mutt-ng might automatically use PGP/MIME for messages
2119 ** which consist of more than a single MIME part. Mutt-ng can be
2120 ** configured to ask before sending PGP/MIME messages when inline
2121 ** (traditional) would not work.
2122 ** See also: ``$$pgp_mime_auto''.
2124 ** Also note that using the old-style PGP message format is \fBstrongly\fP
2125 ** \fBdeprecated\fP.
2129 {"pgp_show_unusable", DT_BOOL, R_NONE, OPTPGPSHOWUNUSABLE, "yes" },
2132 ** If \fIset\fP, Mutt-ng will display non-usable keys on the PGP key selection
2133 ** menu. This includes keys which have been revoked, have expired, or
2134 ** have been marked as ``disabled'' by the user.
2137 {"pgp_sign_as", DT_STR, R_NONE, UL &PgpSignAs, "" },
2140 ** If you have more than one key pair, this option allows you to specify
2141 ** which of your private keys to use. It is recommended that you use the
2142 ** keyid form to specify your key (e.g., ``\fT0x00112233\fP'').
2145 {"pgp_strict_enc", DT_BOOL, R_NONE, OPTPGPSTRICTENC, "yes" },
2148 ** If \fIset\fP, Mutt-ng will automatically encode PGP/MIME signed messages as
2149 ** \fTquoted-printable\fP. Please note that unsetting this variable may
2150 ** lead to problems with non-verifyable PGP signatures, so only change
2151 ** this if you know what you are doing.
2154 {"pgp_timeout", DT_NUM, R_NONE, UL &PgpTimeout, "300" },
2157 ** The number of seconds after which a cached passphrase will expire if
2158 ** not used. Default: 300.
2161 {"pgp_sort_keys", DT_SORT|DT_SORT_KEYS, R_NONE, UL &PgpSortKeys, "address" },
2164 ** Specifies how the entries in the ``pgp keys'' menu are sorted. The
2165 ** following are legal values:
2168 ** .dt address .dd sort alphabetically by user id
2169 ** .dt keyid .dd sort alphabetically by key id
2170 ** .dt date .dd sort by key creation date
2171 ** .dt trust .dd sort by the trust of the key
2174 ** If you prefer reverse order of the above values, prefix it with
2178 {"pgp_mime_auto", DT_QUAD, R_NONE, OPT_PGPMIMEAUTO, "ask-yes" },
2181 ** This option controls whether Mutt-ng will prompt you for
2182 ** automatically sending a (signed/encrypted) message using
2183 ** PGP/MIME when inline (traditional) fails (for any reason).
2185 ** Also note that using the old-style PGP message format is \fBstrongly\fP
2186 ** \fBdeprecated\fP.
2189 {"pgp_auto_decode", DT_BOOL, R_NONE, OPTPGPAUTODEC, "no" },
2192 ** If \fIset\fP, Mutt-ng will automatically attempt to decrypt traditional PGP
2193 ** messages whenever the user performs an operation which ordinarily would
2194 ** result in the contents of the message being operated on. For example,
2195 ** if the user displays a pgp-traditional message which has not been manually
2196 ** checked with the check-traditional-pgp function, Mutt-ng will automatically
2197 ** check the message for traditional pgp.
2200 /* XXX Default values! */
2202 {"pgp_decode_command", DT_STR, R_NONE, UL &PgpDecodeCommand, "" },
2205 ** This format strings specifies a command which is used to decode
2206 ** application/pgp attachments.
2208 ** The PGP command formats have their own set of \fTprintf(3)\fP-like sequences:
2211 ** .dt %p .dd Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty
2212 ** string otherwise. Note: This may be used with a %? construct.
2213 ** .dt %f .dd Expands to the name of a file containing a message.
2214 ** .dt %s .dd Expands to the name of a file containing the signature part
2215 ** . of a multipart/signed attachment when verifying it.
2216 ** .dt %a .dd The value of $$pgp_sign_as.
2217 ** .dt %r .dd One or more key IDs.
2220 ** For examples on how to configure these formats for the various versions
2221 ** of PGP which are floating around, see the pgp*.rc and gpg.rc files in
2222 ** the \fTsamples/\fP subdirectory which has been installed on your system
2223 ** alongside the documentation.
2226 {"pgp_getkeys_command", DT_STR, R_NONE, UL &PgpGetkeysCommand, "" },
2229 ** This command is invoked whenever Mutt-ng will need public key information.
2230 ** \fT%r\fP is the only \fTprintf(3)\fP-like sequence used with this format.
2233 {"pgp_verify_command", DT_STR, R_NONE, UL &PgpVerifyCommand, "" },
2236 ** This command is used to verify PGP signatures.
2239 {"pgp_decrypt_command", DT_STR, R_NONE, UL &PgpDecryptCommand, "" },
2242 ** This command is used to decrypt a PGP encrypted message.
2245 {"pgp_clearsign_command", DT_STR, R_NONE, UL &PgpClearSignCommand, "" },
2248 ** This format is used to create a old-style ``clearsigned'' PGP message.
2250 ** Note that the use of this format is \fBstrongly\fP \fBdeprecated\fP.
2253 {"pgp_sign_command", DT_STR, R_NONE, UL &PgpSignCommand, "" },
2256 ** This command is used to create the detached PGP signature for a
2257 ** multipart/signed PGP/MIME body part.
2260 {"pgp_encrypt_sign_command", DT_STR, R_NONE, UL &PgpEncryptSignCommand, "" },
2263 ** This command is used to both sign and encrypt a body part.
2266 {"pgp_encrypt_only_command", DT_STR, R_NONE, UL &PgpEncryptOnlyCommand, "" },
2269 ** This command is used to encrypt a body part without signing it.
2272 {"pgp_import_command", DT_STR, R_NONE, UL &PgpImportCommand, "" },
2275 ** This command is used to import a key from a message into
2276 ** the user's public key ring.
2279 {"pgp_export_command", DT_STR, R_NONE, UL &PgpExportCommand, "" },
2282 ** This command is used to export a public key from the user's
2286 {"pgp_verify_key_command", DT_STR, R_NONE, UL &PgpVerifyKeyCommand, "" },
2289 ** This command is used to verify key information from the key selection
2293 {"pgp_list_secring_command", DT_STR, R_NONE, UL &PgpListSecringCommand, "" },
2296 ** This command is used to list the secret key ring's contents. The
2297 ** output format must be analogous to the one used by
2298 ** \fTgpg --list-keys --with-colons\fP.
2300 ** This format is also generated by the \fTpgpring\fP utility which comes
2304 {"pgp_list_pubring_command", DT_STR, R_NONE, UL &PgpListPubringCommand, "" },
2307 ** This command is used to list the public key ring's contents. The
2308 ** output format must be analogous to the one used by
2309 ** \fTgpg --list-keys --with-colons\fP.
2311 ** This format is also generated by the \fTpgpring\fP utility which comes
2315 {"forward_decrypt", DT_BOOL, R_NONE, OPTFORWDECRYPT, "yes" },
2318 ** Controls the handling of encrypted messages when forwarding a message.
2319 ** When \fIset\fP, the outer layer of encryption is stripped off. This
2320 ** variable is only used if ``$$mime_forward'' is \fIset\fP and
2321 ** ``$$mime_forward_decode'' is \fIunset\fP.
2324 {"smime_timeout", DT_NUM, R_NONE, UL &SmimeTimeout, "300" },
2327 ** The number of seconds after which a cached passphrase will expire if
2331 {"smime_encrypt_with", DT_STR, R_NONE, UL &SmimeCryptAlg, "" },
2334 ** This sets the algorithm that should be used for encryption.
2335 ** Valid choices are ``\fTdes\fP'', ``\fTdes3\fP'', ``\fTrc2-40\fP'',
2336 ** ``\fTrc2-64\fP'', ``\frc2-128\fP''.
2338 ** If \fIunset\fP ``\fI3des\fP'' (TripleDES) is used.
2341 {"smime_keys", DT_PATH, R_NONE, UL &SmimeKeys, "" },
2344 ** Since there is no pubring/secring as with PGP, Mutt-ng has to handle
2345 ** storage ad retrieval of keys/certs by itself. This is very basic right now,
2346 ** and stores keys and certificates in two different directories, both
2347 ** named as the hash-value retrieved from OpenSSL. There is an index file
2348 ** which contains mailbox-address keyid pair, and which can be manually
2349 ** edited. This one points to the location of the private keys.
2352 {"smime_ca_location", DT_PATH, R_NONE, UL &SmimeCALocation, "" },
2355 ** This variable contains the name of either a directory, or a file which
2356 ** contains trusted certificates for use with OpenSSL.
2359 {"smime_certificates", DT_PATH, R_NONE, UL &SmimeCertificates, "" },
2362 ** Since there is no pubring/secring as with PGP, Mutt-ng has to handle
2363 ** storage and retrieval of keys by itself. This is very basic right
2364 ** now, and keys and certificates are stored in two different
2365 ** directories, both named as the hash-value retrieved from
2366 ** OpenSSL. There is an index file which contains mailbox-address
2367 ** keyid pairs, and which can be manually edited. This one points to
2368 ** the location of the certificates.
2371 {"smime_decrypt_command", DT_STR, R_NONE, UL &SmimeDecryptCommand, "" },
2374 ** This format string specifies a command which is used to decrypt
2375 ** \fTapplication/x-pkcs7-mime\fP attachments.
2377 ** The OpenSSL command formats have their own set of \fTprintf(3)\fP-like sequences
2378 ** similar to PGP's:
2381 ** .dt %f .dd Expands to the name of a file containing a message.
2382 ** .dt %s .dd Expands to the name of a file containing the signature part
2383 ** . of a multipart/signed attachment when verifying it.
2384 ** .dt %k .dd The key-pair specified with $$smime_default_key
2385 ** .dt %c .dd One or more certificate IDs.
2386 ** .dt %a .dd The algorithm used for encryption.
2387 ** .dt %C .dd CA location: Depending on whether $$smime_ca_location
2388 ** . points to a directory or file, this expands to
2389 ** . "-CApath $$smime_ca_location" or "-CAfile $$smime_ca_location".
2392 ** For examples on how to configure these formats, see the smime.rc in
2393 ** the \fTsamples/\fP subdirectory which has been installed on your system
2394 ** alongside the documentation.
2397 {"smime_verify_command", DT_STR, R_NONE, UL &SmimeVerifyCommand, "" },
2400 ** This command is used to verify S/MIME signatures of type \fTmultipart/signed\fP.
2403 {"smime_verify_opaque_command", DT_STR, R_NONE, UL &SmimeVerifyOpaqueCommand, "" },
2406 ** This command is used to verify S/MIME signatures of type
2407 ** \fTapplication/x-pkcs7-mime\fP.
2410 {"smime_sign_command", DT_STR, R_NONE, UL &SmimeSignCommand, "" },
2413 ** This command is used to created S/MIME signatures of type
2414 ** \fTmultipart/signed\fP, which can be read by all mail clients.
2417 {"smime_sign_opaque_command", DT_STR, R_NONE, UL &SmimeSignOpaqueCommand, "" },
2420 ** This command is used to created S/MIME signatures of type
2421 ** \fTapplication/x-pkcs7-signature\fP, which can only be handled by mail
2422 ** clients supporting the S/MIME extension.
2425 {"smime_encrypt_command", DT_STR, R_NONE, UL &SmimeEncryptCommand, "" },
2428 ** This command is used to create encrypted S/MIME messages.
2431 {"smime_pk7out_command", DT_STR, R_NONE, UL &SmimePk7outCommand, "" },
2434 ** This command is used to extract PKCS7 structures of S/MIME signatures,
2435 ** in order to extract the public X509 certificate(s).
2438 {"smime_get_cert_command", DT_STR, R_NONE, UL &SmimeGetCertCommand, "" },
2441 ** This command is used to extract X509 certificates from a PKCS7 structure.
2444 {"smime_get_signer_cert_command", DT_STR, R_NONE, UL &SmimeGetSignerCertCommand, "" },
2447 ** This command is used to extract only the signers X509 certificate from a S/MIME
2448 ** signature, so that the certificate's owner may get compared to the
2449 ** email's ``\fTFrom:\fP'' header field.
2452 {"smime_import_cert_command", DT_STR, R_NONE, UL &SmimeImportCertCommand, "" },
2455 ** This command is used to import a certificate via \fTsmime_keysng\fP.
2458 {"smime_get_cert_email_command", DT_STR, R_NONE, UL &SmimeGetCertEmailCommand, "" },
2461 ** This command is used to extract the mail address(es) used for storing
2462 ** X509 certificates, and for verification purposes (to check whether the
2463 ** certificate was issued for the sender's mailbox).
2466 {"smime_default_key", DT_STR, R_NONE, UL &SmimeDefaultKey, "" },
2469 ** This is the default key-pair to use for signing. This must be set to the
2470 ** keyid (the hash-value that OpenSSL generates) to work properly
2473 #if defined(USE_LIBESMTP)
2474 {"smtp_auth_username", DT_SYN, R_NONE, UL "smtp_user", 0},
2475 {"smtp_user", DT_STR, R_NONE, UL &SmtpAuthUser, "" },
2478 ** Availability: SMTP
2481 ** Defines the username to use with SMTP AUTH. Setting this variable will
2482 ** cause Mutt-ng to attempt to use SMTP AUTH when sending.
2484 {"smtp_auth_password", DT_SYN, R_NONE, UL "smtp_pass", 0},
2485 {"smtp_pass", DT_STR, R_NONE, UL &SmtpAuthPass, "" },
2488 ** Availability: SMTP
2491 ** Defines the password to use with SMTP AUTH. If ``$$smtp_user''
2492 ** is set, but this variable is not, you will be prompted for a password
2495 ** \fBNote:\fP Storing passwords in a configuration file
2496 ** presents a security risk since the superuser of your machine may read it
2497 ** regardless of the file's permissions.
2499 {"smtp_envelope", DT_STR, R_NONE, UL &SmtpEnvFrom, "" },
2502 ** Availability: SMTP
2505 ** If this variable is non-empty, it'll be used as the envelope sender. If it's empty
2506 ** (the default), the value of the regular \fTFrom:\fP header will be used.
2509 ** This may be necessary as some providers don't allow for arbitrary values
2510 ** as the envelope sender but only a particular one which may not be the same as the
2511 ** user's desired \fTFrom:\fP header.
2513 {"smtp_host", DT_STR, R_NONE, UL &SmtpHost, "" },
2516 ** Availability: SMTP
2519 ** Defines the SMTP host which will be used to deliver mail, as opposed
2520 ** to invoking the sendmail binary. Setting this variable overrides the
2521 ** value of ``$$sendmail'', and any associated variables.
2523 {"smtp_port", DT_NUM, R_NONE, UL &SmtpPort, "25" },
2526 ** Availability: SMTP
2529 ** Defines the port that the SMTP host is listening on for mail delivery.
2530 ** Must be specified as a number.
2532 ** Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP
2533 ** servers will probably desire 587, the mail submission port.
2535 {"smtp_use_tls", DT_STR, R_NONE, UL &SmtpUseTLS, "" },
2538 ** Availability: SMTP (and SSL)
2541 ** Defines wether to use STARTTLS. If this option is set to ``\fIrequired\fP''
2542 ** and the server does not support STARTTLS or there is an error in the
2543 ** TLS Handshake, the connection will fail. Setting this to ``\fIenabled\fP''
2544 ** will try to start TLS and continue without TLS in case of an error.
2547 ** Muttng still needs to have SSL support enabled in order to use it.
2550 #if defined(USE_SSL) || defined(USE_GNUTLS)
2552 {"ssl_client_cert", DT_PATH, R_NONE, UL &SslClientCert, "" },
2555 ** Availability: SSL
2558 ** The file containing a client certificate and its associated private
2561 #endif /* USE_SSL */
2562 {"ssl_force_tls", DT_BOOL, R_NONE, OPTSSLFORCETLS, "no" },
2565 ** If this variable is \fIset\fP, mutt-ng will require that all connections
2566 ** to remote servers be encrypted. Furthermore it will attempt to
2567 ** negotiate TLS even if the server does not advertise the capability,
2568 ** since it would otherwise have to abort the connection anyway. This
2569 ** option supersedes ``$$ssl_starttls''.
2571 {"ssl_starttls", DT_QUAD, R_NONE, OPT_SSLSTARTTLS, "yes" },
2574 ** Availability: SSL or GNUTLS
2577 ** If \fIset\fP (the default), Mutt-ng will attempt to use STARTTLS on servers
2578 ** advertising the capability. When \fIunset\fP, Mutt-ng will not attempt to
2579 ** use STARTTLS regardless of the server's capabilities.
2581 {"certificate_file", DT_PATH, R_NONE, UL &SslCertFile, "~/.mutt_certificates"},
2584 ** Availability: SSL or GNUTLS
2587 ** This variable specifies the file where the certificates you trust
2588 ** are saved. When an unknown certificate is encountered, you are asked
2589 ** if you accept it or not. If you accept it, the certificate can also
2590 ** be saved in this file and further connections are automatically
2593 ** You can also manually add CA certificates in this file. Any server
2594 ** certificate that is signed with one of these CA certificates are
2595 ** also automatically accepted.
2597 ** Example: \fTset certificate_file=~/.muttng/certificates\fP
2599 # if defined(_MAKEDOC) || !defined (USE_GNUTLS)
2600 {"ssl_usesystemcerts", DT_BOOL, R_NONE, OPTSSLSYSTEMCERTS, "yes" },
2603 ** Availability: SSL
2606 ** If set to \fIyes\fP, Mutt-ng will use CA certificates in the
2607 ** system-wide certificate store when checking if server certificate
2608 ** is signed by a trusted CA.
2610 {"entropy_file", DT_PATH, R_NONE, UL &SslEntropyFile, "" },
2613 ** Availability: SSL
2616 ** The file which includes random data that is used to initialize SSL
2617 ** library functions.
2619 {"ssl_use_sslv2", DT_BOOL, R_NONE, OPTSSLV2, "yes" },
2622 ** Availability: SSL
2625 ** This variables specifies whether to attempt to use SSLv2 in the
2626 ** SSL authentication process.
2628 # endif /* _MAKEDOC || !USE_GNUTLS */
2629 {"ssl_use_sslv3", DT_BOOL, R_NONE, OPTSSLV3, "yes" },
2632 ** Availability: SSL or GNUTLS
2635 ** This variables specifies whether to attempt to use SSLv3 in the
2636 ** SSL authentication process.
2638 {"ssl_use_tlsv1", DT_BOOL, R_NONE, OPTTLSV1, "yes" },
2641 ** Availability: SSL or GNUTLS
2644 ** This variables specifies whether to attempt to use TLSv1 in the
2645 ** SSL authentication process.
2648 {"ssl_min_dh_prime_bits", DT_NUM, R_NONE, UL &SslDHPrimeBits, "0" },
2651 ** Availability: GNUTLS
2654 ** This variable specifies the minimum acceptable prime size (in bits)
2655 ** for use in any Diffie-Hellman key exchange. A value of 0 will use
2656 ** the default from the GNUTLS library.
2658 {"ssl_ca_certificates_file", DT_PATH, R_NONE, UL &SslCACertFile, "" },
2661 ** This variable specifies a file containing trusted CA certificates.
2662 ** Any server certificate that is signed with one of these CA
2663 ** certificates are also automatically accepted.
2665 ** Example: \fTset ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt\fP
2667 # endif /* USE_GNUTLS */
2668 # endif /* USE_SSL || USE_GNUTLS */
2669 {"pipe_split", DT_BOOL, R_NONE, OPTPIPESPLIT, "no" },
2672 ** Used in connection with the \fIpipe-message\fP command and the ``tag-
2673 ** prefix'' or ``tag-prefix-cond'' operators.
2674 ** If this variable is \fIunset\fP, when piping a list of
2675 ** tagged messages Mutt-ng will concatenate the messages and will pipe them
2676 ** as a single folder. When \fIset\fP, Mutt-ng will pipe the messages one by one.
2677 ** In both cases the messages are piped in the current sorted order,
2678 ** and the ``$$pipe_sep'' separator is added after each message.
2680 {"pipe_decode", DT_BOOL, R_NONE, OPTPIPEDECODE, "no" },
2683 ** Used in connection with the \fIpipe-message\fP command. When \fIunset\fP,
2684 ** Mutt-ng will pipe the messages without any preprocessing. When \fIset\fP, Mutt-ng
2685 ** will weed headers and will attempt to PGP/MIME decode the messages
2688 {"pipe_sep", DT_STR, R_NONE, UL &PipeSep, "\n"},
2691 ** The separator to add between messages when piping a list of tagged
2692 ** messages to an external Unix command.
2695 {"pop_authenticators", DT_STR, R_NONE, UL &PopAuthenticators, "" },
2698 ** Availability: POP
2701 ** This is a colon-delimited list of authentication methods Mutt-ng may
2702 ** attempt to use to log in to an POP server, in the order Mutt-ng should
2703 ** try them. Authentication methods are either ``\fTuser\fP'', ``\fTapop\fP''
2704 ** or any SASL mechanism, eg ``\fTdigest-md5\fP'', ``\fTgssapi\fP'' or ``\fTcram-md5\fP''.
2706 ** This parameter is case-insensitive. If this parameter is \fIunset\fP
2707 ** (the default) Mutt-ng will try all available methods, in order from
2708 ** most-secure to least-secure.
2710 ** Example: \fTset pop_authenticators="digest-md5:apop:user"\fP
2712 {"pop_auth_try_all", DT_BOOL, R_NONE, OPTPOPAUTHTRYALL, "yes" },
2715 ** Availability: POP
2718 ** If \fIset\fP, Mutt-ng will try all available methods. When \fIunset\fP, Mutt-ng will
2719 ** only fall back to other authentication methods if the previous
2720 ** methods are unavailable. If a method is available but authentication
2721 ** fails, Mutt-ng will not connect to the POP server.
2723 {"pop_checkinterval", DT_SYN, R_NONE, UL "pop_mail_check", 0},
2724 {"pop_mail_check", DT_NUM, R_NONE, UL &PopCheckTimeout, "60" },
2727 ** Availability: POP
2730 ** This variable configures how often (in seconds) POP should look for
2733 {"pop_delete", DT_QUAD, R_NONE, OPT_POPDELETE, "ask-no" },
2736 ** Availability: POP
2739 ** If \fIset\fP, Mutt-ng will delete successfully downloaded messages from the POP
2740 ** server when using the ``fetch-mail'' function. When \fIunset\fP, Mutt-ng will
2741 ** download messages but also leave them on the POP server.
2743 {"pop_host", DT_STR, R_NONE, UL &PopHost, ""},
2746 ** Availability: POP
2749 ** The name of your POP server for the ``fetch-mail'' function. You
2750 ** can also specify an alternative port, username and password, i.e.:
2752 ** \fT[pop[s]://][username[:password]@]popserver[:port]\fP
2754 ** \fBNote:\fP Storing passwords in a configuration file
2755 ** presents a security risk since the superuser of your machine may read it
2756 ** regardless of the file's permissions.
2758 {"pop_last", DT_BOOL, R_NONE, OPTPOPLAST, "no" },
2761 ** Availability: POP
2764 ** If this variable is \fIset\fP, Mutt-ng will try to use the ``\fTLAST\fP'' POP command
2765 ** for retrieving only unread messages from the POP server when using
2766 ** the ``fetch-mail'' function.
2768 {"pop_reconnect", DT_QUAD, R_NONE, OPT_POPRECONNECT, "ask-yes" },
2771 ** Availability: POP
2774 ** Controls whether or not Mutt-ng will try to reconnect to a POP server when the
2775 ** connection is lost.
2777 {"pop_user", DT_STR, R_NONE, UL &PopUser, "" },
2780 ** Availability: POP
2783 ** Your login name on the POP server.
2785 ** This variable defaults to your user name on the local machine.
2787 {"pop_pass", DT_STR, R_NONE, UL &PopPass, ""},
2790 ** Availability: POP
2793 ** Specifies the password for your POP account. If \fIunset\fP, Mutt-ng will
2794 ** prompt you for your password when you open POP mailbox.
2796 ** \fBNote:\fP Storing passwords in a configuration file
2797 ** presents a security risk since the superuser of your machine may read it
2798 ** regardless of the file's permissions.
2800 #endif /* USE_POP */
2801 {"post_indent_string", DT_STR, R_NONE, UL &PostIndentString, ""},
2804 ** Similar to the ``$$attribution'' variable, Mutt-ng will append this
2805 ** string after the inclusion of a message which is being replied to.
2808 {"nntp_post_moderated", DT_QUAD, R_NONE, OPT_TOMODERATED, "ask-yes" },
2811 ** Availability: NNTP
2814 ** If set to \fIyes\fP, Mutt-ng will post articles to newsgroup that have
2815 ** not permissions to post (e.g. moderated).
2817 ** \fBNote:\fP if the newsserver
2818 ** does not support posting to that newsgroup or a group is totally read-only, that
2819 ** posting will not have any effect.
2822 {"postpone", DT_QUAD, R_NONE, OPT_POSTPONE, "ask-yes" },
2825 ** Controls whether or not messages are saved in the ``$$postponed''
2826 ** mailbox when you elect not to send immediately.
2828 {"postponed", DT_PATH, R_NONE, UL &Postponed, "~/postponed"},
2831 ** Mutt-ng allows you to indefinitely ``$postpone sending a message'' which
2832 ** you are editing. When you choose to postpone a message, Mutt-ng saves it
2833 ** in the mailbox specified by this variable. Also see the ``$$postpone''
2837 {"preconnect", DT_STR, R_NONE, UL &Preconnect, "" },
2840 ** If \fIset\fP, a shell command to be executed if Mutt-ng fails to establish
2841 ** a connection to the server. This is useful for setting up secure
2842 ** connections, e.g. with \fTssh(1)\fP. If the command returns a nonzero
2843 ** status, Mutt-ng gives up opening the server. Example:
2845 ** \fTpreconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net
2846 ** sleep 20 < /dev/null > /dev/null"\fP
2848 ** Mailbox ``foo'' on mailhost.net can now be reached
2849 ** as ``{localhost:1234}foo''.
2851 ** \fBNote:\fP For this example to work, you must be able to log in to the
2852 ** remote machine without having to enter a password.
2854 #endif /* USE_SOCKET */
2855 {"print", DT_QUAD, R_NONE, OPT_PRINT, "ask-no" },
2858 ** Controls whether or not Mutt-ng really prints messages.
2859 ** This is set to \fIask-no\fP by default, because some people
2860 ** accidentally hit ``p'' often.
2862 {"print_command", DT_PATH, R_NONE, UL &PrintCmd, "lpr"},
2865 ** This specifies the command pipe that should be used to print messages.
2867 {"print_decode", DT_BOOL, R_NONE, OPTPRINTDECODE, "yes" },
2870 ** Used in connection with the print-message command. If this
2871 ** option is \fIset\fP, the message is decoded before it is passed to the
2872 ** external command specified by $$print_command. If this option
2873 ** is \fIunset\fP, no processing will be applied to the message when
2874 ** printing it. The latter setting may be useful if you are using
2875 ** some advanced printer filter which is able to properly format
2876 ** e-mail messages for printing.
2878 {"print_split", DT_BOOL, R_NONE, OPTPRINTSPLIT, "no" },
2881 ** Used in connection with the print-message command. If this option
2882 ** is \fIset\fP, the command specified by $$print_command is executed once for
2883 ** each message which is to be printed. If this option is \fIunset\fP,
2884 ** the command specified by $$print_command is executed only once, and
2885 ** all the messages are concatenated, with a form feed as the message
2888 ** Those who use the \fTenscript(1)\fP program's mail-printing mode will
2889 ** most likely want to set this option.
2891 {"prompt_after", DT_BOOL, R_NONE, OPTPROMPTAFTER, "yes" },
2894 ** If you use an \fIexternal\fP ``$$pager'', setting this variable will
2895 ** cause Mutt-ng to prompt you for a command when the pager exits rather
2896 ** than returning to the index menu. If \fIunset\fP, Mutt-ng will return to the
2897 ** index menu when the external pager exits.
2899 {"query_command", DT_PATH, R_NONE, UL &QueryCmd, ""},
2902 ** This specifies the command that Mutt-ng will use to make external address
2903 ** queries. The string should contain a \fT%s\fP, which will be substituted
2904 ** with the query string the user types. See ``$query'' for more
2907 {"quit", DT_QUAD, R_NONE, OPT_QUIT, "yes" },
2910 ** This variable controls whether ``quit'' and ``exit'' actually quit
2911 ** from Mutt-ng. If it set to \fIyes\fP, they do quit, if it is set to \fIno\fP, they
2912 ** have no effect, and if it is set to \fIask-yes\fP or \fIask-no\fP, you are
2913 ** prompted for confirmation when you try to quit.
2915 {"quote_empty", DT_BOOL, R_NONE, OPTQUOTEEMPTY, "yes" },
2918 ** Controls whether or not empty lines will be quoted using
2919 ** ``$indent_string''.
2921 {"quote_quoted", DT_BOOL, R_NONE, OPTQUOTEQUOTED, "no" },
2924 ** Controls how quoted lines will be quoted. If \fIset\fP, one quote
2925 ** character will be added to the end of existing prefix. Otherwise,
2926 ** quoted lines will be prepended by ``$indent_string''.
2928 {"quote_regexp", DT_RX, R_PAGER, UL &QuoteRegexp, "^([ \t]*[|>:}#])+"},
2931 ** A regular expression used in the internal-pager to determine quoted
2932 ** sections of text in the body of a message.
2934 ** \fBNote:\fP In order to use the \fIquoted\fP\fBx\fP patterns in the
2935 ** internal pager, you need to set this to a regular expression that
2936 ** matches \fIexactly\fP the quote characters at the beginning of quoted
2939 {"read_inc", DT_NUM, R_NONE, UL &ReadInc, "10" },
2942 ** If set to a value greater than 0, Mutt-ng will display which message it
2943 ** is currently on when reading a mailbox. The message is printed after
2944 ** \fIread_inc\fP messages have been read (e.g., if set to 25, Mutt-ng will
2945 ** print a message when it reads message 25, and then again when it gets
2946 ** to message 50). This variable is meant to indicate progress when
2947 ** reading large mailboxes which may take some time.
2948 ** When set to 0, only a single message will appear before the reading
2951 ** Also see the ``$$write_inc'' variable.
2953 {"read_only", DT_BOOL, R_NONE, OPTREADONLY, "no" },
2956 ** If set, all folders are opened in read-only mode.
2958 {"realname", DT_STR, R_BOTH, UL &Realname, "" },
2961 ** This variable specifies what ``real'' or ``personal'' name should be used
2962 ** when sending messages.
2964 ** By default, this is the GECOS field from \fT/etc/passwd\fP.
2967 ** variable will \fInot\fP be used when the user has set a real name
2968 ** in the $$from variable.
2970 {"recall", DT_QUAD, R_NONE, OPT_RECALL, "ask-yes" },
2973 ** Controls whether or not Mutt-ng recalls postponed messages
2974 ** when composing a new message. Also see ``$$postponed''.
2976 ** Setting this variable to \fIyes\fP is not generally useful, and thus not
2979 {"record", DT_PATH, R_NONE, UL &Outbox, ""},
2982 ** This specifies the file into which your outgoing messages should be
2983 ** appended. (This is meant as the primary method for saving a copy of
2984 ** your messages, but another way to do this is using the ``$my_hdr''
2985 ** command to create a \fTBcc:\fP header field with your email address in it.)
2987 ** The value of \fI$$record\fP is overridden by the ``$$force_name'' and
2988 ** ``$$save_name'' variables, and the ``$fcc-hook'' command.
2990 {"reply_regexp", DT_RX, R_INDEX|R_RESORT, UL &ReplyRegexp, "^(re([\\[0-9\\]+])*|aw):[ \t]*"},
2993 ** A regular expression used to recognize reply messages when threading
2994 ** and replying. The default value corresponds to the English ``Re:'' and
2995 ** the German ``Aw:''.
2997 {"reply_self", DT_BOOL, R_NONE, OPTREPLYSELF, "no" },
3000 ** If \fIunset\fP and you are replying to a message sent by you, Mutt-ng will
3001 ** assume that you want to reply to the recipients of that message rather
3002 ** than to yourself.
3004 {"reply_to", DT_QUAD, R_NONE, OPT_REPLYTO, "ask-yes" },
3007 ** If \fIset\fP, when replying to a message, Mutt-ng will use the address listed
3008 ** in the ``\fTReply-To:\fP'' header field as the recipient of the reply. If \fIunset\fP,
3009 ** it will use the address in the ``\fTFrom:\fP'' header field instead.
3012 ** option is useful for reading a mailing list that sets the ``\fTReply-To:\fP''
3013 ** header field to the list address and you want to send a private
3014 ** message to the author of a message.
3016 {"resolve", DT_BOOL, R_NONE, OPTRESOLVE, "yes" },
3019 ** When set, the cursor will be automatically advanced to the next
3020 ** (possibly undeleted) message whenever a command that modifies the
3021 ** current message is executed.
3023 {"reverse_alias", DT_BOOL, R_BOTH, OPTREVALIAS, "no" },
3026 ** This variable controls whether or not Mutt-ng will display the ``personal''
3027 ** name from your aliases in the index menu if it finds an alias that
3028 ** matches the message's sender. For example, if you have the following
3031 ** \fTalias juser abd30425@somewhere.net (Joe User)\fP
3033 ** and then you receive mail which contains the following header:
3035 ** \fTFrom: abd30425@somewhere.net\fP
3037 ** It would be displayed in the index menu as ``Joe User'' instead of
3038 ** ``abd30425@somewhere.net.'' This is useful when the person's e-mail
3039 ** address is not human friendly (like CompuServe addresses).
3041 {"reverse_name", DT_BOOL, R_BOTH, OPTREVNAME, "no" },
3044 ** It may sometimes arrive that you receive mail to a certain machine,
3045 ** move the messages to another machine, and reply to some the messages
3046 ** from there. If this variable is \fIset\fP, the default \fTFrom:\fP line of
3047 ** the reply messages is built using the address where you received the
3048 ** messages you are replying to \fBif\fP that address matches your
3049 ** alternates. If the variable is \fIunset\fP, or the address that would be
3050 ** used doesn't match your alternates, the \fTFrom:\fP line will use
3051 ** your address on the current machine.
3053 {"reverse_realname", DT_BOOL, R_BOTH, OPTREVREAL, "yes" },
3056 ** This variable fine-tunes the behaviour of the $reverse_name feature.
3057 ** When it is \fIset\fP, Mutt-ng will use the address from incoming messages as-is,
3058 ** possibly including eventual real names. When it is \fIunset\fP, Mutt-ng will
3059 ** override any such real names with the setting of the $realname variable.
3061 {"rfc2047_parameters", DT_BOOL, R_NONE, OPTRFC2047PARAMS, "no" },
3064 ** When this variable is \fIset\fP, Mutt-ng will decode RFC-2047-encoded MIME
3065 ** parameters. You want to set this variable when Mutt-ng suggests you
3066 ** to save attachments to files named like this:
3068 ** \fT=?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=\fP
3070 ** When this variable is \fIset\fP interactively, the change doesn't have
3071 ** the desired effect before you have changed folders.
3073 ** Note that this use of RFC 2047's encoding is explicitly,
3074 ** prohibited by the standard, but nevertheless encountered in the
3077 ** Also note that setting this parameter will \fInot\fP have the effect
3078 ** that Mutt-ng \fIgenerates\fP this kind of encoding. Instead, Mutt-ng will
3079 ** unconditionally use the encoding specified in RFC 2231.
3081 {"save_address", DT_BOOL, R_NONE, OPTSAVEADDRESS, "no" },
3084 ** If \fIset\fP, Mutt-ng will take the sender's full address when choosing a
3085 ** default folder for saving a mail. If ``$$save_name'' or ``$$force_name''
3086 ** is \fIset\fP too, the selection of the fcc folder will be changed as well.
3088 {"save_empty", DT_BOOL, R_NONE, OPTSAVEEMPTY, "yes" },
3091 ** When \fIunset\fP, mailboxes which contain no saved messages will be removed
3092 ** when closed (the exception is ``$$spoolfile'' which is never removed).
3093 ** If \fIset\fP, mailboxes are never removed.
3095 ** \fBNote:\fP This only applies to mbox and MMDF folders, Mutt-ng does not
3096 ** delete MH and Maildir directories.
3098 {"save_name", DT_BOOL, R_NONE, OPTSAVENAME, "no" },
3101 ** This variable controls how copies of outgoing messages are saved.
3102 ** When set, a check is made to see if a mailbox specified by the
3103 ** recipient address exists (this is done by searching for a mailbox in
3104 ** the ``$$folder'' directory with the \fIusername\fP part of the
3105 ** recipient address). If the mailbox exists, the outgoing message will
3106 ** be saved to that mailbox, otherwise the message is saved to the
3107 ** ``$$record'' mailbox.
3109 ** Also see the ``$$force_name'' variable.
3111 {"score", DT_BOOL, R_NONE, OPTSCORE, "yes" },
3114 ** When this variable is \fIunset\fP, scoring is turned off. This can
3115 ** be useful to selectively disable scoring for certain folders when the
3116 ** ``$$score_threshold_delete'' variable and friends are used.
3119 {"score_threshold_delete", DT_NUM, R_NONE, UL &ScoreThresholdDelete, "-1" },
3122 ** Messages which have been assigned a score equal to or lower than the value
3123 ** of this variable are automatically marked for deletion by Mutt-ng. Since
3124 ** Mutt-ng scores are always greater than or equal to zero, the default setting
3125 ** of this variable will never mark a message for deletion.
3127 {"score_threshold_flag", DT_NUM, R_NONE, UL &ScoreThresholdFlag, "9999" },
3130 ** Messages which have been assigned a score greater than or equal to this
3131 ** variable's value are automatically marked ``flagged''.
3133 {"score_threshold_read", DT_NUM, R_NONE, UL &ScoreThresholdRead, "-1" },
3136 ** Messages which have been assigned a score equal to or lower than the value
3137 ** of this variable are automatically marked as read by Mutt-ng. Since
3138 ** Mutt-ng scores are always greater than or equal to zero, the default setting
3139 ** of this variable will never mark a message read.
3141 {"send_charset", DT_STR, R_NONE, UL &SendCharset, "us-ascii:iso-8859-1:utf-8"},
3144 ** A list of character sets for outgoing messages. Mutt-ng will use the
3145 ** first character set into which the text can be converted exactly.
3146 ** If your ``$$charset'' is not \fTiso-8859-1\fP and recipients may not
3147 ** understand \fTUTF-8\fP, it is advisable to include in the list an
3148 ** appropriate widely used standard character set (such as
3149 ** \fTiso-8859-2\fP, \fTkoi8-r\fP or \fTiso-2022-jp\fP) either
3150 ** instead of or after \fTiso-8859-1\fP.
3152 {"sendmail", DT_PATH, R_NONE, UL &Sendmail, SENDMAIL " -oem -oi"},
3155 ** Specifies the program and arguments used to deliver mail sent by Mutt-ng.
3156 ** Mutt-ng expects that the specified program interprets additional
3157 ** arguments as recipient addresses.
3159 {"sendmail_wait", DT_NUM, R_NONE, UL &SendmailWait, "0" },
3162 ** Specifies the number of seconds to wait for the ``$$sendmail'' process
3163 ** to finish before giving up and putting delivery in the background.
3165 ** Mutt-ng interprets the value of this variable as follows:
3167 ** .dt >0 .dd number of seconds to wait for sendmail to finish before continuing
3168 ** .dt 0 .dd wait forever for sendmail to finish
3169 ** .dt <0 .dd always put sendmail in the background without waiting
3172 ** Note that if you specify a value other than 0, the output of the child
3173 ** process will be put in a temporary file. If there is some error, you
3174 ** will be informed as to where to find the output.
3176 {"shell", DT_PATH, R_NONE, UL &Shell, "" },
3179 ** Command to use when spawning a subshell. By default, the user's login
3180 ** shell from \fT/etc/passwd\fP is used.
3183 {"nntp_save_unsubscribed", DT_BOOL, R_NONE, OPTSAVEUNSUB, "no" },
3186 ** Availability: NNTP
3189 ** When \fIset\fP, info about unsubscribed newsgroups will be saved into the
3190 ** ``newsrc'' file and into the news cache.
3194 {"nntp_show_new_news", DT_BOOL, R_NONE, OPTSHOWNEWNEWS, "yes" },
3197 ** Availability: NNTP
3200 ** If \fIset\fP, the newsserver will be asked for new newsgroups on entering
3201 ** the browser. Otherwise, it will be done only once for a newsserver.
3202 ** Also controls whether or not the number of new articles of subscribed
3203 ** newsgroups will be checked.
3205 {"nntp_show_only_unread", DT_BOOL, R_NONE, OPTSHOWONLYUNREAD, "no" },
3208 ** Availability: NNTP
3211 ** If \fIset\fP, only subscribed newsgroups that contain unread articles
3212 ** will be displayed in the newsgroup browser.
3215 {"sig_dashes", DT_BOOL, R_NONE, OPTSIGDASHES, "yes" },
3218 ** If set, a line containing ``\fT-- \fP'' (dash, dash, space)
3219 ** will be inserted before your ``$$signature''. It is \fBstrongly\fP
3220 ** recommended that you not unset this variable unless your ``signature''
3221 ** contains just your name. The reason for this is because many software
3222 ** packages use ``\fT-- \n\fP'' to detect your signature.
3224 ** For example, Mutt-ng has the ability to highlight
3225 ** the signature in a different color in the builtin pager.
3227 {"sig_on_top", DT_BOOL, R_NONE, OPTSIGONTOP, "no" },
3230 ** If \fIset\fP, the signature will be included before any quoted or forwarded
3231 ** text. It is \fBstrongly\fP recommended that you do not set this variable
3232 ** unless you really know what you are doing, and are prepared to take
3233 ** some heat from netiquette guardians.
3235 {"signature", DT_PATH, R_NONE, UL &Signature, "~/.signature"},
3238 ** Specifies the filename of your signature, which is appended to all
3239 ** outgoing messages. If the filename ends with a pipe (``\fT|\fP''), it is
3240 ** assumed that filename is a shell command and input should be read from
3243 {"signoff_string", DT_STR, R_NONE, UL &SignOffString, "" },
3246 ** If \fIset\fP, this string will be inserted before the signature. This is useful
3247 ** for people that want to sign off every message they send with their name.
3249 ** If you want to insert your website's URL, additional contact information or
3250 ** witty quotes into your mails, better use a signature file instead of
3251 ** the signoff string.
3253 {"simple_search", DT_STR, R_NONE, UL &SimpleSearch, "~f %s | ~s %s"},
3256 ** Specifies how Mutt-ng should expand a simple search into a real search
3257 ** pattern. A simple search is one that does not contain any of the ~
3258 ** operators. See ``$patterns'' for more information on search patterns.
3260 ** For example, if you simply type ``joe'' at a search or limit prompt, Mutt-ng
3261 ** will automatically expand it to the value specified by this variable.
3262 ** For the default value it would be:
3264 ** \fT~f joe | ~s joe\fP
3266 {"smart_wrap", DT_BOOL, R_PAGER, OPTWRAP, "yes" },
3269 ** Controls the display of lines longer than the screen width in the
3270 ** internal pager. If \fIset\fP, long lines are wrapped at a word boundary.
3271 ** If \fIunset\fP, lines are simply wrapped at the screen edge. Also see the
3272 ** ``$$markers'' variable.
3274 {"smileys", DT_RX, R_PAGER, UL &Smileys, "(>From )|(:[-^]?[][)(><}{|/DP])"},
3277 ** The \fIpager\fP uses this variable to catch some common false
3278 ** positives of ``$$quote_regexp'', most notably smileys in the beginning
3281 {"sleep_time", DT_NUM, R_NONE, UL &SleepTime, "1" },
3284 ** Specifies time, in seconds, to pause while displaying certain informational
3285 ** messages, while moving from folder to folder and after expunging
3286 ** messages from the current folder. The default is to pause one second, so
3287 ** a value of zero for this option suppresses the pause.
3289 {"sort", DT_SORT, R_INDEX|R_RESORT, UL &Sort, "date" },
3292 ** Specifies how to sort messages in the \fIindex\fP menu. Valid values
3296 ** . date or date-sent
3299 ** . mailbox-order (unsorted)
3308 ** You may optionally use the ``reverse-'' prefix to specify reverse sorting
3309 ** order (example: \fTset sort=reverse-date-sent\fP).
3311 {"sort_alias", DT_SORT|DT_SORT_ALIAS, R_NONE, UL &SortAlias, "alias" },
3314 ** Specifies how the entries in the ``alias'' menu are sorted. The
3315 ** following are legal values:
3318 ** . address (sort alphabetically by email address)
3319 ** . alias (sort alphabetically by alias name)
3320 ** . unsorted (leave in order specified in .muttrc)
3323 {"sort_aux", DT_SORT|DT_SORT_AUX, R_INDEX|R_RESORT_BOTH, UL &SortAux, "date" },
3326 ** When sorting by threads, this variable controls how threads are sorted
3327 ** in relation to other threads, and how the branches of the thread trees
3328 ** are sorted. This can be set to any value that ``$$sort'' can, except
3329 ** threads (in that case, Mutt-ng will just use date-sent). You can also
3330 ** specify the ``last-'' prefix in addition to ``reverse-'' prefix, but last-
3331 ** must come after reverse-. The last- prefix causes messages to be
3332 ** sorted against its siblings by which has the last descendant, using
3333 ** the rest of sort_aux as an ordering.
3335 ** For instance, \fTset sort_aux=last-date-received\fP would mean that if
3336 ** a new message is received in a thread, that thread becomes the last one
3337 ** displayed (or the first, if you have \fTset sort=reverse-threads\fP.)
3339 ** \fBNote:\fP For reversed ``$$sort'' order $$sort_aux is reversed again
3340 ** (which is not the right thing to do, but kept to not break any existing
3341 ** configuration setting).
3343 {"sort_browser", DT_SORT|DT_SORT_BROWSER, R_NONE, UL &BrowserSort, "alpha" },
3346 ** Specifies how to sort entries in the file browser. By default, the
3347 ** entries are sorted alphabetically. Valid values:
3350 ** . alpha (alphabetically)
3356 ** You may optionally use the ``reverse-'' prefix to specify reverse sorting
3357 ** order (example: \fTset sort_browser=reverse-date\fP).
3359 {"sort_re", DT_BOOL, R_INDEX|R_RESORT|R_RESORT_INIT, OPTSORTRE, "yes" },
3362 ** This variable is only useful when sorting by threads with
3363 ** ``$$strict_threads'' \fIunset\fP. In that case, it changes the heuristic
3364 ** Mutt-ng uses to thread messages by subject. With $$sort_re \fIset\fP,
3365 ** Mutt-ng will only attach a message as the child of another message by
3366 ** subject if the subject of the child message starts with a substring
3367 ** matching the setting of ``$$reply_regexp''. With $$sort_re \fIunset\fP,
3368 ** Mutt-ng will attach the message whether or not this is the case,
3369 ** as long as the non-``$$reply_regexp'' parts of both messages are identical.
3371 {"spam_separator", DT_STR, R_NONE, UL &SpamSep, ","},
3374 ** ``$spam_separator'' controls what happens when multiple spam headers
3375 ** are matched: if \fIunset\fP, each successive header will overwrite any
3376 ** previous matches value for the spam label. If \fIset\fP, each successive
3377 ** match will append to the previous, using ``$spam_separator'' as a
3380 {"spoolfile", DT_PATH, R_NONE, UL &Spoolfile, "" },
3383 ** If your spool mailbox is in a non-default place where Mutt-ng cannot find
3384 ** it, you can specify its location with this variable. Mutt-ng will
3385 ** automatically set this variable to the value of the environment
3386 ** variable $$$MAIL if it is not set.
3388 {"status_chars", DT_STR, R_BOTH, UL &StChars, "-*%A"},
3391 ** Controls the characters used by the ``\fT%r\fP'' indicator in
3392 ** ``$$status_format''. The first character is used when the mailbox is
3393 ** unchanged. The second is used when the mailbox has been changed, and
3394 ** it needs to be resynchronized. The third is used if the mailbox is in
3395 ** read-only mode, or if the mailbox will not be written when exiting
3396 ** that mailbox (You can toggle whether to write changes to a mailbox
3397 ** with the toggle-write operation, bound by default to ``\fT%\fP'').
3398 ** The fourth is used to indicate that the current folder has been
3399 ** opened in attach-message mode (Certain operations like composing
3400 ** a new mail, replying, forwarding, etc. are not permitted in this mode).
3402 {"status_format", DT_STR, R_BOTH, UL &Status, "-%r-Mutt-ng: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l? %l?]---(%s/%S)-%>-(%P)---"},
3405 ** Controls the format of the status line displayed in the \fIindex\fP
3406 ** menu. This string is similar to ``$$index_format'', but has its own
3407 ** set of \fTprintf(3)\fP-like sequences:
3410 ** .dt %b .dd number of mailboxes with new mail *
3411 ** .dt %B .dd the short pathname of the current mailbox
3412 ** .dt %d .dd number of deleted messages *
3413 ** .dt %f .dd the full pathname of the current mailbox
3414 ** .dt %F .dd number of flagged messages *
3415 ** .dt %h .dd local hostname
3416 ** .dt %l .dd size (in bytes) of the current mailbox *
3417 ** .dt %L .dd size (in bytes) of the messages shown
3418 ** (i.e., which match the current limit) *
3419 ** .dt %m .dd the number of messages in the mailbox *
3420 ** .dt %M .dd the number of messages shown (i.e., which match the current limit) *
3421 ** .dt %n .dd number of new messages in the mailbox *
3422 ** .dt %o .dd number of old unread messages *
3423 ** .dt %p .dd number of postponed messages *
3424 ** .dt %P .dd percentage of the way through the index
3425 ** .dt %r .dd modified/read-only/won't-write/attach-message indicator,
3426 ** according to $$status_chars
3427 ** .dt %s .dd current sorting mode ($$sort)
3428 ** .dt %S .dd current aux sorting method ($$sort_aux)
3429 ** .dt %t .dd number of tagged messages *
3430 ** .dt %u .dd number of unread messages *
3431 ** .dt %v .dd Mutt-ng version string
3432 ** .dt %V .dd currently active limit pattern, if any *
3433 ** .dt %>X .dd right justify the rest of the string and pad with "X"
3434 ** .dt %|X .dd pad to the end of the line with "X"
3437 ** * = can be optionally printed if nonzero
3439 ** Some of the above sequences can be used to optionally print a string
3440 ** if their value is nonzero. For example, you may only want to see the
3441 ** number of flagged messages if such messages exist, since zero is not
3442 ** particularly meaningful. To optionally print a string based upon one
3443 ** of the above sequences, the following construct is used
3445 ** \fT%?<sequence_char>?<optional_string>?\fP
3447 ** where \fIsequence_char\fP is a character from the table above, and
3448 ** \fIoptional_string\fP is the string you would like printed if
3449 ** \fIsequence_char\fP is nonzero. \fIoptional_string\fP \fBmay\fP contain
3450 ** other sequences as well as normal text, but you may \fBnot\fP nest
3451 ** optional strings.
3453 ** Here is an example illustrating how to optionally print the number of
3454 ** new messages in a mailbox:
3456 ** \fT%?n?%n new messages.?\fP
3458 ** Additionally you can switch between two strings, the first one, if a
3459 ** value is zero, the second one, if the value is nonzero, by using the
3460 ** following construct:
3462 ** \fT%?<sequence_char>?<if_string>&<else_string>?\fP
3464 ** You can additionally force the result of any \fTprintf(3)\fP-like sequence
3465 ** to be lowercase by prefixing the sequence character with an underscore
3466 ** (\fT_\fP) sign. For example, if you want to display the local hostname in
3467 ** lowercase, you would use:
3471 ** If you prefix the sequence character with a colon (\fT:\fP) character, Mutt-ng
3472 ** will replace any dots in the expansion by underscores. This might be helpful
3473 ** with IMAP folders that don't like dots in folder names.
3475 {"status_on_top", DT_BOOL, R_BOTH, OPTSTATUSONTOP, "no" },
3478 ** Setting this variable causes the ``status bar'' to be displayed on
3479 ** the first line of the screen rather than near the bottom.
3481 {"strict_mailto", DT_BOOL, R_NONE, OPTSTRICTMAILTO, "yes" },
3485 ** With mailto: style links, a body as well as arbitrary header information
3486 ** may be embedded. This may lead to (user) headers being overwriten without note
3487 ** if ``$$edit_headers'' is unset.
3490 ** If this variable is \fIset\fP, mutt-ng is strict and allows anything to be
3491 ** changed. If it's \fIunset\fP, all headers given will be prefixed with
3492 ** ``X-Mailto-'' and the message including headers will be shown in the editor
3493 ** regardless of what ``$$edit_headers'' is set to.
3495 {"strict_mime", DT_BOOL, R_NONE, OPTSTRICTMIME, "yes" },
3498 ** When \fIunset\fP, non MIME-compliant messages that doesn't have any
3499 ** charset indication in the ``\fTContent-Type:\fP'' header field can
3500 ** be displayed (non MIME-compliant messages are often generated by old
3501 ** mailers or buggy mailers like MS Outlook Express).
3502 ** See also $$assumed_charset.
3504 ** This option also replaces linear-white-space between encoded-word
3505 ** and *text to a single space to prevent the display of MIME-encoded
3506 ** ``\fTSubject:\fP'' header field from being devided into multiple lines.
3508 {"strict_threads", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTSTRICTTHREADS, "no" },
3511 ** If \fIset\fP, threading will only make use of the ``\fTIn-Reply-To:\fP'' and
3512 ** ``\fTReferences:\fP'' header fields when you ``$$sort'' by message threads. By
3513 ** default, messages with the same subject are grouped together in
3514 ** ``pseudo threads.'' This may not always be desirable, such as in a
3515 ** personal mailbox where you might have several unrelated messages with
3516 ** the subject ``hi'' which will get grouped together.
3518 {"strip_was", DT_BOOL, R_NONE, OPTSTRIPWAS, "no" },
3521 ** When \fIset\fP, mutt-ng will remove the trailing part of the ``\fTSubject:\fP''
3522 ** line which matches $$strip_was_regex when replying. This is useful to
3523 ** properly react on subject changes and reduce ``subject noise.'' (esp. in Usenet)
3525 {"strip_was_regex", DT_RX, R_NONE, UL &StripWasRegexp, "\\([Ww][Aa][RrSs]: .*\\)[ ]*$"},
3528 ** When non-empty and $$strip_was is \fIset\fP, mutt-ng will remove this
3529 ** trailing part of the ``Subject'' line when replying if it won't be empty
3532 {"stuff_quoted", DT_BOOL, R_BOTH, OPTSTUFFQUOTED, "no" },
3535 ** If \fIset\fP, attachments with flowed format will have their quoting ``stuffed'',
3536 ** i.e. a space will be inserted between the quote characters and the actual
3539 {"suspend", DT_BOOL, R_NONE, OPTSUSPEND, "yes" },
3542 ** When \fIunset\fP, Mutt-ng won't stop when the user presses the terminal's
3543 ** \fIsusp\fP key, usually \fTCTRL+Z\fP. This is useful if you run Mutt-ng
3544 ** inside an xterm using a command like ``\fTxterm -e muttng\fP.''
3546 {"text_flowed", DT_BOOL, R_NONE, OPTTEXTFLOWED, "no" },
3549 ** When \fIset\fP, Mutt-ng will generate \fTtext/plain; format=flowed\fP attachments.
3550 ** This format is easier to handle for some mailing software, and generally
3551 ** just looks like ordinary text. To actually make use of this format's
3552 ** features, you'll need support in your editor.
3554 ** Note that $$indent_string is ignored when this option is set.
3556 {"thread_received", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTTHREADRECEIVED, "no" },
3559 ** When \fIset\fP, Mutt-ng uses the date received rather than the date sent
3560 ** to thread messages by subject.
3562 {"thorough_search", DT_BOOL, R_NONE, OPTTHOROUGHSRC, "no" },
3565 ** Affects the \fT~b\fP and \fT~h\fP search operations described in
3566 ** section ``$patterns'' above. If \fIset\fP, the headers and attachments of
3567 ** messages to be searched are decoded before searching. If \fIunset\fP,
3568 ** messages are searched as they appear in the folder.
3570 {"tilde", DT_BOOL, R_PAGER, OPTTILDE, "no" },
3573 ** When \fIset\fP, the internal-pager will pad blank lines to the bottom of the
3574 ** screen with a tilde (~).
3576 {"timeout", DT_NUM, R_NONE, UL &Timeout, "600" },
3579 ** This variable controls the \fInumber of seconds\fP Mutt-ng will wait
3580 ** for a key to be pressed in the main menu before timing out and
3581 ** checking for new mail. A value of zero or less will cause Mutt-ng
3582 ** to never time out.
3584 {"tmpdir", DT_PATH, R_NONE, UL &Tempdir, "" },
3587 ** This variable allows you to specify where Mutt-ng will place its
3588 ** temporary files needed for displaying and composing messages. If
3589 ** this variable is not set, the environment variable \fT$$$TMPDIR\fP is
3590 ** used. If \fT$$$TMPDIR\fP is not set then "\fT/tmp\fP" is used.
3592 {"to_chars", DT_STR, R_BOTH, UL &Tochars, " +TCFL"},
3595 ** Controls the character used to indicate mail addressed to you. The
3596 ** first character is the one used when the mail is NOT addressed to your
3597 ** address (default: space). The second is used when you are the only
3598 ** recipient of the message (default: +). The third is when your address
3599 ** appears in the ``\fTTo:\fP'' header field, but you are not the only recipient of
3600 ** the message (default: T). The fourth character is used when your
3601 ** address is specified in the ``\fTCc:\fP'' header field, but you are not the only
3602 ** recipient. The fifth character is used to indicate mail that was sent
3603 ** by \fIyou\fP. The sixth character is used to indicate when a mail
3604 ** was sent to a mailing-list you're subscribe to (default: L).
3606 {"trash", DT_PATH, R_NONE, UL &TrashPath, "" },
3609 ** If \fIset\fP, this variable specifies the path of the trash folder where the
3610 ** mails marked for deletion will be moved, instead of being irremediably
3613 ** \fBNote\fP: When you delete a message in the trash folder, it is really
3614 ** deleted, so that there is no way to recover mail.
3617 {"tunnel", DT_STR, R_NONE, UL &Tunnel, "" },
3620 ** Setting this variable will cause Mutt-ng to open a pipe to a command
3621 ** instead of a raw socket. You may be able to use this to set up
3622 ** preauthenticated connections to your IMAP/POP3 server. Example:
3624 ** \fTtunnel="ssh -q mailhost.net /usr/local/libexec/imapd"\fP
3626 ** \fBNote:\fP For this example to work you must be able to log in to the remote
3627 ** machine without having to enter a password.
3630 {"umask", DT_NUM, R_NONE, UL &Umask, "0077" },
3633 ** This sets the umask that will be used by Mutt-ng when creating all
3634 ** kinds of files. If \fIunset\fP, the default value is \fT077\fP.
3636 {"use_8bitmime", DT_BOOL, R_NONE, OPTUSE8BITMIME, "no" },
3639 ** \fBWarning:\fP do not set this variable unless you are using a version
3640 ** of sendmail which supports the \fT-B8BITMIME\fP flag (such as sendmail
3641 ** 8.8.x) or in connection with the SMTP support via libESMTP.
3642 ** Otherwise you may not be able to send mail.
3644 ** When \fIset\fP, Mutt-ng will either invoke ``$$sendmail'' with the \fT-B8BITMIME\fP
3645 ** flag when sending 8-bit messages to enable ESMTP negotiation or tell
3646 ** libESMTP to do so.
3648 {"use_domain", DT_BOOL, R_NONE, OPTUSEDOMAIN, "yes" },
3651 ** When \fIset\fP, Mutt-ng will qualify all local addresses (ones without the
3652 ** @host portion) with the value of ``$$hostname''. If \fIunset\fP, no
3653 ** addresses will be qualified.
3655 {"use_from", DT_BOOL, R_NONE, OPTUSEFROM, "yes" },
3658 ** When \fIset\fP, Mutt-ng will generate the ``\fTFrom:\fP'' header field when
3659 ** sending messages. If \fIunset\fP, no ``\fTFrom:\fP'' header field will be
3660 ** generated unless the user explicitly sets one using the ``$my_hdr''
3664 {"use_idn", DT_BOOL, R_BOTH, OPTUSEIDN, "yes" },
3667 ** Availability: IDN
3670 ** When \fIset\fP, Mutt-ng will show you international domain names decoded.
3672 ** \fBNote:\fP You can use IDNs for addresses even if this is \fIunset\fP.
3673 ** This variable only affects decoding.
3675 #endif /* HAVE_LIBIDN */
3676 #ifdef HAVE_GETADDRINFO
3677 {"use_ipv6", DT_BOOL, R_NONE, OPTUSEIPV6, "yes" },
3680 ** When \fIset\fP, Mutt-ng will look for IPv6 addresses of hosts it tries to
3681 ** contact. If this option is \fIunset\fP, Mutt-ng will restrict itself to IPv4 addresses.
3682 ** Normally, the default should work.
3684 #endif /* HAVE_GETADDRINFO */
3685 {"user_agent", DT_SYN, R_NONE, UL "agent_string", 0 },
3686 {"agent_string", DT_BOOL, R_NONE, OPTXMAILER, "yes" },
3689 ** When \fIset\fP, Mutt-ng will add a ``\fTUser-Agent:\fP'' header to outgoing
3690 ** messages, indicating which version of Mutt-ng was used for composing
3693 {"visual", DT_PATH, R_NONE, UL &Visual, "" },
3696 ** Specifies the visual editor to invoke when the \fI~v\fP command is
3697 ** given in the builtin editor.
3699 {"wait_key", DT_BOOL, R_NONE, OPTWAITKEY, "yes" },
3702 ** Controls whether Mutt-ng will ask you to press a key after \fIshell-
3703 ** escape\fP, \fIpipe-message\fP, \fIpipe-entry\fP, \fIprint-message\fP,
3704 ** and \fIprint-entry\fP commands.
3706 ** It is also used when viewing attachments with ``$auto_view'', provided
3707 ** that the corresponding mailcap entry has a \fTneedsterminal\fP flag,
3708 ** and the external program is interactive.
3710 ** When \fIset\fP, Mutt-ng will always ask for a key. When \fIunset\fP, Mutt-ng will wait
3711 ** for a key only if the external command returned a non-zero status.
3713 {"weed", DT_BOOL, R_NONE, OPTWEED, "yes" },
3716 ** When \fIset\fP, Mutt-ng will weed headers when displaying, forwarding,
3717 ** printing, or replying to messages.
3719 {"wrap_search", DT_BOOL, R_NONE, OPTWRAPSEARCH, "yes" },
3722 ** Controls whether searches wrap around the end of the mailbox.
3724 ** When \fIset\fP, searches will wrap around the first (or last) message. When
3725 ** \fIunset\fP, searches will not wrap.
3727 {"wrapmargin", DT_NUM, R_PAGER, UL &WrapMargin, "0" },
3730 ** Controls the size of the margin remaining at the right side of
3731 ** the terminal when Mutt-ng's pager does smart wrapping.
3733 {"write_inc", DT_NUM, R_NONE, UL &WriteInc, "10" },
3736 ** When writing a mailbox, a message will be printed every
3737 ** \fIwrite_inc\fP messages to indicate progress. If set to 0, only a
3738 ** single message will be displayed before writing a mailbox.
3740 ** Also see the ``$$read_inc'' variable.
3742 {"write_bcc", DT_BOOL, R_NONE, OPTWRITEBCC, "yes" },
3745 ** Controls whether Mutt-ng writes out the Bcc header when preparing
3746 ** messages to be sent. Exim users may wish to \fIunset\fP this.
3748 {"xterm_icon", DT_STR, R_BOTH, UL &XtermIcon, "M%?n?AIL&ail?"},
3751 ** Controls the format of the X11 icon title, as long as $$xterm_set_titles
3752 ** is \fIset\fP. This string is identical in formatting to the one used by
3753 ** ``$$status_format''.
3755 {"xterm_set_titles", DT_BOOL, R_BOTH, OPTXTERMSETTITLES, "no" },
3758 ** Controls whether Mutt-ng sets the xterm title bar and icon name
3759 ** (as long as you're in an appropriate terminal). The default must
3760 ** be \fIunset\fP to force in the validity checking.
3762 {"xterm_leave", DT_STR, R_BOTH, UL &XtermLeave, "" },
3765 ** If $$xterm_set_titles is \fIset\fP, this string will be used to
3766 ** set the title when leaving mutt-ng. For terminal-based programs,
3767 ** there's no easy and portable way to read the current title so mutt-ng
3768 ** cannot read it upon startup and restore it when exiting.
3771 ** Based on the xterm FAQ, the following might work:
3774 ** \fTset xterm_leave = "`test x$$$DISPLAY != x && xprop -id $$$WINDOWID | grep WM_NAME | cut -d '"' -f 2`"\fP
3776 {"xterm_title", DT_STR, R_BOTH, UL &XtermTitle, "Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?"},
3779 ** Controls the format of the title bar of the xterm provided that
3780 ** $$xterm_set_titles has been \fIset\fP. This string is identical in formatting
3781 ** to the one used by ``$$status_format''.
3784 {"nntp_x_comment_to", DT_BOOL, R_NONE, OPTXCOMMENTTO, "no" },
3787 ** Availability: NNTP
3790 ** If \fIset\fP, Mutt-ng will add a ``\fTX-Comment-To:\fP'' header field
3791 ** (that contains full name of the original article author) to articles that
3799 static const char* Features[] = {
3800 #ifdef NCURSES_VERSION
3803 #ifdef USE_SLANG_CURSES
3806 #ifdef _LIBICONV_VERSION
3815 #ifdef DL_STANDALONE
3842 #ifdef USE_COMPRESSED
3848 #ifdef CRYPT_BACKEND_CLASSIC_PGP
3851 #ifdef CRYPT_BACKEND_CLASSIC_SMIME
3854 #ifdef CRYPT_BACKEND_GPGME
3873 const struct mapping_t SortMethods[] = {
3874 {"date", SORT_DATE},
3875 {"date-sent", SORT_DATE},
3876 {"date-received", SORT_RECEIVED},
3877 {"mailbox-order", SORT_ORDER},
3878 {"subject", SORT_SUBJECT},
3879 {"from", SORT_FROM},
3880 {"size", SORT_SIZE},
3881 {"threads", SORT_THREADS},
3883 {"score", SORT_SCORE},
3884 {"spam", SORT_SPAM},
3888 /* same as SortMethods, but with "threads" replaced by "date" */
3890 const struct mapping_t SortAuxMethods[] = {
3891 {"date", SORT_DATE},
3892 {"date-sent", SORT_DATE},
3893 {"date-received", SORT_RECEIVED},
3894 {"mailbox-order", SORT_ORDER},
3895 {"subject", SORT_SUBJECT},
3896 {"from", SORT_FROM},
3897 {"size", SORT_SIZE},
3898 {"threads", SORT_DATE}, /* note: sort_aux == threads
3902 {"score", SORT_SCORE},
3903 {"spam", SORT_SPAM},
3908 const struct mapping_t SortBrowserMethods[] = {
3909 {"alpha", SORT_SUBJECT},
3910 {"date", SORT_DATE},
3911 {"size", SORT_SIZE},
3912 {"unsorted", SORT_ORDER},
3916 const struct mapping_t SortAliasMethods[] = {
3917 {"alias", SORT_ALIAS},
3918 {"address", SORT_ADDRESS},
3919 {"unsorted", SORT_ORDER},
3923 const struct mapping_t SortKeyMethods[] = {
3924 {"address", SORT_ADDRESS},
3925 {"date", SORT_DATE},
3926 {"keyid", SORT_KEYID},
3927 {"trust", SORT_TRUST},
3932 /* functions used to parse commands in a rc file */
3934 static int parse_list (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3935 static int parse_spam_list (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3936 static int parse_unlist (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3938 static int parse_lists (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3939 static int parse_unlists (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3940 static int parse_alias (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3941 static int parse_unalias (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3942 static int parse_ifdef (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3943 static int parse_ignore (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3944 static int parse_unignore (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3945 static int parse_source (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3946 static int parse_set (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3947 static int parse_my_hdr (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3948 static int parse_unmy_hdr (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3949 static int parse_subscribe (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3950 static int parse_unsubscribe (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3952 static int parse_alternates (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3953 static int parse_unalternates (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3957 int (*func) (BUFFER *, BUFFER *, unsigned long, BUFFER *);
3959 unsigned long data1;
3962 struct command_t Commands[] = {
3963 {"alternates", parse_alternates, 0},
3964 {"unalternates", parse_unalternates, 0},
3966 {"account-hook", mutt_parse_hook, M_ACCOUNTHOOK},
3968 {"alias", parse_alias, 0},
3969 {"auto_view", parse_list, UL &AutoViewList},
3970 {"alternative_order", parse_list, UL &AlternativeOrderList},
3971 {"bind", mutt_parse_bind, 0},
3972 {"charset-hook", mutt_parse_hook, M_CHARSETHOOK},
3974 {"color", mutt_parse_color, 0},
3975 {"uncolor", mutt_parse_uncolor, 0},
3977 {"exec", mutt_parse_exec, 0},
3978 {"fcc-hook", mutt_parse_hook, M_FCCHOOK},
3979 {"fcc-save-hook", mutt_parse_hook, M_FCCHOOK|M_SAVEHOOK},
3980 {"folder-hook", mutt_parse_hook, M_FOLDERHOOK},
3981 #ifdef USE_COMPRESSED
3982 {"open-hook", mutt_parse_hook, M_OPENHOOK},
3983 {"close-hook", mutt_parse_hook, M_CLOSEHOOK},
3984 {"append-hook", mutt_parse_hook, M_APPENDHOOK},
3986 {"hdr_order", parse_list, UL &HeaderOrderList},
3987 {"ifdef", parse_ifdef, 1},
3988 {"ifndef", parse_ifdef, 0},
3990 {"iconv-hook", mutt_parse_hook, M_ICONVHOOK},
3992 {"ignore", parse_ignore, 0},
3993 {"lists", parse_lists, 0},
3994 {"macro", mutt_parse_macro, 0},
3995 {"mailboxes", buffy_parse_mailboxes, M_MAILBOXES},
3996 {"unmailboxes", buffy_parse_mailboxes, M_UNMAILBOXES},
3997 {"message-hook", mutt_parse_hook, M_MESSAGEHOOK},
3998 {"mbox-hook", mutt_parse_hook, M_MBOXHOOK},
3999 {"mime_lookup", parse_list, UL &MimeLookupList},
4000 {"unmime_lookup", parse_unlist, UL &MimeLookupList},
4001 {"mono", mutt_parse_mono, 0},
4002 {"my_hdr", parse_my_hdr, 0},
4003 {"pgp-hook", mutt_parse_hook, M_CRYPTHOOK},
4004 {"crypt-hook", mutt_parse_hook, M_CRYPTHOOK},
4005 {"push", mutt_parse_push, 0},
4006 {"reply-hook", mutt_parse_hook, M_REPLYHOOK},
4007 {"reset", parse_set, M_SET_RESET},
4008 {"save-hook", mutt_parse_hook, M_SAVEHOOK},
4009 {"score", mutt_parse_score, 0},
4010 {"send-hook", mutt_parse_hook, M_SENDHOOK},
4011 {"send2-hook", mutt_parse_hook, M_SEND2HOOK},
4012 {"set", parse_set, 0},
4013 {"source", parse_source, 0},
4014 {"spam", parse_spam_list, M_SPAM},
4015 {"nospam", parse_spam_list, M_NOSPAM},
4016 {"subscribe", parse_subscribe, 0},
4017 {"toggle", parse_set, M_SET_INV},
4018 {"unalias", parse_unalias, 0},
4019 {"unalternative_order", parse_unlist, UL &AlternativeOrderList},
4020 {"unauto_view", parse_unlist, UL &AutoViewList},
4021 {"unhdr_order", parse_unlist, UL &HeaderOrderList},
4022 {"unhook", mutt_parse_unhook, 0},
4023 {"unignore", parse_unignore, 0},
4024 {"unlists", parse_unlists, 0},
4025 {"unmono", mutt_parse_unmono, 0},
4026 {"unmy_hdr", parse_unmy_hdr, 0},
4027 {"unscore", mutt_parse_unscore, 0},
4028 {"unset", parse_set, M_SET_UNSET},
4029 {"unsubscribe", parse_unsubscribe, 0},