(The problem of spam): Fix, reported by Cheng Gao

[gnus] / texi / message.texi

diff --git a/texi/message.texi b/texi/message.texi
index d1f77c6..af78f63 100644 (file)
--- a/texi/message.texi
+++ b/texi/message.texi
@@ -18,7 +18,7 @@
 
 This file documents Message, the Emacs message composition mode.
 
 
 This file documents Message, the Emacs message composition mode.
 

-Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003 
+Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004 

 Free Software Foundation, Inc.
 
 Permission is granted to copy, distribute and/or modify this document
 Free Software Foundation, Inc.
 
 Permission is granted to copy, distribute and/or modify this document


@@ -88,7 +88,7 @@ Message mode buffers.
 * Key Index::         List of Message mode keys.
 @end menu
 
 * Key Index::         List of Message mode keys.
 @end menu
 

-This manual corresponds to Message 5.10.1.  Message is distributed
+This manual corresponds to Message v5.10.6.  Message is distributed

 with the Gnus distribution bearing the same version number as this
 manual.
 
 with the Gnus distribution bearing the same version number as this
 manual.
 


@@ -353,6 +353,7 @@ will be removed before popping up the buffer.  The default is
 @node Mailing Lists
 @section Mailing Lists
 
 @node Mailing Lists
 @section Mailing Lists
 

+@cindex Mail-Followup-To

 Sometimes while posting to mailing lists, the poster needs to direct
 followups to the post to specific places.  The Mail-Followup-To (MFT)
 was created to enable just this.  Two example scenarios where this is
 Sometimes while posting to mailing lists, the poster needs to direct
 followups to the post to specific places.  The Mail-Followup-To (MFT)
 was created to enable just this.  Two example scenarios where this is


@@ -491,7 +492,7 @@ Gnus will prompt you for an action.
 
 @end table
 
 
 @end table
 

-It is considered good nettiquette to honor MFT, as it is assumed the
+It is considered good netiquette to honor MFT, as it is assumed the

 fellow who posted a message knows where the followups need to go
 better than you do.
 
 fellow who posted a message knows where the followups need to go
 better than you do.
 


@@ -830,7 +831,7 @@ The most typical thing users want to use the multipart things in
 be done with the @kbd{C-c C-a} command, which will prompt for a file
 name and a @acronym{MIME} type.
 
 be done with the @kbd{C-c C-a} command, which will prompt for a file
 name and a @acronym{MIME} type.
 

-You can also create arbitrarily complex multiparts using the MML
+You can also create arbitrarily complex multiparts using the @acronym{MML}

 language (@pxref{Composing, , Composing, emacs-mime, The Emacs MIME
 Manual}).
 
 language (@pxref{Composing, , Composing, emacs-mime, The Emacs MIME
 Manual}).
 


@@ -876,12 +877,13 @@ Libidn} installed in order to use this functionality.
 @cindex encrypt
 @cindex secure
 
 @cindex encrypt
 @cindex secure
 

-Using the MML language, Message is able to create digitally signed and
-digitally encrypted messages.  Message (or rather MML) currently
-support @acronym{PGP} (RFC 1991), @acronym{PGP/MIME} (RFC 2015/3156) and @acronym{S/MIME}.
-Instructing MML to perform security operations on a @acronym{MIME} part is
-done using the @kbd{C-c C-m s} key map for signing and the @kbd{C-c
-C-m c} key map for encryption, as follows.
+Using the @acronym{MML} language, Message is able to create digitally
+signed and digitally encrypted messages.  Message (or rather
+@acronym{MML}) currently support @acronym{PGP} (RFC 1991),
+@acronym{PGP/MIME} (RFC 2015/3156) and @acronym{S/MIME}.  Instructing
+@acronym{MML} to perform security operations on a @acronym{MIME} part is
+done using the @kbd{C-c C-m s} key map for signing and the @kbd{C-c C-m
+c} key map for encryption, as follows.

 
 @table @kbd
 
 
 @table @kbd
 


@@ -924,21 +926,22 @@ Digitally encrypt current message using @acronym{PGP/MIME}.
 @item C-c C-m C-n
 @kindex C-c C-m C-n
 @findex mml-unsecure-message
 @item C-c C-m C-n
 @kindex C-c C-m C-n
 @findex mml-unsecure-message

-Remove security related MML tags from message.
+Remove security related @acronym{MML} tags from message.

 
 @end table
 
 These commands do not immediately sign or encrypt the message, they
 
 @end table
 
 These commands do not immediately sign or encrypt the message, they

-merely insert the proper MML secure tag to instruct the MML engine to
-perform that operation when the message is actually sent.  They may
-perform other operations too, such as locating and retrieving a
-@acronym{S/MIME} certificate of the person you wish to send encrypted mail
-to.  When the mml parsing engine converts your MML into a properly
-encoded @acronym{MIME} message, the secure tag will be replaced with either
-a part or a multipart tag.  If your message contains other mml parts,
-a multipart tag will be used; if no other parts are present in your
-message a single part tag will be used.  This way, message mode will
-do the Right Thing (TM) with signed/encrypted multipart messages.
+merely insert the proper @acronym{MML} secure tag to instruct the
+@acronym{MML} engine to perform that operation when the message is
+actually sent.  They may perform other operations too, such as locating
+and retrieving a @acronym{S/MIME} certificate of the person you wish to
+send encrypted mail to.  When the mml parsing engine converts your
+@acronym{MML} into a properly encoded @acronym{MIME} message, the secure
+tag will be replaced with either a part or a multipart tag.  If your
+message contains other mml parts, a multipart tag will be used; if no
+other parts are present in your message a single part tag will be used.
+This way, message mode will do the Right Thing (TM) with
+signed/encrypted multipart messages.

 
 Since signing and especially encryption often is used when sensitive
 information is sent, you may want to have some way to ensure that your
 
 Since signing and especially encryption often is used when sensitive
 information is sent, you may want to have some way to ensure that your


@@ -970,24 +973,25 @@ programs are required to make things work, and some small general hints.
 modern cryptography, @acronym{S/MIME}, various PKCS standards, OpenSSL and
 so on.
 
 modern cryptography, @acronym{S/MIME}, various PKCS standards, OpenSSL and
 so on.
 

-The @acronym{S/MIME} support in Message (and MML) require OpenSSL.  OpenSSL
-performs the actual @acronym{S/MIME} sign/encrypt operations.  OpenSSL can
-be found at @uref{http://www.openssl.org/}.  OpenSSL 0.9.6 and later
-should work.  Version 0.9.5a cannot extract mail addresses from
-certificates, and it insert a spurious CR character into @acronym{MIME}
-separators so you may wish to avoid it if you would like to avoid
-being regarded as someone who send strange mail.  (Although by sending
-@acronym{S/MIME} messages you've probably already lost that contest.)
+The @acronym{S/MIME} support in Message (and @acronym{MML}) require
+OpenSSL.  OpenSSL performs the actual @acronym{S/MIME} sign/encrypt
+operations.  OpenSSL can be found at @uref{http://www.openssl.org/}.
+OpenSSL 0.9.6 and later should work.  Version 0.9.5a cannot extract mail
+addresses from certificates, and it insert a spurious CR character into
+@acronym{MIME} separators so you may wish to avoid it if you would like
+to avoid being regarded as someone who send strange mail.  (Although by
+sending @acronym{S/MIME} messages you've probably already lost that
+contest.)

 
 To be able to send encrypted mail, a personal certificate is not
 
 To be able to send encrypted mail, a personal certificate is not

-required.  Message (MML) need a certificate for the person to whom you
+required.  Message (@acronym{MML}) need a certificate for the person to whom you

 wish to communicate with though.  You're asked for this when you type
 @kbd{C-c C-m c s}.  Currently there are two ways to retrieve this
 certificate, from a local file or from DNS.  If you chose a local
 file, it need to contain a X.509 certificate in @acronym{PEM} format.
 If you chose DNS, you're asked for the domain name where the
 certificate is stored, the default is a good guess.  To my belief,
 wish to communicate with though.  You're asked for this when you type
 @kbd{C-c C-m c s}.  Currently there are two ways to retrieve this
 certificate, from a local file or from DNS.  If you chose a local
 file, it need to contain a X.509 certificate in @acronym{PEM} format.
 If you chose DNS, you're asked for the domain name where the
 certificate is stored, the default is a good guess.  To my belief,

-Message (MML) is the first mail agent in the world to support
+Message (@acronym{MML}) is the first mail agent in the world to support

 retrieving @acronym{S/MIME} certificates from DNS, so you're not
 likely to find very many certificates out there.  At least there
 should be one, stored at the domain @code{simon.josefsson.org}.  LDAP
 retrieving @acronym{S/MIME} certificates from DNS, so you're not
 likely to find very many certificates out there.  At least there
 should be one, stored at the domain @code{simon.josefsson.org}.  LDAP


@@ -997,8 +1001,8 @@ command line to retrieve a certificate into a file and use it.)
 
 As for signing messages, OpenSSL can't perform signing operations
 without some kind of configuration.  Especially, you need to tell it
 
 As for signing messages, OpenSSL can't perform signing operations
 without some kind of configuration.  Especially, you need to tell it

-where your private key and your certificate is stored.  MML uses an
-Emacs interface to OpenSSL, aptly named @code{smime.el}, and it
+where your private key and your certificate is stored.  @acronym{MML}
+uses an Emacs interface to OpenSSL, aptly named @code{smime.el}, and it

 contain a @code{custom} group used for this configuration.  So, try
 @kbd{M-x customize-group RET smime RET} and look around.
 
 contain a @code{custom} group used for this configuration.  So, try
 @kbd{M-x customize-group RET smime RET} and look around.
 


@@ -1049,7 +1053,7 @@ solution is to use PGP 2.x instead (i.e., if you use @code{pgg}, set
 @code{pgg-default-scheme} to @code{pgp}).  If you do want to use
 GnuPG, you can use a compatibility script called @code{gpg-2comp}
 available from
 @code{pgg-default-scheme} to @code{pgp}).  If you do want to use
 GnuPG, you can use a compatibility script called @code{gpg-2comp}
 available from

-@url{http://muppet.faveve.uni-stuttgart.de/~gero/gpg-2comp/}.  You
+@uref{http://muppet.faveve.uni-stuttgart.de/~gero/gpg-2comp/}.  You

 could also convince your fellow PGP 2.x users to convert to GnuPG.
 @vindex mml-signencrypt-style-alist
 As a final workaround, you can make the sign and encryption work in
 could also convince your fellow PGP 2.x users to convert to GnuPG.
 @vindex mml-signencrypt-style-alist
 As a final workaround, you can make the sign and encryption work in


@@ -1067,7 +1071,7 @@ to change this behavior you can customize the
 This causes to sign and encrypt in two passes, thus generating a
 message that can be understood by PGP version 2.
 
 This causes to sign and encrypt in two passes, thus generating a
 message that can be understood by PGP version 2.
 

-(Refer to @url{http://www.gnupg.org/gph/en/pgp2x.html} for more
+(Refer to @uref{http://www.gnupg.org/gph/en/pgp2x.html} for more

 information about the problem.)
 
 @node Various Commands
 information about the problem.)
 
 @node Various Commands


@@ -1223,7 +1227,7 @@ controlled by the @code{ispell-message-dictionary-alist} variable:
 @lisp
 (setq ispell-message-dictionary-alist
       '(("^Newsgroups:.*\\bde\\." . "deutsch8")
 @lisp
 (setq ispell-message-dictionary-alist
       '(("^Newsgroups:.*\\bde\\." . "deutsch8")

-       (".*" . "default")))
+        (".*" . "default")))

 @end lisp
 
 @code{ispell} depends on having the external @samp{ispell} command
 @end lisp
 
 @code{ispell} depends on having the external @samp{ispell} command


@@ -1412,6 +1416,13 @@ hidden when composing a message.
       '(not "From" "Subject" "To" "Cc" "Newsgroups"))
 @end lisp
 
       '(not "From" "Subject" "To" "Cc" "Newsgroups"))
 @end lisp
 

+@item message-header-synonyms
+@vindex message-header-synonyms
+A list of lists of header synonyms.  E.g., if this list contains a
+member list with elements @code{Cc} and @code{To}, then
+@code{message-carefully-insert-headers} will not insert a @code{To}
+header when the message is already @code{Cc}ed to the recipient.
+

 @end table
 
 
 @end table
 
 


@@ -1941,7 +1952,7 @@ Hook run after sending messages.
 
 @item message-cancel-hook
 @vindex message-cancel-hook
 
 @item message-cancel-hook
 @vindex message-cancel-hook

-Hook run when cancelling news articles.
+Hook run when canceling news articles.

 
 @item message-mode-syntax-table
 @vindex message-mode-syntax-table
 
 @item message-mode-syntax-table
 @vindex message-mode-syntax-table