X-Git-Url: http://cgit.sxemacs.org/?a=blobdiff_plain;f=texi%2Fmessage.texi;h=eadacf732209e3f951c4ed794c91c28f36a5fb59;hb=6e78f2356811a237efe323789441d9c1da9d9bc3;hp=5fc109c1a94d28f276bc918bd73fd413ba7505d5;hpb=e9cbcce5e08949322618dfaa89494d3905e3486b;p=gnus diff --git a/texi/message.texi b/texi/message.texi index 5fc109c1a..eadacf732 100644 --- a/texi/message.texi +++ b/texi/message.texi @@ -77,7 +77,7 @@ Message mode buffers. @c Adjust ../Makefile.in if you change the following lines: Message is distributed with Gnus. The Gnus distribution @c -corresponding to this manual is Ma Gnus v0.2 +corresponding to this manual is Ma Gnus v0.6 @node Interface @@ -163,8 +163,8 @@ header should be. If it does not, it should just return @code{nil}, and the normal methods for determining the To header will be used. Each list element should be a cons, where the @sc{car} should be the -name of a header (e.g. @code{Cc}) and the @sc{cdr} should be the header -value (e.g. @samp{larsi@@ifi.uio.no}). All these headers will be +name of a header (e.g., @code{Cc}) and the @sc{cdr} should be the header +value (e.g., @samp{larsi@@ifi.uio.no}). All these headers will be inserted into the head of the outgoing mail. @@ -407,7 +407,7 @@ and very difficult to follow. @end itemize -Gnus honors the MFT header in other's messages (i.e. while following +Gnus honors the MFT header in other's messages (i.e., while following up to someone else's post) and also provides support for generating sensible MFT headers for outgoing messages as well. @@ -1041,7 +1041,7 @@ modern cryptography, @acronym{S/MIME}, various PKCS standards, OpenSSL and so on. The @acronym{S/MIME} support in Message (and @acronym{MML}) require -OpenSSL. OpenSSL performs the actual @acronym{S/MIME} sign/encrypt +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 @@ -1054,7 +1054,7 @@ To be able to send encrypted mail, a personal certificate is not 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 +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, @@ -1091,7 +1091,7 @@ The @file{key+cert.pem} file should be pointed to from the @emph{Note!} Your private key is now stored unencrypted in the file, so take care in handling it. Storing encrypted keys on the disk are supported, and Gnus will ask you for a passphrase before invoking -OpenSSL. Read the OpenSSL documentation for how to achieve this. If +OpenSSL@. Read the OpenSSL documentation for how to achieve this. If you use unencrypted keys (e.g., if they are on a secure storage, or if you are on a secure single user machine) simply press @code{RET} at the passphrase prompt. @@ -1101,10 +1101,11 @@ the passphrase prompt. @acronym{PGP/MIME} requires an external OpenPGP implementation, such as @uref{http://www.gnupg.org/, GNU Privacy Guard}. Pre-OpenPGP -implementations such as PGP 2.x and PGP 5.x are also supported. One -Emacs interface to the PGP implementations, PGG (@pxref{Top, ,PGG, -pgg, PGG Manual}), is included, but Mailcrypt is also supported. -@xref{PGP Compatibility}. +implementations such as PGP 2.x and PGP 5.x are also supported. The +default Emacs interface to the PGP implementation is EasyPG +(@pxref{Top,,EasyPG Assistant User's Manual, epa, EasyPG Assistant +User's Manual}), but PGG (@pxref{Top, ,PGG, pgg, PGG Manual}) and +Mailcrypt are also supported. @xref{PGP Compatibility}. @cindex gpg-agent Message internally calls GnuPG (the @command{gpg} command) to perform @@ -1139,11 +1140,6 @@ does the trick. gpg --use-agent --sign < /dev/null > /dev/null @end example -The Lisp variable @code{pgg-gpg-use-agent} controls whether to use -@command{gpg-agent}. See also @xref{Caching passphrase, , , pgg, The -PGG Manual}. - - @node PGP Compatibility @subsection Compatibility with older implementations @@ -1158,9 +1154,9 @@ your PGP implementation, so we refer to it. If you have imported your old PGP 2.x key into GnuPG, and want to send signed and encrypted messages to your fellow PGP 2.x users, you'll discover that the receiver cannot understand what you send. One -solution is to use PGP 2.x instead (i.e., if you use @code{pgg}, set +solution is to use PGP 2.x instead (e.g., if you use @code{pgg}, set @code{pgg-default-scheme} to @code{pgp}). You could also convince your -fellow PGP 2.x users to convert to GnuPG. +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 two steps; separately sign, then encrypt a message. If you would like @@ -1680,7 +1676,7 @@ installation. Most versions of MH doesn't like being fed messages that contain the headers in this variable. If this variable is non-@code{nil} (which is the default), these headers will be removed before mailing when sending -messages via MH. Set it to @code{nil} if your MH can handle these +messages via MH@. Set it to @code{nil} if your MH can handle these headers. @item message-qmail-inject-program @@ -1694,7 +1690,7 @@ Arguments passed to qmail-inject programs. This should be a list of strings, one string for each argument. It may also be a function. -For e.g., if you wish to set the envelope sender address so that bounces +E.g., if you wish to set the envelope sender address so that bounces go to the right place or to deal with listserv's usage of that address, you might set this variable to @code{'("-f" "you@@some.where")}. @@ -1784,7 +1780,7 @@ This required header will be generated by Message. A unique ID will be created based on the date, time, user name (for the local part) and the domain part. For the domain part, message will look (in this order) at @code{message-user-fqdn}, @code{system-name}, @code{mail-host-address} -and @code{message-user-mail-address} (i.e. @code{user-mail-address}) +and @code{message-user-mail-address} (i.e., @code{user-mail-address}) until a probably valid fully qualified domain name (FQDN) was found. @item User-Agent