X-Git-Url: http://git.madism.org/?a=blobdiff_plain;f=doc%2Fmanual.sgml.head;h=66898380e82f6d0daba757719c90577de4ceb117;hb=618ceafdc9564dbb8f3bf45c3869297a1d5a3320;hp=eace2afc1bb2a839601fe49445b30b832af2aca3;hpb=0f3e091d19c9ed02a522a5e8d9efc9ec725b5382;p=apps%2Fmadmutt.git diff --git a/doc/manual.sgml.head b/doc/manual.sgml.head index eace2af..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 @@ -4409,26 +4459,29 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg 1524. Mutt-ng can be set up to - variable for details.) These utilities may have security issues - like overriding arbitrary files, contain exploitable bugs or just - leak information which is a bad in combination with running them - without prompting. When using mutt-ng's autoview mechanism - involing use of mailcap files, please make sure that + variable for details.) + + These utilities may have a variety of security vulnerabilities, + including 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... - you manually select trustworthy applications with a - reasonable calling sequence + manually select trustworth applications with a reasonable + calling sequence - you check the contents of mailcap files from time to time - (for example after doing software installations/upgrades) + periodically check the contents of mailcap files, + especially after software installations or upgrades - you, if you're the system's operator, always keep the - software packages involved up-to-date + keep the software packages referenced in the mailcap file up to date - you never ever change the default value of the - variable + leave the variable in its default + state to restrict mailcap expandos to a safe set of characters @@ -4462,7 +4515,7 @@ mailbox. However, it is possible to read other mailboxes and to send messages from the command line as well. --A expand an alias +-A expand an alias -a attach a file to a message -b specify a blind carbon-copy (BCC) address -c specify a carbon-copy (Cc) address