X-Git-Url: http://git.madism.org/?p=apps%2Fmadmutt.git;a=blobdiff_plain;f=doc%2Fmanual.txt;h=ec54e0b8f96697d0c8dd59e28ab87383fcec7990;hp=47b941a3c98bfa55cce0bae2fe728e9941598923;hb=452ffdd4bbcd8f2dd9e4811c115824b556814ebb;hpb=11dfc0aa39e31496da16c708f972a6718dd7ee5c diff --git a/doc/manual.txt b/doc/manual.txt index 47b941a..ec54e0b 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 + version devel-r462 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.320 , page 158) variable. + can be customized with the _$_t_o___c_h_a_r_s (section 7.4.336 , page 171) 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 30) 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 74) script for high- + also be used by an external _a_u_t_o_v_i_e_w (section 5.4 , page 78) 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.289 , page 149) by _t_h_r_e_a_d_s, there are + When the mailbox is _s_o_r_t_e_d (section 7.4.304 , page 161) 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 105). 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 105) to optionally display the number of + tion 7.4.116 , page 115). 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 115) 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.309 , page 156). + See also: _$_s_t_r_i_c_t___t_h_r_e_a_d_s (section 7.4.325 , page 168). _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 80) variable for - future use. NNoottee:: Specifying an _$_a_l_i_a_s___f_i_l_e (section 6.4.3 , page 80) 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 89) variable for + future use. NNoottee:: Specifying an _$_a_l_i_a_s___f_i_l_e (section 7.4.5 , page 89) does not + add the aliases specified there-in, you must also _s_o_u_r_c_e (section 3.29 , page + 45) 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 32) 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 66), 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 67). There, it's used to fine-tune the properties of attachments you are + page 71). 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 29) 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 100) 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 110) 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 129), _$_p_i_p_e___s_p_l_i_t - (section 6.4.202 , page 129), _$_p_i_p_e___s_e_p (section 6.4.201 , page 129) and - _$_w_a_i_t___k_e_y (section 6.4.332 , page 161) control the exact behavior of this + it. The variables _$_p_i_p_e___d_e_c_o_d_e (section 7.4.213 , page 140), _$_p_i_p_e___s_p_l_i_t + (section 7.4.215 , page 141), _$_p_i_p_e___s_e_p (section 7.4.214 , page 140) and + _$_w_a_i_t___k_e_y (section 7.4.347 , page 173) 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.333 , page 161) variable. + the value of the _$_w_e_e_d (section 7.4.348 , page 173) 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.332 , page 161) can be used to control whether Mutt-ng will wait for a key + 7.4.347 , page 173) 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 134) variable to + The _p_a_g_e_r uses the _$_q_u_o_t_e___r_e_g_e_x_p (section 7.4.238 , page 146) 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.305 , page 153) will change to a + folder. The %r in _$_s_t_a_t_u_s___f_o_r_m_a_t (section 7.4.321 , page 165) 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 92). + Also see _e_d_i_t___h_e_a_d_e_r_s (section 7.4.59 , page 102). _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 127) permanently. + _$_p_g_p___s_i_g_n___a_s (section 7.4.205 , page 139) 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 124)) have obvious meanings. But some explana- + _m_a_t (section 7.4.192 , page 135)) 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 113)). 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 124)). 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 132) variable. This means that you can + the _$_p_o_s_t_p_o_n_e_d (section 7.4.227 , page 143) 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 132) quad-option. + See also the _$_p_o_s_t_p_o_n_e (section 7.4.226 , page 143) 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 76) option is specified. This + the ``-n'' _c_o_m_m_a_n_d _l_i_n_e (section 7.1 , page 82) 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 78) to configure Mutt-ng. + your _c_o_m_m_a_n_d_s (section 7.3 , page 85) 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 - 78). 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 + 85). 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,161 @@ 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 85). 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 78). + sets the _$_r_e_c_o_r_d (section 7.4.243 , page 147) 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 112) to + the value to which _$_f_o_l_d_e_r (section 7.4.70 , page 104) 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 112) won't change even if + _$_f_o_l_d_e_r (section 7.4.70 , page 104) 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. + + _N_o_t_e_: _t_h_i_s _i_s _a _d_r_a_f_t _f_e_a_t_u_r_e _a_n_d _m_a_y_b_e _s_u_b_j_e_c_t _t_o _c_h_a_n_g_e _i_n _t_h_e _n_e_a_r _f_u_t_u_r_e_. + + _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): + + The Mutt Next Generation E-Mail Client 26 - _3_._3 _D_e_f_i_n_i_n_g_/_U_s_i_n_g _a_l_i_a_s_e_s + set read_inc = 100 + set folder = $read_inc + set read_inc = $folder + set user_magic_number = 42 + set folder = $user_magic_number + + _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, ... ] @@ -1142,20 +1276,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 45). 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 80) + only one file, the one pointed to by the _$_a_l_i_a_s___f_i_l_e (section 7.4.5 , page 89) 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 45) 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,10 +1295,13 @@ 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 92) variable set. + (section 7.4.59 , page 102) 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 + + The Mutt Next Generation E-Mail Client 27 + will bring up a menu with the matching aliases. In order to be presented with the full list of aliases, you must hit tab with out a partial alias, such as at the beginning of the prompt or after a comma denoting multiple addresses. @@ -1175,7 +1310,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 @@ -1204,11 +1339,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. @@ -1219,6 +1351,8 @@ compose The compose menu is the screen used when sending a new message. + The Mutt Next Generation E-Mail Client 28 + pager The pager is the mode used to display message/attachment data, and help listings. @@ -1240,8 +1374,6 @@ In addition, _k_e_y may consist of: - The Mutt Next Generation E-Mail Client 26 - \t tab tab backtab / shift-tab @@ -1269,10 +1401,12 @@ _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 163). The special + list of functions, see the _r_e_f_e_r_e_n_c_e (section 7.5 , page 175). 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 + The Mutt Next Generation E-Mail Client 29 + + _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 +1420,18 @@ 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 - - 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 + It is often desirable to change settings based on which mailbox you are read- + ing. 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.295 , page - 151) 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.310 , page + 163) 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,36 +1446,36 @@ 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 ] Macros are useful when you would like a single key to perform a series of actions. When you press _k_e_y in menu _m_e_n_u, Mutt-ng will behave as if you had + + The Mutt Next Generation E-Mail Client 30 + 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 27) 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 163). + 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 175). 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 - (eg. the system Muttngrc). Optionally you can specify a descriptive text after _s_e_q_u_e_n_c_e, which is shown in @@ -1353,7 +1484,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 ] @@ -1376,6 +1507,8 @@ +o error (error messages printed by Mutt-ng) + The Mutt Next Generation E-Mail Client 31 + +o header (match _r_e_g_e_x_p in the message header) +o hdrdefault (default color of the message header in the pager) @@ -1390,15 +1523,13 @@ +o normal - +o quoted (text matching _$_q_u_o_t_e___r_e_g_e_x_p (section 6.4.225 , page 134) in the + +o quoted (text matching _$_q_u_o_t_e___r_e_g_e_x_p (section 7.4.238 , page 146) 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 - +o signature +o status (mode lines used to display info about the mailbox or message) @@ -1431,8 +1562,11 @@ +o color_x - _f_o_r_e_g_r_o_u_n_d can optionally be prefixed with the keyword bright to make the fore- - ground color boldfaced (e.g., brightred). + _f_o_r_e_g_r_o_u_n_d can optionally be prefixed with the keyword bright to make the + + The Mutt Next Generation E-Mail Client 32 + + foreground color boldfaced (e.g., brightred). If your terminal supports it, the special keyword _d_e_f_a_u_l_t can be used as a transparent color. The value _b_r_i_g_h_t_d_e_f_a_u_l_t is also valid. If Mutt-ng is @@ -1451,8 +1585,6 @@ 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 - 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 the colors for your display (for example by changing the color associated with @@ -1479,11 +1611,14 @@ +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 ... ] Messages often have many header fields added by automatic processing systems, + + The Mutt Next Generation E-Mail Client 33 + or which may not seem useful to display on the screen. This command allows you to specify header fields which you don't normally want to see. @@ -1506,9 +1641,7 @@ unignore organization organisation x-mailer: x-newsreader: x-mailing-list: unignore posted-to: - The Mutt Next Generation E-Mail Client 31 - - _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 +1650,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 136).) + _$_r_e_p_l_y___t_o (section 7.4.246 , page 148).) 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 +1669,11 @@ 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 + The Mutt Next Generation E-Mail Client 34 + + _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 +1688,14 @@ 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 32 + set wrapmargin = 10 The code above makes the line break 10 columns before the right side of the terminal. @@ -1566,50 +1703,86 @@ 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 + + The Mutt Next Generation E-Mail Client 35 - 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: + differentiate 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 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 100) variable pro- + vides the mechanism to generate a DelSp=yes parameter on _o_u_t_g_o_i_n_g messages. + + The Mutt Next Generation E-Mail Client 36 + + 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 60). 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,7 +1791,7 @@ 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 95) + lowup-To header is controlled by the _$_f_o_l_l_o_w_u_p___t_o (section 7.4.72 , page 105) configuration variable. More precisely, Mutt-ng maintains lists of patterns for the addresses of known @@ -1647,7 +1820,9 @@ 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 + The Mutt Next Generation E-Mail Client 37 + + _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 +1831,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 ... ] @@ -1687,11 +1860,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 94) and _$_s_p_o_o_l_f_i_l_e (section - 6.4.295 , page 151)) should be executed before the mailboxes command. + 60) (such as ``='' and ``!''), any variable definition that affect these char- + acters (like _$_f_o_l_d_e_r (section 7.4.70 , page 104) and _$_s_p_o_o_l_f_i_l_e (section + 7.4.310 , page 163)) 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: @@ -1699,6 +1872,8 @@ unmy_hdr _f_i_e_l_d [ _f_i_e_l_d ... ] + The Mutt Next Generation E-Mail Client 38 + The ``my_hdr'' command allows you to create your own header fields which will be added to every message you send. @@ -1707,8 +1882,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 +1889,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 92) 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 102) 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. @@ -1727,7 +1900,7 @@ 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,55 +1912,55 @@ 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 This command is used to override the default filename used when saving mes- sages. _f_i_l_e_n_a_m_e will be used as the default filename if the message is _F_r_o_m_: + + The Mutt Next Generation E-Mail Client 39 + 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 57) 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 39) 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 136). Mutt-ng searches the initial list of message + (section 7.4.243 , page 147). 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 136) mailbox. + 7.4.243 , page 147) mailbox. - 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 57) 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 39) 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 38) 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 @@ -1795,6 +1968,8 @@ Usage: send2-hook [!]_p_a_t_t_e_r_n _c_o_m_m_a_n_d + The Mutt Next Generation E-Mail Client 40 + These commands can be used to execute arbitrary configuration commands based upon recipients of the message. _p_a_t_t_e_r_n is a regular expression matching the desired address. _c_o_m_m_a_n_d is executed when _r_e_g_e_x_p matches recipients of the @@ -1805,26 +1980,24 @@ 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 140) variable depending on the message's + _$_s_e_n_d_m_a_i_l (section 7.4.260 , page 151) 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 57) 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 84), _$_s_i_g_n_a_t_u_r_e (section 6.4.259 , page 142) and - _$_l_o_c_a_l_e (section 6.4.114 , page 108) variables in order to change the language + _t_i_o_n (section 7.4.18 , page 93), _$_s_i_g_n_a_t_u_r_e (section 7.4.272 , page 154) and + _$_l_o_c_a_l_e (section 7.4.120 , page 119) 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 @@ -1833,7 +2006,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,49 +2016,49 @@ 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 57) for information on the exact format of _p_a_t_t_e_r_n. Example: 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 + The Mutt Next Generation E-Mail Client 41 - Usage: crypt-hook _p_a_t_t_e_r_n _k_e_y_i_d + message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""' - When encrypting messages with PGP or OpenSSL, you may want to associate a + _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 - The Mutt Next Generation E-Mail Client 38 + Usage: crypt-hook _p_a_t_t_e_r_n _k_e_y_i_d - 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 + in the _m_a_c_r_o (section 3.8 , page 29) command. You may use it to automatically run a sequence of commands at startup, or when entering certain folders. - _3_._2_4 _E_x_e_c_u_t_i_n_g _f_u_n_c_t_i_o_n_s + _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 163). ``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 175). ``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 @@ -1897,6 +2070,8 @@ that you aren't interested in deleted. For this purpose, mutt-ng features a mechanism called ``scoring''. + The Mutt Next Generation E-Mail Client 42 + When you use scoring, every message has a base score of 0. You can then use the score command to define patterns and a positive or negative value associated with it. When a pattern matches a message, the message's score will be raised @@ -1905,8 +2080,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: @@ -1928,24 +2101,26 @@ 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 139), _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___r_e_a_d (section 6.4.245 , page 139), - _$_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 139) 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 139) 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 139) are set to -1, which means that in the default + tion 7.4.257 , page 150), _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___r_e_a_d (section 7.4.258 , page 151), + _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___d_e_l_e_t_e (section 7.4.256 , page 150) and. By default, + _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___r_e_a_d (section 7.4.258 , page 151) and _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___d_e_l_e_t_e + (section 7.4.256 , page 150) 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 + The Mutt Next Generation E-Mail Client 43 + + _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 +2130,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 105) variable. + the %H selector in the _$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.116 , page 115) variable. (Tip: try %?H?[%H] ? to display spam tags only when they are defined for a given message.) @@ -2002,6 +2174,8 @@ expression matches against for _s_e_a_r_c_h and _l_i_m_i_t functions. And it's what sort- ing by spam attribute will use as a sort key. + The Mutt Next Generation E-Mail Client 44 + That's a pretty complicated example, and most people's actual environments will have only one spam filter. The simpler your configuration, the more effective mutt can be, especially when it comes to sorting. @@ -2011,9 +2185,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 @@ -2039,7 +2210,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,12 +2220,15 @@ 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 80). 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 87). 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. _s_t_r_i_n_g variables consist of any number of printable characters. _s_t_r_i_n_g_s must + + The Mutt Next Generation E-Mail Client 45 + be enclosed in quotes if they contain spaces or tabs. You may also use the ``C'' escape sequences \\nn and \\tt for newline and tab, respectively. @@ -2065,8 +2239,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 @@ -2094,7 +2266,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 +2280,20 @@ 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 + The Mutt Next Generation E-Mail Client 46 + + _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 @@ -2144,7 +2315,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 +2324,9 @@ 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 + + The Mutt Next Generation E-Mail Client 47 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 +2334,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 @@ -2196,21 +2367,20 @@ 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 103), + test for the availability of _$_i_m_a_p___m_a_i_l___c_h_e_c_k (section 7.4.105 , page 113), 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 122) only if the pager menu is available, use: + (section 7.4.182 , page 133) only if the pager menu is available, use: + + The Mutt Next Generation E-Mail Client 48 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,12 +2391,18 @@ ifdef feature_slang 'source ~/.mutt-ng/setup-slang' ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' + _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 7.4 , page 87) 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 77) must be specified using regular expressions (regexp) in + tion 7.2 , page 83) 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. @@ -2241,6 +2417,9 @@ Note that the regular expression can be enclosed/delimited by either ' or ' which is useful if the regular expression includes a white-space character. + + The Mutt Next Generation E-Mail Client 49 + See _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 (section 3.2 , page 21) for more informa- tion on ' and ' delimiter processing. To match a literal ' or ' you must pref- ace it with \ (backslash). @@ -2254,8 +2433,6 @@ sign ``$'' are metacharacters that respectively match the empty string at the beginning and end of a line. - The Mutt Next Generation E-Mail Client 46 - A list of characters enclosed by ``['' and ``]'' matches any single character in that list; if the first character of the list is a caret ``^'' then it matches any character nnoott in the list. For example, the regular expression @@ -2297,6 +2474,9 @@ [:punct:] Punctuation characters (characters that are not letter, digits, + + The Mutt Next Generation E-Mail Client 50 + control characters, or space characters). [:space:] @@ -2310,9 +2490,6 @@ A character class is only valid in a regular expression inside the brackets of a character list. Note that the brackets in these class names are part of the - - The Mutt Next Generation E-Mail Client 47 - symbolic names, and must be included in addition to the brackets delimiting the bracket list. For example, [[[[::ddiiggiitt::]]]] is equivalent to [[00--99]]. @@ -2355,6 +2532,8 @@ {,m} The preceding item is matched at most _m times. + The Mutt Next Generation E-Mail Client 51 + {n,m} The preceding item is matched at least _n times, but no more than _m times. @@ -2367,9 +2546,6 @@ ing regular expression matches any string matching either subexpression. Repetition takes precedence over concatenation, which in turn takes precedence - - The Mutt Next Generation E-Mail Client 48 - over alternation. A whole subexpression may be enclosed in parentheses to override these precedence rules. @@ -2410,8 +2586,11 @@ Mutt-ng's pattern language provides a simple yet effective way to set up rules 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 + + The Mutt Next Generation E-Mail Client 52 + negated. For a complete listing of these patterns, please refer to table _P_a_t_- - _t_e_r_n_s (section 6.2 , page 77) in the Reference chapter. + _t_e_r_n_s (section 7.2 , page 83) in the Reference chapter. It must be noted that in this table, EXPR, USER, ID and SUBJECT are regular expressions. For ranges, the forms <[MAX], >>[MIN], [MIN]- and -[MAX] are also @@ -2423,8 +2602,6 @@ most simple possibility is to logically AND several patterns by stringing them together: - The Mutt Next Generation E-Mail Client 49 - ~s 'SPAM' ~U The pattern above matches all messages that contain ``SPAM'' in the subject and @@ -2461,6 +2638,9 @@ ~d 01/01/2005+1y ~d 18/10/2004-2w + + The Mutt Next Generation E-Mail Client 53 + ~d 28/12/2004*1d The first pattern matches all dates between January 1st, 2005 and January 1st @@ -2472,8 +2652,6 @@ date ranges between a fixed number of units and the current date. How this works can be seen in the following example: - The Mutt Next Generation E-Mail Client 50 - ~d >2w # messages older than two weeks ~d <3d # messages newer than 3 days ~d =1m # messages that are exactly one month old @@ -2498,7 +2676,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.305 , page 153) variable. For the hostname and version + _m_a_t (section 7.4.321 , page 165) 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: @@ -2510,6 +2688,8 @@ Mutt-ng 1.5.9i on mailhost: ... + The Mutt Next Generation E-Mail Client 54 + In the index, there're more useful information one could want to see: +o which mailbox is open @@ -2520,8 +2700,6 @@ To include the mailbox' name is as easy as: - The Mutt Next Generation E-Mail Client 51 - set status_format = "%v on %h: %B: ... When the currently opened mailbox is Inbox, this will be expanded to: @@ -2556,6 +2734,8 @@ This is achieved by the following syntax for those expandos which may be printed nonzero: + The Mutt Next Generation E-Mail Client 55 + %??&? Using this we can make mutt-ng to do the following: @@ -2565,8 +2745,6 @@ +o and make it print ``no new messages'' if there aren't any - The Mutt Next Generation E-Mail Client 52 - The corresponding configuration is: set status_format = "%v on %h: %B: %?n?%n new messages&no new messages? ... @@ -2603,6 +2781,9 @@ %>X Since the previous expando stops at the end of line, there must be + + The Mutt Next Generation E-Mail Client 56 + 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 ver- @@ -2612,8 +2793,6 @@ set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)" - The Mutt Next Generation E-Mail Client 53 - _4_._4 _U_s_i_n_g _T_a_g_s Sometimes it is desirable to perform an operation on a group of messages all at @@ -2622,17 +2801,17 @@ 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 77) for Mutt-ng's pattern matching + default. See _p_a_t_t_e_r_n_s (section 7.2 , page 83) 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 84) 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 93) 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 29) 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 @@ -2644,31 +2823,30 @@ 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 77) along + _e_x_p_r_e_s_s_i_o_n (section 4.1 , page 48) or _p_a_t_t_e_r_n (section 7.2 , page 83) 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 39) + + The Mutt Next Generation E-Mail Client 57 - +o _m_e_s_s_a_g_e_-_h_o_o_k (section 3.21 , page 37) + +o _m_e_s_s_a_g_e_-_h_o_o_k (section 3.22 , page 40) - +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 38) - +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 39) for specific details on each type of _h_o_o_k available. NNoottee:: if a hook changes configuration settings, these changes remain effective until the end of the current mutt session. As this is generally not desired, a default hook needs to be added before all other hooks to restore configuration - - The Mutt Next Generation E-Mail Client 54 - defaults. Here is an example with send-hook and the my_hdr directive: send-hook . 'unmy_hdr From:' @@ -2678,11 +2856,11 @@ 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 48) 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 77) 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 83) 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 @@ -2699,9 +2877,11 @@ 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 90) 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 90) that is in - effect at that time will be used. + 7.4.49 , page 100) 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 100) that is + in effect at that time will be used. + + The Mutt Next Generation E-Mail Client 58 _4_._6 _U_s_i_n_g _t_h_e _s_i_d_e_b_a_r @@ -2715,8 +2895,6 @@ If you want to specify the mailboxes you can do so with: - The Mutt Next Generation E-Mail Client 55 - set mbox='=INBOX' mailboxes INBOX \ MBOX1 \ @@ -2752,20 +2930,19 @@ You can then go up and down by pressing Ctrl-P and Ctrl-N, and switch on and off the sidebar simply by pressing 'B'. + The Mutt Next Generation E-Mail Client 59 + _4_._7 _E_x_t_e_r_n_a_l _A_d_d_r_e_s_s _Q_u_e_r_i_e_s 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 134) vari- + simple interface. Using the _$_q_u_e_r_y___c_o_m_m_a_n_d (section 7.4.234 , page 145) vari- able, you specify the wrapper command to use. For example: set query_command = "mutt_ldap_query.pl '%s'" The wrapper script should accept the query on the command-line. It should return a one line message, then each matching response on a single line, each - - The Mutt Next Generation E-Mail Client 56 - line containing a tab separated address then name then some other optional information. On error, or if there are no matching addresses, return a non- zero exit code and a one line error message. @@ -2798,12 +2975,14 @@ 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 111) + uses the default specified with the _$_m_b_o_x___t_y_p_e (section 7.4.132 , page 121) variable. mmbbooxx. This is the most widely used mailbox format for UNIX. All messages are stored in a single file. Each message has a line of the form: + The Mutt Next Generation E-Mail Client 60 + From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST to denote the start of a new message (this is often referred to as the @@ -2815,9 +2994,6 @@ MMHH. A radical departure from _m_b_o_x and _M_M_D_F, a mailbox consists of a directory and each message is stored in a separate file. The filename indicates the mes- sage number (however, this is may not correspond to the message number Mutt-ng - - The Mutt Next Generation E-Mail Client 57 - displays). Deleted messages are renamed with a comma (,) prepended to the file- name. NNoottee:: Mutt detects this type of mailbox by looking for either .mh_sequences or .xmhcache (needed to distinguish normal directories from MH @@ -2835,12 +3011,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.295 , page 151) (incoming) + +o ! -- refers to your _$_s_p_o_o_l_f_i_l_e (section 7.4.310 , page 163) (incoming) mailbox - +o > -- refers to your _$_m_b_o_x (section 6.4.124 , page 111) file + +o > -- refers to your _$_m_b_o_x (section 7.4.131 , page 121) file - +o < -- refers to your _$_r_e_c_o_r_d (section 6.4.230 , page 136) file + +o < -- refers to your _$_r_e_c_o_r_d (section 7.4.243 , page 147) file +o ^ -- refers to the current mailbox @@ -2848,29 +3024,29 @@ +o ~ -- refers to your home directory - +o = or + -- refers to your _$_f_o_l_d_e_r (section 6.4.64 , page 94) directory + +o = or + -- refers to your _$_f_o_l_d_e_r (section 7.4.70 , page 104) 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 38) 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 Mutt-ng has a few configuration options that make dealing with large amounts of + + The Mutt Next Generation E-Mail Client 61 + 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 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 105) variable, the escape + box. In the _$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.116 , page 115) variable, the escape ``%L'' will return the string ``To '' when ``list'' appears in the ``To'' - - The Mutt Next Generation E-Mail Client 58 - field, and ``Cc '' when it appears in the ``Cc'' field (otherwise it returns the name of the author). @@ -2884,7 +3060,7 @@ 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 95) option is set, mutt will + and if the _$_f_o_l_l_o_w_u_p___t_o (section 7.4.72 , page 105) 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 @@ -2894,7 +3070,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 100) configuration variable is set. Using list-reply + (section 7.4.94 , page 110) 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. @@ -2907,30 +3083,29 @@ 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 136) variable to help decide which address to use. If set to + 7.4.246 , page 148) 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 will be used when present. + The Mutt Next Generation E-Mail Client 62 + 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 105) variable's ``%y'' and ``%Y'' + _$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.116 , page 115) 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 + ``~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.289 , page 149) the mail- + Lastly, Mutt-ng has the ability to _s_o_r_t (section 7.4.304 , page 161) 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 - - The Mutt Next Generation E-Mail Client 59 - - graphically. If you've ever used a threaded news client, this is the same con- - cept. It makes dealing with large volume mailing lists easier because you can - easily delete uninteresting threads and quickly find topics of value. + like structure where a message and all of its replies are represented graphi- + cally. If you've ever used a threaded news client, this is the same concept. + It makes dealing with large volume mailing lists easier because you can easily + delete uninteresting threads and quickly find topics of value. _4_._1_1 _E_d_i_t_i_n_g _t_h_r_e_a_d_s @@ -2963,22 +3138,31 @@ RFC1894 defines a set of MIME content types for relaying information about the status of electronic mail messages. These can be thought of as ``return - receipts.'' 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 - should be returned. + receipts.'' - To support this, there are two variables. _$_d_s_n___n_o_t_i_f_y (section 6.4.51 , page - 91) is used to request receipts for different results (such as failed message, - message delivered, etc.). _$_d_s_n___r_e_t_u_r_n (section 6.4.52 , page 92) requests how - much of your message should be returned with the receipt (headers or full mes- - sage). Refer to the man page on sendmail for more details on DSN. + Users can make use of it in one of the following two ways: - _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 63 - If Mutt-ng was compiled with POP3 support (by running the _c_o_n_f_i_g_u_r_e script with + +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 + should be returned. - The Mutt Next Generation E-Mail Client 60 + +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 7.4.56 , page 101) 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 7.4.57 , page 102) 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_) + + 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. @@ -2993,7 +3177,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 131) variable, which defaults + by the _$_p_o_p___m_a_i_l___c_h_e_c_k (section 7.4.221 , page 142) 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 @@ -3003,13 +3187,15 @@ 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 130), fetch all your - new mail and place it in the local _s_p_o_o_l_f_i_l_e (section 6.4.295 , page 151). + It allows to connect to _p_o_p___h_o_s_t (section 7.4.219 , page 142), fetch all your + new mail and place it in the local _s_p_o_o_l_f_i_l_e (section 7.4.310 , page 163). 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- sider using a specialized program, such as fetchmail + The Mutt Next Generation E-Mail Client 64 + _4_._1_4 _I_M_A_P _S_u_p_p_o_r_t _(_O_P_T_I_O_N_A_L_) If Mutt-ng was compiled with IMAP support (by running the _c_o_n_f_i_g_u_r_e script with @@ -3030,12 +3216,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 _-_-_w_i_t_h_-_s_s_l flag), connections to IMAP servers can be encrypted. This - - The Mutt Next Generation E-Mail Client 61 - - naturally requires that the server supports SSL encrypted connections. To - access a folder with IMAP/SSL, you should use imaps://[user- + 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- name@]imapserver[:port]/path/to/folder as your folder path. Pine-compatible notation is also supported, i.e. {[user- @@ -3047,12 +3230,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 102) 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 113) + 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 103) and - _$_t_i_m_e_o_u_t (section 6.4.318 , page 158) variables. + want to carefully tune the _$_i_m_a_p___m_a_i_l___c_h_e_c_k (section 7.4.105 , page 113) and + _$_t_i_m_e_o_u_t (section 7.4.334 , page 170) 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 @@ -3068,6 +3251,8 @@ sages and subfolders. On Cyrus-like servers folders will often contain both messages and subfolders. + The Mutt Next Generation E-Mail Client 65 + +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 @@ -3088,9 +3273,6 @@ To use ANONYMOUS, simply make your username blank or "anonymous". SASL is a special super-authenticator, which selects among several protocols - - The Mutt Next Generation E-Mail Client 62 - (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 DIGEST-MD5 and possibly GSSAPI), your entire session will be encrypted and @@ -3103,15 +3285,15 @@ There are a few variables which control authentication: - +o _$_i_m_a_p___u_s_e_r (section 6.4.105 , page 104) - controls the username under + +o _$_i_m_a_p___u_s_e_r (section 7.4.111 , page 114) - 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 103) - a password which you may pre- + +o _$_i_m_a_p___p_a_s_s (section 7.4.106 , page 113) - 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 101) - 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 111) - 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). @@ -3122,9 +3304,12 @@ 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 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 6.4.156 , page 119) variable. + The Default newsserver can be obtained from the $NNTPSERVER environment + + The Mutt Next Generation E-Mail Client 66 + + 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 7.4.169 , page 130) 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. @@ -3133,8 +3318,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 + 41). 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, @@ -3143,8 +3328,6 @@ In mutt-ng this is as easy as - The Mutt Next Generation E-Mail Client 63 - score ~* =42 This tells mutt-ng to apply a score of 42 to all messages whose sender speci- @@ -3166,7 +3349,38 @@ from people who they have defined an alias for so that those 2 groups of messages are excluded from the strict rules. - _4_._1_6 _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_) + _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 67 + + 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 62) 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.341 , page 172). + + 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 7.4.299 , page 160) + variable pointing to your SMTP server. + + Authentication mechanisms are available via the _$_s_m_t_p___u_s_e_r (section 7.4.303 , + page 161) and _$_s_m_t_p___p_a_s_s (section 7.4.300 , page 160) 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 7.4.302 , page 161) 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. + 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 7.4.298 , + page 160) 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_) If you happen to have accounts on multiple IMAP and/or POP servers, you may find managing all the authentication settings inconvenient and error-prone. @@ -3180,21 +3394,20 @@ account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo' account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"' - _4_._1_7 _S_t_a_r_t _a _W_W_W _B_r_o_w_s_e_r _o_n _U_R_L_s _(_E_X_T_E_R_N_A_L_) + _4_._1_8 _S_t_a_r_t _a _W_W_W _B_r_o_w_s_e_r _o_n _U_R_L_s _(_E_X_T_E_R_N_A_L_) If a message contains URLs (_u_n_i_f_i_e_d _r_e_s_o_u_r_c_e _l_o_c_a_t_o_r = address in the WWW space like _h_t_t_p_:_/_/_w_w_w_._m_u_t_t_._o_r_g_/), it is efficient to get a menu with all the URLs and start a WWW browser on one of them. This functionality is provided by the - external urlview program which can be retrieved at - - The Mutt Next Generation E-Mail Client 64 - - ftp://ftp.mutt.org/mutt/contrib/ and the configuration commands: + external urlview program which can be retrieved at ftp://ftp.mutt.org/mutt/con- + trib/ and the configuration commands: macro index \cb |urlview\n macro pager \cb |urlview\n - _4_._1_8 _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_) + The Mutt Next Generation E-Mail Client 68 + + _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_- _u_r_e script with the _-_-_e_n_a_b_l_e_-_c_o_m_p_r_e_s_s_e_d flag), Mutt can open folders stored in @@ -3208,8 +3421,8 @@ 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.18.1 , page 64), _c_l_o_s_e_- - _h_o_o_k (section 4.18.2 , page 64) and _a_p_p_e_n_d_-_h_o_o_k (section 4.18.3 , page 65)) + There are three hooks defined (_o_p_e_n_-_h_o_o_k (section 4.19.1 , page 68), _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 69)) which define commands to uncompress and compress a folder and to append mes- sages to an existing compressed folder respectively. @@ -3220,27 +3433,24 @@ 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.18.3 , page 65), 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.18.2 , page 64) (or give + tion 4.19.3 , page 69), 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.18.3 , page 65) though you'll be able to append to the folder. + _h_o_o_k (section 4.19.3 , page 69) 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 138), so that the compressed file + unset _$_s_a_v_e___e_m_p_t_y (section 7.4.253 , page 149), so that the compressed file will be removed if you delete all of the messages. - _4_._1_8_._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 + _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 Usage: open-hook _r_e_g_e_x_p '_c_o_m_m_a_n_d' The _c_o_m_m_a_n_d is the command that can be used for opening the folders whose names - - The Mutt Next Generation E-Mail Client 65 - match _r_e_g_e_x_p. The _c_o_m_m_a_n_d string is the printf-like format string, and it should accept two @@ -3249,6 +3459,9 @@ %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 69 + 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 @@ -3260,17 +3473,17 @@ If the _c_o_m_m_a_n_d is empty, this operation is disabled for this file type. - _4_._1_8_._2 _W_r_i_t_e _a _c_o_m_p_r_e_s_s_e_d _m_a_i_l_b_o_x + _4_._1_9_._2 _W_r_i_t_e _a _c_o_m_p_r_e_s_s_e_d _m_a_i_l_b_o_x 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.18.1 , page 64) command after some changes were made to it. + 4.19.1 , page 68) command after some changes were made to it. 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.18.1 , page 64) command. Temporary folder in this case is the folder previ- - ously produced by the <_o_p_e_n_-_h_o_o_k (section 4.18.1 , page 64) command. + 4.19.1 , page 68) 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 68) 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. @@ -3282,19 +3495,16 @@ 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.18.2 , page 64) 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_8_._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 + _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 Usage: append-hook _r_e_g_e_x_p '_c_o_m_m_a_n_d' 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 - - The Mutt Next Generation E-Mail Client 66 - - _r_e_g_e_x_p. It has the same format as in the _o_p_e_n_-_h_o_o_k (section 4.18.1 , page 64) + _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 68) command. The temporary folder in this case contains the messages that are being appended. @@ -3303,23 +3513,25 @@ Example: + The Mutt Next Generation E-Mail Client 70 + append-hook \\.gz$ "gzip -c %t >> %f" - When _a_p_p_e_n_d_-_h_o_o_k (section 4.18.3 , page 65) is used, the folder is not opened, + When _a_p_p_e_n_d_-_h_o_o_k (section 4.19.3 , page 69) 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 111)) type is always + is. Thus the default (_$_m_b_o_x___t_y_p_e (section 7.4.132 , page 121)) 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.18.2 , - page 64) is called, and not _a_p_p_e_n_d_-_h_o_o_k (section 4.18.3 , page 65). _a_p_p_e_n_d_- - _h_o_o_k (section 4.18.3 , page 65) is only for appending to existing folders. + 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 69) is called, and not _a_p_p_e_n_d_-_h_o_o_k (section 4.19.3 , page 69). _a_p_p_e_n_d_- + _h_o_o_k (section 4.19.3 , page 69) 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.18.1 , page 64) and _c_l_o_s_e_-_h_o_o_k (section 4.18.2 , page 64)respectively) each + 4.19.1 , page 68) and _c_l_o_s_e_-_h_o_o_k (section 4.19.2 , page 69)respectively) each time you will add to it. - _4_._1_8_._4 _E_n_c_r_y_p_t_e_d _f_o_l_d_e_r_s + _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 you want to encrypt a folder with PGP, you may want to use the following hooks: @@ -3339,9 +3551,6 @@ Quite a bit of effort has been made to make Mutt-ng the premier text-mode MIME MUA. Every effort has been made to provide the functionality that the discern- ing MIME user requires, and the conformance to the standards wherever possible. - - The Mutt Next Generation E-Mail Client 67 - When configuring Mutt-ng for MIME, there are two extra types of configuration files which Mutt-ng uses. One is the mime.types file, which contains the map- ping of file extensions to IANA MIME types. The other is the mailcap file, @@ -3352,6 +3561,8 @@ 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 71 + _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 @@ -3394,9 +3605,6 @@ The compose menu is the menu you see before you send a message. It allows you to edit the recipient list, the subject, and other aspects of your message. It - - The Mutt Next Generation E-Mail Client 68 - also contains a list of the attachments of your message, including the main body. From this menu, you can print, copy, filter, pipe, edit, compose, review, and rename an attachment or a list of tagged attachments. You can also @@ -3408,6 +3616,8 @@ - 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 72 + 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 @@ -3447,9 +3657,6 @@ these if the appropriate entry is found in the mime.types file. It also recog- nises other major mime types, such as the chemical type that is widely used in the molecular modelling community to pass molecular data in various forms to - - The Mutt Next Generation E-Mail Client 69 - various molecular viewers. Non-recognised mime types should only be used if the recipient of the message is likely to be expecting such attachments. @@ -3460,6 +3667,9 @@ 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 73 + XMosaic, lynx and metamail. In order to handle various MIME types that Mutt-ng can not handle internally, @@ -3501,9 +3711,6 @@ body of the MIME message to a temporary file, and then call the view command with the %s replaced by the name of the temporary file. In both cases, Mutt-ng will turn over the terminal to the view program until the program quits, at - - The Mutt Next Generation E-Mail Client 70 - which time Mutt will remove the temporary file if it exists. So, in the simplest form, you can send a text/plain message to the external @@ -3515,6 +3722,8 @@ text/plain; more %s + The Mutt Next Generation E-Mail Client 74 + Perhaps you would like to use lynx to interactively view a text/html message: text/html; lynx %s @@ -3543,7 +3752,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 109) variable. + them, see the _m_a_i_l_c_a_p___s_a_n_i_t_i_z_e (section 7.4.123 , page 119) 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. @@ -3553,9 +3762,6 @@ double quotes. Mutt-ng does this for you, the right way, as should any other program which interprets mailcap. Don't put them into backtick expansions. Be highly careful with eval statements, and avoid them if possible at all. Trying - - The Mutt Next Generation E-Mail Client 71 - to fix broken behaviour with quotes introduces new leaks - there is no alterna- tive to correct quoting in the first place. @@ -3568,6 +3774,8 @@ 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 75 + _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 @@ -3592,11 +3800,11 @@ needsterminal Mutt-ng uses this flag when viewing attachments with _a_u_t_o_v_i_e_w (sec- - tion 5.4 , page 74), in order to decide whether it should honor - the setting of the _$_w_a_i_t___k_e_y (section 6.4.332 , page 161) variable + tion 5.4 , page 78), in order to decide whether it should honor + the setting of the _$_w_a_i_t___k_e_y (section 7.4.347 , page 173) 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.332 , page 161) and the exit + ng will use _$_w_a_i_t___k_e_y (section 7.4.347 , page 173) 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. @@ -3606,8 +3814,6 @@ of a specific MIME type. Mutt-ng supports this from the compose menu. - The Mutt Next Generation E-Mail Client 72 - composetyped= This flag specifies the command to use to create a new attachment of a specific MIME type. This command differs from the compose @@ -3623,6 +3829,9 @@ 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 76 + it to compose new attachments. Mutt-ng will default to the defined editor for text attachments. @@ -3660,9 +3869,6 @@ When searching for an entry in the mailcap file, Mutt-ng will search for the most useful entry for its purpose. For instance, if you are attempting to print an image/gif, and you have the following entries in your mailcap file, - - The Mutt Next Generation E-Mail Client 73 - Mutt-ng will search for an entry with the print command: image/*; xv %s @@ -3672,17 +3878,19 @@ 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 74) to denote + In addition, you can use this with _A_u_t_o_v_i_e_w (section 5.4 , page 78) 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 77 + 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 74), Mutt-ng will choose the third entry + For _A_u_t_o_v_i_e_w (section 5.4 , page 78), 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. @@ -3714,8 +3922,6 @@ Content-Type: text/plain; charset=iso-8859-1 - The Mutt Next Generation E-Mail Client 74 - then Mutt-ng will expand %{charset} to iso-8859-1. The default metamail mailcap file uses this feature to test the charset to spawn an xterm using the right charset to view the message. @@ -3731,6 +3937,8 @@ This mailcap file is fairly simple and standard: + The Mutt Next Generation E-Mail Client 78 + # I'm always running X :) video/*; xanim %s > /dev/null image/*; xv %s > /dev/null @@ -3740,8 +3948,6 @@ This mailcap file shows quite a number of examples: - The Mutt Next Generation E-Mail Client 75 - # 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 @@ -3781,8 +3987,11 @@ _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 view- - ing MIME attachments while in the pager. + viewer defined in the mailcap file, Mutt-ng has support for automatically + + The Mutt Next Generation E-Mail Client 79 + + viewing 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 @@ -3794,8 +4003,6 @@ For instance, if you set auto_view to: - The Mutt Next Generation E-Mail Client 76 - 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- @@ -3822,7 +4029,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 74), and use that. Failing that, Mutt-ng will look for any text + 5.4 , page 78), 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- @@ -3831,6 +4038,9 @@ _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 80 + 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 @@ -3842,24 +4052,142 @@ mime_lookup application/octet-stream application/X-Lotus-Manuscript In addition, the unmime_lookup command may be used to disable this feature for + any particular mime-type if it had been set, for example, in a global muttrc. - The Mutt Next Generation E-Mail Client 77 + _6_. _S_e_c_u_r_i_t_y _C_o_n_s_i_d_e_r_a_t_i_o_n_s - any particular mime-type if it had been set, for example, in a global muttrc. + 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.339 , page 171) 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.335 , page 170) + variable. + + The Mutt Next Generation E-Mail Client 81 + + _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 124) variable. Please make sure + that you really know how local parts of these Message-ID: headers are composed. + + _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 102) 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.323 , page 168) 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 - _6_. _R_e_f_e_r_e_n_c_e + +o turn on the _$_e_d_i_t___h_e_a_d_e_r_s (section 7.4.59 , page 102) variable by force + to let the user see all the headers (because they still may leak informa- + tion.) - _6_._1 _C_o_m_m_a_n_d _l_i_n_e _o_p_t_i_o_n_s + _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 + + 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 119) variable for + details.) + + These utilities may have a variety of security vulnerabilities, including + + The Mutt Next Generation E-Mail Client 82 + + overwriting 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 + + +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 119) 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 + The Mutt Next Generation E-Mail Client 83 + + -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 @@ -3872,6 +4200,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 @@ -3892,13 +4222,13 @@ mutt -s 'data set for run #2' professor@bigschool.edu < ~/run2.dat - The Mutt Next Generation E-Mail Client 78 - This command will send a message to ``professor@bigschool.edu'' with a subject 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 84 ~A all messages ~b EXPR messages which contain EXPR in the message body @@ -3946,136 +4276,210 @@ address (excluded are addresses matching against alternates or any alias) - The Mutt Next Generation E-Mail Client 79 - 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 + 48). 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 85 + *) 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.16 , page 62) _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 33) _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 33) [ * | _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 75) _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 79) _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 75) _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 79) _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.18.3 , page 65) _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 69) _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 74) _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 78) _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 74) _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 78) _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.18.2 , page 64) _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 30) _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 30) _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 41) _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 39) _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 - The Mutt Next Generation E-Mail Client 80 + +o _h_d_r___o_r_d_e_r (section 3.17 , page 38) _h_e_a_d_e_r [ _h_e_a_d_e_r ... ] - +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 _u_n_h_d_r___o_r_d_e_r (section 3.17 , page 38) _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 _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_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_g_n_o_r_e (section 3.10 , page 32) _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] - +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 ... ] + The Mutt Next Generation E-Mail Client 86 - +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 32) _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 29) _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 40) _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 75) _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 79) _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 75) _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 79) _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 30) _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 30) _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 37) _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 37) _f_i_e_l_d [ _f_i_e_l_d ... ] - +o _o_p_e_n_-_h_o_o_k (section 4.18.1 , page 64) _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 68) _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 44) _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 38) _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 41) _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 41) _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 39) _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 44) [no|inv]_v_a_r_i_a_b_l_e[=_v_a_l_u_e] [ _v_a_r_i_a_b_l_e ... ] - The Mutt Next Generation E-Mail Client 81 + +o _u_n_s_e_t (section 3.28 , page 44) _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.29 , page 45) _f_i_l_e_n_a_m_e + + +o _s_p_a_m (section 3.27 , page 42) _p_a_t_t_e_r_n _f_o_r_m_a_t + + +o _n_o_s_p_a_m (section 3.27 , page 42) _p_a_t_t_e_r_n + + The Mutt Next Generation E-Mail Client 87 + + +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.13 , page 36) _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] + + +o _t_o_g_g_l_e (section 3.28 , page 44) _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.30 , page 46) _h_o_o_k_-_t_y_p_e + + _7_._4 _C_o_n_f_i_g_u_r_a_t_i_o_n _v_a_r_i_a_b_l_e_s - +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 ... ] + 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: - +o _s_o_u_r_c_e (section 3.28 , page 42) _f_i_l_e_n_a_m_e + The Mutt Next Generation E-Mail Client 88 - +o _s_p_a_m (section 3.26 , page 39) _p_a_t_t_e_r_n _f_o_r_m_a_t + edit_hdrs edit_headers + forw_decode forward_decode + forw_format forward_format + forw_quote forward_quote + hdr_format index_format + indent_str indent_string + mime_fwd mime_forward + msg_format message_format + pgp_autosign crypt_autosign + pgp_autoencrypt crypt_autoencrypt + pgp_replyencrypt crypt_replyencrypt + pgp_replysign crypt_replysign + pgp_replysignencrypted crypt_replysignencrypted + pgp_verify_sig crypt_verify_sig + pgp_create_traditional pgp_autoinline + pgp_auto_traditional pgp_replyinline + forw_decrypt forward_decrypt + smime_sign_as smime_default_key + post_indent_str post_indent_string + print_cmd print_command + shorten_hierarchy sidebar_shorten_hierarchy + ask_followup_to nntp_ask_followup_to + ask_x_comment_to nntp_ask_x_comment_to + catchup_newsgroup nntp_catchup + followup_to_poster nntp_followup_to_poster + group_index_format nntp_group_index_format + inews nntp_inews + mime_subject nntp_mime_subject + news_cache_dir nntp_cache_dir + news_server nntp_host + newsrc nntp_newsrc + nntp_poll nntp_mail_check + pop_checkinterval pop_mail_check + post_moderated nntp_post_moderated + save_unsubscribed nntp_save_unsubscribed + show_new_news nntp_show_new_news + show_only_unread nntp_show_only_unread + x_comment_to nntp_x_comment_to + smtp_auth_username smtp_user + smtp_auth_password smtp_pass + + The contrib subdirectory contains a script named update-config.pl which eases + migration. + + A complete list of current variables follows. + + _7_._4_._1 _a_b_o_r_t___n_o_a_t_t_a_c_h - +o _n_o_s_p_a_m (section 3.26 , page 39) _p_a_t_t_e_r_n + Type: quadoption - +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 ... ] + Default: no - +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 ... ] + This variable specifies whether to abort sending if no attachment was made but - +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 ... ] + The Mutt Next Generation E-Mail Client 89 - +o _u_n_h_o_o_k (section 3.29 , page 42) _h_o_o_k_-_t_y_p_e + 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 92). 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. - _6_._4 _C_o_n_f_i_g_u_r_a_t_i_o_n _v_a_r_i_a_b_l_e_s + 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 92) are + intended to remind the user to attach files if the message's text references + them. - _6_._4_._1 _a_b_o_r_t___n_o_s_u_b_j_e_c_t + 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 92) variable. + + _7_._4_._2 _a_b_o_r_t___n_o_s_u_b_j_e_c_t Type: quadoption @@ -4085,17 +4489,26 @@ 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 Default: yes - If set to _y_e_s, composition will automatically abort after editing the message - 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. + If set to _y_e_s, composition will automatically abort after editing the message + 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. + + _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. - _6_._4_._3 _a_l_i_a_s___f_i_l_e + _7_._4_._5 _a_l_i_a_s___f_i_l_e Type: path @@ -4105,13 +4518,13 @@ 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 45)'' 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 - Type: string + The Mutt Next Generation E-Mail Client 90 - The Mutt Next Generation E-Mail Client 82 + Type: string Default: '%4n %2f %t %-10a %r' @@ -4133,7 +4546,7 @@ %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 @@ -4142,7 +4555,7 @@ 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 @@ -4155,7 +4568,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 @@ -4166,9 +4579,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. - The Mutt Next Generation E-Mail Client 83 + The Mutt Next Generation E-Mail Client 91 - _6_._4_._8 _a_s_c_i_i___c_h_a_r_s + _7_._4_._1_0 _a_s_c_i_i___c_h_a_r_s Type: boolean @@ -4177,7 +4590,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 @@ -4186,7 +4599,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 @@ -4195,7 +4608,7 @@ If _s_e_t, Mutt-ng will prompt you for carbon-copy (Cc) recipients before editing the body of an outgoing message. - _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 @@ -4212,9 +4625,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.308 , page 156) is unset. + is valid only if _$_s_t_r_i_c_t___m_i_m_e (section 7.4.324 , page 168) 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 @@ -4223,7 +4636,7 @@ This variable describes the format of the ``attachment'' menu. The following printf(3)-style sequences are understood: - The Mutt Next Generation E-Mail Client 84 + The Mutt Next Generation E-Mail Client 92 %C charset @@ -4273,18 +4686,31 @@ %|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 93 + + 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 88). + + This variable and _$_a_b_o_r_t___n_o_a_t_t_a_c_h (section 7.4.1 , page 88) 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 Default: '\n' - The Mutt Next Generation E-Mail Client 85 - 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 @@ -4292,11 +4718,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 83)'' 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 93)'' 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 @@ -4304,9 +4730,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 105)''. + on ``_$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.116 , page 115)''. - _6_._4_._1_6 _a_u_t_o___t_a_g + _7_._4_._1_9 _a_u_t_o___t_a_g Type: boolean @@ -4317,30 +4743,30 @@ ``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 92)'', 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 94 + + When _s_e_t along with ``_$_e_d_i_t___h_e_a_d_e_r_s (section 7.4.59 , page 102)'', 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 93)''. + Also see ``_$_f_a_s_t___r_e_p_l_y (section 7.4.66 , page 104)''. - _6_._4_._1_8 _b_e_e_p + _7_._4_._2_1 _b_e_e_p Type: boolean Default: yes - The Mutt Next Generation E-Mail Client 86 - 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 @@ -4348,9 +4774,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 84)'' variable. + tion 7.4.21 , page 94)'' variable. - _6_._4_._2_0 _b_o_u_n_c_e + _7_._4_._2_3 _b_o_u_n_c_e Type: quadoption @@ -4361,7 +4787,7 @@ _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 @@ -4370,7 +4796,7 @@ 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 @@ -4379,10 +4805,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 95 + 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 @@ -4392,9 +4821,6 @@ This variable specifies the file where the certificates you trust are saved. When an unknown certificate is encountered, you are asked if you accept it or - - The Mutt Next Generation E-Mail Client 87 - not. If you accept it, the certificate can also be saved in this file and fur- ther connections are automatically accepted. @@ -4404,7 +4830,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 @@ -4412,7 +4838,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 @@ -4426,7 +4852,7 @@ 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 @@ -4435,21 +4861,21 @@ 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 96 + + _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.305 , page 153)'', but has + string is similar to ``_$_s_t_a_t_u_s___f_o_r_m_a_t (section 7.4.321 , page 165)'', but has its own set of printf(3)-like sequences: %a total number of attachments - The Mutt Next Generation E-Mail Client 88 - %h local hostname @@ -4459,11 +4885,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.305 , page 153)'' - 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 86)''. + See the text describing the ``_$_s_t_a_t_u_s___f_o_r_m_a_t (section 7.4.321 , page 165)'' + 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 96)''. - _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 @@ -4471,7 +4897,7 @@ 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 @@ -4480,7 +4906,7 @@ When _s_e_t, Mutt-ng will prompt for confirmation when appending messages to an 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 @@ -4489,7 +4915,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 97 Type: number @@ -4499,29 +4927,27 @@ 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 Default: 'text/plain' - The Mutt Next Generation E-Mail Client 89 - 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 - 136)'', ``_$_s_a_v_e___n_a_m_e (section 6.4.241 , page 138)'', ``_$_f_o_r_c_e___n_a_m_e (section - 6.4.68 , page 96)'' 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.243 , page + 147)'', ``_$_s_a_v_e___n_a_m_e (section 7.4.254 , page 150)'', ``_$_f_o_r_c_e___n_a_m_e (section + 7.4.74 , page 106)'' 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 @@ -4531,11 +4957,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 146)'' is _s_e_t, then OpenSSL is used instead to create S/MIME + 7.4.290 , page 158)'' 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_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 @@ -4543,11 +4969,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 88)'', ``_$_c_r_y_p_t___r_e_p_l_y_e_n_c_r_y_p_t (section 6.4.38 , page 89)'', - ``_$_c_r_y_p_t___a_u_t_o_s_i_g_n (section 6.4.36 , page 88)'', ``_$_c_r_y_p_t___r_e_p_l_y_s_i_g_n (section - 6.4.39 , page 89)'' and ``_$_s_m_i_m_e___i_s___d_e_f_a_u_l_t (section 6.4.277 , page 146)''. + 7.4.37 , page 97)'', ``_$_c_r_y_p_t___r_e_p_l_y_e_n_c_r_y_p_t (section 7.4.41 , page 98)'', + ``_$_c_r_y_p_t___a_u_t_o_s_i_g_n (section 7.4.39 , page 97)'', ``_$_c_r_y_p_t___r_e_p_l_y_s_i_g_n (section + 7.4.42 , page 98)'' and ``_$_s_m_i_m_e___i_s___d_e_f_a_u_l_t (section 7.4.290 , page 158)''. + + The Mutt Next Generation E-Mail Client 98 - _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 @@ -4556,13 +4984,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 146)'' is _s_e_t, then OpenSSL is + ``_$_s_m_i_m_e___i_s___d_e_f_a_u_l_t (section 7.4.290 , page 158)'' 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 90 - - _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 @@ -4570,11 +4996,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 88)'', ``_$_c_r_y_p_t___r_e_p_l_y_e_n_c_r_y_p_t (section 6.4.38 , page 89)'', - ``_$_c_r_y_p_t___a_u_t_o_s_i_g_n (section 6.4.36 , page 88)'', ``_$_c_r_y_p_t___r_e_p_l_y_s_i_g_n (section - 6.4.39 , page 89)'' and ``_$_s_m_i_m_e___i_s___d_e_f_a_u_l_t (section 6.4.277 , page 146)''. + 7.4.37 , page 97)'', ``_$_c_r_y_p_t___r_e_p_l_y_e_n_c_r_y_p_t (section 7.4.41 , page 98)'', + ``_$_c_r_y_p_t___a_u_t_o_s_i_g_n (section 7.4.39 , page 97)'', ``_$_c_r_y_p_t___r_e_p_l_y_s_i_g_n (section + 7.4.42 , page 98)'' and ``_$_s_m_i_m_e___i_s___d_e_f_a_u_l_t (section 7.4.290 , page 158)''. - _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 @@ -4583,7 +5009,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 @@ -4594,7 +5020,7 @@ 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 @@ -4602,12 +5028,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 89)'', because it allows you to sign all messages which are + 7.4.41 , page 98)'', because it allows you to sign all messages which are + + The Mutt Next Generation E-Mail Client 99 + 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 89)'', 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 98)'', 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 @@ -4616,12 +5045,9 @@ If _s_e_t, Mutt-ng will include a time stamp in the lines surrounding PGP or S/MIME output, so spoofing such lines is more difficult. If you are using col- ors to mark these lines, and rely on these, you may _u_n_s_e_t this setting. - - The Mutt Next Generation E-Mail Client 91 - (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 @@ -4634,7 +5060,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 @@ -4644,23 +5070,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 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 105)''. This is passed to strftime(3) + ``_$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.116 , page 115)''. 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 108)''. If the first character in the string + ``_$_l_o_c_a_l_e (section 7.4.120 , page 119)''. 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 100 + + _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 @@ -4673,12 +5116,9 @@ hook is declared. The default value matches if the message is either from a user matching the regular expression given, or if it is from you (if the from address matches ``alternates'') and is to or cc'ed to a user matching the given - - The Mutt Next Generation E-Mail Client 92 - regular expression. - _6_._4_._4_6 _d_e_l_e_t_e + _7_._4_._5_0 _d_e_l_e_t_e Type: quadoption @@ -4689,7 +5129,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.330 , page 169) 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.330 , page 169) is _s_e_t) but not on incomming. + + The Mutt Next Generation E-Mail Client 101 + + _7_._4_._5_2 _d_e_l_e_t_e___u_n_t_a_g Type: boolean @@ -4699,7 +5155,7 @@ 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 @@ -4709,36 +5165,34 @@ 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 91), 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 101), 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. - The Mutt Next Generation E-Mail Client 93 - - _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 Default: '' - NNoottee:: you should not enable this unless you are using Sendmail 8.8.x or - greater. + NNoottee:: you should not enable this unless you are using Sendmail 8.8.x or greater + or in connection with the SMTP support via libESMTP. This variable sets the request for when notification is returned. The string consists of a comma separated list (no spaces!) of one or more of the follow- @@ -4746,16 +5200,18 @@ 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 102 + 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 Default: '' - NNoottee:: you should not enable this unless you are using Sendmail 8.8.x or - greater. + NNoottee:: you should not enable this unless you are using Sendmail 8.8.x or greater + or in connection with the SMTP support via libESMTP. This variable controls how much of your message is returned in DSN messages. It may be set to either _h_d_r_s to return just the message header, or _f_u_l_l to @@ -4763,7 +5219,7 @@ 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 @@ -4774,7 +5230,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 @@ -4783,9 +5239,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 102) option. - The Mutt Next Generation E-Mail Client 94 + _7_._4_._6_0 _e_d_i_t_o_r Type: path @@ -4795,7 +5252,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 103 + + 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 102) 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 102) had to be turned on by + force because _$_s_t_r_i_c_t___m_a_i_l_t_o (section 7.4.323 , page 168) 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 @@ -4806,7 +5280,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 @@ -5066,9 +5547,7 @@ Defaults to the contents of the environment variable $EMAIL. - _6_._4_._7_5 _g_e_c_o_s___m_a_s_k - - The Mutt Next Generation E-Mail Client 99 + _7_._4_._8_1 _g_e_c_o_s___m_a_s_k Type: regular expression @@ -5086,28 +5565,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 37)'' 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 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.333 , page - 161)'' setting applies. + are replying to into the edit buffer. The ``_$_w_e_e_d (section 7.4.348 , page + 173)'' 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 @@ -5115,17 +5594,18 @@ Availability: Header Cache - The _$_h_e_a_d_e_r___c_a_c_h_e (section 6.4.78 , page 98) variable points to the header - cache database. + The _$_h_e_a_d_e_r___c_a_c_h_e (section 7.4.84 , page 108) variable points to the header + + The Mutt Next Generation E-Mail Client 109 - If _$_h_e_a_d_e_r___c_a_c_h_e (section 6.4.78 , page 98) points to a directory it will con- - tain a header cache database per folder. If _$_h_e_a_d_e_r___c_a_c_h_e (section 6.4.78 , - page 98) 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. + cache database. - The Mutt Next Generation E-Mail Client 100 + If _$_h_e_a_d_e_r___c_a_c_h_e (section 7.4.84 , page 108) 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 + 7.4.84 , page 108) 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 @@ -5135,7 +5615,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 @@ -5150,18 +5630,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 - 6.4.89 , page 100)'' variable when adding the domain part to addresses. This + 7.4.95 , page 110)'' 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 @@ -5170,7 +5650,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 110 Type: boolean @@ -5179,9 +5661,7 @@ When _s_e_t, Mutt-ng will not show the presence of missing messages in the thread tree. - The Mutt Next Generation E-Mail Client 101 - - _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 @@ -5190,7 +5670,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 @@ -5198,19 +5678,19 @@ 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 99) is set, this option will have no effect. + _i_n_g (section 7.4.89 , page 109) 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 99) 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 109) 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 @@ -5219,7 +5699,7 @@ 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 @@ -5228,22 +5708,21 @@ 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 111 + + _7_._4_._9_5 _h_o_s_t_n_a_m_e Type: string Default: '' Specifies the hostname to use after the ``@'' in local e-mail addresses and - - The Mutt Next Generation E-Mail Client 102 - during generation of Message-Id: headers. 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 @@ -5257,7 +5736,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 @@ -5280,32 +5759,31 @@ 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___d_e_l_i_m___c_h_a_r_s + _7_._4_._9_8 _i_m_a_p___c_h_e_c_k___s_u_b_s_c_r_i_b_e_d - Type: string - - Default: '/.' + Type: boolean - Availability: IMAP + Default: no - 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 94) variable. + The Mutt Next Generation E-Mail Client 112 - The Mutt Next Generation E-Mail Client 103 + 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.15 , page 37)'' command. - _6_._4_._9_3 _i_m_a_p___f_o_r_c_e___s_s_l + _7_._4_._9_9 _i_m_a_p___d_e_l_i_m___c_h_a_r_s - Type: boolean + Type: string - Default: no + Default: '/.' - Availability: IMAP and SSL or IMAP and GNUTLS + Availability: IMAP - If this variable is _s_e_t, Mutt-ng will always use SSL when connecting to IMAP - servers. + 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 7.4.70 , page 104) 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 @@ -5320,7 +5798,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 @@ -5332,7 +5810,7 @@ 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 @@ -5344,16 +5822,16 @@ 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 113 + 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. - The Mutt Next Generation E-Mail Client 104 - 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 @@ -5365,7 +5843,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 @@ -5375,21 +5853,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 - 104).'' + This variable defaults to the value of ``_$_i_m_a_p___u_s_e_r (section 7.4.111 , page + 114).'' - _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 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 109)'' 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 119)'' 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 @@ -5400,13 +5878,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 114 + 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. - The Mutt Next Generation E-Mail Client 105 - - _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 @@ -5419,7 +5897,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 @@ -5432,7 +5910,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 @@ -5443,7 +5921,7 @@ 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 @@ -5456,11 +5934,11 @@ 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 115 - Type: string + _7_._4_._1_1_1 _i_m_a_p___u_s_e_r - The Mutt Next Generation E-Mail Client 106 + Type: string Default: '' @@ -5470,7 +5948,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 @@ -5481,7 +5959,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 @@ -5490,7 +5968,7 @@ 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 @@ -5499,7 +5977,7 @@ 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 @@ -5509,17 +5987,16 @@ 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 - Default: '%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s' - - This variable allows you to customize the message index display to your + The Mutt Next Generation E-Mail Client 116 - The Mutt Next Generation E-Mail Client 107 + Default: '%4C %Z %{%b %d} %-15.15L (%?l?%4l&%4c?) %s' - personal taste. + This variable allows you to customize the message index display to your per- + sonal taste. ``Format strings'' are similar to the strings used in the ``C'' function printf(3) to format output (see the man page for more detail). The following @@ -5570,11 +6047,11 @@ %g newsgroup name (if compiled with nntp support) + The Mutt Next Generation E-Mail Client 117 + %i message-id of the current message - The Mutt Next Generation E-Mail Client 108 - %l number of lines in the message (does not work with maildir, mh, and possibly IMAP folders) @@ -5610,8 +6087,8 @@ `to:' field (recipients) %T - the appropriate character from the _$_t_o___c_h_a_r_s (section 6.4.320 , - page 158) string + the appropriate character from the _$_t_o___c_h_a_r_s (section 7.4.336 , + page 171) string %u user (login) name of the author @@ -5626,13 +6103,12 @@ %y `x-label:' field, if present + The Mutt Next Generation E-Mail Client 118 + %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 - - The Mutt Next Generation E-Mail Client 109 - - preceding message's `x-label'. + (2) at the top of a thread, or (3) `x-label' is different from pre- + ceding message's `x-label'. %Z message status flags @@ -5662,9 +6138,9 @@ %|X pad to the end of the line with character 'X' - See also: ``_$_t_o___c_h_a_r_s (section 6.4.320 , page 158)''. + See also: ``_$_t_o___c_h_a_r_s (section 7.4.336 , page 171)''. - _6_._4_._1_1_1 _i_s_p_e_l_l + _7_._4_._1_1_7 _i_s_p_e_l_l Type: path @@ -5672,29 +6148,29 @@ 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 111)'' 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 121)'' 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 119 - _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 - The Mutt Next Generation E-Mail Client 110 - Default: no When _s_e_t, address replies to the mailing list the original message came from (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 @@ -5703,7 +6179,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 @@ -5713,9 +6189,9 @@ 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 103). + 7.4.105 , page 113). - _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 @@ -5724,7 +6200,7 @@ This variable specifies which files to consult when attempting to display MIME 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 @@ -5736,21 +6212,21 @@ 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 120 Type: boolean Default: yes - The Mutt Next Generation E-Mail Client 111 - Availability: Header Cache Check for Maildir unaware programs other than Mutt-ng having modified maildir 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 @@ -5764,7 +6240,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 @@ -5777,7 +6253,7 @@ up with an 'O' next to them in the ``index'' menu, indicating that they are old. - _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 @@ -5785,21 +6261,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 143)'' variable. + ``_$_s_m_a_r_t___w_r_a_p (section 7.4.276 , page 155)'' 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 121 + operator ``!''. Only files whose names match this mask will be shown. The match is always case-sensitive. - The Mutt Next Generation E-Mail Client 112 + _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. - _6_._4_._1_2_3 _m_a_x___l_i_n_e___l_e_n_g_t_h + _7_._4_._1_3_0 _m_a_x___l_i_n_e___l_e_n_g_t_h Type: number @@ -5808,18 +6296,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.335 , page 161). + (section 7.4.350 , page 174). - _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.295 , page 151)'' folder will be appended. + 7.4.310 , page 163)'' 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 @@ -5828,17 +6316,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 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 - 121)''.) + scrolling through menus. (Similar to ``_$_p_a_g_e_r___c_o_n_t_e_x_t (section 7.4.180 , page + 133)''.) - _6_._4_._1_2_7 _m_e_n_u___m_o_v_e___o_f_f + The Mutt Next Generation E-Mail Client 122 + + _7_._4_._1_3_4 _m_e_n_u___m_o_v_e___o_f_f Type: boolean @@ -5848,20 +6338,18 @@ 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 Default: no - The Mutt Next Generation E-Mail Client 113 - When _s_e_t, menus will be scrolled up or down one line when you attempt to move across a screen boundary. If _u_n_s_e_t, the screen is cleared and the next or pre- 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 @@ -5869,9 +6357,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 105)''. + section on ``_$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.116 , page 115)''. - _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 @@ -5884,7 +6372,7 @@ 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 @@ -5893,7 +6381,9 @@ 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 123 + + _7_._4_._1_3_9 _m_h___p_u_r_g_e Type: boolean @@ -5903,7 +6393,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 @@ -5911,9 +6401,7 @@ The name of the MH sequence used for flagged messages. - The Mutt Next Generation E-Mail Client 114 - - _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 @@ -5921,7 +6409,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 @@ -5929,7 +6417,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 @@ -5942,20 +6430,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 96)'' and ``_$_m_i_m_e___f_o_r_- - _w_a_r_d___d_e_c_o_d_e (section 6.4.137 , page 113)''. + Also see ``_$_f_o_r_w_a_r_d___d_e_c_o_d_e (section 7.4.75 , page 106)'' and ``_$_m_i_m_e___f_o_r_- + _w_a_r_d___d_e_c_o_d_e (section 7.4.144 , page 123)''. - _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 124 + 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 113)'' is _s_e_t. Other- - wise ``_$_f_o_r_w_a_r_d___d_e_c_o_d_e (section 6.4.69 , page 96)'' is used instead. + a message while ``_$_m_i_m_e___f_o_r_w_a_r_d (section 7.4.143 , page 123)'' is _s_e_t. Other- + wise ``_$_f_o_r_w_a_r_d___d_e_c_o_d_e (section 7.4.75 , page 106)'' 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 @@ -5965,9 +6455,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 - - The Mutt Next Generation E-Mail Client 115 + _7_._4_._1_4_6 _m_i_x___e_n_t_r_y___f_o_r_m_a_t Type: string @@ -5990,7 +6478,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 @@ -6002,17 +6490,19 @@ used with various sets of parameters to gather the list of known remailers, and to finally send a message through the mixmaster chain. - _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 125 + 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 111)'' 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 121)'' 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 @@ -6023,8 +6513,6 @@ generated. The '%' character marks that certain data will be added to the string, similar to printf(3). The following characters are allowed: - The Mutt Next Generation E-Mail Client 116 - %d the current day of month @@ -6062,6 +6550,8 @@ %X the current UNIX timestamp (hexadecimal) + The Mutt Next Generation E-Mail Client 126 + %Y the current year (Y2K compliant) @@ -6071,7 +6561,62 @@ 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. - _6_._4_._1_4_3 _n_a_r_r_o_w___t_r_e_e + _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___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_. + + _7_._4_._1_5_3 _m_u_t_t_n_g___r_e_v_i_s_i_o_n + + Type: system property + + Value: 462 + + _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_. + + _7_._4_._1_5_4 _m_u_t_t_n_g___s_y_s_c_o_n_f_d_i_r + + Type: system property + + Value: /opt/freebsd4/mutt-ng/etc + + _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 Mutt Next Generation E-Mail Client 127 + + _7_._4_._1_5_5 _m_u_t_t_n_g___v_e_r_s_i_o_n + + Type: system property + + Value: devel + + _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_6 _n_a_r_r_o_w___t_r_e_e Type: boolean @@ -6080,9 +6625,7 @@ This variable, when _s_e_t, makes the thread tree narrower, allowing deeper threads to fit on the screen. - The Mutt Next Generation E-Mail Client 117 - - _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_5_7 _n_n_t_p___a_s_k___f_o_l_l_o_w_u_p___t_o Type: boolean @@ -6093,7 +6636,7 @@ 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 + _7_._4_._1_5_8 _n_n_t_p___a_s_k___x___c_o_m_m_e_n_t___t_o Type: boolean @@ -6104,7 +6647,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_5_9 _n_n_t_p___c_a_c_h_e___d_i_r Type: path @@ -6119,7 +6662,9 @@ 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 + The Mutt Next Generation E-Mail Client 128 + + _7_._4_._1_6_0 _n_n_t_p___c_a_t_c_h_u_p Type: quadoption @@ -6130,24 +6675,22 @@ 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_1 _n_n_t_p___c_o_n_t_e_x_t Type: number Default: 1000 - The Mutt Next Generation E-Mail Client 118 - 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 116)) and how + caching is enabled, see _$_n_n_t_p___c_a_c_h_e___d_i_r (section 7.4.159 , page 127)) 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 116), 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.161 , + page 128), all older ones will be removed/not shown in the index. - _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 + _7_._4_._1_6_2 _n_n_t_p___f_o_l_l_o_w_u_p___t_o___p_o_s_t_e_r Type: quadoption @@ -6159,7 +6702,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_3 _n_n_t_p___g_r_o_u_p___i_n_d_e_x___f_o_r_m_a_t Type: string @@ -6168,8 +6711,10 @@ 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 105)'', but has its own set of printf(3)-like sequences: + personal taste. This string is similar to ``_i_n_d_e_x___f_o_r_m_a_t (section 7.4.116 , + page 115)'', but has its own set of printf(3)-like sequences: + + The Mutt Next Generation E-Mail Client 129 %C current newsgroup number %d description of newsgroup (retrieved from server) @@ -6181,7 +6726,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_4 _n_n_t_p___h_o_s_t Type: string @@ -6191,8 +6736,6 @@ This variable specifies the name (or address) of the NNTP server to be used. - The Mutt Next Generation E-Mail Client 119 - It defaults to the value specified via the environment variable $NNTPSERVER or contained in the file /etc/nntpserver. @@ -6205,7 +6748,7 @@ security risk since the superuser of your machine may read it regardless of the file's permissions. - _6_._4_._1_5_2 _n_n_t_p___i_n_e_w_s + _7_._4_._1_6_5 _n_n_t_p___i_n_e_w_s Type: path @@ -6221,10 +6764,12 @@ 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_6 _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 130 + Default: yes Availability: NNTP @@ -6232,7 +6777,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_6_7 _n_n_t_p___m_a_i_l___c_h_e_c_k Type: number @@ -6244,9 +6789,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.). - The Mutt Next Generation E-Mail Client 120 - - _6_._4_._1_5_5 _n_n_t_p___m_i_m_e___s_u_b_j_e_c_t + _7_._4_._1_6_8 _n_n_t_p___m_i_m_e___s_u_b_j_e_c_t Type: boolean @@ -6259,7 +6802,7 @@ 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_6_9 _n_n_t_p___n_e_w_s_r_c Type: path @@ -6275,10 +6818,12 @@ %s newsserver name - _6_._4_._1_5_7 _n_n_t_p___p_a_s_s + _7_._4_._1_7_0 _n_n_t_p___p_a_s_s Type: string + The Mutt Next Generation E-Mail Client 131 + Default: '' Availability: NNTP @@ -6288,7 +6833,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_1 _n_n_t_p___p_o_s_t___m_o_d_e_r_a_t_e_d Type: quadoption @@ -6299,12 +6844,10 @@ If set to _y_e_s, Mutt-ng will post articles to newsgroup that have not permis- sions to post (e.g. moderated). - The Mutt Next Generation E-Mail Client 121 - 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_2 _n_n_t_p___r_e_c_o_n_n_e_c_t Type: quadoption @@ -6315,7 +6858,7 @@ 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_3 _n_n_t_p___s_a_v_e___u_n_s_u_b_s_c_r_i_b_e_d Type: boolean @@ -6326,7 +6869,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_4 _n_n_t_p___s_h_o_w___n_e_w___n_e_w_s Type: boolean @@ -6335,11 +6878,14 @@ Availability: NNTP If _s_e_t, the newsserver will be asked for new newsgroups on entering the + + The Mutt Next Generation E-Mail Client 132 + 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_5 _n_n_t_p___s_h_o_w___o_n_l_y___u_n_r_e_a_d Type: boolean @@ -6350,20 +6896,18 @@ 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_6 _n_n_t_p___u_s_e_r Type: string Default: '' - The Mutt Next Generation E-Mail Client 122 - Availability: NNTP 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_7_7 _n_n_t_p___x___c_o_m_m_e_n_t___t_o Type: boolean @@ -6374,7 +6918,7 @@ 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_7_8 _o_p_e_r_a_t_i_n_g___s_y_s_t_e_m Type: string @@ -6386,12 +6930,14 @@ 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_7_9 _p_a_g_e_r Type: path Default: 'builtin' + The Mutt Next Generation E-Mail Client 133 + 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. @@ -6401,7 +6947,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_0 _p_a_g_e_r___c_o_n_t_e_x_t Type: number @@ -6412,9 +6958,7 @@ will display the line after the last one on the screen at the top of the next page (0 lines of context). - The Mutt Next Generation E-Mail Client 123 - - _6_._4_._1_6_8 _p_a_g_e_r___f_o_r_m_a_t + _7_._4_._1_8_1 _p_a_g_e_r___f_o_r_m_a_t Type: string @@ -6422,10 +6966,10 @@ 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 105)'' + sequences are listed in the ``_$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.116 , page 115)'' section. - _6_._4_._1_6_9 _p_a_g_e_r___i_n_d_e_x___l_i_n_e_s + _7_._4_._1_8_2 _p_a_g_e_r___i_n_d_e_x___l_i_n_e_s Type: number @@ -6442,16 +6986,18 @@ 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_3 _p_a_g_e_r___s_t_o_p Type: boolean Default: no + The Mutt Next Generation E-Mail Client 134 + 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_4 _p_g_p___a_u_t_o___d_e_c_o_d_e Type: boolean @@ -6464,12 +7010,10 @@ 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_5 _p_g_p___a_u_t_o_i_n_l_i_n_e Type: boolean - The Mutt Next Generation E-Mail Client 124 - Default: no This option controls whether Mutt-ng generates old-style inline (traditional) @@ -6479,12 +7023,12 @@ 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 126)''. + ``_$_p_g_p___m_i_m_e___a_u_t_o (section 7.4.201 , page 138)''. 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_6 _p_g_p___c_h_e_c_k___e_x_i_t Type: boolean @@ -6493,7 +7037,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_8_7 _p_g_p___c_l_e_a_r_s_i_g_n___c_o_m_m_a_n_d Type: string @@ -6503,7 +7047,9 @@ Note that the use of this format is ssttrroonnggllyy ddeepprreeccaatteedd. (PGP only) - _6_._4_._1_7_5 _p_g_p___d_e_c_o_d_e___c_o_m_m_a_n_d + The Mutt Next Generation E-Mail Client 135 + + _7_._4_._1_8_8 _p_g_p___d_e_c_o_d_e___c_o_m_m_a_n_d Type: string @@ -6525,10 +7071,8 @@ Expands to the name of a file containing the signature part of a multipart/signed attachment when verifying it. - The Mutt Next Generation E-Mail Client 125 - %a - The value of _$_p_g_p___s_i_g_n___a_s (section 6.4.192 , page 127). + The value of _$_p_g_p___s_i_g_n___a_s (section 7.4.205 , page 139). %r One or more key IDs. @@ -6538,7 +7082,7 @@ 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 + _7_._4_._1_8_9 _p_g_p___d_e_c_r_y_p_t___c_o_m_m_a_n_d Type: string @@ -6546,7 +7090,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_0 _p_g_p___e_n_c_r_y_p_t___o_n_l_y___c_o_m_m_a_n_d Type: string @@ -6554,23 +7098,25 @@ 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_1 _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 136 + 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_2 _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 - 105)'', 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 + 115)'', but has its own set of printf(3)-like sequences: %n number @@ -6581,8 +7127,6 @@ %u user id - The Mutt Next Generation E-Mail Client 126 - %a algorithm @@ -6603,7 +7147,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_3 _p_g_p___e_x_p_o_r_t___c_o_m_m_a_n_d Type: string @@ -6612,39 +7156,39 @@ 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_4 _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 137 + 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_5 _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 129) + verified if the output from _$_p_g_p___v_e_r_i_f_y___c_o_m_m_a_n_d (section 7.4.211 , page 140) 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_6 _p_g_p___i_g_n_o_r_e___s_u_b_k_e_y_s Type: boolean Default: yes - The Mutt Next Generation E-Mail Client 127 - Setting this variable will cause Mutt-ng to ignore OpenPGP subkeys. Instead, 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_._1_9_7 _p_g_p___i_m_p_o_r_t___c_o_m_m_a_n_d Type: string @@ -6653,7 +7197,7 @@ This command is used to import a key from a message into the user's public key 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_._1_9_8 _p_g_p___l_i_s_t___p_u_b_r_i_n_g___c_o_m_m_a_n_d Type: string @@ -6665,19 +7209,22 @@ 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_._1_9_9 _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 138 + 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_0 _p_g_p___l_o_n_g___i_d_s Type: boolean @@ -6686,7 +7233,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_1 _p_g_p___m_i_m_e___a_u_t_o Type: quadoption @@ -6694,15 +7241,12 @@ This option controls whether Mutt-ng will prompt you for automatically sending a (signed/encrypted) message using PGP/MIME when inline (traditional) fails - - The Mutt Next Generation E-Mail Client 128 - (for any reason). 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_2 _p_g_p___r_e_p_l_y_i_n_l_i_n_e Type: boolean @@ -6718,17 +7262,19 @@ 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 126)''. + ``_$_p_g_p___m_i_m_e___a_u_t_o (section 7.4.201 , page 138)''. 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_3 _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 139 + If _s_e_t, signed and encrypted messages will consist of nested multipart/signed and multipart/encrypted body parts. @@ -6736,7 +7282,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_4 _p_g_p___s_h_o_w___u_n_u_s_a_b_l_e Type: boolean @@ -6746,19 +7292,17 @@ 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_5 _p_g_p___s_i_g_n___a_s Type: string Default: '' - The Mutt Next Generation E-Mail Client 129 - If you have more than one key pair, this option allows you to specify which of 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_6 _p_g_p___s_i_g_n___c_o_m_m_a_n_d Type: string @@ -6767,7 +7311,7 @@ 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_0_7 _p_g_p___s_o_r_t___k_e_y_s Type: sort order @@ -6785,13 +7329,15 @@ date sort by key creation date + The Mutt Next Generation E-Mail Client 140 + 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_0_8 _p_g_p___s_t_r_i_c_t___e_n_c Type: boolean @@ -6802,18 +7348,16 @@ 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_0_9 _p_g_p___t_i_m_e_o_u_t Type: number Default: 300 - The Mutt Next Generation E-Mail Client 130 - 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_0 _p_g_p___u_s_e___g_p_g___a_g_e_n_t Type: boolean @@ -6821,7 +7365,7 @@ 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 + _7_._4_._2_1_1 _p_g_p___v_e_r_i_f_y___c_o_m_m_a_n_d Type: string @@ -6829,7 +7373,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_2 _p_g_p___v_e_r_i_f_y___k_e_y___c_o_m_m_a_n_d Type: string @@ -6838,17 +7382,19 @@ 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_3 _p_i_p_e___d_e_c_o_d_e Type: boolean + The Mutt Next Generation E-Mail Client 141 + 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_4 _p_i_p_e___s_e_p Type: string @@ -6857,23 +7403,20 @@ 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_5 _p_i_p_e___s_p_l_i_t Type: boolean Default: no Used in connection with the _p_i_p_e_-_m_e_s_s_a_g_e command and the ``tag- prefix'' or - - The Mutt Next Generation E-Mail Client 131 - ``tag-prefix-cond'' operators. If this variable is _u_n_s_e_t, when piping a list 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 129)'' separator is added after each message. + (section 7.4.214 , page 140)'' 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_6 _p_o_p___a_u_t_h___t_r_y___a_l_l Type: boolean @@ -6886,7 +7429,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_1_7 _p_o_p___a_u_t_h_e_n_t_i_c_a_t_o_r_s Type: string @@ -6899,13 +7442,15 @@ tication methods are either ``user'', ``apop'' or any SASL mechanism, eg ``digest-md5'', ``gssapi'' or ``cram-md5''. + The Mutt Next Generation E-Mail Client 142 + 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_1_8 _p_o_p___d_e_l_e_t_e Type: quadoption @@ -6917,12 +7462,10 @@ 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_1_9 _p_o_p___h_o_s_t Type: string - The Mutt Next Generation E-Mail Client 132 - Default: '' Availability: POP @@ -6935,7 +7478,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_0_7 _p_o_p___l_a_s_t + _7_._4_._2_2_0 _p_o_p___l_a_s_t Type: boolean @@ -6947,7 +7490,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_1 _p_o_p___m_a_i_l___c_h_e_c_k Type: number @@ -6955,9 +7498,11 @@ Availability: POP + The Mutt Next Generation E-Mail Client 143 + 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_2 _p_o_p___p_a_s_s Type: string @@ -6971,20 +7516,18 @@ 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_3 _p_o_p___r_e_c_o_n_n_e_c_t Type: quadoption Default: ask-yes - The Mutt Next Generation E-Mail Client 133 - Availability: POP 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_4 _p_o_p___u_s_e_r Type: string @@ -6996,49 +7539,48 @@ 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_5 _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 84)'' variable, Mutt-ng + Similar to the ``_$_a_t_t_r_i_b_u_t_i_o_n (section 7.4.18 , page 93)'' 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_6 _p_o_s_t_p_o_n_e Type: quadoption Default: ask-yes + The Mutt Next Generation E-Mail Client 144 + Controls whether or not messages are saved in the ``_$_p_o_s_t_p_o_n_e_d (section - 6.4.214 , page 132)'' mailbox when you elect not to send immediately. + 7.4.227 , page 143)'' 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_2_7 _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 132) + Mutt-ng allows you to indefinitely ``_p_o_s_t_p_o_n_e (section 7.4.226 , page 143) 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 132)'' variable. + ``_$_p_o_s_t_p_o_n_e (section 7.4.226 , page 143)'' variable. - _6_._4_._2_1_5 _p_r_e_c_o_n_n_e_c_t + _7_._4_._2_2_8 _p_r_e_c_o_n_n_e_c_t Type: string Default: '' - If _s_e_t, a shell command to be executed if Mutt-ng fails to establish a - - The Mutt Next Generation E-Mail Client 134 - - connection to the server. This is useful for setting up secure connections, - e.g. with ssh(1). If the command returns a nonzero status, Mutt-ng gives up - opening the server. Example: + If _s_e_t, a shell command to be executed if Mutt-ng fails to establish a connec- + tion to the server. This is useful for setting up secure connections, e.g. with + ssh(1). If the command returns a nonzero status, Mutt-ng gives up opening the + server. Example: preconnect='ssh -f -q -L 1234:mailhost.net:143 mailhost.net sleep 20 < /dev/null > /dev/null' @@ -7048,7 +7590,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_._2_1_6 _p_r_i_n_t + _7_._4_._2_2_9 _p_r_i_n_t Type: quadoption @@ -7057,7 +7599,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_0 _p_r_i_n_t___c_o_m_m_a_n_d Type: path @@ -7065,49 +7607,49 @@ 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_1 _p_r_i_n_t___d_e_c_o_d_e Type: boolean + The Mutt Next Generation E-Mail Client 145 + 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 133). 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.230 , page 144). 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_2 _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 133) is executed + command specified by _$_p_r_i_n_t___c_o_m_m_a_n_d (section 7.4.230 , page 144) 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 133) is executed + command specified by _$_p_r_i_n_t___c_o_m_m_a_n_d (section 7.4.230 , page 144) is executed only once, and all the messages are concatenated, with a form feed as the mes- sage separator. - The Mutt Next Generation E-Mail Client 135 - 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_3 _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 121)'', setting this + If you use an _e_x_t_e_r_n_a_l ``_$_p_a_g_e_r (section 7.4.179 , page 132)'', setting this variable will cause Mutt-ng to prompt you for a command when the pager exits 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_4 _q_u_e_r_y___c_o_m_m_a_n_d Type: path @@ -7115,30 +7657,33 @@ 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 58)'' for more information. - _6_._4_._2_2_2 _q_u_i_t + _7_._4_._2_3_5 _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 146 + 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_6 _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 105)''. + tion 7.4.115 , page 115)''. - _6_._4_._2_2_4 _q_u_o_t_e___q_u_o_t_e_d + _7_._4_._2_3_7 _q_u_o_t_e___q_u_o_t_e_d Type: boolean @@ -7146,11 +7691,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 105)''. - - The Mutt Next Generation E-Mail Client 136 + by ``_i_n_d_e_n_t___s_t_r_i_n_g (section 7.4.115 , page 115)''. - _6_._4_._2_2_5 _q_u_o_t_e___r_e_g_e_x_p + _7_._4_._2_3_8 _q_u_o_t_e___r_e_g_e_x_p Type: regular expression @@ -7163,7 +7706,7 @@ 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_3_9 _r_e_a_d___i_n_c Type: number @@ -7177,9 +7720,11 @@ 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.337 , page 162)'' variable. + Also see the ``_$_w_r_i_t_e___i_n_c (section 7.4.352 , page 174)'' variable. - _6_._4_._2_2_7 _r_e_a_d___o_n_l_y + _7_._4_._2_4_0 _r_e_a_d___o_n_l_y + + The Mutt Next Generation E-Mail Client 147 Type: boolean @@ -7187,7 +7732,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_1 _r_e_a_l_n_a_m_e Type: string @@ -7199,22 +7744,20 @@ 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 97) variable. + _$_f_r_o_m (section 7.4.80 , page 107) variable. - _6_._4_._2_2_9 _r_e_c_a_l_l + _7_._4_._2_4_2 _r_e_c_a_l_l Type: quadoption - The Mutt Next Generation E-Mail Client 137 - 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 132)''. + message. Also see ``_$_p_o_s_t_p_o_n_e_d (section 7.4.227 , page 143)''. 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_3 _r_e_c_o_r_d Type: path @@ -7222,25 +7765,28 @@ 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 37)'' 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_6_) is overridden by the - ``_$_f_o_r_c_e___n_a_m_e (section 6.4.68 , page 96)'' and ``_$_s_a_v_e___n_a_m_e (section - 6.4.241 , page 138)'' 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_3 _, _p_a_g_e _1_4_7_) is overridden by the + ``_$_f_o_r_c_e___n_a_m_e (section 7.4.74 , page 106)'' and ``_$_s_a_v_e___n_a_m_e (section + 7.4.254 , page 150)'' 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_4 _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 reply- - ing. The default value corresponds to the English ``Re:'' and the German + A regular expression used to recognize reply messages when threading and + + The Mutt Next Generation E-Mail Client 148 + + replying. 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_5 _r_e_p_l_y___s_e_l_f Type: boolean @@ -7250,7 +7796,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_6 _r_e_p_l_y___t_o Type: quadoption @@ -7261,13 +7807,10 @@ use the address in the ``From:'' header field instead. This option is useful for reading a mailing list that sets the ``Reply-To:'' - - The Mutt Next Generation E-Mail Client 138 - 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_4_7 _r_e_s_o_l_v_e Type: boolean @@ -7277,7 +7820,7 @@ 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_4_8 _r_e_v_e_r_s_e___a_l_i_a_s Type: boolean @@ -7294,10 +7837,13 @@ From: abd30425@somewhere.net It would be displayed in the index menu as ``Joe User'' instead of + + The Mutt Next Generation E-Mail Client 149 + ``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_4_9 _r_e_v_e_r_s_e___n_a_m_e Type: boolean @@ -7311,22 +7857,19 @@ 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_0 _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 , - - The Mutt Next Generation E-Mail Client 139 - - page 137) 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.249 , + page 148) 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 135) variable. + (section 7.4.241 , page 146) 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_1 _r_f_c_2_0_4_7___p_a_r_a_m_e_t_e_r_s Type: boolean @@ -7348,48 +7891,48 @@ _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_2 _s_a_v_e___a_d_d_r_e_s_s Type: boolean + The Mutt Next Generation E-Mail Client 150 + 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 138)'' or - ``_$_f_o_r_c_e___n_a_m_e (section 6.4.68 , page 96)'' 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.254 , page 150)'' or + ``_$_f_o_r_c_e___n_a_m_e (section 7.4.74 , page 106)'' 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_3 _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.295 , page 151)'' which is + closed (the exception is ``_$_s_p_o_o_l_f_i_l_e (section 7.4.310 , page 163)'' 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_4 _s_a_v_e___n_a_m_e Type: boolean - The Mutt Next Generation E-Mail Client 140 - Default: no 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 94)'' 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 104)'' 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 136)'' mailbox. + the message is saved to the ``_$_r_e_c_o_r_d (section 7.4.243 , page 147)'' mailbox. - Also see the ``_$_f_o_r_c_e___n_a_m_e (section 6.4.68 , page 96)'' variable. + Also see the ``_$_f_o_r_c_e___n_a_m_e (section 7.4.74 , page 106)'' variable. - _6_._4_._2_4_2 _s_c_o_r_e + _7_._4_._2_5_5 _s_c_o_r_e Type: boolean @@ -7397,9 +7940,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 139)'' variable and friends are used. + _o_l_d___d_e_l_e_t_e (section 7.4.256 , page 150)'' 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_6 _s_c_o_r_e___t_h_r_e_s_h_o_l_d___d_e_l_e_t_e Type: number @@ -7408,9 +7951,12 @@ 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 151 + 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_5_7 _s_c_o_r_e___t_h_r_e_s_h_o_l_d___f_l_a_g Type: number @@ -7419,7 +7965,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_5_8 _s_c_o_r_e___t_h_r_e_s_h_o_l_d___r_e_a_d Type: number @@ -7430,9 +7976,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 - - The Mutt Next Generation E-Mail Client 141 + _7_._4_._2_5_9 _s_e_n_d___c_h_a_r_s_e_t Type: string @@ -7440,12 +7984,12 @@ 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 86)'' is not iso-8859-1 and recipients may not under- + (section 7.4.27 , page 95)'' 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 instead of or after iso-8859-1. - _6_._4_._2_4_7 _s_e_n_d_m_a_i_l + _7_._4_._2_6_0 _s_e_n_d_m_a_i_l Type: path @@ -7455,16 +7999,18 @@ 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_1 _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 140)'' 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.260 , + page 151)'' process to finish before giving up and putting delivery in the background. + The Mutt Next Generation E-Mail Client 152 + Mutt-ng interprets the value of this variable as follows: >0 @@ -7480,7 +8026,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_2 _s_h_e_l_l Type: path @@ -7489,19 +8035,17 @@ Command to use when spawning a subshell. By default, the user's login shell from /etc/passwd is used. - The Mutt Next Generation E-Mail Client 142 - - _6_._4_._2_5_0 _s_i_d_e_b_a_r___b_o_u_n_d_a_r_y + _7_._4_._2_6_3 _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 141) is _s_e_t, this variable specifies the characters at which to + 7.4.267 , page 153) is _s_e_t, this variable specifies the characters at which to 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_4 _s_i_d_e_b_a_r___d_e_l_i_m Type: string @@ -7510,7 +8054,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_5 _s_i_d_e_b_a_r___n_e_w_m_a_i_l___o_n_l_y Type: boolean @@ -7518,58 +8062,72 @@ 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_6 _s_i_d_e_b_a_r___n_u_m_b_e_r___f_o_r_m_a_t Type: string - Default: '%c%?n?(%n)?%?f?[%f]?' + The Mutt Next Generation E-Mail Client 153 + + Default: '%m%?n?(%n)?%?f?[%f]?' This variable controls how message counts are printed when the sidebar is enabled. If this variable is _e_m_p_t_y (_a_n_d _o_n_l_y _i_f), no numbers will be printed _a_n_d mutt-ng won't frequently count mail (which may be a great speedup esp. with mbox-style mailboxes.) - The following printf(3)-like sequences are supported: + The following printf(3)-like sequences are supported all of which may be + printed non-zero: - %c - Total number of messages. + %d + Number of deleted messages. 1) - %f + %F Number of flagged messages. + %m + Total number of messages. + + %M + Total number of messages shown, i.e. not hidden by a limit. 1) + %n Number of new messages. - The %f and %n expandos may optionally be printed non-zero. + %t + Number of tagged messages. 1) - _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 + 1) These expandos only have a non-zero value for the current mailbox and will + always be zero otherwise. - Type: boolean + _7_._4_._2_6_7 _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 143 + Type: boolean Default: no 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 142)'' is set to a too low value). For example, if the news- + 7.4.269 , page 153)'' 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 140) variable. + _b_a_r___b_o_u_n_d_a_r_y (section 7.4.263 , page 152) variable. - _6_._4_._2_5_5 _s_i_d_e_b_a_r___v_i_s_i_b_l_e + _7_._4_._2_6_8 _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 154 + with the ``mailboxes'' command). - _6_._4_._2_5_6 _s_i_d_e_b_a_r___w_i_d_t_h + _7_._4_._2_6_9 _s_i_d_e_b_a_r___w_i_d_t_h Type: number @@ -7577,14 +8135,14 @@ The width of the sidebar. - _6_._4_._2_5_7 _s_i_g___d_a_s_h_e_s + _7_._4_._2_7_0 _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 142)''. It is ssttrroonnggllyy recommended + your ``_$_s_i_g_n_a_t_u_r_e (section 7.4.272 , page 154)''. 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. @@ -7592,7 +8150,7 @@ 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_1 _s_i_g___o_n___t_o_p Type: boolean @@ -7603,9 +8161,7 @@ know what you are doing, and are prepared to take some heat from netiquette guardians. - The Mutt Next Generation E-Mail Client 144 - - _6_._4_._2_5_9 _s_i_g_n_a_t_u_r_e + _7_._4_._2_7_2 _s_i_g_n_a_t_u_r_e Type: path @@ -7615,7 +8171,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_3 _s_i_g_n_o_f_f___s_t_r_i_n_g Type: string @@ -7624,11 +8180,13 @@ 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 155 + 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_4 _s_i_m_p_l_e___s_e_a_r_c_h Type: string @@ -7636,7 +8194,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 77)'' for more information on search patterns. + ``_p_a_t_t_e_r_n_s (section 7.2 , page 83)'' 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 @@ -7644,7 +8202,7 @@ ~f joe | ~s joe - _6_._4_._2_6_2 _s_l_e_e_p___t_i_m_e + _7_._4_._2_7_5 _s_l_e_e_p___t_i_m_e Type: number @@ -7655,30 +8213,30 @@ 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 + _7_._4_._2_7_6 _s_m_a_r_t___w_r_a_p Type: boolean - The Mutt Next Generation E-Mail Client 145 - Default: yes 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 110)'' variable. + simply wrapped at the screen edge. Also see the ``_$_m_a_r_k_e_r_s (section 7.4.127 , + page 120)'' variable. - _6_._4_._2_6_4 _s_m_i_l_e_y_s + _7_._4_._2_7_7 _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 134)'', most notably smileys in the + ``_$_q_u_o_t_e___r_e_g_e_x_p (section 7.4.238 , page 146)'', 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 + _7_._4_._2_7_8 _s_m_i_m_e___a_s_k___c_e_r_t___l_a_b_e_l + + The Mutt Next Generation E-Mail Client 156 Type: boolean @@ -7688,7 +8246,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_7_9 _s_m_i_m_e___c_a___l_o_c_a_t_i_o_n Type: path @@ -7697,7 +8255,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_0 _s_m_i_m_e___c_e_r_t_i_f_i_c_a_t_e_s Type: path @@ -7710,14 +8268,12 @@ 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 + _7_._4_._2_8_1 _s_m_i_m_e___d_e_c_r_y_p_t___c_o_m_m_a_n_d Type: string Default: '' - The Mutt Next Generation E-Mail Client 146 - This format string specifies a command which is used to decrypt application/x- pkcs7-mime attachments. @@ -7732,8 +8288,10 @@ 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 145) + The key-pair specified with _$_s_m_i_m_e___d_e_f_a_u_l_t___k_e_y (section 7.4.283 , + page 157) + + The Mutt Next Generation E-Mail Client 157 %c One or more certificate IDs. @@ -7743,15 +8301,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 144) 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 144)' or - '-CAfile _$_s_m_i_m_e___c_a___l_o_c_a_t_i_o_n (section 6.4.266 , page 144)'. + 7.4.279 , page 156) 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.279 , page 156)' or + '-CAfile _$_s_m_i_m_e___c_a___l_o_c_a_t_i_o_n (section 7.4.279 , page 156)'. 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_2 _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 @@ -7762,7 +8320,7 @@ 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_3 _s_m_i_m_e___d_e_f_a_u_l_t___k_e_y Type: string @@ -7771,9 +8329,7 @@ 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) - The Mutt Next Generation E-Mail Client 147 - - _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_4 _s_m_i_m_e___e_n_c_r_y_p_t___c_o_m_m_a_n_d Type: string @@ -7781,7 +8337,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_5 _s_m_i_m_e___e_n_c_r_y_p_t___w_i_t_h Type: string @@ -7792,7 +8348,9 @@ If _u_n_s_e_t ``_3_d_e_s'' (TripleDES) is used. (S/MIME only) - _6_._4_._2_7_3 _s_m_i_m_e___g_e_t___c_e_r_t___c_o_m_m_a_n_d + The Mutt Next Generation E-Mail Client 158 + + _7_._4_._2_8_6 _s_m_i_m_e___g_e_t___c_e_r_t___c_o_m_m_a_n_d Type: string @@ -7801,7 +8359,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_8_7 _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 @@ -7811,7 +8369,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_8_8 _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 @@ -7821,17 +8379,15 @@ 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 + _7_._4_._2_8_9 _s_m_i_m_e___i_m_p_o_r_t___c_e_r_t___c_o_m_m_a_n_d Type: string Default: '' - The Mutt Next Generation E-Mail Client 148 - 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_0 _s_m_i_m_e___i_s___d_e_f_a_u_l_t Type: boolean @@ -7844,9 +8400,11 @@ 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 89).) (S/MIME only) + tion 7.4.40 , page 98).) (S/MIME only) - _6_._4_._2_7_8 _s_m_i_m_e___k_e_y_s + _7_._4_._2_9_1 _s_m_i_m_e___k_e_y_s + + The Mutt Next Generation E-Mail Client 159 Type: path @@ -7859,7 +8417,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_2 _s_m_i_m_e___p_k_7_o_u_t___c_o_m_m_a_n_d Type: string @@ -7868,7 +8426,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_3 _s_m_i_m_e___s_i_g_n___c_o_m_m_a_n_d Type: string @@ -7877,19 +8435,17 @@ 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 + _7_._4_._2_9_4 _s_m_i_m_e___s_i_g_n___o_p_a_q_u_e___c_o_m_m_a_n_d Type: string Default: '' - The Mutt Next Generation E-Mail Client 149 - This command is used to created S/MIME signatures of type application/x- 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_5 _s_m_i_m_e___t_i_m_e_o_u_t Type: number @@ -7898,16 +8454,18 @@ 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_6 _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 160 + 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_._2_9_7 _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 @@ -7916,7 +8474,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___a_u_t_h___p_a_s_s_w_o_r_d + _7_._4_._2_9_8 _s_m_t_p___e_n_v_e_l_o_p_e Type: string @@ -7924,14 +8482,14 @@ Availability: SMTP - Defines the password to use with SMTP AUTH. If ``_$_s_m_t_p___a_u_t_h___u_s_e_r_n_a_m_e (section - 6.4.286 , page 148)'' is set, but this variable is not, you will be prompted - for a password when sending. + If this variable is non-empty, it'll be used as the envelope sender. If it's + empty (the default), the value of the regular From: header will be used. - 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. + This may be necessary as some providers don't allow for arbitrary values as the + 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___a_u_t_h___u_s_e_r_n_a_m_e + _7_._4_._2_9_9 _s_m_t_p___h_o_s_t Type: string @@ -7939,12 +8497,11 @@ Availability: SMTP - The Mutt Next Generation E-Mail Client 150 - - Defines the username to use with SMTP AUTH. Setting this variable will cause - Mutt-ng to attempt to use SMTP AUTH when sending. + 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 7.4.260 , page 151)'', and any associated variables. - _6_._4_._2_8_7 _s_m_t_p___h_o_s_t + _7_._4_._3_0_0 _s_m_t_p___p_a_s_s Type: string @@ -7952,11 +8509,16 @@ Availability: SMTP - 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 140)'', and any associated variables. + Defines the password to use with SMTP AUTH. If ``_$_s_m_t_p___u_s_e_r (section + 7.4.303 , page 161)'' 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 161 - _6_._4_._2_8_8 _s_m_t_p___p_o_r_t + _7_._4_._3_0_1 _s_m_t_p___p_o_r_t Type: number @@ -7970,7 +8532,32 @@ 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_o_r_t + _7_._4_._3_0_2 _s_m_t_p___u_s_e___t_l_s + + Type: string + + Default: '' + + Availability: SMTP (and SSL) + + Defines wether to use STARTTLS. If this option is set to ``_r_e_q_u_i_r_e_d'' and the + server does not support STARTTLS or there is an error in the TLS Handshake, the + connection will fail. Setting this to ``_e_n_a_b_l_e_d'' will try to start TLS and + continue without TLS in case of an error. Muttng still needs to have SSL sup- + port enabled in order to use it. + + _7_._4_._3_0_3 _s_m_t_p___u_s_e_r + + Type: string + + Default: '' + + Availability: SMTP + + Defines the username to use with SMTP AUTH. Setting this variable will cause + Mutt-ng to attempt to use SMTP AUTH when sending. + + _7_._4_._3_0_4 _s_o_r_t Type: sort order @@ -7978,6 +8565,8 @@ Specifies how to sort messages in the _i_n_d_e_x menu. Valid values are: + The Mutt Next Generation E-Mail Client 162 + date or date-sent date-received from @@ -7992,9 +8581,7 @@ You may optionally use the ``reverse-'' prefix to specify reverse sorting order (example: set sort=reverse-date-sent). - The Mutt Next Generation E-Mail Client 151 - - _6_._4_._2_9_0 _s_o_r_t___a_l_i_a_s + _7_._4_._3_0_5 _s_o_r_t___a_l_i_a_s Type: sort order @@ -8007,7 +8594,7 @@ alias (sort alphabetically by alias name) unsorted (leave in order specified in .muttrc) - _6_._4_._2_9_1 _s_o_r_t___a_u_x + _7_._4_._3_0_6 _s_o_r_t___a_u_x Type: sort order @@ -8015,7 +8602,7 @@ 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.289 , page 149)'' can, + This can be set to any value that ``_$_s_o_r_t (section 7.4.304 , page 161)'' 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 @@ -8026,11 +8613,13 @@ 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.289 , page 149)'' order _$_s_o_r_t___a_u_x - (section 6.4.291 , page 150) is reversed again (which is not the right thing + NNoottee:: For reversed ``_$_s_o_r_t (section 7.4.304 , page 161)'' order _$_s_o_r_t___a_u_x + (section 7.4.306 , page 162) is reversed again (which is not the right thing to do, but kept to not break any existing configuration setting). - _6_._4_._2_9_2 _s_o_r_t___b_r_o_w_s_e_r + The Mutt Next Generation E-Mail Client 163 + + _7_._4_._3_0_7 _s_o_r_t___b_r_o_w_s_e_r Type: sort order @@ -8044,51 +8633,52 @@ size unsorted - The Mutt Next Generation E-Mail Client 152 - You may optionally use the ``reverse-'' prefix to specify reverse sorting order (example: set sort_browser=reverse-date). - _6_._4_._2_9_3 _s_o_r_t___r_e + _7_._4_._3_0_8 _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.309 , page 156)'' _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.293 , - page 150) _s_e_t, Mutt-ng will only attach a message as the child of another mes- + (section 7.4.325 , page 168)'' _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.308 , + page 163) _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 136)''. With - _$_s_o_r_t___r_e (section 6.4.293 , page 150) _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.244 , page 147)''. With + _$_s_o_r_t___r_e (section 7.4.308 , page 163) _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 136)'' parts of both messages are identical. + 7.4.244 , page 147)'' parts of both messages are identical. - _6_._4_._2_9_4 _s_p_a_m___s_e_p_a_r_a_t_o_r + _7_._4_._3_0_9 _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.294 , page 151)'' controls what happens when + ``_s_p_a_m___s_e_p_a_r_a_t_o_r (section 7.4.309 , page 163)'' 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.294 , - page 151)'' 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.309 , + page 163)'' as a separator. - _6_._4_._2_9_5 _s_p_o_o_l_f_i_l_e + _7_._4_._3_1_0 _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 164 + 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_6 _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_1 _s_s_l___c_a___c_e_r_t_i_f_i_c_a_t_e_s___f_i_l_e Type: path @@ -8100,9 +8690,7 @@ Example: set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt - The Mutt Next Generation E-Mail Client 153 - - _6_._4_._2_9_7 _s_s_l___c_l_i_e_n_t___c_e_r_t + _7_._4_._3_1_2 _s_s_l___c_l_i_e_n_t___c_e_r_t Type: path @@ -8112,7 +8700,19 @@ The file containing a client certificate and its associated private key. - _6_._4_._2_9_8 _s_s_l___m_i_n___d_h___p_r_i_m_e___b_i_t_s + _7_._4_._3_1_3 _s_s_l___f_o_r_c_e___t_l_s + + Type: boolean + + Default: no + + 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 + abort the connection anyway. This option supersedes ``_$_s_s_l___s_t_a_r_t_t_l_s (section + 7.4.315 , page 164)''. + + _7_._4_._3_1_4 _s_s_l___m_i_n___d_h___p_r_i_m_e___b_i_t_s Type: number @@ -8124,10 +8724,12 @@ any Diffie-Hellman key exchange. A value of 0 will use the default from the GNUTLS library. - _6_._4_._2_9_9 _s_s_l___s_t_a_r_t_t_l_s + _7_._4_._3_1_5 _s_s_l___s_t_a_r_t_t_l_s Type: quadoption + The Mutt Next Generation E-Mail Client 165 + Default: yes Availability: SSL or GNUTLS @@ -8136,7 +8738,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_0 _s_s_l___u_s_e___s_s_l_v_2 + _7_._4_._3_1_6 _s_s_l___u_s_e___s_s_l_v_2 Type: boolean @@ -8147,7 +8749,7 @@ This variables specifies whether to attempt to use SSLv2 in the SSL authentica- tion process. - _6_._4_._3_0_1 _s_s_l___u_s_e___s_s_l_v_3 + _7_._4_._3_1_7 _s_s_l___u_s_e___s_s_l_v_3 Type: boolean @@ -8155,13 +8757,10 @@ Availability: SSL or GNUTLS - This variables specifies whether to attempt to use SSLv3 in the SSL - - The Mutt Next Generation E-Mail Client 154 - - authentication process. + This variables specifies whether to attempt to use SSLv3 in the SSL authentica- + tion process. - _6_._4_._3_0_2 _s_s_l___u_s_e___t_l_s_v_1 + _7_._4_._3_1_8 _s_s_l___u_s_e___t_l_s_v_1 Type: boolean @@ -8172,7 +8771,7 @@ This variables specifies whether to attempt to use TLSv1 in the SSL authentica- tion process. - _6_._4_._3_0_3 _s_s_l___u_s_e_s_y_s_t_e_m_c_e_r_t_s + _7_._4_._3_1_9 _s_s_l___u_s_e_s_y_s_t_e_m_c_e_r_t_s Type: boolean @@ -8183,14 +8782,16 @@ 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_4 _s_t_a_t_u_s___c_h_a_r_s + _7_._4_._3_2_0 _s_t_a_t_u_s___c_h_a_r_s + + The Mutt Next Generation E-Mail Client 166 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.305 , page 153)''. The first character is used when the mailbox is + tion 7.4.321 , page 165)''. 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 @@ -8199,7 +8800,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_5 _s_t_a_t_u_s___f_o_r_m_a_t + _7_._4_._3_2_1 _s_t_a_t_u_s___f_o_r_m_a_t Type: string @@ -8208,14 +8809,12 @@ %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 105)'', but has + string is similar to ``_$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.116 , page 115)'', but has its own set of printf(3)-like sequences: %b number of mailboxes with new mail * - The Mutt Next Generation E-Mail Client 155 - %B the short pathname of the current mailbox @@ -8241,6 +8840,8 @@ %m the number of messages in the mailbox * + The Mutt Next Generation E-Mail Client 167 + %M the number of messages shown (i.e., which match the current limit) * @@ -8259,20 +8860,18 @@ %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.304 , page 153) + to _$_s_t_a_t_u_s___c_h_a_r_s (section 7.4.320 , page 165) %s - current sorting mode (_$_s_o_r_t (section 6.4.289 , page 149)) + current sorting mode (_$_s_o_r_t (section 7.4.304 , page 161)) %S - current aux sorting method (_$_s_o_r_t___a_u_x (section 6.4.291 , page - 150)) + current aux sorting method (_$_s_o_r_t___a_u_x (section 7.4.306 , page + 162)) %t number of tagged messages * - The Mutt Next Generation E-Mail Client 156 - %u number of unread messages * @@ -8298,6 +8897,8 @@ %??? + The Mutt Next Generation E-Mail Client 168 + 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 @@ -8324,18 +8925,16 @@ 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_6 _s_t_a_t_u_s___o_n___t_o_p + _7_._4_._3_2_2 _s_t_a_t_u_s___o_n___t_o_p Type: boolean - The Mutt Next Generation E-Mail Client 157 - Default: no 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_0_7 _s_t_r_i_c_t___m_a_i_l_t_o + _7_._4_._3_2_3 _s_t_r_i_c_t___m_a_i_l_t_o Type: boolean @@ -8343,65 +8942,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 92)'' is unset. + ``_$_e_d_i_t___h_e_a_d_e_r_s (section 7.4.59 , page 102)'' 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 92)'' is set to. + ``_$_e_d_i_t___h_e_a_d_e_r_s (section 7.4.59 , page 102)'' is set to. - _6_._4_._3_0_8 _s_t_r_i_c_t___m_i_m_e + _7_._4_._3_2_4 _s_t_r_i_c_t___m_i_m_e Type: boolean + The Mutt Next Generation E-Mail Client 169 + 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 82). + Express). See also _$_a_s_s_u_m_e_d___c_h_a_r_s_e_t (section 7.4.13 , page 91). 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_0_9 _s_t_r_i_c_t___t_h_r_e_a_d_s + _7_._4_._3_2_5 _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.289 , page 149)'' by mes- + ences:'' header fields when you ``_$_s_o_r_t (section 7.4.304 , page 161)'' 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_0 _s_t_r_i_p___w_a_s + _7_._4_._3_2_6 _s_t_r_i_p___w_a_s Type: boolean Default: no - The Mutt Next Generation E-Mail Client 158 - 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.311 , page 156) when replying. This is + matches _$_s_t_r_i_p___w_a_s___r_e_g_e_x (section 7.4.327 , page 169) when replying. This is useful to properly react on subject changes and reduce ``subject noise.'' (esp. in Usenet) - _6_._4_._3_1_1 _s_t_r_i_p___w_a_s___r_e_g_e_x + _7_._4_._3_2_7 _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.310 , page 156) is _s_e_t, mutt-ng + When non-empty and _$_s_t_r_i_p___w_a_s (section 7.4.326 , page 169) 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_2 _s_t_u_f_f___q_u_o_t_e_d + _7_._4_._3_2_8 _s_t_u_f_f___q_u_o_t_e_d Type: boolean @@ -8410,7 +9009,9 @@ 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. - _6_._4_._3_1_3 _s_u_s_p_e_n_d + The Mutt Next Generation E-Mail Client 170 + + _7_._4_._3_2_9 _s_u_s_p_e_n_d Type: boolean @@ -8420,7 +9021,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_4 _t_e_x_t___f_l_o_w_e_d + _7_._4_._3_3_0 _t_e_x_t___f_l_o_w_e_d Type: boolean @@ -8431,23 +9032,21 @@ 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 105) is ignored when this + Note that _$_i_n_d_e_n_t___s_t_r_i_n_g (section 7.4.115 , page 115) is ignored when this option is set. - _6_._4_._3_1_5 _t_h_o_r_o_u_g_h___s_e_a_r_c_h + _7_._4_._3_3_1 _t_h_o_r_o_u_g_h___s_e_a_r_c_h Type: boolean Default: no - The Mutt Next Generation E-Mail Client 159 - Affects the ~b and ~h search operations described in section ``_p_a_t_t_e_r_n_s (sec- - tion 6.2 , page 77)'' above. If _s_e_t, the headers and attachments of messages + tion 7.2 , page 83)'' 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_6 _t_h_r_e_a_d___r_e_c_e_i_v_e_d + _7_._4_._3_3_2 _t_h_r_e_a_d___r_e_c_e_i_v_e_d Type: boolean @@ -8456,7 +9055,7 @@ When _s_e_t, Mutt-ng uses the date received rather than the date sent to thread messages by subject. - _6_._4_._3_1_7 _t_i_l_d_e + _7_._4_._3_3_3 _t_i_l_d_e Type: boolean @@ -8465,7 +9064,9 @@ When _s_e_t, the internal-pager will pad blank lines to the bottom of the screen with a tilde (~). - _6_._4_._3_1_8 _t_i_m_e_o_u_t + The Mutt Next Generation E-Mail Client 171 + + _7_._4_._3_3_4 _t_i_m_e_o_u_t Type: number @@ -8475,7 +9076,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_1_9 _t_m_p_d_i_r + _7_._4_._3_3_5 _t_m_p_d_i_r Type: path @@ -8486,7 +9087,7 @@ set, the environment variable $TMPDIR is used. If $TMPDIR is not set then '/tmp' is used. - _6_._4_._3_2_0 _t_o___c_h_a_r_s + _7_._4_._3_3_6 _t_o___c_h_a_r_s Type: string @@ -8496,16 +9097,13 @@ acter is the one used when the mail is NOT addressed to your address (default: space). The second is used when you are the only recipient of the message (default: +). The third is when your address appears in the ``To:'' header - - The Mutt Next Generation E-Mail Client 160 - field, but you are not the only recipient of the message (default: T). The fourth character is used when your address is specified in the ``Cc:'' header field, but you are not the only recipient. The fifth character is used to 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_1 _t_r_a_s_h + _7_._4_._3_3_7 _t_r_a_s_h Type: path @@ -8517,12 +9115,14 @@ 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_2 _t_u_n_n_e_l + _7_._4_._3_3_8 _t_u_n_n_e_l Type: string Default: '' + The Mutt Next Generation E-Mail Client 172 + 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: @@ -8532,7 +9132,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_3 _u_m_a_s_k + _7_._4_._3_3_9 _u_m_a_s_k Type: number @@ -8541,7 +9141,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_4 _u_n_c_o_l_l_a_p_s_e___j_u_m_p + _7_._4_._3_4_0 _u_n_c_o_l_l_a_p_s_e___j_u_m_p Type: boolean @@ -8550,32 +9150,34 @@ 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_5 _u_s_e___8_b_i_t_m_i_m_e + _7_._4_._3_4_1 _u_s_e___8_b_i_t_m_i_m_e Type: boolean - The Mutt Next Generation E-Mail Client 161 - Default: no 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 you may not be - able to send mail. + 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 + mail. - When _s_e_t, Mutt-ng will invoke ``_$_s_e_n_d_m_a_i_l (section 6.4.247 , page 140)'' with - the -B8BITMIME flag when sending 8-bit messages to enable ESMTP negotiation. + When _s_e_t, Mutt-ng will either invoke ``_$_s_e_n_d_m_a_i_l (section 7.4.260 , page + 151)'' with the -B8BITMIME flag when sending 8-bit messages to enable ESMTP + negotiation or tell libESMTP to do so. - _6_._4_._3_2_6 _u_s_e___d_o_m_a_i_n + _7_._4_._3_4_2 _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 100)''. If _u_n_s_e_t, + tion) with the value of ``_$_h_o_s_t_n_a_m_e (section 7.4.95 , page 110)''. If _u_n_s_e_t, no addresses will be qualified. - _6_._4_._3_2_7 _u_s_e___f_r_o_m + _7_._4_._3_4_3 _u_s_e___f_r_o_m + + The Mutt Next Generation E-Mail Client 173 Type: boolean @@ -8583,9 +9185,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 37)'' command. - _6_._4_._3_2_8 _u_s_e___i_d_n + _7_._4_._3_4_4 _u_s_e___i_d_n Type: boolean @@ -8598,7 +9200,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_2_9 _u_s_e___i_p_v_6 + _7_._4_._3_4_5 _u_s_e___i_p_v_6 Type: boolean @@ -8608,18 +9210,7 @@ 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_0 _u_s_e_r___a_g_e_n_t - - The Mutt Next Generation E-Mail Client 162 - - 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_1 _v_i_s_u_a_l + _7_._4_._3_4_6 _v_i_s_u_a_l Type: path @@ -8628,7 +9219,7 @@ Specifies the visual editor to invoke when the _~_v command is given in the builtin editor. - _6_._4_._3_3_2 _w_a_i_t___k_e_y + _7_._4_._3_4_7 _w_a_i_t___k_e_y Type: boolean @@ -8638,13 +9229,16 @@ _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 - 74)'', provided that the corresponding mailcap entry has a needsterminal flag, + 78)'', 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 + + The Mutt Next Generation E-Mail Client 174 + a key only if the external command returned a non-zero status. - _6_._4_._3_3_3 _w_e_e_d + _7_._4_._3_4_8 _w_e_e_d Type: boolean @@ -8653,7 +9247,7 @@ When _s_e_t, Mutt-ng will weed headers when displaying, forwarding, printing, or replying to messages. - _6_._4_._3_3_4 _w_r_a_p___s_e_a_r_c_h + _7_._4_._3_4_9 _w_r_a_p___s_e_a_r_c_h Type: boolean @@ -8664,9 +9258,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_5 _w_r_a_p_m_a_r_g_i_n - - The Mutt Next Generation E-Mail Client 163 + _7_._4_._3_5_0 _w_r_a_p_m_a_r_g_i_n Type: number @@ -8675,7 +9267,7 @@ 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_6 _w_r_i_t_e___b_c_c + _7_._4_._3_5_1 _w_r_i_t_e___b_c_c Type: boolean @@ -8684,7 +9276,7 @@ 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_3_7 _w_r_i_t_e___i_n_c + _7_._4_._3_5_2 _w_r_i_t_e___i_n_c Type: number @@ -8694,25 +9286,27 @@ 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 135)'' variable. + Also see the ``_$_r_e_a_d___i_n_c (section 7.4.239 , page 146)'' variable. - _6_._4_._3_3_8 _x_t_e_r_m___i_c_o_n + _7_._4_._3_5_3 _x_t_e_r_m___i_c_o_n + + The Mutt Next Generation E-Mail Client 175 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.340 , page 162) 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.305 , page 153)''. + tion 7.4.355 , page 175) 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.321 , page 165)''. - _6_._4_._3_3_9 _x_t_e_r_m___l_e_a_v_e + _7_._4_._3_5_4 _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.340 , page 162) 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.355 , page 175) 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. @@ -8722,9 +9316,7 @@ set xterm_leave = '`test x$DISPLAY != x && xprop -id $WINDOWID | grep WM_NAME | cut -d ''' -f 2`' - The Mutt Next Generation E-Mail Client 164 - - _6_._4_._3_4_0 _x_t_e_r_m___s_e_t___t_i_t_l_e_s + _7_._4_._3_5_5 _x_t_e_r_m___s_e_t___t_i_t_l_e_s Type: boolean @@ -8734,33 +9326,33 @@ 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_1 _x_t_e_r_m___t_i_t_l_e + _7_._4_._3_5_6 _x_t_e_r_m___t_i_t_l_e Type: string 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.340 , page 162) 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.305 , - page 153)''. + _$_x_t_e_r_m___s_e_t___t_i_t_l_e_s (section 7.4.355 , page 175) 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.321 , + page 165)''. - _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 Mutt Next Generation E-Mail Client 176 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- tings for this menu will affect the default bindings for all menus (except as noted). - The Mutt Next Generation E-Mail Client 165 - bottom-page L move to the bottom of the page current-bottom not bound move current entry to bottom of page current-middle not bound move current entry to middle of page @@ -8793,9 +9385,9 @@ 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 + _7_._5_._2 _i_n_d_e_x - The Mutt Next Generation E-Mail Client 166 + The Mutt Next Generation E-Mail Client 177 bounce-message b remail a message to another user change-folder c open a different folder @@ -8852,7 +9444,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 167 + The Mutt Next Generation E-Mail Client 178 sort-mailbox o sort messages sort-reverse O sort messages in reverse order @@ -8868,9 +9460,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 168 + The Mutt Next Generation E-Mail Client 179 bottom not bound jump to the bottom of the message bounce-message b remail a message to another user @@ -8927,7 +9519,7 @@ recall-message R recall a postponed message redraw-screen ^L clear and redraw the screen - The Mutt Next Generation E-Mail Client 169 + The Mutt Next Generation E-Mail Client 180 reply r reply to a message save-message s save message/attachment to a file @@ -8948,13 +9540,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 @@ -8965,9 +9557,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 170 + The Mutt Next Generation E-Mail Client 181 bounce-message b remail a message to another user collapse-parts v toggle display of subparts @@ -8988,9 +9580,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 171 + The Mutt Next Generation E-Mail Client 182 attach-file a attach a file(s) to this message attach-message A attach message(s) to this message @@ -9026,14 +9618,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 172 + The Mutt Next Generation E-Mail Client 183 change-dir c change directories check-new TAB check mailboxes for new mail @@ -9050,12 +9642,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 @@ -9080,11 +9672,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 173 + The Mutt Next Generation E-Mail Client 184 - _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. @@ -9127,7 +9719,7 @@ Marco d'Itri , - Bjoern Jacke , + Bjrn Jacke , Byrial Jensen , @@ -9139,11 +9731,11 @@ Felix von Leitner (a.k.a ``Fefe'') , - The Mutt Next Generation E-Mail Client 174 + The Mutt Next Generation E-Mail Client 185 Brandon Long , - Jimmy Maekelae , + Jimmy Mkel , Lars Marowsky-Bree , @@ -9185,6 +9777,8 @@ The following people have been very helpful to the development of Mutt-ng: + Christian Gall + Iain Lea Andreas Kneib @@ -9193,14 +9787,14 @@ Elimar Riesebieter - _7_._2 _A_b_o_u_t _t_h_i_s _d_o_c_u_m_e_n_t + The Mutt Next Generation E-Mail Client 186 - The Mutt Next Generation E-Mail Client 175 + _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 176 + The Mutt Next Generation E-Mail Client 187 CONTENTS @@ -9249,478 +9843,519 @@ 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 - - 4. Advanced Usage ....................................................... 45 - 4.1 Regular Expressions ............................................ 45 - 4.2 Patterns ....................................................... 48 - 4.2.1 Complex Patterns 48 - 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) ........................................ 59 - 4.14 IMAP Support (OPTIONAL) ........................................ 60 - 4.14.1 The Folder Browser 61 + 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 25 + 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 ................................................ 29 + 3.9 Using color and mono video attributes .......................... 30 + 3.10 Ignoring (weeding) unwanted message headers .................... 32 + 3.11 Alternative addresses .......................................... 33 + 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 35 + 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 ........................................... 37 + 3.17 Defining the order of headers when viewing messages ............ 38 + 3.18 Specify default save filename .................................. 38 + 3.19 Specify default Fcc: mailbox when composing .................... 39 + 3.20 Specify default save filename and default Fcc: mailbox at once . 39 + 3.21 Change settings based upon message recipients .................. 39 + 3.22 Change settings before formatting a message .................... 40 + 3.23 Choosing the cryptographic key of the recipient ................ 41 + 3.24 Adding key sequences to the keyboard buffer .................... 41 + 3.25 Executing functions ............................................ 41 + 3.26 Message Scoring ................................................ 41 + 3.27 Spam detection ................................................. 43 + 3.28 Setting variables .............................................. 44 + 3.29 Reading initialization commands from another file .............. 45 + 3.30 Removing hooks ................................................. 46 + 3.31 Sharing Setups ............................................. 46 + 3.31.1 Character Sets 46 + 3.31.2 Modularization 46 + 3.31.3 Conditional parts 46 + 3.32 Obsolete Variables ............................................. 48 + + 4. Advanced Usage ....................................................... 48 + 4.1 Regular Expressions ............................................ 48 + 4.2 Patterns ....................................................... 51 + 4.2.1 Complex Patterns 52 + 4.2.2 Patterns and Dates 52 + 4.3 Format Strings ............................................. 53 + 4.3.1 Introduction 53 + 4.3.2 Conditional Expansion 54 + 4.3.3 Modifications and Padding 55 + 4.4 Using Tags ..................................................... 56 + 4.5 Using Hooks .................................................... 56 + 4.5.1 Message Matching in Hooks 57 ii - 4.14.2 Authentication 61 - 4.15 NNTP Support (OPTIONAL) ........................................ 62 - 4.15.1 Again: Scoring 62 - 4.16 Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) ............ 63 - 4.17 Start a WWW Browser on URLs (EXTERNAL) ......................... 63 - 4.18 Compressed folders Support (OPTIONAL) .......................... 64 - 4.18.1 Open a compressed mailbox for reading 64 - 4.18.2 Write a compressed mailbox 65 - 4.18.3 Append a message to a compressed mailbox 65 - 4.18.4 Encrypted folders 66 - - 5. Mutt-ng's MIME Support ............................................... 66 - 5.1 Using MIME in Mutt ............................................. 67 - 5.1.1 Viewing MIME messages in the pager 67 - 5.1.2 The Attachment Menu 67 - 5.1.3 The Compose Menu 67 - 5.2 MIME Type configuration with mime.types ........................ 68 - 5.3 MIME Viewer configuration with mailcap ......................... 69 - 5.3.1 The Basics of the mailcap file 69 - 5.3.2 Secure use of mailcap 70 - 5.3.3 Advanced mailcap Usage 71 - 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 ......................................... 79 - 6.4 Configuration variables .......................................... 81 - 6.4.1 abort_nosubject 81 - 6.4.2 abort_unmodified 81 - 6.4.3 alias_file 81 - 6.4.4 alias_format 81 - 6.4.5 allow_8bit 82 - 6.4.6 allow_ansi 82 - 6.4.7 arrow_cursor 82 - 6.4.8 ascii_chars 83 - 6.4.9 askbcc 83 - 6.4.10 askcc 83 - 6.4.11 assumed_charset 83 - 6.4.12 attach_format 83 - 6.4.13 attach_sep 84 - 6.4.14 attach_split 85 - 6.4.15 attribution 85 - 6.4.16 auto_tag 85 - 6.4.17 autoedit 85 - 6.4.18 beep 85 - 6.4.19 beep_new 86 - 6.4.20 bounce 86 - 6.4.21 bounce_delivered 86 - 6.4.22 braille_friendly 86 + 4.6 Using the sidebar .............................................. 58 + 4.7 External Address Queries ....................................... 59 + 4.8 Mailbox Formats ................................................ 59 + 4.9 Mailbox Shortcuts .............................................. 60 + 4.10 Handling Mailing Lists ......................................... 60 + 4.11 Editing threads ................................................ 62 + 4.11.1 Linking threads 62 + 4.11.2 Breaking threads 62 + 4.12 Delivery Status Notification (DSN) Support ..................... 62 + 4.13 POP3 Support (OPTIONAL) ........................................ 63 + 4.14 IMAP Support (OPTIONAL) ........................................ 64 + 4.14.1 The Folder Browser 64 + 4.14.2 Authentication 65 + 4.15 NNTP Support (OPTIONAL) ........................................ 65 + 4.15.1 Again: Scoring 66 + 4.16 SMTP Support (OPTIONAL) ........................................ 66 + 4.17 Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) ............ 67 + 4.18 Start a WWW Browser on URLs (EXTERNAL) ......................... 67 + 4.19 Compressed folders Support (OPTIONAL) .......................... 68 + 4.19.1 Open a compressed mailbox for reading 68 + 4.19.2 Write a compressed mailbox 69 + 4.19.3 Append a message to a compressed mailbox 69 + 4.19.4 Encrypted folders 70 + + 5. Mutt-ng's MIME Support ............................................... 70 + 5.1 Using MIME in Mutt ............................................. 70 + 5.1.1 Viewing MIME messages in the pager 71 + 5.1.2 The Attachment Menu 71 + 5.1.3 The Compose Menu 71 + 5.2 MIME Type configuration with mime.types ........................ 72 + 5.3 MIME Viewer configuration with mailcap ......................... 72 + 5.3.1 The Basics of the mailcap file 73 + 5.3.2 Secure use of mailcap 74 + 5.3.3 Advanced mailcap Usage 75 + 5.3.4 Example mailcap files 77 + 5.4 MIME Autoview .................................................. 78 + 5.5 MIME Multipart/Alternative ..................................... 79 + 5.6 MIME Lookup .................................................... 79 + + 6. Security Considerations ............................................ 80 + 6.1 Passwords .................................................. 80 + 6.2 Temporary Files ............................................ 80 + 6.3 Information Leaks ............................................ 81 + 6.3.1 Message-ID: headers 81 + 6.3.2 mailto:-style links 81 + 6.4 External applications ...................................... 81 + 6.4.1 mailcap 81 + 6.4.2 Other 82 + + 7. Reference ............................................................ 82 + 7.1 Command line options ........................................... 82 + 7.2 Patterns ....................................................... 83 + 7.3 Configuration Commands ......................................... 85 iii - 6.4.23 certificate_file 86 - 6.4.24 charset 87 - 6.4.25 check_new 87 - 6.4.26 collapse_unread 87 - 6.4.27 compose_format 87 - 6.4.28 config_charset 88 - 6.4.29 confirmappend 88 - 6.4.30 confirmcreate 88 - 6.4.31 connect_timeout 88 - 6.4.32 content_type 88 - 6.4.33 copy 89 - 6.4.34 crypt_autoencrypt 89 - 6.4.35 crypt_autopgp 89 - 6.4.36 crypt_autosign 89 - 6.4.37 crypt_autosmime 90 - 6.4.38 crypt_replyencrypt 90 - 6.4.39 crypt_replysign 90 - 6.4.40 crypt_replysignencrypted 90 - 6.4.41 crypt_timestamp 90 - 6.4.42 crypt_use_gpgme 91 - 6.4.43 crypt_verify_sig 91 - 6.4.44 date_format 91 - 6.4.45 default_hook 91 - 6.4.46 delete 92 - 6.4.47 delete_untag 92 - 6.4.48 digest_collapse 92 - 6.4.49 display_filter 92 - 6.4.50 dotlock_program 92 - 6.4.51 dsn_notify 93 - 6.4.52 dsn_return 93 - 6.4.53 duplicate_threads 93 - 6.4.54 edit_headers 93 - 6.4.55 editor 93 - 6.4.56 encode_from 94 - 6.4.57 entropy_file 94 - 6.4.58 envelope_from 94 - 6.4.59 escape 94 - 6.4.60 fast_reply 94 - 6.4.61 fcc_attach 95 - 6.4.62 fcc_clear 95 - 6.4.63 file_charset 95 - 6.4.64 folder 95 - 6.4.65 folder_format 96 - 6.4.66 followup_to 96 - 6.4.67 force_buffy_check 97 - 6.4.68 force_name 97 - 6.4.69 forward_decode 97 - 6.4.70 forward_decrypt 97 - 6.4.71 forward_edit 98 - 6.4.72 forward_format 98 - 6.4.73 forward_quote 98 - 6.4.74 from 98 - 6.4.75 gecos_mask 98 + 7.4 Configuration variables .......................................... 87 + 7.4.1 abort_noattach 88 + 7.4.2 abort_nosubject 89 + 7.4.3 abort_unmodified 89 + 7.4.4 agent_string 89 + 7.4.5 alias_file 89 + 7.4.6 alias_format 89 + 7.4.7 allow_8bit 90 + 7.4.8 allow_ansi 90 + 7.4.9 arrow_cursor 90 + 7.4.10 ascii_chars 91 + 7.4.11 askbcc 91 + 7.4.12 askcc 91 + 7.4.13 assumed_charset 91 + 7.4.14 attach_format 91 + 7.4.15 attach_remind_regexp 92 + 7.4.16 attach_sep 93 + 7.4.17 attach_split 93 + 7.4.18 attribution 93 + 7.4.19 auto_tag 93 + 7.4.20 autoedit 93 + 7.4.21 beep 94 + 7.4.22 beep_new 94 + 7.4.23 bounce 94 + 7.4.24 bounce_delivered 94 + 7.4.25 braille_friendly 94 + 7.4.26 certificate_file 95 + 7.4.27 charset 95 + 7.4.28 check_new 95 + 7.4.29 collapse_unread 95 + 7.4.30 compose_format 96 + 7.4.31 config_charset 96 + 7.4.32 confirmappend 96 + 7.4.33 confirmcreate 96 + 7.4.34 connect_timeout 96 + 7.4.35 content_type 97 + 7.4.36 copy 97 + 7.4.37 crypt_autoencrypt 97 + 7.4.38 crypt_autopgp 97 + 7.4.39 crypt_autosign 98 + 7.4.40 crypt_autosmime 98 + 7.4.41 crypt_replyencrypt 98 + 7.4.42 crypt_replysign 98 + 7.4.43 crypt_replysignencrypted 98 + 7.4.44 crypt_timestamp 99 + 7.4.45 crypt_use_gpgme 99 + 7.4.46 crypt_verify_sig 99 + 7.4.47 date_format 99 + 7.4.48 debug_level 100 + 7.4.49 default_hook 100 + 7.4.50 delete 100 + 7.4.51 delete_space 100 + 7.4.52 delete_untag 101 iv - 6.4.76 hdrs 99 - 6.4.77 header 99 - 6.4.78 header_cache 99 - 6.4.79 header_cache_compress 100 - 6.4.80 help 100 - 6.4.81 hidden_host 100 - 6.4.82 hide_limited 100 - 6.4.83 hide_missing 100 - 6.4.84 hide_thread_subject 101 - 6.4.85 hide_top_limited 101 - 6.4.86 hide_top_missing 101 - 6.4.87 history 101 - 6.4.88 honor_followup_to 101 - 6.4.89 hostname 101 - 6.4.90 ignore_list_reply_to 102 - 6.4.91 imap_authenticators 102 - 6.4.92 imap_delim_chars 102 - 6.4.93 imap_force_ssl 103 - 6.4.94 imap_headers 103 - 6.4.95 imap_home_namespace 103 - 6.4.96 imap_keepalive 103 - 6.4.97 imap_list_subscribed 104 - 6.4.98 imap_login 104 - 6.4.99 imap_mail_check 104 - 6.4.100 imap_pass 104 - 6.4.101 imap_passive 105 - 6.4.102 imap_peek 105 - 6.4.103 imap_reconnect 105 - 6.4.104 imap_servernoise 105 - 6.4.105 imap_user 105 - 6.4.106 implicit_autoview 106 - 6.4.107 include 106 - 6.4.108 include_onlyfirst 106 - 6.4.109 indent_string 106 - 6.4.110 index_format 106 - 6.4.111 ispell 109 - 6.4.112 keep_flagged 109 - 6.4.113 list_reply 109 - 6.4.114 locale 110 - 6.4.115 mail_check 110 - 6.4.116 mailcap_path 110 - 6.4.117 mailcap_sanitize 110 - 6.4.118 maildir_header_cache_verify 110 - 6.4.119 maildir_trash 111 - 6.4.120 mark_old 111 - 6.4.121 markers 111 - 6.4.122 mask 111 - 6.4.123 max_line_length 112 - 6.4.124 mbox 112 - 6.4.125 mbox_type 112 - 6.4.126 menu_context 112 - 6.4.127 menu_move_off 112 - 6.4.128 menu_scroll 112 + 7.4.53 digest_collapse 101 + 7.4.54 display_filter 101 + 7.4.55 dotlock_program 101 + 7.4.56 dsn_notify 101 + 7.4.57 dsn_return 102 + 7.4.58 duplicate_threads 102 + 7.4.59 edit_headers 102 + 7.4.60 editor 102 + 7.4.61 editor_headers 102 + 7.4.62 encode_from 103 + 7.4.63 entropy_file 103 + 7.4.64 envelope_from 103 + 7.4.65 escape 103 + 7.4.66 fast_reply 104 + 7.4.67 fcc_attach 104 + 7.4.68 fcc_clear 104 + 7.4.69 file_charset 104 + 7.4.70 folder 104 + 7.4.71 folder_format 105 + 7.4.72 followup_to 106 + 7.4.73 force_buffy_check 106 + 7.4.74 force_name 106 + 7.4.75 forward_decode 106 + 7.4.76 forward_decrypt 107 + 7.4.77 forward_edit 107 + 7.4.78 forward_format 107 + 7.4.79 forward_quote 107 + 7.4.80 from 107 + 7.4.81 gecos_mask 108 + 7.4.82 hdrs 108 + 7.4.83 header 108 + 7.4.84 header_cache 108 + 7.4.85 header_cache_compress 109 + 7.4.86 help 109 + 7.4.87 hidden_host 109 + 7.4.88 hide_limited 109 + 7.4.89 hide_missing 109 + 7.4.90 hide_thread_subject 110 + 7.4.91 hide_top_limited 110 + 7.4.92 hide_top_missing 110 + 7.4.93 history 110 + 7.4.94 honor_followup_to 110 + 7.4.95 hostname 111 + 7.4.96 ignore_list_reply_to 111 + 7.4.97 imap_authenticators 111 + 7.4.98 imap_check_subscribed 111 + 7.4.99 imap_delim_chars 112 + 7.4.100 imap_headers 112 + 7.4.101 imap_home_namespace 112 + 7.4.102 imap_keepalive 112 + 7.4.103 imap_list_subscribed 113 + 7.4.104 imap_login 113 + 7.4.105 imap_mail_check 113 v - 6.4.129 message_format 113 - 6.4.130 meta_key 113 - 6.4.131 metoo 113 - 6.4.132 mh_purge 113 - 6.4.133 mh_seq_flagged 113 - 6.4.134 mh_seq_replied 114 - 6.4.135 mh_seq_unseen 114 - 6.4.136 mime_forward 114 - 6.4.137 mime_forward_decode 114 - 6.4.138 mime_forward_rest 114 - 6.4.139 mix_entry_format 114 - 6.4.140 mixmaster 115 - 6.4.141 move 115 - 6.4.142 msgid_format 115 - 6.4.143 narrow_tree 116 - 6.4.144 nntp_ask_followup_to 117 - 6.4.145 nntp_ask_x_comment_to 117 - 6.4.146 nntp_cache_dir 117 - 6.4.147 nntp_catchup 117 - 6.4.148 nntp_context 117 - 6.4.149 nntp_followup_to_poster 118 - 6.4.150 nntp_group_index_format 118 - 6.4.151 nntp_host 118 - 6.4.152 nntp_inews 119 - 6.4.153 nntp_load_description 119 - 6.4.154 nntp_mail_check 119 - 6.4.155 nntp_mime_subject 120 - 6.4.156 nntp_newsrc 120 - 6.4.157 nntp_pass 120 - 6.4.158 nntp_post_moderated 120 - 6.4.159 nntp_reconnect 121 - 6.4.160 nntp_save_unsubscribed 121 - 6.4.161 nntp_show_new_news 121 - 6.4.162 nntp_show_only_unread 121 - 6.4.163 nntp_user 121 - 6.4.164 nntp_x_comment_to 122 - 6.4.165 operating_system 122 - 6.4.166 pager 122 - 6.4.167 pager_context 122 - 6.4.168 pager_format 123 - 6.4.169 pager_index_lines 123 - 6.4.170 pager_stop 123 - 6.4.171 pgp_auto_decode 123 - 6.4.172 pgp_autoinline 123 - 6.4.173 pgp_check_exit 124 - 6.4.174 pgp_clearsign_command 124 - 6.4.175 pgp_decode_command 124 - 6.4.176 pgp_decrypt_command 125 - 6.4.177 pgp_encrypt_only_command 125 - 6.4.178 pgp_encrypt_sign_command 125 - 6.4.179 pgp_entry_format 125 - 6.4.180 pgp_export_command 126 - 6.4.181 pgp_getkeys_command 126 + 7.4.106 imap_pass 113 + 7.4.107 imap_passive 114 + 7.4.108 imap_peek 114 + 7.4.109 imap_reconnect 114 + 7.4.110 imap_servernoise 114 + 7.4.111 imap_user 115 + 7.4.112 implicit_autoview 115 + 7.4.113 include 115 + 7.4.114 include_onlyfirst 115 + 7.4.115 indent_string 115 + 7.4.116 index_format 115 + 7.4.117 ispell 118 + 7.4.118 keep_flagged 118 + 7.4.119 list_reply 119 + 7.4.120 locale 119 + 7.4.121 mail_check 119 + 7.4.122 mailcap_path 119 + 7.4.123 mailcap_sanitize 119 + 7.4.124 maildir_header_cache_verify 119 + 7.4.125 maildir_trash 120 + 7.4.126 mark_old 120 + 7.4.127 markers 120 + 7.4.128 mask 120 + 7.4.129 max_display_recips 121 + 7.4.130 max_line_length 121 + 7.4.131 mbox 121 + 7.4.132 mbox_type 121 + 7.4.133 menu_context 121 + 7.4.134 menu_move_off 122 + 7.4.135 menu_scroll 122 + 7.4.136 message_format 122 + 7.4.137 meta_key 122 + 7.4.138 metoo 122 + 7.4.139 mh_purge 123 + 7.4.140 mh_seq_flagged 123 + 7.4.141 mh_seq_replied 123 + 7.4.142 mh_seq_unseen 123 + 7.4.143 mime_forward 123 + 7.4.144 mime_forward_decode 123 + 7.4.145 mime_forward_rest 124 + 7.4.146 mix_entry_format 124 + 7.4.147 mixmaster 124 + 7.4.148 move 124 + 7.4.149 msgid_format 125 + 7.4.150 muttng_bindir 126 + 7.4.151 muttng_docdir 126 + 7.4.152 muttng_hcache_backend 126 + 7.4.153 muttng_revision 126 + 7.4.154 muttng_sysconfdir 126 + 7.4.155 muttng_version 127 + 7.4.156 narrow_tree 127 + 7.4.157 nntp_ask_followup_to 127 + 7.4.158 nntp_ask_x_comment_to 127 vi - 6.4.182 pgp_good_sign 126 - 6.4.183 pgp_ignore_subkeys 126 - 6.4.184 pgp_import_command 127 - 6.4.185 pgp_list_pubring_command 127 - 6.4.186 pgp_list_secring_command 127 - 6.4.187 pgp_long_ids 127 - 6.4.188 pgp_mime_auto 127 - 6.4.189 pgp_replyinline 128 - 6.4.190 pgp_retainable_sigs 128 - 6.4.191 pgp_show_unusable 128 - 6.4.192 pgp_sign_as 128 - 6.4.193 pgp_sign_command 129 - 6.4.194 pgp_sort_keys 129 - 6.4.195 pgp_strict_enc 129 - 6.4.196 pgp_timeout 129 - 6.4.197 pgp_use_gpg_agent 130 - 6.4.198 pgp_verify_command 130 - 6.4.199 pgp_verify_key_command 130 - 6.4.200 pipe_decode 130 - 6.4.201 pipe_sep 130 - 6.4.202 pipe_split 130 - 6.4.203 pop_auth_try_all 131 - 6.4.204 pop_authenticators 131 - 6.4.205 pop_delete 131 - 6.4.206 pop_host 131 - 6.4.207 pop_last 132 - 6.4.208 pop_mail_check 132 - 6.4.209 pop_pass 132 - 6.4.210 pop_reconnect 132 - 6.4.211 pop_user 133 - 6.4.212 post_indent_string 133 - 6.4.213 postpone 133 - 6.4.214 postponed 133 - 6.4.215 preconnect 133 - 6.4.216 print 134 - 6.4.217 print_command 134 - 6.4.218 print_decode 134 - 6.4.219 print_split 134 - 6.4.220 prompt_after 135 - 6.4.221 query_command 135 - 6.4.222 quit 135 - 6.4.223 quote_empty 135 - 6.4.224 quote_quoted 135 - 6.4.225 quote_regexp 136 - 6.4.226 read_inc 136 - 6.4.227 read_only 136 - 6.4.228 realname 136 - 6.4.229 recall 136 - 6.4.230 record 137 - 6.4.231 reply_regexp 137 - 6.4.232 reply_self 137 - 6.4.233 reply_to 137 - 6.4.234 resolve 138 + 7.4.159 nntp_cache_dir 127 + 7.4.160 nntp_catchup 128 + 7.4.161 nntp_context 128 + 7.4.162 nntp_followup_to_poster 128 + 7.4.163 nntp_group_index_format 128 + 7.4.164 nntp_host 129 + 7.4.165 nntp_inews 129 + 7.4.166 nntp_load_description 129 + 7.4.167 nntp_mail_check 130 + 7.4.168 nntp_mime_subject 130 + 7.4.169 nntp_newsrc 130 + 7.4.170 nntp_pass 130 + 7.4.171 nntp_post_moderated 131 + 7.4.172 nntp_reconnect 131 + 7.4.173 nntp_save_unsubscribed 131 + 7.4.174 nntp_show_new_news 131 + 7.4.175 nntp_show_only_unread 132 + 7.4.176 nntp_user 132 + 7.4.177 nntp_x_comment_to 132 + 7.4.178 operating_system 132 + 7.4.179 pager 132 + 7.4.180 pager_context 133 + 7.4.181 pager_format 133 + 7.4.182 pager_index_lines 133 + 7.4.183 pager_stop 133 + 7.4.184 pgp_auto_decode 134 + 7.4.185 pgp_autoinline 134 + 7.4.186 pgp_check_exit 134 + 7.4.187 pgp_clearsign_command 134 + 7.4.188 pgp_decode_command 135 + 7.4.189 pgp_decrypt_command 135 + 7.4.190 pgp_encrypt_only_command 135 + 7.4.191 pgp_encrypt_sign_command 135 + 7.4.192 pgp_entry_format 136 + 7.4.193 pgp_export_command 136 + 7.4.194 pgp_getkeys_command 136 + 7.4.195 pgp_good_sign 137 + 7.4.196 pgp_ignore_subkeys 137 + 7.4.197 pgp_import_command 137 + 7.4.198 pgp_list_pubring_command 137 + 7.4.199 pgp_list_secring_command 137 + 7.4.200 pgp_long_ids 138 + 7.4.201 pgp_mime_auto 138 + 7.4.202 pgp_replyinline 138 + 7.4.203 pgp_retainable_sigs 138 + 7.4.204 pgp_show_unusable 139 + 7.4.205 pgp_sign_as 139 + 7.4.206 pgp_sign_command 139 + 7.4.207 pgp_sort_keys 139 + 7.4.208 pgp_strict_enc 140 + 7.4.209 pgp_timeout 140 + 7.4.210 pgp_use_gpg_agent 140 + 7.4.211 pgp_verify_command 140 vii - 6.4.235 reverse_alias 138 - 6.4.236 reverse_name 138 - 6.4.237 reverse_realname 138 - 6.4.238 rfc2047_parameters 139 - 6.4.239 save_address 139 - 6.4.240 save_empty 139 - 6.4.241 save_name 139 - 6.4.242 score 140 - 6.4.243 score_threshold_delete 140 - 6.4.244 score_threshold_flag 140 - 6.4.245 score_threshold_read 140 - 6.4.246 send_charset 140 - 6.4.247 sendmail 141 - 6.4.248 sendmail_wait 141 - 6.4.249 shell 141 - 6.4.250 sidebar_boundary 142 - 6.4.251 sidebar_delim 142 - 6.4.252 sidebar_newmail_only 142 - 6.4.253 sidebar_number_format 142 - 6.4.254 sidebar_shorten_hierarchy 142 - 6.4.255 sidebar_visible 143 - 6.4.256 sidebar_width 143 - 6.4.257 sig_dashes 143 - 6.4.258 sig_on_top 143 - 6.4.259 signature 144 - 6.4.260 signoff_string 144 - 6.4.261 simple_search 144 - 6.4.262 sleep_time 144 - 6.4.263 smart_wrap 144 - 6.4.264 smileys 145 - 6.4.265 smime_ask_cert_label 145 - 6.4.266 smime_ca_location 145 - 6.4.267 smime_certificates 145 - 6.4.268 smime_decrypt_command 145 - 6.4.269 smime_decrypt_use_default_key 146 - 6.4.270 smime_default_key 146 - 6.4.271 smime_encrypt_command 147 - 6.4.272 smime_encrypt_with 147 - 6.4.273 smime_get_cert_command 147 - 6.4.274 smime_get_cert_email_command 147 - 6.4.275 smime_get_signer_cert_command 147 - 6.4.276 smime_import_cert_command 147 - 6.4.277 smime_is_default 148 - 6.4.278 smime_keys 148 - 6.4.279 smime_pk7out_command 148 - 6.4.280 smime_sign_command 148 - 6.4.281 smime_sign_opaque_command 148 - 6.4.282 smime_timeout 149 - 6.4.283 smime_verify_command 149 - 6.4.284 smime_verify_opaque_command 149 - 6.4.285 smtp_auth_password 149 - 6.4.286 smtp_auth_username 149 - 6.4.287 smtp_host 150 + 7.4.212 pgp_verify_key_command 140 + 7.4.213 pipe_decode 140 + 7.4.214 pipe_sep 141 + 7.4.215 pipe_split 141 + 7.4.216 pop_auth_try_all 141 + 7.4.217 pop_authenticators 141 + 7.4.218 pop_delete 142 + 7.4.219 pop_host 142 + 7.4.220 pop_last 142 + 7.4.221 pop_mail_check 142 + 7.4.222 pop_pass 143 + 7.4.223 pop_reconnect 143 + 7.4.224 pop_user 143 + 7.4.225 post_indent_string 143 + 7.4.226 postpone 143 + 7.4.227 postponed 144 + 7.4.228 preconnect 144 + 7.4.229 print 144 + 7.4.230 print_command 144 + 7.4.231 print_decode 144 + 7.4.232 print_split 145 + 7.4.233 prompt_after 145 + 7.4.234 query_command 145 + 7.4.235 quit 145 + 7.4.236 quote_empty 146 + 7.4.237 quote_quoted 146 + 7.4.238 quote_regexp 146 + 7.4.239 read_inc 146 + 7.4.240 read_only 146 + 7.4.241 realname 147 + 7.4.242 recall 147 + 7.4.243 record 147 + 7.4.244 reply_regexp 147 + 7.4.245 reply_self 148 + 7.4.246 reply_to 148 + 7.4.247 resolve 148 + 7.4.248 reverse_alias 148 + 7.4.249 reverse_name 149 + 7.4.250 reverse_realname 149 + 7.4.251 rfc2047_parameters 149 + 7.4.252 save_address 149 + 7.4.253 save_empty 150 + 7.4.254 save_name 150 + 7.4.255 score 150 + 7.4.256 score_threshold_delete 150 + 7.4.257 score_threshold_flag 151 + 7.4.258 score_threshold_read 151 + 7.4.259 send_charset 151 + 7.4.260 sendmail 151 + 7.4.261 sendmail_wait 151 + 7.4.262 shell 152 + 7.4.263 sidebar_boundary 152 + 7.4.264 sidebar_delim 152 viii - 6.4.288 smtp_port 150 - 6.4.289 sort 150 - 6.4.290 sort_alias 151 - 6.4.291 sort_aux 151 - 6.4.292 sort_browser 151 - 6.4.293 sort_re 152 - 6.4.294 spam_separator 152 - 6.4.295 spoolfile 152 - 6.4.296 ssl_ca_certificates_file 152 - 6.4.297 ssl_client_cert 153 - 6.4.298 ssl_min_dh_prime_bits 153 - 6.4.299 ssl_starttls 153 - 6.4.300 ssl_use_sslv2 153 - 6.4.301 ssl_use_sslv3 153 - 6.4.302 ssl_use_tlsv1 154 - 6.4.303 ssl_usesystemcerts 154 - 6.4.304 status_chars 154 - 6.4.305 status_format 154 - 6.4.306 status_on_top 156 - 6.4.307 strict_mailto 157 - 6.4.308 strict_mime 157 - 6.4.309 strict_threads 157 - 6.4.310 strip_was 157 - 6.4.311 strip_was_regex 158 - 6.4.312 stuff_quoted 158 - 6.4.313 suspend 158 - 6.4.314 text_flowed 158 - 6.4.315 thorough_search 158 - 6.4.316 thread_received 159 - 6.4.317 tilde 159 - 6.4.318 timeout 159 - 6.4.319 tmpdir 159 - 6.4.320 to_chars 159 - 6.4.321 trash 160 - 6.4.322 tunnel 160 - 6.4.323 umask 160 - 6.4.324 uncollapse_jump 160 - 6.4.325 use_8bitmime 160 - 6.4.326 use_domain 161 - 6.4.327 use_from 161 - 6.4.328 use_idn 161 - 6.4.329 use_ipv6 161 - 6.4.330 user_agent 161 - 6.4.331 visual 162 - 6.4.332 wait_key 162 - 6.4.333 weed 162 - 6.4.334 wrap_search 162 - 6.4.335 wrapmargin 162 - 6.4.336 write_bcc 163 - 6.4.337 write_inc 163 - 6.4.338 xterm_icon 163 - 6.4.339 xterm_leave 163 - 6.4.340 xterm_set_titles 164 + 7.4.265 sidebar_newmail_only 152 + 7.4.266 sidebar_number_format 152 + 7.4.267 sidebar_shorten_hierarchy 153 + 7.4.268 sidebar_visible 153 + 7.4.269 sidebar_width 154 + 7.4.270 sig_dashes 154 + 7.4.271 sig_on_top 154 + 7.4.272 signature 154 + 7.4.273 signoff_string 154 + 7.4.274 simple_search 155 + 7.4.275 sleep_time 155 + 7.4.276 smart_wrap 155 + 7.4.277 smileys 155 + 7.4.278 smime_ask_cert_label 155 + 7.4.279 smime_ca_location 156 + 7.4.280 smime_certificates 156 + 7.4.281 smime_decrypt_command 156 + 7.4.282 smime_decrypt_use_default_key 157 + 7.4.283 smime_default_key 157 + 7.4.284 smime_encrypt_command 157 + 7.4.285 smime_encrypt_with 157 + 7.4.286 smime_get_cert_command 158 + 7.4.287 smime_get_cert_email_command 158 + 7.4.288 smime_get_signer_cert_command 158 + 7.4.289 smime_import_cert_command 158 + 7.4.290 smime_is_default 158 + 7.4.291 smime_keys 158 + 7.4.292 smime_pk7out_command 159 + 7.4.293 smime_sign_command 159 + 7.4.294 smime_sign_opaque_command 159 + 7.4.295 smime_timeout 159 + 7.4.296 smime_verify_command 159 + 7.4.297 smime_verify_opaque_command 160 + 7.4.298 smtp_envelope 160 + 7.4.299 smtp_host 160 + 7.4.300 smtp_pass 160 + 7.4.301 smtp_port 161 + 7.4.302 smtp_use_tls 161 + 7.4.303 smtp_user 161 + 7.4.304 sort 161 + 7.4.305 sort_alias 162 + 7.4.306 sort_aux 162 + 7.4.307 sort_browser 163 + 7.4.308 sort_re 163 + 7.4.309 spam_separator 163 + 7.4.310 spoolfile 163 + 7.4.311 ssl_ca_certificates_file 164 + 7.4.312 ssl_client_cert 164 + 7.4.313 ssl_force_tls 164 + 7.4.314 ssl_min_dh_prime_bits 164 + 7.4.315 ssl_starttls 164 + 7.4.316 ssl_use_sslv2 165 + 7.4.317 ssl_use_sslv3 165 ix - 6.4.341 xterm_title 164 - 6.5 Functions ....................................................... 164 - 6.5.1 generic 164 - 6.5.2 index 165 - 6.5.3 pager 167 - 6.5.4 alias 169 - 6.5.5 query 169 - 6.5.6 attach 169 - 6.5.7 compose 170 - 6.5.8 postpone 171 - 6.5.9 browser 171 - 6.5.10 pgp 172 - 6.5.11 editor 172 - - 7. Miscellany ............................................................ 172 - 7.1 Acknowledgments ................................................. 173 - 7.2 About this document ............................................. 174 + 7.4.318 ssl_use_tlsv1 165 + 7.4.319 ssl_usesystemcerts 165 + 7.4.320 status_chars 165 + 7.4.321 status_format 166 + 7.4.322 status_on_top 168 + 7.4.323 strict_mailto 168 + 7.4.324 strict_mime 168 + 7.4.325 strict_threads 169 + 7.4.326 strip_was 169 + 7.4.327 strip_was_regex 169 + 7.4.328 stuff_quoted 169 + 7.4.329 suspend 170 + 7.4.330 text_flowed 170 + 7.4.331 thorough_search 170 + 7.4.332 thread_received 170 + 7.4.333 tilde 170 + 7.4.334 timeout 171 + 7.4.335 tmpdir 171 + 7.4.336 to_chars 171 + 7.4.337 trash 171 + 7.4.338 tunnel 171 + 7.4.339 umask 172 + 7.4.340 uncollapse_jump 172 + 7.4.341 use_8bitmime 172 + 7.4.342 use_domain 172 + 7.4.343 use_from 172 + 7.4.344 use_idn 173 + 7.4.345 use_ipv6 173 + 7.4.346 visual 173 + 7.4.347 wait_key 173 + 7.4.348 weed 174 + 7.4.349 wrap_search 174 + 7.4.350 wrapmargin 174 + 7.4.351 write_bcc 174 + 7.4.352 write_inc 174 + 7.4.353 xterm_icon 174 + 7.4.354 xterm_leave 175 + 7.4.355 xterm_set_titles 175 + 7.4.356 xterm_title 175 + 7.5 Functions ....................................................... 175 + 7.5.1 generic 175 + 7.5.2 index 176 + 7.5.3 pager 178 + 7.5.4 alias 180 + 7.5.5 query 180 + 7.5.6 attach 180 + 7.5.7 compose 181 + 7.5.8 postpone 182 + 7.5.9 browser 182 + 7.5.10 pgp 183 + 7.5.11 editor 183 + + 8. Miscellany ............................................................ 183 x + 8.1 Acknowledgments ................................................. 184 + 8.2 About this document ............................................. 186 + + xi +