X-Git-Url: https://cgit.sxemacs.org/?a=blobdiff_plain;f=texi%2Fmessage.texi;h=78168acb465df8f48efb1ef3cf2efed3e37fcd02;hb=5b8ecce52d86ed7352e6e5b5d768c34321a4c58d;hp=3599e59b7a7196843b60da3afb5bd68d4e7757ad;hpb=a3e52de2271f1336cb7e3c31c14bd122f4db609e;p=gnus diff --git a/texi/message.texi b/texi/message.texi index 3599e59b7..6d60fe227 100644 --- a/texi/message.texi +++ b/texi/message.texi @@ -1,10 +1,13 @@ \input texinfo @c -*-texinfo-*- @setfilename message -@settitle Message 5.4.57 Manual +@settitle Pterodactyl Message 0.86 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 @iftex @finalout @end iftex @@ -14,7 +17,7 @@ This file documents Message, the Emacs message composition mode. -Copyright (C) 1996 Free Software Foundation, Inc. +Copyright (C) 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 @@ -39,13 +42,13 @@ into another language, under the above conditions for modified versions. @tex @titlepage -@title Message 5.4.57 Manual +@title Pterodactyl Message 0.86 Manual @author by Lars Magne Ingebrigtsen @page @vskip 0pt plus 1filll -Copyright @copyright{} 1996 Free Software Foundation, Inc. +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 @@ -67,21 +70,22 @@ into another language, under the above conditions for modified versions. @node Top @top Message -All message composition (both mail and news) takes place in Message mode -buffers. +All message composition from Gnus (both mail and news) takes place in +Message mode buffers. @menu * Interface:: Setting up message buffers. * Commands:: Commands you can execute in message mode buffers. * Variables:: Customizing the message buffers. * Compatibility:: Making Message backwards compatible. +* Appendices:: More technical things. * Index:: Variable, function and concept index. * Key Index:: List of Message mode keys. @end menu -This manual corresponds to Message 5.4.57. Message is distributed with -the Gnus distribution bearing the same version number as this manual -has. +This manual corresponds to Pterodactyl Message 0.86. Message is +distributed with the Gnus distribution bearing the same version number +as this manual. @node Interface @@ -112,22 +116,22 @@ sending it. @section New Mail Message @findex message-mail -The @code{message-mail} command pops up a new message buffer. +The @code{message-mail} command pops up a new message buffer. Two optional parameters are accepted: The first will be used as the @code{To} header and the second as the @code{Subject} header. If these -aren't present, those two headers will be empty. +are @code{nil}, those two headers will be empty. @node New News Message @section New News Message @findex message-news -The @code{message-news} command pops up a new message buffer. +The @code{message-news} command pops up a new message buffer. This function accepts two optional parameters. The first will be used as the @code{Newsgroups} header and the second as the @code{Subject} -header. If these aren't present, those two headers will be empty. +header. If these are @code{nil}, those two headers will be empty. @node Reply @@ -138,9 +142,9 @@ The @code{message-reply} function pops up a message buffer that's a reply to the message in the current buffer. @vindex message-reply-to-function -Message uses the normal methods to determine where replies are to go, -but you can change the behavior to suit your needs by fiddling with the -@code{message-reply-to-function} variable. +Message uses the normal methods to determine where replies are to go +(@pxref{Responses}), but you can change the behavior to suit your needs +by fiddling with the @code{message-reply-to-function} variable. If you want the replies to go to the @code{Sender} instead of the @code{From}, you could do something like this: @@ -149,8 +153,8 @@ 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")) - (t + (mail-fetch-field "sender")) + (t nil)))) @end lisp @@ -166,7 +170,7 @@ This function can also return a list. In that case, each list element should be a cons, where the car should be the name of an header (eg. @code{Cc}) and the cdr should be the header value (eg. @samp{larsi@@ifi.uio.no}). All these headers will be inserted into -the head of the outgoing mail. +the head of the outgoing mail. @node Wide Reply @@ -182,7 +186,7 @@ reply that goes out to all people listed in the @code{To}, @code{From} Message uses the normal methods to determine where wide replies are to go, 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}). +@code{message-reply-to-function} (@pxref{Reply}). @findex rmail-dont-reply-to-names Addresses that match the @code{rmail-dont-reply-to-names} regular @@ -229,7 +233,7 @@ supersede the message in the current buffer. Headers matching the @code{message-ignored-supersedes-headers} are removed before popping up the new message buffer. The default is@* @samp{^Path:\\|^Date\\|^NNTP-Posting-Host:\\|^Xref:\\|^Lines:\\|@* -^Received:\\|^X-From-Line:\\|Return-Path:}. +^Received:\\|^X-From-Line:\\|Return-Path:\\|^Supersedes:}. @@ -245,13 +249,13 @@ news. @item message-forward-start-separator @vindex message-forward-start-separator Delimiter inserted before forwarded messages. The default is@* -@samp{------- Start of forwarded message -------\n}. +@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}. +@samp{------- End of forwarded message -------\n}. @item message-signature-before-forwarded-message @vindex message-signature-before-forwarded-message @@ -261,7 +265,32 @@ 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. +Regexp matching header lines to be included in forwarded messages. + +@item message-make-forward-subject-function +@vindex message-make-forward-subject-function +A list of functions that are called to generate a subject header for +forwarded messages. The subject generated by the previous function is +passed into each successive function. + +The provided functions are: + +@table @code +@item message-forward-subject-author-subject +@findex message-forward-subject-author-subject +Source of article (author or newsgroup), in brackets followed by the +subject. + +@item message-forward-subject-fwd +Subject of article with @samp{Fwd:} prepended to it. +@end table + +@item message-wash-forwarded-subjects +@vindex message-wash-forwarded-subjects +If this variable is @code{t}, the subjects of forwarded messages have +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}. @end table @@ -276,7 +305,7 @@ and resend the message in the current buffer to that address. @vindex message-ignored-resent-headers Headers that match the @code{message-ignored-resent-headers} regexp will be removed before sending the message. The default is -@samp{^Return-receipt}. +@samp{^Return-receipt}. @node Bouncing @@ -287,12 +316,12 @@ The @code{message-bounce} command will, if the current buffer contains a bounced mail message, pop up a message buffer stripped of the bounce information. A @dfn{bounced message} is typically a mail you've sent out that has been returned by some @code{mailer-daemon} as -undeliverable. +undeliverable. @vindex message-ignored-bounced-headers Headers that match the @code{message-ignored-bounced-headers} regexp will be removed before popping up the buffer. The default is -@samp{^Received:}. +@samp{^\\(Received\\|Return-Path\\):}. @node Commands @@ -302,6 +331,7 @@ will be removed before popping up the buffer. The default is * Header Commands:: Commands for moving to headers. * Movement:: Moving around in message buffers. * Insertion:: Inserting things into message buffers. +* MIME:: @sc{mime} considerations. * Various Commands:: Various things. * Sending:: Actually sending the message. * Mail Aliases:: How to use mail aliases. @@ -322,57 +352,57 @@ it will be inserted. Describe the message mode. @item C-c C-f C-t -@kindex C-c C-f C-t +@kindex C-c C-f C-t @findex message-goto-to Go to the @code{To} header (@code{message-goto-to}). @item C-c C-f C-b -@kindex C-c C-f C-b +@kindex C-c C-f C-b @findex message-goto-bcc Go to the @code{Bcc} header (@code{message-goto-bcc}). @item C-c C-f C-f -@kindex C-c C-f C-f +@kindex C-c C-f C-f @findex message-goto-fcc Go to the @code{Fcc} header (@code{message-goto-fcc}). @item C-c C-f C-c -@kindex C-c C-f C-c +@kindex C-c C-f C-c @findex message-goto-cc Go to the @code{Cc} header (@code{message-goto-cc}). @item C-c C-f C-s -@kindex C-c C-f C-s +@kindex C-c C-f C-s @findex message-goto-subject Go to the @code{Subject} header (@code{message-goto-subject}). @item C-c C-f C-r -@kindex C-c C-f C-r +@kindex C-c C-f C-r @findex message-goto-reply-to Go to the @code{Reply-To} header (@code{message-goto-reply-to}). @item C-c C-f C-n -@kindex C-c C-f C-n +@kindex C-c C-f C-n @findex message-goto-newsgroups Go to the @code{Newsgroups} header (@code{message-goto-newsgroups}). @item C-c C-f C-d -@kindex C-c C-f C-d +@kindex C-c C-f C-d @findex message-goto-distribution Go to the @code{Distribution} header (@code{message-goto-distribution}). @item C-c C-f C-o -@kindex C-c C-f C-o +@kindex C-c C-f C-o @findex message-goto-followup-to Go to the @code{Followup-To} header (@code{message-goto-followup-to}). @item C-c C-f C-k -@kindex C-c C-f C-k +@kindex C-c C-f C-k @findex message-goto-keywords Go to the @code{Keywords} header (@code{message-goto-keywords}). @item C-c C-f C-u -@kindex C-c C-f C-u +@kindex C-c C-f C-u @findex message-goto-summary Go to the @code{Summary} header (@code{message-goto-summary}). @@ -384,13 +414,13 @@ Go to the @code{Summary} header (@code{message-goto-summary}). @table @kbd @item C-c C-b -@kindex C-c C-b +@kindex C-c C-b @findex message-goto-body Move to the beginning of the body of the message -(@code{message-goto-body}). +(@code{message-goto-body}). @item C-c C-i -@kindex C-c C-i +@kindex C-c C-i @findex message-goto-signature Move to the signature of the message (@code{message-goto-signature}). @@ -403,21 +433,30 @@ Move to the signature of the message (@code{message-goto-signature}). @table @kbd @item C-c C-y -@kindex 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 -(@code{message-yank-original}). +(@code{message-yank-original}). @item C-c C-q -@kindex C-c C-q +@kindex C-c C-q @findex message-fill-yanked-message -Fill the yanked message (@code{message-fill-yanked-message}). +Fill the yanked message (@code{message-fill-yanked-message}). Warning: +Can severely mess up the yanked text if its quoting conventions are +strange. You'll quickly get a feel for when it's safe, though. Anyway, +just remember that @kbd{C-x u} (@code{undo}) is available and you'll be +all right. @item C-c C-w -@kindex C-c C-w +@kindex C-c C-w @findex message-insert-signature Insert a signature at the end of the buffer -(@code{message-insert-signature}). +(@code{message-insert-signature}). + +@item C-c M-h +@kindex C-c M-h +@findex message-insert-headers +Insert the message headers (@code{message-insert-headers}). @end table @@ -431,7 +470,15 @@ 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}. +@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 @@ -441,7 +488,6 @@ 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{> }. -If it is @code{nil}, just indent the message. @item message-indentation-spaces @vindex message-indentation-spaces @@ -451,10 +497,14 @@ Number of spaces to indent yanked messages. @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}. You can also set it to -@code{sc-cite-original} to use Supercite. +@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 @@ -478,7 +528,7 @@ The default is @samp{~/.signature}. @end table -Note that RFC1036 says that a signature should be preceded by the three +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 @@ -489,6 +539,27 @@ 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 +@cindex MML +@cindex MIME +@cindex multipart +@cindex attachment + +Message is a @sc{mime}-compliant posting agent. The user generally +doesn't have to do anything to make the @sc{mime} happen---Message will +automatically add the @code{Content-Type} and +@code{Content-Transfer-Encoding} headers. + +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 +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 Various Commands @section Various Commands @@ -496,7 +567,7 @@ that you are silly and have nothing important to say. @table @kbd @item C-c C-r -@kindex C-c C-r +@kindex C-c C-r @findex message-caesar-buffer-body Caesar rotate (aka. rot13) the current message (@code{message-caesar-buffer-body}). If narrowing is in effect, just @@ -510,15 +581,50 @@ 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. +@item C-c C-z +@kindex C-c C-x +@findex message-kill-to-signature +Kill all the text up to the signature, or if that's missing, up to the +end of the message (@code{message-kill-to-signature}). + +@item C-c C-v +@kindex C-c C-v +@findex message-delete-not-region +Delete all text in the body of the message that is outside the region +(@code{message-delete-not-region}). + +@item M-RET +@kindex M-RET +@kindex message-newline-and-reformat +Insert four newlines, and then reformat if inside quoted text. + +Here's an example: + +@example +> This is some quoted text. And here's more quoted text. +@end example + +If point is before @samp{And} and you press @kbd{M-RET}, you'll get: + +@example +> This is some quoted text. + +* + +> And here's more quoted text. +@end example + +@samp{*} says where point will be placed. + @item C-c C-t -@kindex C-c C-t +@kindex C-c C-t @findex message-insert-to Insert a @code{To} header that contains the @code{Reply-To} or @code{From} header of the message you're following up -(@code{message-insert-to}). +(@code{message-insert-to}). @item C-c C-n -@kindex C-c C-n +@kindex C-c C-n @findex message-insert-newsgroups Insert a @code{Newsgroups} header that reflects the @code{Followup-To} or @code{Newsgroups} header of the article you're replying to @@ -538,15 +644,15 @@ prompt for a new buffer name. @table @kbd @item C-c C-c -@kindex C-c C-c +@kindex C-c C-c @findex message-send-and-exit Send the message and bury the current buffer -(@code{message-send-and-exit}). +(@code{message-send-and-exit}). @item C-c C-s -@kindex C-c C-s +@kindex C-c C-s @findex message-send -Send the message (@code{message-send}). +Send the message (@code{message-send}). @item C-c C-d @kindex C-c C-d @@ -609,21 +715,22 @@ expansions have to be done explicitly. @node Message Headers @section Message Headers -Message is quite aggressive on the message generation front. It has -to be -- it's a combined news and mail agent. To be able to send -combined messages, it has to generate all headers itself to ensure that -mail and news copies of messages look sufficiently similar. +Message is quite aggressive on the message generation front. It has to +be -- it's a combined news and mail agent. To be able to send combined +messages, it has to generate all headers itself (instead of letting the +mail/news system do it) to ensure that mail and news copies of messages +look sufficiently similar. @table @code @item message-generate-headers-first @vindex message-generate-headers-first If non-@code{nil}, generate all headers before starting to compose the -message. +message. @item message-from-style @vindex message-from-style -Specifies how @code{From} headers should look. There are four legal +Specifies how @code{From} headers should look. There are four valid values: @table @code @@ -653,13 +760,25 @@ ship it off again. By default, this variable makes sure that the old generated @code{Message-ID} is deleted, and a new one generated. If this isn't done, the entire empire would probably crumble, anarchy would prevail, and cats would start walking on two legs and rule the world. -Allegedly. +Allegedly. @item message-default-headers @vindex message-default-headers This string is inserted at the end of the headers in all message buffers. +@item message-subject-re-regexp +@vindex message-subject-re-regexp +Responses to messages have subjects that start with @samp{Re: }. This +is @emph{not} an abbreviation of the English word ``response'', but in +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: } +(``svar'') instead, which is meaningless and evil. However, you may +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. + @end table @@ -676,7 +795,7 @@ buffers. @item message-ignored-mail-headers @vindex message-ignored-mail-headers Regexp of headers to be removed before mailing. The default is -@samp{^Gcc:\\|^Fcc:}. +@samp{^[GF]cc:\\|^Resent-Fcc:}. @item message-default-mail-headers @vindex message-default-mail-headers @@ -687,7 +806,7 @@ buffers that are initialized as mail. @node Mail Variables -@section Mail Variables +@section Mail Variables @table @code @item message-send-mail-function @@ -700,8 +819,9 @@ instead, set this variable to @code{message-send-mail-with-mh}. @vindex message-mh-deletable-headers 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. Set it to -@code{nil} if your MH can handle these headers. +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. @end table @@ -712,7 +832,7 @@ the default), these headers will be removed before mailing. Set it to @vindex message-required-news-headers @code{message-required-news-headers} a list of header symbols. These headers will either be automatically generated, or, if that's -impossible, they will be prompted for. The following symbols are legal: +impossible, they will be prompted for. The following symbols are valid: @table @code @@ -727,7 +847,7 @@ This required header will be filled out with the result of the @item Subject @cindex Subject -This required header will be prompted for if not present already. +This required header will be prompted for if not present already. @item Newsgroups @cindex Newsgroups @@ -818,31 +938,37 @@ Other variables for customizing outgoing news articles: @item message-syntax-checks @vindex message-syntax-checks -If non-@code{nil}, Message will attempt to check the legality of the -headers, as well as some other stuff, before posting. You can control -the granularity of the check by adding or removing elements from this -list. Legal elements are: +Controls what syntax checks should not be performed on outgoing posts. +To disable checking of long signatures, for instance, add + +@lisp +(signature . disabled) +@end lisp + +to this list. + +Valid checks are: @table @code -@item subject-cmsg +@item subject-cmsg Check the subject for commands. @item sender @cindex Sender -Insert a new @code{Sender} header if the @code{From} header looks odd. -@item multiple-headers +Insert a new @code{Sender} header if the @code{From} header looks odd. +@item multiple-headers Check for the existence of multiple equal headers. -@item sendsys +@item sendsys @cindex sendsys Check for the existence of version and sendsys commands. @item message-id Check whether the @code{Message-ID} looks ok. @item from Check whether the @code{From} header seems nice. -@item long-lines +@item long-lines @cindex long lines Check for too long lines. @item control-chars -Check for illegal characters. +Check for invalid characters. @item size Check for excessive size. @item new-text @@ -855,14 +981,19 @@ Check whether the article has an @code{Approved} header, which is something only moderators should include. @item empty Check whether the article is empty. +@item invisible-text +Check whether there is any invisible text in the buffer. @item empty-headers Check whether any of the headers are empty. @item existing-newsgroups -Check whether the newsgroups mentioned in the @code{Newsgroups} and +Check whether the newsgroups mentioned in the @code{Newsgroups} and @code{Followup-To} headers exist. @item valid-newsgroups Check whether the @code{Newsgroups} and @code{Followup-to} headers are valid syntactically. +@item repeated-newsgroups +Check whether the @code{Newsgroups} and @code{Followup-to} headers +contains repeated group names. @item shorten-followup-to Check whether to add a @code{Followup-to} header to shorten the number of groups to post to. @@ -873,7 +1004,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:\\|^Bcc:\\|^Gcc:\\|^Fcc:}. +@samp{^NNTP-Posting-Host:\\|^Xref:\\|^[BGF]cc:\\|^Resent-Fcc:}. @item message-default-news-headers @vindex message-default-news-headers @@ -890,11 +1021,12 @@ buffers that are initialized as news. @item message-send-news-function @vindex message-send-news-function Function used to send the current buffer as news. The default is -@code{message-send-news}. +@code{message-send-news}. @item message-post-method @vindex message-post-method -Method used for posting a prepared news message. +Gnusish @dfn{select method} (see the Gnus manual for details) used for +posting a prepared news message. @end table @@ -906,7 +1038,7 @@ Method used for posting a prepared news message. @item message-signature-separator @vindex message-signature-separator Regexp matching the signature separator. It is @samp{^-- *$} by -default. +default. @item mail-header-separator @vindex mail-header-separator @@ -915,24 +1047,21 @@ follows this line--} by default. @item message-directory @vindex message-directory -Directory used by many mailey things. The default is @file{~/Mail/}. - -@item message-autosave-directory -@vindex message-autosave-directory -Directory where message buffers will be autosaved to. +Directory used by many mailey things. The default is @file{~/Mail/}. @item message-signature-setup-hook @vindex message-signature-setup-hook Hook run when initializing the message buffer. It is run after the -headers have been inserted but before the signature has been inserted. +headers have been inserted but before the signature has been inserted. @item message-setup-hook @vindex message-setup-hook -Hook run as the last thing when the message buffer has been initialized. +Hook run as the last thing when the message buffer has been initialized, +but before yanked text is inserted. @item message-header-setup-hook @vindex message-header-setup-hook -Hook called narrowed to the headers after initializing the headers. +Hook called narrowed to the headers after initializing the headers. For instance, if you're running Gnus and wish to insert a @samp{Mail-Copies-To} header in all your news articles and all messages @@ -946,7 +1075,8 @@ you send to mailing lists, you could do something like the following: (gnus-group-find-parameter group 'to-list)) (insert "Mail-Copies-To: never\n")))) -(add-hook 'message-header-setup-hook 'my-message-header-setup-hook) +(add-hook 'message-header-setup-hook + 'my-message-header-setup-hook) @end lisp @item message-send-hook @@ -961,9 +1091,8 @@ If you want to add certain headers before sending, you can use the (add-hook 'message-send-hook 'my-message-add-content) (defun my-message-add-content () (message-add-header - "Mime-Version: 1.0" - "Content-Type: text/plain" - "Content-Transfer-Encoding: 7bit")) + "X-In-No-Sense: Nonsense" + "X-Whatever: no")) @end lisp This function won't add the header if the header is already present. @@ -1022,11 +1151,11 @@ A function to be called if @var{predicate} returns non-@code{nil}. @table @code -@item message-fcc-handler-function -@vindex message-fcc-handler-function +@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 -function is @code{rmail-output} which saves in Unix mailbox format. +function is @code{message-output} which saves in Unix mailbox format. @item message-courtesy-message @vindex message-courtesy-message @@ -1035,7 +1164,7 @@ 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"}. @end table @@ -1088,7 +1217,7 @@ If non-@code{nil}, kill the buffer immediately on exit. When Message is being used from a news/mail reader, the reader is likely to want to perform some task after the message has been sent. Perhaps return to the previous window configuration or mark an article as -replied. +replied. @vindex message-kill-actions @vindex message-postpone-actions @@ -1101,7 +1230,7 @@ C-d} which postpones the message editing and buries the message buffer, and @kbd{C-c C-k} which kills the message buffer. Each of these actions have lists associated with them that contains actions to be executed: @code{message-send-actions}, @code{message-exit-actions}, -@code{message-postpone-actions}, and @code{message-kill-actions}. +@code{message-postpone-actions}, and @code{message-kill-actions}. Message provides a function to interface with these lists: @code{message-add-action}. The first parameter is the action to be @@ -1138,6 +1267,74 @@ This will initialize many Message variables from the values in the corresponding mail variables. +@node Appendices +@chapter Appendices + +@menu +* Responses:: Standard rules for determining where responses go. +@end menu + + +@node Responses +@section Responses + +To determine where a message is to go, the following algorithm is used +by default. + +@table @dfn +@item reply +A @dfn{reply} is when you want to respond @emph{just} to the person who +sent the message via mail. There will only be one recipient. To +determine who the recipient will be, the following headers are +consulted, in turn: + +@table @code +@item Reply-To + +@item From +@end table + + +@item wide reply +A @dfn{wide reply} is a mail response that includes @emph{all} entities +mentioned in the message you are responded to. All mailboxes from the +following headers will be concatenated to form the outgoing +@code{To}/@code{Cc} headers: + +@table @code +@item From +(unless there's a @code{Reply-To}, in which case that is used instead). + +@item Cc + +@item To +@end table + +If a @code{Mail-Copies-To} header is present, it will also be included +in the list of mailboxes. If this header is @samp{never}, that means +that the @code{From} (or @code{Reply-To}) mailbox will be suppressed. + + +@item followup +A @dfn{followup} is a response sent via news. The following headers +(listed in order of precedence) determine where the response is to be +sent: + +@table @code + +@item Followup-To + +@item Newsgroups + +@end table + +If a @code{Mail-Copies-To} header is present, it will be used as the +basis of the new @code{Cc} header, except if this header is +@samp{never}. + +@end table + + @node Index @chapter Index