X-Git-Url: http://git.chise.org/gitweb/?a=blobdiff_plain;f=texi%2Fmessage.texi;h=178b86703117854694fb0135161077c497ada857;hb=ba465d382d0b222fdd7b62a6c736c37ade08b8ba;hp=21b04dfee81f9cef273f4acb10a317e2422298d4;hpb=4c8a462f47791317a6f8a06fe7f0374905ac0132;p=elisp%2Fgnus.git- diff --git a/texi/message.texi b/texi/message.texi index 21b04df..178b867 100644 --- a/texi/message.texi +++ b/texi/message.texi @@ -1,67 +1,70 @@ \input texinfo @c -*-texinfo-*- @setfilename message -@settitle Pterodactyl Message 0.88 Manual +@settitle T-gnus 6.14 Message Manual @synindex fn cp @synindex vr cp @synindex pg cp -@c @direntry -@c * Message: (message). Mail and news composition mode that goes with Gnus. -@c @end direntry +@dircategory Editors +@direntry +* Message: (message). Mail and news composition mode that goes with Gnus. +@end direntry @iftex @finalout @end iftex @setchapternewpage odd -@ifinfo +@ifnottex This file documents Message, the Emacs message composition mode. -Copyright (C) 1996,97,98,99 Free Software Foundation, Inc. +Copyright (C) 1996,97,98,99,2000 Free Software Foundation, Inc. -Permission is granted to make and distribute verbatim copies of -this manual provided the copyright notice and this permission notice -are preserved on all copies. +Permission is granted to copy, distribute and/or modify this document +under the terms of the GNU Free Documentation License, Version 1.1 or +any later version published by the Free Software Foundation; with no +Invariant Sections, with the Front-Cover texts being ``A GNU +Manual'', and with the Back-Cover Texts as in (a) below. A copy of the +license is included in the section entitled ``GNU Free Documentation +License'' in the Emacs manual. -@ignore -Permission is granted to process this file through Tex and print the -results, provided the printed document carries copying permission -notice identical to this one except for the removal of this paragraph -(this paragraph not being relevant to the printed manual). +(a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify +this GNU Manual, like GNU software. Copies published by the Free +Software Foundation raise funds for GNU development.'' -@end ignore -Permission is granted to copy and distribute modified versions of this -manual under the conditions for verbatim copying, provided also that the -entire resulting derived work is distributed under the terms of a -permission notice identical to this one. - -Permission is granted to copy and distribute translations of this manual -into another language, under the above conditions for modified versions. -@end ifinfo +This document is part of a collection distributed under the GNU Free +Documentation License. If you want to distribute this document +separately from the collection, you can do so by adding a copy of the +license to the document, as described in section 6 of the license. +@end ifnottex @tex @titlepage -@title Pterodactyl Message 0.88 Manual +@title T-gnus 6.14 Message Manual @author by Lars Magne Ingebrigtsen @page @vskip 0pt plus 1filll -Copyright @copyright{} 1996,97,98,99 Free Software Foundation, Inc. - -Permission is granted to make and distribute verbatim copies of -this manual provided the copyright notice and this permission notice -are preserved on all copies. - -Permission is granted to copy and distribute modified versions of this -manual under the conditions for verbatim copying, provided that the -entire resulting derived work is distributed under the terms of a -permission notice identical to this one. - -Permission is granted to copy and distribute translations of this manual -into another language, under the above conditions for modified versions. - +Copyright @copyright{} 1996,97,98,99,2000 Free Software Foundation, Inc. + +Permission is granted to copy, distribute and/or modify this document +under the terms of the GNU Free Documentation License, Version 1.1 or +any later version published by the Free Software Foundation; with the +Invariant Sections being none, with the Front-Cover texts being ``A GNU +Manual'', and with the Back-Cover Texts as in (a) below. A copy of the +license is included in the section entitled ``GNU Free Documentation +License'' in the Emacs manual. + +(a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify +this GNU Manual, like GNU software. Copies published by the Free +Software Foundation raise funds for GNU development.'' + +This document is part of a collection distributed under the GNU Free +Documentation License. If you want to distribute this document +separately from the collection, you can do so by adding a copy of the +license to the document, as described in section 6 of the license. @end titlepage @page @@ -83,7 +86,7 @@ Message mode buffers. * Key Index:: List of Message mode keys. @end menu -This manual corresponds to Pterodactyl Message 0.88. Message is +This manual corresponds to T-gnus 6.14 Message. Message is distributed with the Gnus distribution bearing the same version number as this manual. @@ -153,7 +156,7 @@ If you want the replies to go to the @code{Sender} instead of the (setq message-reply-to-function (lambda () (cond ((equal (mail-fetch-field "from") "somebody") - (mail-fetch-field "sender")) + (list (cons 'To (mail-fetch-field "sender")))) (t nil)))) @end lisp @@ -188,8 +191,8 @@ but you can change the behavior to suit your needs by fiddling with the @code{message-wide-reply-to-function}. It is used in the same way as @code{message-reply-to-function} (@pxref{Reply}). -@findex rmail-dont-reply-to-names -Addresses that match the @code{rmail-dont-reply-to-names} regular +@findex message-dont-reply-to-names +Addresses that match the @code{message-dont-reply-to-names} regular expression will be removed from the @code{Cc} header. @@ -246,26 +249,9 @@ the message in the current buffer. If given a prefix, forward using news. @table @code -@item message-forward-start-separator -@vindex message-forward-start-separator -Delimiter inserted before forwarded messages. The default is@* -@samp{------- Start of forwarded message -------\n}. - -@vindex message-forward-end-separator -@item message-forward-end-separator -@vindex message-forward-end-separator -Delimiter inserted after forwarded messages. The default is@* -@samp{------- End of forwarded message -------\n}. - -@item message-signature-before-forwarded-message -@vindex message-signature-before-forwarded-message -If this variable is @code{t}, which it is by default, your personal -signature will be inserted before the forwarded message. If not, the -forwarded message will be inserted first in the new mail. - -@item message-included-forward-headers -@vindex message-included-forward-headers -Regexp matching header lines to be included in forwarded messages. +@item message-forward-ignored-headers +@vindex message-forward-ignored-headers +All headers that match this regexp will be deleted when forwarding a message. @item message-make-forward-subject-function @vindex message-make-forward-subject-function @@ -292,6 +278,12 @@ the evidence of previous forwards (such as @samp{Fwd:}, @samp{Re:}, @samp{(fwd)}) removed before the new subject is constructed. The default value is @code{nil}. +@item message-forward-as-mime +@vindex message-forward-as-mime +If this variable is @code{t} (the default), forwarded messages are +included as inline MIME RFC822 parts. If it's @code{nil}, forwarded +messages will just be copied inline to the new message, like previous, +non MIME-savvy versions of gnus would do. @end table @@ -332,6 +324,7 @@ will be removed before popping up the buffer. The default is * Movement:: Moving around in message buffers. * Insertion:: Inserting things into message buffers. * MIME:: @sc{mime} considerations. +* Security:: Signing and encrypting messages. * Various Commands:: Various things. * Sending:: Actually sending the message. * Mail Aliases:: How to use mail aliases. @@ -435,9 +428,16 @@ Move to the signature of the message (@code{message-goto-signature}). @item C-c C-y @kindex C-c C-y @findex message-yank-original -Yank the message that's being replied to into the message buffer +Yank the message in the buffer @code{gnus-article-copy} into the message +buffer. Normally @code{gnus-article-copy} is what you are replying to (@code{message-yank-original}). +@item C-c M-C-y +@kindex C-c M-C-y +@findex message-yank-buffer +Prompt for a buffer name and yank the contents of that buffer into the +message buffer (@code{message-yank-buffer}). + @item C-c C-q @kindex C-c C-q @findex message-fill-yanked-message @@ -467,6 +467,10 @@ All headers that match this regexp will be removed from yanked messages. The default is @samp{.}, which means that all headers will be removed. +@item message-cite-prefix-regexp +@vindex message-cite-prefix-regexp +Regexp matching the longest possible citation prefix on a line. + @item message-citation-line-function @vindex message-citation-line-function Function called to insert the citation line. The default is @@ -489,6 +493,22 @@ to quote the person you are answering. Inserting quoted text is done by @dfn{yanking}, and each quoted line you yank will have @code{message-yank-prefix} prepended to it. The default is @samp{> }. +@item message-yank-add-new-references +@vindex message-yank-add-new-references +@cindex yanking +Non-@code{nil} means new IDs will be added to References field when an +article is yanked by the command @code{message-yank-original} +interactively. If it is a symbol @code{message-id-only}, only an ID +from Message-ID field is used, otherwise IDs extracted from References, +In-Reply-To and Message-ID fields are used. + +@item message-list-references-add-position +@vindex message-list-references-add-position +@cindex yanking +Integer value means position for adding to References field when an +article is yanked by the command @code{message-yank-original} +interactively. + @item message-indentation-spaces @vindex message-indentation-spaces Number of spaces to indent yanked messages. @@ -560,6 +580,135 @@ You can also create arbitrarily complex multiparts using the MML language (@pxref{Composing, , Composing, emacs-mime, The Emacs MIME Manual}). +@node Security +@section Security +@cindex Security +@cindex S/MIME +@cindex PGP/MIME +@cindex sign +@cindex encrypt + +Using the MML language, Message is able to create digitally signed and +digitally encrypted messages. Message (or rather MML) currently support +PGP/MIME and S/MIME. Instructing MML to perform security operations on +a MIME part is done using the @code{M-m s} key map for signing and the +@code{M-m c} key map for encryption, as follows. + +@table @kbd + +@item M-m s s +@kindex M-m s s +@findex mml-secure-sign-smime + +Digitally sign current MIME part using S/MIME. + +@item M-m s p +@kindex M-m s p +@findex mml-secure-sign-pgp + +Digitally sign current MIME part using PGP/MIME. + +@item M-m c s +@kindex M-m c s +@findex mml-secure-encrypt-smime + +Digitally encrypt current MIME part using S/MIME. + +@item M-m c p +@kindex M-m c p +@findex mml-secure-encrypt-pgpmime + +Digitally encrypt current MIME part using PGP/MIME. + +@end table + +These commands do not immediately sign or encrypt the message, they +merely insert proper MML tags 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 S/MIME certificate of +the person you wish to send encrypted mail to. + +Since signing and especially encryption often is used when sensitive +information is sent, you may want to have some way to ensure that your +mail is actually signed or encrypted. After invoking the above +sign/encrypt commands, it is possible to preview the raw article by +using @code{C-u M-m P} (@code{mml-preview}). Then you can verify that +your long rant about what your ex-significant other or whomever actually +did with that funny looking person at that strange party the other +night, actually will be sent encrypted. + +@emph{Note!} Neither PGP/MIME nor S/MIME encrypt/signs RFC822 headers. +They only operate on the MIME object. Keep this in mind before sending +mail with a sensitive Subject line. + +Actually using the security commands above is not very difficult. At +least not compared with making sure all involved programs talk with each +other properly. Thus, we now describe what external libraries or +programs are required to make things work, and some small general hints. + +@subsection Using S/MIME + +@emph{Note!} This section assume you have a basic familiarity with +modern cryptography, S/MIME, various PKCS standards, OpenSSL and so on. + +The S/MIME support in Message (and MML) require OpenSSL. OpenSSL +perform the actual S/MIME sign/encrypt operations. OpenSSL can be found +at @code{http://www.openssl.org/}. OpenSSL 0.9.5a and later should +work. However, version 0.9.5a insert a spurious CR character into 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 S/MIME +messages you've probably already lost that contest.) + +To be able to send encrypted mail, a personal certificate is not +required. Message (MML) need a certificate for the person to whom you +wish to communicate with though. You're asked for this when you type +@code{M-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 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 retrieving 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 is a more popular method of distributing certificates, support for +it is planned. (Meanwhile, you can use @code{ldapsearch} from the +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 +where your private key and your certificate is stored. 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 @code{M-x +customize-group RET smime RET} and look around. + +Currently there is no support for talking to a CA (or RA) to create your +own certificate. None is planned either. You need to do this manually +with OpenSSL or using some other program. I used Netscape and got a +free S/MIME certificate from one of the big CA's on the net. Netscape +is able to export your private key and certificate in PKCS #12 format. +Use OpenSSL to convert this into a plain X.509 certificate in PEM format +as follows. + +@example +$ openssl pkcs12 -in ns.p12 -clcerts -nodes > key+cert.pem +@end example + +The @code{key+cert.pem} file should be pointed to from the +@code{smime-keys} variable. You should now be able to send signed mail. + +@emph{Note!} Your private key is store unencrypted in the file, so take +care in handling it. + +@subsection Using PGP/MIME + +PGP/MIME require an external OpenPGP implementation, such as GNU Privacy +Guard (@code{http://www.gnupg.org/}. It also require a Emacs interface +to it, such as Mailcrypt (available from +@code{http://www.nb.net/~lbudney/linux/software/mailcrypt.html}) or +Florian Weimer's @code{gpg.el}. + +Creating your own OpenPGP key is described in detail in the +documentation of your OpenPGP implementation, so we refer to it. @node Various Commands @section Various Commands @@ -578,8 +727,9 @@ many places to rotate the text. The default is 13. @kindex C-c C-e @findex message-elide-region Elide the text between point and mark (@code{message-elide-region}). -The text is killed and an ellipsis (@samp{[...]}) will be inserted in -its place. +The text is killed and replaced with the contents of the variable +@code{message-elide-ellipsis}. The default value is to use an ellipsis +(@samp{[...]}). @item C-c C-z @kindex C-c C-x @@ -779,6 +929,11 @@ have to deal with users that use these evil tools, in which case you may set this variable to a regexp that matches these prefixes. Myself, I just throw away non-compliant mail. +@item message-alternative-emails +@vindex message-alternative-emails +A regexp to match the alternative email addresses. The first matched +address (not primary one) is used in the @code{From} field. + @end table @@ -873,11 +1028,10 @@ This optional header will be computed by Message. @findex system-name @cindex Sun This required header will be generated by Message. A unique ID will be -created based on the date, time, user name and system name. Message will -use @code{mail-host-address} as the fully qualified domain name (FQDN) -of the machine if that variable is defined. If not, it will use -@code{system-name}, which doesn't report a FQDN on some machines -- -notably Suns. +created based on the date, time, user name and system name. Message +will use @code{system-name} to determine the name of the system. If +this isn't a fully qualified domain name (FQDN), Message will use +@code{mail-host-address} as the FQDN of the machine. @item X-Newsreader @cindex X-Newsreader @@ -1035,6 +1189,17 @@ posting a prepared news message. @section Various Message Variables @table @code +@item message-default-charset +@vindex message-default-charset +@cindex charset +Symbol naming a @sc{mime} charset. Non-ASCII characters in messages are +assumed to be encoded using this charset. The default is @code{nil}, +which means ask the user. (This variable is used only on non-@sc{mule} +Emacsen. +@xref{Charset Translation, , Charset Translation, emacs-mime, + Emacs MIME Manual}, for details on the @sc{mule}-to-@sc{mime} +translation process. + @item message-signature-separator @vindex message-signature-separator Regexp matching the signature separator. It is @samp{^-- *$} by @@ -1154,7 +1319,7 @@ A function to be called if @var{predicate} returns non-@code{nil}. @item message-fcc-handler-function @vindex message-fcc-handler-function A function called to save outgoing articles. This function will be -called with the name of the file to store the article in. The default +called with the name of the file to store the article in. The default function is @code{message-output} which saves in Unix mailbox format. @item message-courtesy-message @@ -1185,6 +1350,18 @@ this is a function, call that function with three parameters: The type, the to address and the group name. (Any of these may be @code{nil}.) The function should return the new buffer name. +@item message-use-multi-frames +@vindex message-use-multi-frames +If non-@code{nil}, generate new frames. The default is @code{nil}. + +@item message-delete-frame-on-exit +@vindex message-delete-frame-on-exit +The @code{message-delete-frame-on-exit} variable says whether to delete +the frame after sending the message or killing the message buffer. If it +is @code{nil} (which is the default), don't delete the frame. If it is +@code{ask}, ask wheter to delete the frame. If it is @code{t}, always +delete the frame. + @item message-max-buffers @vindex message-max-buffers This variable says how many old message buffers to keep. If there are