X-Git-Url: http://git.madism.org/?a=blobdiff_plain;f=doc%2Fmanual.txt;h=f91d763a653cc5f18f3922ae06da5d02d4c6ee1f;hb=618ceafdc9564dbb8f3bf45c3869297a1d5a3320;hp=457beac60ee047a5f71d2116b6a4cfb6ba72bfea;hpb=f7a7cee0f8bce7ddc378197a9394c6fceb6988ec;p=apps%2Fmadmutt.git diff --git a/doc/manual.txt b/doc/manual.txt index 457beac..f91d763 100644 --- a/doc/manual.txt +++ b/doc/manual.txt @@ -4,7 +4,7 @@ by Andreas Krennmair and others originally based on _m_u_t_t by Michael Elkins and others - version devel-r392 + version devel AAbbssttrraacctt @@ -413,7 +413,7 @@ +o cclleeaarr--ffllaagg (default: W) Furthermore, the following flags reflect who the message is addressed to. They - can be customized with the _$_t_o___c_h_a_r_s (section 6.4.323 , page 160) variable. + can be customized with the _$_t_o___c_h_a_r_s (section 7.4.325 , page 165) variable. + message is to you and you only @@ -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 75) script for high- lighting purposes. NNoottee:: If you change the colors for your display, for exam- ple by changing the color associated with color2 for your xterm, then that color will be used instead of green. _2_._5_._3 _T_h_r_e_a_d_e_d _M_o_d_e - When the mailbox is _s_o_r_t_e_d (section 6.4.291 , page 150) by _t_h_r_e_a_d_s, there are + When the mailbox is _s_o_r_t_e_d (section 7.4.293 , page 156) 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 106). 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 106) to optionally display the number of + tion 7.4.111 , page 111). For example, you could use "%?M?(#%03M)&(%4l)?" in + _$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.111 , page 111) to optionally display the number of hidden messages if the thread is collapsed. - See also: _$_s_t_r_i_c_t___t_h_r_e_a_d_s (section 6.4.312 , page 158). + See also: _$_s_t_r_i_c_t___t_h_r_e_a_d_s (section 7.4.314 , page 163). _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 @@ -531,8 +531,8 @@ 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 81) variable for - future use. NNoottee:: Specifying an _$_a_l_i_a_s___f_i_l_e (section 6.4.3 , page 81) does not + the file specified by the _$_a_l_i_a_s___f_i_l_e (section 7.4.3 , page 86) variable for + future use. NNoottee:: Specifying an _$_a_l_i_a_s___f_i_l_e (section 7.4.3 , page 86) does not add the aliases specified there-in, you must also _s_o_u_r_c_e (section 3.28 , page 42) the file. @@ -570,12 +570,12 @@ This command is used to temporarily edit an attachment's content type to fix, for instance, bogus character set parameters. When invoked from the index or from the pager, you'll have the opportunity to edit the top-level attachment's - content type. On the _a_t_t_a_c_h_m_e_n_t _m_e_n_u (section 5.1.2 , page 67), you can + content type. On the _a_t_t_a_c_h_m_e_n_t _m_e_n_u (section 5.1.2 , page 68), 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 68). There, it's used to fine-tune the properties of attachments you are going to send. eenntteerr--ccoommmmaanndd @@ -604,8 +604,8 @@ 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 101) configuration variable is set. + page 33) 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.89 , page 106) 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 130), _$_p_i_p_e___s_p_l_i_t - (section 6.4.202 , page 130), _$_p_i_p_e___s_e_p (section 6.4.201 , page 130) and - _$_w_a_i_t___k_e_y (section 6.4.335 , page 162) control the exact behavior of this + it. The variables _$_p_i_p_e___d_e_c_o_d_e (section 7.4.202 , page 135), _$_p_i_p_e___s_p_l_i_t + (section 7.4.204 , page 135), _$_p_i_p_e___s_e_p (section 7.4.203 , page 135) and + _$_w_a_i_t___k_e_y (section 7.4.337 , page 168) control the exact behavior of this function. rreesseenndd--mmeessssaaggee @@ -625,7 +625,7 @@ message. This function is best described as "recall from arbitrary folders". It can conveniently be used to forward MIME messages while preserving the orig- inal mail structure. Note that the amount of headers included here depends on - the value of the _$_w_e_e_d (section 6.4.336 , page 163) variable. + the value of the _$_w_e_e_d (section 7.4.338 , page 168) variable. This function is also available from the attachment menu. You can use this to easily resend a message which was included with a bounce message as a mes- @@ -635,14 +635,14 @@ (default: !) Asks for an external Unix command and executes it. The _$_w_a_i_t___k_e_y (section - 6.4.335 , page 162) can be used to control whether Mutt-ng will wait for a key + 7.4.337 , page 168) 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 135) variable to + The _p_a_g_e_r uses the _$_q_u_o_t_e___r_e_g_e_x_p (section 7.4.227 , page 140) variable to detect quoted text when displaying the body of the message. This function tog- gles the display of the quoted material in the message. It is particularly useful when are interested in just the response and there is a large amount of @@ -755,7 +755,7 @@ sages from. You can now tag messages in that folder and they will be attached to the message you are sending. Note that certain operations like composing a new mail, replying, forwarding, etc. are not permitted when you are in that - folder. The %r in _$_s_t_a_t_u_s___f_o_r_m_a_t (section 6.4.308 , page 155) will change to a + folder. The %r in _$_s_t_a_t_u_s___f_o_r_m_a_t (section 7.4.310 , page 160) 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 93). + Also see _e_d_i_t___h_e_a_d_e_r_s (section 7.4.55 , page 98). _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 128) permanently. + _$_p_g_p___s_i_g_n___a_s (section 7.4.194 , page 133) 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 125)) have obvious meanings. But some explana- + _m_a_t (section 7.4.181 , page 130)) 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 114)). 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.141 , + page 119)). 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 133) variable. This means that you can + the _$_p_o_s_t_p_o_n_e_d (section 7.4.216 , page 138) 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 133) quad-option. + See also the _$_p_o_s_t_p_o_n_e (section 7.4.215 , page 138) 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 79) option is specified. This file is typically /usr/local/share/muttng/Muttngrc or /etc/Muttngrc, Mutt-ng users will find this file in /usr/local/share/muttng/Muttrc or /etc/Muttngrc. Mutt will next look for a file named .muttrc in your home directory, Mutt-ng @@ -1037,12 +1037,12 @@ has a subdirectory named .mutt, mutt try to load a file named .muttng/muttngrc. .muttrc (or .muttngrc for Mutt-ng) is the file where you will usually place - your _c_o_m_m_a_n_d_s (section 6.3 , page 79) to configure Mutt-ng. + your _c_o_m_m_a_n_d_s (section 7.3 , page 82) 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 - An initialization file consists of a series of _c_o_m_m_a_n_d_s (section 6.3 , page - 79). Each line of the file may contain one or more commands. When multiple + An initialization file consists of a series of _c_o_m_m_a_n_d_s (section 7.3 , page + 82). 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- @@ -1120,7 +1120,7 @@ set record=+sent_on_$HOSTNAME The commands understood by mutt are explained in the next paragraphs. For a - complete list, see the _c_o_m_m_a_n_d _r_e_f_e_r_e_n_c_e (section 6.3 , page 79). + complete list, see the _c_o_m_m_a_n_d _r_e_f_e_r_e_n_c_e (section 7.3 , page 82). _3_._3 _D_e_f_i_n_i_n_g_/_U_s_i_n_g _a_l_i_a_s_e_s @@ -1146,7 +1146,7 @@ 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 81) + only one file, the one pointed to by the _$_a_l_i_a_s___f_i_l_e (section 7.4.3 , page 86) 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 @@ -1163,7 +1163,7 @@ To use aliases, you merely use the alias at any place in mutt where mutt prompts for addresses, such as the _T_o_: or _C_c_: prompt. You can also enter aliases in your editor at the appropriate headers if you have the _$_e_d_i_t___h_e_a_d_e_r_s - (section 6.4.54 , page 93) variable set. + (section 7.4.55 , page 98) 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 @@ -1269,7 +1269,7 @@ _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 165). The special + list of functions, see the _r_e_f_e_r_e_n_c_e (section 7.5 , page 170). 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 @@ -1299,8 +1299,8 @@ mailboxes to execute _c_o_m_m_a_n_d before loading. If a mailbox matches multiple folder-hook's, they are executed in the order given in the muttrc. - NNoottee:: if you use the ``!'' shortcut for _$_s_p_o_o_l_f_i_l_e (section 6.4.297 , page - 152) 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.299 , page + 158) 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. @@ -1336,7 +1336,7 @@ 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 165). + 7.5 , page 170). 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 @@ -1390,7 +1390,7 @@ +o normal - +o quoted (text matching _$_q_u_o_t_e___r_e_g_e_x_p (section 6.4.225 , page 135) in the + +o quoted (text matching _$_q_u_o_t_e___r_e_g_e_x_p (section 7.4.227 , page 140) in the body of a message) +o quoted1, quoted2, ..., quotedNN (higher levels of quoting) @@ -1517,7 +1517,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 137).) + _$_r_e_p_l_y___t_o (section 7.4.235 , page 142).) 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 @@ -1538,6 +1538,8 @@ _3_._1_1 _F_o_r_m_a_t _= _F_l_o_w_e_d + _3_._1_1_._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- playing them on fixed-size terminals. But times changed, and nowadays hardly @@ -1551,65 +1553,99 @@ For introductory information on format=flowed messages, see . + _3_._1_1_._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. If your terminal is so wide that the lines are embarrassingly long, you can also set a maximum line length: - set max_line_length = 120 + set max_line_length = 120 The example above will give you lines not longer than 120 characters. When you view at format=flowed messages, you will often see the quoting hierar- chy like in the following example: - >Bill, can you please send last month's progress report to Mr. - >Morgan? We also urgently need the cost estimation for the new - >production server that we want to set up before our customer's - >project will go live. + >Bill, can you please send last month's progress report to Mr. + >Morgan? We also urgently need the cost estimation for the new + >production server that we want to set up before our customer's + >project will go live. This obviously doesn't look very nice, and it makes it very hard to differenti- ate between text and quoting character. The solution is to configure mutt-ng to "stuff" the quoting: - set stuff_quoted + set stuff_quoted This will lead to a nicer result that is easier to read: - > Bill, can you please send last month's progress report to Mr. - > Morgan? We also urgently need the cost estimation for the new - > production server that we want to set up before our customer's - > project will go live. + > Bill, can you please send last month's progress report to Mr. + > Morgan? We also urgently need the cost estimation for the new + > production server that we want to set up before our customer's + > project will go live. + + _3_._1_1_._3 _S_e_n_d_i_n_g If you want mutt-ng to send emails with format=flowed set, you need to explic- itly set it: - set text_flowed + set text_flowed + + The Mutt Next Generation E-Mail Client 33 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_1_._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.47 , page 96) variable pro- + vides the mechanism to generate a DelSp=yes parameter on _o_u_t_g_o_i_n_g messages. + According to the standard, clients receiving a format=flowed messages should + delete the last space of a flowed line but still interpret the line as flowed. + Because flowed lines usually contain only one space at the end, this parameter + would make the receiving client concatenate the last word of the previous with + the first of the current line _w_i_t_h_o_u_t a space. This makes ordinary text unread- + able and is intended for languages rarely using spaces. So please use this set- + ting only if you're sure what you're doing. + + _3_._1_2 _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 58). In order to take advantage of them, you must specify which addresses belong to mailing lists, and which mailing lists you are subscribed to. Once you have done this, the _l_i_s_t_-_r_e_p_l_y (section 2.5.4 , page 12) function will work for all known lists. Additionally, when you send a message to a sub- @@ -1618,9 +1654,11 @@ the Mail-Followup-To header is a non-standard extension which is not supported by all mail user agents. Adding it is not bullet-proof against receiving per- sonal CCs of list messages. Also note that the generation of the Mail-Fol- - lowup-To header is controlled by the _$_f_o_l_l_o_w_u_p___t_o (section 6.4.66 , page 96) + lowup-To header is controlled by the _$_f_o_l_l_o_w_u_p___t_o (section 7.4.67 , page 101) configuration variable. + The Mutt Next Generation E-Mail Client 34 + More precisely, Mutt-ng maintains lists of patterns for the addresses of known and subscribed mailing lists. Every subscribed mailing list is known. To mark a mailing list as known, use the ``lists'' command. To mark it as subscribed, @@ -1656,8 +1694,6 @@ 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). @@ -1673,6 +1709,9 @@ Pressing TAB in the directory browser will bring up a menu showing the files specified by the mailboxes command, and indicate which contain new messages. + + The Mutt Next Generation E-Mail Client 35 + Mutt-ng will automatically enter this mode when invoked from the command line with the -y option. @@ -1687,9 +1726,9 @@ 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 95) and _$_s_p_o_o_l_f_i_l_e (section - 6.4.297 , page 152)) should be executed before the mailboxes command. + 57) (such as ``='' and ``!''), any variable definition that affect these char- + acters (like _$_f_o_l_d_e_r (section 7.4.65 , page 100) and _$_s_p_o_o_l_f_i_l_e (section + 7.4.299 , page 158)) 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 @@ -1707,8 +1746,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 +1753,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 93) variable, or use the _e_d_i_t_- + set the _e_d_i_t___h_e_a_d_e_r_s (section 7.4.55 , page 98) variable, or use the _e_d_i_t_- _h_e_a_d_e_r_s function (default: ``E'') in the send-menu so that you can edit the header of your message along with the body. @@ -1725,6 +1762,8 @@ remove. For example, to remove all ``To'' and ``Cc'' header fields, you could use: + The Mutt Next Generation E-Mail Client 36 + 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 @@ -1748,15 +1787,12 @@ 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 54) 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. @@ -1766,12 +1802,14 @@ 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.232 , page 142). 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.232 , page 142) mailbox. + + The Mutt Next Generation E-Mail Client 37 - 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 54) for information on the exact format of _p_a_t_t_e_r_n. Example: fcc-hook [@.]aol\\.com$ +spammers @@ -1785,7 +1823,7 @@ 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.18 , page 36) and a _s_a_v_e_-_h_o_o_k (section 3.17 , page 36) 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 @@ -1805,27 +1843,28 @@ and _r_e_p_l_i_e_s. NNoottee:: reply-hooks are matched bbeeffoorree the send-hook, rreeggaarrddlleessss of the order specified in the users's configuration file. - The Mutt Next Generation E-Mail Client 37 - send2-hook is matched every time a message is changed, either by editing it, or by using the compose menu to change its recipients or subject. send2-hook is executed after send-hook, and can, e.g., be used to set parameters such as the - _$_s_e_n_d_m_a_i_l (section 6.4.247 , page 140) variable depending on the message's + _$_s_e_n_d_m_a_i_l (section 7.4.249 , page 146) 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 54) 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 85), _$_s_i_g_n_a_t_u_r_e (section 6.4.259 , page 143) and - _$_l_o_c_a_l_e (section 6.4.114 , page 109) variables in order to change the language - of the attributions and signatures based upon the recipients. + Another typical use for this command is to change the values of the + + The Mutt Next Generation E-Mail Client 38 + + _$_a_t_t_r_i_b_u_t_i_o_n (section 7.4.15 , page 89), _$_s_i_g_n_a_t_u_r_e (section 7.4.261 , page + 149) and _$_l_o_c_a_l_e (section 7.4.115 , page 114) variables in order to change the + language of the attributions and signatures based upon the recipients. NNoottee:: the send-hook's are only executed ONCE after getting the initial list of recipients. Adding a recipient after replying or editing the message will NOT @@ -1843,7 +1882,7 @@ tiple matches occur, commands are executed in the order they are specified in the muttrc. - See _M_e_s_s_a_g_e _M_a_t_c_h_i_n_g _i_n _H_o_o_k_s (section 4.5.1 , page 53) for information on the + See _M_e_s_s_a_g_e _M_a_t_c_h_i_n_g _i_n _H_o_o_k_s (section 4.5.1 , page 54) for information on the exact format of _p_a_t_t_e_r_n. Example: @@ -1855,15 +1894,12 @@ Usage: crypt-hook _p_a_t_t_e_r_n _k_e_y_i_d - When encrypting messages with PGP or OpenSSL, you may want to associate a - - The Mutt Next Generation E-Mail Client 38 - - certain key with a given e-mail address automatically, either because the - recipient's public key can't be deduced from the destination address, or - because, for some reasons, you need to override the key Mutt-ng would normally - use. The crypt-hook command provides a method by which you can specify the ID - of the public key to be used when encrypting messages to a certain recipient. + When encrypting messages with PGP or OpenSSL, you may want to associate a cer- + tain key with a given e-mail address automatically, either because the recipi- + ent's public key can't be deduced from the destination address, or because, for + some reasons, you need to override the key Mutt-ng would normally use. The + crypt-hook command provides a method by which you can specify the ID of the + public key to be used when encrypting messages to a certain recipient. The meaning of "key id" is to be taken broadly in this context: You can either put a numerical key ID here, an e-mail address, or even just a real name. @@ -1872,17 +1908,21 @@ Usage: push _s_t_r_i_n_g - This command adds the named string to the keyboard buffer. The string may con- - tain control characters, key names and function names like the sequence string - in the _m_a_c_r_o (section 3.7 , page 27) command. You may use it to automatically - run a sequence of commands at startup, or when entering certain folders. + This command adds the named string to the keyboard buffer. The string may + + The Mutt Next Generation E-Mail Client 39 + + contain 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 auto- + matically run a sequence of commands at startup, or when entering certain fold- + ers. _3_._2_4 _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 165). ``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 170). ``exec function'' is equivalent to ``push ''. _3_._2_5 _M_e_s_s_a_g_e _S_c_o_r_i_n_g @@ -1905,8 +1945,6 @@ score "~f nion@muttng\.org" 50 score "~f @sco\.com" -100 - The Mutt Next Generation E-Mail Client 39 - If the pattern matches, it is also possible to set the score value of the cur- rent message to a certain value and then stop evaluation: @@ -1921,6 +1959,8 @@ +o flag threshold: when a message has a score value equal or higher than the flag threshold, it will be flagged. + The Mutt Next Generation E-Mail Client 40 + +o read threshold: when a message has a score value equal or lower than the read threshold, it will be marked as read. @@ -1928,10 +1968,10 @@ 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 140), _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___r_e_a_d (section 6.4.245 , page 140), - _$_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 140) 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 140) 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 140) are set to -1, which means that in the default + tion 7.4.246 , page 145), _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___r_e_a_d (section 7.4.247 , page 145), + _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___d_e_l_e_t_e (section 7.4.245 , page 145) and. By default, + _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___r_e_a_d (section 7.4.247 , page 145) and _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___d_e_l_e_t_e + (section 7.4.245 , page 145) 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 @@ -1955,10 +1995,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 106) variable. + the %H selector in the _$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.111 , page 111) variable. (Tip: try %?H?[%H] ? to display spam tags only when they are defined for a given message.) @@ -1974,6 +2011,9 @@ with the second, etc. If you're using multiple spam filters, a message can have more than one spam- + + The Mutt Next Generation E-Mail Client 41 + related header. You can define spam patterns for each filter you use. If a mes- sage matches two or more of these patterns, and the $spam_separator variable is set to a string, then the message's spam tag will consist of all the _f_o_r_m_a_t @@ -2011,9 +2051,6 @@ mutt will sort numerically first, and lexically only when two numbers are equal in value. (This is like UNIX's sort -n.) A message with no spam attributes at all -- that is, one that didn't match _a_n_y of your spam patterns -- is sorted at - - The Mutt Next Generation E-Mail Client 41 - lowest priority. Numbers are sorted next, beginning with 0 and ranging upward. Finally, non-numeric strings are sorted, with ``a'' taking lower priority than ``z''. Clearly, in general, sorting by spam tags is most effective when you can @@ -2030,6 +2067,9 @@ instead of adding an exception. Likewise, if the _p_a_t_t_e_r_n for a spam command matches an entry on the nospam list, that nospam entry will be removed. If the _p_a_t_t_e_r_n for nospam is ``*'', _a_l_l _e_n_t_r_i_e_s _o_n _b_o_t_h _l_i_s_t_s will be removed. This + + The Mutt Next Generation E-Mail Client 42 + might be the default action if you use spam and nospam in conjunction with a folder-hook. @@ -2049,8 +2089,8 @@ Usage: reset _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ] - This command is used to set (and unset) _c_o_n_f_i_g_u_r_a_t_i_o_n _v_a_r_i_a_b_l_e_s (section 6.4 , - page 81). There are four basic types of variables: boolean, number, string and + This command is used to set (and unset) _c_o_n_f_i_g_u_r_a_t_i_o_n _v_a_r_i_a_b_l_e_s (section 7.4 , + page 84). There are four basic types of variables: boolean, number, string and quadoption. _b_o_o_l_e_a_n variables can be _s_e_t (true) or _u_n_s_e_t (false). _n_u_m_b_e_r variables can be assigned a positive integer value. @@ -2065,8 +2105,6 @@ if you had answered ``no.'' A value of _a_s_k_-_y_e_s will cause a prompt with a default answer of ``yes'' and _a_s_k_-_n_o will provide a default answer of ``no.'' - The Mutt Next Generation E-Mail Client 42 - Prefixing a variable with ``no'' will unset it. Example: set noaskbcc. For _b_o_o_l_e_a_n variables, you may optionally prefix the variable name with inv to @@ -2082,6 +2120,8 @@ Using the enter-command function in the _i_n_d_e_x menu, you can query the value of a variable by prefixing the name of the variable with a question mark: + The Mutt Next Generation E-Mail Client 43 + set ?allow_8bit The question mark is actually only required for boolean and quadoption vari- @@ -2115,9 +2155,6 @@ 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 @@ -2132,6 +2169,9 @@ specify in which character set their configuration files are encoded. Please note that while reading the configuration files, this is only respected after the corresponding declaration appears. It's advised to put the following at the + + The Mutt Next Generation E-Mail Client 44 + very beginning of a users muttngrc: set config_charset = "..." @@ -2161,8 +2201,6 @@ To solve this, mutt-ng contain a feature based on the ``ifdef'' patch written for mutt. Its basic syntax is: - The Mutt Next Generation E-Mail Client 44 - ifdef ifndef @@ -2178,6 +2216,9 @@ All available functions, variables and menus are documented elsewhere in this manual but ``features'' is specific to these two commands. To test for one, + + The Mutt Next Generation E-Mail Client 45 + prefix one of the following keywords with feature_: ncurses, slang, iconv, idn, dotlock, standalone, pop, nntp, imap, ssl, @@ -2196,21 +2237,18 @@ An example for testing for variable names can be used if users use different revisions of mutt-ng whereby the older one may not have a certain variable. To - test for the availability of _$_i_m_a_p___m_a_i_l___c_h_e_c_k (section 6.4.99 , page 104), + test for the availability of _$_i_m_a_p___m_a_i_l___c_h_e_c_k (section 7.4.100 , page 109), 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.171 , page 128) only if the pager menu is available, use: ifdef pager 'set pager_index_lines = 10' For completeness, too, the opposite of ifdef is provided: ifndef which only executes the command if the test fails. For example, the following two examples - - The Mutt Next Generation E-Mail Client 45 - are equivalent: ifdef feature_ncurses 'source ~/.mutt-ng/setup-ncurses' @@ -2221,12 +2259,20 @@ ifdef feature_slang 'source ~/.mutt-ng/setup-slang' ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' + The Mutt Next Generation E-Mail Client 46 + + _3_._3_1 _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 84) 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 80) 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. @@ -2254,8 +2300,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 @@ -2266,6 +2310,8 @@ place it anywhere but first. Finally, to include a literal hyphen ``-'' place it last. + The Mutt Next Generation E-Mail Client 47 + Certain named classes of characters are predefined. Character classes consist of ``[:'', a keyword denoting the class, and ``:]''. The following classes are defined by the POSIX standard: @@ -2310,9 +2356,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]]. @@ -2323,6 +2366,9 @@ Collating Symbols A collating symbol is a multi-character collating element enclosed + + The Mutt Next Generation E-Mail Client 48 + in ``[.'' and ``.]''. For example, if ``ch'' is a collating ele- ment, then [[[[..cchh..]]]] is a regexp that matches this collating ele- ment, while [[cchh]] is a regexp that matches either ``c'' or ``h''. @@ -2367,9 +2413,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. @@ -2380,6 +2423,8 @@ Matches the empty string at either the beginning or the end of a word. + The Mutt Next Generation E-Mail Client 49 + \\B Matches the empty string within a word. @@ -2411,7 +2456,7 @@ to match messages, e.g. for operations like tagging and scoring. A pattern con- sists of one or more sub-pattern, which can be logically grouped, ORed, and negated. For a complete listing of these patterns, please refer to table _P_a_t_- - _t_e_r_n_s (section 6.2 , page 77) in the Reference chapter. + _t_e_r_n_s (section 7.2 , page 80) 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 +2468,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 @@ -2433,6 +2476,8 @@ To logical OR patterns, simply use the | operator. This one especially useful when using local groups: + The Mutt Next Generation E-Mail Client 50 + ~f ("nion@muttng\.org"|"ak@muttng\.org"|"pdmef@muttng\.org") (~b mutt-ng|~s Mutt-ng) !~x '@synflood\.at' @@ -2472,8 +2517,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 @@ -2482,6 +2525,8 @@ _4_._3_._1 _I_n_t_r_o_d_u_c_t_i_o_n + The Mutt Next Generation E-Mail Client 51 + The so called _F_o_r_m_a_t _S_t_r_i_n_g_s offer great flexibility when configuring mutt-ng. In short, they describe what items to print out how in menus and status mes- sages. @@ -2498,7 +2543,7 @@ +o the current mutt-ng version number The setting for the status bar of the index is controlled via the _$_s_t_a_t_u_s___f_o_r_- - _m_a_t (section 6.4.308 , page 155) variable. For the hostname and version + _m_a_t (section 7.4.310 , page 160) 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: @@ -2520,8 +2565,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: @@ -2530,6 +2573,9 @@ For the number of certain types of messages, one more feature of the format strings is extremely useful. If there aren't messages of a certain type, it may + + The Mutt Next Generation E-Mail Client 52 + not be desired to print just that there aren't any but instead only print some- thing if there are any. @@ -2565,8 +2611,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? ... @@ -2576,6 +2620,8 @@ set status_format = "%v on %h: %B: %?n?%n&no? new messages ... + The Mutt Next Generation E-Mail Client 53 + As you might see from this rather simple example, one can create very complex but fancy status messages. Please see the reference chapter for expandos and those which may be printed nonzero. @@ -2612,8 +2658,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 +2666,20 @@ ject. To tag all messages matching a pattern, use the tag-pattern function, which is bound to ``shift-T'' by default. Or you can select individual mes- sages by hand using the ``tag-message'' function, which is bound to ``t'' by - default. See _p_a_t_t_e_r_n_s (section 6.2 , page 77) for Mutt-ng's pattern matching + + The Mutt Next Generation E-Mail Client 54 + + default. See _p_a_t_t_e_r_n_s (section 7.2 , page 80) 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 85) 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.16 , + page 90) 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.7 , page 27) or _p_u_s_h (section 3.23 , page 38) 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,20 +2691,20 @@ 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 45) or _p_a_t_t_e_r_n (section 7.2 , page 80) along with a configuration option/command. See +o _f_o_l_d_e_r_-_h_o_o_k (section 3.6 , page 26) - +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.20 , page 37) +o _m_e_s_s_a_g_e_-_h_o_o_k (section 3.21 , page 37) - +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.17 , page 36) - +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.13 , page 34) - +o _f_c_c_-_h_o_o_k (section 3.18 , page 35) + +o _f_c_c_-_h_o_o_k (section 3.18 , page 36) +o _f_c_c_-_s_a_v_e_-_h_o_o_k (section 3.19 , page 36) @@ -2666,23 +2713,22 @@ 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:' send-hook ~C'^b@b\.b$' my_hdr from: c@c.c + The Mutt Next Generation E-Mail Client 55 + _4_._5_._1 _M_e_s_s_a_g_e _M_a_t_c_h_i_n_g _i_n _H_o_o_k_s Hooks that act upon messages (send-hook, save-hook, fcc-hook, message-hook) are evaluated in a slightly different manner. For the other types of hooks, a _r_e_g_- - _u_l_a_r _e_x_p_r_e_s_s_i_o_n (section 4.1 , page 44) is sufficient. But in dealing with + _u_l_a_r _e_x_p_r_e_s_s_i_o_n (section 4.1 , page 45) 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 80) 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,8 +2745,8 @@ 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 91) 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 91) that is in + 7.4.45 , page 96) 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.45 , page 96) that is in effect at that time will be used. _4_._6 _U_s_i_n_g _t_h_e _s_i_d_e_b_a_r @@ -2715,8 +2761,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 \ @@ -2725,6 +2769,8 @@ You can also specify the colors for mailboxes with new mails by using: + The Mutt Next Generation E-Mail Client 56 + color sidebar_new red black color sidebar white black @@ -2756,16 +2802,13 @@ 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.223 , page 140) 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. @@ -2775,6 +2818,9 @@ Searching database ... 20 entries ... 3 matching: me@cs.hmc.edu Michael Elkins mutt dude blong@fiction.net Brandon Long mutt and more + + The Mutt Next Generation E-Mail Client 57 + roessler@guug.de Thomas Roessler mutt pgp There are two mechanisms for accessing the query function of mutt. One is to @@ -2798,7 +2844,7 @@ Mutt-ng supports reading and writing of four different mailbox formats: mbox, MMDF, MH and Maildir. The mailbox type is autodetected, so there is no need to use a flag for different mailbox types. When creating new mailboxes, Mutt-ng - uses the default specified with the _$_m_b_o_x___t_y_p_e (section 6.4.125 , page 112) + uses the default specified with the _$_m_b_o_x___t_y_p_e (section 7.4.127 , page 117) variable. mmbbooxx. This is the most widely used mailbox format for UNIX. All messages are @@ -2815,9 +2861,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 @@ -2827,6 +2870,9 @@ ment for sendmail). Similar to _M_H, except that it adds three subdirectories of the mailbox: _t_m_p, _n_e_w and _c_u_r. Filenames for the messages are chosen in such a way they are unique, even when two programs are writing the mailbox over NFS, + + The Mutt Next Generation E-Mail Client 58 + which means that no file locking is needed. _4_._9 _M_a_i_l_b_o_x _S_h_o_r_t_c_u_t_s @@ -2835,12 +2881,12 @@ These shortcuts can be used anywhere you are prompted for a file or mailbox path. - +o ! -- refers to your _$_s_p_o_o_l_f_i_l_e (section 6.4.297 , page 152) (incoming) + +o ! -- refers to your _$_s_p_o_o_l_f_i_l_e (section 7.4.299 , page 158) (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.126 , page 117) 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.232 , page 142) file +o ^ -- refers to the current mailbox @@ -2848,9 +2894,9 @@ +o ~ -- refers to your home directory - +o = or + -- refers to your _$_f_o_l_d_e_r (section 6.4.64 , page 95) directory + +o = or + -- refers to your _$_f_o_l_d_e_r (section 7.4.65 , page 100) 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.17 , page 36) 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 @@ -2860,17 +2906,14 @@ 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.12 , page 33) 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 106) variable, the escape + box. In the _$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.111 , page 111) 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). @@ -2880,11 +2923,14 @@ person. The ``list-reply'' function, which by default is bound to ``L'' in the _i_n_d_e_x menu and _p_a_g_e_r, helps reduce the clutter by only replying to the known mailing list addresses instead of all recipients (except as specified by Mail- + + The Mutt Next Generation E-Mail Client 59 + Followup-To, see below). Mutt-ng also supports the Mail-Followup-To header. When you send a message to a list of recipients which includes one or several subscribed mailing lists, - and if the _$_f_o_l_l_o_w_u_p___t_o (section 6.4.66 , page 96) option is set, mutt will + and if the _$_f_o_l_l_o_w_u_p___t_o (section 7.4.67 , page 101) 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 +2940,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 101) configuration variable is set. Using list-reply + (section 7.4.89 , page 106) 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,7 +2953,7 @@ the message. This can create problems when trying to reply directly to the author in private, since most mail clients will automatically reply to the address given in the ``Reply-To'' field. Mutt-ng uses the _$_r_e_p_l_y___t_o (section - 6.4.233 , page 137) variable to help decide which address to use. If set to + 7.4.235 , page 142) 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 @@ -2915,26 +2961,26 @@ 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 106) variable's ``%y'' and ``%Y'' + _$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.111 , page 111) variable's ``%y'' and ``%Y'' escapes can be used to expand ``X-Label:'' fields in the index, and Mutt-ng's pattern-matcher can match regular expressions to ``X-Label:'' fields with the ``~y'' selector. ``X-Label:'' is not a standard message header field, but it can easily be inserted by procmail and other mail filtering agents. - Lastly, Mutt-ng has the ability to _s_o_r_t (section 6.4.291 , page 150) the mail- + Lastly, Mutt-ng has the ability to _s_o_r_t (section 7.4.293 , page 156) 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 Mutt-ng has the ability to dynamically restructure threads that are broken + + The Mutt Next Generation E-Mail Client 60 + either by misconfigured software or bad behavior from some correspondents. This allows to clean your mailboxes formats) from these annoyances which make it hard to follow a discussion. @@ -2975,18 +3021,18 @@ To support this, there are two variables: - +o _$_d_s_n___n_o_t_i_f_y (section 6.4.51 , page 92) is used to request receipts for + +o _$_d_s_n___n_o_t_i_f_y (section 7.4.52 , page 97) is used to request receipts for different results (such as failed message, message delivered, etc.). - The Mutt Next Generation E-Mail Client 60 - - +o _$_d_s_n___r_e_t_u_r_n (section 6.4.52 , page 93) requests how much of your message + +o _$_d_s_n___r_e_t_u_r_n (section 7.4.53 , page 97) requests how much of your message should be returned with the receipt (headers or full message). Please see the reference chapter for possible values. _4_._1_3 _P_O_P_3 _S_u_p_p_o_r_t _(_O_P_T_I_O_N_A_L_) + The Mutt Next Generation E-Mail Client 61 + 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. @@ -3002,7 +3048,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 132) variable, which defaults + by the _$_p_o_p___m_a_i_l___c_h_e_c_k (section 7.4.210 , page 137) 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 @@ -3012,8 +3058,8 @@ name@]popserver[:port]/. Another way to access your POP3 mail is the _f_e_t_c_h_-_m_a_i_l function (default: G). - It allows to connect to _p_o_p___h_o_s_t (section 6.4.206 , page 131), fetch all your - new mail and place it in the local _s_p_o_o_l_f_i_l_e (section 6.4.297 , page 152). + It allows to connect to _p_o_p___h_o_s_t (section 7.4.208 , page 136), fetch all your + new mail and place it in the local _s_p_o_o_l_f_i_l_e (section 7.4.299 , page 158). 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- @@ -3030,9 +3076,6 @@ INBOX is the special name for your spool mailbox on the IMAP server. If you want to access another mail folder at the IMAP server, you should use imap://imapserver/path/to/folder where path/to/folder is the path of the folder - - The Mutt Next Generation E-Mail Client 61 - you want to access. You can select an alternative port by specifying it with the server, i.e.: @@ -3042,6 +3085,9 @@ name@imapserver[:port]/INBOX. If Mutt-ng was compiled with SSL support (by running the _c_o_n_f_i_g_u_r_e script with + + The Mutt Next Generation E-Mail Client 62 + 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- @@ -3056,12 +3102,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 103) vari- + 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.98 , page 108) vari- able. 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 104) and - _$_t_i_m_e_o_u_t (section 6.4.321 , page 160) variables. + want to carefully tune the _$_i_m_a_p___m_a_i_l___c_h_e_c_k (section 7.4.100 , page 109) and + _$_t_i_m_e_o_u_t (section 7.4.323 , page 165) 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 @@ -3087,8 +3133,6 @@ respectively). You may also subscribe and unsubscribe to mailboxes (nor- mally these are bound to s and u, respectively). - The Mutt Next Generation E-Mail Client 62 - _4_._1_4_._2 _A_u_t_h_e_n_t_i_c_a_t_i_o_n Mutt-ng supports four authentication methods with IMAP servers: SASL, GSSAPI, @@ -3098,6 +3142,8 @@ which allows you to log in to a public IMAP server without having an account. To use ANONYMOUS, simply make your username blank or "anonymous". + The Mutt Next Generation E-Mail Client 63 + SASL is a special super-authenticator, which selects among several protocols (including GSSAPI, CRAM-MD5, ANONYMOUS, and DIGEST-MD5) the most secure method available on your host and the server. Using some of these methods (including @@ -3111,15 +3157,15 @@ There are a few variables which control authentication: - +o _$_i_m_a_p___u_s_e_r (section 6.4.105 , page 105) - controls the username under + +o _$_i_m_a_p___u_s_e_r (section 7.4.106 , page 110) - 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 104) - a password which you may pre- + +o _$_i_m_a_p___p_a_s_s (section 7.4.101 , page 109) - 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 102) - 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.92 , page 107) - 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). @@ -3132,7 +3178,7 @@ 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. + file as specified by the _$_n_n_t_p___n_e_w_s_r_c (section 7.4.158 , page 125) 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. @@ -3141,9 +3187,6 @@ Especially for Usenet, people often ask for advanced filtering and scoring functionality. Of course, mutt-ng has scoring and allows a killfile, too. How - - The Mutt Next Generation E-Mail Client 63 - 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). @@ -3154,6 +3197,8 @@ In mutt-ng this is as easy as + The Mutt Next Generation E-Mail Client 64 + score ~* =42 This tells mutt-ng to apply a score of 42 to all messages whose sender speci- @@ -3181,29 +3226,30 @@ 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 58) section) as well as handling the 8BIT- - MIME flag controlled via _$_u_s_e___8_b_i_t_m_i_m_e (section 6.4.328 , page 161). + _N_o_t_i_f_i_c_a_t_i_o_n (section 4.12 , page 59) section) as well as handling the 8BIT- + MIME flag controlled via _$_u_s_e___8_b_i_t_m_i_m_e (section 7.4.330 , page 166). To enable sending mail directly via SMTP without an MTA such as Postfix or - SSMTP and the like, simply set the _$_s_m_t_p___h_o_s_t (section 6.4.286 , page 149) + SSMTP and the like, simply set the _$_s_m_t_p___h_o_s_t (section 7.4.288 , page 154) variable pointing to your SMTP server. - The Mutt Next Generation E-Mail Client 64 - - Authentication mechanisms are available via the _$_s_m_t_p___u_s_e_r (section 6.4.290 , - page 150) and _$_s_m_t_p___p_a_s_s (section 6.4.287 , page 149) variables. + Authentication mechanisms are available via the _$_s_m_t_p___u_s_e_r (section 7.4.292 , + page 155) and _$_s_m_t_p___p_a_s_s (section 7.4.289 , page 155) variables. Transport Encryption via the StartTLS command is also available. For this to work, first of all Mutt-ng must be built with SSL or GNUTLS. Secondly, the - _$_s_m_t_p___u_s_e___t_l_s (section 6.4.289 , page 150) variable must be either set to + _$_s_m_t_p___u_s_e___t_l_s (section 7.4.291 , page 155) variable must be either set to ``enabled'' or ``required.'' In both cases, StartTLS will be used if the server supports it: for the second case, the connection will fail if it doesn't while switching back to unencrypted communication for the first one. Some mail providers require user's to set a particular envelope sender, i.e. + + The Mutt Next Generation E-Mail Client 65 + they allow for only one value which may not be what the user wants to send as - the From: header. In this case, the variable _$_s_m_t_p___e_n_v_e_l_o_p_e (section 6.4.285 , - page 149) may be used to set the envelope different from the From: header. + the From: header. In this case, the variable _$_s_m_t_p___e_n_v_e_l_o_p_e (section 7.4.287 , + page 154) 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_) @@ -3237,8 +3283,6 @@ an arbitrary format, provided that the user has a script to convert from/to this format to one of the accepted. - The Mutt Next Generation E-Mail Client 65 - The most common use is to open compressed archived folders e.g. with gzip. In addition, the user can provide a script that gets a folder in an accepted @@ -3246,11 +3290,13 @@ may be faster than converting the entire folder to the accepted format, append- ing to it and converting back to the user-defined format. - There are three hooks defined (_o_p_e_n_-_h_o_o_k (section 4.19.1 , page 64), _c_l_o_s_e_- - _h_o_o_k (section 4.19.2 , page 65) and _a_p_p_e_n_d_-_h_o_o_k (section 4.19.3 , page 65)) + There are three hooks defined (_o_p_e_n_-_h_o_o_k (section 4.19.1 , page 65), _c_l_o_s_e_- + _h_o_o_k (section 4.19.2 , page 66) and _a_p_p_e_n_d_-_h_o_o_k (section 4.19.3 , page 66)) which define commands to uncompress and compress a folder and to append mes- sages to an existing compressed folder respectively. + The Mutt Next Generation E-Mail Client 66 + For example: open-hook \\.gz$ "gzip -cd %f > %t" @@ -3258,17 +3304,17 @@ append-hook \\.gz$ "gzip -c %t >> %f" You do not have to specify all of the commands. If you omit _a_p_p_e_n_d_-_h_o_o_k (sec- - tion 4.19.3 , page 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.19.2 , page 65) (or give + tion 4.19.3 , page 66), the folder will be open and closed again each time you + will add to it. If you omit _c_l_o_s_e_-_h_o_o_k (section 4.19.2 , page 66) (or give empty command) , the folder will be open in the mode. If you specify _a_p_p_e_n_d_- - _h_o_o_k (section 4.19.3 , page 65) though you'll be able to append to the folder. + _h_o_o_k (section 4.19.3 , page 66) 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 139), so that the compressed file + unset _$_s_a_v_e___e_m_p_t_y (section 7.4.242 , page 144), so that the compressed file will be removed if you delete all of the messages. _4_._1_9_._1 _O_p_e_n _a _c_o_m_p_r_e_s_s_e_d _m_a_i_l_b_o_x _f_o_r _r_e_a_d_i_n_g @@ -3291,8 +3337,6 @@ Example: - The Mutt Next Generation E-Mail Client 66 - open-hook \\.gz$ "gzip -cd %f > %t" If the _c_o_m_m_a_n_d is empty, this operation is disabled for this file type. @@ -3302,12 +3346,14 @@ Usage: close-hook _r_e_g_e_x_p '_c_o_m_m_a_n_d' This is used to close the folder that was open with the _o_p_e_n_-_h_o_o_k (section - 4.19.1 , page 64) command after some changes were made to it. + 4.19.1 , page 65) command after some changes were made to it. + + The Mutt Next Generation E-Mail Client 67 The _c_o_m_m_a_n_d string is the command that can be used for closing the folders whose names match _r_e_g_e_x_p. It has the same format as in the _o_p_e_n_-_h_o_o_k (section - 4.19.1 , page 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.19.1 , page 64) command. + 4.19.1 , page 65) command. Temporary folder in this case is the folder previ- + ously produced by the <_o_p_e_n_-_h_o_o_k (section 4.19.1 , page 65) command. 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. @@ -3319,7 +3365,7 @@ If the _c_o_m_m_a_n_d is empty, this operation is disabled for this file type, and the file can only be open in the readonly mode. - _c_l_o_s_e_-_h_o_o_k (section 4.19.2 , page 65) is not called when you exit from the + _c_l_o_s_e_-_h_o_o_k (section 4.19.2 , page 66) is not called when you exit from the folder if the folder was not changed. _4_._1_9_._3 _A_p_p_e_n_d _a _m_e_s_s_a_g_e _t_o _a _c_o_m_p_r_e_s_s_e_d _m_a_i_l_b_o_x @@ -3328,7 +3374,7 @@ This command is used for saving to an existing compressed folder. The _c_o_m_m_a_n_d is the command that can be used for appending to the folders whose names match - _r_e_g_e_x_p. It has the same format as in the _o_p_e_n_-_h_o_o_k (section 4.19.1 , page 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 65) command. The temporary folder in this case contains the messages that are being appended. @@ -3339,23 +3385,22 @@ append-hook \\.gz$ "gzip -c %t >> %f" - When _a_p_p_e_n_d_-_h_o_o_k (section 4.19.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 66) 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 112)) type is always - - The Mutt Next Generation E-Mail Client 67 - + is. Thus the default (_$_m_b_o_x___t_y_p_e (section 7.4.127 , page 117)) type is always supposed (i.e. this is the format used for the temporary folder). If the file does not exist when you save to it, _c_l_o_s_e_-_h_o_o_k (section 4.19.2 , - page 65) is called, and not _a_p_p_e_n_d_-_h_o_o_k (section 4.19.3 , page 65). _a_p_p_e_n_d_- - _h_o_o_k (section 4.19.3 , page 65) is only for appending to existing folders. + page 66) is called, and not _a_p_p_e_n_d_-_h_o_o_k (section 4.19.3 , page 66). _a_p_p_e_n_d_- + _h_o_o_k (section 4.19.3 , page 66) is only for appending to existing folders. If the _c_o_m_m_a_n_d is empty, this operation is disabled for this file type. In this case, the folder will be open and closed again (using _o_p_e_n_-_h_o_o_k (section - 4.19.1 , page 64) and _c_l_o_s_e_-_h_o_o_k (section 4.19.2 , page 65)respectively) each + 4.19.1 , page 65) and _c_l_o_s_e_-_h_o_o_k (section 4.19.2 , page 66)respectively) each time you will add to it. + The Mutt Next Generation E-Mail Client 68 + _4_._1_9_._4 _E_n_c_r_y_p_t_e_d _f_o_l_d_e_r_s The compressed folders support can also be used to handle encrypted folders. If @@ -3392,9 +3437,6 @@ the message to a text representation. Mutt-ng internally supports a number of MIME types, including text/plain, text/enriched, message/rfc822, and mes- sage/news. In addition, the export controlled version of Mutt-ng recognizes a - - The Mutt Next Generation E-Mail Client 68 - variety of PGP MIME types, including PGP/MIME and application/pgp. Mutt-ng will denote attachments with a couple lines describing them. These @@ -3406,6 +3448,8 @@ Where the Description is the description or filename given for the attachment, and the Encoding is one of 7bit/8bit/quoted-printable/base64/binary. + The Mutt Next Generation E-Mail Client 69 + If Mutt-ng cannot deal with a MIME type, it will display a message like: [-- image/gif is unsupported (use 'v' to view this part) --] @@ -3446,9 +3490,6 @@ 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 the edit-type command (default: ^T). The next field is the encoding for the - - The Mutt Next Generation E-Mail Client 69 - attachment, which allows a binary message to be encoded for transmission on 7bit links. It can be changed with the edit-encoding command (default: ^E). The next field is the size of the attachment, rounded to kilobytes or @@ -3459,6 +3500,9 @@ _5_._2 _M_I_M_E _T_y_p_e _c_o_n_f_i_g_u_r_a_t_i_o_n _w_i_t_h _m_i_m_e_._t_y_p_e_s When you add an attachment to your mail message, Mutt-ng searches your personal + + The Mutt Next Generation E-Mail Client 70 + mime.types file at ${HOME}/.mime.types, and then the system mime.types file at /usr/local/share/mutt/mime.types or /etc/mime.types @@ -3498,9 +3542,6 @@ In order to handle various MIME types that Mutt-ng can not handle internally, Mutt-ng parses a series of external configuration files to find an external - - The Mutt Next Generation E-Mail Client 70 - handler. The default search string for these files is a colon delimited list set to @@ -3511,6 +3552,8 @@ In particular, the metamail distribution will install a mailcap file, usually as /usr/local/etc/mailcap, which contains some baseline entries. + The Mutt Next Generation E-Mail Client 71 + _5_._3_._1 _T_h_e _B_a_s_i_c_s _o_f _t_h_e _m_a_i_l_c_a_p _f_i_l_e A mailcap file consists of a series of lines which are comments, blank, or def- @@ -3553,8 +3596,6 @@ text/html; lynx %s - The Mutt Next Generation E-Mail Client 71 - In this case, lynx does not support viewing a file from stdin, so you must use the %s syntax. NNoottee:: _S_o_m_e _o_l_d_e_r _v_e_r_s_i_o_n_s _o_f _l_y_n_x _c_o_n_t_a_i_n _a _b_u_g _w_h_e_r_e _t_h_e_y _w_i_l_l _c_h_e_c_k _t_h_e _m_a_i_l_c_a_p _f_i_l_e _f_o_r _a _v_i_e_w_e_r _f_o_r _t_e_x_t_/_h_t_m_l_. _T_h_e_y _w_i_l_l _f_i_n_d _t_h_e _l_i_n_e @@ -3564,6 +3605,8 @@ On the other hand, maybe you don't want to use lynx interactively, you just want to have it convert the text/html to text/plain, then you can use: + The Mutt Next Generation E-Mail Client 72 + text/html; lynx -dump %s | more Perhaps you wish to use lynx to view text/html files, and a pager on all other @@ -3579,7 +3622,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 110) variable. + them, see the _m_a_i_l_c_a_p___s_a_n_i_t_i_z_e (section 7.4.118 , page 115) variable. Although mutt's procedures to invoke programs with mailcap seem to be safe, there are other applications parsing mailcap, maybe taking less care of it. @@ -3605,8 +3648,6 @@ _5_._3_._3_._1 _O_p_t_i_o_n_a_l _F_i_e_l_d_s - The Mutt Next Generation E-Mail Client 72 - In addition to the required content-type and view command fields, you can add semi-colon ';' separated fields to set flags and other options. Mutt-ng recog- nizes the following optional fields: @@ -3616,6 +3657,9 @@ amounts of text on stdout. This causes Mutt-ng to invoke a pager (either the internal pager or the external pager defined by the pager variable) on the output of the view command. Without this + + The Mutt Next Generation E-Mail Client 73 + flag, Mutt-ng assumes that the command is interactive. One could use this to replace the pipe to more in the lynx -dump example in the Basic section: @@ -3627,11 +3671,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.335 , page 162) variable + tion 5.4 , page 75), in order to decide whether it should honor + the setting of the _$_w_a_i_t___k_e_y (section 7.4.337 , page 168) variable or not. When an attachment is viewed using an interactive program, and the corresponding mailcap entry has a _n_e_e_d_s_t_e_r_m_i_n_a_l flag, Mutt- - ng will use _$_w_a_i_t___k_e_y (section 6.4.335 , page 162) and the exit + ng will use _$_w_a_i_t___k_e_y (section 7.4.337 , page 168) 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. @@ -3659,8 +3703,6 @@ it to compose new attachments. Mutt-ng will default to the defined editor for text attachments. - The Mutt Next Generation E-Mail Client 73 - nametemplate=