X-Git-Url: http://git.madism.org/?p=apps%2Fmadmutt.git;a=blobdiff_plain;f=doc%2Fmanual.txt;h=9e59608d27c52afdce8c30e588365a65496a1f30;hp=b162ee5e82f1a354283db3565a37a1ab462425a1;hb=7132fe3b1612c153f3638d1f9664ba9eab9063d6;hpb=c6b020e0fa5c38e4fd8a6ffb75e00338c0535b11 diff --git a/doc/manual.txt b/doc/manual.txt index b162ee5..9e59608 100644 --- a/doc/manual.txt +++ b/doc/manual.txt @@ -4,7 +4,7 @@ by Andreas Krennmair and others originally based on _m_u_t_t by Michael Elkins and others - version devel-r392 + version devel-r471 AAbbssttrraacctt @@ -316,7 +316,7 @@ ^G n/a abort n/a finish editing - You can remap the _e_d_i_t_o_r functions using the _b_i_n_d (section 3.4 , page 24) com- + You can remap the _e_d_i_t_o_r functions using the _b_i_n_d (section 3.5 , page 27) com- mand. For example, to make the _D_e_l_e_t_e key delete the character in front of the cursor rather than under, you could use @@ -413,7 +413,7 @@ +o cclleeaarr--ffllaagg (default: W) Furthermore, the following flags reflect who the message is addressed to. They - can be customized with the _$_t_o___c_h_a_r_s (section 6.4.323 , page 162) variable. + can be customized with the _$_t_o___c_h_a_r_s (section 7.4.339 , page 172) variable. + message is to you and you only @@ -461,7 +461,7 @@ letter again for bold or the letter, backspace, ``_'' for denoting underline. Mutt-ng will attempt to display these in bold and underline respectively if your terminal supports them. If not, you can use the bold and underline _c_o_l_o_r - (section 3.8 , page 27) objects to specify a color or mono attribute for them. + (section 3.9 , page 31) objects to specify a color or mono attribute for them. Additionally, the internal pager supports the ANSI escape sequences for charac- ter attributes. Mutt-ng translates them into the correct color and character @@ -490,14 +490,14 @@ The Mutt Next Generation E-Mail Client 11 Mutt-ng uses these attributes for handling text/enriched messages, and they can - also be used by an external _a_u_t_o_v_i_e_w (section 5.4 , page 75) script for high- + also be used by an external _a_u_t_o_v_i_e_w (section 5.4 , page 79) script for high- lighting purposes. NNoottee:: If you change the colors for your display, for exam- ple by changing the color associated with color2 for your xterm, then that color will be used instead of green. _2_._5_._3 _T_h_r_e_a_d_e_d _M_o_d_e - When the mailbox is _s_o_r_t_e_d (section 6.4.291 , page 152) by _t_h_r_e_a_d_s, there are + When the mailbox is _s_o_r_t_e_d (section 7.4.307 , page 163) by _t_h_r_e_a_d_s, there are a few additional functions available in the _i_n_d_e_x and _p_a_g_e_r modes. ^D delete-thread delete all messages in the current thread @@ -518,11 +518,11 @@ NNoottee:: Collapsing a thread displays only the first message in the thread and hides the others. This is useful when threads contain so many messages that you can only see a handful of threads on the screen. See %M in _$_i_n_d_e_x___f_o_r_m_a_t (sec- - tion 6.4.110 , page 108). For example, you could use "%?M?(#%03M)&(%4l)?" in - _$_i_n_d_e_x___f_o_r_m_a_t (section 6.4.110 , page 108) to optionally display the number of + tion 7.4.116 , page 116). For example, you could use "%?M?(#%03M)&(%4l)?" in + _$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.116 , page 116) to optionally display the number of hidden messages if the thread is collapsed. - See also: _$_s_t_r_i_c_t___t_h_r_e_a_d_s (section 6.4.312 , page 160). + See also: _$_s_t_r_i_c_t___t_h_r_e_a_d_s (section 7.4.328 , page 170). _2_._5_._4 _M_i_s_c_e_l_l_a_n_e_o_u_s _F_u_n_c_t_i_o_n_s @@ -530,11 +530,11 @@ (default: a) Creates a new alias based upon the current message (or prompts for a new one). - Once editing is complete, an _a_l_i_a_s (section 3.3 , page 23) command is added to - the file specified by the _$_a_l_i_a_s___f_i_l_e (section 6.4.3 , page 83) variable for - future use. NNoottee:: Specifying an _$_a_l_i_a_s___f_i_l_e (section 6.4.3 , page 83) does not - add the aliases specified there-in, you must also _s_o_u_r_c_e (section 3.28 , page - 42) the file. + Once editing is complete, an _a_l_i_a_s (section 3.4 , page 26) command is added to + the file specified by the _$_a_l_i_a_s___f_i_l_e (section 7.4.5 , page 90) variable for + future use. NNoottee:: Specifying an _$_a_l_i_a_s___f_i_l_e (section 7.4.5 , page 90) does not + add the aliases specified there-in, you must also _s_o_u_r_c_e (section 3.29 , page + 46) the file. cchheecckk--ttrraaddiittiioonnaall--ppggpp (default: ESC P) @@ -552,7 +552,7 @@ (default: h) Toggles the weeding of message header fields specified by _i_g_n_o_r_e (section - 3.9 , page 30) commands. + 3.10 , page 33) commands. eeddiitt (default: e) @@ -570,12 +570,12 @@ This command is used to temporarily edit an attachment's content type to fix, for instance, bogus character set parameters. When invoked from the index or from the pager, you'll have the opportunity to edit the top-level attachment's - content type. On the _a_t_t_a_c_h_m_e_n_t _m_e_n_u (section 5.1.2 , page 67), you can + content type. On the _a_t_t_a_c_h_m_e_n_t _m_e_n_u (section 5.1.2 , page 71), you can change any attachment's content type. These changes are not persistent, and get lost upon changing folders. Note that this command is also available on the _c_o_m_p_o_s_e _m_e_n_u (section 5.1.3 , - page 68). There, it's used to fine-tune the properties of attachments you are + page 72). There, it's used to fine-tune the properties of attachments you are going to send. eenntteerr--ccoommmmaanndd @@ -583,7 +583,7 @@ This command is used to execute any command you would normally put in a config- uration file. A common use is to check the settings of variables, or in con- - junction with _m_a_c_r_o_s (section 3.7 , page 27) to change settings on the fly. + junction with _m_a_c_r_o_s (section 3.8 , page 30) to change settings on the fly. eexxttrraacctt--kkeeyyss (default: ^K) @@ -603,9 +603,9 @@ (default: L) Reply to the current or tagged message(s) by extracting any addresses which - match the regular expressions given by the _l_i_s_t_s _o_r _s_u_b_s_c_r_i_b_e (section 3.12 , - page 32) commands, but also honor any Mail-Followup-To header(s) if the - _$_h_o_n_o_r___f_o_l_l_o_w_u_p___t_o (section 6.4.88 , page 103) configuration variable is set. + match the regular expressions given by the _l_i_s_t_s _o_r _s_u_b_s_c_r_i_b_e (section 3.13 , + page 36) commands, but also honor any Mail-Followup-To header(s) if the + _$_h_o_n_o_r___f_o_l_l_o_w_u_p___t_o (section 7.4.94 , page 111) configuration variable is set. Using this when replying to messages posted to mailing lists helps avoid dupli- cate copies being sent to the author of the message you are replying to. @@ -613,9 +613,9 @@ (default: |) Asks for an external Unix command and pipes the current or tagged message(s) to - it. The variables _$_p_i_p_e___d_e_c_o_d_e (section 6.4.200 , page 131), _$_p_i_p_e___s_p_l_i_t - (section 6.4.202 , page 132), _$_p_i_p_e___s_e_p (section 6.4.201 , page 132) and - _$_w_a_i_t___k_e_y (section 6.4.335 , page 164) control the exact behavior of this + it. The variables _$_p_i_p_e___d_e_c_o_d_e (section 7.4.216 , page 142), _$_p_i_p_e___s_p_l_i_t + (section 7.4.218 , page 142), _$_p_i_p_e___s_e_p (section 7.4.217 , page 142) and + _$_w_a_i_t___k_e_y (section 7.4.350 , page 174) control the exact behavior of this function. rreesseenndd--mmeessssaaggee @@ -625,7 +625,7 @@ message. This function is best described as "recall from arbitrary folders". It can conveniently be used to forward MIME messages while preserving the orig- inal mail structure. Note that the amount of headers included here depends on - the value of the _$_w_e_e_d (section 6.4.336 , page 165) variable. + the value of the _$_w_e_e_d (section 7.4.351 , page 175) variable. This function is also available from the attachment menu. You can use this to easily resend a message which was included with a bounce message as a mes- @@ -635,14 +635,14 @@ (default: !) Asks for an external Unix command and executes it. The _$_w_a_i_t___k_e_y (section - 6.4.335 , page 164) can be used to control whether Mutt-ng will wait for a key + 7.4.350 , page 174) can be used to control whether Mutt-ng will wait for a key to be pressed when the command returns (presumably to let the user read the output of the command), based on the return status of the named command. ttooggggllee--qquuootteedd (default: T) - The _p_a_g_e_r uses the _$_q_u_o_t_e___r_e_g_e_x_p (section 6.4.225 , page 137) variable to + The _p_a_g_e_r uses the _$_q_u_o_t_e___r_e_g_e_x_p (section 7.4.241 , page 147) variable to detect quoted text when displaying the body of the message. This function tog- gles the display of the quoted material in the message. It is particularly useful when are interested in just the response and there is a large amount of @@ -755,7 +755,7 @@ sages from. You can now tag messages in that folder and they will be attached to the message you are sending. Note that certain operations like composing a new mail, replying, forwarding, etc. are not permitted when you are in that - folder. The %r in _$_s_t_a_t_u_s___f_o_r_m_a_t (section 6.4.308 , page 157) will change to a + folder. The %r in _$_s_t_a_t_u_s___f_o_r_m_a_t (section 7.4.324 , page 167) will change to a 'A' to indicate that you are in attach-message mode. The Mutt Next Generation E-Mail Client 16 @@ -863,7 +863,7 @@ field, Mutt-ng will not generate a _R_e_f_e_r_e_n_c_e_s_: field, which allows you to cre- ate a new message thread. - Also see _e_d_i_t___h_e_a_d_e_r_s (section 6.4.54 , page 95). + Also see _e_d_i_t___h_e_a_d_e_r_s (section 7.4.59 , page 103). _2_._6_._4 _U_s_i_n_g _M_u_t_t_-_n_g _w_i_t_h _P_G_P @@ -872,7 +872,7 @@ Pgp: [ E | S | S_<_i_d_> ] ``E'' encrypts, ``S'' signs and ``S'' signs with the given key, setting - _$_p_g_p___s_i_g_n___a_s (section 6.4.192 , page 130) permanently. + _$_p_g_p___s_i_g_n___a_s (section 7.4.208 , page 140) permanently. If you have told mutt to PGP encrypt a message, it will guide you through a key selection process when you try to send the message. Mutt-ng will not ask you @@ -890,7 +890,7 @@ encrypted using the selected public keys, and sent out. Most fields of the entries in the key selection menu (see also _$_p_g_p___e_n_t_r_y___f_o_r_- - _m_a_t (section 6.4.179 , page 127)) have obvious meanings. But some explana- + _m_a_t (section 7.4.195 , page 137)) have obvious meanings. But some explana- tions on the capabilities, flags, and validity fields are in order. The flags sequence (%f) will expand to one of the following flags: @@ -947,8 +947,8 @@ leave the menu, or accept them pressing (by default) the Return key. Note that different remailers do have different capabilities, indicated in the - %c entry of the remailer menu lines (see _$_m_i_x___e_n_t_r_y___f_o_r_m_a_t (section 6.4.139 , - page 116)). Most important is the ``middleman'' capability, indicated by a + %c entry of the remailer menu lines (see _$_m_i_x___e_n_t_r_y___f_o_r_m_a_t (section 7.4.146 , + page 125)). Most important is the ``middleman'' capability, indicated by a capital ``M'': This means that the remailer in question cannot be used as the final element of a chain, but will only forward messages to other mixmaster remailers. For details on the other capabilities, please have a look at the @@ -1001,7 +1001,7 @@ At times it is desirable to delay sending a message that you have already begun to compose. When the _p_o_s_t_p_o_n_e_-_m_e_s_s_a_g_e function is used in the _c_o_m_p_o_s_e menu, the body of your message and attachments are stored in the mailbox specified by - the _$_p_o_s_t_p_o_n_e_d (section 6.4.214 , page 135) variable. This means that you can + the _$_p_o_s_t_p_o_n_e_d (section 7.4.230 , page 145) variable. This means that you can recall the message even if you exit Mutt-ng and then restart it at a later time. @@ -1019,7 +1019,7 @@ be in the same folder with the message you replied to for the status of the message to be updated. - See also the _$_p_o_s_t_p_o_n_e (section 6.4.213 , page 134) quad-option. + See also the _$_p_o_s_t_p_o_n_e (section 7.4.229 , page 145) quad-option. _3_. _C_o_n_f_i_g_u_r_a_t_i_o_n @@ -1029,7 +1029,7 @@ out of the box, it is often desirable to tailor Mutt-ng to suit your own tastes. When Mutt-ng is first invoked, it will attempt to read the ``system'' configuration file (defaults set by your local system administrator), unless - the ``-n'' _c_o_m_m_a_n_d _l_i_n_e (section 6.1 , page 77) option is specified. This + the ``-n'' _c_o_m_m_a_n_d _l_i_n_e (section 7.1 , page 83) option is specified. This file is typically /usr/local/share/muttng/Muttngrc or /etc/Muttngrc, Mutt-ng users will find this file in /usr/local/share/muttng/Muttrc or /etc/Muttngrc. Mutt will next look for a file named .muttrc in your home directory, Mutt-ng @@ -1037,12 +1037,12 @@ has a subdirectory named .mutt, mutt try to load a file named .muttng/muttngrc. .muttrc (or .muttngrc for Mutt-ng) is the file where you will usually place - your _c_o_m_m_a_n_d_s (section 6.3 , page 79) to configure Mutt-ng. + your _c_o_m_m_a_n_d_s (section 7.3 , page 86) to configure Mutt-ng. - _3_._2 _S_y_n_t_a_x _o_f _I_n_i_t_i_a_l_i_z_a_t_i_o_n _F_i_l_e_s + _3_._2 _B_a_s_i_c _S_y_n_t_a_x _o_f _I_n_i_t_i_a_l_i_z_a_t_i_o_n _F_i_l_e_s - An initialization file consists of a series of _c_o_m_m_a_n_d_s (section 6.3 , page - 79). Each line of the file may contain one or more commands. When multiple + An initialization file consists of a series of _c_o_m_m_a_n_d_s (section 7.3 , page + 86). Each line of the file may contain one or more commands. When multiple commands are used, they must be separated by a semicolon (;). set realname='Mutt-ng user' ; ignore x- @@ -1102,27 +1102,187 @@ which includes line3 and line4. line5 is a new line of its own and thus is interpreted again. - It is also possible to substitute the output of a Unix command in an initial- - ization file. This is accomplished by enclosing the command in backquotes - (``). For example, + The commands understood by mutt are explained in the next paragraphs. For a + complete list, see the _c_o_m_m_a_n_d _r_e_f_e_r_e_n_c_e (section 7.3 , page 86). The Mutt Next Generation E-Mail Client 23 + _3_._3 _E_x_p_a_n_s_i_o_n _w_i_t_h_i_n _v_a_r_i_a_b_l_e_s + + Besides just assign static content to variables, there's plenty of ways of + adding external and more or less dynamic content. + + _3_._3_._1 _C_o_m_m_a_n_d_s_' _O_u_t_p_u_t + + It is possible to substitute the output of a Unix command in an initialization + file. This is accomplished by enclosing the command in backquotes (``) as in, + for example: + my_hdr X-Operating-System: `uname -a` The output of the Unix command ``uname -a'' will be substituted before the line - is parsed. Note that since initialization files are line oriented, only the + is parsed. Note that since initialization files are line oriented, only the first line of output from the Unix command will be substituted. + _3_._3_._2 _E_n_v_i_r_o_n_m_e_n_t _V_a_r_i_a_b_l_e_s + UNIX environments can be accessed like the way it is done in shells like sh and - bash: Prepend the name of the environment by a ``$''. For example, + bash: Prepend the name of the environment by a ``$'' sign. For example, set record=+sent_on_$HOSTNAME - The commands understood by mutt are explained in the next paragraphs. For a - complete list, see the _c_o_m_m_a_n_d _r_e_f_e_r_e_n_c_e (section 6.3 , page 79). + sets the _$_r_e_c_o_r_d (section 7.4.246 , page 148) variable to the string _+_s_e_n_t___o_n__ + and appends the value of the evironment variable $HOSTNAME. + + NNoottee:: There will be no warning if an environment variable is not defined. The + result will of the expansion will then be empty. + + _3_._3_._3 _C_o_n_f_i_g_u_r_a_t_i_o_n _V_a_r_i_a_b_l_e_s + + As for environment variables, the values of all configuration variables as + string can be used in the same way, too. For example, + + set imap_home_namespace = $folder + + would set the value of _$_i_m_a_p___h_o_m_e___n_a_m_e_s_p_a_c_e (section 7.4.101 , page 113) to + the value to which _$_f_o_l_d_e_r (section 7.4.70 , page 105) is _c_u_r_r_e_n_t_l_y set to. + + NNoottee:: There're no logical links established in such cases so that the the value + for _$_i_m_a_p___h_o_m_e___n_a_m_e_s_p_a_c_e (section 7.4.101 , page 113) won't change even if + _$_f_o_l_d_e_r (section 7.4.70 , page 105) gets changed. + + NNoottee:: There will be no warning if a configuration variable is not defined or is + empty. The result will of the expansion will then be empty. + + The Mutt Next Generation E-Mail Client 24 + + _3_._3_._4 _S_e_l_f_-_D_e_f_i_n_e_d _V_a_r_i_a_b_l_e_s + + Mutt-ng flexibly allows users to define their own variables. To avoid conflicts + with the standard set and to prevent misleading error messages, there's a + reserved namespace for them: all user-defined variables must be prefixed with + user_ and can be used just like any ordinary configuration or environment vari- + able. + + For example, to view the manual, users can either define two macros like the + following + + macro generic "!less -r /path/to/manual" "Show manual" + macro pager "!less -r /path/to/manual" "Show manual" + + for generic, pager and index. The alternative is to define a custom variable + like so: + + set user_manualcmd = "!less -r /path/to_manual" + macro generic "$user_manualcmd" "Show manual" + macro pager "$user_manualcmd" "Show manual" + macro index "$user_manualcmd" "Show manual" + + to re-use the command sequence as in: + + macro index "$user_manualcmd | grep '\^[ ]\\+~. '" "Show Patterns" + + Using this feature, arbitrary sequences can be defined once and recalled and + reused where necessary. More advanced scenarios could include to save a vari- + able's value at the beginning of macro sequence and restore it at end. + + When the variable is first defined, the first value it gets assigned is also + the initial value to which it can be reset using the reset command. + + The complete removal is done via the unset keyword. + + After the following sequence: + + set user_foo = 42 + set user_foo = 666 + + the variable $user_foo has a current value of 666 and an initial of 42. The + query + + set ?user_foo + + The Mutt Next Generation E-Mail Client 25 + + will show 666. After doing the reset via + + reset user_foo + + a following query will give 42 as the result. After unsetting it via + + unset user_foo + + any query or operation (except the noted expansion within other statements) + will lead to an error message. + + _3_._3_._5 _P_r_e_-_D_e_f_i_n_e_d _V_a_r_i_a_b_l_e_s + + In order to allow users to share one setup over a number of different machines + without having to change its contents, there's a number of pre-defined vari- + ables. These are prefixed with muttng_ and are read-only, i.e. they cannot be + set, unset or reset. The reference chapter lists all available variables. + + _P_l_e_a_s_e _c_o_n_s_u_l_t _t_h_e _l_o_c_a_l _c_o_p_y _o_f _y_o_u_r _m_a_n_u_a_l _f_o_r _t_h_e_i_r _v_a_l_u_e_s _a_s _t_h_e_y _m_a_y _d_i_f_- + _f_e_r _f_r_o_m _d_i_f_f_e_r_e_n_t _m_a_n_u_a_l _s_o_u_r_c_e_s_. Where the manual is installed in can be + queried (already using such a variable) by running: + + muttng -Q muttng_docdir + + To extend the example for viewing the manual via self-defined variables, it can + be made more readable and more portable by changing the real path in: + + set user_manualcmd = '!less -r /path/to_manual' + + to: + + set user_manualcmd = "!less -r $muttng_docdir/manual.txt" + + which works everywhere if a manual is installed. + + Please note that by the type of quoting, muttng determines when to expand these + values: when it finds double quotes, the value will be expanded during reading + the setup files but when it finds single quotes, it'll expand it at runtime as + needed. + + For example, the statement + + folder-hook . "set user_current_folder = $muttng_folder_name" + + The Mutt Next Generation E-Mail Client 26 + + will be already be translated to the following when reading the startup files: + + folder-hook . "set user_current_folder = some_folder" + + with some_folder being the name of the first folder muttng opens. On the con- + trary, + + folder-hook . 'set user_current_folder = $muttng_folder_name' + + will be executed at runtime because of the single quotes so that user_cur- + rent_folder will always have the value of the currently opened folder. + + A more practical example is: + + folder-hook . 'source ~/.mutt/score-$muttng_folder_name' + + which can be used to source files containing score commands depending on the + folder the user enters. + + _3_._3_._6 _T_y_p_e _C_o_n_v_e_r_s_i_o_n_s + + A note about variable's types during conversion: internally values are stored + in internal types but for any dump/query or set operation they're converted to + and from string. That means that there's no need to worry about types when ref- + erencing any variable. As an example, the following can be used without harm + (besides makeing muttng very likely behave strange): + + set read_inc = 100 + set folder = $read_inc + set read_inc = $folder + set user_magic_number = 42 + set folder = $user_magic_number - _3_._3 _D_e_f_i_n_i_n_g_/_U_s_i_n_g _a_l_i_a_s_e_s + _3_._4 _D_e_f_i_n_i_n_g_/_U_s_i_n_g _a_l_i_a_s_e_s Usage: alias _k_e_y _a_d_d_r_e_s_s [ , _a_d_d_r_e_s_s, ... ] @@ -1135,6 +1295,8 @@ To remove an alias or aliases (``*'' means all aliases): + The Mutt Next Generation E-Mail Client 27 + unalias [ * | _k_e_y _._._. ] alias muttdude me@cs.hmc.edu (Michael Elkins) @@ -1142,20 +1304,18 @@ Unlike other mailers, Mutt-ng doesn't require aliases to be defined in a spe- cial file. The alias command can appear anywhere in a configuration file, as - long as this file is _s_o_u_r_c_e_d (section 3.28 , page 42). Consequently, you can + long as this file is _s_o_u_r_c_e_d (section 3.29 , page 46). Consequently, you can have multiple alias files, or you can have all aliases defined in your muttrc. On the other hand, the _c_r_e_a_t_e_-_a_l_i_a_s (section 2.5.4 , page 11) function can use - only one file, the one pointed to by the _$_a_l_i_a_s___f_i_l_e (section 6.4.3 , page 83) + only one file, the one pointed to by the _$_a_l_i_a_s___f_i_l_e (section 7.4.5 , page 90) variable (which is ~/.muttrc by default). This file is not special either, in the sense that Mutt-ng will happily append aliases to any file, but in order for the new aliases to take effect you need to explicitly _s_o_u_r_c_e (section - 3.28 , page 42) this file too. + 3.29 , page 46) this file too. For example: - The Mutt Next Generation E-Mail Client 24 - source /usr/local/share/Mutt-ng.aliases source ~/.mail_aliases set alias_file=~/.mail_aliases @@ -1163,7 +1323,7 @@ To use aliases, you merely use the alias at any place in mutt where mutt prompts for addresses, such as the _T_o_: or _C_c_: prompt. You can also enter aliases in your editor at the appropriate headers if you have the _$_e_d_i_t___h_e_a_d_e_r_s - (section 6.4.54 , page 95) variable set. + (section 7.4.59 , page 103) variable set. In addition, at the various address prompts, you can use the tab character to expand a partial alias to the full alias. If there are multiple matches, mutt @@ -1175,7 +1335,7 @@ _e_n_t_r_y key (default: RET), and use the _e_x_i_t key (default: q) to return to the address prompt. - _3_._4 _C_h_a_n_g_i_n_g _t_h_e _d_e_f_a_u_l_t _k_e_y _b_i_n_d_i_n_g_s + _3_._5 _C_h_a_n_g_i_n_g _t_h_e _d_e_f_a_u_l_t _k_e_y _b_i_n_d_i_n_g_s Usage: bind _m_a_p _k_e_y _f_u_n_c_t_i_o_n @@ -1186,6 +1346,8 @@ fied by separating them with commas (no additional whitespace is allowed). The currently defined maps are: + The Mutt Next Generation E-Mail Client 28 + generic This is not a real menu, but is used as a fallback for all of the other menus except for the pager and editor modes. If a key is not @@ -1204,11 +1366,8 @@ messages. browser - The browser is used for both browsing the local directory - - The Mutt Next Generation E-Mail Client 25 - - structure, and for listing all of your incoming mailboxes. + The browser is used for both browsing the local directory struc- + ture, and for listing all of your incoming mailboxes. editor The editor is the line-based editor the user enters text data. @@ -1240,7 +1399,7 @@ In addition, _k_e_y may consist of: - The Mutt Next Generation E-Mail Client 26 + The Mutt Next Generation E-Mail Client 29 \t tab tab @@ -1269,10 +1428,10 @@ _k_e_y does not need to be enclosed in quotes unless it contains a space (`` ''). _f_u_n_c_t_i_o_n specifies which action to take when _k_e_y is pressed. For a complete - list of functions, see the _r_e_f_e_r_e_n_c_e (section 6.5 , page 166). The special + list of functions, see the _r_e_f_e_r_e_n_c_e (section 7.5 , page 177). The special function noop unbinds the specified key sequence. - _3_._5 _D_e_f_i_n_i_n_g _a_l_i_a_s_e_s _f_o_r _c_h_a_r_a_c_t_e_r _s_e_t_s + _3_._6 _D_e_f_i_n_i_n_g _a_l_i_a_s_e_s _f_o_r _c_h_a_r_a_c_t_e_r _s_e_t_s Usage: charset-hook _a_l_i_a_s _c_h_a_r_s_e_t @@ -1286,21 +1445,21 @@ This is helpful when your systems character conversion library insists on using strange, system-specific names for character sets. - _3_._6 _S_e_t_t_i_n_g _v_a_r_i_a_b_l_e_s _b_a_s_e_d _u_p_o_n _m_a_i_l_b_o_x + _3_._7 _S_e_t_t_i_n_g _v_a_r_i_a_b_l_e_s _b_a_s_e_d _u_p_o_n _m_a_i_l_b_o_x Usage: folder-hook [!]_r_e_g_e_x_p _c_o_m_m_a_n_d It is often desirable to change settings based on which mailbox you are - The Mutt Next Generation E-Mail Client 27 + The Mutt Next Generation E-Mail Client 30 reading. The folder-hook command provides a method by which you can execute any configuration command. _r_e_g_e_x_p is a regular expression specifying in which mailboxes to execute _c_o_m_m_a_n_d before loading. If a mailbox matches multiple folder-hook's, they are executed in the order given in the muttrc. - NNoottee:: if you use the ``!'' shortcut for _$_s_p_o_o_l_f_i_l_e (section 6.4.297 , page - 154) at the beginning of the pattern, you must place it inside of double or + NNoottee:: if you use the ``!'' shortcut for _$_s_p_o_o_l_f_i_l_e (section 7.4.313 , page + 165) at the beginning of the pattern, you must place it inside of double or single quotes in order to distinguish it from the logical _n_o_t operator for the expression. @@ -1315,7 +1474,7 @@ folder-hook . set sort=date-sent - _3_._7 _K_e_y_b_o_a_r_d _m_a_c_r_o_s + _3_._8 _K_e_y_b_o_a_r_d _m_a_c_r_o_s Usage: macro _m_e_n_u _k_e_y _s_e_q_u_e_n_c_e [ _d_e_s_c_r_i_p_t_i_o_n ] @@ -1324,26 +1483,26 @@ typed _s_e_q_u_e_n_c_e. So if you have a common sequence of commands you type, you can create a macro to execute those commands with a single key. - _m_e_n_u is the _m_a_p (section 3.4 , page 24) which the macro will be bound. Multi- + _m_e_n_u is the _m_a_p (section 3.5 , page 28) which the macro will be bound. Multi- ple maps may be specified by separating multiple menu arguments by commas. Whitespace may not be used in between the menu arguments and the commas sepa- rating them. _k_e_y and _s_e_q_u_e_n_c_e are expanded by the same rules as the _k_e_y _b_i_n_d_i_n_g_s (section - 3.4 , page 24). There are some additions however. The first is that control + 3.5 , page 27). There are some additions however. The first is that control characters in _s_e_q_u_e_n_c_e can also be specified as _^_x. In order to get a caret (`^'') you need to use _^_^. Secondly, to specify a certain key such as _u_p or to invoke a function directly, you can use the format _<_k_e_y _n_a_m_e_> and _<_f_u_n_c_t_i_o_n _n_a_m_e_>. For a listing of key names see the section on _k_e_y _b_i_n_d_i_n_g_s (section - 3.4 , page 24). Functions are listed in the _f_u_n_c_t_i_o_n _r_e_f_e_r_e_n_c_e (section - 6.5 , page 166). + 3.5 , page 27). Functions are listed in the _f_u_n_c_t_i_o_n _r_e_f_e_r_e_n_c_e (section + 7.5 , page 177). The advantage with using function names directly is that the macros will work regardless of the current key bindings, so they are not dependent on the user having particular key definitions. This makes them more robust and portable, and also facilitates defining of macros in files used by more than one user - The Mutt Next Generation E-Mail Client 28 + The Mutt Next Generation E-Mail Client 31 (eg. the system Muttngrc). @@ -1353,7 +1512,7 @@ NNoottee:: Macro definitions (if any) listed in the help screen(s), are silently truncated at the screen width, and are not wrapped. - _3_._8 _U_s_i_n_g _c_o_l_o_r _a_n_d _m_o_n_o _v_i_d_e_o _a_t_t_r_i_b_u_t_e_s + _3_._9 _U_s_i_n_g _c_o_l_o_r _a_n_d _m_o_n_o _v_i_d_e_o _a_t_t_r_i_b_u_t_e_s Usage: color _o_b_j_e_c_t _f_o_r_e_g_r_o_u_n_d _b_a_c_k_g_r_o_u_n_d [ _r_e_g_e_x_p ] @@ -1390,14 +1549,14 @@ +o normal - +o quoted (text matching _$_q_u_o_t_e___r_e_g_e_x_p (section 6.4.225 , page 137) in the + +o quoted (text matching _$_q_u_o_t_e___r_e_g_e_x_p (section 7.4.241 , page 147) in the body of a message) +o quoted1, quoted2, ..., quotedNN (higher levels of quoting) +o search (highlighting of words in the pager) - The Mutt Next Generation E-Mail Client 29 + The Mutt Next Generation E-Mail Client 32 +o signature @@ -1451,7 +1610,7 @@ command for it to be removed. The pattern ``*'' is a special token which means to clear the color index list of all entries. - The Mutt Next Generation E-Mail Client 30 + The Mutt Next Generation E-Mail Client 33 Mutt-ng also recognizes the keywords _c_o_l_o_r_0, _c_o_l_o_r_1, ..., _c_o_l_o_rNN--11 (NN being the number of colors supported by your terminal). This is useful when you remap @@ -1479,7 +1638,7 @@ +o standout - _3_._9 _I_g_n_o_r_i_n_g _(_w_e_e_d_i_n_g_) _u_n_w_a_n_t_e_d _m_e_s_s_a_g_e _h_e_a_d_e_r_s + _3_._1_0 _I_g_n_o_r_i_n_g _(_w_e_e_d_i_n_g_) _u_n_w_a_n_t_e_d _m_e_s_s_a_g_e _h_e_a_d_e_r_s Usage: [un]ignore _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] @@ -1506,9 +1665,9 @@ unignore organization organisation x-mailer: x-newsreader: x-mailing-list: unignore posted-to: - The Mutt Next Generation E-Mail Client 31 + The Mutt Next Generation E-Mail Client 34 - _3_._1_0 _A_l_t_e_r_n_a_t_i_v_e _a_d_d_r_e_s_s_e_s + _3_._1_1 _A_l_t_e_r_n_a_t_i_v_e _a_d_d_r_e_s_s_e_s Usage: [un]alternates _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] @@ -1517,7 +1676,7 @@ instance, when replying to a message that you sent to a different party, mutt will automatically suggest to send the response to the original message's recipients -- responding to yourself won't make much sense in many cases. (See - _$_r_e_p_l_y___t_o (section 6.4.233 , page 139).) + _$_r_e_p_l_y___t_o (section 7.4.249 , page 149).) Many users receive e-mail under a number of different addresses. To fully use mutt's features here, the program must be able to recognize what e-mail @@ -1536,7 +1695,9 @@ be removed. If the _r_e_g_e_x_p for unalternates is ``*'', _a_l_l _e_n_t_r_i_e_s on alternates will be removed. - _3_._1_1 _F_o_r_m_a_t _= _F_l_o_w_e_d + _3_._1_2 _F_o_r_m_a_t _= _F_l_o_w_e_d + + _3_._1_2_._1 _I_n_t_r_o_d_u_c_t_i_o_n Mutt-ng contains support for so-called format=flowed messages. In the begin- ning of email, each message had a fixed line width, and it was enough for dis- @@ -1551,14 +1712,16 @@ For introductory information on format=flowed messages, see . + _3_._1_2_._2 _R_e_c_e_i_v_i_n_g_: _D_i_s_p_l_a_y _S_e_t_u_p + When you receive emails that are marked as format=flowed messages, and is for- matted correctly, mutt-ng will try to reformat the message to optimally fit on your terminal. If you want a fixed margin on the right side of your terminal, you can set the following: - set wrapmargin = 10 + The Mutt Next Generation E-Mail Client 35 - The Mutt Next Generation E-Mail Client 32 + set wrapmargin = 10 The code above makes the line break 10 columns before the right side of the terminal. @@ -1566,50 +1729,82 @@ If your terminal is so wide that the lines are embarrassingly long, you can also set a maximum line length: - set max_line_length = 120 + set max_line_length = 120 The example above will give you lines not longer than 120 characters. When you view at format=flowed messages, you will often see the quoting hierar- chy like in the following example: - >Bill, can you please send last month's progress report to Mr. - >Morgan? We also urgently need the cost estimation for the new - >production server that we want to set up before our customer's - >project will go live. + >Bill, can you please send last month's progress report to Mr. + >Morgan? We also urgently need the cost estimation for the new + >production server that we want to set up before our customer's + >project will go live. This obviously doesn't look very nice, and it makes it very hard to differenti- ate between text and quoting character. The solution is to configure mutt-ng to "stuff" the quoting: - set stuff_quoted + set stuff_quoted This will lead to a nicer result that is easier to read: - > Bill, can you please send last month's progress report to Mr. - > Morgan? We also urgently need the cost estimation for the new - > production server that we want to set up before our customer's - > project will go live. + > Bill, can you please send last month's progress report to Mr. + > Morgan? We also urgently need the cost estimation for the new + > production server that we want to set up before our customer's + > project will go live. + + _3_._1_2_._3 _S_e_n_d_i_n_g If you want mutt-ng to send emails with format=flowed set, you need to explic- itly set it: - set text_flowed + set text_flowed + + The Mutt Next Generation E-Mail Client 36 Additionally, you have to use an editor which supports writing format=flowed- conforming emails. For vim, this is done by adding w to the formatoptions (see :h formatoptions and :h fo-table) when writing emails. - _3_._1_2 _M_a_i_l_i_n_g _l_i_s_t_s + Also note that _f_o_r_m_a_t_=_f_l_o_w_e_d knows about ``space-stuffing'', that is, when + sending messages, some kinds of lines have to be indented with a single space + on the sending side. On the receiving side, the first space (if any) is + removed. As a consequence and in addition to the above simple setting, please + keep this in mind when making manual formattings within the editor. Also note + that mutt-ng currently violates the standard (RfC 3676) as it does not space- + stuff lines starting with: - The Mutt Next Generation E-Mail Client 33 + +o > This is _n_o_t the quote character but a right angle used for other reasons + + +o From with a trailing space. + + +o just a space for formatting reasons + + Please make sure that you manually prepend a space to each of them. + + _3_._1_2_._4 _A_d_d_i_t_i_o_n_a_l _N_o_t_e_s + + " + + For completeness, the _$_d_e_l_e_t_e___s_p_a_c_e (section 7.4.51 , page 101) variable pro- + vides the mechanism to generate a DelSp=yes parameter on _o_u_t_g_o_i_n_g messages. + According to the standard, clients receiving a format=flowed messages should + delete the last space of a flowed line but still interpret the line as flowed. + Because flowed lines usually contain only one space at the end, this parameter + would make the receiving client concatenate the last word of the previous with + the first of the current line _w_i_t_h_o_u_t a space. This makes ordinary text unread- + able and is intended for languages rarely using spaces. So please use this set- + ting only if you're sure what you're doing. + + _3_._1_3 _M_a_i_l_i_n_g _l_i_s_t_s Usage: [un]lists _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] Usage: [un]subscribe _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] Mutt-ng has a few nice features for _h_a_n_d_l_i_n_g _m_a_i_l_i_n_g _l_i_s_t_s (section 4.10 , - page 57). In order to take advantage of them, you must specify which addresses + page 61). In order to take advantage of them, you must specify which addresses belong to mailing lists, and which mailing lists you are subscribed to. Once you have done this, the _l_i_s_t_-_r_e_p_l_y (section 2.5.4 , page 12) function will work for all known lists. Additionally, when you send a message to a sub- @@ -1618,9 +1813,11 @@ the Mail-Followup-To header is a non-standard extension which is not supported by all mail user agents. Adding it is not bullet-proof against receiving per- sonal CCs of list messages. Also note that the generation of the Mail-Fol- - lowup-To header is controlled by the _$_f_o_l_l_o_w_u_p___t_o (section 6.4.66 , page 98) + lowup-To header is controlled by the _$_f_o_l_l_o_w_u_p___t_o (section 7.4.72 , page 106) configuration variable. + The Mutt Next Generation E-Mail Client 37 + More precisely, Mutt-ng maintains lists of patterns for the addresses of known and subscribed mailing lists. Every subscribed mailing list is known. To mark a mailing list as known, use the ``lists'' command. To mark it as subscribed, @@ -1647,7 +1844,7 @@ To remove a mailing list from the list of subscribed mailing lists, but keep it on the list of known mailing lists, use ``unsubscribe''. - _3_._1_3 _U_s_i_n_g _M_u_l_t_i_p_l_e _s_p_o_o_l _m_a_i_l_b_o_x_e_s + _3_._1_4 _U_s_i_n_g _M_u_l_t_i_p_l_e _s_p_o_o_l _m_a_i_l_b_o_x_e_s Usage: mbox-hook [!]_p_a_t_t_e_r_n _m_a_i_l_b_o_x @@ -1656,12 +1853,10 @@ regular expression specifying the mailbox to treat as a ``spool'' mailbox and _m_a_i_l_b_o_x specifies where mail should be saved when read. - The Mutt Next Generation E-Mail Client 34 - Unlike some of the other _h_o_o_k commands, only the _f_i_r_s_t matching pattern is used (it is not possible to save read mail in more than a single mailbox). - _3_._1_4 _D_e_f_i_n_i_n_g _m_a_i_l_b_o_x_e_s _w_h_i_c_h _r_e_c_e_i_v_e _m_a_i_l + _3_._1_5 _D_e_f_i_n_i_n_g _m_a_i_l_b_o_x_e_s _w_h_i_c_h _r_e_c_e_i_v_e _m_a_i_l Usage: [un]mailboxes [!]_f_i_l_e_n_a_m_e [ _f_i_l_e_n_a_m_e ... ] @@ -1673,6 +1868,9 @@ Pressing TAB in the directory browser will bring up a menu showing the files specified by the mailboxes command, and indicate which contain new messages. + + The Mutt Next Generation E-Mail Client 38 + Mutt-ng will automatically enter this mode when invoked from the command line with the -y option. @@ -1687,11 +1885,11 @@ NNoottee:: the filenames in the mailboxes command are resolved when the command is executed, so if these names contain _s_h_o_r_t_c_u_t _c_h_a_r_a_c_t_e_r_s (section 4.9 , page - 56) (such as ``='' and ``!''), any variable definition that affect these char- - acters (like _$_f_o_l_d_e_r (section 6.4.64 , page 97) and _$_s_p_o_o_l_f_i_l_e (section - 6.4.297 , page 154)) should be executed before the mailboxes command. + 61) (such as ``='' and ``!''), any variable definition that affect these char- + acters (like _$_f_o_l_d_e_r (section 7.4.70 , page 105) and _$_s_p_o_o_l_f_i_l_e (section + 7.4.313 , page 165)) should be executed before the mailboxes command. - _3_._1_5 _U_s_e_r _d_e_f_i_n_e_d _h_e_a_d_e_r_s + _3_._1_6 _U_s_e_r _d_e_f_i_n_e_d _h_e_a_d_e_r_s Usage: @@ -1707,8 +1905,6 @@ my_hdr Organization: A Really Big Company, Anytown, USA - The Mutt Next Generation E-Mail Client 35 - in your .muttrc. NNoottee:: space characters are _n_o_t allowed between the keyword and the colon @@ -1716,7 +1912,7 @@ there, so Mutt-ng enforces the rule. If you would like to add a header field to a single message, you should either - set the _e_d_i_t___h_e_a_d_e_r_s (section 6.4.54 , page 95) variable, or use the _e_d_i_t_- + set the _e_d_i_t___h_e_a_d_e_r_s (section 7.4.59 , page 103) variable, or use the _e_d_i_t_- _h_e_a_d_e_r_s function (default: ``E'') in the send-menu so that you can edit the header of your message along with the body. @@ -1725,9 +1921,11 @@ remove. For example, to remove all ``To'' and ``Cc'' header fields, you could use: + The Mutt Next Generation E-Mail Client 39 + unmy_hdr to cc - _3_._1_6 _D_e_f_i_n_i_n_g _t_h_e _o_r_d_e_r _o_f _h_e_a_d_e_r_s _w_h_e_n _v_i_e_w_i_n_g _m_e_s_s_a_g_e_s + _3_._1_7 _D_e_f_i_n_i_n_g _t_h_e _o_r_d_e_r _o_f _h_e_a_d_e_r_s _w_h_e_n _v_i_e_w_i_n_g _m_e_s_s_a_g_e_s Usage: hdr_order _h_e_a_d_e_r_1 _h_e_a_d_e_r_2 _h_e_a_d_e_r_3 @@ -1739,7 +1937,7 @@ hdr_order From Date: From: To: Cc: Subject: - _3_._1_7 _S_p_e_c_i_f_y _d_e_f_a_u_l_t _s_a_v_e _f_i_l_e_n_a_m_e + _3_._1_8 _S_p_e_c_i_f_y _d_e_f_a_u_l_t _s_a_v_e _f_i_l_e_n_a_m_e Usage: save-hook [!]_p_a_t_t_e_r_n _f_i_l_e_n_a_m_e @@ -1748,46 +1946,45 @@ an address matching _r_e_g_e_x_p or if you are the author and the message is addressed _t_o_: something matching _r_e_g_e_x_p. - See _M_e_s_s_a_g_e _M_a_t_c_h_i_n_g _i_n _H_o_o_k_s (section 4.5.1 , page 53) for information on the + See _M_e_s_s_a_g_e _M_a_t_c_h_i_n_g _i_n _H_o_o_k_s (section 4.5.1 , page 58) for information on the exact format of _p_a_t_t_e_r_n. Examples: save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins - - The Mutt Next Generation E-Mail Client 36 - save-hook aol\\.com$ +spam - Also see the _f_c_c_-_s_a_v_e_-_h_o_o_k (section 3.19 , page 36) command. + Also see the _f_c_c_-_s_a_v_e_-_h_o_o_k (section 3.20 , page 40) command. - _3_._1_8 _S_p_e_c_i_f_y _d_e_f_a_u_l_t _F_c_c_: _m_a_i_l_b_o_x _w_h_e_n _c_o_m_p_o_s_i_n_g + _3_._1_9 _S_p_e_c_i_f_y _d_e_f_a_u_l_t _F_c_c_: _m_a_i_l_b_o_x _w_h_e_n _c_o_m_p_o_s_i_n_g Usage: fcc-hook [!]_p_a_t_t_e_r_n _m_a_i_l_b_o_x This command is used to save outgoing mail in a mailbox other than _$_r_e_c_o_r_d - (section 6.4.230 , page 138). Mutt-ng searches the initial list of message + (section 7.4.246 , page 148). Mutt-ng searches the initial list of message recipients for the first matching _r_e_g_e_x_p and uses _m_a_i_l_b_o_x as the default Fcc: mailbox. If no match is found the message will be saved to _$_r_e_c_o_r_d (section - 6.4.230 , page 138) mailbox. + 7.4.246 , page 148) mailbox. + + The Mutt Next Generation E-Mail Client 40 - See _M_e_s_s_a_g_e _M_a_t_c_h_i_n_g _i_n _H_o_o_k_s (section 4.5.1 , page 53) for information on the + See _M_e_s_s_a_g_e _M_a_t_c_h_i_n_g _i_n _H_o_o_k_s (section 4.5.1 , page 58) for information on the exact format of _p_a_t_t_e_r_n. Example: fcc-hook [@.]aol\\.com$ +spammers The above will save a copy of all messages going to the aol.com domain to the - `+spammers' mailbox by default. Also see the _f_c_c_-_s_a_v_e_-_h_o_o_k (section 3.19 , - page 36) command. + `+spammers' mailbox by default. Also see the _f_c_c_-_s_a_v_e_-_h_o_o_k (section 3.20 , + page 40) command. - _3_._1_9 _S_p_e_c_i_f_y _d_e_f_a_u_l_t _s_a_v_e _f_i_l_e_n_a_m_e _a_n_d _d_e_f_a_u_l_t _F_c_c_: _m_a_i_l_b_o_x _a_t _o_n_c_e + _3_._2_0 _S_p_e_c_i_f_y _d_e_f_a_u_l_t _s_a_v_e _f_i_l_e_n_a_m_e _a_n_d _d_e_f_a_u_l_t _F_c_c_: _m_a_i_l_b_o_x _a_t _o_n_c_e Usage: fcc-save-hook [!]_p_a_t_t_e_r_n _m_a_i_l_b_o_x This command is a shortcut, equivalent to doing both a _f_c_c_-_h_o_o_k (section - 3.18 , page 35) and a _s_a_v_e_-_h_o_o_k (section 3.17 , page 35) with its arguments. + 3.19 , page 39) and a _s_a_v_e_-_h_o_o_k (section 3.18 , page 39) with its arguments. - _3_._2_0 _C_h_a_n_g_e _s_e_t_t_i_n_g_s _b_a_s_e_d _u_p_o_n _m_e_s_s_a_g_e _r_e_c_i_p_i_e_n_t_s + _3_._2_1 _C_h_a_n_g_e _s_e_t_t_i_n_g_s _b_a_s_e_d _u_p_o_n _m_e_s_s_a_g_e _r_e_c_i_p_i_e_n_t_s Usage: reply-hook [!]_p_a_t_t_e_r_n _c_o_m_m_a_n_d @@ -1805,27 +2002,28 @@ and _r_e_p_l_i_e_s. NNoottee:: reply-hooks are matched bbeeffoorree the send-hook, rreeggaarrddlleessss of the order specified in the users's configuration file. - The Mutt Next Generation E-Mail Client 37 - send2-hook is matched every time a message is changed, either by editing it, or by using the compose menu to change its recipients or subject. send2-hook is executed after send-hook, and can, e.g., be used to set parameters such as the - _$_s_e_n_d_m_a_i_l (section 6.4.247 , page 142) variable depending on the message's + _$_s_e_n_d_m_a_i_l (section 7.4.263 , page 152) variable depending on the message's sender address. For each type of send-hook or reply-hook, when multiple matches occur, commands are executed in the order they are specified in the muttrc (for that type of hook). - See _M_e_s_s_a_g_e _M_a_t_c_h_i_n_g _i_n _H_o_o_k_s (section 4.5.1 , page 53) for information on the + See _M_e_s_s_a_g_e _M_a_t_c_h_i_n_g _i_n _H_o_o_k_s (section 4.5.1 , page 58) for information on the exact format of _p_a_t_t_e_r_n. Example: send-hook mutt 'set mime_forward signature=''' - Another typical use for this command is to change the values of the _$_a_t_t_r_i_b_u_- - _t_i_o_n (section 6.4.15 , page 86), _$_s_i_g_n_a_t_u_r_e (section 6.4.259 , page 145) and - _$_l_o_c_a_l_e (section 6.4.114 , page 111) variables in order to change the language - of the attributions and signatures based upon the recipients. + Another typical use for this command is to change the values of the + + The Mutt Next Generation E-Mail Client 41 + + _$_a_t_t_r_i_b_u_t_i_o_n (section 7.4.18 , page 94), _$_s_i_g_n_a_t_u_r_e (section 7.4.275 , page + 155) and _$_l_o_c_a_l_e (section 7.4.120 , page 120) variables in order to change the + language of the attributions and signatures based upon the recipients. NNoottee:: the send-hook's are only executed ONCE after getting the initial list of recipients. Adding a recipient after replying or editing the message will NOT @@ -1833,7 +2031,7 @@ ify recipient headers, or the message's subject, don't have any effect on the current message when executed from a send-hook. - _3_._2_1 _C_h_a_n_g_e _s_e_t_t_i_n_g_s _b_e_f_o_r_e _f_o_r_m_a_t_t_i_n_g _a _m_e_s_s_a_g_e + _3_._2_2 _C_h_a_n_g_e _s_e_t_t_i_n_g_s _b_e_f_o_r_e _f_o_r_m_a_t_t_i_n_g _a _m_e_s_s_a_g_e Usage: message-hook [!]_p_a_t_t_e_r_n _c_o_m_m_a_n_d @@ -1843,7 +2041,7 @@ tiple matches occur, commands are executed in the order they are specified in the muttrc. - See _M_e_s_s_a_g_e _M_a_t_c_h_i_n_g _i_n _H_o_o_k_s (section 4.5.1 , page 53) for information on the + See _M_e_s_s_a_g_e _M_a_t_c_h_i_n_g _i_n _H_o_o_k_s (section 4.5.1 , page 58) for information on the exact format of _p_a_t_t_e_r_n. Example: @@ -1851,41 +2049,42 @@ message-hook ~A 'set pager=builtin' message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""' - _3_._2_2 _C_h_o_o_s_i_n_g _t_h_e _c_r_y_p_t_o_g_r_a_p_h_i_c _k_e_y _o_f _t_h_e _r_e_c_i_p_i_e_n_t + _3_._2_3 _C_h_o_o_s_i_n_g _t_h_e _c_r_y_p_t_o_g_r_a_p_h_i_c _k_e_y _o_f _t_h_e _r_e_c_i_p_i_e_n_t Usage: crypt-hook _p_a_t_t_e_r_n _k_e_y_i_d - When encrypting messages with PGP or OpenSSL, you may want to associate a - - The Mutt Next Generation E-Mail Client 38 - - certain key with a given e-mail address automatically, either because the - recipient's public key can't be deduced from the destination address, or - because, for some reasons, you need to override the key Mutt-ng would normally - use. The crypt-hook command provides a method by which you can specify the ID - of the public key to be used when encrypting messages to a certain recipient. + When encrypting messages with PGP or OpenSSL, you may want to associate a cer- + tain key with a given e-mail address automatically, either because the recipi- + ent's public key can't be deduced from the destination address, or because, for + some reasons, you need to override the key Mutt-ng would normally use. The + crypt-hook command provides a method by which you can specify the ID of the + public key to be used when encrypting messages to a certain recipient. The meaning of "key id" is to be taken broadly in this context: You can either put a numerical key ID here, an e-mail address, or even just a real name. - _3_._2_3 _A_d_d_i_n_g _k_e_y _s_e_q_u_e_n_c_e_s _t_o _t_h_e _k_e_y_b_o_a_r_d _b_u_f_f_e_r + _3_._2_4 _A_d_d_i_n_g _k_e_y _s_e_q_u_e_n_c_e_s _t_o _t_h_e _k_e_y_b_o_a_r_d _b_u_f_f_e_r Usage: push _s_t_r_i_n_g - This command adds the named string to the keyboard buffer. The string may con- - tain control characters, key names and function names like the sequence string - in the _m_a_c_r_o (section 3.7 , page 27) command. You may use it to automatically - run a sequence of commands at startup, or when entering certain folders. + This command adds the named string to the keyboard buffer. The string may - _3_._2_4 _E_x_e_c_u_t_i_n_g _f_u_n_c_t_i_o_n_s + The Mutt Next Generation E-Mail Client 42 + + contain control characters, key names and function names like the sequence + string in the _m_a_c_r_o (section 3.8 , page 30) command. You may use it to auto- + matically run a sequence of commands at startup, or when entering certain fold- + ers. + + _3_._2_5 _E_x_e_c_u_t_i_n_g _f_u_n_c_t_i_o_n_s Usage: exec _f_u_n_c_t_i_o_n [ _f_u_n_c_t_i_o_n ... ] This command can be used to execute any function. Functions are listed in the - _f_u_n_c_t_i_o_n _r_e_f_e_r_e_n_c_e (section 6.5 , page 166). ``exec function'' is equivalent + _f_u_n_c_t_i_o_n _r_e_f_e_r_e_n_c_e (section 7.5 , page 177). ``exec function'' is equivalent to ``push ''. - _3_._2_5 _M_e_s_s_a_g_e _S_c_o_r_i_n_g + _3_._2_6 _M_e_s_s_a_g_e _S_c_o_r_i_n_g Usage: score _p_a_t_t_e_r_n _v_a_l_u_e @@ -1905,8 +2104,6 @@ score "~f nion@muttng\.org" 50 score "~f @sco\.com" -100 - The Mutt Next Generation E-Mail Client 39 - If the pattern matches, it is also possible to set the score value of the cur- rent message to a certain value and then stop evaluation: @@ -1921,6 +2118,8 @@ +o flag threshold: when a message has a score value equal or higher than the flag threshold, it will be flagged. + The Mutt Next Generation E-Mail Client 43 + +o read threshold: when a message has a score value equal or lower than the read threshold, it will be marked as read. @@ -1928,24 +2127,24 @@ delete threshold, it will be marked as deleted. These three thresholds can be set via the variables _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___f_l_a_g (sec- - tion 6.4.244 , page 142), _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___r_e_a_d (section 6.4.245 , page 142), - _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___d_e_l_e_t_e (section 6.4.243 , page 141) and. By default, - _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___r_e_a_d (section 6.4.245 , page 142) and _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___d_e_l_e_t_e - (section 6.4.243 , page 141) are set to -1, which means that in the default + tion 7.4.260 , page 152), _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___r_e_a_d (section 7.4.261 , page 152), + _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___d_e_l_e_t_e (section 7.4.259 , page 152) and. By default, + _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___r_e_a_d (section 7.4.261 , page 152) and _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___d_e_l_e_t_e + (section 7.4.259 , page 152) are set to -1, which means that in the default threshold configuration no message will ever get marked as read or deleted. Scoring gets especially interesting when combined with the color command and the ~n pattern: - color black yellow "~n 10-" - color red yellow "~n 100-" + color index black yellow "~n 10-" + color index red yellow "~n 100-" The rules above mark all messages with a score between 10 and 99 with black and yellow, and messages with a score greater or equal 100 with red and yellow. This might be unusual to you if you're used to e.g. slrn's scoring mechanism, but it is more flexible, as it visually marks different scores. - _3_._2_6 _S_p_a_m _d_e_t_e_c_t_i_o_n + _3_._2_7 _S_p_a_m _d_e_t_e_c_t_i_o_n Usage: spam _p_a_t_t_e_r_n _f_o_r_m_a_t @@ -1955,10 +2154,7 @@ your spam patterns with the spam and nospam commands, you can _l_i_m_i_t, _s_e_a_r_c_h, and _s_o_r_t your mail based on its spam attributes, as determined by the external filter. You also can display the spam attributes in your index display using - - The Mutt Next Generation E-Mail Client 40 - - the %H selector in the _$_i_n_d_e_x___f_o_r_m_a_t (section 6.4.110 , page 108) variable. + the %H selector in the _$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.116 , page 116) variable. (Tip: try %?H?[%H] ? to display spam tags only when they are defined for a given message.) @@ -1974,6 +2170,9 @@ with the second, etc. If you're using multiple spam filters, a message can have more than one spam- + + The Mutt Next Generation E-Mail Client 44 + related header. You can define spam patterns for each filter you use. If a mes- sage matches two or more of these patterns, and the $spam_separator variable is set to a string, then the message's spam tag will consist of all the _f_o_r_m_a_t @@ -2011,9 +2210,6 @@ mutt will sort numerically first, and lexically only when two numbers are equal in value. (This is like UNIX's sort -n.) A message with no spam attributes at all -- that is, one that didn't match _a_n_y of your spam patterns -- is sorted at - - The Mutt Next Generation E-Mail Client 41 - lowest priority. Numbers are sorted next, beginning with 0 and ranging upward. Finally, non-numeric strings are sorted, with ``a'' taking lower priority than ``z''. Clearly, in general, sorting by spam tags is most effective when you can @@ -2030,6 +2226,9 @@ instead of adding an exception. Likewise, if the _p_a_t_t_e_r_n for a spam command matches an entry on the nospam list, that nospam entry will be removed. If the _p_a_t_t_e_r_n for nospam is ``*'', _a_l_l _e_n_t_r_i_e_s _o_n _b_o_t_h _l_i_s_t_s will be removed. This + + The Mutt Next Generation E-Mail Client 45 + might be the default action if you use spam and nospam in conjunction with a folder-hook. @@ -2039,7 +2238,7 @@ spam "^From: .*MAILER-DAEMON" "999" - _3_._2_7 _S_e_t_t_i_n_g _v_a_r_i_a_b_l_e_s + _3_._2_8 _S_e_t_t_i_n_g _v_a_r_i_a_b_l_e_s Usage: set [no|inv]_v_a_r_i_a_b_l_e[=_v_a_l_u_e] [ _v_a_r_i_a_b_l_e ... ] @@ -2049,8 +2248,8 @@ Usage: reset _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ] - This command is used to set (and unset) _c_o_n_f_i_g_u_r_a_t_i_o_n _v_a_r_i_a_b_l_e_s (section 6.4 , - page 81). There are four basic types of variables: boolean, number, string and + This command is used to set (and unset) _c_o_n_f_i_g_u_r_a_t_i_o_n _v_a_r_i_a_b_l_e_s (section 7.4 , + page 88). There are four basic types of variables: boolean, number, string and quadoption. _b_o_o_l_e_a_n variables can be _s_e_t (true) or _u_n_s_e_t (false). _n_u_m_b_e_r variables can be assigned a positive integer value. @@ -2065,8 +2264,6 @@ if you had answered ``no.'' A value of _a_s_k_-_y_e_s will cause a prompt with a default answer of ``yes'' and _a_s_k_-_n_o will provide a default answer of ``no.'' - The Mutt Next Generation E-Mail Client 42 - Prefixing a variable with ``no'' will unset it. Example: set noaskbcc. For _b_o_o_l_e_a_n variables, you may optionally prefix the variable name with inv to @@ -2082,6 +2279,8 @@ Using the enter-command function in the _i_n_d_e_x menu, you can query the value of a variable by prefixing the name of the variable with a question mark: + The Mutt Next Generation E-Mail Client 46 + set ?allow_8bit The question mark is actually only required for boolean and quadoption vari- @@ -2094,7 +2293,7 @@ With the reset command there exists the special variable ``all'', which allows you to reset all variables to their system defaults. - _3_._2_8 _R_e_a_d_i_n_g _i_n_i_t_i_a_l_i_z_a_t_i_o_n _c_o_m_m_a_n_d_s _f_r_o_m _a_n_o_t_h_e_r _f_i_l_e + _3_._2_9 _R_e_a_d_i_n_g _i_n_i_t_i_a_l_i_z_a_t_i_o_n _c_o_m_m_a_n_d_s _f_r_o_m _a_n_o_t_h_e_r _f_i_l_e Usage: source _f_i_l_e_n_a_m_e [ _f_i_l_e_n_a_m_e ... ] @@ -2108,21 +2307,18 @@ If the filename ends with a vertical bar (|), then _f_i_l_e_n_a_m_e is considered to be an executable program from which to read input (eg. source ~/bin/myscript|). - _3_._2_9 _R_e_m_o_v_i_n_g _h_o_o_k_s + _3_._3_0 _R_e_m_o_v_i_n_g _h_o_o_k_s Usage: unhook [ * | _h_o_o_k_-_t_y_p_e ] This command permits you to flush hooks you have previously defined. You can either remove all hooks by giving the ``*'' character as an argument, or you can remove all hooks of a specific type by saying something like unhook send- - - The Mutt Next Generation E-Mail Client 43 - hook. - _3_._3_0 _S_h_a_r_i_n_g _S_e_t_u_p_s + _3_._3_1 _S_h_a_r_i_n_g _S_e_t_u_p_s - _3_._3_0_._1 _C_h_a_r_a_c_t_e_r _S_e_t_s + _3_._3_1_._1 _C_h_a_r_a_c_t_e_r _S_e_t_s As users may run mutt-ng on different systems, the configuration must be main- tained because it's likely that people want to use the setup everywhere they @@ -2132,6 +2328,9 @@ specify in which character set their configuration files are encoded. Please note that while reading the configuration files, this is only respected after the corresponding declaration appears. It's advised to put the following at the + + The Mutt Next Generation E-Mail Client 47 + very beginning of a users muttngrc: set config_charset = "..." @@ -2144,7 +2343,7 @@ while, again, replacing the dots with the appropriate name. This tells vim as which character set to read and save the file. - _3_._3_0_._2 _M_o_d_u_l_a_r_i_z_a_t_i_o_n + _3_._3_1_._2 _M_o_d_u_l_a_r_i_z_a_t_i_o_n ``Modularization'' means to divide the setup into several files while sorting the options or commands by topic. Especially for longer setups (e.g. with many @@ -2153,7 +2352,7 @@ When using separation, setups may be, as a whole or in fractions, shared over different systems. - _3_._3_0_._3 _C_o_n_d_i_t_i_o_n_a_l _p_a_r_t_s + _3_._3_1_._3 _C_o_n_d_i_t_i_o_n_a_l _p_a_r_t_s When using a configuration on different systems, the user may not always have influence on how mutt-ng is installed and which features it includes. @@ -2161,8 +2360,6 @@ To solve this, mutt-ng contain a feature based on the ``ifdef'' patch written for mutt. Its basic syntax is: - The Mutt Next Generation E-Mail Client 44 - ifdef ifndef @@ -2178,6 +2375,9 @@ All available functions, variables and menus are documented elsewhere in this manual but ``features'' is specific to these two commands. To test for one, + + The Mutt Next Generation E-Mail Client 48 + prefix one of the following keywords with feature_: ncurses, slang, iconv, idn, dotlock, standalone, pop, nntp, imap, ssl, @@ -2196,21 +2396,18 @@ An example for testing for variable names can be used if users use different revisions of mutt-ng whereby the older one may not have a certain variable. To - test for the availability of _$_i_m_a_p___m_a_i_l___c_h_e_c_k (section 6.4.99 , page 105), + test for the availability of _$_i_m_a_p___m_a_i_l___c_h_e_c_k (section 7.4.105 , page 114), use: ifdef imap_mail_check 'set imap_mail_check = 300' Provided for completeness is the test for menu names. To set _$_p_a_g_e_r___i_n_d_e_x___l_i_n_e_s - (section 6.4.169 , page 124) only if the pager menu is available, use: + (section 7.4.185 , page 134) only if the pager menu is available, use: ifdef pager 'set pager_index_lines = 10' For completeness, too, the opposite of ifdef is provided: ifndef which only executes the command if the test fails. For example, the following two examples - - The Mutt Next Generation E-Mail Client 45 - are equivalent: ifdef feature_ncurses 'source ~/.mutt-ng/setup-ncurses' @@ -2221,18 +2418,20 @@ ifdef feature_slang 'source ~/.mutt-ng/setup-slang' ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - _3_._3_1 _O_b_s_o_l_e_t_e _V_a_r_i_a_b_l_e_s + The Mutt Next Generation E-Mail Client 49 + + _3_._3_2 _O_b_s_o_l_e_t_e _V_a_r_i_a_b_l_e_s In the process of ensuring and creating more consistency, many variables have been renamed and some of the old names were already removed. Please see _O_b_s_o_- - _l_e_t_e _V_a_r_i_a_b_l_e_s (section 6.4 , page 81) for a complete list. + _l_e_t_e _V_a_r_i_a_b_l_e_s (section 7.4 , page 88) for a complete list. _4_. _A_d_v_a_n_c_e_d _U_s_a_g_e _4_._1 _R_e_g_u_l_a_r _E_x_p_r_e_s_s_i_o_n_s All string patterns in Mutt-ng including those in more complex _p_a_t_t_e_r_n_s (sec- - tion 6.2 , page 78) must be specified using regular expressions (regexp) in + tion 7.2 , page 84) must be specified using regular expressions (regexp) in the ``POSIX extended'' syntax (which is more or less the syntax used by egrep and GNU awk). For your convenience, we have included below a brief description of this syntax. @@ -2252,9 +2451,6 @@ ace it with \ (backslash). The fundamental building blocks are the regular expressions that match a single - - The Mutt Next Generation E-Mail Client 46 - character. Most characters, including all letters and digits, are regular expressions that match themselves. Any metacharacter with special meaning may be quoted by preceding it with a backslash. @@ -2273,6 +2469,8 @@ place it anywhere but first. Finally, to include a literal hyphen ``-'' place it last. + The Mutt Next Generation E-Mail Client 50 + Certain named classes of characters are predefined. Character classes consist of ``[:'', a keyword denoting the class, and ``:]''. The following classes are defined by the POSIX standard: @@ -2309,8 +2507,6 @@ [:space:] Space characters (such as space, tab and formfeed, to name a few). - The Mutt Next Generation E-Mail Client 47 - [:upper:] Upper-case alphabetic characters. @@ -2329,6 +2525,9 @@ Collating Symbols A collating symbol is a multi-character collating element enclosed + + The Mutt Next Generation E-Mail Client 51 + in ``[.'' and ``.]''. For example, if ``ch'' is a collating ele- ment, then [[[[..cchh..]]]] is a regexp that matches this collating ele- ment, while [[cchh]] is a regexp that matches either ``c'' or ``h''. @@ -2365,8 +2564,6 @@ The preceding item is matched at least _n times, but no more than _m times. - The Mutt Next Generation E-Mail Client 48 - Two regular expressions may be concatenated; the resulting regular expression matches any string formed by concatenating two substrings that respectively match the concatenated subexpressions. @@ -2385,6 +2582,8 @@ Matches the empty string at either the beginning or the end of a word. + The Mutt Next Generation E-Mail Client 52 + \\B Matches the empty string within a word. @@ -2416,12 +2615,9 @@ to match messages, e.g. for operations like tagging and scoring. A pattern con- sists of one or more sub-pattern, which can be logically grouped, ORed, and negated. For a complete listing of these patterns, please refer to table _P_a_t_- - _t_e_r_n_s (section 6.2 , page 78) in the Reference chapter. + _t_e_r_n_s (section 7.2 , page 84) in the Reference chapter. It must be noted that in this table, EXPR, USER, ID and SUBJECT are regular - - The Mutt Next Generation E-Mail Client 49 - expressions. For ranges, the forms <[MAX], >>[MIN], [MIN]- and -[MAX] are also possible. @@ -2439,6 +2635,8 @@ To logical OR patterns, simply use the | operator. This one especially useful when using local groups: + The Mutt Next Generation E-Mail Client 53 + ~f ("nion@muttng\.org"|"ak@muttng\.org"|"pdmef@muttng\.org") (~b mutt-ng|~s Mutt-ng) !~x '@synflood\.at' @@ -2470,9 +2668,6 @@ ~d 28/12/2004*1d The first pattern matches all dates between January 1st, 2005 and January 1st - - The Mutt Next Generation E-Mail Client 50 - 2006. The second pattern matches all dates between October 18th, 2004 and October 4th 2004 (2 weeks before 18/10/2004), while the third pattern matches all dates 1 day around December 28th, 2004 (i.e. Dec 27th, 28th and 29th). @@ -2489,6 +2684,8 @@ _4_._3_._1 _I_n_t_r_o_d_u_c_t_i_o_n + The Mutt Next Generation E-Mail Client 54 + The so called _F_o_r_m_a_t _S_t_r_i_n_g_s offer great flexibility when configuring mutt-ng. In short, they describe what items to print out how in menus and status mes- sages. @@ -2505,7 +2702,7 @@ +o the current mutt-ng version number The setting for the status bar of the index is controlled via the _$_s_t_a_t_u_s___f_o_r_- - _m_a_t (section 6.4.308 , page 157) variable. For the hostname and version + _m_a_t (section 7.4.324 , page 167) variable. For the hostname and version string, there's an expando for $status_format: %h expands to the hostname and %v to the version string. When just configuring: @@ -2519,8 +2716,6 @@ In the index, there're more useful information one could want to see: - The Mutt Next Generation E-Mail Client 51 - +o which mailbox is open +o how man new, flagged or postponed messages @@ -2537,6 +2732,9 @@ For the number of certain types of messages, one more feature of the format strings is extremely useful. If there aren't messages of a certain type, it may + + The Mutt Next Generation E-Mail Client 55 + not be desired to print just that there aren't any but instead only print some- thing if there are any. @@ -2565,8 +2763,6 @@ %??&? - The Mutt Next Generation E-Mail Client 52 - Using this we can make mutt-ng to do the following: +o make it print ``_n new messages'' whereby _n is the count but only if there @@ -2583,6 +2779,8 @@ set status_format = "%v on %h: %B: %?n?%n&no? new messages ... + The Mutt Next Generation E-Mail Client 56 + As you might see from this rather simple example, one can create very complex but fancy status messages. Please see the reference chapter for expandos and those which may be printed nonzero. @@ -2612,11 +2810,8 @@ Since the previous expando stops at the end of line, there must be a way to fill the gap between two items via the %>X expando: it puts as many characters X in between two items so that the rest of - the line will be right-justified. For example, to not put the - - The Mutt Next Generation E-Mail Client 53 - - version string and hostname of our example on the left but on the + the line will be right-justified. For example, to not put the ver- + sion string and hostname of our example on the left but on the right and fill the gap with spaces, one might use (note the space after %>): @@ -2630,17 +2825,20 @@ ject. To tag all messages matching a pattern, use the tag-pattern function, which is bound to ``shift-T'' by default. Or you can select individual mes- sages by hand using the ``tag-message'' function, which is bound to ``t'' by - default. See _p_a_t_t_e_r_n_s (section 6.2 , page 78) for Mutt-ng's pattern matching + + The Mutt Next Generation E-Mail Client 57 + + default. See _p_a_t_t_e_r_n_s (section 7.2 , page 84) for Mutt-ng's pattern matching syntax. Once you have tagged the desired messages, you can use the ``tag-prefix'' oper- ator, which is the ``;'' (semicolon) key by default. When the ``tag-prefix'' operator is used, the nneexxtt operation will be applied to all tagged messages if - that operation can be used in that manner. If the _$_a_u_t_o___t_a_g (section 6.4.16 , - page 87) variable is set, the next operation applies to the tagged messages + that operation can be used in that manner. If the _$_a_u_t_o___t_a_g (section 7.4.19 , + page 94) variable is set, the next operation applies to the tagged messages automatically, without requiring the ``tag-prefix''. - In _m_a_c_r_o_s (section 3.7 , page 27) or _p_u_s_h (section 3.23 , page 37) commands, + In _m_a_c_r_o_s (section 3.8 , page 30) or _p_u_s_h (section 3.24 , page 41) commands, you can use the ``tag-prefix-cond'' operator. If there are no tagged messages, mutt will "eat" the rest of the macro to abort it's execution. Mutt-ng will stop "eating" the macro when it encounters the ``end-cond'' operator; after @@ -2652,24 +2850,22 @@ arbitrary commands before performing some operation. For example, you may wish to tailor your configuration based upon which mailbox you are reading, or to whom you are sending mail. In the Mutt-ng world, a _h_o_o_k consists of a _r_e_g_u_l_a_r - _e_x_p_r_e_s_s_i_o_n (section 4.1 , page 44) or _p_a_t_t_e_r_n (section 6.2 , page 78) along + _e_x_p_r_e_s_s_i_o_n (section 4.1 , page 49) or _p_a_t_t_e_r_n (section 7.2 , page 84) along with a configuration option/command. See - +o _f_o_l_d_e_r_-_h_o_o_k (section 3.6 , page 26) + +o _f_o_l_d_e_r_-_h_o_o_k (section 3.7 , page 29) - +o _s_e_n_d_-_h_o_o_k (section 3.20 , page 36) + +o _s_e_n_d_-_h_o_o_k (section 3.21 , page 40) - +o _m_e_s_s_a_g_e_-_h_o_o_k (section 3.21 , page 37) - - The Mutt Next Generation E-Mail Client 54 + +o _m_e_s_s_a_g_e_-_h_o_o_k (section 3.22 , page 41) - +o _s_a_v_e_-_h_o_o_k (section 3.17 , page 35) + +o _s_a_v_e_-_h_o_o_k (section 3.18 , page 39) - +o _m_b_o_x_-_h_o_o_k (section 3.13 , page 33) + +o _m_b_o_x_-_h_o_o_k (section 3.14 , page 37) - +o _f_c_c_-_h_o_o_k (section 3.18 , page 35) + +o _f_c_c_-_h_o_o_k (section 3.19 , page 39) - +o _f_c_c_-_s_a_v_e_-_h_o_o_k (section 3.19 , page 36) + +o _f_c_c_-_s_a_v_e_-_h_o_o_k (section 3.20 , page 40) for specific details on each type of _h_o_o_k available. @@ -2681,15 +2877,17 @@ send-hook . 'unmy_hdr From:' send-hook ~C'^b@b\.b$' my_hdr from: c@c.c + The Mutt Next Generation E-Mail Client 58 + _4_._5_._1 _M_e_s_s_a_g_e _M_a_t_c_h_i_n_g _i_n _H_o_o_k_s Hooks that act upon messages (send-hook, save-hook, fcc-hook, message-hook) are evaluated in a slightly different manner. For the other types of hooks, a _r_e_g_- - _u_l_a_r _e_x_p_r_e_s_s_i_o_n (section 4.1 , page 44) is sufficient. But in dealing with + _u_l_a_r _e_x_p_r_e_s_s_i_o_n (section 4.1 , page 49) is sufficient. But in dealing with messages a finer grain of control is needed for matching since for different purposes you want to match different criteria. - Mutt-ng allows the use of the _s_e_a_r_c_h _p_a_t_t_e_r_n (section 6.2 , page 78) language + Mutt-ng allows the use of the _s_e_a_r_c_h _p_a_t_t_e_r_n (section 7.2 , page 84) language for matching messages in hook commands. This works in exactly the same way as it would when _l_i_m_i_t_i_n_g or _s_e_a_r_c_h_i_n_g the mailbox, except that you are restricted to those operators which match information mutt extracts from the header of the @@ -2706,14 +2904,12 @@ searching language. You can still specify a simple _r_e_g_u_l_a_r _e_x_p_r_e_s_s_i_o_n like the other hooks, in which case Mutt-ng will translate your pattern into the full language, using the translation specified by the _$_d_e_f_a_u_l_t___h_o_o_k (section - 6.4.45 , page 93) variable. The pattern is translated at the time the hook is - declared, so the value of _$_d_e_f_a_u_l_t___h_o_o_k (section 6.4.45 , page 93) that is in - effect at that time will be used. + 7.4.49 , page 101) variable. The pattern is translated at the time the hook + is declared, so the value of _$_d_e_f_a_u_l_t___h_o_o_k (section 7.4.49 , page 101) that is + in effect at that time will be used. _4_._6 _U_s_i_n_g _t_h_e _s_i_d_e_b_a_r - The Mutt Next Generation E-Mail Client 55 - The sidebar, a feature specific to Mutt-ng, allows you to use a mailbox listing which looks very similar to the ones you probably know from GUI mail clients. The sidebar lists all specified mailboxes, shows the number in each and high- @@ -2732,6 +2928,8 @@ You can also specify the colors for mailboxes with new mails by using: + The Mutt Next Generation E-Mail Client 59 + color sidebar_new red black color sidebar white black @@ -2761,11 +2959,9 @@ _4_._7 _E_x_t_e_r_n_a_l _A_d_d_r_e_s_s _Q_u_e_r_i_e_s - The Mutt Next Generation E-Mail Client 56 - Mutt-ng supports connecting to external directory databases such as LDAP, ph/qi, bbdb, or NIS through a wrapper script which connects to mutt using a - simple interface. Using the _$_q_u_e_r_y___c_o_m_m_a_n_d (section 6.4.221 , page 136) vari- + simple interface. Using the _$_q_u_e_r_y___c_o_m_m_a_n_d (section 7.4.237 , page 146) vari- able, you specify the wrapper command to use. For example: set query_command = "mutt_ldap_query.pl '%s'" @@ -2781,6 +2977,9 @@ Searching database ... 20 entries ... 3 matching: me@cs.hmc.edu Michael Elkins mutt dude blong@fiction.net Brandon Long mutt and more + + The Mutt Next Generation E-Mail Client 60 + roessler@guug.de Thomas Roessler mutt pgp There are two mechanisms for accessing the query function of mutt. One is to @@ -2804,7 +3003,7 @@ Mutt-ng supports reading and writing of four different mailbox formats: mbox, MMDF, MH and Maildir. The mailbox type is autodetected, so there is no need to use a flag for different mailbox types. When creating new mailboxes, Mutt-ng - uses the default specified with the _$_m_b_o_x___t_y_p_e (section 6.4.125 , page 113) + uses the default specified with the _$_m_b_o_x___t_y_p_e (section 7.4.132 , page 122) variable. mmbbooxx. This is the most widely used mailbox format for UNIX. All messages are @@ -2812,8 +3011,6 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST - The Mutt Next Generation E-Mail Client 57 - to denote the start of a new message (this is often referred to as the ``From_'' line). @@ -2832,6 +3029,9 @@ ment for sendmail). Similar to _M_H, except that it adds three subdirectories of the mailbox: _t_m_p, _n_e_w and _c_u_r. Filenames for the messages are chosen in such a way they are unique, even when two programs are writing the mailbox over NFS, + + The Mutt Next Generation E-Mail Client 61 + which means that no file locking is needed. _4_._9 _M_a_i_l_b_o_x _S_h_o_r_t_c_u_t_s @@ -2840,12 +3040,12 @@ These shortcuts can be used anywhere you are prompted for a file or mailbox path. - +o ! -- refers to your _$_s_p_o_o_l_f_i_l_e (section 6.4.297 , page 154) (incoming) + +o ! -- refers to your _$_s_p_o_o_l_f_i_l_e (section 7.4.313 , page 165) (incoming) mailbox - +o > -- refers to your _$_m_b_o_x (section 6.4.124 , page 113) file + +o > -- refers to your _$_m_b_o_x (section 7.4.131 , page 122) file - +o < -- refers to your _$_r_e_c_o_r_d (section 6.4.230 , page 138) file + +o < -- refers to your _$_r_e_c_o_r_d (section 7.4.246 , page 148) file +o ^ -- refers to the current mailbox @@ -2853,9 +3053,9 @@ +o ~ -- refers to your home directory - +o = or + -- refers to your _$_f_o_l_d_e_r (section 6.4.64 , page 97) directory + +o = or + -- refers to your _$_f_o_l_d_e_r (section 7.4.70 , page 105) directory - +o @_a_l_i_a_s -- refers to the _d_e_f_a_u_l_t _s_a_v_e _f_o_l_d_e_r (section 3.17 , page 35) as + +o @_a_l_i_a_s -- refers to the _d_e_f_a_u_l_t _s_a_v_e _f_o_l_d_e_r (section 3.18 , page 39) as determined by the address of the alias _4_._1_0 _H_a_n_d_l_i_n_g _M_a_i_l_i_n_g _L_i_s_t_s @@ -2864,17 +3064,14 @@ mail easier. The first thing you must do is to let Mutt know what addresses you consider to be mailing lists (technically this does not have to be a mail- ing list, but that is what it is most often used for), and what lists you are - - The Mutt Next Generation E-Mail Client 58 - subscribed to. This is accomplished through the use of the _l_i_s_t_s _a_n_d _s_u_b_s_c_r_i_b_e - (section 3.12 , page 32) commands in your muttrc. + (section 3.13 , page 36) commands in your muttrc. Now that Mutt-ng knows what your mailing lists are, it can do several things, the first of which is the ability to show the name of a list through which you received a message (i.e., of a subscribed list) in the _i_n_d_e_x menu display. This is useful to distinguish between personal and list mail in the same mail- - box. In the _$_i_n_d_e_x___f_o_r_m_a_t (section 6.4.110 , page 108) variable, the escape + box. In the _$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.116 , page 116) variable, the escape ``%L'' will return the string ``To '' when ``list'' appears in the ``To'' field, and ``Cc '' when it appears in the ``Cc'' field (otherwise it returns the name of the author). @@ -2885,11 +3082,14 @@ person. The ``list-reply'' function, which by default is bound to ``L'' in the _i_n_d_e_x menu and _p_a_g_e_r, helps reduce the clutter by only replying to the known mailing list addresses instead of all recipients (except as specified by Mail- + + The Mutt Next Generation E-Mail Client 62 + Followup-To, see below). Mutt-ng also supports the Mail-Followup-To header. When you send a message to a list of recipients which includes one or several subscribed mailing lists, - and if the _$_f_o_l_l_o_w_u_p___t_o (section 6.4.66 , page 98) option is set, mutt will + and if the _$_f_o_l_l_o_w_u_p___t_o (section 7.4.72 , page 106) option is set, mutt will generate a Mail-Followup-To header which contains all the recipients to whom you send this message, but not your address. This indicates that group-replies or list-replies (also known as ``followups'') to this message should only be @@ -2899,7 +3099,7 @@ Conversely, when group-replying or list-replying to a message which has a Mail- Followup-To header, mutt will respect this header if the _$_h_o_n_o_r___f_o_l_l_o_w_u_p___t_o - (section 6.4.88 , page 103) configuration variable is set. Using list-reply + (section 7.4.94 , page 111) configuration variable is set. Using list-reply will in this case also make sure that the reply goes to the mailing list, even if it's not specified in the list of recipients in the Mail-Followup-To. @@ -2912,7 +3112,7 @@ the message. This can create problems when trying to reply directly to the author in private, since most mail clients will automatically reply to the address given in the ``Reply-To'' field. Mutt-ng uses the _$_r_e_p_l_y___t_o (section - 6.4.233 , page 139) variable to help decide which address to use. If set to + 7.4.249 , page 149) variable to help decide which address to use. If set to _a_s_k_-_y_e_s or _a_s_k_-_n_o, you will be prompted as to whether or not you would like to use the address given in the ``Reply-To'' field, or reply directly to the address given in the ``From'' field. When set to _y_e_s, the ``Reply-To'' field @@ -2920,16 +3120,13 @@ The ``X-Label:'' header field can be used to further identify mailing lists or list subject matter (or just to annotate messages individually). The - _$_i_n_d_e_x___f_o_r_m_a_t (section 6.4.110 , page 108) variable's ``%y'' and ``%Y'' - - The Mutt Next Generation E-Mail Client 59 - + _$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.116 , page 116) variable's ``%y'' and ``%Y'' escapes can be used to expand ``X-Label:'' fields in the index, and Mutt-ng's pattern-matcher can match regular expressions to ``X-Label:'' fields with the ``~y'' selector. ``X-Label:'' is not a standard message header field, but it can easily be inserted by procmail and other mail filtering agents. - Lastly, Mutt-ng has the ability to _s_o_r_t (section 6.4.291 , page 152) the mail- + Lastly, Mutt-ng has the ability to _s_o_r_t (section 7.4.307 , page 163) the mail- box into _t_h_r_e_a_d_s (section 2.5.3 , page 11). A thread is a group of messages which all relate to the same subject. This is usually organized into a tree- like structure where a message and all of its replies are represented graphi- @@ -2940,6 +3137,9 @@ _4_._1_1 _E_d_i_t_i_n_g _t_h_r_e_a_d_s Mutt-ng has the ability to dynamically restructure threads that are broken + + The Mutt Next Generation E-Mail Client 63 + either by misconfigured software or bad behavior from some correspondents. This allows to clean your mailboxes formats) from these annoyances which make it hard to follow a discussion. @@ -2974,25 +3174,24 @@ +o Berkeley sendmail 8.8.x currently has some command line options in which the mail client can make requests as to what type of status messages - - The Mutt Next Generation E-Mail Client 60 - should be returned. +o The SMTP support via libESMTP supports it, too. To support this, there are two variables: - +o _$_d_s_n___n_o_t_i_f_y (section 6.4.51 , page 94) is used to request receipts for + +o _$_d_s_n___n_o_t_i_f_y (section 7.4.56 , page 102) is used to request receipts for different results (such as failed message, message delivered, etc.). - +o _$_d_s_n___r_e_t_u_r_n (section 6.4.52 , page 94) requests how much of your message + +o _$_d_s_n___r_e_t_u_r_n (section 7.4.57 , page 103) requests how much of your message should be returned with the receipt (headers or full message). Please see the reference chapter for possible values. _4_._1_3 _P_O_P_3 _S_u_p_p_o_r_t _(_O_P_T_I_O_N_A_L_) + The Mutt Next Generation E-Mail Client 64 + If Mutt-ng was compiled with POP3 support (by running the _c_o_n_f_i_g_u_r_e script with the _-_-_e_n_a_b_l_e_-_p_o_p flag), it has the ability to work with mailboxes located on a remote POP3 server and fetch mail for local browsing. @@ -3008,7 +3207,7 @@ Polling for new mail is more expensive over POP3 than locally. For this reason the frequency at which Mutt-ng will check for mail remotely can be controlled - by the _$_p_o_p___m_a_i_l___c_h_e_c_k (section 6.4.208 , page 133) variable, which defaults + by the _$_p_o_p___m_a_i_l___c_h_e_c_k (section 7.4.224 , page 144) variable, which defaults to every 60 seconds. If Mutt-ng was compiled with SSL support (by running the _c_o_n_f_i_g_u_r_e script with @@ -3018,8 +3217,8 @@ name@]popserver[:port]/. Another way to access your POP3 mail is the _f_e_t_c_h_-_m_a_i_l function (default: G). - It allows to connect to _p_o_p___h_o_s_t (section 6.4.206 , page 133), fetch all your - new mail and place it in the local _s_p_o_o_l_f_i_l_e (section 6.4.297 , page 154). + It allows to connect to _p_o_p___h_o_s_t (section 7.4.222 , page 143), fetch all your + new mail and place it in the local _s_p_o_o_l_f_i_l_e (section 7.4.313 , page 165). After this point, Mutt-ng runs exactly as if the mail had always been local. NNoottee:: If you only need to fetch all messages to local mailbox you should con- @@ -3027,8 +3226,6 @@ _4_._1_4 _I_M_A_P _S_u_p_p_o_r_t _(_O_P_T_I_O_N_A_L_) - The Mutt Next Generation E-Mail Client 61 - If Mutt-ng was compiled with IMAP support (by running the _c_o_n_f_i_g_u_r_e script with the _-_-_e_n_a_b_l_e_-_i_m_a_p flag), it has the ability to work with folders located on a remote IMAP server. @@ -3047,6 +3244,9 @@ name@imapserver[:port]/INBOX. If Mutt-ng was compiled with SSL support (by running the _c_o_n_f_i_g_u_r_e script with + + The Mutt Next Generation E-Mail Client 65 + the _-_-_w_i_t_h_-_s_s_l flag), connections to IMAP servers can be encrypted. This natu- rally requires that the server supports SSL encrypted connections. To access a folder with IMAP/SSL, you should use imaps://[user- @@ -3061,12 +3261,12 @@ When browsing folders on an IMAP server, you can toggle whether to look at only the folders you are subscribed to, or all folders with the _t_o_g_g_l_e_-_s_u_b_s_c_r_i_b_e_d - command. See also the _$_i_m_a_p___l_i_s_t___s_u_b_s_c_r_i_b_e_d (section 6.4.97 , page 105) vari- - able. + command. See also the _$_i_m_a_p___l_i_s_t___s_u_b_s_c_r_i_b_e_d (section 7.4.103 , page 114) + variable. Polling for new mail on an IMAP server can cause noticeable delays. So, you'll - want to carefully tune the _$_i_m_a_p___m_a_i_l___c_h_e_c_k (section 6.4.99 , page 105) and - _$_t_i_m_e_o_u_t (section 6.4.321 , page 161) variables. + want to carefully tune the _$_i_m_a_p___m_a_i_l___c_h_e_c_k (section 7.4.105 , page 114) and + _$_t_i_m_e_o_u_t (section 7.4.337 , page 172) variables. Note that if you are using mbox as the mail store on UW servers prior to v12.250, the server has been reported to disconnect a client if another client @@ -3082,8 +3282,6 @@ sages and subfolders. On Cyrus-like servers folders will often contain both messages and subfolders. - The Mutt Next Generation E-Mail Client 62 - +o For the case where an entry can contain both messages and subfolders, the selection key (bound to enter by default) will choose to descend into the subfolder view. If you wish to view the messages in that folder, you must @@ -3103,6 +3301,8 @@ which allows you to log in to a public IMAP server without having an account. To use ANONYMOUS, simply make your username blank or "anonymous". + The Mutt Next Generation E-Mail Client 66 + SASL is a special super-authenticator, which selects among several protocols (including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most secure method available on your host and the server. Using some of these methods (including @@ -3116,15 +3316,15 @@ There are a few variables which control authentication: - +o _$_i_m_a_p___u_s_e_r (section 6.4.105 , page 107) - controls the username under + +o _$_i_m_a_p___u_s_e_r (section 7.4.111 , page 115) - controls the username under which you request authentication on the IMAP server, for all authentica- tors. This is overridden by an explicit username in the mailbox path (i.e. by using a mailbox name of the form {user@host}). - +o _$_i_m_a_p___p_a_s_s (section 6.4.100 , page 106) - a password which you may pre- + +o _$_i_m_a_p___p_a_s_s (section 7.4.106 , page 114) - a password which you may pre- set, used by all authentication methods where a password is needed. - +o _$_i_m_a_p___a_u_t_h_e_n_t_i_c_a_t_o_r_s (section 6.4.91 , page 103) - a colon-delimited list + +o _$_i_m_a_p___a_u_t_h_e_n_t_i_c_a_t_o_r_s (section 7.4.97 , page 112) - a colon-delimited list of IMAP authentication methods to try, in the order you wish to try them. If specified, this overrides mutt's default (attempt everything, in the order listed above). @@ -3135,12 +3335,9 @@ newsserver via NNTP. You can open a newsgroup with the ``change-newsgroup'' function from the index/pager which is by default bound to i. - The Default newsserver can be obtained from the $NNTPSERVER environment - - The Mutt Next Generation E-Mail Client 63 - - variable. Like other news readers, info about subscribed newsgroups is saved in - a file as specified by the _$_n_n_t_p___n_e_w_s_r_c (section 6.4.156 , page 121) variable. + The Default newsserver can be obtained from the $NNTPSERVER environment vari- + able. Like other news readers, info about subscribed newsgroups is saved in a + file as specified by the _$_n_n_t_p___n_e_w_s_r_c (section 7.4.172 , page 131) variable. Article headers are cached and can be loaded from a file when a newsgroup is entered instead loading from newsserver; currently, this caching mechanism still is different from the header caching for maildir/IMAP. @@ -3149,8 +3346,8 @@ Especially for Usenet, people often ask for advanced filtering and scoring functionality. Of course, mutt-ng has scoring and allows a killfile, too. How - to use a killfile has been discussed in _M_e_s_s_a_g_e _s_c_o_r_i_n_g (section 3.25 , page - 38). + to use a killfile has been discussed in _M_e_s_s_a_g_e _s_c_o_r_i_n_g (section 3.26 , page + 42). What has not been discusses in detail is mutt-ng's built-in realname filter. For may newsreaders including those for ``advanced users'' like _s_l_r_n or _t_i_n, @@ -3159,7 +3356,9 @@ In mutt-ng this is as easy as - score ~* =42 + The Mutt Next Generation E-Mail Client 67 + + score ~* =42 This tells mutt-ng to apply a score of 42 to all messages whose sender speci- fied a valid realname and a valid email address. Using @@ -3183,33 +3382,33 @@ _4_._1_6 _S_M_T_P _S_u_p_p_o_r_t _(_O_P_T_I_O_N_A_L_) Mutt-ng can be built using a library called ``libESMTP'' which provides SMTP - - The Mutt Next Generation E-Mail Client 64 - functionality. When configure was called with --with-libesmtp or the output muttng -v contains +USE_LIBESMTP, this will be or is the case already. The SMTP support includes support for Delivery Status Notification (see _D_e_l_i_v_e_r_y _S_t_a_t_u_s - _N_o_t_i_f_i_c_a_t_i_o_n (section 4.12 , page 59) section) as well as handling the 8BIT- - MIME flag controlled via _$_u_s_e___8_b_i_t_m_i_m_e (section 6.4.328 , page 163). + _N_o_t_i_f_i_c_a_t_i_o_n (section 4.12 , page 63) section) as well as handling the 8BIT- + MIME flag controlled via _$_u_s_e___8_b_i_t_m_i_m_e (section 7.4.344 , page 173). To enable sending mail directly via SMTP without an MTA such as Postfix or - SSMTP and the like, simply set the _$_s_m_t_p___h_o_s_t (section 6.4.286 , page 151) + SSMTP and the like, simply set the _$_s_m_t_p___h_o_s_t (section 7.4.302 , page 161) variable pointing to your SMTP server. - Authentication mechanisms are available via the _$_s_m_t_p___u_s_e_r (section 6.4.290 , - page 152) and _$_s_m_t_p___p_a_s_s (section 6.4.287 , page 151) variables. + Authentication mechanisms are available via the _$_s_m_t_p___u_s_e_r (section 7.4.306 , + page 162) and _$_s_m_t_p___p_a_s_s (section 7.4.303 , page 162) variables. Transport Encryption via the StartTLS command is also available. For this to work, first of all Mutt-ng must be built with SSL or GNUTLS. Secondly, the - _$_s_m_t_p___u_s_e___t_l_s (section 6.4.289 , page 152) variable must be either set to + _$_s_m_t_p___u_s_e___t_l_s (section 7.4.305 , page 162) variable must be either set to ``enabled'' or ``required.'' In both cases, StartTLS will be used if the server supports it: for the second case, the connection will fail if it doesn't while switching back to unencrypted communication for the first one. Some mail providers require user's to set a particular envelope sender, i.e. + + The Mutt Next Generation E-Mail Client 68 + they allow for only one value which may not be what the user wants to send as - the From: header. In this case, the variable _$_s_m_t_p___e_n_v_e_l_o_p_e (section 6.4.285 , - page 151) may be used to set the envelope different from the From: header. + the From: header. In this case, the variable _$_s_m_t_p___e_n_v_e_l_o_p_e (section 7.4.301 , + page 161) may be used to set the envelope different from the From: header. _4_._1_7 _M_a_n_a_g_i_n_g _m_u_l_t_i_p_l_e _I_M_A_P_/_P_O_P_/_N_N_T_P _a_c_c_o_u_n_t_s _(_O_P_T_I_O_N_A_L_) @@ -3236,8 +3435,6 @@ macro index \cb |urlview\n macro pager \cb |urlview\n - The Mutt Next Generation E-Mail Client 65 - _4_._1_9 _C_o_m_p_r_e_s_s_e_d _f_o_l_d_e_r_s _S_u_p_p_o_r_t _(_O_P_T_I_O_N_A_L_) If Mutt-ng was compiled with compressed folders support (by running the _c_o_n_f_i_g_- @@ -3252,11 +3449,13 @@ may be faster than converting the entire folder to the accepted format, append- ing to it and converting back to the user-defined format. - There are three hooks defined (_o_p_e_n_-_h_o_o_k (section 4.19.1 , page 65), _c_l_o_s_e_- - _h_o_o_k (section 4.19.2 , page 65) and _a_p_p_e_n_d_-_h_o_o_k (section 4.19.3 , page 66)) + There are three hooks defined (_o_p_e_n_-_h_o_o_k (section 4.19.1 , page 69), _c_l_o_s_e_- + _h_o_o_k (section 4.19.2 , page 69) and _a_p_p_e_n_d_-_h_o_o_k (section 4.19.3 , page 70)) which define commands to uncompress and compress a folder and to append mes- sages to an existing compressed folder respectively. + The Mutt Next Generation E-Mail Client 69 + For example: open-hook \\.gz$ "gzip -cd %f > %t" @@ -3264,17 +3463,17 @@ append-hook \\.gz$ "gzip -c %t >> %f" You do not have to specify all of the commands. If you omit _a_p_p_e_n_d_-_h_o_o_k (sec- - tion 4.19.3 , page 66), the folder will be open and closed again each time you - will add to it. If you omit _c_l_o_s_e_-_h_o_o_k (section 4.19.2 , page 65) (or give + tion 4.19.3 , page 70), the folder will be open and closed again each time you + will add to it. If you omit _c_l_o_s_e_-_h_o_o_k (section 4.19.2 , page 69) (or give empty command) , the folder will be open in the mode. If you specify _a_p_p_e_n_d_- - _h_o_o_k (section 4.19.3 , page 66) though you'll be able to append to the folder. + _h_o_o_k (section 4.19.3 , page 70) though you'll be able to append to the folder. Note that Mutt-ng will only try to use hooks if the file is not in one of the accepted formats. In particular, if the file is empty, mutt supposes it is not compressed. This is important because it allows the use of programs that do not have well defined extensions. Just use '.' as a regexp. But this may be sur- prising if your compressing script produces empty files. In this situation, - unset _$_s_a_v_e___e_m_p_t_y (section 6.4.240 , page 141), so that the compressed file + unset _$_s_a_v_e___e_m_p_t_y (section 7.4.256 , page 151), so that the compressed file will be removed if you delete all of the messages. _4_._1_9_._1 _O_p_e_n _a _c_o_m_p_r_e_s_s_e_d _m_a_i_l_b_o_x _f_o_r _r_e_a_d_i_n_g @@ -3290,9 +3489,6 @@ %f and %t can be repeated any number of times in the command string, and all of the entries are replaced with the appropriate folder name. In addition, %% is - - The Mutt Next Generation E-Mail Client 66 - replaced by %, as in printf, and any other %anything is left as is. The _c_o_m_m_a_n_d should nnoott remove the original compressed file. The _c_o_m_m_a_n_d should @@ -3309,12 +3505,14 @@ Usage: close-hook _r_e_g_e_x_p '_c_o_m_m_a_n_d' This is used to close the folder that was open with the _o_p_e_n_-_h_o_o_k (section - 4.19.1 , page 65) command after some changes were made to it. + 4.19.1 , page 69) command after some changes were made to it. + + The Mutt Next Generation E-Mail Client 70 The _c_o_m_m_a_n_d string is the command that can be used for closing the folders whose names match _r_e_g_e_x_p. It has the same format as in the _o_p_e_n_-_h_o_o_k (section - 4.19.1 , page 65) command. Temporary folder in this case is the folder previ- - ously produced by the <_o_p_e_n_-_h_o_o_k (section 4.19.1 , page 65) command. + 4.19.1 , page 69) command. Temporary folder in this case is the folder previ- + ously produced by the <_o_p_e_n_-_h_o_o_k (section 4.19.1 , page 69) command. The _c_o_m_m_a_n_d should nnoott remove the decompressed file. The _c_o_m_m_a_n_d should return non-zero exit status if it fails, so mutt knows something's wrong. @@ -3326,7 +3524,7 @@ If the _c_o_m_m_a_n_d is empty, this operation is disabled for this file type, and the file can only be open in the readonly mode. - _c_l_o_s_e_-_h_o_o_k (section 4.19.2 , page 65) is not called when you exit from the + _c_l_o_s_e_-_h_o_o_k (section 4.19.2 , page 69) is not called when you exit from the folder if the folder was not changed. _4_._1_9_._3 _A_p_p_e_n_d _a _m_e_s_s_a_g_e _t_o _a _c_o_m_p_r_e_s_s_e_d _m_a_i_l_b_o_x @@ -3335,7 +3533,7 @@ This command is used for saving to an existing compressed folder. The _c_o_m_m_a_n_d is the command that can be used for appending to the folders whose names match - _r_e_g_e_x_p. It has the same format as in the _o_p_e_n_-_h_o_o_k (section 4.19.1 , page 65) + _r_e_g_e_x_p. It has the same format as in the _o_p_e_n_-_h_o_o_k (section 4.19.1 , page 69) command. The temporary folder in this case contains the messages that are being appended. @@ -3344,24 +3542,24 @@ Example: - The Mutt Next Generation E-Mail Client 67 - append-hook \\.gz$ "gzip -c %t >> %f" - When _a_p_p_e_n_d_-_h_o_o_k (section 4.19.3 , page 66) is used, the folder is not opened, + When _a_p_p_e_n_d_-_h_o_o_k (section 4.19.3 , page 70) is used, the folder is not opened, which saves time, but this means that we can not find out what the folder type - is. Thus the default (_$_m_b_o_x___t_y_p_e (section 6.4.125 , page 113)) type is always + is. Thus the default (_$_m_b_o_x___t_y_p_e (section 7.4.132 , page 122)) type is always supposed (i.e. this is the format used for the temporary folder). If the file does not exist when you save to it, _c_l_o_s_e_-_h_o_o_k (section 4.19.2 , - page 65) is called, and not _a_p_p_e_n_d_-_h_o_o_k (section 4.19.3 , page 66). _a_p_p_e_n_d_- - _h_o_o_k (section 4.19.3 , page 66) is only for appending to existing folders. + page 69) is called, and not _a_p_p_e_n_d_-_h_o_o_k (section 4.19.3 , page 70). _a_p_p_e_n_d_- + _h_o_o_k (section 4.19.3 , page 70) is only for appending to existing folders. If the _c_o_m_m_a_n_d is empty, this operation is disabled for this file type. In this case, the folder will be open and closed again (using _o_p_e_n_-_h_o_o_k (section - 4.19.1 , page 65) and _c_l_o_s_e_-_h_o_o_k (section 4.19.2 , page 65)respectively) each + 4.19.1 , page 69) and _c_l_o_s_e_-_h_o_o_k (section 4.19.2 , page 69)respectively) each time you will add to it. + The Mutt Next Generation E-Mail Client 71 + _4_._1_9_._4 _E_n_c_r_y_p_t_e_d _f_o_l_d_e_r_s The compressed folders support can also be used to handle encrypted folders. If @@ -3392,8 +3590,6 @@ There are three areas/menus in Mutt-ng which deal with MIME, they are the pager (while viewing a message), the attachment menu and the compose menu. - The Mutt Next Generation E-Mail Client 68 - _5_._1_._1 _V_i_e_w_i_n_g _M_I_M_E _m_e_s_s_a_g_e_s _i_n _t_h_e _p_a_g_e_r When you select a message from the index and view it in the pager, Mutt decodes @@ -3411,6 +3607,8 @@ Where the Description is the description or filename given for the attachment, and the Encoding is one of 7bit/8bit/quoted-printable/base64/binary. + The Mutt Next Generation E-Mail Client 72 + If Mutt-ng cannot deal with a MIME type, it will display a message like: [-- image/gif is unsupported (use 'v' to view this part) --] @@ -3447,8 +3645,6 @@ - 1 [text/plain, 7bit, 1K] /tmp/mutt-euler-8082-0 2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz - The Mutt Next Generation E-Mail Client 69 - The '-' denotes that Mutt-ng will delete the file after sending (or postponing, or canceling) the message. It can be toggled with the toggle-unlink command (default: u). The next field is the MIME content-type, and can be changed with @@ -3463,6 +3659,9 @@ _5_._2 _M_I_M_E _T_y_p_e _c_o_n_f_i_g_u_r_a_t_i_o_n _w_i_t_h _m_i_m_e_._t_y_p_e_s When you add an attachment to your mail message, Mutt-ng searches your personal + + The Mutt Next Generation E-Mail Client 73 + mime.types file at ${HOME}/.mime.types, and then the system mime.types file at /usr/local/share/mutt/mime.types or /etc/mime.types @@ -3498,9 +3697,6 @@ referred to as the mailcap format. Many MIME compliant programs utilize the mailcap format, allowing you to specify handling for all MIME types in one place for all programs. Programs known to use this format include Netscape, - - The Mutt Next Generation E-Mail Client 70 - XMosaic, lynx and metamail. In order to handle various MIME types that Mutt-ng can not handle internally, @@ -3515,6 +3711,8 @@ In particular, the metamail distribution will install a mailcap file, usually as /usr/local/etc/mailcap, which contains some baseline entries. + The Mutt Next Generation E-Mail Client 74 + _5_._3_._1 _T_h_e _B_a_s_i_c_s _o_f _t_h_e _m_a_i_l_c_a_p _f_i_l_e A mailcap file consists of a series of lines which are comments, blank, or def- @@ -3553,8 +3751,6 @@ text/plain; more %s - The Mutt Next Generation E-Mail Client 71 - Perhaps you would like to use lynx to interactively view a text/html message: text/html; lynx %s @@ -3568,6 +3764,8 @@ On the other hand, maybe you don't want to use lynx interactively, you just want to have it convert the text/html to text/plain, then you can use: + The Mutt Next Generation E-Mail Client 75 + text/html; lynx -dump %s | more Perhaps you wish to use lynx to view text/html files, and a pager on all other @@ -3583,7 +3781,7 @@ The interpretation of shell meta-characters embedded in MIME parameters can lead to security problems in general. Mutt-ng tries to quote parameters in expansion of %s syntaxes properly, and avoids risky characters by substituting - them, see the _m_a_i_l_c_a_p___s_a_n_i_t_i_z_e (section 6.4.117 , page 112) variable. + them, see the _m_a_i_l_c_a_p___s_a_n_i_t_i_z_e (section 7.4.123 , page 120) variable. Although mutt's procedures to invoke programs with mailcap seem to be safe, there are other applications parsing mailcap, maybe taking less care of it. @@ -3605,8 +3803,6 @@ text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \ && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1 - The Mutt Next Generation E-Mail Client 72 - _5_._3_._3 _A_d_v_a_n_c_e_d _m_a_i_l_c_a_p _U_s_a_g_e _5_._3_._3_._1 _O_p_t_i_o_n_a_l _F_i_e_l_d_s @@ -3620,6 +3816,9 @@ amounts of text on stdout. This causes Mutt-ng to invoke a pager (either the internal pager or the external pager defined by the pager variable) on the output of the view command. Without this + + The Mutt Next Generation E-Mail Client 76 + flag, Mutt-ng assumes that the command is interactive. One could use this to replace the pipe to more in the lynx -dump example in the Basic section: @@ -3631,11 +3830,11 @@ needsterminal Mutt-ng uses this flag when viewing attachments with _a_u_t_o_v_i_e_w (sec- - tion 5.4 , page 75), in order to decide whether it should honor - the setting of the _$_w_a_i_t___k_e_y (section 6.4.335 , page 164) variable + tion 5.4 , page 79), in order to decide whether it should honor + the setting of the _$_w_a_i_t___k_e_y (section 7.4.350 , page 174) variable or not. When an attachment is viewed using an interactive program, and the corresponding mailcap entry has a _n_e_e_d_s_t_e_r_m_i_n_a_l flag, Mutt- - ng will use _$_w_a_i_t___k_e_y (section 6.4.335 , page 164) and the exit + ng will use _$_w_a_i_t___k_e_y (section 7.4.350 , page 174) and the exit status of the program to decide if it will ask you to press a key after the external program has exited. In all other situations it will not prompt you for a key. @@ -3660,9 +3859,6 @@ edit= This flag specifies the command to use to edit a specific MIME type. Mutt-ng supports this from the compose menu, and also uses - - The Mutt Next Generation E-Mail Client 73 - it to compose new attachments. Mutt-ng will default to the defined editor for text attachments. @@ -3676,6 +3872,8 @@ text/html; lynx %s; nametemplate=%s.html + The Mutt Next Generation E-Mail Client 77 + test= This field specifies a command to run to test whether this mailcap entry should be used. The command is defined with the command @@ -3709,19 +3907,17 @@ Mutt-ng will skip the image/* entry and use the image/gif entry with the print command. - In addition, you can use this with _A_u_t_o_v_i_e_w (section 5.4 , page 75) to denote + In addition, you can use this with _A_u_t_o_v_i_e_w (section 5.4 , page 79) to denote two commands for viewing an attachment, one to be viewed automatically, the other to be viewed interactively from the attachment menu. In addition, you can then use the test feature to determine which viewer to use interactively depending on your environment. - The Mutt Next Generation E-Mail Client 74 - text/html; netscape -remote 'openURL(%s)' ; test=RunningX text/html; lynx %s; nametemplate=%s.html text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput - For _A_u_t_o_v_i_e_w (section 5.4 , page 75), Mutt-ng will choose the third entry + For _A_u_t_o_v_i_e_w (section 5.4 , page 79), Mutt-ng will choose the third entry because of the copiousoutput tag. For interactive viewing, Mutt will run the program RunningX to determine if it should use the first entry. If the program returns non-zero, Mutt-ng will use the second entry for interactive viewing. @@ -3729,6 +3925,9 @@ _5_._3_._3_._3 _C_o_m_m_a_n_d _E_x_p_a_n_s_i_o_n The various commands defined in the mailcap files are passed to the /bin/sh + + The Mutt Next Generation E-Mail Client 78 + shell using the system() function. Before the command is passed to /bin/sh -c, it is parsed to expand various special parameters with information from Mutt- ng. The keywords Mutt-ng expands are: @@ -3768,8 +3967,6 @@ This mailcap file is fairly simple and standard: - The Mutt Next Generation E-Mail Client 75 - # I'm always running X :) video/*; xanim %s > /dev/null image/*; xv %s > /dev/null @@ -3779,6 +3976,8 @@ This mailcap file shows quite a number of examples: + The Mutt Next Generation E-Mail Client 79 + # Use xanim to view all videos Xanim produces a header on startup, # send that to /dev/null so I don't see it video/*; xanim %s > /dev/null @@ -3818,11 +4017,8 @@ _5_._4 _M_I_M_E _A_u_t_o_v_i_e_w In addition to explicitly telling Mutt-ng to view an attachment with the MIME - viewer defined in the mailcap file, Mutt-ng has support for automatically - - The Mutt Next Generation E-Mail Client 76 - - viewing MIME attachments while in the pager. + viewer defined in the mailcap file, Mutt-ng has support for automatically view- + ing MIME attachments while in the pager. To work, you must define a viewer in the mailcap file which uses the copi- ousoutput option to denote that it is non-interactive. Usually, you also use @@ -3834,6 +4030,8 @@ For instance, if you set auto_view to: + The Mutt Next Generation E-Mail Client 80 + auto_view text/html application/x-gunzip application/postscript image/gif application/x-tar-gz Mutt-ng could use the following mailcap entries to automatically view attach- @@ -3860,7 +4058,7 @@ alternative_order text/enriched text/plain text application/postscript image/* Next, mutt will check if any of the types have a defined _a_u_t_o___v_i_e_w (section - 5.4 , page 75), and use that. Failing that, Mutt-ng will look for any text + 5.4 , page 79), and use that. Failing that, Mutt-ng will look for any text type. As a last attempt, mutt will look for any type it knows how to handle. To remove a MIME type from the alternative_order list, use the unalterna- @@ -3869,9 +4067,6 @@ _5_._6 _M_I_M_E _L_o_o_k_u_p Mutt-ng's mime_lookup list specifies a list of mime-types that should not be - - The Mutt Next Generation E-Mail Client 77 - treated according to their mailcap entry. This option is designed to deal with binary types such as application/octet-stream. When an attachment's mime-type is listed in mime_lookup, then the extension of the filename will be compared @@ -3883,21 +4078,142 @@ mime_lookup application/octet-stream application/X-Lotus-Manuscript In addition, the unmime_lookup command may be used to disable this feature for + + The Mutt Next Generation E-Mail Client 81 + any particular mime-type if it had been set, for example, in a global muttrc. - _6_. _R_e_f_e_r_e_n_c_e + _6_. _S_e_c_u_r_i_t_y _C_o_n_s_i_d_e_r_a_t_i_o_n_s + + First of all, mutt-ng contains no security holes included by intention but may + contain unknown security holes. As a consequence, please run mutt-ng only with + as few permissions as possible. + + Please do not run mutt-ng as the super user. + + When configuring mutt-ng, there're some points to note about secure setups. + + In practice, mutt-ng can be easily made as vulnerable as even the most insecure + mail user agents (in their default configuration) just by changing mutt-ng's + configuration files: it then can execute arbitrary programs and scripts + attached to messages, send out private data on its own, etc. Although this is + not believed to the common type of setup, please read this chapter carefully. + + _6_._1 _P_a_s_s_w_o_r_d_s + + Although mutt-ng can be told the various passwords for accounts, please never + store passwords in configuration files. Besides the fact that the system's + operator can always read them, you could forget to replace the actual password + with asterisks when reporting a bug or asking for help via, for example, a + mailing list so that your mail including your password could be archived by + internet search engines, etc. Please never store passwords on disk. + + _6_._2 _T_e_m_p_o_r_a_r_y _F_i_l_e_s + + Mutt-ng uses many temporary files for viewing messages, verifying digital sig- + natures, etc. The _$_u_m_a_s_k (section 7.4.342 , page 173) variable can be used to + change the default permissions of these files. Please only change it if you + really know what you are doing. Also, a different location for these files may + be desired which can be changed via the _$_t_m_p_d_i_r (section 7.4.338 , page 172) + variable. + + _6_._3 _I_n_f_o_r_m_a_t_i_o_n _L_e_a_k_s + + _6_._3_._1 _M_e_s_s_a_g_e_-_I_D_: _h_e_a_d_e_r_s + + In the default configuration, mutt-ng will leak some information to the outside + world when sending messages: the generation of Message-ID: headers includes a + step counter which is increased (and rotated) with every message sent. If you'd + like to hide this information probably telling others how many mail you sent in + which time, you at least need to remove the %P expando from the default setting + of the _$_m_s_g_i_d___f_o_r_m_a_t (section 7.4.149 , page 125) variable. Please make sure + that you really know how local parts of these Message-ID: headers are composed. + + The Mutt Next Generation E-Mail Client 82 + + _6_._3_._2 _m_a_i_l_t_o_:_-_s_t_y_l_e _l_i_n_k_s + + As mutt-ng be can be set up to be the mail client to handle mailto: style links + in websites, there're security considerations, too. To keep the old behavior by + default, mutt-ng will be strict in interpreting them which means that arbitrary + header fields can be embedded in these links which could override existing + header fields or attach arbitrary files. This may be problematic if the + _$_e_d_i_t___h_e_a_d_e_r_s (section 7.4.59 , page 103) variable is _u_n_s_e_t, i.e. the user + doesn't want to see header fields while editing the message. + + For example, following a link like + + mailto:joe@host?Attach=~/.gnupg/secring.gpg + + will send out the user's private gnupg keyring to joe@host if the user doesn't + follow the information on screen carefully enough. + + When _u_n_s_e_t_t_i_n_g the _$_s_t_r_i_c_t___m_a_i_l_t_o (section 7.4.326 , page 169) variable, mutt- + ng will + + +o be less strict when interpreting these links by prepending a X-Mailto- + string to all header fields embedded in such a link _a_n_d + + +o turn on the _$_e_d_i_t___h_e_a_d_e_r_s (section 7.4.59 , page 103) variable by force + to let the user see all the headers (because they still may leak informa- + tion.) + + _6_._4 _E_x_t_e_r_n_a_l _a_p_p_l_i_c_a_t_i_o_n_s + + Mutt-ng in many places has to rely on external applications or for convenience + supports mechanisms involving external applications. + + _6_._4_._1 _m_a_i_l_c_a_p - _6_._1 _C_o_m_m_a_n_d _l_i_n_e _o_p_t_i_o_n_s + One of these is the mailcap mechanism as defined by RfC 1524. Mutt-ng can be + set up to _a_u_t_o_m_a_t_i_c_a_l_l_y execute any given utility as listed in one of the mail- + cap files (see the _$_m_a_i_l_c_a_p___p_a_t_h (section 7.4.122 , page 120) variable for + details.) + + These utilities may have a variety of security vulnerabilities, including over- + writing of arbitrary files, information leaks or other exploitable bugs. These + vulnerabilities may go unnoticed by the user, especially when they are called + automatically (and without interactive prompting) from the mailcap file(s). + When using mutt-ng's autoview mechanism in combination with mailcap files, + please be sure to... + + +o manually select trustworth applications with a reasonable calling sequence + + +o periodically check the contents of mailcap files, especially after soft- + ware installations or upgrades + + The Mutt Next Generation E-Mail Client 83 + + +o keep the software packages referenced in the mailcap file up to date + + +o leave the _$_m_a_i_l_c_a_p___s_a_n_i_t_i_z_e (section 7.4.123 , page 120) variable in its + default state to restrict mailcap expandos to a safe set of characters + + _6_._4_._2 _O_t_h_e_r + + Besides the mailcap mechanism, mutt-ng uses a number of other external utili- + ties for operation. + + The same security considerations apply for these as for tools involved via + mailcap (for example, mutt-ng is vulnerable to Denial of Service Attacks with + compressed folders support if the uncompressed mailbox is too large for the + disk it is saved to.) + + As already noted, most of these problems are not built in but caused by wrong + configuration, so please check your configuration. + + _7_. _R_e_f_e_r_e_n_c_e + + _7_._1 _C_o_m_m_a_n_d _l_i_n_e _o_p_t_i_o_n_s Running mutt with no arguments will make Mutt-ng attempt to read your spool mailbox. However, it is possible to read other mailboxes and to send messages from the command line as well. - -A expand an alias + -A expand an alias -a attach a file to a message -b specify a blind carbon-copy (BCC) address -c specify a carbon-copy (Cc) address - -D print the value of all variables on stdout -e specify a config command to be run after initialization files are read -f specify a mailbox to load -F specify an alternate file to read initialization commands @@ -3910,6 +4226,8 @@ -Q query a configuration variable -R open mailbox in read-only mode -s specify a subject (enclose in quotes if it contains spaces) + -t dump the value of all variables to stdout + -T dump the value of all changed variables to stdout -v show version number and compile-time definitions -x simulate the mailx(1) compose mode -y show a menu containing the files specified by the mailboxes command @@ -3918,7 +4236,7 @@ To read messages in a mailbox - The Mutt Next Generation E-Mail Client 78 + The Mutt Next Generation E-Mail Client 84 mutt [ -nz ] [ -F _m_u_t_t_r_c ] [ -m _t_y_p_e ] [ -f _m_a_i_l_b_o_x ] @@ -3936,9 +4254,9 @@ of ``data set for run #2''. In the body of the message will be the contents of the file ``~/run2.dat''. - _6_._2 _P_a_t_t_e_r_n_s + _7_._2 _P_a_t_t_e_r_n_s - The Mutt Next Generation E-Mail Client 79 + The Mutt Next Generation E-Mail Client 85 ~A all messages ~b EXPR messages which contain EXPR in the message body @@ -3960,6 +4278,7 @@ ~L EXPR message is either originated or received by EXPR ~l message is addressed to a known mailing list ~m [MIN]-[MAX] message in the range MIN to MAX *) + ~M multipart messages ~n [MIN]-[MAX] messages with a score in the range MIN to MAX *) ~N new messages ~O old messages @@ -3987,140 +4306,140 @@ alternates or any alias) Where EXPR, USER, ID, and SUBJECT are _r_e_g_u_l_a_r _e_x_p_r_e_s_s_i_o_n_s (section 4.1 , page - 44). Special attention has to be made when using regular expressions inside of + 49). Special attention has to be made when using regular expressions inside of patterns. Specifically, Mutt-ng's parser for these patterns will strip one level of backslash (\), which is normally used for quoting. If it is your intention to use a backslash in the regular expression, you will need to use two backslashes instead (\\). - The Mutt Next Generation E-Mail Client 80 + The Mutt Next Generation E-Mail Client 86 *) The forms <[MAX], >[MIN], [MIN]- and -[MAX] are allowed, too. - _6_._3 _C_o_n_f_i_g_u_r_a_t_i_o_n _C_o_m_m_a_n_d_s + _7_._3 _C_o_n_f_i_g_u_r_a_t_i_o_n _C_o_m_m_a_n_d_s The following are the commands understood by mutt. - +o _a_c_c_o_u_n_t_-_h_o_o_k (section 4.17 , page 63) _p_a_t_t_e_r_n _c_o_m_m_a_n_d + +o _a_c_c_o_u_n_t_-_h_o_o_k (section 4.17 , page 67) _p_a_t_t_e_r_n _c_o_m_m_a_n_d - +o _a_l_i_a_s (section 3.3 , page 23) _k_e_y _a_d_d_r_e_s_s [ , _a_d_d_r_e_s_s, ... ] + +o _a_l_i_a_s (section 3.4 , page 26) _k_e_y _a_d_d_r_e_s_s [ , _a_d_d_r_e_s_s, ... ] - +o _u_n_a_l_i_a_s (section 3.3 , page 23) [ * | _k_e_y ... ] + +o _u_n_a_l_i_a_s (section 3.4 , page 26) [ * | _k_e_y ... ] - +o _a_l_t_e_r_n_a_t_e_s (section 3.10 , page 30) _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] + +o _a_l_t_e_r_n_a_t_e_s (section 3.11 , page 34) _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] - +o _u_n_a_l_t_e_r_n_a_t_e_s (section 3.10 , page 30) [ * | _r_e_g_e_x_p ... ] + +o _u_n_a_l_t_e_r_n_a_t_e_s (section 3.11 , page 34) [ * | _r_e_g_e_x_p ... ] - +o _a_l_t_e_r_n_a_t_i_v_e___o_r_d_e_r (section 5.5 , page 76) _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ] + +o _a_l_t_e_r_n_a_t_i_v_e___o_r_d_e_r (section 5.5 , page 80) _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ] - +o _u_n_a_l_t_e_r_n_a_t_i_v_e___o_r_d_e_r (section 5.5 , page 76) _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ] + +o _u_n_a_l_t_e_r_n_a_t_i_v_e___o_r_d_e_r (section 5.5 , page 80) _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ] - +o _a_p_p_e_n_d_-_h_o_o_k (section 4.19.3 , page 66) _r_e_g_e_x_p _c_o_m_m_a_n_d + +o _a_p_p_e_n_d_-_h_o_o_k (section 4.19.3 , page 70) _r_e_g_e_x_p _c_o_m_m_a_n_d - +o _a_u_t_o___v_i_e_w (section 5.4 , page 75) _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ] + +o _a_u_t_o___v_i_e_w (section 5.4 , page 79) _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ] - +o _u_n_a_u_t_o___v_i_e_w (section 5.4 , page 75) _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ] + +o _u_n_a_u_t_o___v_i_e_w (section 5.4 , page 79) _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ] - +o _b_i_n_d (section 3.4 , page 24) _m_a_p _k_e_y _f_u_n_c_t_i_o_n + +o _b_i_n_d (section 3.5 , page 27) _m_a_p _k_e_y _f_u_n_c_t_i_o_n - +o _c_h_a_r_s_e_t_-_h_o_o_k (section 3.5 , page 26) _a_l_i_a_s _c_h_a_r_s_e_t + +o _c_h_a_r_s_e_t_-_h_o_o_k (section 3.6 , page 29) _a_l_i_a_s _c_h_a_r_s_e_t - +o _c_l_o_s_e_-_h_o_o_k (section 4.19.2 , page 65) _r_e_g_e_x_p _c_o_m_m_a_n_d + +o _c_l_o_s_e_-_h_o_o_k (section 4.19.2 , page 69) _r_e_g_e_x_p _c_o_m_m_a_n_d - +o _c_o_l_o_r (section 3.8 , page 27) _o_b_j_e_c_t _f_o_r_e_g_r_o_u_n_d _b_a_c_k_g_r_o_u_n_d [ _r_e_g_e_x_p ] + +o _c_o_l_o_r (section 3.9 , page 31) _o_b_j_e_c_t _f_o_r_e_g_r_o_u_n_d _b_a_c_k_g_r_o_u_n_d [ _r_e_g_e_x_p ] - +o _u_n_c_o_l_o_r (section 3.8 , page 27) _i_n_d_e_x _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] + +o _u_n_c_o_l_o_r (section 3.9 , page 31) _i_n_d_e_x _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] - +o _e_x_e_c (section 3.24 , page 37) _f_u_n_c_t_i_o_n [ _f_u_n_c_t_i_o_n ... ] + +o _e_x_e_c (section 3.25 , page 42) _f_u_n_c_t_i_o_n [ _f_u_n_c_t_i_o_n ... ] - +o _f_c_c_-_h_o_o_k (section 3.18 , page 35) _p_a_t_t_e_r_n _m_a_i_l_b_o_x + +o _f_c_c_-_h_o_o_k (section 3.19 , page 39) _p_a_t_t_e_r_n _m_a_i_l_b_o_x - +o _f_c_c_-_s_a_v_e_-_h_o_o_k (section 3.19 , page 36) _p_a_t_t_e_r_n _m_a_i_l_b_o_x + +o _f_c_c_-_s_a_v_e_-_h_o_o_k (section 3.20 , page 40) _p_a_t_t_e_r_n _m_a_i_l_b_o_x - +o _f_o_l_d_e_r_-_h_o_o_k (section 3.6 , page 26) _p_a_t_t_e_r_n _c_o_m_m_a_n_d + +o _f_o_l_d_e_r_-_h_o_o_k (section 3.7 , page 29) _p_a_t_t_e_r_n _c_o_m_m_a_n_d - +o _h_d_r___o_r_d_e_r (section 3.16 , page 35) _h_e_a_d_e_r [ _h_e_a_d_e_r ... ] + +o _h_d_r___o_r_d_e_r (section 3.17 , page 39) _h_e_a_d_e_r [ _h_e_a_d_e_r ... ] - +o _u_n_h_d_r___o_r_d_e_r (section 3.16 , page 35) _h_e_a_d_e_r [ _h_e_a_d_e_r ... ] + +o _u_n_h_d_r___o_r_d_e_r (section 3.17 , page 39) _h_e_a_d_e_r [ _h_e_a_d_e_r ... ] - +o _i_c_o_n_v_-_h_o_o_k (section 3.5 , page 26) _c_h_a_r_s_e_t _l_o_c_a_l_-_c_h_a_r_s_e_t + +o _i_c_o_n_v_-_h_o_o_k (section 3.6 , page 29) _c_h_a_r_s_e_t _l_o_c_a_l_-_c_h_a_r_s_e_t - +o _i_g_n_o_r_e (section 3.9 , page 30) _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] + +o _i_g_n_o_r_e (section 3.10 , page 33) _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] - The Mutt Next Generation E-Mail Client 81 + The Mutt Next Generation E-Mail Client 87 - +o _u_n_i_g_n_o_r_e (section 3.9 , page 30) _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] + +o _u_n_i_g_n_o_r_e (section 3.10 , page 33) _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] - +o _l_i_s_t_s (section 3.12 , page 32) _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] + +o _l_i_s_t_s (section 3.13 , page 36) _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] - +o _u_n_l_i_s_t_s (section 3.12 , page 32) _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] + +o _u_n_l_i_s_t_s (section 3.13 , page 36) _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] - +o _m_a_c_r_o (section 3.7 , page 27) _m_e_n_u _k_e_y _s_e_q_u_e_n_c_e [ _d_e_s_c_r_i_p_t_i_o_n ] + +o _m_a_c_r_o (section 3.8 , page 30) _m_e_n_u _k_e_y _s_e_q_u_e_n_c_e [ _d_e_s_c_r_i_p_t_i_o_n ] - +o _m_a_i_l_b_o_x_e_s (section 3.14 , page 33) _f_i_l_e_n_a_m_e [ _f_i_l_e_n_a_m_e ... ] + +o _m_a_i_l_b_o_x_e_s (section 3.15 , page 37) _f_i_l_e_n_a_m_e [ _f_i_l_e_n_a_m_e ... ] - +o _m_b_o_x_-_h_o_o_k (section 3.13 , page 33) _p_a_t_t_e_r_n _m_a_i_l_b_o_x + +o _m_b_o_x_-_h_o_o_k (section 3.14 , page 37) _p_a_t_t_e_r_n _m_a_i_l_b_o_x - +o _m_e_s_s_a_g_e_-_h_o_o_k (section 3.21 , page 37) _p_a_t_t_e_r_n _c_o_m_m_a_n_d + +o _m_e_s_s_a_g_e_-_h_o_o_k (section 3.22 , page 41) _p_a_t_t_e_r_n _c_o_m_m_a_n_d - +o _m_i_m_e___l_o_o_k_u_p (section 5.6 , page 76) _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ] + +o _m_i_m_e___l_o_o_k_u_p (section 5.6 , page 80) _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ] - +o _u_n_m_i_m_e___l_o_o_k_u_p (section 5.6 , page 76) _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ] + +o _u_n_m_i_m_e___l_o_o_k_u_p (section 5.6 , page 80) _m_i_m_e_t_y_p_e [ _m_i_m_e_t_y_p_e ... ] - +o _m_o_n_o (section 3.8 , page 27) _o_b_j_e_c_t _a_t_t_r_i_b_u_t_e [ _r_e_g_e_x_p ] + +o _m_o_n_o (section 3.9 , page 31) _o_b_j_e_c_t _a_t_t_r_i_b_u_t_e [ _r_e_g_e_x_p ] - +o _u_n_m_o_n_o (section 3.8 , page 27) _i_n_d_e_x _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] + +o _u_n_m_o_n_o (section 3.9 , page 31) _i_n_d_e_x _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] - +o _m_y___h_d_r (section 3.15 , page 34) _s_t_r_i_n_g + +o _m_y___h_d_r (section 3.16 , page 38) _s_t_r_i_n_g - +o _u_n_m_y___h_d_r (section 3.15 , page 34) _f_i_e_l_d [ _f_i_e_l_d ... ] + +o _u_n_m_y___h_d_r (section 3.16 , page 38) _f_i_e_l_d [ _f_i_e_l_d ... ] - +o _o_p_e_n_-_h_o_o_k (section 4.19.1 , page 65) _r_e_g_e_x_p _c_o_m_m_a_n_d + +o _o_p_e_n_-_h_o_o_k (section 4.19.1 , page 69) _r_e_g_e_x_p _c_o_m_m_a_n_d - +o _c_r_y_p_t_-_h_o_o_k (section 3.22 , page 37) _p_a_t_t_e_r_n _k_e_y_-_i_d + +o _c_r_y_p_t_-_h_o_o_k (section 3.23 , page 41) _p_a_t_t_e_r_n _k_e_y_-_i_d - +o _p_u_s_h (section 3.23 , page 37) _s_t_r_i_n_g + +o _p_u_s_h (section 3.24 , page 41) _s_t_r_i_n_g - +o _r_e_s_e_t (section 3.27 , page 41) _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ] + +o _r_e_s_e_t (section 3.28 , page 45) _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ] - +o _s_a_v_e_-_h_o_o_k (section 3.17 , page 35) _r_e_g_e_x_p _f_i_l_e_n_a_m_e + +o _s_a_v_e_-_h_o_o_k (section 3.18 , page 39) _r_e_g_e_x_p _f_i_l_e_n_a_m_e - +o _s_c_o_r_e (section 3.25 , page 38) _p_a_t_t_e_r_n _v_a_l_u_e + +o _s_c_o_r_e (section 3.26 , page 42) _p_a_t_t_e_r_n _v_a_l_u_e - +o _u_n_s_c_o_r_e (section 3.25 , page 38) _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] + +o _u_n_s_c_o_r_e (section 3.26 , page 42) _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] - +o _s_e_n_d_-_h_o_o_k (section 3.20 , page 36) _r_e_g_e_x_p _c_o_m_m_a_n_d + +o _s_e_n_d_-_h_o_o_k (section 3.21 , page 40) _r_e_g_e_x_p _c_o_m_m_a_n_d +o _r_e_p_l_y_-_h_o_o_k (section , page ) _r_e_g_e_x_p _c_o_m_m_a_n_d - +o _s_e_t (section 3.27 , page 41) [no|inv]_v_a_r_i_a_b_l_e[=_v_a_l_u_e] [ _v_a_r_i_a_b_l_e ... ] + +o _s_e_t (section 3.28 , page 45) [no|inv]_v_a_r_i_a_b_l_e[=_v_a_l_u_e] [ _v_a_r_i_a_b_l_e ... ] - +o _u_n_s_e_t (section 3.27 , page 41) _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ] + +o _u_n_s_e_t (section 3.28 , page 45) _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ] - +o _s_o_u_r_c_e (section 3.28 , page 42) _f_i_l_e_n_a_m_e + +o _s_o_u_r_c_e (section 3.29 , page 46) _f_i_l_e_n_a_m_e - +o _s_p_a_m (section 3.26 , page 39) _p_a_t_t_e_r_n _f_o_r_m_a_t + +o _s_p_a_m (section 3.27 , page 43) _p_a_t_t_e_r_n _f_o_r_m_a_t - +o _n_o_s_p_a_m (section 3.26 , page 39) _p_a_t_t_e_r_n + +o _n_o_s_p_a_m (section 3.27 , page 43) _p_a_t_t_e_r_n - The Mutt Next Generation E-Mail Client 82 + The Mutt Next Generation E-Mail Client 88 - +o _s_u_b_s_c_r_i_b_e (section 3.12 , page 32) _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] + +o _s_u_b_s_c_r_i_b_e (section 3.13 , page 36) _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] - +o _u_n_s_u_b_s_c_r_i_b_e (section 3.12 , page 32) _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] + +o _u_n_s_u_b_s_c_r_i_b_e (section 3.13 , page 36) _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] - +o _t_o_g_g_l_e (section 3.27 , page 41) _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ] + +o _t_o_g_g_l_e (section 3.28 , page 45) _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ] - +o _u_n_h_o_o_k (section 3.29 , page 42) _h_o_o_k_-_t_y_p_e + +o _u_n_h_o_o_k (section 3.30 , page 46) _h_o_o_k_-_t_y_p_e - _6_._4 _C_o_n_f_i_g_u_r_a_t_i_o_n _v_a_r_i_a_b_l_e_s + _7_._4 _C_o_n_f_i_g_u_r_a_t_i_o_n _v_a_r_i_a_b_l_e_s The following list contains all variables which, in the process of providing more consistency, have been renamed and are partially even removed already. The left column contains the old synonym variables, the right column the full/new name: - The Mutt Next Generation E-Mail Client 83 + The Mutt Next Generation E-Mail Client 89 edit_hdrs edit_headers forw_decode forward_decode @@ -4168,20 +4487,38 @@ A complete list of current variables follows. - _6_._4_._1 _a_b_o_r_t___n_o_s_u_b_j_e_c_t + _7_._4_._1 _a_b_o_r_t___n_o_a_t_t_a_c_h Type: quadoption - Default: ask-yes + Default: no - If set to _y_e_s, when composing messages and no subject is given at the subject + This variable specifies whether to abort sending if no attachment was made but - The Mutt Next Generation E-Mail Client 84 + The Mutt Next Generation E-Mail Client 90 + + the content references them, i.e. the content matches the regular expression + given in _$_a_t_t_a_c_h___r_e_m_i_n_d___r_e_g_e_x_p (section 7.4.15 , page 93). If a match was + found and this variable is set to _y_e_s, message sending will be aborted but the + mail will be send nevertheless if set to _n_o. + + This variable and _$_a_t_t_a_c_h___r_e_m_i_n_d___r_e_g_e_x_p (section 7.4.15 , page 93) are + intended to remind the user to attach files if the message's text references + them. + + See also the _$_a_t_t_a_c_h___r_e_m_i_n_d___r_e_g_e_x_p (section 7.4.15 , page 93) variable. + + _7_._4_._2 _a_b_o_r_t___n_o_s_u_b_j_e_c_t + + Type: quadoption + Default: ask-yes + + If set to _y_e_s, when composing messages and no subject is given at the subject prompt, composition will be aborted. If set to _n_o, composing messages with no subject given at the subject prompt will never be aborted. - _6_._4_._2 _a_b_o_r_t___u_n_m_o_d_i_f_i_e_d + _7_._4_._3 _a_b_o_r_t___u_n_m_o_d_i_f_i_e_d Type: quadoption @@ -4191,7 +4528,16 @@ body if no changes are made to the file (this check only happens after the _f_i_r_s_t edit of the file). When set to _n_o, composition will never be aborted. - _6_._4_._3 _a_l_i_a_s___f_i_l_e + _7_._4_._4 _a_g_e_n_t___s_t_r_i_n_g + + Type: boolean + + Default: yes + + When _s_e_t, Mutt-ng will add a ``User-Agent:'' header to outgoing messages, indi- + cating which version of Mutt-ng was used for composing them. + + _7_._4_._5 _a_l_i_a_s___f_i_l_e Type: path @@ -4201,9 +4547,11 @@ tion 2.5.4 , page 11)'' function. NNoottee:: Mutt-ng will not automatically source this file; you must explicitly use - the ``_s_o_u_r_c_e (section 3.28 , page 42)'' command for it to be executed. + the ``_s_o_u_r_c_e (section 3.29 , page 46)'' command for it to be executed. - _6_._4_._4 _a_l_i_a_s___f_o_r_m_a_t + _7_._4_._6 _a_l_i_a_s___f_o_r_m_a_t + + The Mutt Next Generation E-Mail Client 91 Type: string @@ -4227,18 +4575,16 @@ %t character which indicates if the alias is tagged for inclusion - _6_._4_._5 _a_l_l_o_w___8_b_i_t + _7_._4_._7 _a_l_l_o_w___8_b_i_t Type: boolean Default: yes - The Mutt Next Generation E-Mail Client 85 - Controls whether 8-bit data is converted to 7-bit using either quoted-printable or base64 encoding when sending mail. - _6_._4_._6 _a_l_l_o_w___a_n_s_i + _7_._4_._8 _a_l_l_o_w___a_n_s_i Type: boolean @@ -4251,7 +4597,7 @@ sage could include a line like ``[-- PGP output follows ...' and give it the same color as your attachment color. - _6_._4_._7 _a_r_r_o_w___c_u_r_s_o_r + _7_._4_._9 _a_r_r_o_w___c_u_r_s_o_r Type: boolean @@ -4262,7 +4608,9 @@ will make response faster because there is less that has to be redrawn on the screen when moving to the next or previous entries in the menu. - _6_._4_._8 _a_s_c_i_i___c_h_a_r_s + The Mutt Next Generation E-Mail Client 92 + + _7_._4_._1_0 _a_s_c_i_i___c_h_a_r_s Type: boolean @@ -4271,7 +4619,7 @@ If _s_e_t, Mutt-ng will use plain ASCII characters when displaying thread and attachment trees, instead of the default ACS characters. - _6_._4_._9 _a_s_k_b_c_c + _7_._4_._1_1 _a_s_k_b_c_c Type: boolean @@ -4280,7 +4628,7 @@ If _s_e_t, Mutt-ng will prompt you for blind-carbon-copy (Bcc) recipients before editing an outgoing message. - _6_._4_._1_0 _a_s_k_c_c + _7_._4_._1_2 _a_s_k_c_c Type: boolean @@ -4289,9 +4637,7 @@ If _s_e_t, Mutt-ng will prompt you for carbon-copy (Cc) recipients before editing the body of an outgoing message. - The Mutt Next Generation E-Mail Client 86 - - _6_._4_._1_1 _a_s_s_u_m_e_d___c_h_a_r_s_e_t + _7_._4_._1_3 _a_s_s_u_m_e_d___c_h_a_r_s_e_t Type: string @@ -4308,9 +4654,9 @@ set assumed_charset='iso-2022-jp:euc-jp:shift_jis:utf-8' However, only the first content is valid for the message body. This variable - is valid only if _$_s_t_r_i_c_t___m_i_m_e (section 6.4.311 , page 159) is unset. + is valid only if _$_s_t_r_i_c_t___m_i_m_e (section 7.4.327 , page 170) is unset. - _6_._4_._1_2 _a_t_t_a_c_h___f_o_r_m_a_t + _7_._4_._1_4 _a_t_t_a_c_h___f_o_r_m_a_t Type: string @@ -4319,6 +4665,8 @@ This variable describes the format of the ``attachment'' menu. The following printf(3)-style sequences are understood: + The Mutt Next Generation E-Mail Client 93 + %C charset @@ -4346,8 +4694,6 @@ %M MIME subtype - The Mutt Next Generation E-Mail Client 87 - %n attachment number @@ -4369,7 +4715,22 @@ %|X pad to the end of the line with character 'X' - _6_._4_._1_3 _a_t_t_a_c_h___s_e_p + _7_._4_._1_5 _a_t_t_a_c_h___r_e_m_i_n_d___r_e_g_e_x_p + + Type: regular expression + + Default: 'attach' + + The Mutt Next Generation E-Mail Client 94 + + If this variable is non-empty, muttng will scan a message's contents before + sending for this regular expression. If it is found, it will ask for what to do + depending on the setting of _$_a_b_o_r_t___n_o_a_t_t_a_c_h (section 7.4.1 , page 89). + + This variable and _$_a_b_o_r_t___n_o_a_t_t_a_c_h (section 7.4.1 , page 89) are intended to + remind the user to attach files if the message's text references them. + + _7_._4_._1_6 _a_t_t_a_c_h___s_e_p Type: string @@ -4378,7 +4739,7 @@ The separator to add between attachments when operating (saving, printing, pip- ing, etc) on a list of tagged attachments. - _6_._4_._1_4 _a_t_t_a_c_h___s_p_l_i_t + _7_._4_._1_7 _a_t_t_a_c_h___s_p_l_i_t Type: boolean @@ -4386,11 +4747,11 @@ If this variable is _u_n_s_e_t, when operating (saving, printing, piping, etc) on a list of tagged attachments, Mutt-ng will concatenate the attachments and will - operate on them as a single attachment. The ``_$_a_t_t_a_c_h___s_e_p (section 6.4.13 , - page 86)'' separator is added after each attachment. When _s_e_t, Mutt-ng will + operate on them as a single attachment. The ``_$_a_t_t_a_c_h___s_e_p (section 7.4.16 , + page 94)'' separator is added after each attachment. When _s_e_t, Mutt-ng will operate on the attachments one by one. - _6_._4_._1_5 _a_t_t_r_i_b_u_t_i_o_n + _7_._4_._1_8 _a_t_t_r_i_b_u_t_i_o_n Type: string @@ -4398,11 +4759,9 @@ This is the string that will precede a message which has been included in a reply. For a full listing of defined printf(3)-like sequences see the section - on ``_$_i_n_d_e_x___f_o_r_m_a_t (section 6.4.110 , page 108)''. - - _6_._4_._1_6 _a_u_t_o___t_a_g + on ``_$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.116 , page 116)''. - The Mutt Next Generation E-Mail Client 88 + _7_._4_._1_9 _a_u_t_o___t_a_g Type: boolean @@ -4413,20 +4772,22 @@ ``tag-prefix'' function (default: ';') to make the next function apply to all tagged messages. - _6_._4_._1_7 _a_u_t_o_e_d_i_t + _7_._4_._2_0 _a_u_t_o_e_d_i_t Type: boolean Default: no - When _s_e_t along with ``_$_e_d_i_t___h_e_a_d_e_r_s (section 6.4.54 , page 95)'', Mutt-ng will - skip the initial send-menu and allow you to immediately begin editing the body - of your message. The send-menu may still be accessed once you have finished - editing the body of your message. + The Mutt Next Generation E-Mail Client 95 + + When _s_e_t along with ``_$_e_d_i_t___h_e_a_d_e_r_s (section 7.4.59 , page 103)'', Mutt-ng + will skip the initial send-menu and allow you to immediately begin editing the + body of your message. The send-menu may still be accessed once you have fin- + ished editing the body of your message. - Also see ``_$_f_a_s_t___r_e_p_l_y (section 6.4.60 , page 96)''. + Also see ``_$_f_a_s_t___r_e_p_l_y (section 7.4.66 , page 105)''. - _6_._4_._1_8 _b_e_e_p + _7_._4_._2_1 _b_e_e_p Type: boolean @@ -4434,7 +4795,7 @@ When this variable is _s_e_t, Mutt-ng will beep when an error occurs. - _6_._4_._1_9 _b_e_e_p___n_e_w + _7_._4_._2_2 _b_e_e_p___n_e_w Type: boolean @@ -4442,9 +4803,9 @@ When this variable is _s_e_t, Mutt-ng will beep whenever it prints a message noti- fying you of new mail. This is independent of the setting of the ``_$_b_e_e_p (sec- - tion 6.4.18 , page 87)'' variable. + tion 7.4.21 , page 95)'' variable. - _6_._4_._2_0 _b_o_u_n_c_e + _7_._4_._2_3 _b_o_u_n_c_e Type: quadoption @@ -4455,18 +4816,16 @@ _n_o is not generally useful, and thus not recommended, because you are unable to bounce messages. - _6_._4_._2_1 _b_o_u_n_c_e___d_e_l_i_v_e_r_e_d + _7_._4_._2_4 _b_o_u_n_c_e___d_e_l_i_v_e_r_e_d Type: boolean - The Mutt Next Generation E-Mail Client 89 - Default: yes When this variable is _s_e_t, Mutt-ng will include Delivered-To: header fields when bouncing messages. Postfix users may wish to _u_n_s_e_t this variable. - _6_._4_._2_2 _b_r_a_i_l_l_e___f_r_i_e_n_d_l_y + _7_._4_._2_5 _b_r_a_i_l_l_e___f_r_i_e_n_d_l_y Type: boolean @@ -4475,10 +4834,13 @@ When this variable is set, mutt will place the cursor at the beginning of the current line in menus, even when the arrow_cursor variable is unset, making it easier for blind persons using Braille displays to follow these menus. The + + The Mutt Next Generation E-Mail Client 96 + option is disabled by default because many visual terminals don't permit making the cursor invisible. - _6_._4_._2_3 _c_e_r_t_i_f_i_c_a_t_e___f_i_l_e + _7_._4_._2_6 _c_e_r_t_i_f_i_c_a_t_e___f_i_l_e Type: path @@ -4497,7 +4859,7 @@ Example: set certificate_file=~/.muttng/certificates - _6_._4_._2_4 _c_h_a_r_s_e_t + _7_._4_._2_7 _c_h_a_r_s_e_t Type: string @@ -4505,7 +4867,7 @@ Character set your terminal uses to display and enter textual data. - _6_._4_._2_5 _c_h_e_c_k___n_e_w + _7_._4_._2_8 _c_h_e_c_k___n_e_w Type: boolean @@ -4515,14 +4877,11 @@ When _s_e_t, Mutt-ng will check for new mail delivered while the mailbox is open. Especially with MH mailboxes, this operation can take quite some time since it - - The Mutt Next Generation E-Mail Client 90 - involves scanning the directory and checking each file to see if it has already been looked at. If it's _u_n_s_e_t, no check for new mail is performed while the mailbox is open. - _6_._4_._2_6 _c_o_l_l_a_p_s_e___u_n_r_e_a_d + _7_._4_._2_9 _c_o_l_l_a_p_s_e___u_n_r_e_a_d Type: boolean @@ -4531,14 +4890,16 @@ When _u_n_s_e_t, Mutt-ng will not collapse a thread if it contains any unread mes- sages. - _6_._4_._2_7 _c_o_m_p_o_s_e___f_o_r_m_a_t + The Mutt Next Generation E-Mail Client 97 + + _7_._4_._3_0 _c_o_m_p_o_s_e___f_o_r_m_a_t Type: string Default: '-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-' Controls the format of the status line displayed in the ``compose'' menu. This - string is similar to ``_$_s_t_a_t_u_s___f_o_r_m_a_t (section 6.4.308 , page 157)'', but has + string is similar to ``_$_s_t_a_t_u_s___f_o_r_m_a_t (section 7.4.324 , page 167)'', but has its own set of printf(3)-like sequences: %a @@ -4553,11 +4914,11 @@ %v Mutt-ng version string - See the text describing the ``_$_s_t_a_t_u_s___f_o_r_m_a_t (section 6.4.308 , page 157)'' - option for more information on how to set ``_$_c_o_m_p_o_s_e___f_o_r_m_a_t (section 6.4.27 , - page 89)''. + See the text describing the ``_$_s_t_a_t_u_s___f_o_r_m_a_t (section 7.4.324 , page 167)'' + option for more information on how to set ``_$_c_o_m_p_o_s_e___f_o_r_m_a_t (section 7.4.30 , + page 97)''. - _6_._4_._2_8 _c_o_n_f_i_g___c_h_a_r_s_e_t + _7_._4_._3_1 _c_o_n_f_i_g___c_h_a_r_s_e_t Type: string @@ -4565,19 +4926,16 @@ When defined, Mutt-ng will recode commands in rc files from this encoding. - _6_._4_._2_9 _c_o_n_f_i_r_m_a_p_p_e_n_d + _7_._4_._3_2 _c_o_n_f_i_r_m_a_p_p_e_n_d Type: boolean Default: yes When _s_e_t, Mutt-ng will prompt for confirmation when appending messages to an - - The Mutt Next Generation E-Mail Client 91 - existing mailbox. - _6_._4_._3_0 _c_o_n_f_i_r_m_c_r_e_a_t_e + _7_._4_._3_3 _c_o_n_f_i_r_m_c_r_e_a_t_e Type: boolean @@ -4586,7 +4944,9 @@ When _s_e_t, Mutt-ng will prompt for confirmation when saving messages to a mail- box which does not yet exist before creating it. - _6_._4_._3_1 _c_o_n_n_e_c_t___t_i_m_e_o_u_t + _7_._4_._3_4 _c_o_n_n_e_c_t___t_i_m_e_o_u_t + + The Mutt Next Generation E-Mail Client 98 Type: number @@ -4596,7 +4956,7 @@ many seconds if the connection is not able to be established. A negative value causes Mutt-ng to wait indefinitely for the connection to succeed. - _6_._4_._3_2 _c_o_n_t_e_n_t___t_y_p_e + _7_._4_._3_5 _c_o_n_t_e_n_t___t_y_p_e Type: string @@ -4605,18 +4965,18 @@ Sets the default Content-Type: header field for the body of newly composed mes- sages. - _6_._4_._3_3 _c_o_p_y + _7_._4_._3_6 _c_o_p_y Type: quadoption Default: yes This variable controls whether or not copies of your outgoing messages will be - saved for later references. Also see ``_$_r_e_c_o_r_d (section 6.4.230 , page - 138)'', ``_$_s_a_v_e___n_a_m_e (section 6.4.241 , page 141)'', ``_$_f_o_r_c_e___n_a_m_e (section - 6.4.68 , page 98)'' and ``_f_c_c_-_h_o_o_k (section 3.18 , page 35)''. + saved for later references. Also see ``_$_r_e_c_o_r_d (section 7.4.246 , page + 148)'', ``_$_s_a_v_e___n_a_m_e (section 7.4.257 , page 151)'', ``_$_f_o_r_c_e___n_a_m_e (section + 7.4.74 , page 107)'' and ``_f_c_c_-_h_o_o_k (section 3.19 , page 39)''. - _6_._4_._3_4 _c_r_y_p_t___a_u_t_o_e_n_c_r_y_p_t + _7_._4_._3_7 _c_r_y_p_t___a_u_t_o_e_n_c_r_y_p_t Type: boolean @@ -4626,13 +4986,11 @@ going messages. This is probably only useful in connection to the _s_e_n_d_-_h_o_o_k command. It can be overridden by use of the _p_g_p_-_m_e_n_u, when encryption is not required or signing is requested as well. If ``_$_s_m_i_m_e___i_s___d_e_f_a_u_l_t (section - 6.4.277 , page 149)'' is _s_e_t, then OpenSSL is used instead to create S/MIME + 7.4.293 , page 159)'' is _s_e_t, then OpenSSL is used instead to create S/MIME messages and settings can be overridden by use of the _s_m_i_m_e_-_m_e_n_u. (Crypto only) - The Mutt Next Generation E-Mail Client 92 - - _6_._4_._3_5 _c_r_y_p_t___a_u_t_o_p_g_p + _7_._4_._3_8 _c_r_y_p_t___a_u_t_o_p_g_p Type: boolean @@ -4640,11 +4998,13 @@ This variable controls whether or not Mutt-ng may automatically enable PGP encryption/signing for messages. See also ``_$_c_r_y_p_t___a_u_t_o_e_n_c_r_y_p_t (section - 6.4.34 , page 90)'', ``_$_c_r_y_p_t___r_e_p_l_y_e_n_c_r_y_p_t (section 6.4.38 , page 91)'', - ``_$_c_r_y_p_t___a_u_t_o_s_i_g_n (section 6.4.36 , page 91)'', ``_$_c_r_y_p_t___r_e_p_l_y_s_i_g_n (section - 6.4.39 , page 91)'' and ``_$_s_m_i_m_e___i_s___d_e_f_a_u_l_t (section 6.4.277 , page 149)''. + 7.4.37 , page 98)'', ``_$_c_r_y_p_t___r_e_p_l_y_e_n_c_r_y_p_t (section 7.4.41 , page 99)'', + ``_$_c_r_y_p_t___a_u_t_o_s_i_g_n (section 7.4.39 , page 98)'', ``_$_c_r_y_p_t___r_e_p_l_y_s_i_g_n (section + 7.4.42 , page 99)'' and ``_$_s_m_i_m_e___i_s___d_e_f_a_u_l_t (section 7.4.293 , page 159)''. + + The Mutt Next Generation E-Mail Client 99 - _6_._4_._3_6 _c_r_y_p_t___a_u_t_o_s_i_g_n + _7_._4_._3_9 _c_r_y_p_t___a_u_t_o_s_i_g_n Type: boolean @@ -4653,11 +5013,11 @@ Setting this variable will cause Mutt-ng to always attempt to cryptographically sign outgoing messages. This can be overridden by use of the _p_g_p_-_m_e_n_u, when signing is not required or encryption is requested as well. If - ``_$_s_m_i_m_e___i_s___d_e_f_a_u_l_t (section 6.4.277 , page 149)'' is _s_e_t, then OpenSSL is + ``_$_s_m_i_m_e___i_s___d_e_f_a_u_l_t (section 7.4.293 , page 159)'' is _s_e_t, then OpenSSL is used instead to create S/MIME messages and settings can be overridden by use of the _s_m_i_m_e_-_m_e_n_u. (Crypto only) - _6_._4_._3_7 _c_r_y_p_t___a_u_t_o_s_m_i_m_e + _7_._4_._4_0 _c_r_y_p_t___a_u_t_o_s_m_i_m_e Type: boolean @@ -4665,11 +5025,11 @@ This variable controls whether or not Mutt-ng may automatically enable S/MIME encryption/signing for messages. See also ``_$_c_r_y_p_t___a_u_t_o_e_n_c_r_y_p_t (section - 6.4.34 , page 90)'', ``_$_c_r_y_p_t___r_e_p_l_y_e_n_c_r_y_p_t (section 6.4.38 , page 91)'', - ``_$_c_r_y_p_t___a_u_t_o_s_i_g_n (section 6.4.36 , page 91)'', ``_$_c_r_y_p_t___r_e_p_l_y_s_i_g_n (section - 6.4.39 , page 91)'' and ``_$_s_m_i_m_e___i_s___d_e_f_a_u_l_t (section 6.4.277 , page 149)''. + 7.4.37 , page 98)'', ``_$_c_r_y_p_t___r_e_p_l_y_e_n_c_r_y_p_t (section 7.4.41 , page 99)'', + ``_$_c_r_y_p_t___a_u_t_o_s_i_g_n (section 7.4.39 , page 98)'', ``_$_c_r_y_p_t___r_e_p_l_y_s_i_g_n (section + 7.4.42 , page 99)'' and ``_$_s_m_i_m_e___i_s___d_e_f_a_u_l_t (section 7.4.293 , page 159)''. - _6_._4_._3_8 _c_r_y_p_t___r_e_p_l_y_e_n_c_r_y_p_t + _7_._4_._4_1 _c_r_y_p_t___r_e_p_l_y_e_n_c_r_y_p_t Type: boolean @@ -4678,7 +5038,7 @@ If _s_e_t, automatically PGP or OpenSSL encrypt replies to messages which are encrypted. (Crypto only) - _6_._4_._3_9 _c_r_y_p_t___r_e_p_l_y_s_i_g_n + _7_._4_._4_2 _c_r_y_p_t___r_e_p_l_y_s_i_g_n Type: boolean @@ -4686,12 +5046,10 @@ If _s_e_t, automatically PGP or OpenSSL sign replies to messages which are signed. - The Mutt Next Generation E-Mail Client 93 - NNoottee:: this does not work on messages that are encrypted aanndd signed! (Crypto only) - _6_._4_._4_0 _c_r_y_p_t___r_e_p_l_y_s_i_g_n_e_n_c_r_y_p_t_e_d + _7_._4_._4_3 _c_r_y_p_t___r_e_p_l_y_s_i_g_n_e_n_c_r_y_p_t_e_d Type: boolean @@ -4699,12 +5057,15 @@ If _s_e_t, automatically PGP or OpenSSL sign replies to messages which are encrypted. This makes sense in combination with ``_$_c_r_y_p_t___r_e_p_l_y_e_n_c_r_y_p_t (section - 6.4.38 , page 91)'', because it allows you to sign all messages which are + 7.4.41 , page 99)'', because it allows you to sign all messages which are + + The Mutt Next Generation E-Mail Client 100 + automatically encrypted. This works around the problem noted in - ``_$_c_r_y_p_t___r_e_p_l_y_s_i_g_n (section 6.4.39 , page 91)'', that Mutt-ng is not able to + ``_$_c_r_y_p_t___r_e_p_l_y_s_i_g_n (section 7.4.42 , page 99)'', that Mutt-ng is not able to find out whether an encrypted message is also signed. (Crypto only) - _6_._4_._4_1 _c_r_y_p_t___t_i_m_e_s_t_a_m_p + _7_._4_._4_4 _c_r_y_p_t___t_i_m_e_s_t_a_m_p Type: boolean @@ -4715,7 +5076,7 @@ ors to mark these lines, and rely on these, you may _u_n_s_e_t this setting. (Crypto only) - _6_._4_._4_2 _c_r_y_p_t___u_s_e___g_p_g_m_e + _7_._4_._4_5 _c_r_y_p_t___u_s_e___g_p_g_m_e Type: boolean @@ -4728,7 +5089,7 @@ NNoottee: You need to use this option in your .muttngrc configuration file as it won't have any effect when used interactively. - _6_._4_._4_3 _c_r_y_p_t___v_e_r_i_f_y___s_i_g + _7_._4_._4_6 _c_r_y_p_t___v_e_r_i_f_y___s_i_g Type: quadoption @@ -4738,25 +5099,40 @@ whether or not to verify the signature. If ``_n_o'', never attempt to verify cryptographic signatures. (Crypto only) - _6_._4_._4_4 _d_a_t_e___f_o_r_m_a_t + _7_._4_._4_7 _d_a_t_e___f_o_r_m_a_t Type: string - The Mutt Next Generation E-Mail Client 94 - Default: '!%a, %b %d, %Y at %I:%M:%S%p %Z' This variable controls the format of the date printed by the ``%d'' sequence in - ``_$_i_n_d_e_x___f_o_r_m_a_t (section 6.4.110 , page 108)''. This is passed to strftime(3) + ``_$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.116 , page 116)''. This is passed to strftime(3) to process the date. Unless the first character in the string is a bang (``!''), the month and week day names are expanded according to the locale specified in the variable - ``_$_l_o_c_a_l_e (section 6.4.114 , page 111)''. If the first character in the string + ``_$_l_o_c_a_l_e (section 7.4.120 , page 120)''. If the first character in the string is a bang, the bang is discarded, and the month and week day names in the rest of the string are expanded in the _C locale (that is in US English). - _6_._4_._4_5 _d_e_f_a_u_l_t___h_o_o_k + The Mutt Next Generation E-Mail Client 101 + + _7_._4_._4_8 _d_e_b_u_g___l_e_v_e_l + + Type: number + + Default: 0 + + Availability: debug + + This variable specifies the current debug level and may be used to increase or + decrease the verbosity level during runtime. It overrides the level given with + the -d command line option. + + Currently, this number must be >= 0 and <= 5 and muttng must be started with -d + to enable debugging at all; enabling at runtime is not possible. + + _7_._4_._4_9 _d_e_f_a_u_l_t___h_o_o_k Type: string @@ -4771,7 +5147,7 @@ address matches ``alternates'') and is to or cc'ed to a user matching the given regular expression. - _6_._4_._4_6 _d_e_l_e_t_e + _7_._4_._5_0 _d_e_l_e_t_e Type: quadoption @@ -4782,7 +5158,23 @@ be purged without prompting. If set to _n_o, messages marked for deletion will be kept in the mailbox. - _6_._4_._4_7 _d_e_l_e_t_e___u_n_t_a_g + _7_._4_._5_1 _d_e_l_e_t_e___s_p_a_c_e + + Type: boolean + + Default: no + + When sending messages with format=flowed by _s_e_t_t_i_n_g the _$_t_e_x_t___f_l_o_w_e_d (section + 7.4.333 , page 171) variable, this variable specifies whether to also set the + DelSp parameter to yes. If this is _u_n_s_e_t, no additional parameter will be send + as a value of no already is the default behavior. + + NNoottee:: this variable only has an effect on _o_u_t_g_o_i_n_g messages (if _$_t_e_x_t___f_l_o_w_e_d + (section 7.4.333 , page 171) is _s_e_t) but not on incomming. + + The Mutt Next Generation E-Mail Client 102 + + _7_._4_._5_2 _d_e_l_e_t_e___u_n_t_a_g Type: boolean @@ -4792,39 +5184,37 @@ tion. This applies when you either explicitly delete a message, or when you save it to another folder. - _6_._4_._4_8 _d_i_g_e_s_t___c_o_l_l_a_p_s_e + _7_._4_._5_3 _d_i_g_e_s_t___c_o_l_l_a_p_s_e Type: boolean Default: yes - The Mutt Next Generation E-Mail Client 95 - If this option is _s_e_t, Mutt-ng's received-attachments menu will not show the subparts of individual messages in a multipart/digest. To see these subparts, press 'v' on that menu. - _6_._4_._4_9 _d_i_s_p_l_a_y___f_i_l_t_e_r + _7_._4_._5_4 _d_i_s_p_l_a_y___f_i_l_t_e_r Type: path Default: '' When _s_e_t, specifies a command used to filter messages. When a message is - viewed it is passed as standard input to _$_d_i_s_p_l_a_y___f_i_l_t_e_r (section 6.4.49 , - page 94), and the filtered message is read from the standard output. + viewed it is passed as standard input to _$_d_i_s_p_l_a_y___f_i_l_t_e_r (section 7.4.54 , + page 102), and the filtered message is read from the standard output. - _6_._4_._5_0 _d_o_t_l_o_c_k___p_r_o_g_r_a_m + _7_._4_._5_5 _d_o_t_l_o_c_k___p_r_o_g_r_a_m Type: path - Default: '/opt/freebsd4/mutt-ng/bin/muttng_dotlock' + Default: '$muttng_bindir/muttng_dotlock' Availability: Standalone and Dotlock Contains the path of the muttng_dotlock(1) binary to be used by Mutt-ng. - _6_._4_._5_1 _d_s_n___n_o_t_i_f_y + _7_._4_._5_6 _d_s_n___n_o_t_i_f_y Type: string @@ -4839,9 +5229,11 @@ transmission failure, _d_e_l_a_y, to be notified of message delays, _s_u_c_c_e_s_s, to be notified of successful transmission. + The Mutt Next Generation E-Mail Client 103 + Example: set dsn_notify='failure,delay' - _6_._4_._5_2 _d_s_n___r_e_t_u_r_n + _7_._4_._5_7 _d_s_n___r_e_t_u_r_n Type: string @@ -4854,11 +5246,9 @@ It may be set to either _h_d_r_s to return just the message header, or _f_u_l_l to return the full message. - The Mutt Next Generation E-Mail Client 96 - Example: set dsn_return=hdrs - _6_._4_._5_3 _d_u_p_l_i_c_a_t_e___t_h_r_e_a_d_s + _7_._4_._5_8 _d_u_p_l_i_c_a_t_e___t_h_r_e_a_d_s Type: boolean @@ -4869,7 +5259,7 @@ indicate that it thinks they are duplicates of each other with an equals sign in the thread diagram. - _6_._4_._5_4 _e_d_i_t___h_e_a_d_e_r_s + _7_._4_._5_9 _e_d_i_t___h_e_a_d_e_r_s Type: boolean @@ -4878,7 +5268,10 @@ This option allows you to edit the header of your outgoing messages along with the body of your message. - _6_._4_._5_5 _e_d_i_t_o_r + Which empty header fields to show is controlled by the _$_e_d_i_t_o_r___h_e_a_d_e_r_s (section + 7.4.61 , page 103) option. + + _7_._4_._6_0 _e_d_i_t_o_r Type: path @@ -4888,7 +5281,24 @@ value of the $VISUAL, or $EDITOR, environment variable, or to the string 'vi' if neither of those are set. - _6_._4_._5_6 _e_n_c_o_d_e___f_r_o_m + _7_._4_._6_1 _e_d_i_t_o_r___h_e_a_d_e_r_s + + Type: string + + The Mutt Next Generation E-Mail Client 104 + + Default: 'From: To: Cc: Bcc: Subject: Reply-To: Newsgroups: Followup-To: X-Com- + ment-To:' + + If _$_e_d_i_t___h_e_a_d_e_r_s (section 7.4.59 , page 103) is _s_e_t, this space-separated list + specifies which _n_o_n_-_e_m_p_t_y header fields to edit in addition to user-defined + headers. + + Note: if _$_e_d_i_t___h_e_a_d_e_r_s (section 7.4.59 , page 103) had to be turned on by + force because _$_s_t_r_i_c_t___m_a_i_l_t_o (section 7.4.326 , page 169) is _u_n_s_e_t, this + option has no effect. + + _7_._4_._6_2 _e_n_c_o_d_e___f_r_o_m Type: boolean @@ -4899,7 +5309,12 @@ to avoid the tampering certain mail delivery and transport agents tend to do with messages. - _6_._4_._5_7 _e_n_t_r_o_p_y___f_i_l_e + NNoottee:: as mutt-ng currently violates RfC3676 defining format=flowed, it's + ' when replying to the mutt-ng developer's mailing list and Mutt-ng @@ -5160,7 +5576,7 @@ Defaults to the contents of the environment variable $EMAIL. - _6_._4_._7_5 _g_e_c_o_s___m_a_s_k + _7_._4_._8_1 _g_e_c_o_s___m_a_s_k Type: regular expression @@ -5178,30 +5594,28 @@ expression that will match the whole name so Mutt-ng will expand ``Franklin'' to ``Franklin, Steve''. - _6_._4_._7_6 _h_d_r_s + _7_._4_._8_2 _h_d_r_s Type: boolean Default: yes - When _u_n_s_e_t, the header fields normally added by the ``_m_y___h_d_r (section 3.15 , - page 34)'' command are not created. This variable _m_u_s_t be _u_n_s_e_t before compos- + When _u_n_s_e_t, the header fields normally added by the ``_m_y___h_d_r (section 3.16 , + page 38)'' command are not created. This variable _m_u_s_t be _u_n_s_e_t before compos- ing a new message or replying in order to take effect. If _s_e_t, the user defined header fields are added to every new message. - _6_._4_._7_7 _h_e_a_d_e_r + _7_._4_._8_3 _h_e_a_d_e_r Type: boolean - The Mutt Next Generation E-Mail Client 102 - Default: no When _s_e_t, this variable causes Mutt-ng to include the header of the message you - are replying to into the edit buffer. The ``_$_w_e_e_d (section 6.4.336 , page - 165)'' setting applies. + are replying to into the edit buffer. The ``_$_w_e_e_d (section 7.4.351 , page + 175)'' setting applies. - _6_._4_._7_8 _h_e_a_d_e_r___c_a_c_h_e + _7_._4_._8_4 _h_e_a_d_e_r___c_a_c_h_e Type: path @@ -5209,15 +5623,18 @@ Availability: Header Cache - The _$_h_e_a_d_e_r___c_a_c_h_e (section 6.4.78 , page 101) variable points to the header + The _$_h_e_a_d_e_r___c_a_c_h_e (section 7.4.84 , page 109) variable points to the header + + The Mutt Next Generation E-Mail Client 110 + cache database. - If _$_h_e_a_d_e_r___c_a_c_h_e (section 6.4.78 , page 101) points to a directory it will + If _$_h_e_a_d_e_r___c_a_c_h_e (section 7.4.84 , page 109) points to a directory it will contain a header cache database per folder. If _$_h_e_a_d_e_r___c_a_c_h_e (section - 6.4.78 , page 101) points to a file that file will be a single global header + 7.4.84 , page 109) points to a file that file will be a single global header cache. By default it is _u_n_s_e_t so no header caching will be used. - _6_._4_._7_9 _h_e_a_d_e_r___c_a_c_h_e___c_o_m_p_r_e_s_s + _7_._4_._8_5 _h_e_a_d_e_r___c_a_c_h_e___c_o_m_p_r_e_s_s Type: boolean @@ -5227,7 +5644,7 @@ diskspace is used, but the uncompression can result in a slower open of the cached folder. - _6_._4_._8_0 _h_e_l_p + _7_._4_._8_6 _h_e_l_p Type: boolean @@ -5242,21 +5659,18 @@ is primarily aimed at new users, neither of these should present a major prob- lem. - _6_._4_._8_1 _h_i_d_d_e_n___h_o_s_t + _7_._4_._8_7 _h_i_d_d_e_n___h_o_s_t Type: boolean Default: no When _s_e_t, Mutt-ng will skip the host name part of ``_$_h_o_s_t_n_a_m_e (section - - The Mutt Next Generation E-Mail Client 103 - - 6.4.89 , page 103)'' variable when adding the domain part to addresses. This + 7.4.95 , page 111)'' variable when adding the domain part to addresses. This variable does not affect the generation of Message-ID: header fields, and it will not lead to the cut-off of first-level domains. - _6_._4_._8_2 _h_i_d_e___l_i_m_i_t_e_d + _7_._4_._8_8 _h_i_d_e___l_i_m_i_t_e_d Type: boolean @@ -5265,7 +5679,9 @@ When _s_e_t, Mutt-ng will not show the presence of messages that are hidden by limiting, in the thread tree. - _6_._4_._8_3 _h_i_d_e___m_i_s_s_i_n_g + _7_._4_._8_9 _h_i_d_e___m_i_s_s_i_n_g + + The Mutt Next Generation E-Mail Client 111 Type: boolean @@ -5274,7 +5690,7 @@ When _s_e_t, Mutt-ng will not show the presence of missing messages in the thread tree. - _6_._4_._8_4 _h_i_d_e___t_h_r_e_a_d___s_u_b_j_e_c_t + _7_._4_._9_0 _h_i_d_e___t_h_r_e_a_d___s_u_b_j_e_c_t Type: boolean @@ -5283,7 +5699,7 @@ When _s_e_t, Mutt-ng will not show the subject of messages in the thread tree that have the same subject as their parent or closest previously displayed sibling. - _6_._4_._8_5 _h_i_d_e___t_o_p___l_i_m_i_t_e_d + _7_._4_._9_1 _h_i_d_e___t_o_p___l_i_m_i_t_e_d Type: boolean @@ -5291,30 +5707,28 @@ When _s_e_t, Mutt-ng will not show the presence of messages that are hidden by limiting, at the top of threads in the thread tree. Note that when _$_h_i_d_e___m_i_s_s_- - _i_n_g (section 6.4.83 , page 102) is set, this option will have no effect. + _i_n_g (section 7.4.89 , page 110) is set, this option will have no effect. - _6_._4_._8_6 _h_i_d_e___t_o_p___m_i_s_s_i_n_g + _7_._4_._9_2 _h_i_d_e___t_o_p___m_i_s_s_i_n_g Type: boolean Default: yes When _s_e_t, Mutt-ng will not show the presence of missing messages at the top of - threads in the thread tree. Note that when _$_h_i_d_e___l_i_m_i_t_e_d (section 6.4.82 , - page 102) is _s_e_t, this option will have no effect. + threads in the thread tree. Note that when _$_h_i_d_e___l_i_m_i_t_e_d (section 7.4.88 , + page 110) is _s_e_t, this option will have no effect. - _6_._4_._8_7 _h_i_s_t_o_r_y + _7_._4_._9_3 _h_i_s_t_o_r_y Type: number - The Mutt Next Generation E-Mail Client 104 - Default: 10 This variable controls the size (in number of strings remembered) of the string history buffer. The buffer is cleared each time the variable is changed. - _6_._4_._8_8 _h_o_n_o_r___f_o_l_l_o_w_u_p___t_o + _7_._4_._9_4 _h_o_n_o_r___f_o_l_l_o_w_u_p___t_o Type: quadoption @@ -5323,7 +5737,9 @@ This variable controls whether or not a Mail-Followup-To: header field is hon- ored when group-replying to a message. - _6_._4_._8_9 _h_o_s_t_n_a_m_e + The Mutt Next Generation E-Mail Client 112 + + _7_._4_._9_5 _h_o_s_t_n_a_m_e Type: string @@ -5335,7 +5751,7 @@ Please be sure to really know what you are doing when changing this variable to configure a custom domain part of Message-IDs. - _6_._4_._9_0 _i_g_n_o_r_e___l_i_s_t___r_e_p_l_y___t_o + _7_._4_._9_6 _i_g_n_o_r_e___l_i_s_t___r_e_p_l_y___t_o Type: boolean @@ -5349,7 +5765,7 @@ option is set, use the _l_i_s_t_-_r_e_p_l_y function; _g_r_o_u_p_-_r_e_p_l_y will reply to both the sender and the list. - _6_._4_._9_1 _i_m_a_p___a_u_t_h_e_n_t_i_c_a_t_o_r_s + _7_._4_._9_7 _i_m_a_p___a_u_t_h_e_n_t_i_c_a_t_o_r_s Type: string @@ -5363,8 +5779,6 @@ capability string, e.g. ``digest-md5'', ``gssapi'' or ``cram-md5''. This param- eter is case-insensitive. - The Mutt Next Generation E-Mail Client 105 - If this parameter is _u_n_s_e_t (the default) Mutt-ng will try all available meth- ods, in order from most-secure to least-secure. @@ -5374,17 +5788,19 @@ ous methods are unavailable. If a method is available but authentication fails, Mutt-ng will not connect to the IMAP server. - _6_._4_._9_2 _i_m_a_p___c_h_e_c_k___s_u_b_s_c_r_i_b_e_d + _7_._4_._9_8 _i_m_a_p___c_h_e_c_k___s_u_b_s_c_r_i_b_e_d Type: boolean Default: no + The Mutt Next Generation E-Mail Client 113 + When _s_e_t, mutt will fetch the set of subscribed folders from your server on connection, and add them to the set of mailboxes it polls for new mail. See - also the ``_m_a_i_l_b_o_x_e_s (section 3.14 , page 33)'' command. + also the ``_m_a_i_l_b_o_x_e_s (section 3.15 , page 37)'' command. - _6_._4_._9_3 _i_m_a_p___d_e_l_i_m___c_h_a_r_s + _7_._4_._9_9 _i_m_a_p___d_e_l_i_m___c_h_a_r_s Type: string @@ -5394,9 +5810,9 @@ This contains the list of characters which you would like to treat as folder separators for displaying IMAP paths. In particular it helps in using the '=' - shortcut for your _$_f_o_l_d_e_r (section 6.4.64 , page 97) variable. + shortcut for your _$_f_o_l_d_e_r (section 7.4.70 , page 105) variable. - _6_._4_._9_4 _i_m_a_p___h_e_a_d_e_r_s + _7_._4_._1_0_0 _i_m_a_p___h_e_a_d_e_r_s Type: string @@ -5411,7 +5827,7 @@ NNoottee:: This is a space separated list. - _6_._4_._9_5 _i_m_a_p___h_o_m_e___n_a_m_e_s_p_a_c_e + _7_._4_._1_0_1 _i_m_a_p___h_o_m_e___n_a_m_e_s_p_a_c_e Type: string @@ -5419,13 +5835,11 @@ Availability: IMAP - The Mutt Next Generation E-Mail Client 106 - You normally want to see your personal folders alongside your INBOX in the IMAP browser. If you see something else, you may set this variable to the IMAP path to your folders. - _6_._4_._9_6 _i_m_a_p___k_e_e_p_a_l_i_v_e + _7_._4_._1_0_2 _i_m_a_p___k_e_e_p_a_l_i_v_e Type: number @@ -5437,6 +5851,8 @@ wait before polling open IMAP connections, to prevent the server from closing them before Mutt-ng has finished with them. + The Mutt Next Generation E-Mail Client 114 + The default is well within the RFC-specified minimum amount of time (30 min- utes) before a server is allowed to do this, but in practice the RFC does get violated every now and then. @@ -5444,7 +5860,7 @@ Reduce this number if you find yourself getting disconnected from your IMAP server due to inactivity. - _6_._4_._9_7 _i_m_a_p___l_i_s_t___s_u_b_s_c_r_i_b_e_d + _7_._4_._1_0_3 _i_m_a_p___l_i_s_t___s_u_b_s_c_r_i_b_e_d Type: boolean @@ -5456,7 +5872,7 @@ scribed folders or all folders. This can be toggled in the IMAP browser with the _t_o_g_g_l_e_-_s_u_b_s_c_r_i_b_e_d function. - _6_._4_._9_8 _i_m_a_p___l_o_g_i_n + _7_._4_._1_0_4 _i_m_a_p___l_o_g_i_n Type: string @@ -5466,23 +5882,21 @@ Your login name on the IMAP server. - This variable defaults to the value of ``_$_i_m_a_p___u_s_e_r (section 6.4.105 , page - 107).'' + This variable defaults to the value of ``_$_i_m_a_p___u_s_e_r (section 7.4.111 , page + 115).'' - _6_._4_._9_9 _i_m_a_p___m_a_i_l___c_h_e_c_k + _7_._4_._1_0_5 _i_m_a_p___m_a_i_l___c_h_e_c_k Type: number Default: 300 - The Mutt Next Generation E-Mail Client 107 - This variable configures how often (in seconds) Mutt-ng should look for new - mail in IMAP folders. This is split from the ``_m_a_i_l___c_h_e_c_k (section 6.4.115 , - page 111)'' variable to generate less traffic and get more accurate information + mail in IMAP folders. This is split from the ``_m_a_i_l___c_h_e_c_k (section 7.4.121 , + page 120)'' variable to generate less traffic and get more accurate information for local folders. - _6_._4_._1_0_0 _i_m_a_p___p_a_s_s + _7_._4_._1_0_6 _i_m_a_p___p_a_s_s Type: string @@ -5493,11 +5907,13 @@ Specifies the password for your IMAP account. If _u_n_s_e_t, Mutt-ng will prompt you for your password when you invoke the fetch-mail function. + The Mutt Next Generation E-Mail Client 115 + WWaarrnniinngg: you should only use this option when you are on a fairly secure machine, because the superuser can read your configuration even if you are the only one who can read the file. - _6_._4_._1_0_1 _i_m_a_p___p_a_s_s_i_v_e + _7_._4_._1_0_7 _i_m_a_p___p_a_s_s_i_v_e Type: boolean @@ -5510,7 +5926,7 @@ useful if you don't want to be prompted to user/password pairs on Mutt-ng invo- cation, or if opening the connection is slow. - _6_._4_._1_0_2 _i_m_a_p___p_e_e_k + _7_._4_._1_0_8 _i_m_a_p___p_e_e_k Type: boolean @@ -5523,7 +5939,7 @@ closing an IMAP folder somewhat slower. This option exists to appease speed freaks. - _6_._4_._1_0_3 _i_m_a_p___r_e_c_o_n_n_e_c_t + _7_._4_._1_0_9 _i_m_a_p___r_e_c_o_n_n_e_c_t Type: quadoption @@ -5531,12 +5947,10 @@ Availability: IMAP - The Mutt Next Generation E-Mail Client 108 - Controls whether or not Mutt-ng will try to reconnect to IMAP server when the connection is lost. - _6_._4_._1_0_4 _i_m_a_p___s_e_r_v_e_r_n_o_i_s_e + _7_._4_._1_1_0 _i_m_a_p___s_e_r_v_e_r_n_o_i_s_e Type: boolean @@ -5549,7 +5963,9 @@ ration problems on the server which are out of the users' hands, you may wish to suppress them at some point. - _6_._4_._1_0_5 _i_m_a_p___u_s_e_r + The Mutt Next Generation E-Mail Client 116 + + _7_._4_._1_1_1 _i_m_a_p___u_s_e_r Type: string @@ -5561,7 +5977,7 @@ This variable defaults to your user name on the local machine. - _6_._4_._1_0_6 _i_m_p_l_i_c_i_t___a_u_t_o_v_i_e_w + _7_._4_._1_1_2 _i_m_p_l_i_c_i_t___a_u_t_o_v_i_e_w Type: boolean @@ -5572,7 +5988,7 @@ If such an entry is found, Mutt-ng will use the viewer defined in that entry to convert the body part to text form. - _6_._4_._1_0_7 _i_n_c_l_u_d_e + _7_._4_._1_1_3 _i_n_c_l_u_d_e Type: quadoption @@ -5581,18 +5997,16 @@ Controls whether or not a copy of the message(s) you are replying to is included in your reply. - _6_._4_._1_0_8 _i_n_c_l_u_d_e___o_n_l_y_f_i_r_s_t + _7_._4_._1_1_4 _i_n_c_l_u_d_e___o_n_l_y_f_i_r_s_t Type: boolean Default: no - The Mutt Next Generation E-Mail Client 109 - Controls whether or not Mutt-ng includes only the first attachment of the mes- sage you are replying. - _6_._4_._1_0_9 _i_n_d_e_n_t___s_t_r_i_n_g + _7_._4_._1_1_5 _i_n_d_e_n_t___s_t_r_i_n_g Type: string @@ -5602,10 +6016,12 @@ which you are replying. You are strongly encouraged not to change this value, as it tends to agitate the more fanatical netizens. - _6_._4_._1_1_0 _i_n_d_e_x___f_o_r_m_a_t + _7_._4_._1_1_6 _i_n_d_e_x___f_o_r_m_a_t Type: string + The Mutt Next Generation E-Mail Client 117 + Default: '%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s' This variable allows you to customize the message index display to your per- @@ -5642,8 +6058,6 @@ date and time of the message in the format specified by ``date_for- mat'' converted to the local time zone - The Mutt Next Generation E-Mail Client 110 - %e current message number in thread @@ -5662,6 +6076,8 @@ %g newsgroup name (if compiled with nntp support) + The Mutt Next Generation E-Mail Client 118 + %i message-id of the current message @@ -5699,11 +6115,9 @@ %t `to:' field (recipients) - The Mutt Next Generation E-Mail Client 111 - %T - the appropriate character from the _$_t_o___c_h_a_r_s (section 6.4.323 , - page 162) string + the appropriate character from the _$_t_o___c_h_a_r_s (section 7.4.339 , + page 172) string %u user (login) name of the author @@ -5718,6 +6132,8 @@ %y `x-label:' field, if present + The Mutt Next Generation E-Mail Client 119 + %Y `x-label' field, if present, and (1) not at part of a thread tree, (2) at the top of a thread, or (3) `x-label' is different from pre- @@ -5751,11 +6167,9 @@ %|X pad to the end of the line with character 'X' - See also: ``_$_t_o___c_h_a_r_s (section 6.4.323 , page 162)''. - - _6_._4_._1_1_1 _i_s_p_e_l_l + See also: ``_$_t_o___c_h_a_r_s (section 7.4.339 , page 172)''. - The Mutt Next Generation E-Mail Client 112 + _7_._4_._1_1_7 _i_s_p_e_l_l Type: path @@ -5763,17 +6177,19 @@ How to invoke ispell (GNU's spell-checking software). - _6_._4_._1_1_2 _k_e_e_p___f_l_a_g_g_e_d + _7_._4_._1_1_8 _k_e_e_p___f_l_a_g_g_e_d Type: boolean Default: no If _s_e_t, read messages marked as flagged will not be moved from your spool mail- - box to your ``_$_m_b_o_x (section 6.4.124 , page 113)'' mailbox, or as a result of - a ``_m_b_o_x_-_h_o_o_k (section 3.13 , page 33)'' command. + box to your ``_$_m_b_o_x (section 7.4.131 , page 122)'' mailbox, or as a result of + a ``_m_b_o_x_-_h_o_o_k (section 3.14 , page 37)'' command. + + The Mutt Next Generation E-Mail Client 120 - _6_._4_._1_1_3 _l_i_s_t___r_e_p_l_y + _7_._4_._1_1_9 _l_i_s_t___r_e_p_l_y Type: quadoption @@ -5783,7 +6199,7 @@ (instead to the author only). Setting this option to ``_a_s_k_-_y_e_s'' or ``_a_s_k_-_n_o'' will ask if you really intended to reply to the author only. - _6_._4_._1_1_4 _l_o_c_a_l_e + _7_._4_._1_2_0 _l_o_c_a_l_e Type: string @@ -5792,7 +6208,7 @@ The locale used by strftime(3) to format dates. Legal values are the strings your system accepts for the locale variable LC_TIME. - _6_._4_._1_1_5 _m_a_i_l___c_h_e_c_k + _7_._4_._1_2_1 _m_a_i_l___c_h_e_c_k Type: number @@ -5802,21 +6218,18 @@ mail. NNoottee:: This does not apply to IMAP mailboxes, see _$_i_m_a_p___m_a_i_l___c_h_e_c_k (section - 6.4.99 , page 105). + 7.4.105 , page 114). - _6_._4_._1_1_6 _m_a_i_l_c_a_p___p_a_t_h + _7_._4_._1_2_2 _m_a_i_l_c_a_p___p_a_t_h Type: string Default: '' This variable specifies which files to consult when attempting to display MIME - - The Mutt Next Generation E-Mail Client 113 - bodies not directly supported by Mutt-ng. - _6_._4_._1_1_7 _m_a_i_l_c_a_p___s_a_n_i_t_i_z_e + _7_._4_._1_2_3 _m_a_i_l_c_a_p___s_a_n_i_t_i_z_e Type: boolean @@ -5828,7 +6241,9 @@ DDOONN''TT CCHHAANNGGEE TTHHIISS SSEETTTTIINNGG UUNNLLEESSSS YYOOUU AARREE RREEAALLLLYY SSUURREE WWHHAATT YYOOUU AARREE DDOOIINNGG!! - _6_._4_._1_1_8 _m_a_i_l_d_i_r___h_e_a_d_e_r___c_a_c_h_e___v_e_r_i_f_y + _7_._4_._1_2_4 _m_a_i_l_d_i_r___h_e_a_d_e_r___c_a_c_h_e___v_e_r_i_f_y + + The Mutt Next Generation E-Mail Client 121 Type: boolean @@ -5840,7 +6255,7 @@ files when the header cache is in use. This incurs one stat(2) per message every time the folder is opened. - _6_._4_._1_1_9 _m_a_i_l_d_i_r___t_r_a_s_h + _7_._4_._1_2_5 _m_a_i_l_d_i_r___t_r_a_s_h Type: boolean @@ -5854,7 +6269,7 @@ It is similiar to the trash option. - _6_._4_._1_2_0 _m_a_r_k___o_l_d + _7_._4_._1_2_6 _m_a_r_k___o_l_d Type: boolean @@ -5867,9 +6282,7 @@ up with an 'O' next to them in the ``index'' menu, indicating that they are old. - The Mutt Next Generation E-Mail Client 114 - - _6_._4_._1_2_1 _m_a_r_k_e_r_s + _7_._4_._1_2_7 _m_a_r_k_e_r_s Type: boolean @@ -5877,19 +6290,33 @@ Controls the display of wrapped lines in the internal pager. If set, a ``+'' marker is displayed at the beginning of wrapped lines. Also see the - ``_$_s_m_a_r_t___w_r_a_p (section 6.4.263 , page 146)'' variable. + ``_$_s_m_a_r_t___w_r_a_p (section 7.4.279 , page 156)'' variable. - _6_._4_._1_2_2 _m_a_s_k + _7_._4_._1_2_8 _m_a_s_k Type: regular expression Default: '!^\.[^.]' A regular expression used in the file browser, optionally preceded by the _n_o_t + + The Mutt Next Generation E-Mail Client 122 + operator ``!''. Only files whose names match this mask will be shown. The match is always case-sensitive. - _6_._4_._1_2_3 _m_a_x___l_i_n_e___l_e_n_g_t_h + _7_._4_._1_2_9 _m_a_x___d_i_s_p_l_a_y___r_e_c_i_p_s + + Type: number + + Default: 0 + + When set non-zero, this specifies the maximum number of recipient header lines + (To:, Cc: and Bcc:) to display in the pager if header weeding is turned on. In + case the number of lines exeeds its value, the last line will have 3 dots + appended. + + _7_._4_._1_3_0 _m_a_x___l_i_n_e___l_e_n_g_t_h Type: number @@ -5898,18 +6325,18 @@ When _s_e_t, the maximum line length for displaying ``format = flowed'' messages is limited to this length. A value of 0 (which is also the default) means that the maximum line length is determined by the terminal width and _$_w_r_a_p_m_a_r_g_i_n - (section 6.4.338 , page 165). + (section 7.4.353 , page 175). - _6_._4_._1_2_4 _m_b_o_x + _7_._4_._1_3_1 _m_b_o_x Type: path Default: '~/mbox' This specifies the folder into which read mail in your ``_$_s_p_o_o_l_f_i_l_e (section - 6.4.297 , page 154)'' folder will be appended. + 7.4.313 , page 165)'' folder will be appended. - _6_._4_._1_2_5 _m_b_o_x___t_y_p_e + _7_._4_._1_3_2 _m_b_o_x___t_y_p_e Type: folder magic @@ -5918,19 +6345,19 @@ The default mailbox type used when creating new folders. May be any of mbox, MMDF, MH and Maildir. - _6_._4_._1_2_6 _m_e_n_u___c_o_n_t_e_x_t + _7_._4_._1_3_3 _m_e_n_u___c_o_n_t_e_x_t Type: number Default: 0 - The Mutt Next Generation E-Mail Client 115 - This variable controls the number of lines of context that are given when - scrolling through menus. (Similar to ``_$_p_a_g_e_r___c_o_n_t_e_x_t (section 6.4.167 , page - 124)''.) + scrolling through menus. (Similar to ``_$_p_a_g_e_r___c_o_n_t_e_x_t (section 7.4.183 , page + 134)''.) - _6_._4_._1_2_7 _m_e_n_u___m_o_v_e___o_f_f + The Mutt Next Generation E-Mail Client 123 + + _7_._4_._1_3_4 _m_e_n_u___m_o_v_e___o_f_f Type: boolean @@ -5940,7 +6367,7 @@ the screen, unless there are less entries than lines. When _s_e_t, the bottom entry may move off the bottom. - _6_._4_._1_2_8 _m_e_n_u___s_c_r_o_l_l + _7_._4_._1_3_5 _m_e_n_u___s_c_r_o_l_l Type: boolean @@ -5951,7 +6378,7 @@ vious page of the menu is displayed (useful for slow links to avoid many redraws). - _6_._4_._1_2_9 _m_e_s_s_a_g_e___f_o_r_m_a_t + _7_._4_._1_3_6 _m_e_s_s_a_g_e___f_o_r_m_a_t Type: string @@ -5959,9 +6386,9 @@ This is the string displayed in the ``attachment'' menu for attachments of type message/rfc822. For a full listing of defined printf(3)-like sequences see the - section on ``_$_i_n_d_e_x___f_o_r_m_a_t (section 6.4.110 , page 108)''. + section on ``_$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.116 , page 116)''. - _6_._4_._1_3_0 _m_e_t_a___k_e_y + _7_._4_._1_3_7 _m_e_t_a___k_e_y Type: boolean @@ -5974,18 +6401,18 @@ because the result of removing the high bit from ``0xf4'' is ``0x74'', which is the ASCII character ``x''. - _6_._4_._1_3_1 _m_e_t_o_o + _7_._4_._1_3_8 _m_e_t_o_o Type: boolean Default: no - The Mutt Next Generation E-Mail Client 116 - If _u_n_s_e_t, Mutt-ng will remove your address (see the ``alternates'' command) from the list of recipients when replying to a message. - _6_._4_._1_3_2 _m_h___p_u_r_g_e + The Mutt Next Generation E-Mail Client 124 + + _7_._4_._1_3_9 _m_h___p_u_r_g_e Type: boolean @@ -5995,7 +6422,7 @@ _,_<_o_l_d _f_i_l_e _n_a_m_e_> in mh folders instead of really deleting them. If the vari- able is set, the message files will simply be deleted. - _6_._4_._1_3_3 _m_h___s_e_q___f_l_a_g_g_e_d + _7_._4_._1_4_0 _m_h___s_e_q___f_l_a_g_g_e_d Type: string @@ -6003,7 +6430,7 @@ The name of the MH sequence used for flagged messages. - _6_._4_._1_3_4 _m_h___s_e_q___r_e_p_l_i_e_d + _7_._4_._1_4_1 _m_h___s_e_q___r_e_p_l_i_e_d Type: string @@ -6011,7 +6438,7 @@ The name of the MH sequence used to tag replied messages. - _6_._4_._1_3_5 _m_h___s_e_q___u_n_s_e_e_n + _7_._4_._1_4_2 _m_h___s_e_q___u_n_s_e_e_n Type: string @@ -6019,7 +6446,7 @@ The name of the MH sequence used for unseen messages. - _6_._4_._1_3_6 _m_i_m_e___f_o_r_w_a_r_d + _7_._4_._1_4_3 _m_i_m_e___f_o_r_w_a_r_d Type: quadoption @@ -6032,22 +6459,22 @@ the message as it was delivered to you. If you like to switch between MIME and not MIME from mail to mail, set this variable to ask-no or ask-yes. - Also see ``_$_f_o_r_w_a_r_d___d_e_c_o_d_e (section 6.4.69 , page 99)'' and ``_$_m_i_m_e___f_o_r_- - _w_a_r_d___d_e_c_o_d_e (section 6.4.137 , page 115)''. + Also see ``_$_f_o_r_w_a_r_d___d_e_c_o_d_e (section 7.4.75 , page 107)'' and ``_$_m_i_m_e___f_o_r_- + _w_a_r_d___d_e_c_o_d_e (section 7.4.144 , page 124)''. - The Mutt Next Generation E-Mail Client 117 - - _6_._4_._1_3_7 _m_i_m_e___f_o_r_w_a_r_d___d_e_c_o_d_e + _7_._4_._1_4_4 _m_i_m_e___f_o_r_w_a_r_d___d_e_c_o_d_e Type: boolean + The Mutt Next Generation E-Mail Client 125 + Default: no Controls the decoding of complex MIME messages into text/plain when forwarding - a message while ``_$_m_i_m_e___f_o_r_w_a_r_d (section 6.4.136 , page 115)'' is _s_e_t. Other- - wise ``_$_f_o_r_w_a_r_d___d_e_c_o_d_e (section 6.4.69 , page 99)'' is used instead. + a message while ``_$_m_i_m_e___f_o_r_w_a_r_d (section 7.4.143 , page 124)'' is _s_e_t. Other- + wise ``_$_f_o_r_w_a_r_d___d_e_c_o_d_e (section 7.4.75 , page 107)'' is used instead. - _6_._4_._1_3_8 _m_i_m_e___f_o_r_w_a_r_d___r_e_s_t + _7_._4_._1_4_5 _m_i_m_e___f_o_r_w_a_r_d___r_e_s_t Type: quadoption @@ -6057,7 +6484,7 @@ menu, attachments which cannot be decoded in a reasonable manner will be attached to the newly composed message if this option is set. - _6_._4_._1_3_9 _m_i_x___e_n_t_r_y___f_o_r_m_a_t + _7_._4_._1_4_6 _m_i_x___e_n_t_r_y___f_o_r_m_a_t Type: string @@ -6080,7 +6507,7 @@ %a The remailer's e-mail address. - _6_._4_._1_4_0 _m_i_x_m_a_s_t_e_r + _7_._4_._1_4_7 _m_i_x_m_a_s_t_e_r Type: path @@ -6092,19 +6519,19 @@ used with various sets of parameters to gather the list of known remailers, and to finally send a message through the mixmaster chain. - The Mutt Next Generation E-Mail Client 118 - - _6_._4_._1_4_1 _m_o_v_e + _7_._4_._1_4_8 _m_o_v_e Type: quadoption + The Mutt Next Generation E-Mail Client 126 + Default: ask-no Controls whether or not Mutt-ng will move read messages from your spool mailbox - to your ``_$_m_b_o_x (section 6.4.124 , page 113)'' mailbox, or as a result of a - ``_m_b_o_x_-_h_o_o_k (section 3.13 , page 33)'' command. + to your ``_$_m_b_o_x (section 7.4.131 , page 122)'' mailbox, or as a result of a + ``_m_b_o_x_-_h_o_o_k (section 3.14 , page 37)'' command. - _6_._4_._1_4_2 _m_s_g_i_d___f_o_r_m_a_t + _7_._4_._1_4_9 _m_s_g_i_d___f_o_r_m_a_t Type: string @@ -6137,33 +6564,116 @@ the current Message-ID prefix (a character rotating with every Mes- sage-ID being generated) - %r - a random integer value (decimal) + %r + a random integer value (decimal) + + %R + a random integer value (hexadecimal) + + %s + the current second + + %T + the current UNIX timestamp (decimal) + + %X + the current UNIX timestamp (hexadecimal) + + The Mutt Next Generation E-Mail Client 127 + + %Y + the current year (Y2K compliant) + + %% + the '%' character + + NNoottee:: Please only change this setting if you know what you are doing. Also + make sure to consult RFC2822 to produce technically _v_a_l_i_d strings. + + _7_._4_._1_5_0 _m_u_t_t_n_g___b_i_n_d_i_r + + Type: system property + + Value: /opt/freebsd4/mutt-ng/bin + + _T_h_i_s _i_s _a _r_e_a_d_-_o_n_l_y _s_y_s_t_e_m _p_r_o_p_e_r_t_y _a_n_d _s_p_e_c_i_f_i_e_s _t_h_e _d_i_r_e_c_t_o_r_y _c_o_n_t_a_i_n_i_n_g _t_h_e + _m_u_t_t_n_g _b_i_n_a_r_y_. + + _7_._4_._1_5_1 _m_u_t_t_n_g___d_o_c_d_i_r + + Type: system property + + Value: /opt/freebsd4/mutt-ng/doc/muttng + + _T_h_i_s _i_s _a _r_e_a_d_-_o_n_l_y _s_y_s_t_e_m _p_r_o_p_e_r_t_y _a_n_d _s_p_e_c_i_f_i_e_s _t_h_e _d_i_r_e_c_t_o_r_y _c_o_n_t_a_i_n_i_n_g _t_h_e + _m_u_t_t_n_g _d_o_c_u_m_e_n_t_a_t_i_o_n_. + + _7_._4_._1_5_2 _m_u_t_t_n_g___f_o_l_d_e_r___n_a_m_e + + Type: system property + + Value: + + _T_h_i_s _i_s _a _r_e_a_d_-_o_n_l_y _s_y_s_t_e_m _p_r_o_p_e_r_t_y _a_n_d_, _a_t _r_u_n_t_i_m_e_, _s_p_e_c_i_f_i_e_s _t_h_e _l_a_s_t _p_a_r_t _o_f + _t_h_e _f_u_l_l _p_a_t_h _o_r _U_R_I _o_f _t_h_e _f_o_l_d_e_r _c_u_r_r_e_n_t_l_y _o_p_e_n _(_i_f _a_n_y_)_, _i_._e_. _e_v_e_r_y_t_h_i_n_g + _a_f_t_e_r _t_h_e _l_a_s_t _`_`_/_'_'_. + + _7_._4_._1_5_3 _m_u_t_t_n_g___f_o_l_d_e_r___p_a_t_h + + Type: system property + + Value: + + _T_h_i_s _i_s _a _r_e_a_d_-_o_n_l_y _s_y_s_t_e_m _p_r_o_p_e_r_t_y _a_n_d_, _a_t _r_u_n_t_i_m_e_, _s_p_e_c_i_f_i_e_s _t_h_e _f_u_l_l _p_a_t_h _o_r + _U_R_I _o_f _t_h_e _f_o_l_d_e_r _c_u_r_r_e_n_t_l_y _o_p_e_n _(_i_f _a_n_y_)_. + + _7_._4_._1_5_4 _m_u_t_t_n_g___h_c_a_c_h_e___b_a_c_k_e_n_d + + Type: system property + + Value: qdbm + + _T_h_i_s _i_s _a _r_e_a_d_-_o_n_l_y _s_y_s_t_e_m _p_r_o_p_e_r_t_y _a_n_d _s_p_e_c_i_f_i_e_s _t_h_e _h_e_a_d_e_r _c_h_a_c_h_i_n_g_'_s _d_a_t_a_- + _b_a_s_e _b_a_c_k_e_n_d_. + + The Mutt Next Generation E-Mail Client 128 + + _7_._4_._1_5_5 _m_u_t_t_n_g___p_w_d + + Type: system property + + Value: + + _T_h_i_s _i_s _a _r_e_a_d_-_o_n_l_y _s_y_s_t_e_m _p_r_o_p_e_r_t_y _a_n_d_, _a_t _r_u_n_t_i_m_e_, _s_p_e_c_i_f_i_e_s _t_h_e _c_u_r_r_e_n_t + _w_o_r_k_i_n_g _d_i_r_e_c_t_o_r_y _o_f _t_h_e _m_u_t_t_n_g _b_i_n_a_r_y_. + + _7_._4_._1_5_6 _m_u_t_t_n_g___r_e_v_i_s_i_o_n + + Type: system property - %R - a random integer value (hexadecimal) + Value: 471 - %s - the current second + _T_h_i_s _i_s _a _r_e_a_d_-_o_n_l_y _s_y_s_t_e_m _p_r_o_p_e_r_t_y _a_n_d _s_p_e_c_i_f_i_e_s _m_u_t_t_n_g_'_s _s_u_b_v_e_r_s_i_o_n _r_e_v_i_s_i_o_n + _s_t_r_i_n_g_. - %T - the current UNIX timestamp (decimal) + _7_._4_._1_5_7 _m_u_t_t_n_g___s_y_s_c_o_n_f_d_i_r - The Mutt Next Generation E-Mail Client 119 + Type: system property - %X - the current UNIX timestamp (hexadecimal) + Value: /opt/freebsd4/mutt-ng/etc - %Y - the current year (Y2K compliant) + _T_h_i_s _i_s _a _r_e_a_d_-_o_n_l_y _s_y_s_t_e_m _p_r_o_p_e_r_t_y _a_n_d _s_p_e_c_i_f_i_e_s _t_h_e _d_i_r_e_c_t_o_r_y _c_o_n_t_a_i_n_i_n_g _t_h_e + _m_u_t_t_n_g _s_y_s_t_e_m_-_w_i_d_e _c_o_n_f_i_g_u_r_a_t_i_o_n_. - %% - the '%' character + _7_._4_._1_5_8 _m_u_t_t_n_g___v_e_r_s_i_o_n - NNoottee:: Please only change this setting if you know what you are doing. Also - make sure to consult RFC2822 to produce technically _v_a_l_i_d strings. + Type: system property + + Value: devel - _6_._4_._1_4_3 _n_a_r_r_o_w___t_r_e_e + _T_h_i_s _i_s _a _r_e_a_d_-_o_n_l_y _s_y_s_t_e_m _p_r_o_p_e_r_t_y _a_n_d _s_p_e_c_i_f_i_e_s _m_u_t_t_n_g_'_s _v_e_r_s_i_o_n _s_t_r_i_n_g_. + + _7_._4_._1_5_9 _n_a_r_r_o_w___t_r_e_e Type: boolean @@ -6172,7 +6682,7 @@ This variable, when _s_e_t, makes the thread tree narrower, allowing deeper threads to fit on the screen. - _6_._4_._1_4_4 _n_n_t_p___a_s_k___f_o_l_l_o_w_u_p___t_o + _7_._4_._1_6_0 _n_n_t_p___a_s_k___f_o_l_l_o_w_u_p___t_o Type: boolean @@ -6183,7 +6693,9 @@ If _s_e_t, Mutt-ng will prompt you for the Followup-To: header field before edit- ing the body of an outgoing news article. - _6_._4_._1_4_5 _n_n_t_p___a_s_k___x___c_o_m_m_e_n_t___t_o + The Mutt Next Generation E-Mail Client 129 + + _7_._4_._1_6_1 _n_n_t_p___a_s_k___x___c_o_m_m_e_n_t___t_o Type: boolean @@ -6194,7 +6706,7 @@ If _s_e_t, Mutt-ng will prompt you for the X-Comment-To: header field before edit- ing the body of an outgoing news article. - _6_._4_._1_4_6 _n_n_t_p___c_a_c_h_e___d_i_r + _7_._4_._1_6_2 _n_n_t_p___c_a_c_h_e___d_i_r Type: path @@ -6206,12 +6718,10 @@ ers. If _u_n_s_e_t, headers will not be saved at all and will be reloaded each time when you enter a newsgroup. - The Mutt Next Generation E-Mail Client 120 - As for the header caching in connection with IMAP and/or Maildir, this drasti- cally increases speed and lowers traffic. - _6_._4_._1_4_7 _n_n_t_p___c_a_t_c_h_u_p + _7_._4_._1_6_3 _n_n_t_p___c_a_t_c_h_u_p Type: quadoption @@ -6222,7 +6732,7 @@ If this variable is _s_e_t, Mutt-ng will mark all articles in a newsgroup as read when you leaving it. - _6_._4_._1_4_8 _n_n_t_p___c_o_n_t_e_x_t + _7_._4_._1_6_4 _n_n_t_p___c_o_n_t_e_x_t Type: number @@ -6231,13 +6741,15 @@ Availability: NNTP This variable controls how many news articles to cache per newsgroup (if - caching is enabled, see _$_n_n_t_p___c_a_c_h_e___d_i_r (section 6.4.146 , page 118)) and how + caching is enabled, see _$_n_n_t_p___c_a_c_h_e___d_i_r (section 7.4.162 , page 129)) and how many news articles to show in the ``index'' menu. - If there're more articles than defined with _$_n_n_t_p___c_o_n_t_e_x_t (section 6.4.148 , - page 119), all older ones will be removed/not shown in the index. + If there're more articles than defined with _$_n_n_t_p___c_o_n_t_e_x_t (section 7.4.164 , + page 129), all older ones will be removed/not shown in the index. + + _7_._4_._1_6_5 _n_n_t_p___f_o_l_l_o_w_u_p___t_o___p_o_s_t_e_r - _6_._4_._1_4_9 _n_n_t_p___f_o_l_l_o_w_u_p___t_o___p_o_s_t_e_r + The Mutt Next Generation E-Mail Client 130 Type: quadoption @@ -6249,7 +6761,7 @@ header field, a follow-up to the newsgroup is not permitted. The message will be mailed to the submitter of the message via mail. - _6_._4_._1_5_0 _n_n_t_p___g_r_o_u_p___i_n_d_e_x___f_o_r_m_a_t + _7_._4_._1_6_6 _n_n_t_p___g_r_o_u_p___i_n_d_e_x___f_o_r_m_a_t Type: string @@ -6258,10 +6770,8 @@ Availability: NNTP This variable allows you to customize the newsgroup browser display to your - personal taste. This string is similar to ``_i_n_d_e_x___f_o_r_m_a_t (section 6.4.110 , - page 108)'', but has its own set of printf(3)-like sequences: - - The Mutt Next Generation E-Mail Client 121 + personal taste. This string is similar to ``_i_n_d_e_x___f_o_r_m_a_t (section 7.4.116 , + page 116)'', but has its own set of printf(3)-like sequences: %C current newsgroup number %d description of newsgroup (retrieved from server) @@ -6273,7 +6783,7 @@ %>X right justify the rest of the string and pad with character "X" %|X pad to the end of the line with character "X" - _6_._4_._1_5_1 _n_n_t_p___h_o_s_t + _7_._4_._1_6_7 _n_n_t_p___h_o_s_t Type: string @@ -6293,9 +6803,12 @@ NNoottee:: Using a password as shown and stored in a configuration file presents a security risk since the superuser of your machine may read it regardless of the + + The Mutt Next Generation E-Mail Client 131 + file's permissions. - _6_._4_._1_5_2 _n_n_t_p___i_n_e_w_s + _7_._4_._1_6_8 _n_n_t_p___i_n_e_w_s Type: path @@ -6311,12 +6824,10 @@ Example: set inews='/usr/local/bin/inews -hS' - _6_._4_._1_5_3 _n_n_t_p___l_o_a_d___d_e_s_c_r_i_p_t_i_o_n + _7_._4_._1_6_9 _n_n_t_p___l_o_a_d___d_e_s_c_r_i_p_t_i_o_n Type: boolean - The Mutt Next Generation E-Mail Client 122 - Default: yes Availability: NNTP @@ -6324,7 +6835,7 @@ This variable controls whether or not descriptions for newsgroups are to be loaded when subscribing to a newsgroup. - _6_._4_._1_5_4 _n_n_t_p___m_a_i_l___c_h_e_c_k + _7_._4_._1_7_0 _n_n_t_p___m_a_i_l___c_h_e_c_k Type: number @@ -6336,7 +6847,7 @@ article will cause a recheck for new news. If set to 0, Mutt-ng will recheck on each operation in index (stepping, read article, etc.). - _6_._4_._1_5_5 _n_n_t_p___m_i_m_e___s_u_b_j_e_c_t + _7_._4_._1_7_1 _n_n_t_p___m_i_m_e___s_u_b_j_e_c_t Type: boolean @@ -6347,9 +6858,11 @@ If _u_n_s_e_t, an 8-bit ``Subject:'' header field in a news article will not be encoded according to RFC2047. + The Mutt Next Generation E-Mail Client 132 + NNoottee:: Only change this setting if you know what you are doing. - _6_._4_._1_5_6 _n_n_t_p___n_e_w_s_r_c + _7_._4_._1_7_2 _n_n_t_p___n_e_w_s_r_c Type: path @@ -6365,12 +6878,10 @@ %s newsserver name - _6_._4_._1_5_7 _n_n_t_p___p_a_s_s + _7_._4_._1_7_3 _n_n_t_p___p_a_s_s Type: string - The Mutt Next Generation E-Mail Client 123 - Default: '' Availability: NNTP @@ -6380,7 +6891,7 @@ NNoottee:: Storing passwords in a configuration file presents a security risk since the superuser of your machine may read it regardless of the file's permissions. - _6_._4_._1_5_8 _n_n_t_p___p_o_s_t___m_o_d_e_r_a_t_e_d + _7_._4_._1_7_4 _n_n_t_p___p_o_s_t___m_o_d_e_r_a_t_e_d Type: quadoption @@ -6394,7 +6905,7 @@ NNoottee:: if the newsserver does not support posting to that newsgroup or a group is totally read-only, that posting will not have any effect. - _6_._4_._1_5_9 _n_n_t_p___r_e_c_o_n_n_e_c_t + _7_._4_._1_7_5 _n_n_t_p___r_e_c_o_n_n_e_c_t Type: quadoption @@ -6402,10 +6913,12 @@ Availability: NNTP + The Mutt Next Generation E-Mail Client 133 + Controls whether or not Mutt-ng will try to reconnect to a newsserver when the was connection lost. - _6_._4_._1_6_0 _n_n_t_p___s_a_v_e___u_n_s_u_b_s_c_r_i_b_e_d + _7_._4_._1_7_6 _n_n_t_p___s_a_v_e___u_n_s_u_b_s_c_r_i_b_e_d Type: boolean @@ -6416,7 +6929,7 @@ When _s_e_t, info about unsubscribed newsgroups will be saved into the ``newsrc'' file and into the news cache. - _6_._4_._1_6_1 _n_n_t_p___s_h_o_w___n_e_w___n_e_w_s + _7_._4_._1_7_7 _n_n_t_p___s_h_o_w___n_e_w___n_e_w_s Type: boolean @@ -6425,14 +6938,11 @@ Availability: NNTP If _s_e_t, the newsserver will be asked for new newsgroups on entering the - - The Mutt Next Generation E-Mail Client 124 - browser. Otherwise, it will be done only once for a newsserver. Also controls whether or not the number of new articles of subscribed newsgroups will be checked. - _6_._4_._1_6_2 _n_n_t_p___s_h_o_w___o_n_l_y___u_n_r_e_a_d + _7_._4_._1_7_8 _n_n_t_p___s_h_o_w___o_n_l_y___u_n_r_e_a_d Type: boolean @@ -6443,7 +6953,7 @@ If _s_e_t, only subscribed newsgroups that contain unread articles will be dis- played in the newsgroup browser. - _6_._4_._1_6_3 _n_n_t_p___u_s_e_r + _7_._4_._1_7_9 _n_n_t_p___u_s_e_r Type: string @@ -6454,18 +6964,20 @@ Your login name on the NNTP server. If _u_n_s_e_t and the server requires authen- tification, Mutt-ng will prompt you for your account name. - _6_._4_._1_6_4 _n_n_t_p___x___c_o_m_m_e_n_t___t_o + _7_._4_._1_8_0 _n_n_t_p___x___c_o_m_m_e_n_t___t_o Type: boolean Default: no + The Mutt Next Generation E-Mail Client 134 + Availability: NNTP If _s_e_t, Mutt-ng will add a ``X-Comment-To:'' header field (that contains full name of the original article author) to articles that you followup to. - _6_._4_._1_6_5 _o_p_e_r_a_t_i_n_g___s_y_s_t_e_m + _7_._4_._1_8_1 _o_p_e_r_a_t_i_n_g___s_y_s_t_e_m Type: string @@ -6477,14 +6989,12 @@ It may, for example, look as: ``mutt-ng 1.5.9i (Linux)''. - _6_._4_._1_6_6 _p_a_g_e_r + _7_._4_._1_8_2 _p_a_g_e_r Type: path Default: 'builtin' - The Mutt Next Generation E-Mail Client 125 - This variable specifies which pager you would like to use to view messages. ``builtin'' means to use the builtin pager, otherwise this variable should specify the pathname of the external pager you would like to use. @@ -6494,7 +7004,7 @@ screen resizes cause lines longer than the screen width to be badly formatted in the help menu. - _6_._4_._1_6_7 _p_a_g_e_r___c_o_n_t_e_x_t + _7_._4_._1_8_3 _p_a_g_e_r___c_o_n_t_e_x_t Type: number @@ -6505,7 +7015,7 @@ will display the line after the last one on the screen at the top of the next page (0 lines of context). - _6_._4_._1_6_8 _p_a_g_e_r___f_o_r_m_a_t + _7_._4_._1_8_4 _p_a_g_e_r___f_o_r_m_a_t Type: string @@ -6513,10 +7023,12 @@ This variable controls the format of the one-line message ``status'' displayed before each message in either the internal or an external pager. The valid - sequences are listed in the ``_$_i_n_d_e_x___f_o_r_m_a_t (section 6.4.110 , page 108)'' + sequences are listed in the ``_$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.116 , page 116)'' section. - _6_._4_._1_6_9 _p_a_g_e_r___i_n_d_e_x___l_i_n_e_s + The Mutt Next Generation E-Mail Client 135 + + _7_._4_._1_8_5 _p_a_g_e_r___i_n_d_e_x___l_i_n_e_s Type: number @@ -6533,18 +7045,16 @@ folder is less than _p_a_g_e_r___i_n_d_e_x___l_i_n_e_s, then the index will only use as many lines as it needs. - _6_._4_._1_7_0 _p_a_g_e_r___s_t_o_p + _7_._4_._1_8_6 _p_a_g_e_r___s_t_o_p Type: boolean Default: no - The Mutt Next Generation E-Mail Client 126 - When _s_e_t, the internal-pager will nnoott move to the next message when you are at the end of a message and invoke the _n_e_x_t_-_p_a_g_e function. - _6_._4_._1_7_1 _p_g_p___a_u_t_o___d_e_c_o_d_e + _7_._4_._1_8_7 _p_g_p___a_u_t_o___d_e_c_o_d_e Type: boolean @@ -6557,7 +7067,7 @@ ditional-pgp function, Mutt-ng will automatically check the message for tradi- tional pgp. - _6_._4_._1_7_2 _p_g_p___a_u_t_o_i_n_l_i_n_e + _7_._4_._1_8_8 _p_g_p___a_u_t_o_i_n_l_i_n_e Type: boolean @@ -6570,12 +7080,14 @@ Note that Mutt-ng might automatically use PGP/MIME for messages which consist of more than a single MIME part. Mutt-ng can be configured to ask before send- ing PGP/MIME messages when inline (traditional) would not work. See also: - ``_$_p_g_p___m_i_m_e___a_u_t_o (section 6.4.188 , page 129)''. + ``_$_p_g_p___m_i_m_e___a_u_t_o (section 7.4.204 , page 139)''. + + The Mutt Next Generation E-Mail Client 136 Also note that using the old-style PGP message format is ssttrroonnggllyy ddeepprreeccaatteedd. (PGP only) - _6_._4_._1_7_3 _p_g_p___c_h_e_c_k___e_x_i_t + _7_._4_._1_8_9 _p_g_p___c_h_e_c_k___e_x_i_t Type: boolean @@ -6584,7 +7096,7 @@ If _s_e_t, Mutt-ng will check the exit code of the PGP subprocess when signing or encrypting. A non-zero exit code means that the subprocess failed. (PGP only) - _6_._4_._1_7_4 _p_g_p___c_l_e_a_r_s_i_g_n___c_o_m_m_a_n_d + _7_._4_._1_9_0 _p_g_p___c_l_e_a_r_s_i_g_n___c_o_m_m_a_n_d Type: string @@ -6594,9 +7106,7 @@ Note that the use of this format is ssttrroonnggllyy ddeepprreeccaatteedd. (PGP only) - The Mutt Next Generation E-Mail Client 127 - - _6_._4_._1_7_5 _p_g_p___d_e_c_o_d_e___c_o_m_m_a_n_d + _7_._4_._1_9_1 _p_g_p___d_e_c_o_d_e___c_o_m_m_a_n_d Type: string @@ -6619,7 +7129,7 @@ multipart/signed attachment when verifying it. %a - The value of _$_p_g_p___s_i_g_n___a_s (section 6.4.192 , page 130). + The value of _$_p_g_p___s_i_g_n___a_s (section 7.4.208 , page 140). %r One or more key IDs. @@ -6629,7 +7139,9 @@ subdirectory which has been installed on your system alongside the documenta- tion. (PGP only) - _6_._4_._1_7_6 _p_g_p___d_e_c_r_y_p_t___c_o_m_m_a_n_d + The Mutt Next Generation E-Mail Client 137 + + _7_._4_._1_9_2 _p_g_p___d_e_c_r_y_p_t___c_o_m_m_a_n_d Type: string @@ -6637,7 +7149,7 @@ This command is used to decrypt a PGP encrypted message. (PGP only) - _6_._4_._1_7_7 _p_g_p___e_n_c_r_y_p_t___o_n_l_y___c_o_m_m_a_n_d + _7_._4_._1_9_3 _p_g_p___e_n_c_r_y_p_t___o_n_l_y___c_o_m_m_a_n_d Type: string @@ -6645,25 +7157,23 @@ This command is used to encrypt a body part without signing it. (PGP only) - _6_._4_._1_7_8 _p_g_p___e_n_c_r_y_p_t___s_i_g_n___c_o_m_m_a_n_d + _7_._4_._1_9_4 _p_g_p___e_n_c_r_y_p_t___s_i_g_n___c_o_m_m_a_n_d Type: string Default: '' - The Mutt Next Generation E-Mail Client 128 - This command is used to both sign and encrypt a body part. (PGP only) - _6_._4_._1_7_9 _p_g_p___e_n_t_r_y___f_o_r_m_a_t + _7_._4_._1_9_5 _p_g_p___e_n_t_r_y___f_o_r_m_a_t Type: string Default: '%4n %t%f %4l/0x%k %-4a %2c %u' This variable allows you to customize the PGP key selection menu to your per- - sonal taste. This string is similar to ``_$_i_n_d_e_x___f_o_r_m_a_t (section 6.4.110 , page - 108)'', but has its own set of printf(3)-like sequences: + sonal taste. This string is similar to ``_$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.116 , page + 116)'', but has its own set of printf(3)-like sequences: %n number @@ -6686,6 +7196,8 @@ %c capabilities + The Mutt Next Generation E-Mail Client 138 + %t trust/validity of the key-uid association @@ -6694,7 +7206,7 @@ (PGP only) - _6_._4_._1_8_0 _p_g_p___e_x_p_o_r_t___c_o_m_m_a_n_d + _7_._4_._1_9_6 _p_g_p___e_x_p_o_r_t___c_o_m_m_a_n_d Type: string @@ -6703,29 +7215,27 @@ This command is used to export a public key from the user's key ring. (PGP only) - _6_._4_._1_8_1 _p_g_p___g_e_t_k_e_y_s___c_o_m_m_a_n_d + _7_._4_._1_9_7 _p_g_p___g_e_t_k_e_y_s___c_o_m_m_a_n_d Type: string - The Mutt Next Generation E-Mail Client 129 - Default: '' This command is invoked whenever Mutt-ng will need public key information. %r is the only printf(3)-like sequence used with this format. (PGP only) - _6_._4_._1_8_2 _p_g_p___g_o_o_d___s_i_g_n + _7_._4_._1_9_8 _p_g_p___g_o_o_d___s_i_g_n Type: regular expression Default: '' If you assign a text to this variable, then a PGP signature is only considered - verified if the output from _$_p_g_p___v_e_r_i_f_y___c_o_m_m_a_n_d (section 6.4.198 , page 131) + verified if the output from _$_p_g_p___v_e_r_i_f_y___c_o_m_m_a_n_d (section 7.4.214 , page 141) contains the text. Use this variable if the exit code from the command is 0 even for bad signatures. (PGP only) - _6_._4_._1_8_3 _p_g_p___i_g_n_o_r_e___s_u_b_k_e_y_s + _7_._4_._1_9_9 _p_g_p___i_g_n_o_r_e___s_u_b_k_e_y_s Type: boolean @@ -6735,16 +7245,19 @@ the principal key will inherit the subkeys' capabilities. _U_n_s_e_t this if you want to play interesting key selection games. (PGP only) - _6_._4_._1_8_4 _p_g_p___i_m_p_o_r_t___c_o_m_m_a_n_d + _7_._4_._2_0_0 _p_g_p___i_m_p_o_r_t___c_o_m_m_a_n_d Type: string Default: '' This command is used to import a key from a message into the user's public key + + The Mutt Next Generation E-Mail Client 139 + ring. (PGP only) - _6_._4_._1_8_5 _p_g_p___l_i_s_t___p_u_b_r_i_n_g___c_o_m_m_a_n_d + _7_._4_._2_0_1 _p_g_p___l_i_s_t___p_u_b_r_i_n_g___c_o_m_m_a_n_d Type: string @@ -6756,22 +7269,19 @@ This format is also generated by the pgpring utility which comes with Mutt-ng. (PGP only) - _6_._4_._1_8_6 _p_g_p___l_i_s_t___s_e_c_r_i_n_g___c_o_m_m_a_n_d + _7_._4_._2_0_2 _p_g_p___l_i_s_t___s_e_c_r_i_n_g___c_o_m_m_a_n_d Type: string Default: '' This command is used to list the secret key ring's contents. The output format - - The Mutt Next Generation E-Mail Client 130 - must be analogous to the one used by gpg --list-keys --with-colons. This format is also generated by the pgpring utility which comes with Mutt-ng. (PGP only) - _6_._4_._1_8_7 _p_g_p___l_o_n_g___i_d_s + _7_._4_._2_0_3 _p_g_p___l_o_n_g___i_d_s Type: boolean @@ -6780,7 +7290,7 @@ If _s_e_t, use 64 bit PGP key IDs. _U_n_s_e_t uses the normal 32 bit Key IDs. (PGP only) - _6_._4_._1_8_8 _p_g_p___m_i_m_e___a_u_t_o + _7_._4_._2_0_4 _p_g_p___m_i_m_e___a_u_t_o Type: quadoption @@ -6793,12 +7303,14 @@ Also note that using the old-style PGP message format is ssttrroonnggllyy ddeepprreeccaatteedd. (PGP only) - _6_._4_._1_8_9 _p_g_p___r_e_p_l_y_i_n_l_i_n_e + _7_._4_._2_0_5 _p_g_p___r_e_p_l_y_i_n_l_i_n_e Type: boolean Default: no + The Mutt Next Generation E-Mail Client 140 + Setting this variable will cause Mutt-ng to always attempt to create an inline (traditional) message when replying to a message which is PGP encrypted/signed inline. This can be overridden by use of the _p_g_p_-_m_e_n_u, when inline is not @@ -6809,19 +7321,17 @@ Note that Mutt-ng might automatically use PGP/MIME for messages which consist of more than a single MIME part. Mutt-ng can be configured to ask before send- ing PGP/MIME messages when inline (traditional) would not work. See also: - ``_$_p_g_p___m_i_m_e___a_u_t_o (section 6.4.188 , page 129)''. + ``_$_p_g_p___m_i_m_e___a_u_t_o (section 7.4.204 , page 139)''. Also note that using the old-style PGP message format is ssttrroonnggllyy ddeepprreeccaatteedd. (PGP only) - _6_._4_._1_9_0 _p_g_p___r_e_t_a_i_n_a_b_l_e___s_i_g_s + _7_._4_._2_0_6 _p_g_p___r_e_t_a_i_n_a_b_l_e___s_i_g_s Type: boolean Default: no - The Mutt Next Generation E-Mail Client 131 - If _s_e_t, signed and encrypted messages will consist of nested multipart/signed and multipart/encrypted body parts. @@ -6829,7 +7339,7 @@ the outer layer (multipart/encrypted) can be easily removed, while the inner multipart/signed part is retained. (PGP only) - _6_._4_._1_9_1 _p_g_p___s_h_o_w___u_n_u_s_a_b_l_e + _7_._4_._2_0_7 _p_g_p___s_h_o_w___u_n_u_s_a_b_l_e Type: boolean @@ -6839,7 +7349,7 @@ This includes keys which have been revoked, have expired, or have been marked as ``disabled'' by the user. (PGP only) - _6_._4_._1_9_2 _p_g_p___s_i_g_n___a_s + _7_._4_._2_0_8 _p_g_p___s_i_g_n___a_s Type: string @@ -6849,16 +7359,18 @@ your private keys to use. It is recommended that you use the keyid form to specify your key (e.g., ``0x00112233''). (PGP only) - _6_._4_._1_9_3 _p_g_p___s_i_g_n___c_o_m_m_a_n_d + _7_._4_._2_0_9 _p_g_p___s_i_g_n___c_o_m_m_a_n_d Type: string Default: '' + The Mutt Next Generation E-Mail Client 141 + This command is used to create the detached PGP signature for a multi- part/signed PGP/MIME body part. (PGP only) - _6_._4_._1_9_4 _p_g_p___s_o_r_t___k_e_y_s + _7_._4_._2_1_0 _p_g_p___s_o_r_t___k_e_y_s Type: sort order @@ -6876,15 +7388,13 @@ date sort by key creation date - The Mutt Next Generation E-Mail Client 132 - trust sort by the trust of the key If you prefer reverse order of the above values, prefix it with ``reverse-''. (PGP only) - _6_._4_._1_9_5 _p_g_p___s_t_r_i_c_t___e_n_c + _7_._4_._2_1_1 _p_g_p___s_t_r_i_c_t___e_n_c Type: boolean @@ -6895,7 +7405,7 @@ non-verifyable PGP signatures, so only change this if you know what you are doing. (PGP only) - _6_._4_._1_9_6 _p_g_p___t_i_m_e_o_u_t + _7_._4_._2_1_2 _p_g_p___t_i_m_e_o_u_t Type: number @@ -6904,7 +7414,7 @@ The number of seconds after which a cached passphrase will expire if not used. Default: 300. (PGP only) - _6_._4_._1_9_7 _p_g_p___u_s_e___g_p_g___a_g_e_n_t + _7_._4_._2_1_3 _p_g_p___u_s_e___g_p_g___a_g_e_n_t Type: boolean @@ -6912,7 +7422,9 @@ If _s_e_t, Mutt-ng will use a possibly-running gpg-agent process. (PGP only) - _6_._4_._1_9_8 _p_g_p___v_e_r_i_f_y___c_o_m_m_a_n_d + The Mutt Next Generation E-Mail Client 142 + + _7_._4_._2_1_4 _p_g_p___v_e_r_i_f_y___c_o_m_m_a_n_d Type: string @@ -6920,7 +7432,7 @@ This command is used to verify PGP signatures. (PGP only) - _6_._4_._1_9_9 _p_g_p___v_e_r_i_f_y___k_e_y___c_o_m_m_a_n_d + _7_._4_._2_1_5 _p_g_p___v_e_r_i_f_y___k_e_y___c_o_m_m_a_n_d Type: string @@ -6929,19 +7441,17 @@ This command is used to verify key information from the key selection menu. (PGP only) - _6_._4_._2_0_0 _p_i_p_e___d_e_c_o_d_e + _7_._4_._2_1_6 _p_i_p_e___d_e_c_o_d_e Type: boolean - The Mutt Next Generation E-Mail Client 133 - Default: no Used in connection with the _p_i_p_e_-_m_e_s_s_a_g_e command. When _u_n_s_e_t, Mutt-ng will pipe the messages without any preprocessing. When _s_e_t, Mutt-ng will weed head- ers and will attempt to PGP/MIME decode the messages first. - _6_._4_._2_0_1 _p_i_p_e___s_e_p + _7_._4_._2_1_7 _p_i_p_e___s_e_p Type: string @@ -6950,7 +7460,7 @@ The separator to add between messages when piping a list of tagged messages to an external Unix command. - _6_._4_._2_0_2 _p_i_p_e___s_p_l_i_t + _7_._4_._2_1_8 _p_i_p_e___s_p_l_i_t Type: boolean @@ -6961,14 +7471,16 @@ of tagged messages Mutt-ng will concatenate the messages and will pipe them as a single folder. When _s_e_t, Mutt-ng will pipe the messages one by one. In both cases the messages are piped in the current sorted order, and the ``_$_p_i_p_e___s_e_p - (section 6.4.201 , page 132)'' separator is added after each message. + (section 7.4.217 , page 142)'' separator is added after each message. - _6_._4_._2_0_3 _p_o_p___a_u_t_h___t_r_y___a_l_l + _7_._4_._2_1_9 _p_o_p___a_u_t_h___t_r_y___a_l_l Type: boolean Default: yes + The Mutt Next Generation E-Mail Client 143 + Availability: POP If _s_e_t, Mutt-ng will try all available methods. When _u_n_s_e_t, Mutt-ng will only @@ -6976,7 +7488,7 @@ able. If a method is available but authentication fails, Mutt-ng will not con- nect to the POP server. - _6_._4_._2_0_4 _p_o_p___a_u_t_h_e_n_t_i_c_a_t_o_r_s + _7_._4_._2_2_0 _p_o_p___a_u_t_h_e_n_t_i_c_a_t_o_r_s Type: string @@ -6989,15 +7501,13 @@ tication methods are either ``user'', ``apop'' or any SASL mechanism, eg ``digest-md5'', ``gssapi'' or ``cram-md5''. - The Mutt Next Generation E-Mail Client 134 - This parameter is case-insensitive. If this parameter is _u_n_s_e_t (the default) Mutt-ng will try all available methods, in order from most-secure to least- secure. Example: set pop_authenticators='digest-md5:apop:user' - _6_._4_._2_0_5 _p_o_p___d_e_l_e_t_e + _7_._4_._2_2_1 _p_o_p___d_e_l_e_t_e Type: quadoption @@ -7009,7 +7519,7 @@ server when using the ``fetch-mail'' function. When _u_n_s_e_t, Mutt-ng will down- load messages but also leave them on the POP server. - _6_._4_._2_0_6 _p_o_p___h_o_s_t + _7_._4_._2_2_2 _p_o_p___h_o_s_t Type: string @@ -7025,7 +7535,9 @@ NNoottee:: Storing passwords in a configuration file presents a security risk since the superuser of your machine may read it regardless of the file's permissions. - _6_._4_._2_0_7 _p_o_p___l_a_s_t + The Mutt Next Generation E-Mail Client 144 + + _7_._4_._2_2_3 _p_o_p___l_a_s_t Type: boolean @@ -7037,7 +7549,7 @@ retrieving only unread messages from the POP server when using the ``fetch- mail'' function. - _6_._4_._2_0_8 _p_o_p___m_a_i_l___c_h_e_c_k + _7_._4_._2_2_4 _p_o_p___m_a_i_l___c_h_e_c_k Type: number @@ -7045,11 +7557,9 @@ Availability: POP - The Mutt Next Generation E-Mail Client 135 - This variable configures how often (in seconds) POP should look for new mail. - _6_._4_._2_0_9 _p_o_p___p_a_s_s + _7_._4_._2_2_5 _p_o_p___p_a_s_s Type: string @@ -7063,7 +7573,7 @@ NNoottee:: Storing passwords in a configuration file presents a security risk since the superuser of your machine may read it regardless of the file's permissions. - _6_._4_._2_1_0 _p_o_p___r_e_c_o_n_n_e_c_t + _7_._4_._2_2_6 _p_o_p___r_e_c_o_n_n_e_c_t Type: quadoption @@ -7074,7 +7584,7 @@ Controls whether or not Mutt-ng will try to reconnect to a POP server when the connection is lost. - _6_._4_._2_1_1 _p_o_p___u_s_e_r + _7_._4_._2_2_7 _p_o_p___u_s_e_r Type: string @@ -7082,43 +7592,43 @@ Availability: POP + The Mutt Next Generation E-Mail Client 145 + Your login name on the POP server. This variable defaults to your user name on the local machine. - _6_._4_._2_1_2 _p_o_s_t___i_n_d_e_n_t___s_t_r_i_n_g + _7_._4_._2_2_8 _p_o_s_t___i_n_d_e_n_t___s_t_r_i_n_g Type: string Default: '' - Similar to the ``_$_a_t_t_r_i_b_u_t_i_o_n (section 6.4.15 , page 86)'' variable, Mutt-ng + Similar to the ``_$_a_t_t_r_i_b_u_t_i_o_n (section 7.4.18 , page 94)'' variable, Mutt-ng will append this string after the inclusion of a message which is being replied to. - _6_._4_._2_1_3 _p_o_s_t_p_o_n_e + _7_._4_._2_2_9 _p_o_s_t_p_o_n_e Type: quadoption Default: ask-yes - The Mutt Next Generation E-Mail Client 136 - Controls whether or not messages are saved in the ``_$_p_o_s_t_p_o_n_e_d (section - 6.4.214 , page 135)'' mailbox when you elect not to send immediately. + 7.4.230 , page 145)'' mailbox when you elect not to send immediately. - _6_._4_._2_1_4 _p_o_s_t_p_o_n_e_d + _7_._4_._2_3_0 _p_o_s_t_p_o_n_e_d Type: path Default: '~/postponed' - Mutt-ng allows you to indefinitely ``_p_o_s_t_p_o_n_e (section 6.4.213 , page 134) + Mutt-ng allows you to indefinitely ``_p_o_s_t_p_o_n_e (section 7.4.229 , page 145) sending a message'' which you are editing. When you choose to postpone a mes- sage, Mutt-ng saves it in the mailbox specified by this variable. Also see the - ``_$_p_o_s_t_p_o_n_e (section 6.4.213 , page 134)'' variable. + ``_$_p_o_s_t_p_o_n_e (section 7.4.229 , page 145)'' variable. - _6_._4_._2_1_5 _p_r_e_c_o_n_n_e_c_t + _7_._4_._2_3_1 _p_r_e_c_o_n_n_e_c_t Type: string @@ -7137,7 +7647,9 @@ NNoottee:: For this example to work, you must be able to log in to the remote machine without having to enter a password. - _6_._4_._2_1_6 _p_r_i_n_t + The Mutt Next Generation E-Mail Client 146 + + _7_._4_._2_3_2 _p_r_i_n_t Type: quadoption @@ -7146,7 +7658,7 @@ Controls whether or not Mutt-ng really prints messages. This is set to _a_s_k_-_n_o by default, because some people accidentally hit ``p'' often. - _6_._4_._2_1_7 _p_r_i_n_t___c_o_m_m_a_n_d + _7_._4_._2_3_3 _p_r_i_n_t___c_o_m_m_a_n_d Type: path @@ -7154,49 +7666,50 @@ This specifies the command pipe that should be used to print messages. - _6_._4_._2_1_8 _p_r_i_n_t___d_e_c_o_d_e + _7_._4_._2_3_4 _p_r_i_n_t___d_e_c_o_d_e Type: boolean - The Mutt Next Generation E-Mail Client 137 - Default: yes Used in connection with the print-message command. If this option is _s_e_t, the message is decoded before it is passed to the external command specified by - _$_p_r_i_n_t___c_o_m_m_a_n_d (section 6.4.217 , page 135). If this option is _u_n_s_e_t, no pro- + _$_p_r_i_n_t___c_o_m_m_a_n_d (section 7.4.233 , page 146). If this option is _u_n_s_e_t, no pro- cessing will be applied to the message when printing it. The latter setting may be useful if you are using some advanced printer filter which is able to properly format e-mail messages for printing. - _6_._4_._2_1_9 _p_r_i_n_t___s_p_l_i_t + _7_._4_._2_3_5 _p_r_i_n_t___s_p_l_i_t Type: boolean Default: no Used in connection with the print-message command. If this option is _s_e_t, the - command specified by _$_p_r_i_n_t___c_o_m_m_a_n_d (section 6.4.217 , page 135) is executed + command specified by _$_p_r_i_n_t___c_o_m_m_a_n_d (section 7.4.233 , page 146) is executed once for each message which is to be printed. If this option is _u_n_s_e_t, the - command specified by _$_p_r_i_n_t___c_o_m_m_a_n_d (section 6.4.217 , page 135) is executed + command specified by _$_p_r_i_n_t___c_o_m_m_a_n_d (section 7.4.233 , page 146) is executed only once, and all the messages are concatenated, with a form feed as the mes- sage separator. Those who use the enscript(1) program's mail-printing mode will most likely want to set this option. - _6_._4_._2_2_0 _p_r_o_m_p_t___a_f_t_e_r + _7_._4_._2_3_6 _p_r_o_m_p_t___a_f_t_e_r Type: boolean Default: yes - If you use an _e_x_t_e_r_n_a_l ``_$_p_a_g_e_r (section 6.4.166 , page 123)'', setting this + If you use an _e_x_t_e_r_n_a_l ``_$_p_a_g_e_r (section 7.4.182 , page 134)'', setting this variable will cause Mutt-ng to prompt you for a command when the pager exits + + The Mutt Next Generation E-Mail Client 147 + rather than returning to the index menu. If _u_n_s_e_t, Mutt-ng will return to the index menu when the external pager exits. - _6_._4_._2_2_1 _q_u_e_r_y___c_o_m_m_a_n_d + _7_._4_._2_3_7 _q_u_e_r_y___c_o_m_m_a_n_d Type: path @@ -7204,33 +7717,30 @@ This specifies the command that Mutt-ng will use to make external address queries. The string should contain a %s, which will be substituted with the - query string the user types. See ``_q_u_e_r_y (section 4.7 , page 55)'' for more + query string the user types. See ``_q_u_e_r_y (section 4.7 , page 59)'' for more information. - _6_._4_._2_2_2 _q_u_i_t + _7_._4_._2_3_8 _q_u_i_t Type: quadoption Default: yes This variable controls whether ``quit'' and ``exit'' actually quit from Mutt- - - The Mutt Next Generation E-Mail Client 138 - ng. If it set to _y_e_s, they do quit, if it is set to _n_o, they have no effect, and if it is set to _a_s_k_-_y_e_s or _a_s_k_-_n_o, you are prompted for confirmation when you try to quit. - _6_._4_._2_2_3 _q_u_o_t_e___e_m_p_t_y + _7_._4_._2_3_9 _q_u_o_t_e___e_m_p_t_y Type: boolean Default: yes Controls whether or not empty lines will be quoted using ``_i_n_d_e_n_t___s_t_r_i_n_g (sec- - tion 6.4.109 , page 108)''. + tion 7.4.115 , page 116)''. - _6_._4_._2_2_4 _q_u_o_t_e___q_u_o_t_e_d + _7_._4_._2_4_0 _q_u_o_t_e___q_u_o_t_e_d Type: boolean @@ -7238,9 +7748,9 @@ Controls how quoted lines will be quoted. If _s_e_t, one quote character will be added to the end of existing prefix. Otherwise, quoted lines will be prepended - by ``_i_n_d_e_n_t___s_t_r_i_n_g (section 6.4.109 , page 108)''. + by ``_i_n_d_e_n_t___s_t_r_i_n_g (section 7.4.115 , page 116)''. - _6_._4_._2_2_5 _q_u_o_t_e___r_e_g_e_x_p + _7_._4_._2_4_1 _q_u_o_t_e___r_e_g_e_x_p Type: regular expression @@ -7250,10 +7760,13 @@ text in the body of a message. NNoottee:: In order to use the _q_u_o_t_e_dxx patterns in the internal pager, you need to + + The Mutt Next Generation E-Mail Client 148 + set this to a regular expression that matches _e_x_a_c_t_l_y the quote characters at the beginning of quoted lines. - _6_._4_._2_2_6 _r_e_a_d___i_n_c + _7_._4_._2_4_2 _r_e_a_d___i_n_c Type: number @@ -7267,11 +7780,9 @@ time. When set to 0, only a single message will appear before the reading the mailbox. - Also see the ``_$_w_r_i_t_e___i_n_c (section 6.4.340 , page 165)'' variable. + Also see the ``_$_w_r_i_t_e___i_n_c (section 7.4.355 , page 175)'' variable. - _6_._4_._2_2_7 _r_e_a_d___o_n_l_y - - The Mutt Next Generation E-Mail Client 139 + _7_._4_._2_4_3 _r_e_a_d___o_n_l_y Type: boolean @@ -7279,7 +7790,7 @@ If set, all folders are opened in read-only mode. - _6_._4_._2_2_8 _r_e_a_l_n_a_m_e + _7_._4_._2_4_4 _r_e_a_l_n_a_m_e Type: string @@ -7291,20 +7802,22 @@ By default, this is the GECOS field from /etc/passwd. _N_o_t_e_: This variable will _n_o_t be used when the user has set a real name in the - _$_f_r_o_m (section 6.4.74 , page 100) variable. + _$_f_r_o_m (section 7.4.80 , page 108) variable. - _6_._4_._2_2_9 _r_e_c_a_l_l + _7_._4_._2_4_5 _r_e_c_a_l_l Type: quadoption Default: ask-yes Controls whether or not Mutt-ng recalls postponed messages when composing a new - message. Also see ``_$_p_o_s_t_p_o_n_e_d (section 6.4.214 , page 135)''. + message. Also see ``_$_p_o_s_t_p_o_n_e_d (section 7.4.230 , page 145)''. Setting this variable to _y_e_s is not generally useful, and thus not recommended. - _6_._4_._2_3_0 _r_e_c_o_r_d + _7_._4_._2_4_6 _r_e_c_o_r_d + + The Mutt Next Generation E-Mail Client 149 Type: path @@ -7312,28 +7825,25 @@ This specifies the file into which your outgoing messages should be appended. (This is meant as the primary method for saving a copy of your messages, but - another way to do this is using the ``_m_y___h_d_r (section 3.15 , page 34)'' com- + another way to do this is using the ``_m_y___h_d_r (section 3.16 , page 38)'' com- mand to create a Bcc: header field with your email address in it.) - The value of _$_r_e_c_o_r_d _(_s_e_c_t_i_o_n _6_._4_._2_3_0 _, _p_a_g_e _1_3_8_) is overridden by the - ``_$_f_o_r_c_e___n_a_m_e (section 6.4.68 , page 98)'' and ``_$_s_a_v_e___n_a_m_e (section - 6.4.241 , page 141)'' variables, and the ``_f_c_c_-_h_o_o_k (section 3.18 , page - 35)'' command. + The value of _$_r_e_c_o_r_d _(_s_e_c_t_i_o_n _7_._4_._2_4_6 _, _p_a_g_e _1_4_8_) is overridden by the + ``_$_f_o_r_c_e___n_a_m_e (section 7.4.74 , page 107)'' and ``_$_s_a_v_e___n_a_m_e (section + 7.4.257 , page 151)'' variables, and the ``_f_c_c_-_h_o_o_k (section 3.19 , page + 39)'' command. - _6_._4_._2_3_1 _r_e_p_l_y___r_e_g_e_x_p + _7_._4_._2_4_7 _r_e_p_l_y___r_e_g_e_x_p Type: regular expression Default: '^(re([\[0-9\]+])*|aw):[ \t]*' - A regular expression used to recognize reply messages when threading and - - The Mutt Next Generation E-Mail Client 140 - - replying. The default value corresponds to the English ``Re:'' and the German + A regular expression used to recognize reply messages when threading and reply- + ing. The default value corresponds to the English ``Re:'' and the German ``Aw:''. - _6_._4_._2_3_2 _r_e_p_l_y___s_e_l_f + _7_._4_._2_4_8 _r_e_p_l_y___s_e_l_f Type: boolean @@ -7343,7 +7853,7 @@ that you want to reply to the recipients of that message rather than to your- self. - _6_._4_._2_3_3 _r_e_p_l_y___t_o + _7_._4_._2_4_9 _r_e_p_l_y___t_o Type: quadoption @@ -7357,17 +7867,19 @@ header field to the list address and you want to send a private message to the author of a message. - _6_._4_._2_3_4 _r_e_s_o_l_v_e + _7_._4_._2_5_0 _r_e_s_o_l_v_e Type: boolean Default: yes + The Mutt Next Generation E-Mail Client 150 + When set, the cursor will be automatically advanced to the next (possibly undeleted) message whenever a command that modifies the current message is exe- cuted. - _6_._4_._2_3_5 _r_e_v_e_r_s_e___a_l_i_a_s + _7_._4_._2_5_1 _r_e_v_e_r_s_e___a_l_i_a_s Type: boolean @@ -7384,13 +7896,10 @@ From: abd30425@somewhere.net It would be displayed in the index menu as ``Joe User'' instead of - - The Mutt Next Generation E-Mail Client 141 - ``abd30425@somewhere.net.'' This is useful when the person's e-mail address is not human friendly (like CompuServe addresses). - _6_._4_._2_3_6 _r_e_v_e_r_s_e___n_a_m_e + _7_._4_._2_5_2 _r_e_v_e_r_s_e___n_a_m_e Type: boolean @@ -7404,22 +7913,24 @@ would be used doesn't match your alternates, the From: line will use your address on the current machine. - _6_._4_._2_3_7 _r_e_v_e_r_s_e___r_e_a_l_n_a_m_e + _7_._4_._2_5_3 _r_e_v_e_r_s_e___r_e_a_l_n_a_m_e Type: boolean Default: yes - This variable fine-tunes the behaviour of the _r_e_v_e_r_s_e___n_a_m_e (section 6.4.236 , - page 140) feature. When it is _s_e_t, Mutt-ng will use the address from incoming + This variable fine-tunes the behaviour of the _r_e_v_e_r_s_e___n_a_m_e (section 7.4.252 , + page 150) feature. When it is _s_e_t, Mutt-ng will use the address from incoming messages as-is, possibly including eventual real names. When it is _u_n_s_e_t, Mutt-ng will override any such real names with the setting of the _r_e_a_l_n_a_m_e - (section 6.4.228 , page 138) variable. + (section 7.4.244 , page 148) variable. - _6_._4_._2_3_8 _r_f_c_2_0_4_7___p_a_r_a_m_e_t_e_r_s + _7_._4_._2_5_4 _r_f_c_2_0_4_7___p_a_r_a_m_e_t_e_r_s Type: boolean + The Mutt Next Generation E-Mail Client 151 + Default: no When this variable is _s_e_t, Mutt-ng will decode RFC-2047-encoded MIME parame- @@ -7438,33 +7949,31 @@ _g_e_n_e_r_a_t_e_s this kind of encoding. Instead, Mutt-ng will unconditionally use the encoding specified in RFC 2231. - _6_._4_._2_3_9 _s_a_v_e___a_d_d_r_e_s_s + _7_._4_._2_5_5 _s_a_v_e___a_d_d_r_e_s_s Type: boolean - The Mutt Next Generation E-Mail Client 142 - Default: no If _s_e_t, Mutt-ng will take the sender's full address when choosing a default - folder for saving a mail. If ``_$_s_a_v_e___n_a_m_e (section 6.4.241 , page 141)'' or - ``_$_f_o_r_c_e___n_a_m_e (section 6.4.68 , page 98)'' is _s_e_t too, the selection of the + folder for saving a mail. If ``_$_s_a_v_e___n_a_m_e (section 7.4.257 , page 151)'' or + ``_$_f_o_r_c_e___n_a_m_e (section 7.4.74 , page 107)'' is _s_e_t too, the selection of the fcc folder will be changed as well. - _6_._4_._2_4_0 _s_a_v_e___e_m_p_t_y + _7_._4_._2_5_6 _s_a_v_e___e_m_p_t_y Type: boolean Default: yes When _u_n_s_e_t, mailboxes which contain no saved messages will be removed when - closed (the exception is ``_$_s_p_o_o_l_f_i_l_e (section 6.4.297 , page 154)'' which is + closed (the exception is ``_$_s_p_o_o_l_f_i_l_e (section 7.4.313 , page 165)'' which is never removed). If _s_e_t, mailboxes are never removed. NNoottee:: This only applies to mbox and MMDF folders, Mutt-ng does not delete MH and Maildir directories. - _6_._4_._2_4_1 _s_a_v_e___n_a_m_e + _7_._4_._2_5_7 _s_a_v_e___n_a_m_e Type: boolean @@ -7472,14 +7981,16 @@ This variable controls how copies of outgoing messages are saved. When set, a check is made to see if a mailbox specified by the recipient address exists - (this is done by searching for a mailbox in the ``_$_f_o_l_d_e_r (section 6.4.64 , - page 97)'' directory with the _u_s_e_r_n_a_m_e part of the recipient address). If the + (this is done by searching for a mailbox in the ``_$_f_o_l_d_e_r (section 7.4.70 , + page 105)'' directory with the _u_s_e_r_n_a_m_e part of the recipient address). If the mailbox exists, the outgoing message will be saved to that mailbox, otherwise - the message is saved to the ``_$_r_e_c_o_r_d (section 6.4.230 , page 138)'' mailbox. + the message is saved to the ``_$_r_e_c_o_r_d (section 7.4.246 , page 148)'' mailbox. - Also see the ``_$_f_o_r_c_e___n_a_m_e (section 6.4.68 , page 98)'' variable. + The Mutt Next Generation E-Mail Client 152 + + Also see the ``_$_f_o_r_c_e___n_a_m_e (section 7.4.74 , page 107)'' variable. - _6_._4_._2_4_2 _s_c_o_r_e + _7_._4_._2_5_8 _s_c_o_r_e Type: boolean @@ -7487,9 +7998,9 @@ When this variable is _u_n_s_e_t, scoring is turned off. This can be useful to selectively disable scoring for certain folders when the ``_$_s_c_o_r_e___t_h_r_e_s_h_- - _o_l_d___d_e_l_e_t_e (section 6.4.243 , page 141)'' variable and friends are used. + _o_l_d___d_e_l_e_t_e (section 7.4.259 , page 152)'' variable and friends are used. - _6_._4_._2_4_3 _s_c_o_r_e___t_h_r_e_s_h_o_l_d___d_e_l_e_t_e + _7_._4_._2_5_9 _s_c_o_r_e___t_h_r_e_s_h_o_l_d___d_e_l_e_t_e Type: number @@ -7498,12 +8009,9 @@ Messages which have been assigned a score equal to or lower than the value of this variable are automatically marked for deletion by Mutt-ng. Since Mutt-ng scores are always greater than or equal to zero, the default setting of this - - The Mutt Next Generation E-Mail Client 143 - variable will never mark a message for deletion. - _6_._4_._2_4_4 _s_c_o_r_e___t_h_r_e_s_h_o_l_d___f_l_a_g + _7_._4_._2_6_0 _s_c_o_r_e___t_h_r_e_s_h_o_l_d___f_l_a_g Type: number @@ -7512,7 +8020,7 @@ Messages which have been assigned a score greater than or equal to this vari- able's value are automatically marked ``flagged''. - _6_._4_._2_4_5 _s_c_o_r_e___t_h_r_e_s_h_o_l_d___r_e_a_d + _7_._4_._2_6_1 _s_c_o_r_e___t_h_r_e_s_h_o_l_d___r_e_a_d Type: number @@ -7523,7 +8031,7 @@ scores are always greater than or equal to zero, the default setting of this variable will never mark a message read. - _6_._4_._2_4_6 _s_e_n_d___c_h_a_r_s_e_t + _7_._4_._2_6_2 _s_e_n_d___c_h_a_r_s_e_t Type: string @@ -7531,12 +8039,15 @@ A list of character sets for outgoing messages. Mutt-ng will use the first character set into which the text can be converted exactly. If your ``_$_c_h_a_r_s_e_t - (section 6.4.24 , page 88)'' is not iso-8859-1 and recipients may not under- + (section 7.4.27 , page 96)'' is not iso-8859-1 and recipients may not under- stand UTF-8, it is advisable to include in the list an appropriate widely used standard character set (such as iso-8859-2, koi8-r or iso-2022-jp) either + + The Mutt Next Generation E-Mail Client 153 + instead of or after iso-8859-1. - _6_._4_._2_4_7 _s_e_n_d_m_a_i_l + _7_._4_._2_6_3 _s_e_n_d_m_a_i_l Type: path @@ -7546,18 +8057,16 @@ Mutt-ng expects that the specified program interprets additional arguments as recipient addresses. - _6_._4_._2_4_8 _s_e_n_d_m_a_i_l___w_a_i_t + _7_._4_._2_6_4 _s_e_n_d_m_a_i_l___w_a_i_t Type: number Default: 0 - Specifies the number of seconds to wait for the ``_$_s_e_n_d_m_a_i_l (section 6.4.247 , - page 142)'' process to finish before giving up and putting delivery in the + Specifies the number of seconds to wait for the ``_$_s_e_n_d_m_a_i_l (section 7.4.263 , + page 152)'' process to finish before giving up and putting delivery in the background. - The Mutt Next Generation E-Mail Client 144 - Mutt-ng interprets the value of this variable as follows: >0 @@ -7573,7 +8082,7 @@ will be put in a temporary file. If there is some error, you will be informed as to where to find the output. - _6_._4_._2_4_9 _s_h_e_l_l + _7_._4_._2_6_5 _s_h_e_l_l Type: path @@ -7582,17 +8091,20 @@ Command to use when spawning a subshell. By default, the user's login shell from /etc/passwd is used. - _6_._4_._2_5_0 _s_i_d_e_b_a_r___b_o_u_n_d_a_r_y + _7_._4_._2_6_6 _s_i_d_e_b_a_r___b_o_u_n_d_a_r_y Type: string Default: '.' When the sidebar is displayed and _$_s_i_d_e_b_a_r___s_h_o_r_t_e_n___h_i_e_r_a_r_c_h_y (section - 6.4.254 , page 144) is _s_e_t, this variable specifies the characters at which to + 7.4.270 , page 154) is _s_e_t, this variable specifies the characters at which to + + The Mutt Next Generation E-Mail Client 154 + split a folder name into ``hierarchy items.'' - _6_._4_._2_5_1 _s_i_d_e_b_a_r___d_e_l_i_m + _7_._4_._2_6_7 _s_i_d_e_b_a_r___d_e_l_i_m Type: string @@ -7601,7 +8113,7 @@ This specifies the delimiter between the sidebar (if visible) and other screens. - _6_._4_._2_5_2 _s_i_d_e_b_a_r___n_e_w_m_a_i_l___o_n_l_y + _7_._4_._2_6_8 _s_i_d_e_b_a_r___n_e_w_m_a_i_l___o_n_l_y Type: boolean @@ -7609,12 +8121,10 @@ If _s_e_t, only folders with new mail will be shown in the sidebar. - _6_._4_._2_5_3 _s_i_d_e_b_a_r___n_u_m_b_e_r___f_o_r_m_a_t + _7_._4_._2_6_9 _s_i_d_e_b_a_r___n_u_m_b_e_r___f_o_r_m_a_t Type: string - The Mutt Next Generation E-Mail Client 145 - Default: '%m%?n?(%n)?%?f?[%f]?' This variable controls how message counts are printed when the sidebar is @@ -7646,7 +8156,9 @@ 1) These expandos only have a non-zero value for the current mailbox and will always be zero otherwise. - _6_._4_._2_5_4 _s_i_d_e_b_a_r___s_h_o_r_t_e_n___h_i_e_r_a_r_c_h_y + The Mutt Next Generation E-Mail Client 155 + + _7_._4_._2_7_0 _s_i_d_e_b_a_r___s_h_o_r_t_e_n___h_i_e_r_a_r_c_h_y Type: boolean @@ -7654,27 +8166,24 @@ When _s_e_t, the ``hierarchy'' of the sidebar entries will be shortened only if they cannot be printed in full length (because ``_$_s_i_d_e_b_a_r___w_i_d_t_h (section - 6.4.256 , page 145)'' is set to a too low value). For example, if the news- + 7.4.272 , page 155)'' is set to a too low value). For example, if the news- group name ``de.alt.sysadmin.recovery'' doesn't fit on the screen, it'll get shortened ``d.a.s.recovery'' while ``de.alt.d0'' still would and thus will not get shortened. At which characters this compression is done is controled via the _$_s_i_d_e_- - _b_a_r___b_o_u_n_d_a_r_y (section 6.4.250 , page 143) variable. + _b_a_r___b_o_u_n_d_a_r_y (section 7.4.266 , page 153) variable. - _6_._4_._2_5_5 _s_i_d_e_b_a_r___v_i_s_i_b_l_e + _7_._4_._2_7_1 _s_i_d_e_b_a_r___v_i_s_i_b_l_e Type: boolean Default: no This specifies whether or not to show the sidebar (a list of folders specified - - The Mutt Next Generation E-Mail Client 146 - with the ``mailboxes'' command). - _6_._4_._2_5_6 _s_i_d_e_b_a_r___w_i_d_t_h + _7_._4_._2_7_2 _s_i_d_e_b_a_r___w_i_d_t_h Type: number @@ -7682,14 +8191,14 @@ The width of the sidebar. - _6_._4_._2_5_7 _s_i_g___d_a_s_h_e_s + _7_._4_._2_7_3 _s_i_g___d_a_s_h_e_s Type: boolean Default: yes If set, a line containing ``-- '' (dash, dash, space) will be inserted before - your ``_$_s_i_g_n_a_t_u_r_e (section 6.4.259 , page 145)''. It is ssttrroonnggllyy recommended + your ``_$_s_i_g_n_a_t_u_r_e (section 7.4.275 , page 155)''. It is ssttrroonnggllyy recommended that you not unset this variable unless your ``signature'' contains just your name. The reason for this is because many software packages use ``-- \n'' to detect your signature. @@ -7697,18 +8206,20 @@ For example, Mutt-ng has the ability to highlight the signature in a different color in the builtin pager. - _6_._4_._2_5_8 _s_i_g___o_n___t_o_p + _7_._4_._2_7_4 _s_i_g___o_n___t_o_p Type: boolean Default: no + The Mutt Next Generation E-Mail Client 156 + If _s_e_t, the signature will be included before any quoted or forwarded text. It is ssttrroonnggllyy recommended that you do not set this variable unless you really know what you are doing, and are prepared to take some heat from netiquette guardians. - _6_._4_._2_5_9 _s_i_g_n_a_t_u_r_e + _7_._4_._2_7_5 _s_i_g_n_a_t_u_r_e Type: path @@ -7718,7 +8229,7 @@ messages. If the filename ends with a pipe (``|''), it is assumed that file- name is a shell command and input should be read from its stdout. - _6_._4_._2_6_0 _s_i_g_n_o_f_f___s_t_r_i_n_g + _7_._4_._2_7_6 _s_i_g_n_o_f_f___s_t_r_i_n_g Type: string @@ -7727,13 +8238,11 @@ If _s_e_t, this string will be inserted before the signature. This is useful for people that want to sign off every message they send with their name. - The Mutt Next Generation E-Mail Client 147 - If you want to insert your website's URL, additional contact information or witty quotes into your mails, better use a signature file instead of the sig- noff string. - _6_._4_._2_6_1 _s_i_m_p_l_e___s_e_a_r_c_h + _7_._4_._2_7_7 _s_i_m_p_l_e___s_e_a_r_c_h Type: string @@ -7741,7 +8250,7 @@ Specifies how Mutt-ng should expand a simple search into a real search pattern. A simple search is one that does not contain any of the ~ operators. See - ``_p_a_t_t_e_r_n_s (section 6.2 , page 78)'' for more information on search patterns. + ``_p_a_t_t_e_r_n_s (section 7.2 , page 84)'' for more information on search patterns. For example, if you simply type ``joe'' at a search or limit prompt, Mutt-ng will automatically expand it to the value specified by this variable. For the @@ -7749,7 +8258,7 @@ ~f joe | ~s joe - _6_._4_._2_6_2 _s_l_e_e_p___t_i_m_e + _7_._4_._2_7_8 _s_l_e_e_p___t_i_m_e Type: number @@ -7760,7 +8269,9 @@ the current folder. The default is to pause one second, so a value of zero for this option suppresses the pause. - _6_._4_._2_6_3 _s_m_a_r_t___w_r_a_p + The Mutt Next Generation E-Mail Client 157 + + _7_._4_._2_7_9 _s_m_a_r_t___w_r_a_p Type: boolean @@ -7768,22 +8279,20 @@ Controls the display of lines longer than the screen width in the internal pager. If _s_e_t, long lines are wrapped at a word boundary. If _u_n_s_e_t, lines are - simply wrapped at the screen edge. Also see the ``_$_m_a_r_k_e_r_s (section 6.4.121 , - page 112)'' variable. + simply wrapped at the screen edge. Also see the ``_$_m_a_r_k_e_r_s (section 7.4.127 , + page 121)'' variable. - _6_._4_._2_6_4 _s_m_i_l_e_y_s + _7_._4_._2_8_0 _s_m_i_l_e_y_s Type: regular expression Default: '(>From )|(:[-^]?[][)(><}{|/DP])' The _p_a_g_e_r uses this variable to catch some common false positives of - ``_$_q_u_o_t_e___r_e_g_e_x_p (section 6.4.225 , page 137)'', most notably smileys in the + ``_$_q_u_o_t_e___r_e_g_e_x_p (section 7.4.241 , page 147)'', most notably smileys in the beginning of a line - _6_._4_._2_6_5 _s_m_i_m_e___a_s_k___c_e_r_t___l_a_b_e_l - - The Mutt Next Generation E-Mail Client 148 + _7_._4_._2_8_1 _s_m_i_m_e___a_s_k___c_e_r_t___l_a_b_e_l Type: boolean @@ -7793,7 +8302,7 @@ cate about to be added to the database or not. It is _s_e_t by default. (S/MIME only) - _6_._4_._2_6_6 _s_m_i_m_e___c_a___l_o_c_a_t_i_o_n + _7_._4_._2_8_2 _s_m_i_m_e___c_a___l_o_c_a_t_i_o_n Type: path @@ -7802,7 +8311,7 @@ This variable contains the name of either a directory, or a file which contains trusted certificates for use with OpenSSL. (S/MIME only) - _6_._4_._2_6_7 _s_m_i_m_e___c_e_r_t_i_f_i_c_a_t_e_s + _7_._4_._2_8_3 _s_m_i_m_e___c_e_r_t_i_f_i_c_a_t_e_s Type: path @@ -7815,7 +8324,9 @@ address keyid pairs, and which can be manually edited. This one points to the location of the certificates. (S/MIME only) - _6_._4_._2_6_8 _s_m_i_m_e___d_e_c_r_y_p_t___c_o_m_m_a_n_d + The Mutt Next Generation E-Mail Client 158 + + _7_._4_._2_8_4 _s_m_i_m_e___d_e_c_r_y_p_t___c_o_m_m_a_n_d Type: string @@ -7835,10 +8346,8 @@ multipart/signed attachment when verifying it. %k - The key-pair specified with _$_s_m_i_m_e___d_e_f_a_u_l_t___k_e_y (section 6.4.270 , - page 148) - - The Mutt Next Generation E-Mail Client 149 + The key-pair specified with _$_s_m_i_m_e___d_e_f_a_u_l_t___k_e_y (section 7.4.286 , + page 158) %c One or more certificate IDs. @@ -7848,15 +8357,15 @@ %C CA location: Depending on whether _$_s_m_i_m_e___c_a___l_o_c_a_t_i_o_n (section - 6.4.266 , page 147) points to a directory or file, this expands to - '-CApath _$_s_m_i_m_e___c_a___l_o_c_a_t_i_o_n (section 6.4.266 , page 147)' or - '-CAfile _$_s_m_i_m_e___c_a___l_o_c_a_t_i_o_n (section 6.4.266 , page 147)'. + 7.4.282 , page 157) points to a directory or file, this expands to + '-CApath _$_s_m_i_m_e___c_a___l_o_c_a_t_i_o_n (section 7.4.282 , page 157)' or + '-CAfile _$_s_m_i_m_e___c_a___l_o_c_a_t_i_o_n (section 7.4.282 , page 157)'. For examples on how to configure these formats, see the smime.rc in the sam- ples/ subdirectory which has been installed on your system alongside the docu- mentation. (S/MIME only) - _6_._4_._2_6_9 _s_m_i_m_e___d_e_c_r_y_p_t___u_s_e___d_e_f_a_u_l_t___k_e_y + _7_._4_._2_8_5 _s_m_i_m_e___d_e_c_r_y_p_t___u_s_e___d_e_f_a_u_l_t___k_e_y Type: boolean @@ -7867,16 +8376,18 @@ mailbox-address to determine the key to use. It will ask you to supply a key, if it can't find one. (S/MIME only) - _6_._4_._2_7_0 _s_m_i_m_e___d_e_f_a_u_l_t___k_e_y + _7_._4_._2_8_6 _s_m_i_m_e___d_e_f_a_u_l_t___k_e_y Type: string + The Mutt Next Generation E-Mail Client 159 + Default: '' This is the default key-pair to use for signing. This must be set to the keyid (the hash-value that OpenSSL generates) to work properly (S/MIME only) - _6_._4_._2_7_1 _s_m_i_m_e___e_n_c_r_y_p_t___c_o_m_m_a_n_d + _7_._4_._2_8_7 _s_m_i_m_e___e_n_c_r_y_p_t___c_o_m_m_a_n_d Type: string @@ -7884,7 +8395,7 @@ This command is used to create encrypted S/MIME messages. (S/MIME only) - _6_._4_._2_7_2 _s_m_i_m_e___e_n_c_r_y_p_t___w_i_t_h + _7_._4_._2_8_8 _s_m_i_m_e___e_n_c_r_y_p_t___w_i_t_h Type: string @@ -7895,9 +8406,7 @@ If _u_n_s_e_t ``_3_d_e_s'' (TripleDES) is used. (S/MIME only) - The Mutt Next Generation E-Mail Client 150 - - _6_._4_._2_7_3 _s_m_i_m_e___g_e_t___c_e_r_t___c_o_m_m_a_n_d + _7_._4_._2_8_9 _s_m_i_m_e___g_e_t___c_e_r_t___c_o_m_m_a_n_d Type: string @@ -7906,7 +8415,7 @@ This command is used to extract X509 certificates from a PKCS7 structure. (S/MIME only) - _6_._4_._2_7_4 _s_m_i_m_e___g_e_t___c_e_r_t___e_m_a_i_l___c_o_m_m_a_n_d + _7_._4_._2_9_0 _s_m_i_m_e___g_e_t___c_e_r_t___e_m_a_i_l___c_o_m_m_a_n_d Type: string @@ -7916,7 +8425,7 @@ tificates, and for verification purposes (to check whether the certificate was issued for the sender's mailbox). (S/MIME only) - _6_._4_._2_7_5 _s_m_i_m_e___g_e_t___s_i_g_n_e_r___c_e_r_t___c_o_m_m_a_n_d + _7_._4_._2_9_1 _s_m_i_m_e___g_e_t___s_i_g_n_e_r___c_e_r_t___c_o_m_m_a_n_d Type: string @@ -7926,7 +8435,9 @@ signature, so that the certificate's owner may get compared to the email's ``From:'' header field. (S/MIME only) - _6_._4_._2_7_6 _s_m_i_m_e___i_m_p_o_r_t___c_e_r_t___c_o_m_m_a_n_d + The Mutt Next Generation E-Mail Client 160 + + _7_._4_._2_9_2 _s_m_i_m_e___i_m_p_o_r_t___c_e_r_t___c_o_m_m_a_n_d Type: string @@ -7934,7 +8445,7 @@ This command is used to import a certificate via smime_keysng. (S/MIME only) - _6_._4_._2_7_7 _s_m_i_m_e___i_s___d_e_f_a_u_l_t + _7_._4_._2_9_3 _s_m_i_m_e___i_s___d_e_f_a_u_l_t Type: boolean @@ -7947,11 +8458,9 @@ select the same application that was used to sign/encrypt the original message. (Note that this variable can be overridden by unsetting _$_c_r_y_p_t___a_u_t_o_s_m_i_m_e (sec- - tion 6.4.37 , page 91).) (S/MIME only) + tion 7.4.40 , page 99).) (S/MIME only) - _6_._4_._2_7_8 _s_m_i_m_e___k_e_y_s - - The Mutt Next Generation E-Mail Client 151 + _7_._4_._2_9_4 _s_m_i_m_e___k_e_y_s Type: path @@ -7964,7 +8473,7 @@ address keyid pair, and which can be manually edited. This one points to the location of the private keys. (S/MIME only) - _6_._4_._2_7_9 _s_m_i_m_e___p_k_7_o_u_t___c_o_m_m_a_n_d + _7_._4_._2_9_5 _s_m_i_m_e___p_k_7_o_u_t___c_o_m_m_a_n_d Type: string @@ -7973,7 +8482,7 @@ This command is used to extract PKCS7 structures of S/MIME signatures, in order to extract the public X509 certificate(s). (S/MIME only) - _6_._4_._2_8_0 _s_m_i_m_e___s_i_g_n___c_o_m_m_a_n_d + _7_._4_._2_9_6 _s_m_i_m_e___s_i_g_n___c_o_m_m_a_n_d Type: string @@ -7982,7 +8491,9 @@ This command is used to created S/MIME signatures of type multipart/signed, which can be read by all mail clients. (S/MIME only) - _6_._4_._2_8_1 _s_m_i_m_e___s_i_g_n___o_p_a_q_u_e___c_o_m_m_a_n_d + The Mutt Next Generation E-Mail Client 161 + + _7_._4_._2_9_7 _s_m_i_m_e___s_i_g_n___o_p_a_q_u_e___c_o_m_m_a_n_d Type: string @@ -7992,7 +8503,7 @@ pkcs7-signature, which can only be handled by mail clients supporting the S/MIME extension. (S/MIME only) - _6_._4_._2_8_2 _s_m_i_m_e___t_i_m_e_o_u_t + _7_._4_._2_9_8 _s_m_i_m_e___t_i_m_e_o_u_t Type: number @@ -8001,18 +8512,16 @@ The number of seconds after which a cached passphrase will expire if not used. (S/MIME only) - _6_._4_._2_8_3 _s_m_i_m_e___v_e_r_i_f_y___c_o_m_m_a_n_d + _7_._4_._2_9_9 _s_m_i_m_e___v_e_r_i_f_y___c_o_m_m_a_n_d Type: string Default: '' - The Mutt Next Generation E-Mail Client 152 - This command is used to verify S/MIME signatures of type multipart/signed. (S/MIME only) - _6_._4_._2_8_4 _s_m_i_m_e___v_e_r_i_f_y___o_p_a_q_u_e___c_o_m_m_a_n_d + _7_._4_._3_0_0 _s_m_i_m_e___v_e_r_i_f_y___o_p_a_q_u_e___c_o_m_m_a_n_d Type: string @@ -8021,7 +8530,7 @@ This command is used to verify S/MIME signatures of type application/x- pkcs7-mime. (S/MIME only) - _6_._4_._2_8_5 _s_m_t_p___e_n_v_e_l_o_p_e + _7_._4_._3_0_1 _s_m_t_p___e_n_v_e_l_o_p_e Type: string @@ -8036,7 +8545,9 @@ envelope sender but only a particular one which may not be the same as the user's desired From: header. - _6_._4_._2_8_6 _s_m_t_p___h_o_s_t + _7_._4_._3_0_2 _s_m_t_p___h_o_s_t + + The Mutt Next Generation E-Mail Client 162 Type: string @@ -8046,9 +8557,9 @@ Defines the SMTP host which will be used to deliver mail, as opposed to invok- ing the sendmail binary. Setting this variable overrides the value of ``_$_s_e_n_d_- - _m_a_i_l (section 6.4.247 , page 142)'', and any associated variables. + _m_a_i_l (section 7.4.263 , page 152)'', and any associated variables. - _6_._4_._2_8_7 _s_m_t_p___p_a_s_s + _7_._4_._3_0_3 _s_m_t_p___p_a_s_s Type: string @@ -8057,15 +8568,13 @@ Availability: SMTP Defines the password to use with SMTP AUTH. If ``_$_s_m_t_p___u_s_e_r (section - 6.4.290 , page 152)'' is set, but this variable is not, you will be prompted + 7.4.306 , page 162)'' is set, but this variable is not, you will be prompted for a password when sending. NNoottee:: Storing passwords in a configuration file presents a security risk since the superuser of your machine may read it regardless of the file's permissions. - The Mutt Next Generation E-Mail Client 153 - - _6_._4_._2_8_8 _s_m_t_p___p_o_r_t + _7_._4_._3_0_4 _s_m_t_p___p_o_r_t Type: number @@ -8079,7 +8588,7 @@ Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP servers will probably desire 587, the mail submission port. - _6_._4_._2_8_9 _s_m_t_p___u_s_e___t_l_s + _7_._4_._3_0_5 _s_m_t_p___u_s_e___t_l_s Type: string @@ -8093,7 +8602,9 @@ continue without TLS in case of an error. Muttng still needs to have SSL sup- port enabled in order to use it. - _6_._4_._2_9_0 _s_m_t_p___u_s_e_r + The Mutt Next Generation E-Mail Client 163 + + _7_._4_._3_0_6 _s_m_t_p___u_s_e_r Type: string @@ -8104,7 +8615,7 @@ Defines the username to use with SMTP AUTH. Setting this variable will cause Mutt-ng to attempt to use SMTP AUTH when sending. - _6_._4_._2_9_1 _s_o_r_t + _7_._4_._3_0_7 _s_o_r_t Type: sort order @@ -8112,8 +8623,6 @@ Specifies how to sort messages in the _i_n_d_e_x menu. Valid values are: - The Mutt Next Generation E-Mail Client 154 - date or date-sent date-received from @@ -8128,7 +8637,7 @@ You may optionally use the ``reverse-'' prefix to specify reverse sorting order (example: set sort=reverse-date-sent). - _6_._4_._2_9_2 _s_o_r_t___a_l_i_a_s + _7_._4_._3_0_8 _s_o_r_t___a_l_i_a_s Type: sort order @@ -8141,15 +8650,17 @@ alias (sort alphabetically by alias name) unsorted (leave in order specified in .muttrc) - _6_._4_._2_9_3 _s_o_r_t___a_u_x + _7_._4_._3_0_9 _s_o_r_t___a_u_x Type: sort order + The Mutt Next Generation E-Mail Client 164 + Default: date When sorting by threads, this variable controls how threads are sorted in rela- tion to other threads, and how the branches of the thread trees are sorted. - This can be set to any value that ``_$_s_o_r_t (section 6.4.291 , page 152)'' can, + This can be set to any value that ``_$_s_o_r_t (section 7.4.307 , page 163)'' can, except threads (in that case, Mutt-ng will just use date-sent). You can also specify the ``last-'' prefix in addition to ``reverse-'' prefix, but last- must come after reverse-. The last- prefix causes messages to be sorted against its @@ -8160,13 +8671,11 @@ is received in a thread, that thread becomes the last one displayed (or the first, if you have set sort=reverse-threads.) - NNoottee:: For reversed ``_$_s_o_r_t (section 6.4.291 , page 152)'' order _$_s_o_r_t___a_u_x - (section 6.4.293 , page 153) is reversed again (which is not the right thing + NNoottee:: For reversed ``_$_s_o_r_t (section 7.4.307 , page 163)'' order _$_s_o_r_t___a_u_x + (section 7.4.309 , page 163) is reversed again (which is not the right thing to do, but kept to not break any existing configuration setting). - The Mutt Next Generation E-Mail Client 155 - - _6_._4_._2_9_4 _s_o_r_t___b_r_o_w_s_e_r + _7_._4_._3_1_0 _s_o_r_t___b_r_o_w_s_e_r Type: sort order @@ -8183,49 +8692,48 @@ You may optionally use the ``reverse-'' prefix to specify reverse sorting order (example: set sort_browser=reverse-date). - _6_._4_._2_9_5 _s_o_r_t___r_e + _7_._4_._3_1_1 _s_o_r_t___r_e Type: boolean Default: yes This variable is only useful when sorting by threads with ``_$_s_t_r_i_c_t___t_h_r_e_a_d_s - (section 6.4.312 , page 160)'' _u_n_s_e_t. In that case, it changes the heuristic - Mutt-ng uses to thread messages by subject. With _$_s_o_r_t___r_e (section 6.4.295 , - page 154) _s_e_t, Mutt-ng will only attach a message as the child of another mes- + (section 7.4.328 , page 170)'' _u_n_s_e_t. In that case, it changes the heuristic + Mutt-ng uses to thread messages by subject. With _$_s_o_r_t___r_e (section 7.4.311 , + page 164) _s_e_t, Mutt-ng will only attach a message as the child of another mes- sage by subject if the subject of the child message starts with a substring - matching the setting of ``_$_r_e_p_l_y___r_e_g_e_x_p (section 6.4.231 , page 138)''. With - _$_s_o_r_t___r_e (section 6.4.295 , page 154) _u_n_s_e_t, Mutt-ng will attach the message + matching the setting of ``_$_r_e_p_l_y___r_e_g_e_x_p (section 7.4.247 , page 149)''. With + _$_s_o_r_t___r_e (section 7.4.311 , page 164) _u_n_s_e_t, Mutt-ng will attach the message whether or not this is the case, as long as the non-``_$_r_e_p_l_y___r_e_g_e_x_p (section - 6.4.231 , page 138)'' parts of both messages are identical. + 7.4.247 , page 149)'' parts of both messages are identical. - _6_._4_._2_9_6 _s_p_a_m___s_e_p_a_r_a_t_o_r + The Mutt Next Generation E-Mail Client 165 + + _7_._4_._3_1_2 _s_p_a_m___s_e_p_a_r_a_t_o_r Type: string Default: ',' - ``_s_p_a_m___s_e_p_a_r_a_t_o_r (section 6.4.296 , page 154)'' controls what happens when + ``_s_p_a_m___s_e_p_a_r_a_t_o_r (section 7.4.312 , page 164)'' controls what happens when multiple spam headers are matched: if _u_n_s_e_t, each successive header will over- write any previous matches value for the spam label. If _s_e_t, each successive - match will append to the previous, using ``_s_p_a_m___s_e_p_a_r_a_t_o_r (section 6.4.296 , - page 154)'' as a separator. + match will append to the previous, using ``_s_p_a_m___s_e_p_a_r_a_t_o_r (section 7.4.312 , + page 164)'' as a separator. - _6_._4_._2_9_7 _s_p_o_o_l_f_i_l_e + _7_._4_._3_1_3 _s_p_o_o_l_f_i_l_e Type: path Default: '' If your spool mailbox is in a non-default place where Mutt-ng cannot find it, - - The Mutt Next Generation E-Mail Client 156 - you can specify its location with this variable. Mutt-ng will automatically set this variable to the value of the environment variable $MAIL if it is not set. - _6_._4_._2_9_8 _s_s_l___c_a___c_e_r_t_i_f_i_c_a_t_e_s___f_i_l_e + _7_._4_._3_1_4 _s_s_l___c_a___c_e_r_t_i_f_i_c_a_t_e_s___f_i_l_e Type: path @@ -8237,7 +8745,7 @@ Example: set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt - _6_._4_._2_9_9 _s_s_l___c_l_i_e_n_t___c_e_r_t + _7_._4_._3_1_5 _s_s_l___c_l_i_e_n_t___c_e_r_t Type: path @@ -8247,7 +8755,7 @@ The file containing a client certificate and its associated private key. - _6_._4_._3_0_0 _s_s_l___f_o_r_c_e___t_l_s + _7_._4_._3_1_6 _s_s_l___f_o_r_c_e___t_l_s Type: boolean @@ -8256,10 +8764,13 @@ If this variable is _s_e_t, mutt-ng will require that all connections to remote servers be encrypted. Furthermore it will attempt to negotiate TLS even if the server does not advertise the capability, since it would otherwise have to + + The Mutt Next Generation E-Mail Client 166 + abort the connection anyway. This option supersedes ``_$_s_s_l___s_t_a_r_t_t_l_s (section - 6.4.302 , page 155)''. + 7.4.318 , page 166)''. - _6_._4_._3_0_1 _s_s_l___m_i_n___d_h___p_r_i_m_e___b_i_t_s + _7_._4_._3_1_7 _s_s_l___m_i_n___d_h___p_r_i_m_e___b_i_t_s Type: number @@ -8271,12 +8782,10 @@ any Diffie-Hellman key exchange. A value of 0 will use the default from the GNUTLS library. - _6_._4_._3_0_2 _s_s_l___s_t_a_r_t_t_l_s + _7_._4_._3_1_8 _s_s_l___s_t_a_r_t_t_l_s Type: quadoption - The Mutt Next Generation E-Mail Client 157 - Default: yes Availability: SSL or GNUTLS @@ -8285,7 +8794,7 @@ ing the capability. When _u_n_s_e_t, Mutt-ng will not attempt to use STARTTLS regardless of the server's capabilities. - _6_._4_._3_0_3 _s_s_l___u_s_e___s_s_l_v_2 + _7_._4_._3_1_9 _s_s_l___u_s_e___s_s_l_v_2 Type: boolean @@ -8296,7 +8805,7 @@ This variables specifies whether to attempt to use SSLv2 in the SSL authentica- tion process. - _6_._4_._3_0_4 _s_s_l___u_s_e___s_s_l_v_3 + _7_._4_._3_2_0 _s_s_l___u_s_e___s_s_l_v_3 Type: boolean @@ -8307,18 +8816,20 @@ This variables specifies whether to attempt to use SSLv3 in the SSL authentica- tion process. - _6_._4_._3_0_5 _s_s_l___u_s_e___t_l_s_v_1 + _7_._4_._3_2_1 _s_s_l___u_s_e___t_l_s_v_1 Type: boolean Default: yes + The Mutt Next Generation E-Mail Client 167 + Availability: SSL or GNUTLS This variables specifies whether to attempt to use TLSv1 in the SSL authentica- tion process. - _6_._4_._3_0_6 _s_s_l___u_s_e_s_y_s_t_e_m_c_e_r_t_s + _7_._4_._3_2_2 _s_s_l___u_s_e_s_y_s_t_e_m_c_e_r_t_s Type: boolean @@ -8329,16 +8840,14 @@ If set to _y_e_s, Mutt-ng will use CA certificates in the system-wide certificate store when checking if server certificate is signed by a trusted CA. - _6_._4_._3_0_7 _s_t_a_t_u_s___c_h_a_r_s - - The Mutt Next Generation E-Mail Client 158 + _7_._4_._3_2_3 _s_t_a_t_u_s___c_h_a_r_s Type: string Default: '-*%A' Controls the characters used by the ``%r'' indicator in ``_$_s_t_a_t_u_s___f_o_r_m_a_t (sec- - tion 6.4.308 , page 157)''. The first character is used when the mailbox is + tion 7.4.324 , page 167)''. The first character is used when the mailbox is unchanged. The second is used when the mailbox has been changed, and it needs to be resynchronized. The third is used if the mailbox is in read-only mode, or if the mailbox will not be written when exiting that mailbox (You can toggle @@ -8347,7 +8856,7 @@ been opened in attach-message mode (Certain operations like composing a new mail, replying, forwarding, etc. are not permitted in this mode). - _6_._4_._3_0_8 _s_t_a_t_u_s___f_o_r_m_a_t + _7_._4_._3_2_4 _s_t_a_t_u_s___f_o_r_m_a_t Type: string @@ -8356,7 +8865,7 @@ %l?]---(%s/%S)-%>-(%P)---' Controls the format of the status line displayed in the _i_n_d_e_x menu. This - string is similar to ``_$_i_n_d_e_x___f_o_r_m_a_t (section 6.4.110 , page 108)'', but has + string is similar to ``_$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.116 , page 116)'', but has its own set of printf(3)-like sequences: %b @@ -8368,6 +8877,8 @@ %d number of deleted messages * + The Mutt Next Generation E-Mail Client 168 + %f the full pathname of the current mailbox @@ -8387,8 +8898,6 @@ %m the number of messages in the mailbox * - The Mutt Next Generation E-Mail Client 159 - %M the number of messages shown (i.e., which match the current limit) * @@ -8407,14 +8916,14 @@ %r modified/read-only/won't-write/attach-message indicator, according - to _$_s_t_a_t_u_s___c_h_a_r_s (section 6.4.307 , page 156) + to _$_s_t_a_t_u_s___c_h_a_r_s (section 7.4.323 , page 167) %s - current sorting mode (_$_s_o_r_t (section 6.4.291 , page 152)) + current sorting mode (_$_s_o_r_t (section 7.4.307 , page 163)) %S - current aux sorting method (_$_s_o_r_t___a_u_x (section 6.4.293 , page - 153)) + current aux sorting method (_$_s_o_r_t___a_u_x (section 7.4.309 , page + 163)) %t number of tagged messages * @@ -8425,6 +8934,8 @@ %v Mutt-ng version string + The Mutt Next Generation E-Mail Client 169 + %V currently active limit pattern, if any * @@ -8444,8 +8955,6 @@ %??? - The Mutt Next Generation E-Mail Client 160 - where _s_e_q_u_e_n_c_e___c_h_a_r is a character from the table above, and _o_p_t_i_o_n_a_l___s_t_r_i_n_g is the string you would like printed if _s_e_q_u_e_n_c_e___c_h_a_r is nonzero. _o_p_t_i_o_n_a_l___s_t_r_i_n_g mmaayy contain other sequences as well as normal text, but you may nnoott nest @@ -8472,7 +8981,7 @@ replace any dots in the expansion by underscores. This might be helpful with IMAP folders that don't like dots in folder names. - _6_._4_._3_0_9 _s_t_a_t_u_s___o_n___t_o_p + _7_._4_._3_2_5 _s_t_a_t_u_s___o_n___t_o_p Type: boolean @@ -8481,7 +8990,9 @@ Setting this variable causes the ``status bar'' to be displayed on the first line of the screen rather than near the bottom. - _6_._4_._3_1_0 _s_t_r_i_c_t___m_a_i_l_t_o + The Mutt Next Generation E-Mail Client 170 + + _7_._4_._3_2_6 _s_t_r_i_c_t___m_a_i_l_t_o Type: boolean @@ -8489,65 +9000,65 @@ With mailto: style links, a body as well as arbitrary header information may be embedded. This may lead to (user) headers being overwriten without note if - ``_$_e_d_i_t___h_e_a_d_e_r_s (section 6.4.54 , page 95)'' is unset. + ``_$_e_d_i_t___h_e_a_d_e_r_s (section 7.4.59 , page 103)'' is unset. If this variable is _s_e_t, mutt-ng is strict and allows anything to be changed. If it's _u_n_s_e_t, all headers given will be prefixed with ``X-Mailto-'' and the message including headers will be shown in the editor regardless of what - ``_$_e_d_i_t___h_e_a_d_e_r_s (section 6.4.54 , page 95)'' is set to. + ``_$_e_d_i_t___h_e_a_d_e_r_s (section 7.4.59 , page 103)'' is set to. - _6_._4_._3_1_1 _s_t_r_i_c_t___m_i_m_e + _7_._4_._3_2_7 _s_t_r_i_c_t___m_i_m_e Type: boolean - The Mutt Next Generation E-Mail Client 161 - Default: yes When _u_n_s_e_t, non MIME-compliant messages that doesn't have any charset indica- tion in the ``Content-Type:'' header field can be displayed (non MIME-compliant messages are often generated by old mailers or buggy mailers like MS Outlook - Express). See also _$_a_s_s_u_m_e_d___c_h_a_r_s_e_t (section 6.4.11 , page 85). + Express). See also _$_a_s_s_u_m_e_d___c_h_a_r_s_e_t (section 7.4.13 , page 92). This option also replaces linear-white-space between encoded-word and *text to a single space to prevent the display of MIME-encoded ``Subject:'' header field from being devided into multiple lines. - _6_._4_._3_1_2 _s_t_r_i_c_t___t_h_r_e_a_d_s + _7_._4_._3_2_8 _s_t_r_i_c_t___t_h_r_e_a_d_s Type: boolean Default: no If _s_e_t, threading will only make use of the ``In-Reply-To:'' and ``Refer- - ences:'' header fields when you ``_$_s_o_r_t (section 6.4.291 , page 152)'' by mes- + ences:'' header fields when you ``_$_s_o_r_t (section 7.4.307 , page 163)'' by mes- sage threads. By default, messages with the same subject are grouped together in ``pseudo threads.'' This may not always be desirable, such as in a personal mailbox where you might have several unrelated messages with the subject ``hi'' which will get grouped together. - _6_._4_._3_1_3 _s_t_r_i_p___w_a_s + _7_._4_._3_2_9 _s_t_r_i_p___w_a_s Type: boolean Default: no When _s_e_t, mutt-ng will remove the trailing part of the ``Subject:'' line which - matches _$_s_t_r_i_p___w_a_s___r_e_g_e_x (section 6.4.314 , page 160) when replying. This is + matches _$_s_t_r_i_p___w_a_s___r_e_g_e_x (section 7.4.330 , page 170) when replying. This is useful to properly react on subject changes and reduce ``subject noise.'' (esp. in Usenet) - _6_._4_._3_1_4 _s_t_r_i_p___w_a_s___r_e_g_e_x + The Mutt Next Generation E-Mail Client 171 + + _7_._4_._3_3_0 _s_t_r_i_p___w_a_s___r_e_g_e_x Type: regular expression Default: '\([Ww][Aa][RrSs]: .*\)[ ]*$' - When non-empty and _$_s_t_r_i_p___w_a_s (section 6.4.313 , page 160) is _s_e_t, mutt-ng + When non-empty and _$_s_t_r_i_p___w_a_s (section 7.4.329 , page 170) is _s_e_t, mutt-ng will remove this trailing part of the ``Subject'' line when replying if it won't be empty afterwards. - _6_._4_._3_1_5 _s_t_u_f_f___q_u_o_t_e_d + _7_._4_._3_3_1 _s_t_u_f_f___q_u_o_t_e_d Type: boolean @@ -8556,9 +9067,7 @@ If _s_e_t, attachments with flowed format will have their quoting ``stuffed'', i.e. a space will be inserted between the quote characters and the actual text. - The Mutt Next Generation E-Mail Client 162 - - _6_._4_._3_1_6 _s_u_s_p_e_n_d + _7_._4_._3_3_2 _s_u_s_p_e_n_d Type: boolean @@ -8568,7 +9077,7 @@ usually CTRL+Z. This is useful if you run Mutt-ng inside an xterm using a com- mand like ``xterm -e muttng.'' - _6_._4_._3_1_7 _t_e_x_t___f_l_o_w_e_d + _7_._4_._3_3_3 _t_e_x_t___f_l_o_w_e_d Type: boolean @@ -8579,21 +9088,23 @@ like ordinary text. To actually make use of this format's features, you'll need support in your editor. - Note that _$_i_n_d_e_n_t___s_t_r_i_n_g (section 6.4.109 , page 108) is ignored when this + Note that _$_i_n_d_e_n_t___s_t_r_i_n_g (section 7.4.115 , page 116) is ignored when this option is set. - _6_._4_._3_1_8 _t_h_o_r_o_u_g_h___s_e_a_r_c_h + _7_._4_._3_3_4 _t_h_o_r_o_u_g_h___s_e_a_r_c_h Type: boolean Default: no Affects the ~b and ~h search operations described in section ``_p_a_t_t_e_r_n_s (sec- - tion 6.2 , page 78)'' above. If _s_e_t, the headers and attachments of messages + tion 7.2 , page 84)'' above. If _s_e_t, the headers and attachments of messages to be searched are decoded before searching. If _u_n_s_e_t, messages are searched as they appear in the folder. - _6_._4_._3_1_9 _t_h_r_e_a_d___r_e_c_e_i_v_e_d + The Mutt Next Generation E-Mail Client 172 + + _7_._4_._3_3_5 _t_h_r_e_a_d___r_e_c_e_i_v_e_d Type: boolean @@ -8602,7 +9113,7 @@ When _s_e_t, Mutt-ng uses the date received rather than the date sent to thread messages by subject. - _6_._4_._3_2_0 _t_i_l_d_e + _7_._4_._3_3_6 _t_i_l_d_e Type: boolean @@ -8611,9 +9122,7 @@ When _s_e_t, the internal-pager will pad blank lines to the bottom of the screen with a tilde (~). - The Mutt Next Generation E-Mail Client 163 - - _6_._4_._3_2_1 _t_i_m_e_o_u_t + _7_._4_._3_3_7 _t_i_m_e_o_u_t Type: number @@ -8623,7 +9132,7 @@ pressed in the main menu before timing out and checking for new mail. A value of zero or less will cause Mutt-ng to never time out. - _6_._4_._3_2_2 _t_m_p_d_i_r + _7_._4_._3_3_8 _t_m_p_d_i_r Type: path @@ -8634,7 +9143,7 @@ set, the environment variable $TMPDIR is used. If $TMPDIR is not set then '/tmp' is used. - _6_._4_._3_2_3 _t_o___c_h_a_r_s + _7_._4_._3_3_9 _t_o___c_h_a_r_s Type: string @@ -8650,7 +9159,9 @@ indicate mail that was sent by _y_o_u. The sixth character is used to indicate when a mail was sent to a mailing-list you're subscribe to (default: L). - _6_._4_._3_2_4 _t_r_a_s_h + The Mutt Next Generation E-Mail Client 173 + + _7_._4_._3_4_0 _t_r_a_s_h Type: path @@ -8662,14 +9173,12 @@ NNoottee: When you delete a message in the trash folder, it is really deleted, so that there is no way to recover mail. - _6_._4_._3_2_5 _t_u_n_n_e_l + _7_._4_._3_4_1 _t_u_n_n_e_l Type: string Default: '' - The Mutt Next Generation E-Mail Client 164 - Setting this variable will cause Mutt-ng to open a pipe to a command instead of a raw socket. You may be able to use this to set up preauthenticated connec- tions to your IMAP/POP3 server. Example: @@ -8679,7 +9188,7 @@ NNoottee:: For this example to work you must be able to log in to the remote machine without having to enter a password. - _6_._4_._3_2_6 _u_m_a_s_k + _7_._4_._3_4_2 _u_m_a_s_k Type: number @@ -8688,7 +9197,7 @@ This sets the umask that will be used by Mutt-ng when creating all kinds of files. If _u_n_s_e_t, the default value is 077. - _6_._4_._3_2_7 _u_n_c_o_l_l_a_p_s_e___j_u_m_p + _7_._4_._3_4_3 _u_n_c_o_l_l_a_p_s_e___j_u_m_p Type: boolean @@ -8697,7 +9206,7 @@ When _s_e_t, Mutt-ng will jump to the next unread message, if any, when the cur- rent thread is _u_ncollapsed. - _6_._4_._3_2_8 _u_s_e___8_b_i_t_m_i_m_e + _7_._4_._3_4_4 _u_s_e___8_b_i_t_m_i_m_e Type: boolean @@ -8706,25 +9215,26 @@ WWaarrnniinngg:: do not set this variable unless you are using a version of sendmail which supports the -B8BITMIME flag (such as sendmail 8.8.x) or in connection with the SMTP support via libESMTP. Otherwise you may not be able to send + + The Mutt Next Generation E-Mail Client 174 + mail. - When _s_e_t, Mutt-ng will either invoke ``_$_s_e_n_d_m_a_i_l (section 6.4.247 , page - 142)'' with the -B8BITMIME flag when sending 8-bit messages to enable ESMTP + When _s_e_t, Mutt-ng will either invoke ``_$_s_e_n_d_m_a_i_l (section 7.4.263 , page + 152)'' with the -B8BITMIME flag when sending 8-bit messages to enable ESMTP negotiation or tell libESMTP to do so. - _6_._4_._3_2_9 _u_s_e___d_o_m_a_i_n + _7_._4_._3_4_5 _u_s_e___d_o_m_a_i_n Type: boolean Default: yes When _s_e_t, Mutt-ng will qualify all local addresses (ones without the @host por- - tion) with the value of ``_$_h_o_s_t_n_a_m_e (section 6.4.89 , page 103)''. If _u_n_s_e_t, + tion) with the value of ``_$_h_o_s_t_n_a_m_e (section 7.4.95 , page 111)''. If _u_n_s_e_t, no addresses will be qualified. - _6_._4_._3_3_0 _u_s_e___f_r_o_m - - The Mutt Next Generation E-Mail Client 165 + _7_._4_._3_4_6 _u_s_e___f_r_o_m Type: boolean @@ -8732,9 +9242,9 @@ When _s_e_t, Mutt-ng will generate the ``From:'' header field when sending mes- sages. If _u_n_s_e_t, no ``From:'' header field will be generated unless the user - explicitly sets one using the ``_m_y___h_d_r (section 3.15 , page 34)'' command. + explicitly sets one using the ``_m_y___h_d_r (section 3.16 , page 38)'' command. - _6_._4_._3_3_1 _u_s_e___i_d_n + _7_._4_._3_4_7 _u_s_e___i_d_n Type: boolean @@ -8747,7 +9257,7 @@ NNoottee:: You can use IDNs for addresses even if this is _u_n_s_e_t. This variable only affects decoding. - _6_._4_._3_3_2 _u_s_e___i_p_v_6 + _7_._4_._3_4_8 _u_s_e___i_p_v_6 Type: boolean @@ -8757,43 +9267,34 @@ If this option is _u_n_s_e_t, Mutt-ng will restrict itself to IPv4 addresses. Nor- mally, the default should work. - _6_._4_._3_3_3 _u_s_e_r___a_g_e_n_t - - Type: boolean - - Default: yes - - When _s_e_t, Mutt-ng will add a ``User-Agent:'' header to outgoing messages, indi- - cating which version of Mutt-ng was used for composing them. - - _6_._4_._3_3_4 _v_i_s_u_a_l + _7_._4_._3_4_9 _v_i_s_u_a_l Type: path Default: '' + The Mutt Next Generation E-Mail Client 175 + Specifies the visual editor to invoke when the _~_v command is given in the builtin editor. - _6_._4_._3_3_5 _w_a_i_t___k_e_y + _7_._4_._3_5_0 _w_a_i_t___k_e_y Type: boolean Default: yes - The Mutt Next Generation E-Mail Client 166 - Controls whether Mutt-ng will ask you to press a key after _s_h_e_l_l_- _e_s_c_a_p_e, _p_i_p_e_- _m_e_s_s_a_g_e, _p_i_p_e_-_e_n_t_r_y, _p_r_i_n_t_-_m_e_s_s_a_g_e, and _p_r_i_n_t_-_e_n_t_r_y commands. It is also used when viewing attachments with ``_a_u_t_o___v_i_e_w (section 5.4 , page - 75)'', provided that the corresponding mailcap entry has a needsterminal flag, + 79)'', provided that the corresponding mailcap entry has a needsterminal flag, and the external program is interactive. When _s_e_t, Mutt-ng will always ask for a key. When _u_n_s_e_t, Mutt-ng will wait for a key only if the external command returned a non-zero status. - _6_._4_._3_3_6 _w_e_e_d + _7_._4_._3_5_1 _w_e_e_d Type: boolean @@ -8802,7 +9303,7 @@ When _s_e_t, Mutt-ng will weed headers when displaying, forwarding, printing, or replying to messages. - _6_._4_._3_3_7 _w_r_a_p___s_e_a_r_c_h + _7_._4_._3_5_2 _w_r_a_p___s_e_a_r_c_h Type: boolean @@ -8813,7 +9314,7 @@ When _s_e_t, searches will wrap around the first (or last) message. When _u_n_s_e_t, searches will not wrap. - _6_._4_._3_3_8 _w_r_a_p_m_a_r_g_i_n + _7_._4_._3_5_3 _w_r_a_p_m_a_r_g_i_n Type: number @@ -8822,46 +9323,46 @@ Controls the size of the margin remaining at the right side of the terminal when Mutt-ng's pager does smart wrapping. - _6_._4_._3_3_9 _w_r_i_t_e___b_c_c + _7_._4_._3_5_4 _w_r_i_t_e___b_c_c Type: boolean Default: yes + The Mutt Next Generation E-Mail Client 176 + Controls whether Mutt-ng writes out the Bcc header when preparing messages to be sent. Exim users may wish to _u_n_s_e_t this. - _6_._4_._3_4_0 _w_r_i_t_e___i_n_c + _7_._4_._3_5_5 _w_r_i_t_e___i_n_c Type: number Default: 10 - The Mutt Next Generation E-Mail Client 167 - When writing a mailbox, a message will be printed every _w_r_i_t_e___i_n_c messages to indicate progress. If set to 0, only a single message will be displayed before writing a mailbox. - Also see the ``_$_r_e_a_d___i_n_c (section 6.4.226 , page 137)'' variable. + Also see the ``_$_r_e_a_d___i_n_c (section 7.4.242 , page 147)'' variable. - _6_._4_._3_4_1 _x_t_e_r_m___i_c_o_n + _7_._4_._3_5_6 _x_t_e_r_m___i_c_o_n Type: string Default: 'M%?n?AIL&ail?' Controls the format of the X11 icon title, as long as _$_x_t_e_r_m___s_e_t___t_i_t_l_e_s (sec- - tion 6.4.343 , page 166) is _s_e_t. This string is identical in formatting to the - one used by ``_$_s_t_a_t_u_s___f_o_r_m_a_t (section 6.4.308 , page 157)''. + tion 7.4.358 , page 176) is _s_e_t. This string is identical in formatting to the + one used by ``_$_s_t_a_t_u_s___f_o_r_m_a_t (section 7.4.324 , page 167)''. - _6_._4_._3_4_2 _x_t_e_r_m___l_e_a_v_e + _7_._4_._3_5_7 _x_t_e_r_m___l_e_a_v_e Type: string Default: '' - If _$_x_t_e_r_m___s_e_t___t_i_t_l_e_s (section 6.4.343 , page 166) is _s_e_t, this string will be + If _$_x_t_e_r_m___s_e_t___t_i_t_l_e_s (section 7.4.358 , page 176) is _s_e_t, this string will be used to set the title when leaving mutt-ng. For terminal-based programs, there's no easy and portable way to read the current title so mutt-ng cannot read it upon startup and restore it when exiting. @@ -8871,7 +9372,7 @@ set xterm_leave = '`test x$DISPLAY != x && xprop -id $WINDOWID | grep WM_NAME | cut -d ''' -f 2`' - _6_._4_._3_4_3 _x_t_e_r_m___s_e_t___t_i_t_l_e_s + _7_._4_._3_5_8 _x_t_e_r_m___s_e_t___t_i_t_l_e_s Type: boolean @@ -8881,27 +9382,27 @@ you're in an appropriate terminal). The default must be _u_n_s_e_t to force in the validity checking. - _6_._4_._3_4_4 _x_t_e_r_m___t_i_t_l_e + _7_._4_._3_5_9 _x_t_e_r_m___t_i_t_l_e Type: string + The Mutt Next Generation E-Mail Client 177 + Default: 'Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?' Controls the format of the title bar of the xterm provided that - _$_x_t_e_r_m___s_e_t___t_i_t_l_e_s (section 6.4.343 , page 166) has been _s_e_t. This string is - identical in formatting to the one used by ``_$_s_t_a_t_u_s___f_o_r_m_a_t (section 6.4.308 , - page 157)''. - - The Mutt Next Generation E-Mail Client 168 + _$_x_t_e_r_m___s_e_t___t_i_t_l_e_s (section 7.4.358 , page 176) has been _s_e_t. This string is + identical in formatting to the one used by ``_$_s_t_a_t_u_s___f_o_r_m_a_t (section 7.4.324 , + page 167)''. - _6_._5 _F_u_n_c_t_i_o_n_s + _7_._5 _F_u_n_c_t_i_o_n_s The following is the list of available functions listed by the mapping in which they are available. The default key setting is given, and an explanation of what the function does. The key bindings of these functions can be changed - with the _b_i_n_d (section 3.4 , page 24) command. + with the _b_i_n_d (section 3.5 , page 27) command. - _6_._5_._1 _g_e_n_e_r_i_c + _7_._5_._1 _g_e_n_e_r_i_c The _g_e_n_e_r_i_c menu is not a real menu, but specifies common functions (such as movement) available in all menus except for _p_a_g_e_r and _e_d_i_t_o_r. Changing set- @@ -8940,9 +9441,11 @@ top-page H move to the top of the page what-key not bound display the keycode for a key press - _6_._5_._2 _i_n_d_e_x + The Mutt Next Generation E-Mail Client 178 + + _7_._5_._2 _i_n_d_e_x - The Mutt Next Generation E-Mail Client 169 + The Mutt Next Generation E-Mail Client 179 bounce-message b remail a message to another user change-folder c open a different folder @@ -8999,7 +9502,7 @@ show-version V show the Mutt-ng version number and date show-limit ESC l show currently active limit pattern, if any - The Mutt Next Generation E-Mail Client 170 + The Mutt Next Generation E-Mail Client 180 sort-mailbox o sort messages sort-reverse O sort messages in reverse order @@ -9015,9 +9518,9 @@ untag-pattern ^T untag messages matching a pattern view-attachments v show MIME attachments - _6_._5_._3 _p_a_g_e_r + _7_._5_._3 _p_a_g_e_r - The Mutt Next Generation E-Mail Client 171 + The Mutt Next Generation E-Mail Client 181 bottom not bound jump to the bottom of the message bounce-message b remail a message to another user @@ -9074,7 +9577,7 @@ recall-message R recall a postponed message redraw-screen ^L clear and redraw the screen - The Mutt Next Generation E-Mail Client 172 + The Mutt Next Generation E-Mail Client 182 reply r reply to a message save-message s save message/attachment to a file @@ -9095,13 +9598,13 @@ undelete-thread ^U undelete all messages in thread view-attachments v show MIME attachments - _6_._5_._4 _a_l_i_a_s + _7_._5_._4 _a_l_i_a_s search / search for a regular expression search-next n search for next match search-reverse ESC / search backwards for a regular expression - _6_._5_._5 _q_u_e_r_y + _7_._5_._5 _q_u_e_r_y create-alias a create an alias from a message sender mail m compose a new mail message @@ -9112,9 +9615,9 @@ search-opposite not bound search for next match in opposite direction search-reverse ESC / search backwards for a regular expression - _6_._5_._6 _a_t_t_a_c_h + _7_._5_._6 _a_t_t_a_c_h - The Mutt Next Generation E-Mail Client 173 + The Mutt Next Generation E-Mail Client 183 bounce-message b remail a message to another user collapse-parts v toggle display of subparts @@ -9135,9 +9638,9 @@ view-mailcap m force viewing of attachment using mailcap view-text T view attachment as text - _6_._5_._7 _c_o_m_p_o_s_e + _7_._5_._7 _c_o_m_p_o_s_e - The Mutt Next Generation E-Mail Client 174 + The Mutt Next Generation E-Mail Client 184 attach-file a attach a file(s) to this message attach-message A attach message(s) to this message @@ -9173,14 +9676,14 @@ view-attach RET view attachment using mailcap entry if necessary write-fcc w write the message to a folder - _6_._5_._8 _p_o_s_t_p_o_n_e + _7_._5_._8 _p_o_s_t_p_o_n_e delete-entry d delete the current entry undelete-entry u undelete the current entry - _6_._5_._9 _b_r_o_w_s_e_r + _7_._5_._9 _b_r_o_w_s_e_r - The Mutt Next Generation E-Mail Client 175 + The Mutt Next Generation E-Mail Client 185 change-dir c change directories check-new TAB check mailboxes for new mail @@ -9197,12 +9700,12 @@ unsubscribe u unsubscribe to current mailbox (IMAP Only) toggle-subscribed T toggle view all/subscribed mailboxes (IMAP Only) - _6_._5_._1_0 _p_g_p + _7_._5_._1_0 _p_g_p view-name % view the key's user id verify-key c verify a PGP public key - _6_._5_._1_1 _e_d_i_t_o_r + _7_._5_._1_1 _e_d_i_t_o_r backspace BackSpace delete the char in front of the cursor backward-char ^B move the cursor one character to the left @@ -9227,11 +9730,11 @@ transpose-chars not bound transpose character under cursor with previous upcase-word ESC u uppercase all characters in current word - _7_. _M_i_s_c_e_l_l_a_n_y + _8_. _M_i_s_c_e_l_l_a_n_y - The Mutt Next Generation E-Mail Client 176 + The Mutt Next Generation E-Mail Client 186 - _7_._1 _A_c_k_n_o_w_l_e_d_g_m_e_n_t_s + _8_._1 _A_c_k_n_o_w_l_e_d_g_m_e_n_t_s Kari Hurtta co-developed the original MIME parsing code back in the ELM-ME days. @@ -9286,7 +9789,7 @@ Felix von Leitner (a.k.a ``Fefe'') , - The Mutt Next Generation E-Mail Client 177 + The Mutt Next Generation E-Mail Client 187 Brandon Long , @@ -9342,14 +9845,14 @@ Elimar Riesebieter - The Mutt Next Generation E-Mail Client 178 + The Mutt Next Generation E-Mail Client 188 - _7_._2 _A_b_o_u_t _t_h_i_s _d_o_c_u_m_e_n_t + _8_._2 _A_b_o_u_t _t_h_i_s _d_o_c_u_m_e_n_t This document was written in SGML, and then rendered using the sgml-tools pack- age. - The Mutt Next Generation E-Mail Client 179 + The Mutt Next Generation E-Mail Client 189 CONTENTS @@ -9398,483 +9901,522 @@ 3. Configuration ........................................................ 21 3.1 Locations of Configuration Files ............................... 21 - 3.2 Syntax of Initialization Files ................................. 21 - 3.3 Defining/Using aliases ......................................... 23 - 3.4 Changing the default key bindings .............................. 24 - 3.5 Defining aliases for character sets ........................... 26 + 3.2 Basic Syntax of Initialization Files ........................... 21 + 3.3 Expansion within variables ................................... 23 + 3.3.1 Commands' Output 23 + 3.3.2 Environment Variables 23 i - 3.6 Setting variables based upon mailbox ........................... 26 - 3.7 Keyboard macros ................................................ 27 - 3.8 Using color and mono video attributes .......................... 28 - 3.9 Ignoring (weeding) unwanted message headers .................... 30 - 3.10 Alternative addresses .......................................... 31 - 3.11 Format = Flowed ................................................ 31 - 3.12 Mailing lists .................................................. 32 - 3.13 Using Multiple spool mailboxes ................................. 33 - 3.14 Defining mailboxes which receive mail .......................... 34 - 3.15 User defined headers ........................................... 34 - 3.16 Defining the order of headers when viewing messages ............ 35 - 3.17 Specify default save filename .................................. 35 - 3.18 Specify default Fcc: mailbox when composing .................... 36 - 3.19 Specify default save filename and default Fcc: mailbox at once . 36 - 3.20 Change settings based upon message recipients .................. 36 - 3.21 Change settings before formatting a message .................... 37 - 3.22 Choosing the cryptographic key of the recipient ................ 37 - 3.23 Adding key sequences to the keyboard buffer .................... 38 - 3.24 Executing functions ............................................ 38 - 3.25 Message Scoring ................................................ 38 - 3.26 Spam detection ................................................. 39 - 3.27 Setting variables .............................................. 41 - 3.28 Reading initialization commands from another file .............. 42 - 3.29 Removing hooks ................................................. 42 - 3.30 Sharing Setups ............................................. 43 - 3.30.1 Character Sets 43 - 3.30.2 Modularization 43 - 3.30.3 Conditional parts 43 - 3.31 Obsolete Variables ............................................. 45 - - 4. Advanced Usage ....................................................... 45 - 4.1 Regular Expressions ............................................ 45 - 4.2 Patterns ....................................................... 48 - 4.2.1 Complex Patterns 49 - 4.2.2 Patterns and Dates 49 - 4.3 Format Strings ............................................. 50 - 4.3.1 Introduction 50 - 4.3.2 Conditional Expansion 51 - 4.3.3 Modifications and Padding 52 - 4.4 Using Tags ..................................................... 53 - 4.5 Using Hooks .................................................... 53 - 4.5.1 Message Matching in Hooks 54 - 4.6 Using the sidebar .............................................. 54 - 4.7 External Address Queries ....................................... 55 - 4.8 Mailbox Formats ................................................ 56 - 4.9 Mailbox Shortcuts .............................................. 57 - 4.10 Handling Mailing Lists ......................................... 57 - 4.11 Editing threads ................................................ 59 - 4.11.1 Linking threads 59 - 4.11.2 Breaking threads 59 - 4.12 Delivery Status Notification (DSN) Support ..................... 59 - 4.13 POP3 Support (OPTIONAL) ........................................ 60 - 4.14 IMAP Support (OPTIONAL) ........................................ 60 + 3.3.3 Configuration Variables 23 + 3.3.4 Self-Defined Variables 24 + 3.3.5 Pre-Defined Variables 25 + 3.3.6 Type Conversions 26 + 3.4 Defining/Using aliases ......................................... 26 + 3.5 Changing the default key bindings .............................. 27 + 3.6 Defining aliases for character sets ........................... 29 + 3.7 Setting variables based upon mailbox ........................... 29 + 3.8 Keyboard macros ................................................ 30 + 3.9 Using color and mono video attributes .......................... 31 + 3.10 Ignoring (weeding) unwanted message headers .................... 33 + 3.11 Alternative addresses .......................................... 34 + 3.12 Format = Flowed .............................................. 34 + 3.12.1 Introduction 34 + 3.12.2 Receiving: Display Setup 34 + 3.12.3 Sending 35 + 3.12.4 Additional Notes 36 + 3.13 Mailing lists .................................................. 36 + 3.14 Using Multiple spool mailboxes ................................. 37 + 3.15 Defining mailboxes which receive mail .......................... 37 + 3.16 User defined headers ........................................... 38 + 3.17 Defining the order of headers when viewing messages ............ 39 + 3.18 Specify default save filename .................................. 39 + 3.19 Specify default Fcc: mailbox when composing .................... 39 + 3.20 Specify default save filename and default Fcc: mailbox at once . 40 + 3.21 Change settings based upon message recipients .................. 40 + 3.22 Change settings before formatting a message .................... 41 + 3.23 Choosing the cryptographic key of the recipient ................ 41 + 3.24 Adding key sequences to the keyboard buffer .................... 41 + 3.25 Executing functions ............................................ 42 + 3.26 Message Scoring ................................................ 42 + 3.27 Spam detection ................................................. 43 + 3.28 Setting variables .............................................. 45 + 3.29 Reading initialization commands from another file .............. 46 + 3.30 Removing hooks ................................................. 46 + 3.31 Sharing Setups ............................................. 46 + 3.31.1 Character Sets 46 + 3.31.2 Modularization 47 + 3.31.3 Conditional parts 47 + 3.32 Obsolete Variables ............................................. 49 + + 4. Advanced Usage ....................................................... 49 + 4.1 Regular Expressions ............................................ 49 + 4.2 Patterns ....................................................... 52 + 4.2.1 Complex Patterns 52 + 4.2.2 Patterns and Dates 53 + 4.3 Format Strings ............................................. 53 + 4.3.1 Introduction 53 + 4.3.2 Conditional Expansion 55 + 4.3.3 Modifications and Padding 56 + 4.4 Using Tags ..................................................... 56 + 4.5 Using Hooks .................................................... 57 + 4.5.1 Message Matching in Hooks 58 ii - 4.14.1 The Folder Browser 61 - 4.14.2 Authentication 62 - 4.15 NNTP Support (OPTIONAL) ........................................ 62 - 4.15.1 Again: Scoring 63 - 4.16 SMTP Support (OPTIONAL) ........................................ 63 - 4.17 Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) ............ 64 - 4.18 Start a WWW Browser on URLs (EXTERNAL) ......................... 64 - 4.19 Compressed folders Support (OPTIONAL) .......................... 65 - 4.19.1 Open a compressed mailbox for reading 65 - 4.19.2 Write a compressed mailbox 66 - 4.19.3 Append a message to a compressed mailbox 66 - 4.19.4 Encrypted folders 67 - - 5. Mutt-ng's MIME Support ............................................... 67 - 5.1 Using MIME in Mutt ............................................. 67 - 5.1.1 Viewing MIME messages in the pager 68 - 5.1.2 The Attachment Menu 68 - 5.1.3 The Compose Menu 68 - 5.2 MIME Type configuration with mime.types ........................ 69 - 5.3 MIME Viewer configuration with mailcap ......................... 69 - 5.3.1 The Basics of the mailcap file 70 - 5.3.2 Secure use of mailcap 71 - 5.3.3 Advanced mailcap Usage 72 - 5.3.4 Example mailcap files 74 - 5.4 MIME Autoview .................................................. 75 - 5.5 MIME Multipart/Alternative ..................................... 76 - 5.6 MIME Lookup .................................................... 76 - - 6. Reference ............................................................ 77 - 6.1 Command line options ........................................... 77 - 6.2 Patterns ....................................................... 78 - 6.3 Configuration Commands ......................................... 80 - 6.4 Configuration variables .......................................... 82 - 6.4.1 abort_nosubject 83 - 6.4.2 abort_unmodified 84 - 6.4.3 alias_file 84 - 6.4.4 alias_format 84 - 6.4.5 allow_8bit 84 - 6.4.6 allow_ansi 85 - 6.4.7 arrow_cursor 85 - 6.4.8 ascii_chars 85 - 6.4.9 askbcc 85 - 6.4.10 askcc 85 - 6.4.11 assumed_charset 86 - 6.4.12 attach_format 86 - 6.4.13 attach_sep 87 - 6.4.14 attach_split 87 - 6.4.15 attribution 87 - 6.4.16 auto_tag 87 - 6.4.17 autoedit 88 - 6.4.18 beep 88 - 6.4.19 beep_new 88 - 6.4.20 bounce 88 + 4.6 Using the sidebar .............................................. 58 + 4.7 External Address Queries ....................................... 59 + 4.8 Mailbox Formats ................................................ 60 + 4.9 Mailbox Shortcuts .............................................. 61 + 4.10 Handling Mailing Lists ......................................... 61 + 4.11 Editing threads ................................................ 62 + 4.11.1 Linking threads 63 + 4.11.2 Breaking threads 63 + 4.12 Delivery Status Notification (DSN) Support ..................... 63 + 4.13 POP3 Support (OPTIONAL) ........................................ 63 + 4.14 IMAP Support (OPTIONAL) ........................................ 64 + 4.14.1 The Folder Browser 65 + 4.14.2 Authentication 65 + 4.15 NNTP Support (OPTIONAL) ........................................ 66 + 4.15.1 Again: Scoring 66 + 4.16 SMTP Support (OPTIONAL) ........................................ 67 + 4.17 Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) ............ 68 + 4.18 Start a WWW Browser on URLs (EXTERNAL) ......................... 68 + 4.19 Compressed folders Support (OPTIONAL) .......................... 68 + 4.19.1 Open a compressed mailbox for reading 69 + 4.19.2 Write a compressed mailbox 69 + 4.19.3 Append a message to a compressed mailbox 70 + 4.19.4 Encrypted folders 71 + + 5. Mutt-ng's MIME Support ............................................... 71 + 5.1 Using MIME in Mutt ............................................. 71 + 5.1.1 Viewing MIME messages in the pager 71 + 5.1.2 The Attachment Menu 72 + 5.1.3 The Compose Menu 72 + 5.2 MIME Type configuration with mime.types ........................ 72 + 5.3 MIME Viewer configuration with mailcap ......................... 73 + 5.3.1 The Basics of the mailcap file 74 + 5.3.2 Secure use of mailcap 75 + 5.3.3 Advanced mailcap Usage 75 + 5.3.4 Example mailcap files 78 + 5.4 MIME Autoview .................................................. 79 + 5.5 MIME Multipart/Alternative ..................................... 80 + 5.6 MIME Lookup .................................................... 80 + + 6. Security Considerations ............................................ 81 + 6.1 Passwords .................................................. 81 + 6.2 Temporary Files ............................................ 81 + 6.3 Information Leaks ............................................ 81 + 6.3.1 Message-ID: headers 81 + 6.3.2 mailto:-style links 82 + 6.4 External applications ...................................... 82 + 6.4.1 mailcap 82 + 6.4.2 Other 83 + + 7. Reference ............................................................ 83 + 7.1 Command line options ........................................... 83 + 7.2 Patterns ....................................................... 84 + 7.3 Configuration Commands ......................................... 86 iii - 6.4.21 bounce_delivered 88 - 6.4.22 braille_friendly 89 - 6.4.23 certificate_file 89 - 6.4.24 charset 89 - 6.4.25 check_new 89 - 6.4.26 collapse_unread 90 - 6.4.27 compose_format 90 - 6.4.28 config_charset 90 - 6.4.29 confirmappend 90 - 6.4.30 confirmcreate 91 - 6.4.31 connect_timeout 91 - 6.4.32 content_type 91 - 6.4.33 copy 91 - 6.4.34 crypt_autoencrypt 91 - 6.4.35 crypt_autopgp 92 - 6.4.36 crypt_autosign 92 - 6.4.37 crypt_autosmime 92 - 6.4.38 crypt_replyencrypt 92 - 6.4.39 crypt_replysign 92 - 6.4.40 crypt_replysignencrypted 93 - 6.4.41 crypt_timestamp 93 - 6.4.42 crypt_use_gpgme 93 - 6.4.43 crypt_verify_sig 93 - 6.4.44 date_format 93 - 6.4.45 default_hook 94 - 6.4.46 delete 94 - 6.4.47 delete_untag 94 - 6.4.48 digest_collapse 94 - 6.4.49 display_filter 95 - 6.4.50 dotlock_program 95 - 6.4.51 dsn_notify 95 - 6.4.52 dsn_return 95 - 6.4.53 duplicate_threads 96 - 6.4.54 edit_headers 96 - 6.4.55 editor 96 - 6.4.56 encode_from 96 - 6.4.57 entropy_file 96 - 6.4.58 envelope_from 97 - 6.4.59 escape 97 - 6.4.60 fast_reply 97 - 6.4.61 fcc_attach 97 - 6.4.62 fcc_clear 97 - 6.4.63 file_charset 97 - 6.4.64 folder 98 - 6.4.65 folder_format 98 - 6.4.66 followup_to 99 - 6.4.67 force_buffy_check 99 - 6.4.68 force_name 99 - 6.4.69 forward_decode 100 - 6.4.70 forward_decrypt 100 - 6.4.71 forward_edit 100 - 6.4.72 forward_format 100 - 6.4.73 forward_quote 100 + 7.4 Configuration variables .......................................... 88 + 7.4.1 abort_noattach 89 + 7.4.2 abort_nosubject 90 + 7.4.3 abort_unmodified 90 + 7.4.4 agent_string 90 + 7.4.5 alias_file 90 + 7.4.6 alias_format 90 + 7.4.7 allow_8bit 91 + 7.4.8 allow_ansi 91 + 7.4.9 arrow_cursor 91 + 7.4.10 ascii_chars 92 + 7.4.11 askbcc 92 + 7.4.12 askcc 92 + 7.4.13 assumed_charset 92 + 7.4.14 attach_format 92 + 7.4.15 attach_remind_regexp 93 + 7.4.16 attach_sep 94 + 7.4.17 attach_split 94 + 7.4.18 attribution 94 + 7.4.19 auto_tag 94 + 7.4.20 autoedit 94 + 7.4.21 beep 95 + 7.4.22 beep_new 95 + 7.4.23 bounce 95 + 7.4.24 bounce_delivered 95 + 7.4.25 braille_friendly 95 + 7.4.26 certificate_file 96 + 7.4.27 charset 96 + 7.4.28 check_new 96 + 7.4.29 collapse_unread 96 + 7.4.30 compose_format 97 + 7.4.31 config_charset 97 + 7.4.32 confirmappend 97 + 7.4.33 confirmcreate 97 + 7.4.34 connect_timeout 97 + 7.4.35 content_type 98 + 7.4.36 copy 98 + 7.4.37 crypt_autoencrypt 98 + 7.4.38 crypt_autopgp 98 + 7.4.39 crypt_autosign 99 + 7.4.40 crypt_autosmime 99 + 7.4.41 crypt_replyencrypt 99 + 7.4.42 crypt_replysign 99 + 7.4.43 crypt_replysignencrypted 99 + 7.4.44 crypt_timestamp 100 + 7.4.45 crypt_use_gpgme 100 + 7.4.46 crypt_verify_sig 100 + 7.4.47 date_format 100 + 7.4.48 debug_level 101 + 7.4.49 default_hook 101 + 7.4.50 delete 101 + 7.4.51 delete_space 101 + 7.4.52 delete_untag 102 iv - 6.4.74 from 101 - 6.4.75 gecos_mask 101 - 6.4.76 hdrs 101 - 6.4.77 header 101 - 6.4.78 header_cache 102 - 6.4.79 header_cache_compress 102 - 6.4.80 help 102 - 6.4.81 hidden_host 102 - 6.4.82 hide_limited 103 - 6.4.83 hide_missing 103 - 6.4.84 hide_thread_subject 103 - 6.4.85 hide_top_limited 103 - 6.4.86 hide_top_missing 103 - 6.4.87 history 103 - 6.4.88 honor_followup_to 104 - 6.4.89 hostname 104 - 6.4.90 ignore_list_reply_to 104 - 6.4.91 imap_authenticators 104 - 6.4.92 imap_check_subscribed 105 - 6.4.93 imap_delim_chars 105 - 6.4.94 imap_headers 105 - 6.4.95 imap_home_namespace 105 - 6.4.96 imap_keepalive 106 - 6.4.97 imap_list_subscribed 106 - 6.4.98 imap_login 106 - 6.4.99 imap_mail_check 106 - 6.4.100 imap_pass 107 - 6.4.101 imap_passive 107 - 6.4.102 imap_peek 107 - 6.4.103 imap_reconnect 107 - 6.4.104 imap_servernoise 108 - 6.4.105 imap_user 108 - 6.4.106 implicit_autoview 108 - 6.4.107 include 108 - 6.4.108 include_onlyfirst 108 - 6.4.109 indent_string 109 - 6.4.110 index_format 109 - 6.4.111 ispell 111 - 6.4.112 keep_flagged 112 - 6.4.113 list_reply 112 - 6.4.114 locale 112 - 6.4.115 mail_check 112 - 6.4.116 mailcap_path 112 - 6.4.117 mailcap_sanitize 113 - 6.4.118 maildir_header_cache_verify 113 - 6.4.119 maildir_trash 113 - 6.4.120 mark_old 113 - 6.4.121 markers 114 - 6.4.122 mask 114 - 6.4.123 max_line_length 114 - 6.4.124 mbox 114 - 6.4.125 mbox_type 114 - 6.4.126 menu_context 114 + 7.4.53 digest_collapse 102 + 7.4.54 display_filter 102 + 7.4.55 dotlock_program 102 + 7.4.56 dsn_notify 102 + 7.4.57 dsn_return 103 + 7.4.58 duplicate_threads 103 + 7.4.59 edit_headers 103 + 7.4.60 editor 103 + 7.4.61 editor_headers 103 + 7.4.62 encode_from 104 + 7.4.63 entropy_file 104 + 7.4.64 envelope_from 104 + 7.4.65 escape 104 + 7.4.66 fast_reply 105 + 7.4.67 fcc_attach 105 + 7.4.68 fcc_clear 105 + 7.4.69 file_charset 105 + 7.4.70 folder 105 + 7.4.71 folder_format 106 + 7.4.72 followup_to 107 + 7.4.73 force_buffy_check 107 + 7.4.74 force_name 107 + 7.4.75 forward_decode 107 + 7.4.76 forward_decrypt 108 + 7.4.77 forward_edit 108 + 7.4.78 forward_format 108 + 7.4.79 forward_quote 108 + 7.4.80 from 108 + 7.4.81 gecos_mask 109 + 7.4.82 hdrs 109 + 7.4.83 header 109 + 7.4.84 header_cache 109 + 7.4.85 header_cache_compress 110 + 7.4.86 help 110 + 7.4.87 hidden_host 110 + 7.4.88 hide_limited 110 + 7.4.89 hide_missing 110 + 7.4.90 hide_thread_subject 111 + 7.4.91 hide_top_limited 111 + 7.4.92 hide_top_missing 111 + 7.4.93 history 111 + 7.4.94 honor_followup_to 111 + 7.4.95 hostname 112 + 7.4.96 ignore_list_reply_to 112 + 7.4.97 imap_authenticators 112 + 7.4.98 imap_check_subscribed 112 + 7.4.99 imap_delim_chars 113 + 7.4.100 imap_headers 113 + 7.4.101 imap_home_namespace 113 + 7.4.102 imap_keepalive 113 + 7.4.103 imap_list_subscribed 114 + 7.4.104 imap_login 114 + 7.4.105 imap_mail_check 114 v - 6.4.127 menu_move_off 115 - 6.4.128 menu_scroll 115 - 6.4.129 message_format 115 - 6.4.130 meta_key 115 - 6.4.131 metoo 115 - 6.4.132 mh_purge 116 - 6.4.133 mh_seq_flagged 116 - 6.4.134 mh_seq_replied 116 - 6.4.135 mh_seq_unseen 116 - 6.4.136 mime_forward 116 - 6.4.137 mime_forward_decode 117 - 6.4.138 mime_forward_rest 117 - 6.4.139 mix_entry_format 117 - 6.4.140 mixmaster 117 - 6.4.141 move 118 - 6.4.142 msgid_format 118 - 6.4.143 narrow_tree 119 - 6.4.144 nntp_ask_followup_to 119 - 6.4.145 nntp_ask_x_comment_to 119 - 6.4.146 nntp_cache_dir 119 - 6.4.147 nntp_catchup 120 - 6.4.148 nntp_context 120 - 6.4.149 nntp_followup_to_poster 120 - 6.4.150 nntp_group_index_format 120 - 6.4.151 nntp_host 121 - 6.4.152 nntp_inews 121 - 6.4.153 nntp_load_description 121 - 6.4.154 nntp_mail_check 122 - 6.4.155 nntp_mime_subject 122 - 6.4.156 nntp_newsrc 122 - 6.4.157 nntp_pass 122 - 6.4.158 nntp_post_moderated 123 - 6.4.159 nntp_reconnect 123 - 6.4.160 nntp_save_unsubscribed 123 - 6.4.161 nntp_show_new_news 123 - 6.4.162 nntp_show_only_unread 124 - 6.4.163 nntp_user 124 - 6.4.164 nntp_x_comment_to 124 - 6.4.165 operating_system 124 - 6.4.166 pager 124 - 6.4.167 pager_context 125 - 6.4.168 pager_format 125 - 6.4.169 pager_index_lines 125 - 6.4.170 pager_stop 125 - 6.4.171 pgp_auto_decode 126 - 6.4.172 pgp_autoinline 126 - 6.4.173 pgp_check_exit 126 - 6.4.174 pgp_clearsign_command 126 - 6.4.175 pgp_decode_command 127 - 6.4.176 pgp_decrypt_command 127 - 6.4.177 pgp_encrypt_only_command 127 - 6.4.178 pgp_encrypt_sign_command 127 - 6.4.179 pgp_entry_format 128 + 7.4.106 imap_pass 114 + 7.4.107 imap_passive 115 + 7.4.108 imap_peek 115 + 7.4.109 imap_reconnect 115 + 7.4.110 imap_servernoise 115 + 7.4.111 imap_user 116 + 7.4.112 implicit_autoview 116 + 7.4.113 include 116 + 7.4.114 include_onlyfirst 116 + 7.4.115 indent_string 116 + 7.4.116 index_format 116 + 7.4.117 ispell 119 + 7.4.118 keep_flagged 119 + 7.4.119 list_reply 120 + 7.4.120 locale 120 + 7.4.121 mail_check 120 + 7.4.122 mailcap_path 120 + 7.4.123 mailcap_sanitize 120 + 7.4.124 maildir_header_cache_verify 120 + 7.4.125 maildir_trash 121 + 7.4.126 mark_old 121 + 7.4.127 markers 121 + 7.4.128 mask 121 + 7.4.129 max_display_recips 122 + 7.4.130 max_line_length 122 + 7.4.131 mbox 122 + 7.4.132 mbox_type 122 + 7.4.133 menu_context 122 + 7.4.134 menu_move_off 123 + 7.4.135 menu_scroll 123 + 7.4.136 message_format 123 + 7.4.137 meta_key 123 + 7.4.138 metoo 123 + 7.4.139 mh_purge 124 + 7.4.140 mh_seq_flagged 124 + 7.4.141 mh_seq_replied 124 + 7.4.142 mh_seq_unseen 124 + 7.4.143 mime_forward 124 + 7.4.144 mime_forward_decode 124 + 7.4.145 mime_forward_rest 125 + 7.4.146 mix_entry_format 125 + 7.4.147 mixmaster 125 + 7.4.148 move 125 + 7.4.149 msgid_format 126 + 7.4.150 muttng_bindir 127 + 7.4.151 muttng_docdir 127 + 7.4.152 muttng_folder_name 127 + 7.4.153 muttng_folder_path 127 + 7.4.154 muttng_hcache_backend 127 + 7.4.155 muttng_pwd 128 + 7.4.156 muttng_revision 128 + 7.4.157 muttng_sysconfdir 128 + 7.4.158 muttng_version 128 vi - 6.4.180 pgp_export_command 128 - 6.4.181 pgp_getkeys_command 128 - 6.4.182 pgp_good_sign 129 - 6.4.183 pgp_ignore_subkeys 129 - 6.4.184 pgp_import_command 129 - 6.4.185 pgp_list_pubring_command 129 - 6.4.186 pgp_list_secring_command 129 - 6.4.187 pgp_long_ids 130 - 6.4.188 pgp_mime_auto 130 - 6.4.189 pgp_replyinline 130 - 6.4.190 pgp_retainable_sigs 130 - 6.4.191 pgp_show_unusable 131 - 6.4.192 pgp_sign_as 131 - 6.4.193 pgp_sign_command 131 - 6.4.194 pgp_sort_keys 131 - 6.4.195 pgp_strict_enc 132 - 6.4.196 pgp_timeout 132 - 6.4.197 pgp_use_gpg_agent 132 - 6.4.198 pgp_verify_command 132 - 6.4.199 pgp_verify_key_command 132 - 6.4.200 pipe_decode 132 - 6.4.201 pipe_sep 133 - 6.4.202 pipe_split 133 - 6.4.203 pop_auth_try_all 133 - 6.4.204 pop_authenticators 133 - 6.4.205 pop_delete 134 - 6.4.206 pop_host 134 - 6.4.207 pop_last 134 - 6.4.208 pop_mail_check 134 - 6.4.209 pop_pass 135 - 6.4.210 pop_reconnect 135 - 6.4.211 pop_user 135 - 6.4.212 post_indent_string 135 - 6.4.213 postpone 135 - 6.4.214 postponed 136 - 6.4.215 preconnect 136 - 6.4.216 print 136 - 6.4.217 print_command 136 - 6.4.218 print_decode 136 - 6.4.219 print_split 137 - 6.4.220 prompt_after 137 - 6.4.221 query_command 137 - 6.4.222 quit 137 - 6.4.223 quote_empty 138 - 6.4.224 quote_quoted 138 - 6.4.225 quote_regexp 138 - 6.4.226 read_inc 138 - 6.4.227 read_only 138 - 6.4.228 realname 139 - 6.4.229 recall 139 - 6.4.230 record 139 - 6.4.231 reply_regexp 139 - 6.4.232 reply_self 140 + 7.4.159 narrow_tree 128 + 7.4.160 nntp_ask_followup_to 128 + 7.4.161 nntp_ask_x_comment_to 129 + 7.4.162 nntp_cache_dir 129 + 7.4.163 nntp_catchup 129 + 7.4.164 nntp_context 129 + 7.4.165 nntp_followup_to_poster 129 + 7.4.166 nntp_group_index_format 130 + 7.4.167 nntp_host 130 + 7.4.168 nntp_inews 131 + 7.4.169 nntp_load_description 131 + 7.4.170 nntp_mail_check 131 + 7.4.171 nntp_mime_subject 131 + 7.4.172 nntp_newsrc 132 + 7.4.173 nntp_pass 132 + 7.4.174 nntp_post_moderated 132 + 7.4.175 nntp_reconnect 132 + 7.4.176 nntp_save_unsubscribed 133 + 7.4.177 nntp_show_new_news 133 + 7.4.178 nntp_show_only_unread 133 + 7.4.179 nntp_user 133 + 7.4.180 nntp_x_comment_to 133 + 7.4.181 operating_system 134 + 7.4.182 pager 134 + 7.4.183 pager_context 134 + 7.4.184 pager_format 134 + 7.4.185 pager_index_lines 135 + 7.4.186 pager_stop 135 + 7.4.187 pgp_auto_decode 135 + 7.4.188 pgp_autoinline 135 + 7.4.189 pgp_check_exit 136 + 7.4.190 pgp_clearsign_command 136 + 7.4.191 pgp_decode_command 136 + 7.4.192 pgp_decrypt_command 137 + 7.4.193 pgp_encrypt_only_command 137 + 7.4.194 pgp_encrypt_sign_command 137 + 7.4.195 pgp_entry_format 137 + 7.4.196 pgp_export_command 138 + 7.4.197 pgp_getkeys_command 138 + 7.4.198 pgp_good_sign 138 + 7.4.199 pgp_ignore_subkeys 138 + 7.4.200 pgp_import_command 138 + 7.4.201 pgp_list_pubring_command 139 + 7.4.202 pgp_list_secring_command 139 + 7.4.203 pgp_long_ids 139 + 7.4.204 pgp_mime_auto 139 + 7.4.205 pgp_replyinline 139 + 7.4.206 pgp_retainable_sigs 140 + 7.4.207 pgp_show_unusable 140 + 7.4.208 pgp_sign_as 140 + 7.4.209 pgp_sign_command 140 + 7.4.210 pgp_sort_keys 141 + 7.4.211 pgp_strict_enc 141 vii - 6.4.233 reply_to 140 - 6.4.234 resolve 140 - 6.4.235 reverse_alias 140 - 6.4.236 reverse_name 141 - 6.4.237 reverse_realname 141 - 6.4.238 rfc2047_parameters 141 - 6.4.239 save_address 141 - 6.4.240 save_empty 142 - 6.4.241 save_name 142 - 6.4.242 score 142 - 6.4.243 score_threshold_delete 142 - 6.4.244 score_threshold_flag 143 - 6.4.245 score_threshold_read 143 - 6.4.246 send_charset 143 - 6.4.247 sendmail 143 - 6.4.248 sendmail_wait 143 - 6.4.249 shell 144 - 6.4.250 sidebar_boundary 144 - 6.4.251 sidebar_delim 144 - 6.4.252 sidebar_newmail_only 144 - 6.4.253 sidebar_number_format 144 - 6.4.254 sidebar_shorten_hierarchy 145 - 6.4.255 sidebar_visible 145 - 6.4.256 sidebar_width 146 - 6.4.257 sig_dashes 146 - 6.4.258 sig_on_top 146 - 6.4.259 signature 146 - 6.4.260 signoff_string 146 - 6.4.261 simple_search 147 - 6.4.262 sleep_time 147 - 6.4.263 smart_wrap 147 - 6.4.264 smileys 147 - 6.4.265 smime_ask_cert_label 147 - 6.4.266 smime_ca_location 148 - 6.4.267 smime_certificates 148 - 6.4.268 smime_decrypt_command 148 - 6.4.269 smime_decrypt_use_default_key 149 - 6.4.270 smime_default_key 149 - 6.4.271 smime_encrypt_command 149 - 6.4.272 smime_encrypt_with 149 - 6.4.273 smime_get_cert_command 150 - 6.4.274 smime_get_cert_email_command 150 - 6.4.275 smime_get_signer_cert_command 150 - 6.4.276 smime_import_cert_command 150 - 6.4.277 smime_is_default 150 - 6.4.278 smime_keys 150 - 6.4.279 smime_pk7out_command 151 - 6.4.280 smime_sign_command 151 - 6.4.281 smime_sign_opaque_command 151 - 6.4.282 smime_timeout 151 - 6.4.283 smime_verify_command 151 - 6.4.284 smime_verify_opaque_command 152 - 6.4.285 smtp_envelope 152 + 7.4.212 pgp_timeout 141 + 7.4.213 pgp_use_gpg_agent 141 + 7.4.214 pgp_verify_command 142 + 7.4.215 pgp_verify_key_command 142 + 7.4.216 pipe_decode 142 + 7.4.217 pipe_sep 142 + 7.4.218 pipe_split 142 + 7.4.219 pop_auth_try_all 142 + 7.4.220 pop_authenticators 143 + 7.4.221 pop_delete 143 + 7.4.222 pop_host 143 + 7.4.223 pop_last 144 + 7.4.224 pop_mail_check 144 + 7.4.225 pop_pass 144 + 7.4.226 pop_reconnect 144 + 7.4.227 pop_user 144 + 7.4.228 post_indent_string 145 + 7.4.229 postpone 145 + 7.4.230 postponed 145 + 7.4.231 preconnect 145 + 7.4.232 print 146 + 7.4.233 print_command 146 + 7.4.234 print_decode 146 + 7.4.235 print_split 146 + 7.4.236 prompt_after 146 + 7.4.237 query_command 147 + 7.4.238 quit 147 + 7.4.239 quote_empty 147 + 7.4.240 quote_quoted 147 + 7.4.241 quote_regexp 147 + 7.4.242 read_inc 148 + 7.4.243 read_only 148 + 7.4.244 realname 148 + 7.4.245 recall 148 + 7.4.246 record 148 + 7.4.247 reply_regexp 149 + 7.4.248 reply_self 149 + 7.4.249 reply_to 149 + 7.4.250 resolve 149 + 7.4.251 reverse_alias 150 + 7.4.252 reverse_name 150 + 7.4.253 reverse_realname 150 + 7.4.254 rfc2047_parameters 150 + 7.4.255 save_address 151 + 7.4.256 save_empty 151 + 7.4.257 save_name 151 + 7.4.258 score 152 + 7.4.259 score_threshold_delete 152 + 7.4.260 score_threshold_flag 152 + 7.4.261 score_threshold_read 152 + 7.4.262 send_charset 152 + 7.4.263 sendmail 153 + 7.4.264 sendmail_wait 153 viii - 6.4.286 smtp_host 152 - 6.4.287 smtp_pass 152 - 6.4.288 smtp_port 153 - 6.4.289 smtp_use_tls 153 - 6.4.290 smtp_user 153 - 6.4.291 sort 153 - 6.4.292 sort_alias 154 - 6.4.293 sort_aux 154 - 6.4.294 sort_browser 155 - 6.4.295 sort_re 155 - 6.4.296 spam_separator 155 - 6.4.297 spoolfile 155 - 6.4.298 ssl_ca_certificates_file 156 - 6.4.299 ssl_client_cert 156 - 6.4.300 ssl_force_tls 156 - 6.4.301 ssl_min_dh_prime_bits 156 - 6.4.302 ssl_starttls 156 - 6.4.303 ssl_use_sslv2 157 - 6.4.304 ssl_use_sslv3 157 - 6.4.305 ssl_use_tlsv1 157 - 6.4.306 ssl_usesystemcerts 157 - 6.4.307 status_chars 157 - 6.4.308 status_format 158 - 6.4.309 status_on_top 160 - 6.4.310 strict_mailto 160 - 6.4.311 strict_mime 160 - 6.4.312 strict_threads 161 - 6.4.313 strip_was 161 - 6.4.314 strip_was_regex 161 - 6.4.315 stuff_quoted 161 - 6.4.316 suspend 162 - 6.4.317 text_flowed 162 - 6.4.318 thorough_search 162 - 6.4.319 thread_received 162 - 6.4.320 tilde 162 - 6.4.321 timeout 163 - 6.4.322 tmpdir 163 - 6.4.323 to_chars 163 - 6.4.324 trash 163 - 6.4.325 tunnel 163 - 6.4.326 umask 164 - 6.4.327 uncollapse_jump 164 - 6.4.328 use_8bitmime 164 - 6.4.329 use_domain 164 - 6.4.330 use_from 164 - 6.4.331 use_idn 165 - 6.4.332 use_ipv6 165 - 6.4.333 user_agent 165 - 6.4.334 visual 165 - 6.4.335 wait_key 165 - 6.4.336 weed 166 - 6.4.337 wrap_search 166 - 6.4.338 wrapmargin 166 + 7.4.265 shell 153 + 7.4.266 sidebar_boundary 153 + 7.4.267 sidebar_delim 154 + 7.4.268 sidebar_newmail_only 154 + 7.4.269 sidebar_number_format 154 + 7.4.270 sidebar_shorten_hierarchy 155 + 7.4.271 sidebar_visible 155 + 7.4.272 sidebar_width 155 + 7.4.273 sig_dashes 155 + 7.4.274 sig_on_top 155 + 7.4.275 signature 156 + 7.4.276 signoff_string 156 + 7.4.277 simple_search 156 + 7.4.278 sleep_time 156 + 7.4.279 smart_wrap 157 + 7.4.280 smileys 157 + 7.4.281 smime_ask_cert_label 157 + 7.4.282 smime_ca_location 157 + 7.4.283 smime_certificates 157 + 7.4.284 smime_decrypt_command 158 + 7.4.285 smime_decrypt_use_default_key 158 + 7.4.286 smime_default_key 158 + 7.4.287 smime_encrypt_command 159 + 7.4.288 smime_encrypt_with 159 + 7.4.289 smime_get_cert_command 159 + 7.4.290 smime_get_cert_email_command 159 + 7.4.291 smime_get_signer_cert_command 159 + 7.4.292 smime_import_cert_command 160 + 7.4.293 smime_is_default 160 + 7.4.294 smime_keys 160 + 7.4.295 smime_pk7out_command 160 + 7.4.296 smime_sign_command 160 + 7.4.297 smime_sign_opaque_command 161 + 7.4.298 smime_timeout 161 + 7.4.299 smime_verify_command 161 + 7.4.300 smime_verify_opaque_command 161 + 7.4.301 smtp_envelope 161 + 7.4.302 smtp_host 161 + 7.4.303 smtp_pass 162 + 7.4.304 smtp_port 162 + 7.4.305 smtp_use_tls 162 + 7.4.306 smtp_user 163 + 7.4.307 sort 163 + 7.4.308 sort_alias 163 + 7.4.309 sort_aux 163 + 7.4.310 sort_browser 164 + 7.4.311 sort_re 164 + 7.4.312 spam_separator 165 + 7.4.313 spoolfile 165 + 7.4.314 ssl_ca_certificates_file 165 + 7.4.315 ssl_client_cert 165 + 7.4.316 ssl_force_tls 165 + 7.4.317 ssl_min_dh_prime_bits 166 ix - 6.4.339 write_bcc 166 - 6.4.340 write_inc 166 - 6.4.341 xterm_icon 167 - 6.4.342 xterm_leave 167 - 6.4.343 xterm_set_titles 167 - 6.4.344 xterm_title 167 - 6.5 Functions ....................................................... 168 - 6.5.1 generic 168 - 6.5.2 index 168 - 6.5.3 pager 170 - 6.5.4 alias 172 - 6.5.5 query 172 - 6.5.6 attach 172 - 6.5.7 compose 173 - 6.5.8 postpone 174 - 6.5.9 browser 174 - 6.5.10 pgp 175 - 6.5.11 editor 175 - - 7. Miscellany ............................................................ 175 - 7.1 Acknowledgments ................................................. 176 - 7.2 About this document ............................................. 178 + 7.4.318 ssl_starttls 166 + 7.4.319 ssl_use_sslv2 166 + 7.4.320 ssl_use_sslv3 166 + 7.4.321 ssl_use_tlsv1 166 + 7.4.322 ssl_usesystemcerts 167 + 7.4.323 status_chars 167 + 7.4.324 status_format 167 + 7.4.325 status_on_top 169 + 7.4.326 strict_mailto 170 + 7.4.327 strict_mime 170 + 7.4.328 strict_threads 170 + 7.4.329 strip_was 170 + 7.4.330 strip_was_regex 171 + 7.4.331 stuff_quoted 171 + 7.4.332 suspend 171 + 7.4.333 text_flowed 171 + 7.4.334 thorough_search 171 + 7.4.335 thread_received 172 + 7.4.336 tilde 172 + 7.4.337 timeout 172 + 7.4.338 tmpdir 172 + 7.4.339 to_chars 172 + 7.4.340 trash 173 + 7.4.341 tunnel 173 + 7.4.342 umask 173 + 7.4.343 uncollapse_jump 173 + 7.4.344 use_8bitmime 173 + 7.4.345 use_domain 174 + 7.4.346 use_from 174 + 7.4.347 use_idn 174 + 7.4.348 use_ipv6 174 + 7.4.349 visual 174 + 7.4.350 wait_key 175 + 7.4.351 weed 175 + 7.4.352 wrap_search 175 + 7.4.353 wrapmargin 175 + 7.4.354 write_bcc 175 + 7.4.355 write_inc 176 + 7.4.356 xterm_icon 176 + 7.4.357 xterm_leave 176 + 7.4.358 xterm_set_titles 176 + 7.4.359 xterm_title 176 + 7.5 Functions ....................................................... 177 + 7.5.1 generic 177 + 7.5.2 index 178 + 7.5.3 pager 180 + 7.5.4 alias 182 + 7.5.5 query 182 + 7.5.6 attach 182 + 7.5.7 compose 183 + 7.5.8 postpone 184 + 7.5.9 browser 184 + 7.5.10 pgp 185 x + 7.5.11 editor 185 + + 8. Miscellany ............................................................ 185 + 8.1 Acknowledgments ................................................. 186 + 8.2 About this document ............................................. 188 + + xi +