X-Git-Url: http://git.chise.org/gitweb/?a=blobdiff_plain;f=texi%2Fmessage.texi;h=b32b60c6b945cb99fdd348636b1ccc06e4e392ef;hb=1a41a5b2dd8e60004b7ca27566f9a8a5900c6ee1;hp=7543a26081dca02a1fe6f60f7742bafd75970ea3;hpb=ee70a66fb20ed12d43960dd3933c7f416257ef42;p=elisp%2Fgnus.git- diff --git a/texi/message.texi b/texi/message.texi index 7543a26..b32b60c 100644 --- a/texi/message.texi +++ b/texi/message.texi @@ -1,67 +1,71 @@ \input texinfo @c -*-texinfo-*- @setfilename message -@settitle T-gnus 6.13 Message Manual +@settitle T-gnus 6.15 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 Emacs +@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, 1997, 1998, 1999, 2000, 2001, 2002 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 T-gnus 6.13 Message Manual +@title T-gnus 6.15 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, 1997, 1998, 1999, 2000, 2001, 2002 + 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,9 +87,9 @@ Message mode buffers. * Key Index:: List of Message mode keys. @end menu -This manual corresponds to T-gnus 6.13 Message. Message is -distributed with the Gnus distribution bearing the same version number -as this manual. +This manual corresponds to T-gnus 6.15 Message. Message is distributed +with the Gnus distribution bearing the same version number as this +manual. @node Interface @@ -109,6 +113,7 @@ sending it. * Forwarding:: Forwarding a message via news or mail. * Resending:: Resending a mail message. * Bouncing:: Bouncing a mail message. +* Mailing Lists:: Send mail to mailing lists. @end menu @@ -153,7 +158,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 @@ -246,8 +251,8 @@ the message in the current buffer. If given a prefix, forward using news. @table @code -@item message-ignored-forward-headers -@vindex message-ignored-forward-headers +@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 @@ -275,6 +280,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 @sc{mime} RFC822 parts. If it's @code{nil}, forwarded +messages will just be copied inline to the new message, like previous, +non @sc{mime}-savvy versions of gnus would do. @end table @@ -307,31 +318,188 @@ will be removed before popping up the buffer. The default is @samp{^\\(Received\\|Return-Path\\):}. +@node Mailing Lists +@section Mailing Lists + +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 +useful: + +@itemize @bullet +@item +A mailing list poster can use MFT to express that responses should be +sent to just the list, and not the poster as well. This will happen +if the poster is already subscribed to the list. + +@item +A mailing list poster can use MFT to express that responses should be +sent to the list and the poster as well. This will happen if the poster +is not subscribed to the list. + +@item +If a message is posted to several mailing lists, MFT may also be used +to direct the following discussion to one list only, because +discussions that are spread over several lists tend to be fragmented +and very difficult to follow. + +@end itemize + +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. + +@c @menu +@c * Honoring an MFT post:: What to do when one already exists +@c * Composing with a MFT header:: Creating one from scratch. +@c @end menu + +@c @node Composing with a MFT header +@subsection Composing a correct MFT header automagically + +The first step in getting Gnus to automagically generate a MFT header +in posts you make is to give Gnus a list of the mailing lists +addresses you are subscribed to. You can do this in more than one +way. The following variables would come in handy. + +@table @code + +@vindex message-subscribed-addresses +@item message-subscribed-addresses +This should be a list of addresses the user is subscribed to. Its +default value is @code{nil}. Example: +@lisp +(setq message-subscribed-addresses + '("ding@@gnus.org" "bing@@noose.org")) +@end lisp + +@vindex message-subscribed-regexps +@item message-subscribed-regexps +This should be a list of regexps denoting the addresses of mailing +lists subscribed to. Default value is @code{nil}. Example: If you +want to achieve the same result as above: +@lisp +(setq message-subscribed-regexps + '("\\(ding@@gnus\\)\\|\\(bing@@noose\\)\\.org") +@end lisp + +@vindex message-subscribed-address-functions +@item message-subscribed-address-functions +This can be a list of functions to be called (one at a time!!) to +determine the value of MFT headers. It is advisable that these +functions not take any arguments. Default value is @code{nil}. + +There is a pre-defined function in Gnus that is a good candidate for +this variable. @code{gnus-find-subscribed-addresses} is a function +that returns a list of addresses corresponding to the groups that have +the @code{subscribed} (@pxref{(gnus)subscribed}) +group parameter set to a non-nil value. This is how you would do it. + +@lisp +(setq message-subscribed-address-functions + '(gnus-find-subscribed-addresses)) +@end lisp + +@item message-subscribed-address-file +You might be one organised human freak and have a list of addresses of +all subscribed mailing lists in a separate file! Then you can just +set this variable to the name of the file and life would be good. + +@end table + +You can use one or more of the above variables. All their values are +``added'' in some way that works :-) + +Now you are all set. Just start composing a message as you normally do. +And just send it; as always. Just before the message is sent out, Gnus' +MFT generation thingy kicks in and checks if the message already has a +MFT field. If there is one, it is left alone. (Except if it's empty - +in that case, the field is removed and is not replaced with an +automatically generated one. This lets you disable MFT generation on a +per-message basis.) If there is none, then the list of recipient +addresses (in the To: and Cc: headers) is checked to see if one of them +is a list address you are subscribed to. If none of them is a list +address, then no MFT is generated; otherwise, a MFT is added to the +other headers and set to the value of all addresses in To: and Cc: + +Hm. ``So'', you ask, ``what if I send an email to a list I am not +subscribed to? I want my MFT to say that I want an extra copy.'' (This +is supposed to be interpreted by others the same way as if there were no +MFT, but you can use an explicit MFT to override someone else's +to-address group parameter.) Well, the kind folks at Gnus Towers are +working on a database of all known mailing list addresses that can be +used for this purpose. Till then, you could, like, insert a MFT header +manually, with the help of @kbd{C-c C-f C-m} !! + +@c @node Honoring an MFT post +@subsection Honoring an MFT post + +@vindex message-use-mail-followup-to +When you followup to a post on a mailing list, and the post has a MFT +header, Gnus' action will depend on the value of the variable +@code{message-use-mail-followup-to}. This variable can be one of: + +@table @code +@item use + Always honor MFTs. The To: and Cc: headers in your followup will be + derived from the MFT header of the original post. This is the default. + +@item nil + Always dishonor MFTs (just ignore the darned thing) + +@item ask +Gnus will prompt you for an action. + +@end table + +It is considered good nettiquette to honor MFT, as it is assumed the +fellow who posted a message knows where the followups need to go +better than you do. + @node Commands @chapter Commands @menu +* Buffer Entry:: Commands after entering a Message buffer. * Header Commands:: Commands for moving to headers. * 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. +* Spelling:: Having Emacs check your spelling. @end menu +@node Buffer Entry +@section Buffer Entry +@cindex undo +@kindex C-_ + +You most often end up in a Message buffer when responding to some other +message of some sort. Message does lots of handling of quoted text, and +may remove signatures, reformat the text, or the like---depending on +which used settings you're using. Message usually gets things right, +but sometimes it stumbles. To help the user unwind these stumblings, +Message sets the undo boundary before each major automatic action it +takes. If you press the undo key (usually located at @kbd{C-_}) a few +times, you will get back the un-edited message you're responding to. + + @node Header Commands @section Header Commands -All these commands move to the header in question. If it doesn't exist, -it will be inserted. +All these commands move to the header in question (except for the +@samp{Importance:} related commands). If it doesn't exist, it will be +inserted. @table @kbd @item C-c ? @kindex C-c ? -@findex message-goto-to +@findex describe-mode Describe the message mode. @item C-c C-f C-t @@ -339,6 +507,12 @@ Describe the message mode. @findex message-goto-to Go to the @code{To} header (@code{message-goto-to}). +@item C-c C-f C-o +@kindex C-c C-f C-o +@findex message-goto-from +Go to the @code{From} header (@code{message-goto-from}). (The ``o'' +in the key binding is for Originator.) + @item C-c C-f C-b @kindex C-c C-f C-b @findex message-goto-bcc @@ -389,6 +563,27 @@ Go to the @code{Keywords} header (@code{message-goto-keywords}). @findex message-goto-summary Go to the @code{Summary} header (@code{message-goto-summary}). +@item C-c C-f C-i +@kindex C-c C-f C-i +@findex message-insert-or-toggle-importance +This inserts the @samp{Importance:} header with a value of +@samp{high}. This header is used to signal the importance of the +message to the receiver. If the header is already present in the +buffer, it cycles between the three valid values according to RFC +1376: @samp{low}, @samp{normal} and @samp{high}. + +@item M-x message-insert-importance-high +@kindex M-x message-insert-importance-high +@findex message-insert-importance-high +Insert a @samp{Importance:} header with a value of @samp{high}, +deleting headers if necessary. + +@item M-x message-insert-importance-low +@kindex M-x message-insert-importance-low +@findex message-insert-importance-low +Insert a @samp{Importance:} header with a value of @samp{low}, +deleting headers if necessary. + @end table @@ -407,6 +602,13 @@ Move to the beginning of the body of the message @findex message-goto-signature Move to the signature of the message (@code{message-goto-signature}). +@item C-a +@kindex C-a +@findex message-beginning-of-line +If at beginning of header value, go to beginning of line, else go to +beginning of header value. (The header value comes after the header +name and the colon.) + @end table @@ -419,11 +621,11 @@ Move to the signature of the message (@code{message-goto-signature}). @kindex C-c C-y @findex message-yank-original 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 +buffer. Normally @code{gnus-article-copy} is what you are replying to (@code{message-yank-original}). -@item C-c C-Y -@kindex C-c C-Y +@item C-c C-M-y +@kindex C-c C-M-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}). @@ -448,86 +650,16 @@ Insert a signature at the end of the buffer @findex message-insert-headers Insert the message headers (@code{message-insert-headers}). -@end table - -@table @code -@item message-ignored-cited-headers -@vindex message-ignored-cited-headers -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-citation-line-function -@vindex message-citation-line-function -Function called to insert the citation line. The default is -@code{message-insert-citation-line}, which will lead to citation lines -that look like: - -@example -Hallvard B Furuseth writes: -@end example - -Point will be at the beginning of the body of the message when this -function is called. - -@item message-yank-prefix -@vindex message-yank-prefix -@cindex yanking -@cindex quoting -When you are replying to or following up an article, you normally want -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-indentation-spaces -@vindex message-indentation-spaces -Number of spaces to indent yanked messages. - -@item message-cite-function -@vindex message-cite-function -@findex message-cite-original -@findex sc-cite-original -@findex message-cite-original-without-signature -@cindex Supercite -Function for citing an original message. The default is -@code{message-cite-original}, which simply inserts the original message -and prepends @samp{> } to each line. -@code{message-cite-original-without-signature} does the same, but elides -the signature. You can also set it to @code{sc-cite-original} to use -Supercite. - -@item message-indent-citation-function -@vindex message-indent-citation-function -Function for modifying a citation just inserted in the mail buffer. -This can also be a list of functions. Each function can find the -citation between @code{(point)} and @code{(mark t)}. And each function -should leave point and mark around the citation text as modified. - -@item message-signature -@vindex message-signature -String to be inserted at the end of the message buffer. If @code{t} -(which is the default), the @code{message-signature-file} file will be -inserted instead. If a function, the result from the function will be -used instead. If a form, the result from the form will be used instead. -If this variable is @code{nil}, no signature will be inserted at all. - -@item message-signature-file -@vindex message-signature-file -File containing the signature to be inserted at the end of the buffer. -The default is @samp{~/.signature}. +@item C-c M-n +@kindex C-c M-n +@findex message-insert-disposition-notification-to +Insert a request for a disposition +notification. (@code{message-insert-disposition-notification-to}). +This means that if the recipient support RFC 2298 she might send you a +notification that she received the message. @end table -Note that RFC1036bis says that a signature should be preceded by the three -characters @samp{-- } on a line by themselves. This is to make it -easier for the recipient to automatically recognize and process the -signature. So don't remove those characters, even though you might feel -that they ruin your beautiful design, like, totally. - -Also note that no signature should be more than four lines long. -Including ASCII graphics is an efficient way to get everybody to believe -that you are silly and have nothing important to say. - @node MIME @section MIME @@ -543,13 +675,170 @@ automatically add the @code{Content-Type} and The most typical thing users want to use the multipart things in @sc{mime} for is to add ``attachments'' to mail they send out. This can -be done with the @code{C-c C-a} command, which will prompt for a file +be done with the @kbd{C-c C-a} command, which will prompt for a file name and a @sc{mime} type. 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 +@cindex PGP/MIME +@cindex sign +@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 PGP (RFC 1991), @sc{pgp/mime} (RFC 2015/3156) and @sc{s/mime}. +Instructing MML to perform security operations on a @sc{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 + +@item C-c C-m s s +@kindex C-c C-m s s +@findex mml-secure-message-sign-smime + +Digitally sign current message using @sc{s/mime}. + +@item C-c C-m s o +@kindex C-c C-m s o +@findex mml-secure-message-sign-pgp + +Digitally sign current message using PGP. + +@item C-c C-m s p +@kindex C-c C-m s p +@findex mml-secure-message-sign-pgpmime + +Digitally sign current message using @sc{pgp/mime}. + +@item C-c C-m c s +@kindex C-c C-m c s +@findex mml-secure-message-encrypt-smime + +Digitally encrypt current message using @sc{s/mime}. + +@item C-c C-m c o +@kindex C-c C-m c o +@findex mml-secure-message-encrypt-pgp + +Digitally encrypt current message using PGP. + +@item C-c C-m c p +@kindex C-c C-m c p +@findex mml-secure-message-encrypt-pgpmime + +Digitally encrypt current message using @sc{pgp/mime}. + +@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 +@sc{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 @sc{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 +mail is actually signed or encrypted. After invoking the above +sign/encrypt commands, it is possible to preview the raw article by +using @kbd{C-u C-c RET 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 @sc{pgp/mime} nor @sc{s/mime} encrypt/signs +RFC822 headers. They only operate on the @sc{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, @sc{s/mime}, various PKCS standards, OpenSSL and +so on. + +The @sc{s/mime} support in Message (and MML) require OpenSSL. OpenSSL +perform the actual @sc{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 @sc{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 +@sc{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 +@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 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 @sc{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 +@kbd{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 @sc{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 @file{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 + +@sc{pgp/mime} requires an external OpenPGP implementation, such as GNU +Privacy Guard (@uref{http://www.gnupg.org/}). It also requires an +Emacs interface to it, such as Mailcrypt (available from +@uref{http://www.nb.net/~lbudney/linux/software/mailcrypt.html}) or +Florian Weimer's @code{gpg.el}. + +@vindex gpg-temp-directory +Note, if you are using the @code{gpg.el} you must make sure that the +path specified by @code{gpg-temp-directory} have permissions 0700. + +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 @@ -568,8 +857,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 @@ -585,7 +875,7 @@ Delete all text in the body of the message that is outside the region @item M-RET @kindex M-RET -@kindex message-newline-and-reformat +@findex message-newline-and-reformat Insert four newlines, and then reformat if inside quoted text. Here's an example: @@ -652,7 +942,21 @@ Bury the message buffer and exit (@code{message-dont-send}). @item C-c C-k @kindex C-c C-k @findex message-kill-buffer -Kill the message buffer and exit (@code{message-kill-buffer}). +Kill the message buffer and exit (@code{message-kill-buffer}). It will +delete the message frame if it has been created exclusively for the +message buffer. If the option +@code{message-kill-buffer-and-remove-file} is non-@code{nil} and the +backup file has been created for the message buffer, it will also remove +the file after prompting to the user. + +@item C-x k +@kindex C-x k +@findex message-mimic-kill-buffer +@vindex message-kill-buffer-and-remove-file +This is an imitation for @code{kill-buffer} +(@code{message-mimic-kill-buffer}). It dynamically binds the variable +@code{message-kill-buffer-and-remove-file} to @code{nil} and calls the +function @code{message-kill-buffer}. @end table @@ -685,6 +989,51 @@ No expansion will be performed upon sending of the message---all expansions have to be done explicitly. +@node Spelling +@section Spelling +@cindex spelling +@findex ispell-message + +There are two popular ways to have Emacs spell-check your messages: +@code{ispell} and @code{flyspell}. @code{ispell} is the older and +probably more popular package. You typically first write the message, +and then run the entire thing through @code{ispell} and fix all the +typos. To have this happen automatically when you send a message, put +something like the following in your @file{.emacs} file: + +@lisp +(add-hook 'message-send-hook 'ispell-message) +@end lisp + +@vindex ispell-message-dictionary-alist +If you're in the habit of writing in different languages, this can be +controlled by the @code{ispell-message-dictionary-alist} variable: + +@lisp +(setq ispell-message-dictionary-alist + '(("^Newsgroups:.*\\bde\\." . "deutsch8") + (".*" . "default"))) +@end lisp + +@code{ispell} depends on having the external @samp{ispell} command +installed. + +The other popular method is using @code{flyspell}. This package checks +your spelling while you're writing, and marks any mis-spelled words in +various ways. + +To use @code{flyspell}, put something like the following in your +@file{.emacs} file: + +@lisp +(defun my-message-setup-routine () + (flyspell-mode 1)) +(add-hook 'message-setup-hook 'my-message-setup-routine) +@end lisp + +@code{flyspell} depends on having the external @samp{ispell} command +installed. + @node Variables @chapter Variables @@ -695,6 +1044,7 @@ expansions have to be done explicitly. * Mail Variables:: Other mail variables. * News Headers:: Customizing news headers. * News Variables:: Other news variables. +* Insertion Variables:: Customizing how things are inserted. * Various Message Variables:: Other message variables. * Sending Variables:: Variables for sending. * Message Buffers:: How Message names its buffers. @@ -715,8 +1065,14 @@ look sufficiently similar. @item message-generate-headers-first @vindex message-generate-headers-first -If non-@code{nil}, generate all headers before starting to compose the -message. +If non-@code{nil}, generate all required headers before starting to +compose the message. + +The variables @code{message-required-mail-headers} and +@code{message-required-news-headers} specify which headers are required. + +Note that some headers will be removed and re-generated before posting, +because of the variable @code{message-deletable-headers} (see below). @item message-from-style @vindex message-from-style @@ -759,8 +1115,11 @@ buffers. @item message-subject-re-regexp @vindex message-subject-re-regexp +@cindex Aw: +@cindex Sv: +@cindex Re: Responses to messages have subjects that start with @samp{Re: }. This -is @emph{not} an abbreviation of the English word ``response'', but in +is @emph{not} an abbreviation of the English word ``response'', but is Latin, and means ``in response to''. Some illiterate nincompoops have failed to grasp this fact, and have ``internationalized'' their software to use abonimations like @samp{Aw: } (``antwort'') or @samp{Sv: } @@ -769,6 +1128,19 @@ 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. +Here's an example of a value to deal with these headers when +responding to a message: + +@lisp +(setq message-subject-re-regexp + "^\\(\\(\\([Rr][Ee]\\|[Ss][Vv]\\|[Aa][Ww]\\): *\\)+\\)) +@end lisp + +@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 @@ -780,12 +1152,12 @@ just throw away non-compliant mail. @vindex message-required-mail-headers @xref{News Headers}, for the syntax of this variable. It is @code{(From Date Subject (optional . In-Reply-To) Message-ID Lines -(optional . X-Mailer))} by default. +(optional . User-Agent))} by default. @item message-ignored-mail-headers @vindex message-ignored-mail-headers Regexp of headers to be removed before mailing. The default is -@samp{^[GF]cc:\\|^Resent-Fcc:}. +@samp{^[GF]cc:\\|^Resent-Fcc:\\|^Xref:\\|^X-Draft-From:}. @item message-default-mail-headers @vindex message-default-mail-headers @@ -801,9 +1173,15 @@ buffers that are initialized as mail. @table @code @item message-send-mail-function @vindex message-send-mail-function -Function used to send the current buffer as mail. The default is -@code{message-send-mail-with-sendmail}. If you prefer using MH -instead, set this variable to @code{message-send-mail-with-mh}. +@findex message-send-mail-with-sendmail +@findex message-send-mail-with-mh +@findex message-send-mail-with-qmail +@findex smtpmail-send-it +@findex feedmail-send-it +Function used to send the current buffer as mail. The default is +@code{message-send-mail-with-sendmail}. Other valid values include +@code{message-send-mail-with-mh}, @code{message-send-mail-with-qmail}, +@code{smtpmail-send-it} and @code{feedmail-send-it}. @item message-mh-deletable-headers @vindex message-mh-deletable-headers @@ -813,6 +1191,12 @@ 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 headers. +@item message-send-mail-partially-limit +@vindex message-send-mail-partially-limit +The limitation of messages sent as message/partial. +The lower bound of message size in characters, beyond which the message +should be sent in several parts. If it is nil, the size is unlimited. + @end table @@ -868,16 +1252,11 @@ 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 +@item User-Agent +@cindex User-Agent This optional header will be filled out according to the @code{message-newsreader} local variable. -@item X-Mailer -This optional header will be filled out according to the -@code{message-mailer} local variable, unless there already is an -@code{X-Newsreader} header present. - @item In-Reply-To This optional header is filled out using the @code{Date} and @code{From} header of the article being replied to. @@ -993,7 +1372,7 @@ All these conditions are checked by default. @item message-ignored-news-headers @vindex message-ignored-news-headers Regexp of headers to be removed before posting. The default is@* -@samp{^NNTP-Posting-Host:\\|^Xref:\\|^[BGF]cc:\\|^Resent-Fcc:}. +@samp{^NNTP-Posting-Host:\\|^Xref:\\|^[BGF]cc:\\|^Resent-Fcc:\\|^X-Draft-From:}. @item message-default-news-headers @vindex message-default-news-headers @@ -1020,10 +1399,151 @@ posting a prepared news message. @end table +@node Insertion Variables +@section Insertion Variables + +@table @code +@item message-ignored-cited-headers +@vindex message-ignored-cited-headers +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 +@cindex attribution line +Function called to insert the citation line. The default is +@code{message-insert-citation-line}, which will lead to citation lines +that look like: + +@example +Hallvard B Furuseth writes: +@end example + +Point will be at the beginning of the body of the message when this +function is called. + +Note that Gnus provides a feature where clicking on `writes:' hides the +cited text. If you change the citation line too much, readers of your +messages will have to adjust their Gnus, too. See the variable +@code{gnus-cite-attribution-suffix}. @xref{Article Highlighting, , +Article Highlighting, gnus}, for details. + +@item message-yank-prefix +@vindex message-yank-prefix +@cindex yanking +@cindex quoting +When you are replying to or following up an article, you normally want +to quote the person you are answering. Inserting quoted text is done +by @dfn{yanking}, and each line you yank will have +@code{message-yank-prefix} prepended to it (except for quoted and +empty lines which uses @code{message-yank-cited-prefix}). The default +is @samp{> }. + +@item message-yank-cited-prefix +@vindex message-yank-cited-prefix +@cindex yanking +@cindex cited +@cindex quoting +When yanking text from a article which contains no text or already +cited text, each line will be prefixed with the contents of this +variable. The default is @samp{>}. See also +@code{message-yank-prefix}. + +@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. + +@item message-cite-function +@vindex message-cite-function +@findex message-cite-original +@findex sc-cite-original +@findex message-cite-original-without-signature +@cindex Supercite +Function for citing an original message. The default is +@code{message-cite-original}, which simply inserts the original message +and prepends @samp{> } to each line. +@code{message-cite-original-without-signature} does the same, but elides +the signature. You can also set it to @code{sc-cite-original} to use +Supercite. + +@item message-suspend-font-lock-when-citing +@vindex message-suspend-font-lock-when-citing +If non-@code{nil}, suspend font-lock'ing while citing an original +message. Some lazy demand-driven fontification tools (or Emacs itself) +have a bug that they often miss a buffer to be fontified. It will +mostly occur when Emacs prompts user for any inputs in the minibuffer. +Setting this option to non-@code{nil} may help you to avoid unpleasant +errors even if it is an add-hoc expedient. + +@item message-indent-citation-function +@vindex message-indent-citation-function +Function for modifying a citation just inserted in the mail buffer. +This can also be a list of functions. Each function can find the +citation between @code{(point)} and @code{(mark t)}. And each function +should leave point and mark around the citation text as modified. + +@item message-signature +@vindex message-signature +String to be inserted at the end of the message buffer. If @code{t} +(which is the default), the @code{message-signature-file} file will be +inserted instead. If a function, the result from the function will be +used instead. If a form, the result from the form will be used instead. +If this variable is @code{nil}, no signature will be inserted at all. + +@item message-signature-file +@vindex message-signature-file +File containing the signature to be inserted at the end of the buffer. +The default is @file{~/.signature}. + +@end table + +Note that RFC1036bis says that a signature should be preceded by the three +characters @samp{-- } on a line by themselves. This is to make it +easier for the recipient to automatically recognize and process the +signature. So don't remove those characters, even though you might feel +that they ruin your beautiful design, like, totally. + +Also note that no signature should be more than four lines long. +Including ASCII graphics is an efficient way to get everybody to believe +that you are silly and have nothing important to say. + + @node Various Message Variables @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 @@ -1079,9 +1599,8 @@ If you want to add certain headers before sending, you can use the @lisp (add-hook 'message-send-hook 'my-message-add-content) (defun my-message-add-content () - (message-add-header - "X-In-No-Sense: Nonsense" - "X-Whatever: no")) + (message-add-header "X-In-No-Sense: Nonsense") + (message-add-header "X-Whatever: no")) @end lisp This function won't add the header if the header is already present. @@ -1143,7 +1662,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 @@ -1153,7 +1672,12 @@ the mailed copy. If the string contains the format spec @samp{%s}, the newsgroups the article has been posted to will be inserted there. If this variable is @code{nil}, no such courtesy message will be added. The default value is @samp{"The following message is a courtesy copy of -an article\nthat has been posted to %s as well.\n\n"}. +an article\\nthat has been posted to %s as well.\\n\\n"}. + +@item message-fcc-externalize-attachments +@vindex message-fcc-externalize-attachments +If @code{nil}, attach files as normal parts in Fcc copies; if it is +non-@code{nil}, attach local files as external parts. @end table @@ -1206,9 +1730,28 @@ say: @end lisp @item message-kill-buffer-on-exit -@findex message-kill-buffer-on-exit +@vindex message-kill-buffer-on-exit If non-@code{nil}, kill the buffer immediately on exit. +@item message-kill-buffer-query-function +@vindex message-kill-buffer-query-function +@findex message-kill-buffer +@findex message-mimic-kill-buffer +Function used to prompt user whether to kill the message buffer when the +command @code{message-kill-buffer} or @code{message-mimic-kill-buffer} +is used. It defaults to @code{yes-or-no-p}. You may alter the value to +@code{y-or-n-p}, @code{nnheader-Y-or-n-p}, etc. If it is @code{t}, the +buffer will be killed without query. + +@item message-kill-buffer-and-remove-file +@vindex message-kill-buffer-and-remove-file +@findex message-kill-buffer +@findex message-mimic-kill-buffer +If it is non-@code{nil}, remove the backup file if it exists with a +query to the user, after the message buffer is killed. Otherwise the +file won't be removed. It defaults to @code{t}. However, it is treated +as @code{nil} when the command `message-mimic-kill-buffer' is used. + @end table @@ -1258,7 +1801,7 @@ a form to be @code{eval}ed. Message uses virtually only its own variables---older @code{mail-} variables aren't consulted. To force Message to take those variables -into account, you can put the following in your @code{.emacs} file: +into account, you can put the following in your @file{.emacs} file: @lisp (require 'messcompat)