From fa54675b6ceb98bce1a8931b7cc5b70ecedf4225 Mon Sep 17 00:00:00 2001 From: pdmef Date: Tue, 23 Aug 2005 05:00:42 +0000 Subject: [PATCH] Rocco Rutte: - update for f=f and RfC 3676: move code out to rfc3676.[ch] - update for f=f and RfC 3676: when searching for breakpoints, look for ascii space and not isspace() - update for f=f and RfC 3676: add $delete_space to generate DelSp parameter - update for f=f and RfC 3676: respect DelSp parameter git-svn-id: svn://svn.berlios.de/mutt-ng/trunk@435 e385b8ad-14ed-0310-8656-cc95a2468c6d --- Makefile.am | 5 +- UPGRADING | 4 + doc/manual.sgml.head | 174 ++- doc/manual.txt | 2779 +++++++++++++++++++++--------------------- handler.c | 177 +-- init.h | 20 + mutt.h | 1 + rfc3676.c | 245 ++++ rfc3676.h | 23 + send.c | 5 +- 10 files changed, 1834 insertions(+), 1599 deletions(-) create mode 100644 rfc3676.c create mode 100644 rfc3676.h diff --git a/Makefile.am b/Makefile.am index a71cd55..2a90349 100644 --- a/Makefile.am +++ b/Makefile.am @@ -42,7 +42,7 @@ muttng_SOURCES = $(BUILT_SOURCES) \ main.c mbox.c mbyte.c md5c.c menu.c mh.c muttlib.c mutt_idna.c mx.c \ pager.c parse.c pattern.c postpone.c \ query.c \ - recvattach.c recvcmd.c rfc822.c rfc1524.c rfc2047.c rfc2231.c \ + recvattach.c recvcmd.c rfc822.c rfc1524.c rfc2047.c rfc2231.c rfc3676.c \ score.c send.c sendlib.c sidebar.c signal.c sort.c state.c status.c system.c \ thread.c \ url.c utf8.c \ @@ -101,7 +101,8 @@ EXTRA_DIST = COPYRIGHT GPL OPS OPS.PGP OPS.CRYPT OPS.SMIME TODO \ mapping.h md5.h mime.h mutt.h mutt_curses.h mutt_menu.h \ mutt_sasl.h mutt_socket.h mutt_ssl.h mutt_tunnel.h \ mbox.h mh.h mx.h pager.h pgp.h protos.h reldate.h rfc1524.h rfc2047.h \ - rfc2231.h rfc822.h sha1.h sort.h mime.types VERSION autogen.sh \ + rfc2231.h rfc822.h rfc3676.h \ + sha1.h sort.h mime.types VERSION autogen.sh \ _regex.h OPS.MIX remailer.c remailer.h browser.h state.h \ mbyte.h lib.h extlib.c pgpewrap.c smime_keys.pl pgplib.h Muttngrc.head Muttngrc \ makedoc.c stamp-doc-rc README.SSL smime.h\ diff --git a/UPGRADING b/UPGRADING index 2f0c01f..b32ff29 100644 --- a/UPGRADING +++ b/UPGRADING @@ -10,6 +10,10 @@ This document is not the place for verbose documentation; it only offers the necessary keywords to look them up in the manual, ChangeLog or other sources of information. +2005-08-23: + + The $delete_space option has been added. + 2005-08-22: Reading configurations from ~/.muttngrc-$version and diff --git a/doc/manual.sgml.head b/doc/manual.sgml.head index df0ba2e..6689838 100644 --- a/doc/manual.sgml.head +++ b/doc/manual.sgml.head @@ -1664,82 +1664,132 @@ is ``*'', Format = Flowed -

Mutt-ng contains support for so-called For introductory information on . - -

When you receive emails that are marked as Introduction + +

Mutt-ng contains support for so-called For introductory information on . - -set wrapmargin = 10 - + -

The code above makes the line break 10 columns before the right -side of the terminal. + Receiving: Display Setup -

If your terminal is so wide that the lines are embarrassingly long, -you can also set a maximum line length: +

When you receive emails that are marked as -set max_line_length = 120 - + + set wrapmargin = 10 + -

The example above will give you lines not longer than 120 -characters. +

The code above makes the line break 10 columns before the right + side of the terminal. -

When you view at If your terminal is so wide that the lines are embarrassingly long, + you can also set a maximum line length: - ->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. - + + set max_line_length = 120 + -

This obviously doesn't look very nice, and it makes it very -hard to differentiate between text and quoting character. The -solution is to configure mutt-ng to "stuff" the quoting: +

The example above will give you lines not longer than 120 + characters. - -set stuff_quoted - +

When you view at 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. - +

This obviously doesn't look very nice, and it makes it very + hard to differentiate between text and quoting character. The + solution is to configure mutt-ng to "stuff" the quoting: -

If you want mutt-ng to send emails with + set stuff_quoted + - -set text_flowed - +

This will lead to a nicer result that is easier to read: -

Additionally, you have to use an editor which supports writing - + > 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. + + + + + Sending + +

If you want mutt-ng to send emails with + set text_flowed + + +

Additionally, you have to use an editor which supports writing + Also note that + + just a space for formatting reasons + + + + Please make sure that you manually prepend a space to each of them. + + + + Additional Notes + +

For completeness, the variable provides the mechanism + to generate a diff --git a/doc/manual.txt b/doc/manual.txt index d92203e..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-r408 + 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 7.4.324 , page 165) 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 @@ -497,7 +497,7 @@ _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 7.4.292 , page 155) 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 7.4.110 , 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.110 , page 111) 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 7.4.313 , page 163). + 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 @@ -570,7 +570,7 @@ 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. @@ -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 7.4.88 , page 106) 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 7.4.201 , page 134), _$_p_i_p_e___s_p_l_i_t - (section 7.4.203 , page 135), _$_p_i_p_e___s_e_p (section 7.4.202 , page 135) and - _$_w_a_i_t___k_e_y (section 7.4.336 , page 167) 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 7.4.337 , page 168) 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 - 7.4.336 , page 167) 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 7.4.226 , page 140) 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 7.4.309 , page 160) 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 7.4.54 , page 98). + 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 7.4.193 , page 133) 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 7.4.180 , page 130)) 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,7 +947,7 @@ 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 7.4.140 , + %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 @@ -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 7.4.215 , page 138) 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 7.4.214 , page 137) 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 @@ -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 7.4.54 , page 98) 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 7.5 , page 169). 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 7.4.298 , page - 157) 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 - 7.5 , page 169). + 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 7.4.226 , page 140) 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 7.4.234 , page 142).) + _$_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 7.4.66 , page 101) + 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 7.4.64 , page 100) and _$_s_p_o_o_l_f_i_l_e (section - 7.4.298 , page 157)) 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 7.4.54 , page 98) 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 7.4.231 , page 141). 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 - 7.4.231 , page 141) 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 7.4.248 , page 145) 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 7.4.15 , page 89), _$_s_i_g_n_a_t_u_r_e (section 7.4.260 , page 148) and - _$_l_o_c_a_l_e (section 7.4.114 , page 114) 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 7.5 , page 169). ``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 7.4.245 , page 145), _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___r_e_a_d (section 7.4.246 , 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.244 , page 144) and. By default, - _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___r_e_a_d (section 7.4.246 , 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.244 , page 144) 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 7.4.110 , page 111) 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. @@ -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 7.4.99 , page 108), + 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 7.4.170 , page 127) 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,6 +2259,8 @@ 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 @@ -2252,9 +2292,6 @@ ace it with \ (backslash). The fundamental building blocks are the regular expressions that match a single - - The Mutt Next Generation E-Mail Client 46 - character. Most characters, including all letters and digits, are regular expressions that match themselves. Any metacharacter with special meaning may be quoted by preceding it with a backslash. @@ -2273,6 +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: @@ -2309,8 +2348,6 @@ [:space:] Space characters (such as space, tab and formfeed, to name a few). - The Mutt Next Generation E-Mail Client 47 - [:upper:] Upper-case alphabetic characters. @@ -2329,6 +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''. @@ -2365,8 +2405,6 @@ The preceding item is matched at least _n times, but no more than _m times. - The Mutt Next Generation E-Mail Client 48 - Two regular expressions may be concatenated; the resulting regular expression matches any string formed by concatenating two substrings that respectively match the concatenated subexpressions. @@ -2385,6 +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. @@ -2419,9 +2459,6 @@ _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 - - The Mutt Next Generation E-Mail Client 49 - expressions. For ranges, the forms <[MAX], >>[MIN], [MIN]- and -[MAX] are also possible. @@ -2439,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' @@ -2470,9 +2509,6 @@ ~d 28/12/2004*1d The first pattern matches all dates between January 1st, 2005 and January 1st - - The Mutt Next Generation E-Mail Client 50 - 2006. The second pattern matches all dates between October 18th, 2004 and October 4th 2004 (2 weeks before 18/10/2004), while the third pattern matches all dates 1 day around December 28th, 2004 (i.e. Dec 27th, 28th and 29th). @@ -2489,6 +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. @@ -2505,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 7.4.309 , page 160) 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: @@ -2519,8 +2557,6 @@ In the index, there're more useful information one could want to see: - The Mutt Next Generation E-Mail Client 51 - +o which mailbox is open +o how man new, flagged or postponed messages @@ -2537,6 +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 +2604,6 @@ %??&? - The Mutt Next Generation E-Mail Client 52 - Using this we can make mutt-ng to do the following: +o make it print ``_n new messages'' whereby _n is the count but only if there @@ -2583,6 +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,11 +2651,8 @@ Since the previous expando stops at the end of line, there must be a way to fill the gap between two items via the %>X expando: it puts as many characters X in between two items so that the rest of - the line will be right-justified. For example, to not put the - - The Mutt Next Generation E-Mail Client 53 - - version string and hostname of our example on the left but on the + the line will be right-justified. For example, to not put the ver- + sion string and hostname of our example on the left but on the right and fill the gap with spaces, one might use (note the space after %>): @@ -2630,6 +2666,9 @@ 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 + + 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. @@ -2640,7 +2679,7 @@ 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 @@ -2652,22 +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 7.2 , page 80) 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) - The Mutt Next Generation E-Mail Client 54 - - +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) @@ -2681,11 +2718,13 @@ 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. @@ -2712,8 +2751,6 @@ _4_._6 _U_s_i_n_g _t_h_e _s_i_d_e_b_a_r - The Mutt Next Generation E-Mail Client 55 - The sidebar, a feature specific to Mutt-ng, allows you to use a mailbox listing which looks very similar to the ones you probably know from GUI mail clients. The sidebar lists all specified mailboxes, shows the number in each and high- @@ -2732,6 +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 @@ -2761,11 +2800,9 @@ _4_._7 _E_x_t_e_r_n_a_l _A_d_d_r_e_s_s _Q_u_e_r_i_e_s - The Mutt Next Generation E-Mail Client 56 - Mutt-ng supports connecting to external directory databases such as LDAP, ph/qi, bbdb, or NIS through a wrapper script which connects to mutt using a - simple interface. Using the _$_q_u_e_r_y___c_o_m_m_a_n_d (section 7.4.222 , page 139) 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'" @@ -2781,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 @@ -2804,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 7.4.126 , page 116) + 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 @@ -2812,8 +2852,6 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST - The Mutt Next Generation E-Mail Client 57 - to denote the start of a new message (this is often referred to as the ``From_'' line). @@ -2832,6 +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 @@ -2840,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 7.4.298 , page 157) (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 7.4.125 , page 116) 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 7.4.231 , page 141) file + +o < -- refers to your _$_r_e_c_o_r_d (section 7.4.232 , page 142) file +o ^ -- refers to the current mailbox @@ -2853,9 +2894,9 @@ +o ~ -- refers to your home directory - +o = or + -- refers to your _$_f_o_l_d_e_r (section 7.4.64 , page 100) 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 @@ -2864,17 +2905,14 @@ mail easier. The first thing you must do is to let Mutt know what addresses you consider to be mailing lists (technically this does not have to be a mail- ing list, but that is what it is most often used for), and what lists you are - - The Mutt Next Generation E-Mail Client 58 - subscribed to. This is accomplished through the use of the _l_i_s_t_s _a_n_d _s_u_b_s_c_r_i_b_e - (section 3.12 , page 32) commands in your muttrc. + (section 3.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 7.4.110 , page 111) 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'' field, and ``Cc '' when it appears in the ``Cc'' field (otherwise it returns the name of the author). @@ -2885,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 7.4.66 , page 101) 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 @@ -2899,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 7.4.88 , page 106) 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. @@ -2912,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 - 7.4.234 , page 142) 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 @@ -2920,16 +2961,13 @@ The ``X-Label:'' header field can be used to further identify mailing lists or list subject matter (or just to annotate messages individually). The - _$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.110 , page 111) variable's ``%y'' and ``%Y'' - - The Mutt Next Generation E-Mail Client 59 - + _$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.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 7.4.292 , page 155) 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 graphi- @@ -2940,6 +2978,9 @@ _4_._1_1 _E_d_i_t_i_n_g _t_h_r_e_a_d_s Mutt-ng has the ability to dynamically restructure threads that are broken + + The Mutt Next Generation E-Mail Client 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. @@ -2974,25 +3015,24 @@ +o Berkeley sendmail 8.8.x currently has some command line options in which the mail client can make requests as to what type of status messages - - The Mutt Next Generation E-Mail Client 60 - should be returned. +o The SMTP support via libESMTP supports it, too. To support this, there are two variables: - +o _$_d_s_n___n_o_t_i_f_y (section 7.4.51 , page 97) 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.). - +o _$_d_s_n___r_e_t_u_r_n (section 7.4.52 , page 97) 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. @@ -3008,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 7.4.209 , page 136) 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 @@ -3018,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 7.4.207 , 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.298 , page 157). + 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- @@ -3027,8 +3067,6 @@ _4_._1_4 _I_M_A_P _S_u_p_p_o_r_t _(_O_P_T_I_O_N_A_L_) - The Mutt Next Generation E-Mail Client 61 - If Mutt-ng was compiled with IMAP support (by running the _c_o_n_f_i_g_u_r_e script with the _-_-_e_n_a_b_l_e_-_i_m_a_p flag), it has the ability to work with folders located on a remote IMAP server. @@ -3047,6 +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- @@ -3061,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 7.4.97 , page 108) 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 7.4.99 , page 108) and - _$_t_i_m_e_o_u_t (section 7.4.322 , page 164) 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 @@ -3082,8 +3123,6 @@ sages and subfolders. On Cyrus-like servers folders will often contain both messages and subfolders. - The Mutt Next Generation E-Mail Client 62 - +o For the case where an entry can contain both messages and subfolders, the selection key (bound to enter by default) will choose to descend into the subfolder view. If you wish to view the messages in that folder, you must @@ -3103,6 +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 @@ -3116,15 +3157,15 @@ There are a few variables which control authentication: - +o _$_i_m_a_p___u_s_e_r (section 7.4.105 , page 110) - 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 7.4.100 , page 109) - 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 7.4.91 , page 106) - 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). @@ -3135,12 +3176,9 @@ newsserver via NNTP. You can open a newsgroup with the ``change-newsgroup'' function from the index/pager which is by default bound to i. - The Default newsserver can be obtained from the $NNTPSERVER environment - - The Mutt Next Generation E-Mail Client 63 - - variable. Like other news readers, info about subscribed newsgroups is saved in - a file as specified by the _$_n_n_t_p___n_e_w_s_r_c (section 7.4.157 , page 124) variable. + The Default newsserver can be obtained from the $NNTPSERVER environment vari- + able. Like other news readers, info about subscribed newsgroups is saved in a + file as specified by the _$_n_n_t_p___n_e_w_s_r_c (section 7.4.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. @@ -3159,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- @@ -3183,32 +3223,32 @@ _4_._1_6 _S_M_T_P _S_u_p_p_o_r_t _(_O_P_T_I_O_N_A_L_) Mutt-ng can be built using a library called ``libESMTP'' which provides SMTP - - The Mutt Next Generation E-Mail Client 64 - functionality. When configure was called with --with-libesmtp or the output muttng -v contains +USE_LIBESMTP, this will be or is the case already. The SMTP support includes support for Delivery Status Notification (see _D_e_l_i_v_e_r_y _S_t_a_t_u_s _N_o_t_i_f_i_c_a_t_i_o_n (section 4.12 , page 59) section) as well as handling the 8BIT- - MIME flag controlled via _$_u_s_e___8_b_i_t_m_i_m_e (section 7.4.329 , page 166). + 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 7.4.287 , page 154) + 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. - Authentication mechanisms are available via the _$_s_m_t_p___u_s_e_r (section 7.4.291 , - page 155) and _$_s_m_t_p___p_a_s_s (section 7.4.288 , page 154) 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 7.4.290 , page 155) 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 7.4.286 , + 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_) @@ -3236,8 +3276,6 @@ macro index \cb |urlview\n macro pager \cb |urlview\n - The Mutt Next Generation E-Mail Client 65 - _4_._1_9 _C_o_m_p_r_e_s_s_e_d _f_o_l_d_e_r_s _S_u_p_p_o_r_t _(_O_P_T_I_O_N_A_L_) If Mutt-ng was compiled with compressed folders support (by running the _c_o_n_f_i_g_- @@ -3253,10 +3291,12 @@ ing to it and converting back to the user-defined format. There are three hooks defined (_o_p_e_n_-_h_o_o_k (section 4.19.1 , page 65), _c_l_o_s_e_- - _h_o_o_k (section 4.19.2 , page 65) and _a_p_p_e_n_d_-_h_o_o_k (section 4.19.3 , page 66)) + _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" @@ -3265,7 +3305,7 @@ You do not have to specify all of the commands. If you omit _a_p_p_e_n_d_-_h_o_o_k (sec- tion 4.19.3 , page 66), the folder will be open and closed again each time you - will add to it. If you omit _c_l_o_s_e_-_h_o_o_k (section 4.19.2 , page 65) (or give + 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 66) though you'll be able to append to the folder. @@ -3274,7 +3314,7 @@ 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 7.4.241 , page 144), 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 @@ -3290,9 +3330,6 @@ %f and %t can be repeated any number of times in the command string, and all of the entries are replaced with the appropriate folder name. In addition, %% is - - The Mutt Next Generation E-Mail Client 66 - replaced by %, as in printf, and any other %anything is left as is. The _c_o_m_m_a_n_d should nnoott remove the original compressed file. The _c_o_m_m_a_n_d should @@ -3311,6 +3348,8 @@ This is used to close the folder that was open with the _o_p_e_n_-_h_o_o_k (section 4.19.1 , page 65) command after some changes were made to it. + 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 65) command. Temporary folder in this case is the folder previ- @@ -3326,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 @@ -3344,24 +3383,24 @@ Example: - The Mutt Next Generation E-Mail Client 67 - append-hook \\.gz$ "gzip -c %t >> %f" When _a_p_p_e_n_d_-_h_o_o_k (section 4.19.3 , page 66) is used, the folder is not opened, 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 7.4.126 , page 116)) type is always + 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 66). _a_p_p_e_n_d_- + 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 65) 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,8 +3431,6 @@ There are three areas/menus in Mutt-ng which deal with MIME, they are the pager (while viewing a message), the attachment menu and the compose menu. - The Mutt Next Generation E-Mail Client 68 - _5_._1_._1 _V_i_e_w_i_n_g _M_I_M_E _m_e_s_s_a_g_e_s _i_n _t_h_e _p_a_g_e_r When you select a message from the index and view it in the pager, Mutt decodes @@ -3411,6 +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) --] @@ -3447,8 +3486,6 @@ - 1 [text/plain, 7bit, 1K] /tmp/mutt-euler-8082-0 2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz - The Mutt Next Generation E-Mail Client 69 - The '-' denotes that Mutt-ng will delete the file after sending (or postponing, or canceling) the message. It can be toggled with the toggle-unlink command (default: u). The next field is the MIME content-type, and can be changed with @@ -3463,6 +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 +3538,6 @@ referred to as the mailcap format. Many MIME compliant programs utilize the mailcap format, allowing you to specify handling for all MIME types in one place for all programs. Programs known to use this format include Netscape, - - The Mutt Next Generation E-Mail Client 70 - XMosaic, lynx and metamail. In order to handle various MIME types that Mutt-ng can not handle internally, @@ -3515,6 +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 +3592,6 @@ text/plain; more %s - The Mutt Next Generation E-Mail Client 71 - Perhaps you would like to use lynx to interactively view a text/html message: text/html; lynx %s @@ -3568,6 +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 @@ -3583,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 7.4.117 , page 115) 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 +3644,6 @@ text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \ && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1 - The Mutt Next Generation E-Mail Client 72 - _5_._3_._3 _A_d_v_a_n_c_e_d _m_a_i_l_c_a_p _U_s_a_g_e _5_._3_._3_._1 _O_p_t_i_o_n_a_l _F_i_e_l_d_s @@ -3620,6 +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: @@ -3632,10 +3672,10 @@ needsterminal Mutt-ng uses this flag when viewing attachments with _a_u_t_o_v_i_e_w (sec- tion 5.4 , page 75), in order to decide whether it should honor - the setting of the _$_w_a_i_t___k_e_y (section 7.4.336 , page 167) variable + 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 7.4.336 , page 167) 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. @@ -3660,9 +3700,6 @@ edit= This flag specifies the command to use to edit a specific MIME type. Mutt-ng supports this from the compose menu, and also uses - - The Mutt Next Generation E-Mail Client 73 - it to compose new attachments. Mutt-ng will default to the defined editor for text attachments. @@ -3676,6 +3713,8 @@ text/html; lynx %s; nametemplate=%s.html + The Mutt Next Generation E-Mail Client 74 + test= This field specifies a command to run to test whether this mailcap entry should be used. The command is defined with the command @@ -3715,8 +3754,6 @@ can then use the test feature to determine which viewer to use interactively depending on your environment. - The Mutt Next Generation E-Mail Client 74 - text/html; netscape -remote 'openURL(%s)' ; test=RunningX text/html; lynx %s; nametemplate=%s.html text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput @@ -3729,6 +3766,9 @@ _5_._3_._3_._3 _C_o_m_m_a_n_d _E_x_p_a_n_s_i_o_n The various commands defined in the mailcap files are passed to the /bin/sh + + The Mutt Next Generation E-Mail Client 75 + shell using the system() function. Before the command is passed to /bin/sh -c, it is parsed to expand various special parameters with information from Mutt- ng. The keywords Mutt-ng expands are: @@ -3768,8 +3808,6 @@ This mailcap file is fairly simple and standard: - The Mutt Next Generation E-Mail Client 75 - # I'm always running X :) video/*; xanim %s > /dev/null image/*; xv %s > /dev/null @@ -3779,6 +3817,8 @@ This mailcap file shows quite a number of examples: + The Mutt Next Generation E-Mail Client 76 + # Use xanim to view all videos Xanim produces a header on startup, # send that to /dev/null so I don't see it video/*; xanim %s > /dev/null @@ -3818,11 +3858,8 @@ _5_._4 _M_I_M_E _A_u_t_o_v_i_e_w In addition to explicitly telling Mutt-ng to view an attachment with the MIME - viewer defined in the mailcap file, Mutt-ng has support for automatically - - The Mutt Next Generation E-Mail Client 76 - - viewing MIME attachments while in the pager. + viewer defined in the mailcap file, Mutt-ng has support for automatically view- + ing MIME attachments while in the pager. To work, you must define a viewer in the mailcap file which uses the copi- ousoutput option to denote that it is non-interactive. Usually, you also use @@ -3834,6 +3871,8 @@ For instance, if you set auto_view to: + The Mutt Next Generation E-Mail Client 77 + 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- @@ -3869,9 +3908,6 @@ _5_._6 _M_I_M_E _L_o_o_k_u_p Mutt-ng's mime_lookup list specifies a list of mime-types that should not be - - The Mutt Next Generation E-Mail Client 77 - treated according to their mailcap entry. This option is designed to deal with binary types such as application/octet-stream. When an attachment's mime-type is listed in mime_lookup, then the extension of the filename will be compared @@ -3883,6 +3919,9 @@ mime_lookup application/octet-stream application/X-Lotus-Manuscript In addition, the unmime_lookup command may be used to disable this feature for + + The Mutt Next Generation E-Mail Client 78 + any particular mime-type if it had been set, for example, in a global muttrc. _6_. _S_e_c_u_r_i_t_y _C_o_n_s_i_d_e_r_a_t_i_o_n_s @@ -3913,14 +3952,12 @@ _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.327 , page 166) variable can be used to + natures, etc. The _$_u_m_a_s_k (section 7.4.328 , page 166) 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.323 , page 165) + be desired which can be changed via the _$_t_m_p_d_i_r (section 7.4.324 , page 165) variable. - The Mutt Next Generation E-Mail Client 78 - _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 @@ -3930,9 +3967,11 @@ 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.143 , page 120) variable. Please make sure + of the _$_m_s_g_i_d___f_o_r_m_a_t (section 7.4.144 , page 120) variable. Please make sure that you really know how local parts of these Message-ID: headers are composed. + The Mutt Next Generation E-Mail Client 79 + _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 @@ -3940,7 +3979,7 @@ 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.54 , page 98) variable is _u_n_s_e_t, i.e. the user + _$_e_d_i_t___h_e_a_d_e_r_s (section 7.4.55 , page 98) 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 @@ -3950,13 +3989,13 @@ 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.311 , page 162) variable, mutt- + 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.312 , page 162) variable, mutt- ng will +o be less strict when interpreting these links by prepending a X-Mailto- string to all header fields embedded in such a link _a_n_d - +o turn on the _$_e_d_i_t___h_e_a_d_e_r_s (section 7.4.54 , page 98) variable by force to + +o turn on the _$_e_d_i_t___h_e_a_d_e_r_s (section 7.4.55 , page 98) variable by force to let the user see all the headers (because they still may leak informa- tion.) @@ -3969,27 +4008,26 @@ 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.116 , page 114) variable for + cap files (see the _$_m_a_i_l_c_a_p___p_a_t_h (section 7.4.117 , page 115) variable for details.) - These utilities may have a variety of security vulnerabilities, including - - The Mutt Next Generation E-Mail Client 79 - - 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... + These utilities may have a variety of security vulnerabilities, including over- + writing of arbitrary files, information leaks or other exploitable bugs. These + vulnerabilities may go unnoticed by the user, especially when they are called + automatically (and without interactive prompting) from the mailcap file(s). + When using mutt-ng's autoview mechanism in combination with mailcap files, + please be sure to... +o manually select trustworth applications with a reasonable calling sequence +o periodically check the contents of mailcap files, especially after soft- ware installations or upgrades + The Mutt Next Generation E-Mail Client 80 + +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.117 , page 115) variable in its + +o leave the _$_m_a_i_l_c_a_p___s_a_n_i_t_i_z_e (section 7.4.118 , page 115) variable in its default state to restrict mailcap expandos to a safe set of characters _6_._4_._2 _O_t_h_e_r @@ -4013,8 +4051,6 @@ mailbox. However, it is possible to read other mailboxes and to send messages from the command line as well. - The Mutt Next Generation E-Mail Client 80 - -A expand an alias -a attach a file to a message -b specify a blind carbon-copy (BCC) address @@ -4040,6 +4076,8 @@ To read messages in a mailbox + The Mutt Next Generation E-Mail Client 81 + mutt [ -nz ] [ -F _m_u_t_t_r_c ] [ -m _t_y_p_e ] [ -f _m_a_i_l_b_o_x ] To compose a new message @@ -4058,7 +4096,7 @@ _7_._2 _P_a_t_t_e_r_n_s - The Mutt Next Generation E-Mail Client 81 + The Mutt Next Generation E-Mail Client 82 ~A all messages ~b EXPR messages which contain EXPR in the message body @@ -4107,13 +4145,13 @@ alternates or any alias) Where EXPR, USER, ID, and SUBJECT are _r_e_g_u_l_a_r _e_x_p_r_e_s_s_i_o_n_s (section 4.1 , page - 44). Special attention has to be made when using regular expressions inside of + 45). 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 82 + The Mutt Next Generation E-Mail Client 83 *) The forms <[MAX], >[MIN], [MIN]- and -[MAX] are allowed, too. @@ -4121,7 +4159,7 @@ The following are the commands understood by mutt. - +o _a_c_c_o_u_n_t_-_h_o_o_k (section 4.17 , page 63) _p_a_t_t_e_r_n _c_o_m_m_a_n_d + +o _a_c_c_o_u_n_t_-_h_o_o_k (section 4.17 , page 64) _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, ... ] @@ -4145,15 +4183,15 @@ +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_l_o_s_e_-_h_o_o_k (section 4.19.2 , page 65) _r_e_g_e_x_p _c_o_m_m_a_n_d + +o _c_l_o_s_e_-_h_o_o_k (section 4.19.2 , page 66) _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 _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 _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.24 , page 38) _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.18 , 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.19 , page 36) _p_a_t_t_e_r_n _m_a_i_l_b_o_x @@ -4167,19 +4205,19 @@ +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 83 + The Mutt Next Generation E-Mail Client 84 +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 _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.12 , page 33) _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.12 , page 33) _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_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.14 , page 34) _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.13 , page 34) _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 @@ -4191,25 +4229,25 @@ +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 _m_y___h_d_r (section 3.15 , page 34) _s_t_r_i_n_g + +o _m_y___h_d_r (section 3.15 , page 35) _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.15 , page 35) _f_i_e_l_d [ _f_i_e_l_d ... ] +o _o_p_e_n_-_h_o_o_k (section 4.19.1 , page 65) _r_e_g_e_x_p _c_o_m_m_a_n_d - +o _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.22 , page 38) _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.23 , page 38) _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 _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.17 , page 36) _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 _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 _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.20 , page 37) _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 @@ -4219,19 +4257,19 @@ +o _s_o_u_r_c_e (section 3.28 , page 42) _f_i_l_e_n_a_m_e - +o _s_p_a_m (section 3.26 , page 39) _p_a_t_t_e_r_n _f_o_r_m_a_t + +o _s_p_a_m (section 3.26 , page 40) _p_a_t_t_e_r_n _f_o_r_m_a_t - +o _n_o_s_p_a_m (section 3.26 , page 39) _p_a_t_t_e_r_n + +o _n_o_s_p_a_m (section 3.26 , page 40) _p_a_t_t_e_r_n - The Mutt Next Generation E-Mail Client 84 + The Mutt Next Generation E-Mail Client 85 - +o _s_u_b_s_c_r_i_b_e (section 3.12 , page 32) _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] + +o _s_u_b_s_c_r_i_b_e (section 3.12 , page 33) _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] - +o _u_n_s_u_b_s_c_r_i_b_e (section 3.12 , page 32) _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] + +o _u_n_s_u_b_s_c_r_i_b_e (section 3.12 , page 33) _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] +o _t_o_g_g_l_e (section 3.27 , page 41) _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ] - +o _u_n_h_o_o_k (section 3.29 , page 42) _h_o_o_k_-_t_y_p_e + +o _u_n_h_o_o_k (section 3.29 , page 43) _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 @@ -4240,7 +4278,7 @@ left column contains the old synonym variables, the right column the full/new name: - The Mutt Next Generation E-Mail Client 85 + The Mutt Next Generation E-Mail Client 86 edit_hdrs edit_headers forw_decode forward_decode @@ -4296,7 +4334,7 @@ If set to _y_e_s, when composing messages and no subject is given at the subject - The Mutt Next Generation E-Mail Client 86 + The Mutt Next Generation E-Mail Client 87 prompt, composition will be aborted. If set to _n_o, composing messages with no subject given at the subject prompt will never be aborted. @@ -4353,7 +4391,7 @@ Default: yes - The Mutt Next Generation E-Mail Client 87 + The Mutt Next Generation E-Mail Client 88 Controls whether 8-bit data is converted to 7-bit using either quoted-printable or base64 encoding when sending mail. @@ -4409,7 +4447,7 @@ If _s_e_t, Mutt-ng will prompt you for carbon-copy (Cc) recipients before editing the body of an outgoing message. - The Mutt Next Generation E-Mail Client 88 + The Mutt Next Generation E-Mail Client 89 _7_._4_._1_1 _a_s_s_u_m_e_d___c_h_a_r_s_e_t @@ -4428,7 +4466,7 @@ 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 7.4.312 , page 162) is unset. + is valid only if _$_s_t_r_i_c_t___m_i_m_e (section 7.4.313 , page 163) is unset. _7_._4_._1_2 _a_t_t_a_c_h___f_o_r_m_a_t @@ -4466,7 +4504,7 @@ %M MIME subtype - The Mutt Next Generation E-Mail Client 89 + The Mutt Next Generation E-Mail Client 90 %n attachment number @@ -4518,11 +4556,11 @@ 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 7.4.110 , page 111)''. + on ``_$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.111 , page 111)''. _7_._4_._1_6 _a_u_t_o___t_a_g - The Mutt Next Generation E-Mail Client 90 + The Mutt Next Generation E-Mail Client 91 Type: boolean @@ -4539,12 +4577,12 @@ Default: no - When _s_e_t along with ``_$_e_d_i_t___h_e_a_d_e_r_s (section 7.4.54 , page 98)'', Mutt-ng will + When _s_e_t along with ``_$_e_d_i_t___h_e_a_d_e_r_s (section 7.4.55 , page 98)'', 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. - Also see ``_$_f_a_s_t___r_e_p_l_y (section 7.4.60 , page 99)''. + Also see ``_$_f_a_s_t___r_e_p_l_y (section 7.4.61 , page 99)''. _7_._4_._1_8 _b_e_e_p @@ -4579,7 +4617,7 @@ Type: boolean - The Mutt Next Generation E-Mail Client 91 + The Mutt Next Generation E-Mail Client 92 Default: yes @@ -4636,7 +4674,7 @@ When _s_e_t, Mutt-ng will check for new mail delivered while the mailbox is open. Especially with MH mailboxes, this operation can take quite some time since it - The Mutt Next Generation E-Mail Client 92 + The Mutt Next Generation E-Mail Client 93 involves scanning the directory and checking each file to see if it has already been looked at. If it's _u_n_s_e_t, no check for new mail is performed while the @@ -4658,7 +4696,7 @@ 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 7.4.309 , page 160)'', but has + string is similar to ``_$_s_t_a_t_u_s___f_o_r_m_a_t (section 7.4.310 , page 160)'', but has its own set of printf(3)-like sequences: %a @@ -4673,7 +4711,7 @@ %v Mutt-ng version string - See the text describing the ``_$_s_t_a_t_u_s___f_o_r_m_a_t (section 7.4.309 , page 160)'' + See the text describing the ``_$_s_t_a_t_u_s___f_o_r_m_a_t (section 7.4.310 , page 160)'' option for more information on how to set ``_$_c_o_m_p_o_s_e___f_o_r_m_a_t (section 7.4.27 , page 92)''. @@ -4693,7 +4731,7 @@ When _s_e_t, Mutt-ng will prompt for confirmation when appending messages to an - The Mutt Next Generation E-Mail Client 93 + The Mutt Next Generation E-Mail Client 94 existing mailbox. @@ -4732,9 +4770,9 @@ 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 7.4.231 , page - 141)'', ``_$_s_a_v_e___n_a_m_e (section 7.4.242 , page 144)'', ``_$_f_o_r_c_e___n_a_m_e (section - 7.4.68 , page 101)'' 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.232 , page + 142)'', ``_$_s_a_v_e___n_a_m_e (section 7.4.243 , page 144)'', ``_$_f_o_r_c_e___n_a_m_e (section + 7.4.69 , page 102)'' and ``_f_c_c_-_h_o_o_k (section 3.18 , page 36)''. _7_._4_._3_4 _c_r_y_p_t___a_u_t_o_e_n_c_r_y_p_t @@ -4746,11 +4784,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 - 7.4.278 , page 152)'' is _s_e_t, then OpenSSL is used instead to create S/MIME + 7.4.279 , page 153)'' 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 94 + The Mutt Next Generation E-Mail Client 95 _7_._4_._3_5 _c_r_y_p_t___a_u_t_o_p_g_p @@ -4762,7 +4800,7 @@ encryption/signing for messages. See also ``_$_c_r_y_p_t___a_u_t_o_e_n_c_r_y_p_t (section 7.4.34 , page 93)'', ``_$_c_r_y_p_t___r_e_p_l_y_e_n_c_r_y_p_t (section 7.4.38 , page 94)'', ``_$_c_r_y_p_t___a_u_t_o_s_i_g_n (section 7.4.36 , page 94)'', ``_$_c_r_y_p_t___r_e_p_l_y_s_i_g_n (section - 7.4.39 , page 94)'' and ``_$_s_m_i_m_e___i_s___d_e_f_a_u_l_t (section 7.4.278 , page 152)''. + 7.4.39 , page 94)'' and ``_$_s_m_i_m_e___i_s___d_e_f_a_u_l_t (section 7.4.279 , page 153)''. _7_._4_._3_6 _c_r_y_p_t___a_u_t_o_s_i_g_n @@ -4773,7 +4811,7 @@ 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 7.4.278 , page 152)'' is _s_e_t, then OpenSSL is + ``_$_s_m_i_m_e___i_s___d_e_f_a_u_l_t (section 7.4.279 , page 153)'' 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) @@ -4787,7 +4825,7 @@ encryption/signing for messages. See also ``_$_c_r_y_p_t___a_u_t_o_e_n_c_r_y_p_t (section 7.4.34 , page 93)'', ``_$_c_r_y_p_t___r_e_p_l_y_e_n_c_r_y_p_t (section 7.4.38 , page 94)'', ``_$_c_r_y_p_t___a_u_t_o_s_i_g_n (section 7.4.36 , page 94)'', ``_$_c_r_y_p_t___r_e_p_l_y_s_i_g_n (section - 7.4.39 , page 94)'' and ``_$_s_m_i_m_e___i_s___d_e_f_a_u_l_t (section 7.4.278 , page 152)''. + 7.4.39 , page 94)'' and ``_$_s_m_i_m_e___i_s___d_e_f_a_u_l_t (section 7.4.279 , page 153)''. _7_._4_._3_8 _c_r_y_p_t___r_e_p_l_y_e_n_c_r_y_p_t @@ -4806,7 +4844,7 @@ If _s_e_t, automatically PGP or OpenSSL sign replies to messages which are signed. - The Mutt Next Generation E-Mail Client 95 + The Mutt Next Generation E-Mail Client 96 NNoottee:: this does not work on messages that are encrypted aanndd signed! (Crypto only) @@ -4862,17 +4900,17 @@ Type: string - The Mutt Next Generation E-Mail Client 96 + The Mutt Next Generation E-Mail Client 97 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 7.4.110 , page 111)''. This is passed to strftime(3) + ``_$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.111 , page 111)''. 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 7.4.114 , page 114)''. If the first character in the string + ``_$_l_o_c_a_l_e (section 7.4.115 , page 114)''. 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). @@ -4902,7 +4940,23 @@ be purged without prompting. If set to _n_o, messages marked for deletion will be kept in the mailbox. - _7_._4_._4_7 _d_e_l_e_t_e___u_n_t_a_g + _7_._4_._4_7 _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 $text_flowed 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 $text_flowed is + _s_e_t) but not on incomming. + + _7_._4_._4_8 _d_e_l_e_t_e___u_n_t_a_g + + The Mutt Next Generation E-Mail Client 98 Type: boolean @@ -4912,29 +4966,27 @@ tion. This applies when you either explicitly delete a message, or when you save it to another folder. - _7_._4_._4_8 _d_i_g_e_s_t___c_o_l_l_a_p_s_e + _7_._4_._4_9 _d_i_g_e_s_t___c_o_l_l_a_p_s_e Type: boolean Default: yes - The Mutt Next Generation E-Mail Client 97 - If this option is _s_e_t, Mutt-ng's received-attachments menu will not show the subparts of individual messages in a multipart/digest. To see these subparts, press 'v' on that menu. - _7_._4_._4_9 _d_i_s_p_l_a_y___f_i_l_t_e_r + _7_._4_._5_0 _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 7.4.49 , + viewed it is passed as standard input to _$_d_i_s_p_l_a_y___f_i_l_t_e_r (section 7.4.50 , page 97), and the filtered message is read from the standard output. - _7_._4_._5_0 _d_o_t_l_o_c_k___p_r_o_g_r_a_m + _7_._4_._5_1 _d_o_t_l_o_c_k___p_r_o_g_r_a_m Type: path @@ -4944,7 +4996,7 @@ Contains the path of the muttng_dotlock(1) binary to be used by Mutt-ng. - _7_._4_._5_1 _d_s_n___n_o_t_i_f_y + _7_._4_._5_2 _d_s_n___n_o_t_i_f_y Type: string @@ -4961,7 +5013,9 @@ Example: set dsn_notify='failure,delay' - _7_._4_._5_2 _d_s_n___r_e_t_u_r_n + The Mutt Next Generation E-Mail Client 99 + + _7_._4_._5_3 _d_s_n___r_e_t_u_r_n Type: string @@ -4974,11 +5028,9 @@ It may be set to either _h_d_r_s to return just the message header, or _f_u_l_l to return the full message. - The Mutt Next Generation E-Mail Client 98 - Example: set dsn_return=hdrs - _7_._4_._5_3 _d_u_p_l_i_c_a_t_e___t_h_r_e_a_d_s + _7_._4_._5_4 _d_u_p_l_i_c_a_t_e___t_h_r_e_a_d_s Type: boolean @@ -4989,7 +5041,7 @@ indicate that it thinks they are duplicates of each other with an equals sign in the thread diagram. - _7_._4_._5_4 _e_d_i_t___h_e_a_d_e_r_s + _7_._4_._5_5 _e_d_i_t___h_e_a_d_e_r_s Type: boolean @@ -4998,7 +5050,7 @@ This option allows you to edit the header of your outgoing messages along with the body of your message. - _7_._4_._5_5 _e_d_i_t_o_r + _7_._4_._5_6 _e_d_i_t_o_r Type: path @@ -5008,7 +5060,7 @@ value of the $VISUAL, or $EDITOR, environment variable, or to the string 'vi' if neither of those are set. - _7_._4_._5_6 _e_n_c_o_d_e___f_r_o_m + _7_._4_._5_7 _e_n_c_o_d_e___f_r_o_m Type: boolean @@ -5017,9 +5069,17 @@ When _s_e_t, Mutt-ng will quoted-printable encode messages when they contain the string ``From '' (note the trailing space) in the beginning of a line. Useful to avoid the tampering certain mail delivery and transport agents tend to do + + The Mutt Next Generation E-Mail Client 100 + with messages. - _7_._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 @@ -5280,7 +5338,7 @@ Defaults to the contents of the environment variable $EMAIL. - _7_._4_._7_5 _g_e_c_o_s___m_a_s_k + _7_._4_._7_6 _g_e_c_o_s___m_a_s_k Type: regular expression @@ -5293,35 +5351,36 @@ do: set gecos_mask='.*'. This can be useful if you see the following behavior: you address a e-mail to + + The Mutt Next Generation E-Mail Client 105 + user ID stevef whose full name is Steve Franklin. If Mutt-ng expands stevef to ``Franklin'' stevef@foo.bar then you should set the gecos_mask to a regular expression that will match the whole name so Mutt-ng will expand ``Franklin'' to ``Franklin, Steve''. - _7_._4_._7_6 _h_d_r_s + _7_._4_._7_7 _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- + page 35)'' 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. - _7_._4_._7_7 _h_e_a_d_e_r + _7_._4_._7_8 _h_e_a_d_e_r Type: boolean - The Mutt Next Generation E-Mail Client 104 - 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 7.4.337 , page + are replying to into the edit buffer. The ``_$_w_e_e_d (section 7.4.338 , page 168)'' setting applies. - _7_._4_._7_8 _h_e_a_d_e_r___c_a_c_h_e + _7_._4_._7_9 _h_e_a_d_e_r___c_a_c_h_e Type: path @@ -5329,15 +5388,15 @@ Availability: Header Cache - The _$_h_e_a_d_e_r___c_a_c_h_e (section 7.4.78 , page 104) variable points to the header + The _$_h_e_a_d_e_r___c_a_c_h_e (section 7.4.79 , page 104) variable points to the header cache database. - If _$_h_e_a_d_e_r___c_a_c_h_e (section 7.4.78 , page 104) points to a directory it will + If _$_h_e_a_d_e_r___c_a_c_h_e (section 7.4.79 , page 104) 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.78 , page 104) points to a file that file will be a single global header + 7.4.79 , page 104) 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. - _7_._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_0 _h_e_a_d_e_r___c_a_c_h_e___c_o_m_p_r_e_s_s Type: boolean @@ -5347,7 +5406,9 @@ diskspace is used, but the uncompression can result in a slower open of the cached folder. - _7_._4_._8_0 _h_e_l_p + _7_._4_._8_1 _h_e_l_p + + The Mutt Next Generation E-Mail Client 106 Type: boolean @@ -5362,21 +5423,18 @@ is primarily aimed at new users, neither of these should present a major prob- lem. - _7_._4_._8_1 _h_i_d_d_e_n___h_o_s_t + _7_._4_._8_2 _h_i_d_d_e_n___h_o_s_t Type: boolean Default: no When _s_e_t, Mutt-ng will skip the host name part of ``_$_h_o_s_t_n_a_m_e (section - - The Mutt Next Generation E-Mail Client 105 - - 7.4.89 , page 106)'' variable when adding the domain part to addresses. This + 7.4.90 , page 106)'' 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. - _7_._4_._8_2 _h_i_d_e___l_i_m_i_t_e_d + _7_._4_._8_3 _h_i_d_e___l_i_m_i_t_e_d Type: boolean @@ -5385,7 +5443,7 @@ When _s_e_t, Mutt-ng will not show the presence of messages that are hidden by limiting, in the thread tree. - _7_._4_._8_3 _h_i_d_e___m_i_s_s_i_n_g + _7_._4_._8_4 _h_i_d_e___m_i_s_s_i_n_g Type: boolean @@ -5394,7 +5452,7 @@ When _s_e_t, Mutt-ng will not show the presence of missing messages in the thread tree. - _7_._4_._8_4 _h_i_d_e___t_h_r_e_a_d___s_u_b_j_e_c_t + _7_._4_._8_5 _h_i_d_e___t_h_r_e_a_d___s_u_b_j_e_c_t Type: boolean @@ -5403,38 +5461,38 @@ 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. - _7_._4_._8_5 _h_i_d_e___t_o_p___l_i_m_i_t_e_d + _7_._4_._8_6 _h_i_d_e___t_o_p___l_i_m_i_t_e_d Type: boolean + The Mutt Next Generation E-Mail Client 107 + Default: no 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 7.4.83 , page 105) is set, this option will have no effect. + _i_n_g (section 7.4.84 , page 105) is set, this option will have no effect. - _7_._4_._8_6 _h_i_d_e___t_o_p___m_i_s_s_i_n_g + _7_._4_._8_7 _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 7.4.82 , + threads in the thread tree. Note that when _$_h_i_d_e___l_i_m_i_t_e_d (section 7.4.83 , page 105) is _s_e_t, this option will have no effect. - _7_._4_._8_7 _h_i_s_t_o_r_y + _7_._4_._8_8 _h_i_s_t_o_r_y Type: number - The Mutt Next Generation E-Mail Client 106 - Default: 10 This variable controls the size (in number of strings remembered) of the string history buffer. The buffer is cleared each time the variable is changed. - _7_._4_._8_8 _h_o_n_o_r___f_o_l_l_o_w_u_p___t_o + _7_._4_._8_9 _h_o_n_o_r___f_o_l_l_o_w_u_p___t_o Type: quadoption @@ -5443,7 +5501,7 @@ This variable controls whether or not a Mail-Followup-To: header field is hon- ored when group-replying to a message. - _7_._4_._8_9 _h_o_s_t_n_a_m_e + _7_._4_._9_0 _h_o_s_t_n_a_m_e Type: string @@ -5455,7 +5513,7 @@ Please be sure to really know what you are doing when changing this variable to configure a custom domain part of Message-IDs. - _7_._4_._9_0 _i_g_n_o_r_e___l_i_s_t___r_e_p_l_y___t_o + _7_._4_._9_1 _i_g_n_o_r_e___l_i_s_t___r_e_p_l_y___t_o Type: boolean @@ -5463,13 +5521,16 @@ Affects the behaviour of the _r_e_p_l_y function when replying to messages from mailing lists. When _s_e_t, if the ``Reply-To:'' header field is set to the same + + The Mutt Next Generation E-Mail Client 108 + value as the ``To:'' header field, Mutt-ng assumes that the ``Reply-To:'' header field was set by the mailing list to automate responses to the list, and will ignore this field. To direct a response to the mailing list when this 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. - _7_._4_._9_1 _i_m_a_p___a_u_t_h_e_n_t_i_c_a_t_o_r_s + _7_._4_._9_2 _i_m_a_p___a_u_t_h_e_n_t_i_c_a_t_o_r_s Type: string @@ -5483,8 +5544,6 @@ capability string, e.g. ``digest-md5'', ``gssapi'' or ``cram-md5''. This param- eter is case-insensitive. - The Mutt Next Generation E-Mail Client 107 - If this parameter is _u_n_s_e_t (the default) Mutt-ng will try all available meth- ods, in order from most-secure to least-secure. @@ -5494,7 +5553,7 @@ ous methods are unavailable. If a method is available but authentication fails, Mutt-ng will not connect to the IMAP server. - _7_._4_._9_2 _i_m_a_p___c_h_e_c_k___s_u_b_s_c_r_i_b_e_d + _7_._4_._9_3 _i_m_a_p___c_h_e_c_k___s_u_b_s_c_r_i_b_e_d Type: boolean @@ -5502,9 +5561,9 @@ When _s_e_t, mutt will fetch the set of subscribed folders from your server on connection, and add them to the set of mailboxes it polls for new mail. See - also the ``_m_a_i_l_b_o_x_e_s (section 3.14 , page 33)'' command. + also the ``_m_a_i_l_b_o_x_e_s (section 3.14 , page 34)'' command. - _7_._4_._9_3 _i_m_a_p___d_e_l_i_m___c_h_a_r_s + _7_._4_._9_4 _i_m_a_p___d_e_l_i_m___c_h_a_r_s Type: string @@ -5514,12 +5573,14 @@ 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.64 , page 100) variable. + shortcut for your _$_f_o_l_d_e_r (section 7.4.65 , page 100) variable. - _7_._4_._9_4 _i_m_a_p___h_e_a_d_e_r_s + _7_._4_._9_5 _i_m_a_p___h_e_a_d_e_r_s Type: string + The Mutt Next Generation E-Mail Client 109 + Default: '' Availability: IMAP @@ -5531,7 +5592,7 @@ NNoottee:: This is a space separated list. - _7_._4_._9_5 _i_m_a_p___h_o_m_e___n_a_m_e_s_p_a_c_e + _7_._4_._9_6 _i_m_a_p___h_o_m_e___n_a_m_e_s_p_a_c_e Type: string @@ -5539,13 +5600,11 @@ Availability: IMAP - The Mutt Next Generation E-Mail Client 108 - You normally want to see your personal folders alongside your INBOX in the IMAP browser. If you see something else, you may set this variable to the IMAP path to your folders. - _7_._4_._9_6 _i_m_a_p___k_e_e_p_a_l_i_v_e + _7_._4_._9_7 _i_m_a_p___k_e_e_p_a_l_i_v_e Type: number @@ -5564,7 +5623,7 @@ Reduce this number if you find yourself getting disconnected from your IMAP server due to inactivity. - _7_._4_._9_7 _i_m_a_p___l_i_s_t___s_u_b_s_c_r_i_b_e_d + _7_._4_._9_8 _i_m_a_p___l_i_s_t___s_u_b_s_c_r_i_b_e_d Type: boolean @@ -5576,7 +5635,9 @@ 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. - _7_._4_._9_8 _i_m_a_p___l_o_g_i_n + The Mutt Next Generation E-Mail Client 110 + + _7_._4_._9_9 _i_m_a_p___l_o_g_i_n Type: string @@ -5586,23 +5647,21 @@ Your login name on the IMAP server. - This variable defaults to the value of ``_$_i_m_a_p___u_s_e_r (section 7.4.105 , page + This variable defaults to the value of ``_$_i_m_a_p___u_s_e_r (section 7.4.106 , page 110).'' - _7_._4_._9_9 _i_m_a_p___m_a_i_l___c_h_e_c_k + _7_._4_._1_0_0 _i_m_a_p___m_a_i_l___c_h_e_c_k Type: number Default: 300 - The Mutt Next Generation E-Mail Client 109 - 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 7.4.115 , + mail in IMAP folders. This is split from the ``_m_a_i_l___c_h_e_c_k (section 7.4.116 , page 114)'' variable to generate less traffic and get more accurate information for local folders. - _7_._4_._1_0_0 _i_m_a_p___p_a_s_s + _7_._4_._1_0_1 _i_m_a_p___p_a_s_s Type: string @@ -5617,7 +5676,7 @@ machine, because the superuser can read your configuration even if you are the only one who can read the file. - _7_._4_._1_0_1 _i_m_a_p___p_a_s_s_i_v_e + _7_._4_._1_0_2 _i_m_a_p___p_a_s_s_i_v_e Type: boolean @@ -5630,7 +5689,9 @@ 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. - _7_._4_._1_0_2 _i_m_a_p___p_e_e_k + _7_._4_._1_0_3 _i_m_a_p___p_e_e_k + + The Mutt Next Generation E-Mail Client 111 Type: boolean @@ -5643,7 +5704,7 @@ closing an IMAP folder somewhat slower. This option exists to appease speed freaks. - _7_._4_._1_0_3 _i_m_a_p___r_e_c_o_n_n_e_c_t + _7_._4_._1_0_4 _i_m_a_p___r_e_c_o_n_n_e_c_t Type: quadoption @@ -5651,12 +5712,10 @@ Availability: IMAP - The Mutt Next Generation E-Mail Client 110 - Controls whether or not Mutt-ng will try to reconnect to IMAP server when the connection is lost. - _7_._4_._1_0_4 _i_m_a_p___s_e_r_v_e_r_n_o_i_s_e + _7_._4_._1_0_5 _i_m_a_p___s_e_r_v_e_r_n_o_i_s_e Type: boolean @@ -5669,7 +5728,7 @@ ration problems on the server which are out of the users' hands, you may wish to suppress them at some point. - _7_._4_._1_0_5 _i_m_a_p___u_s_e_r + _7_._4_._1_0_6 _i_m_a_p___u_s_e_r Type: string @@ -5681,18 +5740,21 @@ This variable defaults to your user name on the local machine. - _7_._4_._1_0_6 _i_m_p_l_i_c_i_t___a_u_t_o_v_i_e_w + _7_._4_._1_0_7 _i_m_p_l_i_c_i_t___a_u_t_o_v_i_e_w Type: boolean Default: no If _s_e_t, Mutt-ng will look for a mailcap entry with the ``copiousoutput'' flag + + The Mutt Next Generation E-Mail Client 112 + set for _e_v_e_r_y MIME attachment it doesn't have an internal viewer defined for. If such an entry is found, Mutt-ng will use the viewer defined in that entry to convert the body part to text form. - _7_._4_._1_0_7 _i_n_c_l_u_d_e + _7_._4_._1_0_8 _i_n_c_l_u_d_e Type: quadoption @@ -5701,18 +5763,16 @@ Controls whether or not a copy of the message(s) you are replying to is included in your reply. - _7_._4_._1_0_8 _i_n_c_l_u_d_e___o_n_l_y_f_i_r_s_t + _7_._4_._1_0_9 _i_n_c_l_u_d_e___o_n_l_y_f_i_r_s_t Type: boolean Default: no - The Mutt Next Generation E-Mail Client 111 - Controls whether or not Mutt-ng includes only the first attachment of the mes- sage you are replying. - _7_._4_._1_0_9 _i_n_d_e_n_t___s_t_r_i_n_g + _7_._4_._1_1_0 _i_n_d_e_n_t___s_t_r_i_n_g Type: string @@ -5722,7 +5782,7 @@ which you are replying. You are strongly encouraged not to change this value, as it tends to agitate the more fanatical netizens. - _7_._4_._1_1_0 _i_n_d_e_x___f_o_r_m_a_t + _7_._4_._1_1_1 _i_n_d_e_x___f_o_r_m_a_t Type: string @@ -5744,6 +5804,8 @@ %b filename of the original message folder (think mailBox) + The Mutt Next Generation E-Mail Client 113 + %B the list to which the letter was sent, or else the folder name (%b). @@ -5762,8 +5824,6 @@ date and time of the message in the format specified by ``date_for- mat'' converted to the local time zone - The Mutt Next Generation E-Mail Client 112 - %e current message number in thread @@ -5800,6 +5860,8 @@ %M number of hidden messages if the thread is collapsed. + The Mutt Next Generation E-Mail Client 114 + %N message score @@ -5819,10 +5881,8 @@ %t `to:' field (recipients) - The Mutt Next Generation E-Mail Client 113 - %T - the appropriate character from the _$_t_o___c_h_a_r_s (section 7.4.324 , + the appropriate character from the _$_t_o___c_h_a_r_s (section 7.4.325 , page 165) string %u @@ -5856,6 +5916,8 @@ zone, and ``fmt'' is expanded by the library function ``strftime''; a leading bang disables locales + The Mutt Next Generation E-Mail Client 115 + %(fmt) the local date and time when the message was received. ``fmt'' is expanded by the library function ``strftime''; a leading bang dis- @@ -5871,11 +5933,9 @@ %|X pad to the end of the line with character 'X' - See also: ``_$_t_o___c_h_a_r_s (section 7.4.324 , page 165)''. - - _7_._4_._1_1_1 _i_s_p_e_l_l + See also: ``_$_t_o___c_h_a_r_s (section 7.4.325 , page 165)''. - The Mutt Next Generation E-Mail Client 114 + _7_._4_._1_1_2 _i_s_p_e_l_l Type: path @@ -5883,17 +5943,17 @@ How to invoke ispell (GNU's spell-checking software). - _7_._4_._1_1_2 _k_e_e_p___f_l_a_g_g_e_d + _7_._4_._1_1_3 _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 7.4.125 , page 116)'' 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.126 , page 117)'' mailbox, or as a result of + a ``_m_b_o_x_-_h_o_o_k (section 3.13 , page 34)'' command. - _7_._4_._1_1_3 _l_i_s_t___r_e_p_l_y + _7_._4_._1_1_4 _l_i_s_t___r_e_p_l_y Type: quadoption @@ -5903,7 +5963,7 @@ (instead to the author only). Setting this option to ``_a_s_k_-_y_e_s'' or ``_a_s_k_-_n_o'' will ask if you really intended to reply to the author only. - _7_._4_._1_1_4 _l_o_c_a_l_e + _7_._4_._1_1_5 _l_o_c_a_l_e Type: string @@ -5912,7 +5972,9 @@ The locale used by strftime(3) to format dates. Legal values are the strings your system accepts for the locale variable LC_TIME. - _7_._4_._1_1_5 _m_a_i_l___c_h_e_c_k + The Mutt Next Generation E-Mail Client 116 + + _7_._4_._1_1_6 _m_a_i_l___c_h_e_c_k Type: number @@ -5922,21 +5984,18 @@ mail. NNoottee:: This does not apply to IMAP mailboxes, see _$_i_m_a_p___m_a_i_l___c_h_e_c_k (section - 7.4.99 , page 108). + 7.4.100 , page 109). - _7_._4_._1_1_6 _m_a_i_l_c_a_p___p_a_t_h + _7_._4_._1_1_7 _m_a_i_l_c_a_p___p_a_t_h Type: string Default: '' This variable specifies which files to consult when attempting to display MIME - - The Mutt Next Generation E-Mail Client 115 - bodies not directly supported by Mutt-ng. - _7_._4_._1_1_7 _m_a_i_l_c_a_p___s_a_n_i_t_i_z_e + _7_._4_._1_1_8 _m_a_i_l_c_a_p___s_a_n_i_t_i_z_e Type: boolean @@ -5948,7 +6007,7 @@ DDOONN''TT CCHHAANNGGEE TTHHIISS SSEETTTTIINNGG UUNNLLEESSSS YYOOUU AARREE RREEAALLLLYY SSUURREE WWHHAATT YYOOUU AARREE DDOOIINNGG!! - _7_._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_1_9 _m_a_i_l_d_i_r___h_e_a_d_e_r___c_a_c_h_e___v_e_r_i_f_y Type: boolean @@ -5960,7 +6019,7 @@ files when the header cache is in use. This incurs one stat(2) per message every time the folder is opened. - _7_._4_._1_1_9 _m_a_i_l_d_i_r___t_r_a_s_h + _7_._4_._1_2_0 _m_a_i_l_d_i_r___t_r_a_s_h Type: boolean @@ -5969,12 +6028,14 @@ If _s_e_t, messages marked as deleted will be saved with the maildir (T)rashed flag instead of physically deleted. + The Mutt Next Generation E-Mail Client 117 + NNOOTTEE:: this only applies to maildir-style mailboxes. Setting it will have no effect on other mailbox types. It is similiar to the trash option. - _7_._4_._1_2_0 _m_a_r_k___o_l_d + _7_._4_._1_2_1 _m_a_r_k___o_l_d Type: boolean @@ -5987,9 +6048,7 @@ up with an 'O' next to them in the ``index'' menu, indicating that they are old. - The Mutt Next Generation E-Mail Client 116 - - _7_._4_._1_2_1 _m_a_r_k_e_r_s + _7_._4_._1_2_2 _m_a_r_k_e_r_s Type: boolean @@ -5997,9 +6056,9 @@ 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 7.4.264 , page 149)'' variable. + ``_$_s_m_a_r_t___w_r_a_p (section 7.4.265 , page 150)'' variable. - _7_._4_._1_2_2 _m_a_s_k + _7_._4_._1_2_3 _m_a_s_k Type: regular expression @@ -6009,7 +6068,7 @@ operator ``!''. Only files whose names match this mask will be shown. The match is always case-sensitive. - _7_._4_._1_2_3 _m_a_x___d_i_s_p_l_a_y___r_e_c_i_p_s + _7_._4_._1_2_4 _m_a_x___d_i_s_p_l_a_y___r_e_c_i_p_s Type: number @@ -6020,48 +6079,48 @@ case the number of lines exeeds its value, the last line will have 3 dots appended. - _7_._4_._1_2_4 _m_a_x___l_i_n_e___l_e_n_g_t_h + _7_._4_._1_2_5 _m_a_x___l_i_n_e___l_e_n_g_t_h Type: number Default: 0 + The Mutt Next Generation E-Mail Client 118 + 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 7.4.339 , page 168). + (section 7.4.340 , page 168). - _7_._4_._1_2_5 _m_b_o_x + _7_._4_._1_2_6 _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 - 7.4.298 , page 157)'' folder will be appended. + 7.4.299 , page 158)'' folder will be appended. - _7_._4_._1_2_6 _m_b_o_x___t_y_p_e + _7_._4_._1_2_7 _m_b_o_x___t_y_p_e Type: folder magic - The Mutt Next Generation E-Mail Client 117 - Default: mbox The default mailbox type used when creating new folders. May be any of mbox, MMDF, MH and Maildir. - _7_._4_._1_2_7 _m_e_n_u___c_o_n_t_e_x_t + _7_._4_._1_2_8 _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 7.4.168 , page + scrolling through menus. (Similar to ``_$_p_a_g_e_r___c_o_n_t_e_x_t (section 7.4.169 , page 127)''.) - _7_._4_._1_2_8 _m_e_n_u___m_o_v_e___o_f_f + _7_._4_._1_2_9 _m_e_n_u___m_o_v_e___o_f_f Type: boolean @@ -6071,7 +6130,7 @@ the screen, unless there are less entries than lines. When _s_e_t, the bottom entry may move off the bottom. - _7_._4_._1_2_9 _m_e_n_u___s_c_r_o_l_l + _7_._4_._1_3_0 _m_e_n_u___s_c_r_o_l_l Type: boolean @@ -6082,7 +6141,9 @@ vious page of the menu is displayed (useful for slow links to avoid many redraws). - _7_._4_._1_3_0 _m_e_s_s_a_g_e___f_o_r_m_a_t + The Mutt Next Generation E-Mail Client 119 + + _7_._4_._1_3_1 _m_e_s_s_a_g_e___f_o_r_m_a_t Type: string @@ -6090,9 +6151,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 7.4.110 , page 111)''. + section on ``_$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.111 , page 111)''. - _7_._4_._1_3_1 _m_e_t_a___k_e_y + _7_._4_._1_3_2 _m_e_t_a___k_e_y Type: boolean @@ -6100,15 +6161,12 @@ If _s_e_t, forces Mutt-ng to interpret keystrokes with the high bit (bit 8) set as if the user had pressed the ESC key and whatever key remains after having the - - The Mutt Next Generation E-Mail Client 118 - high bit removed. For example, if the key pressed has an ASCII value of 0xf4, then this is treated as if the user had pressed ESC then ``x''. This is because the result of removing the high bit from ``0xf4'' is ``0x74'', which is the ASCII character ``x''. - _7_._4_._1_3_2 _m_e_t_o_o + _7_._4_._1_3_3 _m_e_t_o_o Type: boolean @@ -6117,7 +6175,7 @@ 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. - _7_._4_._1_3_3 _m_h___p_u_r_g_e + _7_._4_._1_3_4 _m_h___p_u_r_g_e Type: boolean @@ -6127,7 +6185,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. - _7_._4_._1_3_4 _m_h___s_e_q___f_l_a_g_g_e_d + _7_._4_._1_3_5 _m_h___s_e_q___f_l_a_g_g_e_d Type: string @@ -6135,15 +6193,17 @@ The name of the MH sequence used for flagged messages. - _7_._4_._1_3_5 _m_h___s_e_q___r_e_p_l_i_e_d + _7_._4_._1_3_6 _m_h___s_e_q___r_e_p_l_i_e_d Type: string + The Mutt Next Generation E-Mail Client 120 + Default: 'replied' The name of the MH sequence used to tag replied messages. - _7_._4_._1_3_6 _m_h___s_e_q___u_n_s_e_e_n + _7_._4_._1_3_7 _m_h___s_e_q___u_n_s_e_e_n Type: string @@ -6151,14 +6211,12 @@ The name of the MH sequence used for unseen messages. - _7_._4_._1_3_7 _m_i_m_e___f_o_r_w_a_r_d + _7_._4_._1_3_8 _m_i_m_e___f_o_r_w_a_r_d Type: quadoption Default: no - The Mutt Next Generation E-Mail Client 119 - When _s_e_t, the message you are forwarding will be attached as a separate MIME part instead of included in the main body of the message. @@ -6166,20 +6224,20 @@ 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 7.4.69 , page 102)'' and ``_$_m_i_m_e___f_o_r_- - _w_a_r_d___d_e_c_o_d_e (section 7.4.138 , page 119)''. + Also see ``_$_f_o_r_w_a_r_d___d_e_c_o_d_e (section 7.4.70 , page 102)'' and ``_$_m_i_m_e___f_o_r_- + _w_a_r_d___d_e_c_o_d_e (section 7.4.139 , page 119)''. - _7_._4_._1_3_8 _m_i_m_e___f_o_r_w_a_r_d___d_e_c_o_d_e + _7_._4_._1_3_9 _m_i_m_e___f_o_r_w_a_r_d___d_e_c_o_d_e Type: boolean 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 7.4.137 , page 118)'' is _s_e_t. Other- - wise ``_$_f_o_r_w_a_r_d___d_e_c_o_d_e (section 7.4.69 , page 102)'' is used instead. + a message while ``_$_m_i_m_e___f_o_r_w_a_r_d (section 7.4.138 , page 119)'' is _s_e_t. Other- + wise ``_$_f_o_r_w_a_r_d___d_e_c_o_d_e (section 7.4.70 , page 102)'' is used instead. - _7_._4_._1_3_9 _m_i_m_e___f_o_r_w_a_r_d___r_e_s_t + _7_._4_._1_4_0 _m_i_m_e___f_o_r_w_a_r_d___r_e_s_t Type: quadoption @@ -6189,12 +6247,14 @@ menu, attachments which cannot be decoded in a reasonable manner will be attached to the newly composed message if this option is set. - _7_._4_._1_4_0 _m_i_x___e_n_t_r_y___f_o_r_m_a_t + _7_._4_._1_4_1 _m_i_x___e_n_t_r_y___f_o_r_m_a_t Type: string Default: '%4n %c %-16s %a' + The Mutt Next Generation E-Mail Client 121 + Availability: Mixmaster This variable describes the format of a remailer line on the mixmaster chain @@ -6212,9 +6272,7 @@ %a The remailer's e-mail address. - The Mutt Next Generation E-Mail Client 120 - - _7_._4_._1_4_1 _m_i_x_m_a_s_t_e_r + _7_._4_._1_4_2 _m_i_x_m_a_s_t_e_r Type: path @@ -6226,17 +6284,17 @@ used with various sets of parameters to gather the list of known remailers, and to finally send a message through the mixmaster chain. - _7_._4_._1_4_2 _m_o_v_e + _7_._4_._1_4_3 _m_o_v_e Type: quadoption Default: ask-no Controls whether or not Mutt-ng will move read messages from your spool mailbox - to your ``_$_m_b_o_x (section 7.4.125 , page 116)'' 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.126 , page 117)'' mailbox, or as a result of a + ``_m_b_o_x_-_h_o_o_k (section 3.13 , page 34)'' command. - _7_._4_._1_4_3 _m_s_g_i_d___f_o_r_m_a_t + _7_._4_._1_4_4 _m_s_g_i_d___f_o_r_m_a_t Type: string @@ -6250,6 +6308,8 @@ %d the current day of month + The Mutt Next Generation E-Mail Client 122 + %h the current hour @@ -6269,8 +6329,6 @@ the current Message-ID prefix (a character rotating with every Mes- sage-ID being generated) - The Mutt Next Generation E-Mail Client 121 - %r a random integer value (decimal) @@ -6295,7 +6353,7 @@ NNoottee:: Please only change this setting if you know what you are doing. Also make sure to consult RFC2822 to produce technically _v_a_l_i_d strings. - _7_._4_._1_4_4 _n_a_r_r_o_w___t_r_e_e + _7_._4_._1_4_5 _n_a_r_r_o_w___t_r_e_e Type: boolean @@ -6304,7 +6362,9 @@ This variable, when _s_e_t, makes the thread tree narrower, allowing deeper threads to fit on the screen. - _7_._4_._1_4_5 _n_n_t_p___a_s_k___f_o_l_l_o_w_u_p___t_o + _7_._4_._1_4_6 _n_n_t_p___a_s_k___f_o_l_l_o_w_u_p___t_o + + The Mutt Next Generation E-Mail Client 123 Type: boolean @@ -6315,7 +6375,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. - _7_._4_._1_4_6 _n_n_t_p___a_s_k___x___c_o_m_m_e_n_t___t_o + _7_._4_._1_4_7 _n_n_t_p___a_s_k___x___c_o_m_m_e_n_t___t_o Type: boolean @@ -6326,9 +6386,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. - The Mutt Next Generation E-Mail Client 122 - - _7_._4_._1_4_7 _n_n_t_p___c_a_c_h_e___d_i_r + _7_._4_._1_4_8 _n_n_t_p___c_a_c_h_e___d_i_r Type: path @@ -6343,7 +6401,7 @@ As for the header caching in connection with IMAP and/or Maildir, this drasti- cally increases speed and lowers traffic. - _7_._4_._1_4_8 _n_n_t_p___c_a_t_c_h_u_p + _7_._4_._1_4_9 _n_n_t_p___c_a_t_c_h_u_p Type: quadoption @@ -6354,7 +6412,7 @@ If this variable is _s_e_t, Mutt-ng will mark all articles in a newsgroup as read when you leaving it. - _7_._4_._1_4_9 _n_n_t_p___c_o_n_t_e_x_t + _7_._4_._1_5_0 _n_n_t_p___c_o_n_t_e_x_t Type: number @@ -6362,14 +6420,16 @@ Availability: NNTP + The Mutt Next Generation E-Mail Client 124 + 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 7.4.147 , page 121)) and how + caching is enabled, see _$_n_n_t_p___c_a_c_h_e___d_i_r (section 7.4.148 , page 122)) 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 7.4.149 , + If there're more articles than defined with _$_n_n_t_p___c_o_n_t_e_x_t (section 7.4.150 , page 122), all older ones will be removed/not shown in the index. - _7_._4_._1_5_0 _n_n_t_p___f_o_l_l_o_w_u_p___t_o___p_o_s_t_e_r + _7_._4_._1_5_1 _n_n_t_p___f_o_l_l_o_w_u_p___t_o___p_o_s_t_e_r Type: quadoption @@ -6381,9 +6441,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. - The Mutt Next Generation E-Mail Client 123 - - _7_._4_._1_5_1 _n_n_t_p___g_r_o_u_p___i_n_d_e_x___f_o_r_m_a_t + _7_._4_._1_5_2 _n_n_t_p___g_r_o_u_p___i_n_d_e_x___f_o_r_m_a_t Type: string @@ -6392,7 +6450,7 @@ 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 7.4.110 , + personal taste. This string is similar to ``_i_n_d_e_x___f_o_r_m_a_t (section 7.4.111 , page 111)'', but has its own set of printf(3)-like sequences: %C current newsgroup number @@ -6405,7 +6463,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" - _7_._4_._1_5_2 _n_n_t_p___h_o_s_t + _7_._4_._1_5_3 _n_n_t_p___h_o_s_t Type: string @@ -6416,6 +6474,9 @@ This variable specifies the name (or address) of the NNTP server to be used. It defaults to the value specified via the environment variable $NNTPSERVER or + + The Mutt Next Generation E-Mail Client 125 + contained in the file /etc/nntpserver. You can also specify a username and an alternative port for each newsserver, @@ -6427,7 +6488,7 @@ security risk since the superuser of your machine may read it regardless of the file's permissions. - _7_._4_._1_5_3 _n_n_t_p___i_n_e_w_s + _7_._4_._1_5_4 _n_n_t_p___i_n_e_w_s Type: path @@ -6435,8 +6496,6 @@ Availability: NNTP - The Mutt Next Generation E-Mail Client 124 - If _s_e_t, specifies the program and arguments used to deliver news posted by Mutt-ng. Otherwise, Mutt-ng posts article using current connection. The fol- lowing printf(3)-style sequence is understood: @@ -6445,7 +6504,7 @@ Example: set inews='/usr/local/bin/inews -hS' - _7_._4_._1_5_4 _n_n_t_p___l_o_a_d___d_e_s_c_r_i_p_t_i_o_n + _7_._4_._1_5_5 _n_n_t_p___l_o_a_d___d_e_s_c_r_i_p_t_i_o_n Type: boolean @@ -6456,7 +6515,7 @@ This variable controls whether or not descriptions for newsgroups are to be loaded when subscribing to a newsgroup. - _7_._4_._1_5_5 _n_n_t_p___m_a_i_l___c_h_e_c_k + _7_._4_._1_5_6 _n_n_t_p___m_a_i_l___c_h_e_c_k Type: number @@ -6468,7 +6527,9 @@ 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.). - _7_._4_._1_5_6 _n_n_t_p___m_i_m_e___s_u_b_j_e_c_t + _7_._4_._1_5_7 _n_n_t_p___m_i_m_e___s_u_b_j_e_c_t + + The Mutt Next Generation E-Mail Client 126 Type: boolean @@ -6481,7 +6542,7 @@ NNoottee:: Only change this setting if you know what you are doing. - _7_._4_._1_5_7 _n_n_t_p___n_e_w_s_r_c + _7_._4_._1_5_8 _n_n_t_p___n_e_w_s_r_c Type: path @@ -6489,8 +6550,6 @@ Availability: NNTP - The Mutt Next Generation E-Mail Client 125 - This file contains information about subscribed newsgroup and articles read so far. @@ -6499,7 +6558,7 @@ %s newsserver name - _7_._4_._1_5_8 _n_n_t_p___p_a_s_s + _7_._4_._1_5_9 _n_n_t_p___p_a_s_s Type: string @@ -6512,7 +6571,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. - _7_._4_._1_5_9 _n_n_t_p___p_o_s_t___m_o_d_e_r_a_t_e_d + _7_._4_._1_6_0 _n_n_t_p___p_o_s_t___m_o_d_e_r_a_t_e_d Type: quadoption @@ -6524,9 +6583,12 @@ sions to post (e.g. moderated). NNoottee:: if the newsserver does not support posting to that newsgroup or a group + + The Mutt Next Generation E-Mail Client 127 + is totally read-only, that posting will not have any effect. - _7_._4_._1_6_0 _n_n_t_p___r_e_c_o_n_n_e_c_t + _7_._4_._1_6_1 _n_n_t_p___r_e_c_o_n_n_e_c_t Type: quadoption @@ -6537,20 +6599,18 @@ Controls whether or not Mutt-ng will try to reconnect to a newsserver when the was connection lost. - _7_._4_._1_6_1 _n_n_t_p___s_a_v_e___u_n_s_u_b_s_c_r_i_b_e_d + _7_._4_._1_6_2 _n_n_t_p___s_a_v_e___u_n_s_u_b_s_c_r_i_b_e_d Type: boolean Default: no - The Mutt Next Generation E-Mail Client 126 - Availability: NNTP When _s_e_t, info about unsubscribed newsgroups will be saved into the ``newsrc'' file and into the news cache. - _7_._4_._1_6_2 _n_n_t_p___s_h_o_w___n_e_w___n_e_w_s + _7_._4_._1_6_3 _n_n_t_p___s_h_o_w___n_e_w___n_e_w_s Type: boolean @@ -6563,7 +6623,7 @@ whether or not the number of new articles of subscribed newsgroups will be checked. - _7_._4_._1_6_3 _n_n_t_p___s_h_o_w___o_n_l_y___u_n_r_e_a_d + _7_._4_._1_6_4 _n_n_t_p___s_h_o_w___o_n_l_y___u_n_r_e_a_d Type: boolean @@ -6574,18 +6634,20 @@ If _s_e_t, only subscribed newsgroups that contain unread articles will be dis- played in the newsgroup browser. - _7_._4_._1_6_4 _n_n_t_p___u_s_e_r + _7_._4_._1_6_5 _n_n_t_p___u_s_e_r Type: string Default: '' + The Mutt Next Generation E-Mail Client 128 + 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. - _7_._4_._1_6_5 _n_n_t_p___x___c_o_m_m_e_n_t___t_o + _7_._4_._1_6_6 _n_n_t_p___x___c_o_m_m_e_n_t___t_o Type: boolean @@ -6596,12 +6658,10 @@ 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. - _7_._4_._1_6_6 _o_p_e_r_a_t_i_n_g___s_y_s_t_e_m + _7_._4_._1_6_7 _o_p_e_r_a_t_i_n_g___s_y_s_t_e_m Type: string - The Mutt Next Generation E-Mail Client 127 - Default: '' This specifies the operating system name for the User-Agent: header field. If @@ -6610,7 +6670,7 @@ It may, for example, look as: ``mutt-ng 1.5.9i (Linux)''. - _7_._4_._1_6_7 _p_a_g_e_r + _7_._4_._1_6_8 _p_a_g_e_r Type: path @@ -6625,7 +6685,7 @@ screen resizes cause lines longer than the screen width to be badly formatted in the help menu. - _7_._4_._1_6_8 _p_a_g_e_r___c_o_n_t_e_x_t + _7_._4_._1_6_9 _p_a_g_e_r___c_o_n_t_e_x_t Type: number @@ -6636,7 +6696,9 @@ will display the line after the last one on the screen at the top of the next page (0 lines of context). - _7_._4_._1_6_9 _p_a_g_e_r___f_o_r_m_a_t + The Mutt Next Generation E-Mail Client 129 + + _7_._4_._1_7_0 _p_a_g_e_r___f_o_r_m_a_t Type: string @@ -6644,10 +6706,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 7.4.110 , page 111)'' + sequences are listed in the ``_$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.111 , page 111)'' section. - _7_._4_._1_7_0 _p_a_g_e_r___i_n_d_e_x___l_i_n_e_s + _7_._4_._1_7_1 _p_a_g_e_r___i_n_d_e_x___l_i_n_e_s Type: number @@ -6656,9 +6718,6 @@ Determines the number of lines of a mini-index which is shown when in the pager. The current message, unless near the top or bottom of the folder, will be roughly one third of the way down this mini-index, giving the reader the - - The Mutt Next Generation E-Mail Client 128 - context of a few messages before and after the message. This is useful, for example, to determine how many messages remain to be read in the current thread. One of the lines is reserved for the status bar from the index, so a @@ -6667,7 +6726,7 @@ 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. - _7_._4_._1_7_1 _p_a_g_e_r___s_t_o_p + _7_._4_._1_7_2 _p_a_g_e_r___s_t_o_p Type: boolean @@ -6676,7 +6735,7 @@ 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. - _7_._4_._1_7_2 _p_g_p___a_u_t_o___d_e_c_o_d_e + _7_._4_._1_7_3 _p_g_p___a_u_t_o___d_e_c_o_d_e Type: boolean @@ -6689,10 +6748,12 @@ ditional-pgp function, Mutt-ng will automatically check the message for tradi- tional pgp. - _7_._4_._1_7_3 _p_g_p___a_u_t_o_i_n_l_i_n_e + _7_._4_._1_7_4 _p_g_p___a_u_t_o_i_n_l_i_n_e Type: boolean + The Mutt Next Generation E-Mail Client 130 + Default: no This option controls whether Mutt-ng generates old-style inline (traditional) @@ -6702,23 +6763,21 @@ 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 7.4.189 , page 132)''. + ``_$_p_g_p___m_i_m_e___a_u_t_o (section 7.4.190 , page 132)''. Also note that using the old-style PGP message format is ssttrroonnggllyy ddeepprreeccaatteedd. (PGP only) - _7_._4_._1_7_4 _p_g_p___c_h_e_c_k___e_x_i_t + _7_._4_._1_7_5 _p_g_p___c_h_e_c_k___e_x_i_t Type: boolean Default: yes - The Mutt Next Generation E-Mail Client 129 - 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) - _7_._4_._1_7_5 _p_g_p___c_l_e_a_r_s_i_g_n___c_o_m_m_a_n_d + _7_._4_._1_7_6 _p_g_p___c_l_e_a_r_s_i_g_n___c_o_m_m_a_n_d Type: string @@ -6728,7 +6787,7 @@ Note that the use of this format is ssttrroonnggllyy ddeepprreeccaatteedd. (PGP only) - _7_._4_._1_7_6 _p_g_p___d_e_c_o_d_e___c_o_m_m_a_n_d + _7_._4_._1_7_7 _p_g_p___d_e_c_o_d_e___c_o_m_m_a_n_d Type: string @@ -6750,8 +6809,10 @@ 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 131 + %a - The value of _$_p_g_p___s_i_g_n___a_s (section 7.4.193 , page 133). + The value of _$_p_g_p___s_i_g_n___a_s (section 7.4.194 , page 133). %r One or more key IDs. @@ -6761,7 +6822,7 @@ subdirectory which has been installed on your system alongside the documenta- tion. (PGP only) - _7_._4_._1_7_7 _p_g_p___d_e_c_r_y_p_t___c_o_m_m_a_n_d + _7_._4_._1_7_8 _p_g_p___d_e_c_r_y_p_t___c_o_m_m_a_n_d Type: string @@ -6769,9 +6830,7 @@ This command is used to decrypt a PGP encrypted message. (PGP only) - The Mutt Next Generation E-Mail Client 130 - - _7_._4_._1_7_8 _p_g_p___e_n_c_r_y_p_t___o_n_l_y___c_o_m_m_a_n_d + _7_._4_._1_7_9 _p_g_p___e_n_c_r_y_p_t___o_n_l_y___c_o_m_m_a_n_d Type: string @@ -6779,7 +6838,7 @@ This command is used to encrypt a body part without signing it. (PGP only) - _7_._4_._1_7_9 _p_g_p___e_n_c_r_y_p_t___s_i_g_n___c_o_m_m_a_n_d + _7_._4_._1_8_0 _p_g_p___e_n_c_r_y_p_t___s_i_g_n___c_o_m_m_a_n_d Type: string @@ -6787,14 +6846,14 @@ This command is used to both sign and encrypt a body part. (PGP only) - _7_._4_._1_8_0 _p_g_p___e_n_t_r_y___f_o_r_m_a_t + _7_._4_._1_8_1 _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 7.4.110 , page + sonal taste. This string is similar to ``_$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.111 , page 111)'', but has its own set of printf(3)-like sequences: %n @@ -6806,6 +6865,8 @@ %u user id + The Mutt Next Generation E-Mail Client 132 + %a algorithm @@ -6826,9 +6887,7 @@ (PGP only) - The Mutt Next Generation E-Mail Client 131 - - _7_._4_._1_8_1 _p_g_p___e_x_p_o_r_t___c_o_m_m_a_n_d + _7_._4_._1_8_2 _p_g_p___e_x_p_o_r_t___c_o_m_m_a_n_d Type: string @@ -6837,7 +6896,7 @@ This command is used to export a public key from the user's key ring. (PGP only) - _7_._4_._1_8_2 _p_g_p___g_e_t_k_e_y_s___c_o_m_m_a_n_d + _7_._4_._1_8_3 _p_g_p___g_e_t_k_e_y_s___c_o_m_m_a_n_d Type: string @@ -6846,28 +6905,30 @@ 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) - _7_._4_._1_8_3 _p_g_p___g_o_o_d___s_i_g_n + _7_._4_._1_8_4 _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 7.4.199 , page 134) + verified if the output from _$_p_g_p___v_e_r_i_f_y___c_o_m_m_a_n_d (section 7.4.200 , page 135) contains the text. Use this variable if the exit code from the command is 0 even for bad signatures. (PGP only) - _7_._4_._1_8_4 _p_g_p___i_g_n_o_r_e___s_u_b_k_e_y_s + _7_._4_._1_8_5 _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 133 + 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) - _7_._4_._1_8_5 _p_g_p___i_m_p_o_r_t___c_o_m_m_a_n_d + _7_._4_._1_8_6 _p_g_p___i_m_p_o_r_t___c_o_m_m_a_n_d Type: string @@ -6876,21 +6937,19 @@ This command is used to import a key from a message into the user's public key ring. (PGP only) - _7_._4_._1_8_6 _p_g_p___l_i_s_t___p_u_b_r_i_n_g___c_o_m_m_a_n_d + _7_._4_._1_8_7 _p_g_p___l_i_s_t___p_u_b_r_i_n_g___c_o_m_m_a_n_d Type: string Default: '' - The Mutt Next Generation E-Mail Client 132 - This command is used to list the public key ring's contents. The output format 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) - _7_._4_._1_8_7 _p_g_p___l_i_s_t___s_e_c_r_i_n_g___c_o_m_m_a_n_d + _7_._4_._1_8_8 _p_g_p___l_i_s_t___s_e_c_r_i_n_g___c_o_m_m_a_n_d Type: string @@ -6902,7 +6961,7 @@ This format is also generated by the pgpring utility which comes with Mutt-ng. (PGP only) - _7_._4_._1_8_8 _p_g_p___l_o_n_g___i_d_s + _7_._4_._1_8_9 _p_g_p___l_o_n_g___i_d_s Type: boolean @@ -6911,7 +6970,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) - _7_._4_._1_8_9 _p_g_p___m_i_m_e___a_u_t_o + _7_._4_._1_9_0 _p_g_p___m_i_m_e___a_u_t_o Type: quadoption @@ -6919,12 +6978,15 @@ 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 134 + (for any reason). Also note that using the old-style PGP message format is ssttrroonnggllyy ddeepprreeccaatteedd. (PGP only) - _7_._4_._1_9_0 _p_g_p___r_e_p_l_y_i_n_l_i_n_e + _7_._4_._1_9_1 _p_g_p___r_e_p_l_y_i_n_l_i_n_e Type: boolean @@ -6938,17 +7000,14 @@ checked/flagged messages. Note that Mutt-ng might automatically use PGP/MIME for messages which consist - - The Mutt Next Generation E-Mail Client 133 - 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 7.4.189 , page 132)''. + ``_$_p_g_p___m_i_m_e___a_u_t_o (section 7.4.190 , page 132)''. Also note that using the old-style PGP message format is ssttrroonnggllyy ddeepprreeccaatteedd. (PGP only) - _7_._4_._1_9_1 _p_g_p___r_e_t_a_i_n_a_b_l_e___s_i_g_s + _7_._4_._1_9_2 _p_g_p___r_e_t_a_i_n_a_b_l_e___s_i_g_s Type: boolean @@ -6961,7 +7020,7 @@ the outer layer (multipart/encrypted) can be easily removed, while the inner multipart/signed part is retained. (PGP only) - _7_._4_._1_9_2 _p_g_p___s_h_o_w___u_n_u_s_a_b_l_e + _7_._4_._1_9_3 _p_g_p___s_h_o_w___u_n_u_s_a_b_l_e Type: boolean @@ -6971,17 +7030,19 @@ This includes keys which have been revoked, have expired, or have been marked as ``disabled'' by the user. (PGP only) - _7_._4_._1_9_3 _p_g_p___s_i_g_n___a_s + _7_._4_._1_9_4 _p_g_p___s_i_g_n___a_s Type: string Default: '' + The Mutt Next Generation E-Mail Client 135 + 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) - _7_._4_._1_9_4 _p_g_p___s_i_g_n___c_o_m_m_a_n_d + _7_._4_._1_9_5 _p_g_p___s_i_g_n___c_o_m_m_a_n_d Type: string @@ -6990,14 +7051,12 @@ This command is used to create the detached PGP signature for a multi- part/signed PGP/MIME body part. (PGP only) - _7_._4_._1_9_5 _p_g_p___s_o_r_t___k_e_y_s + _7_._4_._1_9_6 _p_g_p___s_o_r_t___k_e_y_s Type: sort order Default: address - The Mutt Next Generation E-Mail Client 134 - Specifies how the entries in the ``pgp keys'' menu are sorted. The following are legal values: @@ -7016,7 +7075,7 @@ If you prefer reverse order of the above values, prefix it with ``reverse-''. (PGP only) - _7_._4_._1_9_6 _p_g_p___s_t_r_i_c_t___e_n_c + _7_._4_._1_9_7 _p_g_p___s_t_r_i_c_t___e_n_c Type: boolean @@ -7027,16 +7086,18 @@ non-verifyable PGP signatures, so only change this if you know what you are doing. (PGP only) - _7_._4_._1_9_7 _p_g_p___t_i_m_e_o_u_t + _7_._4_._1_9_8 _p_g_p___t_i_m_e_o_u_t Type: number Default: 300 + The Mutt Next Generation E-Mail Client 136 + The number of seconds after which a cached passphrase will expire if not used. Default: 300. (PGP only) - _7_._4_._1_9_8 _p_g_p___u_s_e___g_p_g___a_g_e_n_t + _7_._4_._1_9_9 _p_g_p___u_s_e___g_p_g___a_g_e_n_t Type: boolean @@ -7044,7 +7105,7 @@ If _s_e_t, Mutt-ng will use a possibly-running gpg-agent process. (PGP only) - _7_._4_._1_9_9 _p_g_p___v_e_r_i_f_y___c_o_m_m_a_n_d + _7_._4_._2_0_0 _p_g_p___v_e_r_i_f_y___c_o_m_m_a_n_d Type: string @@ -7052,9 +7113,7 @@ This command is used to verify PGP signatures. (PGP only) - The Mutt Next Generation E-Mail Client 135 - - _7_._4_._2_0_0 _p_g_p___v_e_r_i_f_y___k_e_y___c_o_m_m_a_n_d + _7_._4_._2_0_1 _p_g_p___v_e_r_i_f_y___k_e_y___c_o_m_m_a_n_d Type: string @@ -7063,7 +7122,7 @@ This command is used to verify key information from the key selection menu. (PGP only) - _7_._4_._2_0_1 _p_i_p_e___d_e_c_o_d_e + _7_._4_._2_0_2 _p_i_p_e___d_e_c_o_d_e Type: boolean @@ -7073,7 +7132,7 @@ 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. - _7_._4_._2_0_2 _p_i_p_e___s_e_p + _7_._4_._2_0_3 _p_i_p_e___s_e_p Type: string @@ -7082,20 +7141,23 @@ The separator to add between messages when piping a list of tagged messages to an external Unix command. - _7_._4_._2_0_3 _p_i_p_e___s_p_l_i_t + _7_._4_._2_0_4 _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 137 + ``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 7.4.202 , page 135)'' separator is added after each message. + (section 7.4.203 , page 135)'' separator is added after each message. - _7_._4_._2_0_4 _p_o_p___a_u_t_h___t_r_y___a_l_l + _7_._4_._2_0_5 _p_o_p___a_u_t_h___t_r_y___a_l_l Type: boolean @@ -7108,9 +7170,7 @@ able. If a method is available but authentication fails, Mutt-ng will not con- nect to the POP server. - The Mutt Next Generation E-Mail Client 136 - - _7_._4_._2_0_5 _p_o_p___a_u_t_h_e_n_t_i_c_a_t_o_r_s + _7_._4_._2_0_6 _p_o_p___a_u_t_h_e_n_t_i_c_a_t_o_r_s Type: string @@ -7129,7 +7189,7 @@ Example: set pop_authenticators='digest-md5:apop:user' - _7_._4_._2_0_6 _p_o_p___d_e_l_e_t_e + _7_._4_._2_0_7 _p_o_p___d_e_l_e_t_e Type: quadoption @@ -7141,10 +7201,12 @@ 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. - _7_._4_._2_0_7 _p_o_p___h_o_s_t + _7_._4_._2_0_8 _p_o_p___h_o_s_t Type: string + The Mutt Next Generation E-Mail Client 138 + Default: '' Availability: POP @@ -7157,7 +7219,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. - _7_._4_._2_0_8 _p_o_p___l_a_s_t + _7_._4_._2_0_9 _p_o_p___l_a_s_t Type: boolean @@ -7165,13 +7227,11 @@ Availability: POP - The Mutt Next Generation E-Mail Client 137 - If this variable is _s_e_t, Mutt-ng will try to use the ``LAST'' POP command for retrieving only unread messages from the POP server when using the ``fetch- mail'' function. - _7_._4_._2_0_9 _p_o_p___m_a_i_l___c_h_e_c_k + _7_._4_._2_1_0 _p_o_p___m_a_i_l___c_h_e_c_k Type: number @@ -7181,7 +7241,7 @@ This variable configures how often (in seconds) POP should look for new mail. - _7_._4_._2_1_0 _p_o_p___p_a_s_s + _7_._4_._2_1_1 _p_o_p___p_a_s_s Type: string @@ -7195,18 +7255,20 @@ 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. - _7_._4_._2_1_1 _p_o_p___r_e_c_o_n_n_e_c_t + _7_._4_._2_1_2 _p_o_p___r_e_c_o_n_n_e_c_t Type: quadoption Default: ask-yes + The Mutt Next Generation E-Mail Client 139 + Availability: POP Controls whether or not Mutt-ng will try to reconnect to a POP server when the connection is lost. - _7_._4_._2_1_2 _p_o_p___u_s_e_r + _7_._4_._2_1_3 _p_o_p___u_s_e_r Type: string @@ -7218,48 +7280,49 @@ This variable defaults to your user name on the local machine. - _7_._4_._2_1_3 _p_o_s_t___i_n_d_e_n_t___s_t_r_i_n_g + _7_._4_._2_1_4 _p_o_s_t___i_n_d_e_n_t___s_t_r_i_n_g Type: string - The Mutt Next Generation E-Mail Client 138 - Default: '' Similar to the ``_$_a_t_t_r_i_b_u_t_i_o_n (section 7.4.15 , page 89)'' variable, Mutt-ng will append this string after the inclusion of a message which is being replied to. - _7_._4_._2_1_4 _p_o_s_t_p_o_n_e + _7_._4_._2_1_5 _p_o_s_t_p_o_n_e Type: quadoption Default: ask-yes Controls whether or not messages are saved in the ``_$_p_o_s_t_p_o_n_e_d (section - 7.4.215 , page 138)'' mailbox when you elect not to send immediately. + 7.4.216 , page 138)'' mailbox when you elect not to send immediately. - _7_._4_._2_1_5 _p_o_s_t_p_o_n_e_d + _7_._4_._2_1_6 _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 7.4.214 , page 137) + Mutt-ng allows you to indefinitely ``_p_o_s_t_p_o_n_e (section 7.4.215 , page 138) 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 7.4.214 , page 137)'' variable. + ``_$_p_o_s_t_p_o_n_e (section 7.4.215 , page 138)'' variable. - _7_._4_._2_1_6 _p_r_e_c_o_n_n_e_c_t + _7_._4_._2_1_7 _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 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: + If _s_e_t, a shell command to be executed if Mutt-ng fails to establish a + + The Mutt Next Generation E-Mail Client 140 + + 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: preconnect='ssh -f -q -L 1234:mailhost.net:143 mailhost.net sleep 20 < /dev/null > /dev/null' @@ -7269,7 +7332,7 @@ NNoottee:: For this example to work, you must be able to log in to the remote machine without having to enter a password. - _7_._4_._2_1_7 _p_r_i_n_t + _7_._4_._2_1_8 _p_r_i_n_t Type: quadoption @@ -7278,9 +7341,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. - The Mutt Next Generation E-Mail Client 139 - - _7_._4_._2_1_8 _p_r_i_n_t___c_o_m_m_a_n_d + _7_._4_._2_1_9 _p_r_i_n_t___c_o_m_m_a_n_d Type: path @@ -7288,7 +7349,7 @@ This specifies the command pipe that should be used to print messages. - _7_._4_._2_1_9 _p_r_i_n_t___d_e_c_o_d_e + _7_._4_._2_2_0 _p_r_i_n_t___d_e_c_o_d_e Type: boolean @@ -7296,52 +7357,52 @@ 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 7.4.218 , page 138). 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.219 , page 139). 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. - _7_._4_._2_2_0 _p_r_i_n_t___s_p_l_i_t + _7_._4_._2_2_1 _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 7.4.218 , page 138) is executed + command specified by _$_p_r_i_n_t___c_o_m_m_a_n_d (section 7.4.219 , page 139) 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 7.4.218 , page 138) is executed + command specified by _$_p_r_i_n_t___c_o_m_m_a_n_d (section 7.4.219 , page 139) 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 141 + Those who use the enscript(1) program's mail-printing mode will most likely want to set this option. - _7_._4_._2_2_1 _p_r_o_m_p_t___a_f_t_e_r + _7_._4_._2_2_2 _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 7.4.167 , page 127)'', setting this + If you use an _e_x_t_e_r_n_a_l ``_$_p_a_g_e_r (section 7.4.168 , page 127)'', 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. - _7_._4_._2_2_2 _q_u_e_r_y___c_o_m_m_a_n_d + _7_._4_._2_2_3 _q_u_e_r_y___c_o_m_m_a_n_d Type: path Default: '' - The Mutt Next Generation E-Mail Client 140 - 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 56)'' for more information. - _7_._4_._2_2_3 _q_u_i_t + _7_._4_._2_2_4 _q_u_i_t Type: quadoption @@ -7352,16 +7413,16 @@ 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. - _7_._4_._2_2_4 _q_u_o_t_e___e_m_p_t_y + _7_._4_._2_2_5 _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 7.4.109 , page 111)''. + tion 7.4.110 , page 111)''. - _7_._4_._2_2_5 _q_u_o_t_e___q_u_o_t_e_d + _7_._4_._2_2_6 _q_u_o_t_e___q_u_o_t_e_d Type: boolean @@ -7369,9 +7430,11 @@ 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 7.4.109 , page 111)''. + by ``_i_n_d_e_n_t___s_t_r_i_n_g (section 7.4.110 , page 111)''. + + The Mutt Next Generation E-Mail Client 142 - _7_._4_._2_2_6 _q_u_o_t_e___r_e_g_e_x_p + _7_._4_._2_2_7 _q_u_o_t_e___r_e_g_e_x_p Type: regular expression @@ -7384,14 +7447,12 @@ set this to a regular expression that matches _e_x_a_c_t_l_y the quote characters at the beginning of quoted lines. - _7_._4_._2_2_7 _r_e_a_d___i_n_c + _7_._4_._2_2_8 _r_e_a_d___i_n_c Type: number Default: 10 - The Mutt Next Generation E-Mail Client 141 - If set to a value greater than 0, Mutt-ng will display which message it is cur- rently on when reading a mailbox. The message is printed after _r_e_a_d___i_n_c mes- sages have been read (e.g., if set to 25, Mutt-ng will print a message when it @@ -7400,9 +7461,9 @@ time. When set to 0, only a single message will appear before the reading the mailbox. - Also see the ``_$_w_r_i_t_e___i_n_c (section 7.4.341 , page 168)'' variable. + Also see the ``_$_w_r_i_t_e___i_n_c (section 7.4.342 , page 169)'' variable. - _7_._4_._2_2_8 _r_e_a_d___o_n_l_y + _7_._4_._2_2_9 _r_e_a_d___o_n_l_y Type: boolean @@ -7410,7 +7471,7 @@ If set, all folders are opened in read-only mode. - _7_._4_._2_2_9 _r_e_a_l_n_a_m_e + _7_._4_._2_3_0 _r_e_a_l_n_a_m_e Type: string @@ -7422,20 +7483,22 @@ By default, this is the GECOS field from /etc/passwd. _N_o_t_e_: This variable will _n_o_t be used when the user has set a real name in the - _$_f_r_o_m (section 7.4.74 , page 103) variable. + _$_f_r_o_m (section 7.4.75 , page 103) variable. - _7_._4_._2_3_0 _r_e_c_a_l_l + _7_._4_._2_3_1 _r_e_c_a_l_l Type: quadoption + The Mutt Next Generation E-Mail Client 143 + 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 7.4.215 , page 138)''. + message. Also see ``_$_p_o_s_t_p_o_n_e_d (section 7.4.216 , page 138)''. Setting this variable to _y_e_s is not generally useful, and thus not recommended. - _7_._4_._2_3_1 _r_e_c_o_r_d + _7_._4_._2_3_2 _r_e_c_o_r_d Type: path @@ -7443,17 +7506,15 @@ 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.15 , page 35)'' com- mand to create a Bcc: header field with your email address in it.) - The Mutt Next Generation E-Mail Client 142 - - The value of _$_r_e_c_o_r_d _(_s_e_c_t_i_o_n _7_._4_._2_3_1 _, _p_a_g_e _1_4_1_) is overridden by the - ``_$_f_o_r_c_e___n_a_m_e (section 7.4.68 , page 101)'' and ``_$_s_a_v_e___n_a_m_e (section - 7.4.242 , page 144)'' 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_3_2 _, _p_a_g_e _1_4_2_) is overridden by the + ``_$_f_o_r_c_e___n_a_m_e (section 7.4.69 , page 102)'' and ``_$_s_a_v_e___n_a_m_e (section + 7.4.243 , page 144)'' variables, and the ``_f_c_c_-_h_o_o_k (section 3.18 , page + 36)'' command. - _7_._4_._2_3_2 _r_e_p_l_y___r_e_g_e_x_p + _7_._4_._2_3_3 _r_e_p_l_y___r_e_g_e_x_p Type: regular expression @@ -7463,7 +7524,7 @@ ing. The default value corresponds to the English ``Re:'' and the German ``Aw:''. - _7_._4_._2_3_3 _r_e_p_l_y___s_e_l_f + _7_._4_._2_3_4 _r_e_p_l_y___s_e_l_f Type: boolean @@ -7473,7 +7534,7 @@ that you want to reply to the recipients of that message rather than to your- self. - _7_._4_._2_3_4 _r_e_p_l_y___t_o + _7_._4_._2_3_5 _r_e_p_l_y___t_o Type: quadoption @@ -7484,10 +7545,13 @@ 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 144 + header field to the list address and you want to send a private message to the author of a message. - _7_._4_._2_3_5 _r_e_s_o_l_v_e + _7_._4_._2_3_6 _r_e_s_o_l_v_e Type: boolean @@ -7497,14 +7561,12 @@ undeleted) message whenever a command that modifies the current message is exe- cuted. - _7_._4_._2_3_6 _r_e_v_e_r_s_e___a_l_i_a_s + _7_._4_._2_3_7 _r_e_v_e_r_s_e___a_l_i_a_s Type: boolean Default: no - The Mutt Next Generation E-Mail Client 143 - This variable controls whether or not Mutt-ng will display the ``personal'' name from your aliases in the index menu if it finds an alias that matches the message's sender. For example, if you have the following alias: @@ -7519,7 +7581,7 @@ ``abd30425@somewhere.net.'' This is useful when the person's e-mail address is not human friendly (like CompuServe addresses). - _7_._4_._2_3_7 _r_e_v_e_r_s_e___n_a_m_e + _7_._4_._2_3_8 _r_e_v_e_r_s_e___n_a_m_e Type: boolean @@ -7533,19 +7595,22 @@ would be used doesn't match your alternates, the From: line will use your address on the current machine. - _7_._4_._2_3_8 _r_e_v_e_r_s_e___r_e_a_l_n_a_m_e + _7_._4_._2_3_9 _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 7.4.237 , + This variable fine-tunes the behaviour of the _r_e_v_e_r_s_e___n_a_m_e (section 7.4.238 , + + The Mutt Next Generation E-Mail Client 145 + page 143) 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 7.4.229 , page 141) variable. + (section 7.4.230 , page 141) variable. - _7_._4_._2_3_9 _r_f_c_2_0_4_7___p_a_r_a_m_e_t_e_r_s + _7_._4_._2_4_0 _r_f_c_2_0_4_7___p_a_r_a_m_e_t_e_r_s Type: boolean @@ -7560,8 +7625,6 @@ When this variable is _s_e_t interactively, the change doesn't have the desired effect before you have changed folders. - The Mutt Next Generation E-Mail Client 144 - Note that this use of RFC 2047's encoding is explicitly, prohibited by the standard, but nevertheless encountered in the wild. @@ -7569,60 +7632,58 @@ _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. - _7_._4_._2_4_0 _s_a_v_e___a_d_d_r_e_s_s + _7_._4_._2_4_1 _s_a_v_e___a_d_d_r_e_s_s Type: boolean 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 7.4.242 , page 144)'' or - ``_$_f_o_r_c_e___n_a_m_e (section 7.4.68 , page 101)'' 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.243 , page 144)'' or + ``_$_f_o_r_c_e___n_a_m_e (section 7.4.69 , page 102)'' is _s_e_t too, the selection of the fcc folder will be changed as well. - _7_._4_._2_4_1 _s_a_v_e___e_m_p_t_y + _7_._4_._2_4_2 _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 7.4.298 , page 157)'' which is + closed (the exception is ``_$_s_p_o_o_l_f_i_l_e (section 7.4.299 , page 158)'' 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. - _7_._4_._2_4_2 _s_a_v_e___n_a_m_e + _7_._4_._2_4_3 _s_a_v_e___n_a_m_e Type: boolean + The Mutt Next Generation E-Mail Client 146 + 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 7.4.64 , + (this is done by searching for a mailbox in the ``_$_f_o_l_d_e_r (section 7.4.65 , page 100)'' 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 7.4.231 , page 141)'' mailbox. + the message is saved to the ``_$_r_e_c_o_r_d (section 7.4.232 , page 142)'' mailbox. - Also see the ``_$_f_o_r_c_e___n_a_m_e (section 7.4.68 , page 101)'' variable. + Also see the ``_$_f_o_r_c_e___n_a_m_e (section 7.4.69 , page 102)'' variable. - _7_._4_._2_4_3 _s_c_o_r_e + _7_._4_._2_4_4 _s_c_o_r_e Type: boolean Default: yes 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 - - The Mutt Next Generation E-Mail Client 145 - - ``_$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___d_e_l_e_t_e (section 7.4.244 , page 144)'' variable and friends - are used. + 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 7.4.245 , page 145)'' variable and friends are used. - _7_._4_._2_4_4 _s_c_o_r_e___t_h_r_e_s_h_o_l_d___d_e_l_e_t_e + _7_._4_._2_4_5 _s_c_o_r_e___t_h_r_e_s_h_o_l_d___d_e_l_e_t_e Type: number @@ -7633,7 +7694,7 @@ scores are always greater than or equal to zero, the default setting of this variable will never mark a message for deletion. - _7_._4_._2_4_5 _s_c_o_r_e___t_h_r_e_s_h_o_l_d___f_l_a_g + _7_._4_._2_4_6 _s_c_o_r_e___t_h_r_e_s_h_o_l_d___f_l_a_g Type: number @@ -7642,7 +7703,7 @@ Messages which have been assigned a score greater than or equal to this vari- able's value are automatically marked ``flagged''. - _7_._4_._2_4_6 _s_c_o_r_e___t_h_r_e_s_h_o_l_d___r_e_a_d + _7_._4_._2_4_7 _s_c_o_r_e___t_h_r_e_s_h_o_l_d___r_e_a_d Type: number @@ -7653,7 +7714,9 @@ scores are always greater than or equal to zero, the default setting of this variable will never mark a message read. - _7_._4_._2_4_7 _s_e_n_d___c_h_a_r_s_e_t + _7_._4_._2_4_8 _s_e_n_d___c_h_a_r_s_e_t + + The Mutt Next Generation E-Mail Client 147 Type: string @@ -7666,27 +7729,24 @@ standard character set (such as iso-8859-2, koi8-r or iso-2022-jp) either instead of or after iso-8859-1. - _7_._4_._2_4_8 _s_e_n_d_m_a_i_l + _7_._4_._2_4_9 _s_e_n_d_m_a_i_l Type: path Default: '/usr/sbin/sendmail -oem -oi' Specifies the program and arguments used to deliver mail sent by Mutt-ng. - - The Mutt Next Generation E-Mail Client 146 - Mutt-ng expects that the specified program interprets additional arguments as recipient addresses. - _7_._4_._2_4_9 _s_e_n_d_m_a_i_l___w_a_i_t + _7_._4_._2_5_0 _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 7.4.248 , - page 145)'' 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.249 , + page 146)'' process to finish before giving up and putting delivery in the background. Mutt-ng interprets the value of this variable as follows: @@ -7704,7 +7764,7 @@ will be put in a temporary file. If there is some error, you will be informed as to where to find the output. - _7_._4_._2_5_0 _s_h_e_l_l + _7_._4_._2_5_1 _s_h_e_l_l Type: path @@ -7713,29 +7773,28 @@ Command to use when spawning a subshell. By default, the user's login shell from /etc/passwd is used. - _7_._4_._2_5_1 _s_i_d_e_b_a_r___b_o_u_n_d_a_r_y + The Mutt Next Generation E-Mail Client 148 + + _7_._4_._2_5_2 _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 - 7.4.255 , page 147) is _s_e_t, this variable specifies the characters at which to + 7.4.256 , page 148) is _s_e_t, this variable specifies the characters at which to split a folder name into ``hierarchy items.'' - _7_._4_._2_5_2 _s_i_d_e_b_a_r___d_e_l_i_m + _7_._4_._2_5_3 _s_i_d_e_b_a_r___d_e_l_i_m Type: string Default: '|' This specifies the delimiter between the sidebar (if visible) and other - - The Mutt Next Generation E-Mail Client 147 - screens. - _7_._4_._2_5_3 _s_i_d_e_b_a_r___n_e_w_m_a_i_l___o_n_l_y + _7_._4_._2_5_4 _s_i_d_e_b_a_r___n_e_w_m_a_i_l___o_n_l_y Type: boolean @@ -7743,7 +7802,7 @@ If _s_e_t, only folders with new mail will be shown in the sidebar. - _7_._4_._2_5_4 _s_i_d_e_b_a_r___n_u_m_b_e_r___f_o_r_m_a_t + _7_._4_._2_5_5 _s_i_d_e_b_a_r___n_u_m_b_e_r___f_o_r_m_a_t Type: string @@ -7769,6 +7828,8 @@ %M Total number of messages shown, i.e. not hidden by a limit. 1) + The Mutt Next Generation E-Mail Client 149 + %n Number of new messages. @@ -7778,7 +7839,7 @@ 1) These expandos only have a non-zero value for the current mailbox and will always be zero otherwise. - _7_._4_._2_5_5 _s_i_d_e_b_a_r___s_h_o_r_t_e_n___h_i_e_r_a_r_c_h_y + _7_._4_._2_5_6 _s_i_d_e_b_a_r___s_h_o_r_t_e_n___h_i_e_r_a_r_c_h_y Type: boolean @@ -7786,18 +7847,15 @@ 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 - 7.4.257 , page 148)'' is set to a too low value). For example, if the - - The Mutt Next Generation E-Mail Client 148 - - newsgroup 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. + 7.4.258 , page 148)'' 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 7.4.251 , page 146) variable. + _b_a_r___b_o_u_n_d_a_r_y (section 7.4.252 , page 146) variable. - _7_._4_._2_5_6 _s_i_d_e_b_a_r___v_i_s_i_b_l_e + _7_._4_._2_5_7 _s_i_d_e_b_a_r___v_i_s_i_b_l_e Type: boolean @@ -7806,7 +7864,7 @@ This specifies whether or not to show the sidebar (a list of folders specified with the ``mailboxes'' command). - _7_._4_._2_5_7 _s_i_d_e_b_a_r___w_i_d_t_h + _7_._4_._2_5_8 _s_i_d_e_b_a_r___w_i_d_t_h Type: number @@ -7814,22 +7872,24 @@ The width of the sidebar. - _7_._4_._2_5_8 _s_i_g___d_a_s_h_e_s + _7_._4_._2_5_9 _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 7.4.260 , page 148)''. It is ssttrroonnggllyy recommended + your ``_$_s_i_g_n_a_t_u_r_e (section 7.4.261 , page 149)''. 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. + The Mutt Next Generation E-Mail Client 150 + For example, Mutt-ng has the ability to highlight the signature in a different color in the builtin pager. - _7_._4_._2_5_9 _s_i_g___o_n___t_o_p + _7_._4_._2_6_0 _s_i_g___o_n___t_o_p Type: boolean @@ -7840,19 +7900,17 @@ know what you are doing, and are prepared to take some heat from netiquette guardians. - _7_._4_._2_6_0 _s_i_g_n_a_t_u_r_e + _7_._4_._2_6_1 _s_i_g_n_a_t_u_r_e Type: path - The Mutt Next Generation E-Mail Client 149 - Default: '~/.signature' Specifies the filename of your signature, which is appended to all outgoing 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. - _7_._4_._2_6_1 _s_i_g_n_o_f_f___s_t_r_i_n_g + _7_._4_._2_6_2 _s_i_g_n_o_f_f___s_t_r_i_n_g Type: string @@ -7865,7 +7923,7 @@ witty quotes into your mails, better use a signature file instead of the sig- noff string. - _7_._4_._2_6_2 _s_i_m_p_l_e___s_e_a_r_c_h + _7_._4_._2_6_3 _s_i_m_p_l_e___s_e_a_r_c_h Type: string @@ -7881,7 +7939,9 @@ ~f joe | ~s joe - _7_._4_._2_6_3 _s_l_e_e_p___t_i_m_e + The Mutt Next Generation E-Mail Client 151 + + _7_._4_._2_6_4 _s_l_e_e_p___t_i_m_e Type: number @@ -7892,7 +7952,7 @@ the current folder. The default is to pause one second, so a value of zero for this option suppresses the pause. - _7_._4_._2_6_4 _s_m_a_r_t___w_r_a_p + _7_._4_._2_6_5 _s_m_a_r_t___w_r_a_p Type: boolean @@ -7900,23 +7960,20 @@ Controls the display of lines longer than the screen width in the internal pager. If _s_e_t, long lines are wrapped at a word boundary. If _u_n_s_e_t, lines are + simply wrapped at the screen edge. Also see the ``_$_m_a_r_k_e_r_s (section 7.4.122 , + page 116)'' variable. - The Mutt Next Generation E-Mail Client 150 - - simply wrapped at the screen edge. Also see the ``_$_m_a_r_k_e_r_s (section 7.4.121 , - page 115)'' variable. - - _7_._4_._2_6_5 _s_m_i_l_e_y_s + _7_._4_._2_6_6 _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 7.4.226 , page 140)'', most notably smileys in the + ``_$_q_u_o_t_e___r_e_g_e_x_p (section 7.4.227 , page 140)'', most notably smileys in the beginning of a line - _7_._4_._2_6_6 _s_m_i_m_e___a_s_k___c_e_r_t___l_a_b_e_l + _7_._4_._2_6_7 _s_m_i_m_e___a_s_k___c_e_r_t___l_a_b_e_l Type: boolean @@ -7926,7 +7983,7 @@ cate about to be added to the database or not. It is _s_e_t by default. (S/MIME only) - _7_._4_._2_6_7 _s_m_i_m_e___c_a___l_o_c_a_t_i_o_n + _7_._4_._2_6_8 _s_m_i_m_e___c_a___l_o_c_a_t_i_o_n Type: path @@ -7935,10 +7992,12 @@ This variable contains the name of either a directory, or a file which contains trusted certificates for use with OpenSSL. (S/MIME only) - _7_._4_._2_6_8 _s_m_i_m_e___c_e_r_t_i_f_i_c_a_t_e_s + _7_._4_._2_6_9 _s_m_i_m_e___c_e_r_t_i_f_i_c_a_t_e_s Type: path + The Mutt Next Generation E-Mail Client 152 + Default: '' Since there is no pubring/secring as with PGP, Mutt-ng has to handle storage @@ -7948,7 +8007,7 @@ address keyid pairs, and which can be manually edited. This one points to the location of the certificates. (S/MIME only) - _7_._4_._2_6_9 _s_m_i_m_e___d_e_c_r_y_p_t___c_o_m_m_a_n_d + _7_._4_._2_7_0 _s_m_i_m_e___d_e_c_r_y_p_t___c_o_m_m_a_n_d Type: string @@ -7957,8 +8016,6 @@ This format string specifies a command which is used to decrypt application/x- pkcs7-mime attachments. - The Mutt Next Generation E-Mail Client 151 - The OpenSSL command formats have their own set of printf(3)-like sequences sim- ilar to PGP's: @@ -7970,7 +8027,7 @@ 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 7.4.271 , + The key-pair specified with _$_s_m_i_m_e___d_e_f_a_u_l_t___k_e_y (section 7.4.272 , page 151) %c @@ -7981,26 +8038,28 @@ %C CA location: Depending on whether _$_s_m_i_m_e___c_a___l_o_c_a_t_i_o_n (section - 7.4.267 , page 150) 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.267 , page 150)' or - '-CAfile _$_s_m_i_m_e___c_a___l_o_c_a_t_i_o_n (section 7.4.267 , page 150)'. + 7.4.268 , page 150) 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.268 , page 150)' or + '-CAfile _$_s_m_i_m_e___c_a___l_o_c_a_t_i_o_n (section 7.4.268 , page 150)'. 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) - _7_._4_._2_7_0 _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_7_1 _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 Default: yes + The Mutt Next Generation E-Mail Client 153 + If _s_e_t (default) this tells Mutt-ng to use the default key for decryption. Oth- erwise, if manage multiple certificate-key-pairs, Mutt-ng will try to use the 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) - _7_._4_._2_7_1 _s_m_i_m_e___d_e_f_a_u_l_t___k_e_y + _7_._4_._2_7_2 _s_m_i_m_e___d_e_f_a_u_l_t___k_e_y Type: string @@ -8009,17 +8068,15 @@ 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) - _7_._4_._2_7_2 _s_m_i_m_e___e_n_c_r_y_p_t___c_o_m_m_a_n_d + _7_._4_._2_7_3 _s_m_i_m_e___e_n_c_r_y_p_t___c_o_m_m_a_n_d Type: string - The Mutt Next Generation E-Mail Client 152 - Default: '' This command is used to create encrypted S/MIME messages. (S/MIME only) - _7_._4_._2_7_3 _s_m_i_m_e___e_n_c_r_y_p_t___w_i_t_h + _7_._4_._2_7_4 _s_m_i_m_e___e_n_c_r_y_p_t___w_i_t_h Type: string @@ -8030,7 +8087,7 @@ If _u_n_s_e_t ``_3_d_e_s'' (TripleDES) is used. (S/MIME only) - _7_._4_._2_7_4 _s_m_i_m_e___g_e_t___c_e_r_t___c_o_m_m_a_n_d + _7_._4_._2_7_5 _s_m_i_m_e___g_e_t___c_e_r_t___c_o_m_m_a_n_d Type: string @@ -8039,7 +8096,7 @@ This command is used to extract X509 certificates from a PKCS7 structure. (S/MIME only) - _7_._4_._2_7_5 _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_7_6 _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 @@ -8049,7 +8106,9 @@ tificates, and for verification purposes (to check whether the certificate was issued for the sender's mailbox). (S/MIME only) - _7_._4_._2_7_6 _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_7_7 _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 + + The Mutt Next Generation E-Mail Client 154 Type: string @@ -8059,7 +8118,7 @@ signature, so that the certificate's owner may get compared to the email's ``From:'' header field. (S/MIME only) - _7_._4_._2_7_7 _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_7_8 _s_m_i_m_e___i_m_p_o_r_t___c_e_r_t___c_o_m_m_a_n_d Type: string @@ -8067,9 +8126,7 @@ This command is used to import a certificate via smime_keysng. (S/MIME only) - _7_._4_._2_7_8 _s_m_i_m_e___i_s___d_e_f_a_u_l_t - - The Mutt Next Generation E-Mail Client 153 + _7_._4_._2_7_9 _s_m_i_m_e___i_s___d_e_f_a_u_l_t Type: boolean @@ -8084,7 +8141,7 @@ (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 7.4.37 , page 94).) (S/MIME only) - _7_._4_._2_7_9 _s_m_i_m_e___k_e_y_s + _7_._4_._2_8_0 _s_m_i_m_e___k_e_y_s Type: path @@ -8097,7 +8154,7 @@ address keyid pair, and which can be manually edited. This one points to the location of the private keys. (S/MIME only) - _7_._4_._2_8_0 _s_m_i_m_e___p_k_7_o_u_t___c_o_m_m_a_n_d + _7_._4_._2_8_1 _s_m_i_m_e___p_k_7_o_u_t___c_o_m_m_a_n_d Type: string @@ -8106,7 +8163,9 @@ This command is used to extract PKCS7 structures of S/MIME signatures, in order to extract the public X509 certificate(s). (S/MIME only) - _7_._4_._2_8_1 _s_m_i_m_e___s_i_g_n___c_o_m_m_a_n_d + The Mutt Next Generation E-Mail Client 155 + + _7_._4_._2_8_2 _s_m_i_m_e___s_i_g_n___c_o_m_m_a_n_d Type: string @@ -8115,7 +8174,7 @@ This command is used to created S/MIME signatures of type multipart/signed, which can be read by all mail clients. (S/MIME only) - _7_._4_._2_8_2 _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_8_3 _s_m_i_m_e___s_i_g_n___o_p_a_q_u_e___c_o_m_m_a_n_d Type: string @@ -8125,9 +8184,7 @@ pkcs7-signature, which can only be handled by mail clients supporting the S/MIME extension. (S/MIME only) - The Mutt Next Generation E-Mail Client 154 - - _7_._4_._2_8_3 _s_m_i_m_e___t_i_m_e_o_u_t + _7_._4_._2_8_4 _s_m_i_m_e___t_i_m_e_o_u_t Type: number @@ -8136,7 +8193,7 @@ The number of seconds after which a cached passphrase will expire if not used. (S/MIME only) - _7_._4_._2_8_4 _s_m_i_m_e___v_e_r_i_f_y___c_o_m_m_a_n_d + _7_._4_._2_8_5 _s_m_i_m_e___v_e_r_i_f_y___c_o_m_m_a_n_d Type: string @@ -8145,7 +8202,7 @@ This command is used to verify S/MIME signatures of type multipart/signed. (S/MIME only) - _7_._4_._2_8_5 _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_8_6 _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 @@ -8154,7 +8211,7 @@ This command is used to verify S/MIME signatures of type application/x- pkcs7-mime. (S/MIME only) - _7_._4_._2_8_6 _s_m_t_p___e_n_v_e_l_o_p_e + _7_._4_._2_8_7 _s_m_t_p___e_n_v_e_l_o_p_e Type: string @@ -8162,6 +8219,8 @@ Availability: SMTP + The Mutt Next Generation E-Mail Client 156 + 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. @@ -8169,7 +8228,7 @@ envelope sender but only a particular one which may not be the same as the user's desired From: header. - _7_._4_._2_8_7 _s_m_t_p___h_o_s_t + _7_._4_._2_8_8 _s_m_t_p___h_o_s_t Type: string @@ -8179,11 +8238,9 @@ Defines the SMTP host which will be used to deliver mail, as opposed to invok- ing the sendmail binary. Setting this variable overrides the value of ``_$_s_e_n_d_- - _m_a_i_l (section 7.4.248 , page 145)'', and any associated variables. + _m_a_i_l (section 7.4.249 , page 146)'', and any associated variables. - The Mutt Next Generation E-Mail Client 155 - - _7_._4_._2_8_8 _s_m_t_p___p_a_s_s + _7_._4_._2_8_9 _s_m_t_p___p_a_s_s Type: string @@ -8192,13 +8249,13 @@ Availability: SMTP Defines the password to use with SMTP AUTH. If ``_$_s_m_t_p___u_s_e_r (section - 7.4.291 , page 155)'' is set, but this variable is not, you will be prompted + 7.4.292 , page 155)'' 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. - _7_._4_._2_8_9 _s_m_t_p___p_o_r_t + _7_._4_._2_9_0 _s_m_t_p___p_o_r_t Type: number @@ -8212,12 +8269,14 @@ Defaults to 25, the standard SMTP port, but RFC 2476-compliant SMTP servers will probably desire 587, the mail submission port. - _7_._4_._2_9_0 _s_m_t_p___u_s_e___t_l_s + _7_._4_._2_9_1 _s_m_t_p___u_s_e___t_l_s Type: string Default: '' + The Mutt Next Generation E-Mail Client 157 + 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 @@ -8226,7 +8285,7 @@ continue without TLS in case of an error. Muttng still needs to have SSL sup- port enabled in order to use it. - _7_._4_._2_9_1 _s_m_t_p___u_s_e_r + _7_._4_._2_9_2 _s_m_t_p___u_s_e_r Type: string @@ -8237,9 +8296,7 @@ Defines the username to use with SMTP AUTH. Setting this variable will cause Mutt-ng to attempt to use SMTP AUTH when sending. - The Mutt Next Generation E-Mail Client 156 - - _7_._4_._2_9_2 _s_o_r_t + _7_._4_._2_9_3 _s_o_r_t Type: sort order @@ -8261,7 +8318,7 @@ You may optionally use the ``reverse-'' prefix to specify reverse sorting order (example: set sort=reverse-date-sent). - _7_._4_._2_9_3 _s_o_r_t___a_l_i_a_s + _7_._4_._2_9_4 _s_o_r_t___a_l_i_a_s Type: sort order @@ -8270,11 +8327,13 @@ Specifies how the entries in the ``alias'' menu are sorted. The following are legal values: + The Mutt Next Generation E-Mail Client 158 + address (sort alphabetically by email address) alias (sort alphabetically by alias name) unsorted (leave in order specified in .muttrc) - _7_._4_._2_9_4 _s_o_r_t___a_u_x + _7_._4_._2_9_5 _s_o_r_t___a_u_x Type: sort order @@ -8282,24 +8341,22 @@ 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 7.4.292 , page 155)'' can, + This can be set to any value that ``_$_s_o_r_t (section 7.4.293 , page 156)'' 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 siblings by which has the last descendant, using the rest of sort_aux as an ordering. - The Mutt Next Generation E-Mail Client 157 - For instance, set sort_aux=last-date-received would mean that if a new message 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 7.4.292 , page 155)'' order _$_s_o_r_t___a_u_x - (section 7.4.294 , page 156) is reversed again (which is not the right thing + NNoottee:: For reversed ``_$_s_o_r_t (section 7.4.293 , page 156)'' order _$_s_o_r_t___a_u_x + (section 7.4.295 , page 156) is reversed again (which is not the right thing to do, but kept to not break any existing configuration setting). - _7_._4_._2_9_5 _s_o_r_t___b_r_o_w_s_e_r + _7_._4_._2_9_6 _s_o_r_t___b_r_o_w_s_e_r Type: sort order @@ -8316,37 +8373,38 @@ You may optionally use the ``reverse-'' prefix to specify reverse sorting order (example: set sort_browser=reverse-date). - _7_._4_._2_9_6 _s_o_r_t___r_e + _7_._4_._2_9_7 _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 7.4.313 , page 163)'' _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.296 , + + The Mutt Next Generation E-Mail Client 159 + + (section 7.4.314 , page 163)'' _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.297 , page 157) _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 7.4.232 , page 141)''. With - _$_s_o_r_t___r_e (section 7.4.296 , page 157) _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.233 , page 142)''. With + _$_s_o_r_t___r_e (section 7.4.297 , page 157) _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 - 7.4.232 , page 141)'' parts of both messages are identical. + 7.4.233 , page 142)'' parts of both messages are identical. - _7_._4_._2_9_7 _s_p_a_m___s_e_p_a_r_a_t_o_r + _7_._4_._2_9_8 _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 7.4.297 , page 157)'' controls what happens when + ``_s_p_a_m___s_e_p_a_r_a_t_o_r (section 7.4.298 , page 157)'' 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 7.4.297 , + match will append to the previous, using ``_s_p_a_m___s_e_p_a_r_a_t_o_r (section 7.4.298 , page 157)'' as a separator. - The Mutt Next Generation E-Mail Client 158 - - _7_._4_._2_9_8 _s_p_o_o_l_f_i_l_e + _7_._4_._2_9_9 _s_p_o_o_l_f_i_l_e Type: path @@ -8357,7 +8415,7 @@ set this variable to the value of the environment variable $MAIL if it is not set. - _7_._4_._2_9_9 _s_s_l___c_a___c_e_r_t_i_f_i_c_a_t_e_s___f_i_l_e + _7_._4_._3_0_0 _s_s_l___c_a___c_e_r_t_i_f_i_c_a_t_e_s___f_i_l_e Type: path @@ -8369,7 +8427,7 @@ Example: set ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt - _7_._4_._3_0_0 _s_s_l___c_l_i_e_n_t___c_e_r_t + _7_._4_._3_0_1 _s_s_l___c_l_i_e_n_t___c_e_r_t Type: path @@ -8379,7 +8437,9 @@ The file containing a client certificate and its associated private key. - _7_._4_._3_0_1 _s_s_l___f_o_r_c_e___t_l_s + The Mutt Next Generation E-Mail Client 160 + + _7_._4_._3_0_2 _s_s_l___f_o_r_c_e___t_l_s Type: boolean @@ -8389,9 +8449,9 @@ 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.303 , page 158)''. + 7.4.304 , page 159)''. - _7_._4_._3_0_2 _s_s_l___m_i_n___d_h___p_r_i_m_e___b_i_t_s + _7_._4_._3_0_3 _s_s_l___m_i_n___d_h___p_r_i_m_e___b_i_t_s Type: number @@ -8400,13 +8460,10 @@ Availability: GNUTLS This variable specifies the minimum acceptable prime size (in bits) for use in - - The Mutt Next Generation E-Mail Client 159 - any Diffie-Hellman key exchange. A value of 0 will use the default from the GNUTLS library. - _7_._4_._3_0_3 _s_s_l___s_t_a_r_t_t_l_s + _7_._4_._3_0_4 _s_s_l___s_t_a_r_t_t_l_s Type: quadoption @@ -8418,7 +8475,7 @@ ing the capability. When _u_n_s_e_t, Mutt-ng will not attempt to use STARTTLS regardless of the server's capabilities. - _7_._4_._3_0_4 _s_s_l___u_s_e___s_s_l_v_2 + _7_._4_._3_0_5 _s_s_l___u_s_e___s_s_l_v_2 Type: boolean @@ -8429,7 +8486,7 @@ This variables specifies whether to attempt to use SSLv2 in the SSL authentica- tion process. - _7_._4_._3_0_5 _s_s_l___u_s_e___s_s_l_v_3 + _7_._4_._3_0_6 _s_s_l___u_s_e___s_s_l_v_3 Type: boolean @@ -8437,10 +8494,12 @@ Availability: SSL or GNUTLS + The Mutt Next Generation E-Mail Client 161 + This variables specifies whether to attempt to use SSLv3 in the SSL authentica- tion process. - _7_._4_._3_0_6 _s_s_l___u_s_e___t_l_s_v_1 + _7_._4_._3_0_7 _s_s_l___u_s_e___t_l_s_v_1 Type: boolean @@ -8451,27 +8510,25 @@ This variables specifies whether to attempt to use TLSv1 in the SSL authentica- tion process. - _7_._4_._3_0_7 _s_s_l___u_s_e_s_y_s_t_e_m_c_e_r_t_s + _7_._4_._3_0_8 _s_s_l___u_s_e_s_y_s_t_e_m_c_e_r_t_s Type: boolean Default: yes - The Mutt Next Generation E-Mail Client 160 - Availability: SSL 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. - _7_._4_._3_0_8 _s_t_a_t_u_s___c_h_a_r_s + _7_._4_._3_0_9 _s_t_a_t_u_s___c_h_a_r_s Type: string Default: '-*%A' Controls the characters used by the ``%r'' indicator in ``_$_s_t_a_t_u_s___f_o_r_m_a_t (sec- - tion 7.4.309 , page 160)''. The first character is used when the mailbox is + tion 7.4.310 , page 160)''. 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 @@ -8480,7 +8537,7 @@ been opened in attach-message mode (Certain operations like composing a new mail, replying, forwarding, etc. are not permitted in this mode). - _7_._4_._3_0_9 _s_t_a_t_u_s___f_o_r_m_a_t + _7_._4_._3_1_0 _s_t_a_t_u_s___f_o_r_m_a_t Type: string @@ -8489,9 +8546,11 @@ %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 7.4.110 , page 111)'', but has + string is similar to ``_$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.111 , page 111)'', but has its own set of printf(3)-like sequences: + The Mutt Next Generation E-Mail Client 162 + %b number of mailboxes with new mail * @@ -8513,8 +8572,6 @@ %l size (in bytes) of the current mailbox * - The Mutt Next Generation E-Mail Client 161 - %L size (in bytes) of the messages shown (i.e., which match the cur- rent limit) * @@ -8540,15 +8597,17 @@ %r modified/read-only/won't-write/attach-message indicator, according - to _$_s_t_a_t_u_s___c_h_a_r_s (section 7.4.308 , page 159) + to _$_s_t_a_t_u_s___c_h_a_r_s (section 7.4.309 , page 160) %s - current sorting mode (_$_s_o_r_t (section 7.4.292 , page 155)) + current sorting mode (_$_s_o_r_t (section 7.4.293 , page 156)) %S - current aux sorting method (_$_s_o_r_t___a_u_x (section 7.4.294 , page + current aux sorting method (_$_s_o_r_t___a_u_x (section 7.4.295 , page 156)) + The Mutt Next Generation E-Mail Client 163 + %t number of tagged messages * @@ -8569,8 +8628,6 @@ * = can be optionally printed if nonzero - The Mutt Next Generation E-Mail Client 162 - Some of the above sequences can be used to optionally print a string if their value is nonzero. For example, you may only want to see the number of flagged messages if such messages exist, since zero is not particularly meaningful. To @@ -8605,7 +8662,9 @@ replace any dots in the expansion by underscores. This might be helpful with IMAP folders that don't like dots in folder names. - _7_._4_._3_1_0 _s_t_a_t_u_s___o_n___t_o_p + The Mutt Next Generation E-Mail Client 164 + + _7_._4_._3_1_1 _s_t_a_t_u_s___o_n___t_o_p Type: boolean @@ -8614,7 +8673,7 @@ Setting this variable causes the ``status bar'' to be displayed on the first line of the screen rather than near the bottom. - _7_._4_._3_1_1 _s_t_r_i_c_t___m_a_i_l_t_o + _7_._4_._3_1_2 _s_t_r_i_c_t___m_a_i_l_t_o Type: boolean @@ -8622,17 +8681,14 @@ 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 7.4.54 , page 98)'' is unset. + ``_$_e_d_i_t___h_e_a_d_e_r_s (section 7.4.55 , page 98)'' is unset. If this variable is _s_e_t, mutt-ng is strict and allows anything to be changed. - - The Mutt Next Generation E-Mail Client 163 - 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 7.4.54 , page 98)'' is set to. + ``_$_e_d_i_t___h_e_a_d_e_r_s (section 7.4.55 , page 98)'' is set to. - _7_._4_._3_1_2 _s_t_r_i_c_t___m_i_m_e + _7_._4_._3_1_3 _s_t_r_i_c_t___m_i_m_e Type: boolean @@ -8647,43 +8703,43 @@ a single space to prevent the display of MIME-encoded ``Subject:'' header field from being devided into multiple lines. - _7_._4_._3_1_3 _s_t_r_i_c_t___t_h_r_e_a_d_s + _7_._4_._3_1_4 _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 7.4.292 , page 155)'' by mes- + ences:'' header fields when you ``_$_s_o_r_t (section 7.4.293 , page 156)'' 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. - _7_._4_._3_1_4 _s_t_r_i_p___w_a_s + _7_._4_._3_1_5 _s_t_r_i_p___w_a_s + + The Mutt Next Generation E-Mail Client 165 Type: boolean Default: no When _s_e_t, mutt-ng will remove the trailing part of the ``Subject:'' line which - matches _$_s_t_r_i_p___w_a_s___r_e_g_e_x (section 7.4.315 , page 163) when replying. This is + matches _$_s_t_r_i_p___w_a_s___r_e_g_e_x (section 7.4.316 , page 163) when replying. This is useful to properly react on subject changes and reduce ``subject noise.'' (esp. in Usenet) - _7_._4_._3_1_5 _s_t_r_i_p___w_a_s___r_e_g_e_x + _7_._4_._3_1_6 _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 7.4.314 , page 163) is _s_e_t, mutt-ng + When non-empty and _$_s_t_r_i_p___w_a_s (section 7.4.315 , page 163) is _s_e_t, mutt-ng will remove this trailing part of the ``Subject'' line when replying if it won't be empty afterwards. - The Mutt Next Generation E-Mail Client 164 - - _7_._4_._3_1_6 _s_t_u_f_f___q_u_o_t_e_d + _7_._4_._3_1_7 _s_t_u_f_f___q_u_o_t_e_d Type: boolean @@ -8692,7 +8748,7 @@ If _s_e_t, attachments with flowed format will have their quoting ``stuffed'', i.e. a space will be inserted between the quote characters and the actual text. - _7_._4_._3_1_7 _s_u_s_p_e_n_d + _7_._4_._3_1_8 _s_u_s_p_e_n_d Type: boolean @@ -8702,7 +8758,7 @@ usually CTRL+Z. This is useful if you run Mutt-ng inside an xterm using a com- mand like ``xterm -e muttng.'' - _7_._4_._3_1_8 _t_e_x_t___f_l_o_w_e_d + _7_._4_._3_1_9 _t_e_x_t___f_l_o_w_e_d Type: boolean @@ -8713,10 +8769,12 @@ 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 7.4.109 , page 111) is ignored when this + Note that _$_i_n_d_e_n_t___s_t_r_i_n_g (section 7.4.110 , page 111) is ignored when this option is set. - _7_._4_._3_1_9 _t_h_o_r_o_u_g_h___s_e_a_r_c_h + _7_._4_._3_2_0 _t_h_o_r_o_u_g_h___s_e_a_r_c_h + + The Mutt Next Generation E-Mail Client 166 Type: boolean @@ -8727,7 +8785,7 @@ to be searched are decoded before searching. If _u_n_s_e_t, messages are searched as they appear in the folder. - _7_._4_._3_2_0 _t_h_r_e_a_d___r_e_c_e_i_v_e_d + _7_._4_._3_2_1 _t_h_r_e_a_d___r_e_c_e_i_v_e_d Type: boolean @@ -8736,9 +8794,7 @@ When _s_e_t, Mutt-ng uses the date received rather than the date sent to thread messages by subject. - The Mutt Next Generation E-Mail Client 165 - - _7_._4_._3_2_1 _t_i_l_d_e + _7_._4_._3_2_2 _t_i_l_d_e Type: boolean @@ -8747,7 +8803,7 @@ When _s_e_t, the internal-pager will pad blank lines to the bottom of the screen with a tilde (~). - _7_._4_._3_2_2 _t_i_m_e_o_u_t + _7_._4_._3_2_3 _t_i_m_e_o_u_t Type: number @@ -8757,7 +8813,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. - _7_._4_._3_2_3 _t_m_p_d_i_r + _7_._4_._3_2_4 _t_m_p_d_i_r Type: path @@ -8768,12 +8824,14 @@ set, the environment variable $TMPDIR is used. If $TMPDIR is not set then '/tmp' is used. - _7_._4_._3_2_4 _t_o___c_h_a_r_s + _7_._4_._3_2_5 _t_o___c_h_a_r_s Type: string Default: ' +TCFL' + The Mutt Next Generation E-Mail Client 167 + Controls the character used to indicate mail addressed to you. The first char- 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 @@ -8784,7 +8842,7 @@ 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). - _7_._4_._3_2_5 _t_r_a_s_h + _7_._4_._3_2_6 _t_r_a_s_h Type: path @@ -8793,12 +8851,10 @@ If _s_e_t, this variable specifies the path of the trash folder where the mails marked for deletion will be moved, instead of being irremediably purged. - The Mutt Next Generation E-Mail Client 166 - NNoottee: When you delete a message in the trash folder, it is really deleted, so that there is no way to recover mail. - _7_._4_._3_2_6 _t_u_n_n_e_l + _7_._4_._3_2_7 _t_u_n_n_e_l Type: string @@ -8813,7 +8869,7 @@ NNoottee:: For this example to work you must be able to log in to the remote machine without having to enter a password. - _7_._4_._3_2_7 _u_m_a_s_k + _7_._4_._3_2_8 _u_m_a_s_k Type: number @@ -8822,7 +8878,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. - _7_._4_._3_2_8 _u_n_c_o_l_l_a_p_s_e___j_u_m_p + _7_._4_._3_2_9 _u_n_c_o_l_l_a_p_s_e___j_u_m_p Type: boolean @@ -8831,7 +8887,9 @@ When _s_e_t, Mutt-ng will jump to the next unread message, if any, when the cur- rent thread is _u_ncollapsed. - _7_._4_._3_2_9 _u_s_e___8_b_i_t_m_i_m_e + The Mutt Next Generation E-Mail Client 168 + + _7_._4_._3_3_0 _u_s_e___8_b_i_t_m_i_m_e Type: boolean @@ -8842,23 +8900,21 @@ with the SMTP support via libESMTP. Otherwise you may not be able to send mail. - When _s_e_t, Mutt-ng will either invoke ``_$_s_e_n_d_m_a_i_l (section 7.4.248 , page - 145)'' with the -B8BITMIME flag when sending 8-bit messages to enable ESMTP + When _s_e_t, Mutt-ng will either invoke ``_$_s_e_n_d_m_a_i_l (section 7.4.249 , page + 146)'' with the -B8BITMIME flag when sending 8-bit messages to enable ESMTP negotiation or tell libESMTP to do so. - _7_._4_._3_3_0 _u_s_e___d_o_m_a_i_n + _7_._4_._3_3_1 _u_s_e___d_o_m_a_i_n Type: boolean - The Mutt Next Generation E-Mail Client 167 - 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 7.4.89 , page 106)''. If _u_n_s_e_t, + tion) with the value of ``_$_h_o_s_t_n_a_m_e (section 7.4.90 , page 106)''. If _u_n_s_e_t, no addresses will be qualified. - _7_._4_._3_3_1 _u_s_e___f_r_o_m + _7_._4_._3_3_2 _u_s_e___f_r_o_m Type: boolean @@ -8866,9 +8922,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.15 , page 35)'' command. - _7_._4_._3_3_2 _u_s_e___i_d_n + _7_._4_._3_3_3 _u_s_e___i_d_n Type: boolean @@ -8881,17 +8937,19 @@ NNoottee:: You can use IDNs for addresses even if this is _u_n_s_e_t. This variable only affects decoding. - _7_._4_._3_3_3 _u_s_e___i_p_v_6 + _7_._4_._3_3_4 _u_s_e___i_p_v_6 Type: boolean Default: yes + The Mutt Next Generation E-Mail Client 169 + When _s_e_t, Mutt-ng will look for IPv6 addresses of hosts it tries to contact. If this option is _u_n_s_e_t, Mutt-ng will restrict itself to IPv4 addresses. Nor- mally, the default should work. - _7_._4_._3_3_4 _u_s_e_r___a_g_e_n_t + _7_._4_._3_3_5 _u_s_e_r___a_g_e_n_t Type: boolean @@ -8900,18 +8958,16 @@ When _s_e_t, Mutt-ng will add a ``User-Agent:'' header to outgoing messages, indi- cating which version of Mutt-ng was used for composing them. - _7_._4_._3_3_5 _v_i_s_u_a_l + _7_._4_._3_3_6 _v_i_s_u_a_l Type: path Default: '' - The Mutt Next Generation E-Mail Client 168 - Specifies the visual editor to invoke when the _~_v command is given in the builtin editor. - _7_._4_._3_3_6 _w_a_i_t___k_e_y + _7_._4_._3_3_7 _w_a_i_t___k_e_y Type: boolean @@ -8927,7 +8983,7 @@ When _s_e_t, Mutt-ng will always ask for a key. When _u_n_s_e_t, Mutt-ng will wait for a key only if the external command returned a non-zero status. - _7_._4_._3_3_7 _w_e_e_d + _7_._4_._3_3_8 _w_e_e_d Type: boolean @@ -8936,7 +8992,7 @@ When _s_e_t, Mutt-ng will weed headers when displaying, forwarding, printing, or replying to messages. - _7_._4_._3_3_8 _w_r_a_p___s_e_a_r_c_h + _7_._4_._3_3_9 _w_r_a_p___s_e_a_r_c_h Type: boolean @@ -8944,10 +9000,12 @@ Controls whether searches wrap around the end of the mailbox. + The Mutt Next Generation E-Mail Client 170 + When _s_e_t, searches will wrap around the first (or last) message. When _u_n_s_e_t, searches will not wrap. - _7_._4_._3_3_9 _w_r_a_p_m_a_r_g_i_n + _7_._4_._3_4_0 _w_r_a_p_m_a_r_g_i_n Type: number @@ -8956,18 +9014,16 @@ Controls the size of the margin remaining at the right side of the terminal when Mutt-ng's pager does smart wrapping. - _7_._4_._3_4_0 _w_r_i_t_e___b_c_c + _7_._4_._3_4_1 _w_r_i_t_e___b_c_c Type: boolean Default: yes - The Mutt Next Generation E-Mail Client 169 - 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. - _7_._4_._3_4_1 _w_r_i_t_e___i_n_c + _7_._4_._3_4_2 _w_r_i_t_e___i_n_c Type: number @@ -8977,35 +9033,37 @@ 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 7.4.227 , page 140)'' variable. + Also see the ``_$_r_e_a_d___i_n_c (section 7.4.228 , page 141)'' variable. - _7_._4_._3_4_2 _x_t_e_r_m___i_c_o_n + _7_._4_._3_4_3 _x_t_e_r_m___i_c_o_n Type: string Default: 'M%?n?AIL&ail?' Controls the format of the X11 icon title, as long as _$_x_t_e_r_m___s_e_t___t_i_t_l_e_s (sec- - tion 7.4.344 , page 169) 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.309 , page 160)''. + tion 7.4.345 , page 169) 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.310 , page 160)''. - _7_._4_._3_4_3 _x_t_e_r_m___l_e_a_v_e + _7_._4_._3_4_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 7.4.344 , page 169) 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.345 , page 169) 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. + The Mutt Next Generation E-Mail Client 171 + Based on the xterm FAQ, the following might work: set xterm_leave = '`test x$DISPLAY != x && xprop -id $WINDOWID | grep WM_NAME | cut -d ''' -f 2`' - _7_._4_._3_4_4 _x_t_e_r_m___s_e_t___t_i_t_l_e_s + _7_._4_._3_4_5 _x_t_e_r_m___s_e_t___t_i_t_l_e_s Type: boolean @@ -9015,17 +9073,15 @@ you're in an appropriate terminal). The default must be _u_n_s_e_t to force in the validity checking. - _7_._4_._3_4_5 _x_t_e_r_m___t_i_t_l_e + _7_._4_._3_4_6 _x_t_e_r_m___t_i_t_l_e Type: string - The Mutt Next Generation E-Mail Client 170 - 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 7.4.344 , page 169) 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.309 , + _$_x_t_e_r_m___s_e_t___t_i_t_l_e_s (section 7.4.345 , page 169) 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.310 , page 160)''. _7_._5 _F_u_n_c_t_i_o_n_s @@ -9042,6 +9098,8 @@ tings for this menu will affect the default bindings for all menus (except as noted). + The Mutt Next Generation E-Mail Client 172 + 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 @@ -9074,11 +9132,9 @@ top-page H move to the top of the page what-key not bound display the keycode for a key press - The Mutt Next Generation E-Mail Client 171 - _7_._5_._2 _i_n_d_e_x - The Mutt Next Generation E-Mail Client 172 + The Mutt Next Generation E-Mail Client 173 bounce-message b remail a message to another user change-folder c open a different folder @@ -9135,7 +9191,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 173 + The Mutt Next Generation E-Mail Client 174 sort-mailbox o sort messages sort-reverse O sort messages in reverse order @@ -9153,7 +9209,7 @@ _7_._5_._3 _p_a_g_e_r - The Mutt Next Generation E-Mail Client 174 + The Mutt Next Generation E-Mail Client 175 bottom not bound jump to the bottom of the message bounce-message b remail a message to another user @@ -9210,7 +9266,7 @@ recall-message R recall a postponed message redraw-screen ^L clear and redraw the screen - The Mutt Next Generation E-Mail Client 175 + The Mutt Next Generation E-Mail Client 176 reply r reply to a message save-message s save message/attachment to a file @@ -9250,7 +9306,7 @@ _7_._5_._6 _a_t_t_a_c_h - The Mutt Next Generation E-Mail Client 176 + The Mutt Next Generation E-Mail Client 177 bounce-message b remail a message to another user collapse-parts v toggle display of subparts @@ -9273,7 +9329,7 @@ _7_._5_._7 _c_o_m_p_o_s_e - The Mutt Next Generation E-Mail Client 177 + The Mutt Next Generation E-Mail Client 178 attach-file a attach a file(s) to this message attach-message A attach message(s) to this message @@ -9316,7 +9372,7 @@ _7_._5_._9 _b_r_o_w_s_e_r - The Mutt Next Generation E-Mail Client 178 + The Mutt Next Generation E-Mail Client 179 change-dir c change directories check-new TAB check mailboxes for new mail @@ -9365,7 +9421,7 @@ _8_. _M_i_s_c_e_l_l_a_n_y - The Mutt Next Generation E-Mail Client 179 + The Mutt Next Generation E-Mail Client 180 _8_._1 _A_c_k_n_o_w_l_e_d_g_m_e_n_t_s @@ -9422,7 +9478,7 @@ Felix von Leitner (a.k.a ``Fefe'') , - The Mutt Next Generation E-Mail Client 180 + The Mutt Next Generation E-Mail Client 181 Brandon Long , @@ -9478,14 +9534,14 @@ Elimar Riesebieter - The Mutt Next Generation E-Mail Client 181 + The Mutt Next Generation E-Mail Client 182 _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 182 + The Mutt Next Generation E-Mail Client 183 CONTENTS @@ -9546,482 +9602,487 @@ 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.11 Format = Flowed .............................................. 31 + 3.11.1 Introduction 31 + 3.11.2 Receiving: Display Setup 31 + 3.11.3 Sending 32 + 3.11.4 Additional Notes 33 + 3.12 Mailing lists .................................................. 33 + 3.13 Using Multiple spool mailboxes ................................. 34 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.15 User defined headers ........................................... 35 + 3.16 Defining the order of headers when viewing messages ............ 36 + 3.17 Specify default save filename .................................. 36 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.19 Specify default save filename and default Fcc: mailbox at once . 37 + 3.20 Change settings based upon message recipients .................. 37 + 3.21 Change settings before formatting a message .................... 38 + 3.22 Choosing the cryptographic key of the recipient ................ 38 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.24 Executing functions ............................................ 39 + 3.25 Message Scoring ................................................ 39 + 3.26 Spam detection ................................................. 40 + 3.27 Setting variables .............................................. 42 + 3.28 Reading initialization commands from another file .............. 43 + 3.29 Removing hooks ................................................. 43 3.30 Sharing Setups ............................................. 43 3.30.1 Character Sets 43 - 3.30.2 Modularization 43 - 3.30.3 Conditional parts 43 - 3.31 Obsolete Variables ............................................. 45 + 3.30.2 Modularization 44 + 3.30.3 Conditional parts 44 + 3.31 Obsolete Variables ............................................. 46 - 4. Advanced Usage ....................................................... 45 - 4.1 Regular Expressions ............................................ 45 - 4.2 Patterns ....................................................... 48 + 4. Advanced Usage ....................................................... 46 + 4.1 Regular Expressions ............................................ 46 + 4.2 Patterns ....................................................... 49 4.2.1 Complex Patterns 49 - 4.2.2 Patterns and Dates 49 + 4.2.2 Patterns and Dates 50 4.3 Format Strings ............................................. 50 4.3.1 Introduction 50 - 4.3.2 Conditional Expansion 51 - 4.3.3 Modifications and Padding 52 + 4.3.2 Conditional Expansion 52 + 4.3.3 Modifications and Padding 53 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.5 Using Hooks .................................................... 54 + 4.5.1 Message Matching in Hooks 55 + 4.6 Using the sidebar .............................................. 55 + 4.7 External Address Queries ....................................... 56 + 4.8 Mailbox Formats ................................................ 57 + 4.9 Mailbox Shortcuts .............................................. 58 + 4.10 Handling Mailing Lists ......................................... 58 4.11 Editing threads ................................................ 59 - 4.11.1 Linking threads 59 - 4.11.2 Breaking threads 59 - 4.12 Delivery Status Notification (DSN) Support ..................... 59 - 4.13 POP3 Support (OPTIONAL) ........................................ 60 - 4.14 IMAP Support (OPTIONAL) ........................................ 60 + 4.11.1 Linking threads 60 ii - 4.14.1 The Folder Browser 61 + 4.11.2 Breaking threads 60 + 4.12 Delivery Status Notification (DSN) Support ..................... 60 + 4.13 POP3 Support (OPTIONAL) ........................................ 60 + 4.14 IMAP Support (OPTIONAL) ........................................ 61 + 4.14.1 The Folder Browser 62 4.14.2 Authentication 62 - 4.15 NNTP Support (OPTIONAL) ........................................ 62 + 4.15 NNTP Support (OPTIONAL) ........................................ 63 4.15.1 Again: Scoring 63 - 4.16 SMTP Support (OPTIONAL) ........................................ 63 - 4.17 Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) ............ 64 - 4.18 Start a WWW Browser on URLs (EXTERNAL) ......................... 64 + 4.16 SMTP Support (OPTIONAL) ........................................ 64 + 4.17 Managing multiple IMAP/POP/NNTP accounts (OPTIONAL) ............ 65 + 4.18 Start a WWW Browser on URLs (EXTERNAL) ......................... 65 4.19 Compressed folders Support (OPTIONAL) .......................... 65 - 4.19.1 Open a compressed mailbox for reading 65 + 4.19.1 Open a compressed mailbox for reading 66 4.19.2 Write a compressed mailbox 66 - 4.19.3 Append a message to a compressed mailbox 66 - 4.19.4 Encrypted folders 67 + 4.19.3 Append a message to a compressed mailbox 67 + 4.19.4 Encrypted folders 68 - 5. Mutt-ng's MIME Support ............................................... 67 - 5.1 Using MIME in Mutt ............................................. 67 + 5. Mutt-ng's MIME Support ............................................... 68 + 5.1 Using MIME in Mutt ............................................. 68 5.1.1 Viewing MIME messages in the pager 68 - 5.1.2 The Attachment Menu 68 - 5.1.3 The Compose Menu 68 + 5.1.2 The Attachment Menu 69 + 5.1.3 The Compose Menu 69 5.2 MIME Type configuration with mime.types ........................ 69 - 5.3 MIME Viewer configuration with mailcap ......................... 69 - 5.3.1 The Basics of the mailcap file 70 - 5.3.2 Secure use of mailcap 71 + 5.3 MIME Viewer configuration with mailcap ......................... 70 + 5.3.1 The Basics of the mailcap file 71 + 5.3.2 Secure use of mailcap 72 5.3.3 Advanced mailcap Usage 72 - 5.3.4 Example mailcap files 74 - 5.4 MIME Autoview .................................................. 75 - 5.5 MIME Multipart/Alternative ..................................... 76 - 5.6 MIME Lookup .................................................... 76 - - 6. Security Considerations ............................................ 77 - 6.1 Passwords .................................................. 77 - 6.2 Temporary Files ............................................ 77 + 5.3.4 Example mailcap files 75 + 5.4 MIME Autoview .................................................. 76 + 5.5 MIME Multipart/Alternative ..................................... 77 + 5.6 MIME Lookup .................................................... 77 + + 6. Security Considerations ............................................ 78 + 6.1 Passwords .................................................. 78 + 6.2 Temporary Files ............................................ 78 6.3 Information Leaks ............................................ 78 6.3.1 Message-ID: headers 78 - 6.3.2 mailto:-style links 78 - 6.4 External applications ...................................... 78 - 6.4.1 mailcap 78 - 6.4.2 Other 79 - - 7. Reference ............................................................ 79 - 7.1 Command line options ........................................... 79 - 7.2 Patterns ....................................................... 80 - 7.3 Configuration Commands ......................................... 82 - 7.4 Configuration variables .......................................... 84 - 7.4.1 abort_nosubject 85 - 7.4.2 abort_unmodified 86 - 7.4.3 alias_file 86 - 7.4.4 alias_format 86 - 7.4.5 allow_8bit 86 - 7.4.6 allow_ansi 87 - 7.4.7 arrow_cursor 87 - 7.4.8 ascii_chars 87 - 7.4.9 askbcc 87 - 7.4.10 askcc 87 + 6.3.2 mailto:-style links 79 + 6.4 External applications ...................................... 79 + 6.4.1 mailcap 79 + 6.4.2 Other 80 + + 7. Reference ............................................................ 80 + 7.1 Command line options ........................................... 80 + 7.2 Patterns ....................................................... 81 + 7.3 Configuration Commands ......................................... 83 + 7.4 Configuration variables .......................................... 85 + 7.4.1 abort_nosubject 86 + 7.4.2 abort_unmodified 87 + 7.4.3 alias_file 87 + 7.4.4 alias_format 87 + 7.4.5 allow_8bit 87 + 7.4.6 allow_ansi 88 iii - 7.4.11 assumed_charset 88 - 7.4.12 attach_format 88 - 7.4.13 attach_sep 89 - 7.4.14 attach_split 89 - 7.4.15 attribution 89 - 7.4.16 auto_tag 89 - 7.4.17 autoedit 90 - 7.4.18 beep 90 - 7.4.19 beep_new 90 - 7.4.20 bounce 90 - 7.4.21 bounce_delivered 90 - 7.4.22 braille_friendly 91 - 7.4.23 certificate_file 91 - 7.4.24 charset 91 - 7.4.25 check_new 91 - 7.4.26 collapse_unread 92 - 7.4.27 compose_format 92 - 7.4.28 config_charset 92 - 7.4.29 confirmappend 92 - 7.4.30 confirmcreate 93 - 7.4.31 connect_timeout 93 - 7.4.32 content_type 93 - 7.4.33 copy 93 - 7.4.34 crypt_autoencrypt 93 - 7.4.35 crypt_autopgp 94 - 7.4.36 crypt_autosign 94 - 7.4.37 crypt_autosmime 94 - 7.4.38 crypt_replyencrypt 94 - 7.4.39 crypt_replysign 94 - 7.4.40 crypt_replysignencrypted 95 - 7.4.41 crypt_timestamp 95 - 7.4.42 crypt_use_gpgme 95 - 7.4.43 crypt_verify_sig 95 - 7.4.44 date_format 95 - 7.4.45 default_hook 96 - 7.4.46 delete 96 - 7.4.47 delete_untag 96 - 7.4.48 digest_collapse 96 - 7.4.49 display_filter 97 - 7.4.50 dotlock_program 97 - 7.4.51 dsn_notify 97 - 7.4.52 dsn_return 97 - 7.4.53 duplicate_threads 98 - 7.4.54 edit_headers 98 - 7.4.55 editor 98 - 7.4.56 encode_from 98 - 7.4.57 entropy_file 98 - 7.4.58 envelope_from 99 - 7.4.59 escape 99 - 7.4.60 fast_reply 99 - 7.4.61 fcc_attach 99 - 7.4.62 fcc_clear 99 - 7.4.63 file_charset 99 + 7.4.7 arrow_cursor 88 + 7.4.8 ascii_chars 88 + 7.4.9 askbcc 88 + 7.4.10 askcc 88 + 7.4.11 assumed_charset 89 + 7.4.12 attach_format 89 + 7.4.13 attach_sep 90 + 7.4.14 attach_split 90 + 7.4.15 attribution 90 + 7.4.16 auto_tag 90 + 7.4.17 autoedit 91 + 7.4.18 beep 91 + 7.4.19 beep_new 91 + 7.4.20 bounce 91 + 7.4.21 bounce_delivered 91 + 7.4.22 braille_friendly 92 + 7.4.23 certificate_file 92 + 7.4.24 charset 92 + 7.4.25 check_new 92 + 7.4.26 collapse_unread 93 + 7.4.27 compose_format 93 + 7.4.28 config_charset 93 + 7.4.29 confirmappend 93 + 7.4.30 confirmcreate 94 + 7.4.31 connect_timeout 94 + 7.4.32 content_type 94 + 7.4.33 copy 94 + 7.4.34 crypt_autoencrypt 94 + 7.4.35 crypt_autopgp 95 + 7.4.36 crypt_autosign 95 + 7.4.37 crypt_autosmime 95 + 7.4.38 crypt_replyencrypt 95 + 7.4.39 crypt_replysign 95 + 7.4.40 crypt_replysignencrypted 96 + 7.4.41 crypt_timestamp 96 + 7.4.42 crypt_use_gpgme 96 + 7.4.43 crypt_verify_sig 96 + 7.4.44 date_format 96 + 7.4.45 default_hook 97 + 7.4.46 delete 97 + 7.4.47 delete_space 97 + 7.4.48 delete_untag 97 + 7.4.49 digest_collapse 98 + 7.4.50 display_filter 98 + 7.4.51 dotlock_program 98 + 7.4.52 dsn_notify 98 + 7.4.53 dsn_return 99 + 7.4.54 duplicate_threads 99 + 7.4.55 edit_headers 99 + 7.4.56 editor 99 + 7.4.57 encode_from 99 + 7.4.58 entropy_file 100 + 7.4.59 envelope_from 100 iv - 7.4.64 folder 100 - 7.4.65 folder_format 100 - 7.4.66 followup_to 101 - 7.4.67 force_buffy_check 101 - 7.4.68 force_name 101 - 7.4.69 forward_decode 102 - 7.4.70 forward_decrypt 102 - 7.4.71 forward_edit 102 - 7.4.72 forward_format 102 - 7.4.73 forward_quote 102 - 7.4.74 from 103 - 7.4.75 gecos_mask 103 - 7.4.76 hdrs 103 - 7.4.77 header 103 - 7.4.78 header_cache 104 - 7.4.79 header_cache_compress 104 - 7.4.80 help 104 - 7.4.81 hidden_host 104 - 7.4.82 hide_limited 105 - 7.4.83 hide_missing 105 - 7.4.84 hide_thread_subject 105 - 7.4.85 hide_top_limited 105 - 7.4.86 hide_top_missing 105 - 7.4.87 history 105 - 7.4.88 honor_followup_to 106 - 7.4.89 hostname 106 - 7.4.90 ignore_list_reply_to 106 - 7.4.91 imap_authenticators 106 - 7.4.92 imap_check_subscribed 107 - 7.4.93 imap_delim_chars 107 - 7.4.94 imap_headers 107 - 7.4.95 imap_home_namespace 107 - 7.4.96 imap_keepalive 108 - 7.4.97 imap_list_subscribed 108 - 7.4.98 imap_login 108 - 7.4.99 imap_mail_check 108 - 7.4.100 imap_pass 109 - 7.4.101 imap_passive 109 - 7.4.102 imap_peek 109 - 7.4.103 imap_reconnect 109 - 7.4.104 imap_servernoise 110 - 7.4.105 imap_user 110 - 7.4.106 implicit_autoview 110 - 7.4.107 include 110 - 7.4.108 include_onlyfirst 110 - 7.4.109 indent_string 111 - 7.4.110 index_format 111 - 7.4.111 ispell 113 - 7.4.112 keep_flagged 114 - 7.4.113 list_reply 114 - 7.4.114 locale 114 - 7.4.115 mail_check 114 - 7.4.116 mailcap_path 114 + 7.4.60 escape 100 + 7.4.61 fast_reply 100 + 7.4.62 fcc_attach 100 + 7.4.63 fcc_clear 101 + 7.4.64 file_charset 101 + 7.4.65 folder 101 + 7.4.66 folder_format 101 + 7.4.67 followup_to 102 + 7.4.68 force_buffy_check 103 + 7.4.69 force_name 103 + 7.4.70 forward_decode 103 + 7.4.71 forward_decrypt 103 + 7.4.72 forward_edit 103 + 7.4.73 forward_format 104 + 7.4.74 forward_quote 104 + 7.4.75 from 104 + 7.4.76 gecos_mask 104 + 7.4.77 hdrs 105 + 7.4.78 header 105 + 7.4.79 header_cache 105 + 7.4.80 header_cache_compress 105 + 7.4.81 help 105 + 7.4.82 hidden_host 106 + 7.4.83 hide_limited 106 + 7.4.84 hide_missing 106 + 7.4.85 hide_thread_subject 106 + 7.4.86 hide_top_limited 106 + 7.4.87 hide_top_missing 107 + 7.4.88 history 107 + 7.4.89 honor_followup_to 107 + 7.4.90 hostname 107 + 7.4.91 ignore_list_reply_to 107 + 7.4.92 imap_authenticators 108 + 7.4.93 imap_check_subscribed 108 + 7.4.94 imap_delim_chars 108 + 7.4.95 imap_headers 108 + 7.4.96 imap_home_namespace 109 + 7.4.97 imap_keepalive 109 + 7.4.98 imap_list_subscribed 109 + 7.4.99 imap_login 110 + 7.4.100 imap_mail_check 110 + 7.4.101 imap_pass 110 + 7.4.102 imap_passive 110 + 7.4.103 imap_peek 110 + 7.4.104 imap_reconnect 111 + 7.4.105 imap_servernoise 111 + 7.4.106 imap_user 111 + 7.4.107 implicit_autoview 111 + 7.4.108 include 112 + 7.4.109 include_onlyfirst 112 + 7.4.110 indent_string 112 + 7.4.111 index_format 112 + 7.4.112 ispell 115 v - 7.4.117 mailcap_sanitize 115 - 7.4.118 maildir_header_cache_verify 115 - 7.4.119 maildir_trash 115 - 7.4.120 mark_old 115 - 7.4.121 markers 116 - 7.4.122 mask 116 - 7.4.123 max_display_recips 116 - 7.4.124 max_line_length 116 - 7.4.125 mbox 116 - 7.4.126 mbox_type 116 - 7.4.127 menu_context 117 - 7.4.128 menu_move_off 117 - 7.4.129 menu_scroll 117 - 7.4.130 message_format 117 - 7.4.131 meta_key 117 - 7.4.132 metoo 118 - 7.4.133 mh_purge 118 - 7.4.134 mh_seq_flagged 118 - 7.4.135 mh_seq_replied 118 - 7.4.136 mh_seq_unseen 118 - 7.4.137 mime_forward 118 - 7.4.138 mime_forward_decode 119 - 7.4.139 mime_forward_rest 119 - 7.4.140 mix_entry_format 119 - 7.4.141 mixmaster 120 - 7.4.142 move 120 - 7.4.143 msgid_format 120 - 7.4.144 narrow_tree 121 - 7.4.145 nntp_ask_followup_to 121 - 7.4.146 nntp_ask_x_comment_to 121 - 7.4.147 nntp_cache_dir 122 - 7.4.148 nntp_catchup 122 - 7.4.149 nntp_context 122 - 7.4.150 nntp_followup_to_poster 122 - 7.4.151 nntp_group_index_format 123 - 7.4.152 nntp_host 123 - 7.4.153 nntp_inews 123 - 7.4.154 nntp_load_description 124 - 7.4.155 nntp_mail_check 124 - 7.4.156 nntp_mime_subject 124 - 7.4.157 nntp_newsrc 124 - 7.4.158 nntp_pass 125 - 7.4.159 nntp_post_moderated 125 - 7.4.160 nntp_reconnect 125 - 7.4.161 nntp_save_unsubscribed 125 - 7.4.162 nntp_show_new_news 126 - 7.4.163 nntp_show_only_unread 126 - 7.4.164 nntp_user 126 - 7.4.165 nntp_x_comment_to 126 - 7.4.166 operating_system 126 - 7.4.167 pager 127 - 7.4.168 pager_context 127 - 7.4.169 pager_format 127 + 7.4.113 keep_flagged 115 + 7.4.114 list_reply 115 + 7.4.115 locale 115 + 7.4.116 mail_check 116 + 7.4.117 mailcap_path 116 + 7.4.118 mailcap_sanitize 116 + 7.4.119 maildir_header_cache_verify 116 + 7.4.120 maildir_trash 116 + 7.4.121 mark_old 117 + 7.4.122 markers 117 + 7.4.123 mask 117 + 7.4.124 max_display_recips 117 + 7.4.125 max_line_length 117 + 7.4.126 mbox 118 + 7.4.127 mbox_type 118 + 7.4.128 menu_context 118 + 7.4.129 menu_move_off 118 + 7.4.130 menu_scroll 118 + 7.4.131 message_format 119 + 7.4.132 meta_key 119 + 7.4.133 metoo 119 + 7.4.134 mh_purge 119 + 7.4.135 mh_seq_flagged 119 + 7.4.136 mh_seq_replied 119 + 7.4.137 mh_seq_unseen 120 + 7.4.138 mime_forward 120 + 7.4.139 mime_forward_decode 120 + 7.4.140 mime_forward_rest 120 + 7.4.141 mix_entry_format 120 + 7.4.142 mixmaster 121 + 7.4.143 move 121 + 7.4.144 msgid_format 121 + 7.4.145 narrow_tree 122 + 7.4.146 nntp_ask_followup_to 122 + 7.4.147 nntp_ask_x_comment_to 123 + 7.4.148 nntp_cache_dir 123 + 7.4.149 nntp_catchup 123 + 7.4.150 nntp_context 123 + 7.4.151 nntp_followup_to_poster 124 + 7.4.152 nntp_group_index_format 124 + 7.4.153 nntp_host 124 + 7.4.154 nntp_inews 125 + 7.4.155 nntp_load_description 125 + 7.4.156 nntp_mail_check 125 + 7.4.157 nntp_mime_subject 125 + 7.4.158 nntp_newsrc 126 + 7.4.159 nntp_pass 126 + 7.4.160 nntp_post_moderated 126 + 7.4.161 nntp_reconnect 127 + 7.4.162 nntp_save_unsubscribed 127 + 7.4.163 nntp_show_new_news 127 + 7.4.164 nntp_show_only_unread 127 + 7.4.165 nntp_user 127 vi - 7.4.170 pager_index_lines 127 - 7.4.171 pager_stop 128 - 7.4.172 pgp_auto_decode 128 - 7.4.173 pgp_autoinline 128 - 7.4.174 pgp_check_exit 128 - 7.4.175 pgp_clearsign_command 129 - 7.4.176 pgp_decode_command 129 - 7.4.177 pgp_decrypt_command 129 - 7.4.178 pgp_encrypt_only_command 130 - 7.4.179 pgp_encrypt_sign_command 130 - 7.4.180 pgp_entry_format 130 - 7.4.181 pgp_export_command 131 - 7.4.182 pgp_getkeys_command 131 - 7.4.183 pgp_good_sign 131 - 7.4.184 pgp_ignore_subkeys 131 - 7.4.185 pgp_import_command 131 - 7.4.186 pgp_list_pubring_command 131 - 7.4.187 pgp_list_secring_command 132 - 7.4.188 pgp_long_ids 132 - 7.4.189 pgp_mime_auto 132 - 7.4.190 pgp_replyinline 132 - 7.4.191 pgp_retainable_sigs 133 - 7.4.192 pgp_show_unusable 133 - 7.4.193 pgp_sign_as 133 - 7.4.194 pgp_sign_command 133 - 7.4.195 pgp_sort_keys 133 - 7.4.196 pgp_strict_enc 134 - 7.4.197 pgp_timeout 134 - 7.4.198 pgp_use_gpg_agent 134 - 7.4.199 pgp_verify_command 134 - 7.4.200 pgp_verify_key_command 135 - 7.4.201 pipe_decode 135 - 7.4.202 pipe_sep 135 - 7.4.203 pipe_split 135 - 7.4.204 pop_auth_try_all 135 - 7.4.205 pop_authenticators 136 - 7.4.206 pop_delete 136 - 7.4.207 pop_host 136 - 7.4.208 pop_last 136 - 7.4.209 pop_mail_check 137 - 7.4.210 pop_pass 137 - 7.4.211 pop_reconnect 137 - 7.4.212 pop_user 137 - 7.4.213 post_indent_string 137 - 7.4.214 postpone 138 - 7.4.215 postponed 138 - 7.4.216 preconnect 138 - 7.4.217 print 138 - 7.4.218 print_command 139 - 7.4.219 print_decode 139 - 7.4.220 print_split 139 - 7.4.221 prompt_after 139 - 7.4.222 query_command 139 + 7.4.166 nntp_x_comment_to 128 + 7.4.167 operating_system 128 + 7.4.168 pager 128 + 7.4.169 pager_context 128 + 7.4.170 pager_format 129 + 7.4.171 pager_index_lines 129 + 7.4.172 pager_stop 129 + 7.4.173 pgp_auto_decode 129 + 7.4.174 pgp_autoinline 129 + 7.4.175 pgp_check_exit 130 + 7.4.176 pgp_clearsign_command 130 + 7.4.177 pgp_decode_command 130 + 7.4.178 pgp_decrypt_command 131 + 7.4.179 pgp_encrypt_only_command 131 + 7.4.180 pgp_encrypt_sign_command 131 + 7.4.181 pgp_entry_format 131 + 7.4.182 pgp_export_command 132 + 7.4.183 pgp_getkeys_command 132 + 7.4.184 pgp_good_sign 132 + 7.4.185 pgp_ignore_subkeys 132 + 7.4.186 pgp_import_command 133 + 7.4.187 pgp_list_pubring_command 133 + 7.4.188 pgp_list_secring_command 133 + 7.4.189 pgp_long_ids 133 + 7.4.190 pgp_mime_auto 133 + 7.4.191 pgp_replyinline 134 + 7.4.192 pgp_retainable_sigs 134 + 7.4.193 pgp_show_unusable 134 + 7.4.194 pgp_sign_as 134 + 7.4.195 pgp_sign_command 135 + 7.4.196 pgp_sort_keys 135 + 7.4.197 pgp_strict_enc 135 + 7.4.198 pgp_timeout 135 + 7.4.199 pgp_use_gpg_agent 136 + 7.4.200 pgp_verify_command 136 + 7.4.201 pgp_verify_key_command 136 + 7.4.202 pipe_decode 136 + 7.4.203 pipe_sep 136 + 7.4.204 pipe_split 136 + 7.4.205 pop_auth_try_all 137 + 7.4.206 pop_authenticators 137 + 7.4.207 pop_delete 137 + 7.4.208 pop_host 137 + 7.4.209 pop_last 138 + 7.4.210 pop_mail_check 138 + 7.4.211 pop_pass 138 + 7.4.212 pop_reconnect 138 + 7.4.213 pop_user 139 + 7.4.214 post_indent_string 139 + 7.4.215 postpone 139 + 7.4.216 postponed 139 + 7.4.217 preconnect 139 + 7.4.218 print 140 vii - 7.4.223 quit 140 - 7.4.224 quote_empty 140 - 7.4.225 quote_quoted 140 - 7.4.226 quote_regexp 140 - 7.4.227 read_inc 140 - 7.4.228 read_only 141 - 7.4.229 realname 141 - 7.4.230 recall 141 - 7.4.231 record 141 - 7.4.232 reply_regexp 142 - 7.4.233 reply_self 142 - 7.4.234 reply_to 142 - 7.4.235 resolve 142 - 7.4.236 reverse_alias 142 - 7.4.237 reverse_name 143 - 7.4.238 reverse_realname 143 - 7.4.239 rfc2047_parameters 143 - 7.4.240 save_address 144 - 7.4.241 save_empty 144 - 7.4.242 save_name 144 - 7.4.243 score 144 - 7.4.244 score_threshold_delete 145 - 7.4.245 score_threshold_flag 145 - 7.4.246 score_threshold_read 145 - 7.4.247 send_charset 145 - 7.4.248 sendmail 145 - 7.4.249 sendmail_wait 146 - 7.4.250 shell 146 - 7.4.251 sidebar_boundary 146 - 7.4.252 sidebar_delim 146 - 7.4.253 sidebar_newmail_only 147 - 7.4.254 sidebar_number_format 147 - 7.4.255 sidebar_shorten_hierarchy 147 - 7.4.256 sidebar_visible 148 - 7.4.257 sidebar_width 148 - 7.4.258 sig_dashes 148 - 7.4.259 sig_on_top 148 - 7.4.260 signature 148 - 7.4.261 signoff_string 149 - 7.4.262 simple_search 149 - 7.4.263 sleep_time 149 - 7.4.264 smart_wrap 149 - 7.4.265 smileys 150 - 7.4.266 smime_ask_cert_label 150 - 7.4.267 smime_ca_location 150 - 7.4.268 smime_certificates 150 - 7.4.269 smime_decrypt_command 150 - 7.4.270 smime_decrypt_use_default_key 151 - 7.4.271 smime_default_key 151 - 7.4.272 smime_encrypt_command 151 - 7.4.273 smime_encrypt_with 152 - 7.4.274 smime_get_cert_command 152 - 7.4.275 smime_get_cert_email_command 152 + 7.4.219 print_command 140 + 7.4.220 print_decode 140 + 7.4.221 print_split 140 + 7.4.222 prompt_after 141 + 7.4.223 query_command 141 + 7.4.224 quit 141 + 7.4.225 quote_empty 141 + 7.4.226 quote_quoted 141 + 7.4.227 quote_regexp 142 + 7.4.228 read_inc 142 + 7.4.229 read_only 142 + 7.4.230 realname 142 + 7.4.231 recall 142 + 7.4.232 record 143 + 7.4.233 reply_regexp 143 + 7.4.234 reply_self 143 + 7.4.235 reply_to 143 + 7.4.236 resolve 144 + 7.4.237 reverse_alias 144 + 7.4.238 reverse_name 144 + 7.4.239 reverse_realname 144 + 7.4.240 rfc2047_parameters 145 + 7.4.241 save_address 145 + 7.4.242 save_empty 145 + 7.4.243 save_name 145 + 7.4.244 score 146 + 7.4.245 score_threshold_delete 146 + 7.4.246 score_threshold_flag 146 + 7.4.247 score_threshold_read 146 + 7.4.248 send_charset 146 + 7.4.249 sendmail 147 + 7.4.250 sendmail_wait 147 + 7.4.251 shell 147 + 7.4.252 sidebar_boundary 148 + 7.4.253 sidebar_delim 148 + 7.4.254 sidebar_newmail_only 148 + 7.4.255 sidebar_number_format 148 + 7.4.256 sidebar_shorten_hierarchy 149 + 7.4.257 sidebar_visible 149 + 7.4.258 sidebar_width 149 + 7.4.259 sig_dashes 149 + 7.4.260 sig_on_top 150 + 7.4.261 signature 150 + 7.4.262 signoff_string 150 + 7.4.263 simple_search 150 + 7.4.264 sleep_time 151 + 7.4.265 smart_wrap 151 + 7.4.266 smileys 151 + 7.4.267 smime_ask_cert_label 151 + 7.4.268 smime_ca_location 151 + 7.4.269 smime_certificates 151 + 7.4.270 smime_decrypt_command 152 + 7.4.271 smime_decrypt_use_default_key 152 viii - 7.4.276 smime_get_signer_cert_command 152 - 7.4.277 smime_import_cert_command 152 - 7.4.278 smime_is_default 152 - 7.4.279 smime_keys 153 - 7.4.280 smime_pk7out_command 153 - 7.4.281 smime_sign_command 153 - 7.4.282 smime_sign_opaque_command 153 - 7.4.283 smime_timeout 154 - 7.4.284 smime_verify_command 154 - 7.4.285 smime_verify_opaque_command 154 - 7.4.286 smtp_envelope 154 - 7.4.287 smtp_host 154 - 7.4.288 smtp_pass 155 - 7.4.289 smtp_port 155 - 7.4.290 smtp_use_tls 155 - 7.4.291 smtp_user 155 - 7.4.292 sort 156 - 7.4.293 sort_alias 156 - 7.4.294 sort_aux 156 - 7.4.295 sort_browser 157 - 7.4.296 sort_re 157 - 7.4.297 spam_separator 157 - 7.4.298 spoolfile 158 - 7.4.299 ssl_ca_certificates_file 158 - 7.4.300 ssl_client_cert 158 - 7.4.301 ssl_force_tls 158 - 7.4.302 ssl_min_dh_prime_bits 158 - 7.4.303 ssl_starttls 159 - 7.4.304 ssl_use_sslv2 159 - 7.4.305 ssl_use_sslv3 159 - 7.4.306 ssl_use_tlsv1 159 - 7.4.307 ssl_usesystemcerts 159 - 7.4.308 status_chars 160 - 7.4.309 status_format 160 - 7.4.310 status_on_top 162 - 7.4.311 strict_mailto 162 - 7.4.312 strict_mime 163 - 7.4.313 strict_threads 163 - 7.4.314 strip_was 163 - 7.4.315 strip_was_regex 163 - 7.4.316 stuff_quoted 164 - 7.4.317 suspend 164 - 7.4.318 text_flowed 164 - 7.4.319 thorough_search 164 - 7.4.320 thread_received 164 - 7.4.321 tilde 165 - 7.4.322 timeout 165 - 7.4.323 tmpdir 165 - 7.4.324 to_chars 165 - 7.4.325 trash 165 - 7.4.326 tunnel 166 - 7.4.327 umask 166 - 7.4.328 uncollapse_jump 166 + 7.4.272 smime_default_key 153 + 7.4.273 smime_encrypt_command 153 + 7.4.274 smime_encrypt_with 153 + 7.4.275 smime_get_cert_command 153 + 7.4.276 smime_get_cert_email_command 153 + 7.4.277 smime_get_signer_cert_command 153 + 7.4.278 smime_import_cert_command 154 + 7.4.279 smime_is_default 154 + 7.4.280 smime_keys 154 + 7.4.281 smime_pk7out_command 154 + 7.4.282 smime_sign_command 155 + 7.4.283 smime_sign_opaque_command 155 + 7.4.284 smime_timeout 155 + 7.4.285 smime_verify_command 155 + 7.4.286 smime_verify_opaque_command 155 + 7.4.287 smtp_envelope 155 + 7.4.288 smtp_host 156 + 7.4.289 smtp_pass 156 + 7.4.290 smtp_port 156 + 7.4.291 smtp_use_tls 156 + 7.4.292 smtp_user 157 + 7.4.293 sort 157 + 7.4.294 sort_alias 157 + 7.4.295 sort_aux 158 + 7.4.296 sort_browser 158 + 7.4.297 sort_re 158 + 7.4.298 spam_separator 159 + 7.4.299 spoolfile 159 + 7.4.300 ssl_ca_certificates_file 159 + 7.4.301 ssl_client_cert 159 + 7.4.302 ssl_force_tls 160 + 7.4.303 ssl_min_dh_prime_bits 160 + 7.4.304 ssl_starttls 160 + 7.4.305 ssl_use_sslv2 160 + 7.4.306 ssl_use_sslv3 160 + 7.4.307 ssl_use_tlsv1 161 + 7.4.308 ssl_usesystemcerts 161 + 7.4.309 status_chars 161 + 7.4.310 status_format 161 + 7.4.311 status_on_top 164 + 7.4.312 strict_mailto 164 + 7.4.313 strict_mime 164 + 7.4.314 strict_threads 164 + 7.4.315 strip_was 164 + 7.4.316 strip_was_regex 165 + 7.4.317 stuff_quoted 165 + 7.4.318 suspend 165 + 7.4.319 text_flowed 165 + 7.4.320 thorough_search 165 + 7.4.321 thread_received 166 + 7.4.322 tilde 166 + 7.4.323 timeout 166 + 7.4.324 tmpdir 166 ix - 7.4.329 use_8bitmime 166 - 7.4.330 use_domain 166 - 7.4.331 use_from 167 - 7.4.332 use_idn 167 - 7.4.333 use_ipv6 167 - 7.4.334 user_agent 167 - 7.4.335 visual 167 - 7.4.336 wait_key 168 - 7.4.337 weed 168 - 7.4.338 wrap_search 168 - 7.4.339 wrapmargin 168 - 7.4.340 write_bcc 168 - 7.4.341 write_inc 169 - 7.4.342 xterm_icon 169 - 7.4.343 xterm_leave 169 - 7.4.344 xterm_set_titles 169 - 7.4.345 xterm_title 169 - 7.5 Functions ....................................................... 170 - 7.5.1 generic 170 - 7.5.2 index 171 - 7.5.3 pager 173 - 7.5.4 alias 175 - 7.5.5 query 175 - 7.5.6 attach 175 - 7.5.7 compose 176 - 7.5.8 postpone 177 - 7.5.9 browser 177 - 7.5.10 pgp 178 - 7.5.11 editor 178 - - 8. Miscellany ............................................................ 178 - 8.1 Acknowledgments ................................................. 179 - 8.2 About this document ............................................. 181 + 7.4.325 to_chars 166 + 7.4.326 trash 167 + 7.4.327 tunnel 167 + 7.4.328 umask 167 + 7.4.329 uncollapse_jump 167 + 7.4.330 use_8bitmime 168 + 7.4.331 use_domain 168 + 7.4.332 use_from 168 + 7.4.333 use_idn 168 + 7.4.334 use_ipv6 168 + 7.4.335 user_agent 169 + 7.4.336 visual 169 + 7.4.337 wait_key 169 + 7.4.338 weed 169 + 7.4.339 wrap_search 169 + 7.4.340 wrapmargin 170 + 7.4.341 write_bcc 170 + 7.4.342 write_inc 170 + 7.4.343 xterm_icon 170 + 7.4.344 xterm_leave 170 + 7.4.345 xterm_set_titles 171 + 7.4.346 xterm_title 171 + 7.5 Functions ....................................................... 171 + 7.5.1 generic 171 + 7.5.2 index 172 + 7.5.3 pager 174 + 7.5.4 alias 176 + 7.5.5 query 176 + 7.5.6 attach 176 + 7.5.7 compose 177 + 7.5.8 postpone 178 + 7.5.9 browser 178 + 7.5.10 pgp 179 + 7.5.11 editor 179 + + 8. Miscellany ............................................................ 179 + 8.1 Acknowledgments ................................................. 180 + 8.2 About this document ............................................. 182 x diff --git a/handler.c b/handler.c index f899a64..6d4857b 100644 --- a/handler.c +++ b/handler.c @@ -24,6 +24,7 @@ #include "handler.h" #include "mutt_curses.h" #include "rfc1524.h" +#include "rfc3676.h" #include "keymap.h" #include "mime.h" #include "copy.h" @@ -781,180 +782,6 @@ int text_enriched_handler (BODY * a, STATE * s) return (0); } -/* - * An implementation of RFC 2646. - * - * NOTE: This still has to be made UTF-8 aware. - * - */ - -#define FLOWED_MAX 77 - -static int get_quote_level (char *line) -{ - int quoted; - - for (quoted = 0; line[quoted] == '>'; quoted++); - return quoted; -} - -static void print_flowed_line (char *line, STATE * s, int ql) -{ - int width; - char *pos, *oldpos; - int len = str_len (line); - int i; - - if (MaxLineLength > 0) { - width = MaxLineLength - WrapMargin - ql - 1; - if (option (OPTSTUFFQUOTED)) - --width; - if (width < 0) - width = MaxLineLength; - } - else { - if (option (OPTMBOXPANE)) - width = COLS - SidebarWidth - WrapMargin - ql - 1; - else - width = COLS - WrapMargin - ql - 1; - - if (option (OPTSTUFFQUOTED)) - --width; - if (width < 0) - width = COLS; - } - - /* fprintf(stderr,"print_flowed_line will print `%s' with ql = %d\n",line,ql); */ - - if (str_len (line) == 0) { - if (option (OPTQUOTEEMPTY)) { - if (s->prefix) - state_puts(s->prefix,s); - for (i=0;i',s); - if (option(OPTSTUFFQUOTED)) - state_putc(' ',s); - } - state_putc('\n',s); - return; - } - - pos = line + width; - oldpos = line; - - /* fprintf(stderr,"oldpos = %p line+len = %p\n",oldpos,line+len); */ - - for (; oldpos < line + len; pos += width) { - /* fprintf(stderr,"outer for loop\n"); */ - if (pos < line + len) { /* only search a new position when we're not over the end of the string w/ pos */ - /* fprintf(stderr,"if 1\n"); */ - if (*pos == ' ') { - /* fprintf(stderr,"if 2: good luck! found a space\n"); */ - *pos = '\0'; - ++pos; - } - else { - /* fprintf(stderr,"if 2: else\n"); */ - char *save = pos; - - while (pos >= oldpos && !isspace (*pos)) { - /* fprintf(stderr,"pos(%p) > oldpos(%p)\n",pos,oldpos); */ - --pos; - } - if (pos < oldpos) { - /* fprintf(stderr,"wow, no space found, searching the other direction\n"); */ - pos = save; - while (pos < line + len && *pos && !isspace (*pos)) { - /* fprintf(stderr,"pos(%p) < line+len(%p)\n",pos,line+len); */ - ++pos; - } - /* fprintf(stderr,"found a space pos = %p\n",pos); */ - } - *pos = '\0'; - ++pos; - } - } - else { - /* fprintf(stderr,"if 1 else\n"); */ - } - if (s->prefix) - state_puts (s->prefix, s); - for (i = 0; i < ql; ++i) - state_putc ('>', s); - if (option (OPTSTUFFQUOTED) && (ql > 0 || s->prefix)) - state_putc (' ', s); - state_puts (oldpos, s); - /* fprintf(stderr,"print_flowed_line: `%s'\n",oldpos); */ - if (pos < line + len) - state_putc (' ', s); - state_putc ('\n', s); - oldpos = pos; - } - /*state_puts(line,s); - state_putc('\n',s); */ -} - -static int text_plain_flowed_handler (BODY * a, STATE * s) -{ - int bytes = a->length; - char buf[LONG_STRING]; - char *curline = str_dup (""); - char *t = NULL; - unsigned int curline_len = 1; - unsigned int quotelevel = 0, newql = 0; - int buf_off, buf_len; - - while (bytes > 0 && fgets (buf, sizeof (buf), s->fpin)) { - buf_len = str_len (buf); - bytes -= buf_len; - - newql = get_quote_level (buf); - - /* a change of quoting level in a paragraph - shouldn't happen, - * but has to be handled - see RFC 3676, sec. 4.5. - */ - if (newql != quotelevel && curline && *curline) { - print_flowed_line (curline, s, quotelevel); - *curline = '\0'; - curline_len = 1; - } - quotelevel = newql; - - /* XXX - If a line is longer than buf (shouldn't happen), it is split. - * This will almost always cause an unintended line break, and - * possibly a change in quoting level. But that's better than not - * displaying it at all. - */ - if ((t = strrchr (buf, '\n')) || (t = strrchr (buf, '\r'))) { - *t = '\0'; - buf_len = t - buf; - } - buf_off = newql; - if (buf[buf_off] == ' ') - buf_off++; - - /* signature separator also flushes the previous paragraph */ - if (strcmp(buf + buf_off, "-- ") == 0 && curline && *curline) { - print_flowed_line (curline, s, quotelevel); - *curline = '\0'; - curline_len = 1; - } - - curline = realloc (curline, curline_len + buf_len - buf_off); - strcpy (curline + curline_len - 1, buf + buf_off); - curline_len += buf_len - buf_off; - - /* if this was a fixed line the paragraph is finished */ - if (buf_len == 0 || buf[buf_len - 1] != ' ' || strcmp(buf + buf_off, "-- ") == 0) { - print_flowed_line (curline, s, quotelevel); - *curline = '\0'; - curline_len = 1; - } - - } - mem_free (&curline); - return (0); -} - #define TXTHTML 1 #define TXTPLAIN 2 #define TXTENRICHED 3 @@ -1530,7 +1357,7 @@ int mutt_body_handler (BODY * b, STATE * s) else if (ascii_strcasecmp ("flowed", mutt_get_parameter ("format", b->parameter)) == 0) - handler = text_plain_flowed_handler; + handler = rfc3676_handler; else plaintext = 1; } diff --git a/init.h b/init.h index 1e13e52..40c7772 100644 --- a/init.h +++ b/init.h @@ -507,6 +507,19 @@ struct option_t MuttVars[] = { ** deleting will automatically be purged without prompting. If set to ** \fIno\fP, messages marked for deletion will be kept in the mailbox. */ + {"delete_space", DT_BOOL, R_NONE, OPTDELSP, 0}, + /* + ** .pp + ** When sending messages with \fTformat=flowed\fP by \fIsetting\fP the + ** $$$text_flowed variable, this variable specifies whether to also + ** set the \fTDelSp\fP parameter to \fTyes\fP. If this is \fIunset\fP, + ** no additional parameter will be send as a value of \fTno\fP already + ** is the default behavior. + ** + ** .pp + ** \fBNote:\fP this variable only has an effect on \fIoutgoing\fP messages + ** (if $$$text_flowed is \fIset\fP) but not on incomming. + */ {"delete_untag", DT_BOOL, R_NONE, OPTDELETEUNTAG, 1}, /* ** .pp @@ -593,6 +606,13 @@ struct option_t MuttVars[] = { ** they contain the string ``\fTFrom \fP'' (note the trailing space) ** in the beginning of a line. Useful to avoid the tampering certain mail ** delivery and transport agents tend to do with messages. + ** + ** .pp + ** \fBNote:\fP as mutt-ng currently violates RfC3676 defining + ** \fTformat=flowed\fP, it's + * Peter J. Holzer + * Rocco Rutte + * + * This file is part of mutt-ng, see http://www.muttng.org/. + * It's licensed under the GNU General Public License, + * please see the file GPL in the top level source directory. + */ + +#if HAVE_CONFIG_H +# include "config.h" +#endif + +#include +#include +#include +#include +#include +#include + +#include "mutt.h" +#include "mutt_curses.h" +#include "ascii.h" +#include "handler.h" +#include "state.h" +#include "lib.h" + +#include "lib/mem.h" +#include "lib/intl.h" +#include "lib/str.h" +#include "lib/debug.h" + +typedef int handler_f (BODY *, STATE *); +typedef handler_f *handler_t; + +#define FLOWED_MAX 77 + +static int get_quote_level (char *line) +{ + int quoted; + + for (quoted = 0; line[quoted] == '>'; quoted++); + return quoted; +} + +static void print_flowed_line (char *line, STATE * s, + int ql, int delsp, + int* spaces, int space_len) { + int width; + char *pos, *oldpos; + int len = str_len (line); + int i; + + if (MaxLineLength > 0) { + width = MaxLineLength - WrapMargin - ql - 1; + if (option (OPTSTUFFQUOTED)) + --width; + if (width < 0) + width = MaxLineLength; + } + else { + if (option (OPTMBOXPANE)) + width = COLS - SidebarWidth - WrapMargin - ql - 1; + else + width = COLS - WrapMargin - ql - 1; + + if (option (OPTSTUFFQUOTED)) + --width; + if (width < 0) + width = COLS; + } + + if (str_len (line) == 0) { + if (option (OPTQUOTEEMPTY)) { + if (s->prefix) + state_puts(s->prefix,s); + for (i=0;i',s); + if (option(OPTSTUFFQUOTED)) + state_putc(' ',s); + } + state_putc('\n',s); + return; + } + + pos = line + width; + oldpos = line; + + for (; oldpos < line + len; pos += width) { + /* only search a new position when we're not over + * the end of the string w/ pos */ + if (pos < line + len) { + /* fprintf(stderr,"if 1\n"); */ + if (*pos == ' ') { + /* fprintf(stderr,"if 2: good luck! found a space\n"); */ + *pos = '\0'; + ++pos; + } + else { + /* fprintf(stderr,"if 2: else\n"); */ + char *save = pos; + + while (pos >= oldpos && *pos != ' ') { + /* fprintf(stderr,"pos(%p) > oldpos(%p)\n",pos,oldpos); */ + --pos; + } + if (pos < oldpos) { + /* fprintf(stderr,"wow, no space found, + * searching the other direction\n"); */ + pos = save; + while (pos < line + len && *pos && *pos != ' ') { + /* fprintf(stderr,"pos(%p) < line+len(%p)\n",pos,line+len); */ + ++pos; + } + /* fprintf(stderr,"found a space pos = %p\n",pos); */ + } + *pos = '\0'; + ++pos; + } + } + else { + /* fprintf(stderr,"if 1 else\n"); */ + } + if (s->prefix) + state_puts (s->prefix, s); + + for (i = 0; i < ql; ++i) + state_putc ('>', s); + if (option (OPTSTUFFQUOTED) && (ql > 0 || s->prefix)) + state_putc (' ', s); + + if (delsp && spaces && space_len > 0) { + /* here, we need to character-wise step through the line + * to eliminate all spaces which were trailing due to DelSp */ + for (i = 0; i < str_len (oldpos); i++) { + if (oldpos[i] == ' ' && spaces[&(oldpos[i])-line] != 0) { + debug_print (4, ("DelSp: spaces[%d] forces space removal\n", + &(oldpos[i])-line)); + continue; + } + /* print space at oldpos[i] if it was non-trailing */ + state_putc (oldpos[i], s); + } + } else + /* for no DelSp, just do whole line as per usual */ + state_puts (oldpos, s); + /* fprintf(stderr,"print_flowed_line: `%s'\n",oldpos); */ + if (pos < line + len) + state_putc (' ', s); + state_putc ('\n', s); + oldpos = pos; + } +} + +int rfc3676_handler (BODY * a, STATE * s) { + int bytes = a->length; + char buf[LONG_STRING]; + char *curline = str_dup (""); + char *t = NULL; + unsigned int curline_len = 1, space_len = 1, + quotelevel = 0, newql = 0; + int buf_off, buf_len; + int delsp = 0; + int* spaces = NULL; + + /* respect DelSP of RfC3676 only with f=f parts */ + if ((t = (char*) mutt_get_parameter ("delsp", a->parameter))) { + delsp = str_len (t) == 3 && ascii_strncasecmp (t, "yes", 3) == 0; + t = NULL; + } + + debug_print (2, ("DelSp: %s\n", delsp ? "yes" : "no")); + + while (bytes > 0 && fgets (buf, sizeof (buf), s->fpin)) { + buf_len = str_len (buf); + bytes -= buf_len; + + newql = get_quote_level (buf); + + /* a change of quoting level in a paragraph - shouldn't happen, + * but has to be handled - see RFC 3676, sec. 4.5. + */ + if (newql != quotelevel && curline && *curline) { + print_flowed_line (curline, s, quotelevel, delsp, spaces, space_len); + *curline = '\0'; + curline_len = 1; + space_len = 0; + } + quotelevel = newql; + + /* XXX - If a line is longer than buf (shouldn't happen), it is split. + * This will almost always cause an unintended line break, and + * possibly a change in quoting level. But that's better than not + * displaying it at all. + */ + if ((t = strrchr (buf, '\n')) || (t = strrchr (buf, '\r'))) { + *t = '\0'; + buf_len = t - buf; + } + buf_off = newql; + /* respect space-stuffing */ + if (buf[buf_off] == ' ') + buf_off++; + + /* signature separator also flushes the previous paragraph */ + if (strcmp(buf + buf_off, "-- ") == 0 && curline && *curline) { + print_flowed_line (curline, s, quotelevel, delsp, spaces, space_len); + *curline = '\0'; + curline_len = 1; + space_len = 0; + } + + mem_realloc (&curline, curline_len + buf_len - buf_off); + mem_realloc (&spaces, (curline_len + buf_len - buf_off)*sizeof (int)); + strcpy (curline + curline_len - 1, buf + buf_off); + memset (&spaces[space_len], 0, (buf_len - buf_off)*sizeof (int)); + curline_len += buf_len - buf_off; + space_len += buf_len - buf_off; + + /* if this was a fixed line the paragraph is finished */ + if (buf_len == 0 || buf[buf_len - 1] != ' ' || strcmp(buf + buf_off, "-- ") == 0) { + print_flowed_line (curline, s, quotelevel, delsp, spaces, space_len); + *curline = '\0'; + curline_len = 1; + space_len = 0; + } else { + /* if last line we appended had a space and we have DelSp=yes, + * get a 1 into spaces array at proper position so that + * print_flowed_line() can handle it; don't kill the space + * right here 'cause we maybe need soft linebreaks to search for break + */ + if (delsp && curline && *curline && curline_len-2 >= 0 && + curline[curline_len-2] == ' ') { + debug_print (4, ("DelSp: marking spaces[%d] for later removal\n", + curline_len-2)); + spaces[curline_len-2] = 1; + } + } + + } + mem_free (&spaces); + mem_free (&curline); + return (0); +} diff --git a/rfc3676.h b/rfc3676.h new file mode 100644 index 0000000..d7d6397 --- /dev/null +++ b/rfc3676.h @@ -0,0 +1,23 @@ +/* + * Parts were written/modified by: + * Andreas Krennmair + * Peter J. Holzer + * Rocco Rutte + * + * This file is part of mutt-ng, see http://www.muttng.org/. + * It's licensed under the GNU General Public License, + * please see the file GPL in the top level source directory. + */ +#ifndef _MUTT_RFC3676_H +#define _MUTT_RFC3676_H + +#include "mutt.h" +#include "state.h" + +/* + * body handler implementing RfC 3676 for format=flowed + */ + +int rfc3676_handler (BODY * a, STATE * s); + +#endif /* !_MUTT_RFC3676_H */ diff --git a/send.c b/send.c index 3b17228..5dad490 100644 --- a/send.c +++ b/send.c @@ -1184,8 +1184,11 @@ int ci_send_message (int flags, /* send mode */ msg->content->use_disp = 0; msg->content->disposition = DISPINLINE; if (option (OPTTEXTFLOWED) && msg->content->type == TYPETEXT - && !ascii_strcasecmp (msg->content->subtype, "plain")) + && !ascii_strcasecmp (msg->content->subtype, "plain")) { mutt_set_parameter ("format", "flowed", &msg->content->parameter); + if (option (OPTDELSP)) + mutt_set_parameter ("delsp", "yes", &msg->content->parameter); + } if (!tempfile) { mutt_mktemp (buffer); -- 2.20.1