1 \input texinfo @c -*-texinfo-*-
4 @settitle T-gnus 6.14 Message Manual
9 @c * Message: (message). Mail and news composition mode that goes with Gnus.
14 @setchapternewpage odd
18 This file documents Message, the Emacs message composition mode.
20 Copyright (C) 1996,97,98,99 Free Software Foundation, Inc.
22 Permission is granted to make and distribute verbatim copies of
23 this manual provided the copyright notice and this permission notice
24 are preserved on all copies.
27 Permission is granted to process this file through Tex and print the
28 results, provided the printed document carries copying permission
29 notice identical to this one except for the removal of this paragraph
30 (this paragraph not being relevant to the printed manual).
33 Permission is granted to copy and distribute modified versions of this
34 manual under the conditions for verbatim copying, provided also that the
35 entire resulting derived work is distributed under the terms of a
36 permission notice identical to this one.
38 Permission is granted to copy and distribute translations of this manual
39 into another language, under the above conditions for modified versions.
45 @title T-gnus 6.14 Message Manual
47 @author by Lars Magne Ingebrigtsen
50 @vskip 0pt plus 1filll
51 Copyright @copyright{} 1996,97,98,99 Free Software Foundation, Inc.
53 Permission is granted to make and distribute verbatim copies of
54 this manual provided the copyright notice and this permission notice
55 are preserved on all copies.
57 Permission is granted to copy and distribute modified versions of this
58 manual under the conditions for verbatim copying, provided that the
59 entire resulting derived work is distributed under the terms of a
60 permission notice identical to this one.
62 Permission is granted to copy and distribute translations of this manual
63 into another language, under the above conditions for modified versions.
73 All message composition from Gnus (both mail and news) takes place in
77 * Interface:: Setting up message buffers.
78 * Commands:: Commands you can execute in message mode buffers.
79 * Variables:: Customizing the message buffers.
80 * Compatibility:: Making Message backwards compatible.
81 * Appendices:: More technical things.
82 * Index:: Variable, function and concept index.
83 * Key Index:: List of Message mode keys.
86 This manual corresponds to T-gnus 6.14 Message. Message is
87 distributed with the Gnus distribution bearing the same version number
94 When a program (or a person) wants to respond to a message -- reply,
95 follow up, forward, cancel -- the program (or person) should just put
96 point in the buffer where the message is and call the required command.
97 @code{Message} will then pop up a new @code{message} mode buffer with
98 appropriate headers filled out, and the user can edit the message before
102 * New Mail Message:: Editing a brand new mail message.
103 * New News Message:: Editing a brand new news message.
104 * Reply:: Replying via mail.
105 * Wide Reply:: Responding to all people via mail.
106 * Followup:: Following up via news.
107 * Canceling News:: Canceling a news article.
108 * Superseding:: Superseding a message.
109 * Forwarding:: Forwarding a message via news or mail.
110 * Resending:: Resending a mail message.
111 * Bouncing:: Bouncing a mail message.
115 @node New Mail Message
116 @section New Mail Message
119 The @code{message-mail} command pops up a new message buffer.
121 Two optional parameters are accepted: The first will be used as the
122 @code{To} header and the second as the @code{Subject} header. If these
123 are @code{nil}, those two headers will be empty.
126 @node New News Message
127 @section New News Message
130 The @code{message-news} command pops up a new message buffer.
132 This function accepts two optional parameters. The first will be used
133 as the @code{Newsgroups} header and the second as the @code{Subject}
134 header. If these are @code{nil}, those two headers will be empty.
140 @findex message-reply
141 The @code{message-reply} function pops up a message buffer that's a
142 reply to the message in the current buffer.
144 @vindex message-reply-to-function
145 Message uses the normal methods to determine where replies are to go
146 (@pxref{Responses}), but you can change the behavior to suit your needs
147 by fiddling with the @code{message-reply-to-function} variable.
149 If you want the replies to go to the @code{Sender} instead of the
150 @code{From}, you could do something like this:
153 (setq message-reply-to-function
155 (cond ((equal (mail-fetch-field "from") "somebody")
156 (mail-fetch-field "sender"))
161 This function will be called narrowed to the head of the article that is
164 As you can see, this function should return a string if it has an
165 opinion as to what the To header should be. If it does not, it should
166 just return @code{nil}, and the normal methods for determining the To
169 This function can also return a list. In that case, each list element
170 should be a cons, where the car should be the name of an header
171 (eg. @code{Cc}) and the cdr should be the header value
172 (eg. @samp{larsi@@ifi.uio.no}). All these headers will be inserted into
173 the head of the outgoing mail.
179 @findex message-wide-reply
180 The @code{message-wide-reply} pops up a message buffer that's a wide
181 reply to the message in the current buffer. A @dfn{wide reply} is a
182 reply that goes out to all people listed in the @code{To}, @code{From}
183 (or @code{Reply-to}) and @code{Cc} headers.
185 @vindex message-wide-reply-to-function
186 Message uses the normal methods to determine where wide replies are to go,
187 but you can change the behavior to suit your needs by fiddling with the
188 @code{message-wide-reply-to-function}. It is used in the same way as
189 @code{message-reply-to-function} (@pxref{Reply}).
191 @findex message-dont-reply-to-names
192 Addresses that match the @code{message-dont-reply-to-names} regular
193 expression will be removed from the @code{Cc} header.
199 @findex message-followup
200 The @code{message-followup} command pops up a message buffer that's a
201 followup to the message in the current buffer.
203 @vindex message-followup-to-function
204 Message uses the normal methods to determine where followups are to go,
205 but you can change the behavior to suit your needs by fiddling with the
206 @code{message-followup-to-function}. It is used in the same way as
207 @code{message-reply-to-function} (@pxref{Reply}).
209 @vindex message-use-followup-to
210 The @code{message-use-followup-to} variable says what to do about
211 @code{Followup-To} headers. If it is @code{use}, always use the value.
212 If it is @code{ask} (which is the default), ask whether to use the
213 value. If it is @code{t}, use the value unless it is @samp{poster}. If
214 it is @code{nil}, don't use the value.
218 @section Canceling News
220 @findex message-cancel-news
221 The @code{message-cancel-news} command cancels the article in the
228 @findex message-supersede
229 The @code{message-supersede} command pops up a message buffer that will
230 supersede the message in the current buffer.
232 @vindex message-ignored-supersedes-headers
233 Headers matching the @code{message-ignored-supersedes-headers} are
234 removed before popping up the new message buffer. The default is@*
235 @samp{^Path:\\|^Date\\|^NNTP-Posting-Host:\\|^Xref:\\|^Lines:\\|@*
236 ^Received:\\|^X-From-Line:\\|Return-Path:\\|^Supersedes:}.
243 @findex message-forward
244 The @code{message-forward} command pops up a message buffer to forward
245 the message in the current buffer. If given a prefix, forward using
249 @item message-ignored-forward-headers
250 @vindex message-ignored-forward-headers
251 All headers that match this regexp will be deleted when forwarding a message.
253 @item message-make-forward-subject-function
254 @vindex message-make-forward-subject-function
255 A list of functions that are called to generate a subject header for
256 forwarded messages. The subject generated by the previous function is
257 passed into each successive function.
259 The provided functions are:
262 @item message-forward-subject-author-subject
263 @findex message-forward-subject-author-subject
264 Source of article (author or newsgroup), in brackets followed by the
267 @item message-forward-subject-fwd
268 Subject of article with @samp{Fwd:} prepended to it.
271 @item message-wash-forwarded-subjects
272 @vindex message-wash-forwarded-subjects
273 If this variable is @code{t}, the subjects of forwarded messages have
274 the evidence of previous forwards (such as @samp{Fwd:}, @samp{Re:},
275 @samp{(fwd)}) removed before the new subject is
276 constructed. The default value is @code{nil}.
284 @findex message-resend
285 The @code{message-resend} command will prompt the user for an address
286 and resend the message in the current buffer to that address.
288 @vindex message-ignored-resent-headers
289 Headers that match the @code{message-ignored-resent-headers} regexp will
290 be removed before sending the message. The default is
291 @samp{^Return-receipt}.
297 @findex message-bounce
298 The @code{message-bounce} command will, if the current buffer contains a
299 bounced mail message, pop up a message buffer stripped of the bounce
300 information. A @dfn{bounced message} is typically a mail you've sent
301 out that has been returned by some @code{mailer-daemon} as
304 @vindex message-ignored-bounced-headers
305 Headers that match the @code{message-ignored-bounced-headers} regexp
306 will be removed before popping up the buffer. The default is
307 @samp{^\\(Received\\|Return-Path\\):}.
314 * Header Commands:: Commands for moving to headers.
315 * Movement:: Moving around in message buffers.
316 * Insertion:: Inserting things into message buffers.
317 * MIME:: @sc{mime} considerations.
318 * Various Commands:: Various things.
319 * Sending:: Actually sending the message.
320 * Mail Aliases:: How to use mail aliases.
324 @node Header Commands
325 @section Header Commands
327 All these commands move to the header in question. If it doesn't exist,
334 @findex message-goto-to
335 Describe the message mode.
339 @findex message-goto-to
340 Go to the @code{To} header (@code{message-goto-to}).
344 @findex message-goto-bcc
345 Go to the @code{Bcc} header (@code{message-goto-bcc}).
349 @findex message-goto-fcc
350 Go to the @code{Fcc} header (@code{message-goto-fcc}).
354 @findex message-goto-cc
355 Go to the @code{Cc} header (@code{message-goto-cc}).
359 @findex message-goto-subject
360 Go to the @code{Subject} header (@code{message-goto-subject}).
364 @findex message-goto-reply-to
365 Go to the @code{Reply-To} header (@code{message-goto-reply-to}).
369 @findex message-goto-newsgroups
370 Go to the @code{Newsgroups} header (@code{message-goto-newsgroups}).
374 @findex message-goto-distribution
375 Go to the @code{Distribution} header (@code{message-goto-distribution}).
379 @findex message-goto-followup-to
380 Go to the @code{Followup-To} header (@code{message-goto-followup-to}).
384 @findex message-goto-keywords
385 Go to the @code{Keywords} header (@code{message-goto-keywords}).
389 @findex message-goto-summary
390 Go to the @code{Summary} header (@code{message-goto-summary}).
401 @findex message-goto-body
402 Move to the beginning of the body of the message
403 (@code{message-goto-body}).
407 @findex message-goto-signature
408 Move to the signature of the message (@code{message-goto-signature}).
420 @findex message-yank-original
421 Yank the message in the buffer @code{gnus-article-copy} into the message
422 buffer. Normally @code{gnus-article-copy} is what you are replying to
423 (@code{message-yank-original}).
427 @findex message-yank-buffer
428 Prompt for a buffer name and yank the contents of that buffer into the
429 message buffer (@code{message-yank-buffer}).
433 @findex message-fill-yanked-message
434 Fill the yanked message (@code{message-fill-yanked-message}). Warning:
435 Can severely mess up the yanked text if its quoting conventions are
436 strange. You'll quickly get a feel for when it's safe, though. Anyway,
437 just remember that @kbd{C-x u} (@code{undo}) is available and you'll be
442 @findex message-insert-signature
443 Insert a signature at the end of the buffer
444 (@code{message-insert-signature}).
448 @findex message-insert-headers
449 Insert the message headers (@code{message-insert-headers}).
454 @item message-ignored-cited-headers
455 @vindex message-ignored-cited-headers
456 All headers that match this regexp will be removed from yanked
457 messages. The default is @samp{.}, which means that all headers will be
460 @item message-citation-line-function
461 @vindex message-citation-line-function
462 Function called to insert the citation line. The default is
463 @code{message-insert-citation-line}, which will lead to citation lines
467 Hallvard B Furuseth <h.b.furuseth@@usit.uio.no> writes:
470 Point will be at the beginning of the body of the message when this
473 @item message-yank-prefix
474 @vindex message-yank-prefix
477 When you are replying to or following up an article, you normally want
478 to quote the person you are answering. Inserting quoted text is done by
479 @dfn{yanking}, and each quoted line you yank will have
480 @code{message-yank-prefix} prepended to it. The default is @samp{> }.
482 @item message-yank-add-new-references
483 @vindex message-yank-add-new-references
485 Non-@code{nil} means new IDs will be added to References field when an
486 article is yanked by the command @code{message-yank-original}
487 interactively. If it is a symbol @code{message-id-only}, only an ID
488 from Message-ID field is used, otherwise IDs extracted from References,
489 In-Reply-To and Message-ID fields are used.
491 @item message-list-references-add-position
492 @vindex message-list-references-add-position
494 Integer value means position for adding to References field when an
495 article is yanked by the command @code{message-yank-original}
498 @item message-indentation-spaces
499 @vindex message-indentation-spaces
500 Number of spaces to indent yanked messages.
502 @item message-cite-function
503 @vindex message-cite-function
504 @findex message-cite-original
505 @findex sc-cite-original
506 @findex message-cite-original-without-signature
508 Function for citing an original message. The default is
509 @code{message-cite-original}, which simply inserts the original message
510 and prepends @samp{> } to each line.
511 @code{message-cite-original-without-signature} does the same, but elides
512 the signature. You can also set it to @code{sc-cite-original} to use
515 @item message-indent-citation-function
516 @vindex message-indent-citation-function
517 Function for modifying a citation just inserted in the mail buffer.
518 This can also be a list of functions. Each function can find the
519 citation between @code{(point)} and @code{(mark t)}. And each function
520 should leave point and mark around the citation text as modified.
522 @item message-signature
523 @vindex message-signature
524 String to be inserted at the end of the message buffer. If @code{t}
525 (which is the default), the @code{message-signature-file} file will be
526 inserted instead. If a function, the result from the function will be
527 used instead. If a form, the result from the form will be used instead.
528 If this variable is @code{nil}, no signature will be inserted at all.
530 @item message-signature-file
531 @vindex message-signature-file
532 File containing the signature to be inserted at the end of the buffer.
533 The default is @samp{~/.signature}.
537 Note that RFC1036bis says that a signature should be preceded by the three
538 characters @samp{-- } on a line by themselves. This is to make it
539 easier for the recipient to automatically recognize and process the
540 signature. So don't remove those characters, even though you might feel
541 that they ruin your beautiful design, like, totally.
543 Also note that no signature should be more than four lines long.
544 Including ASCII graphics is an efficient way to get everybody to believe
545 that you are silly and have nothing important to say.
555 Message is a @sc{mime}-compliant posting agent. The user generally
556 doesn't have to do anything to make the @sc{mime} happen---Message will
557 automatically add the @code{Content-Type} and
558 @code{Content-Transfer-Encoding} headers.
560 The most typical thing users want to use the multipart things in
561 @sc{mime} for is to add ``attachments'' to mail they send out. This can
562 be done with the @code{C-c C-a} command, which will prompt for a file
563 name and a @sc{mime} type.
565 You can also create arbitrarily complex multiparts using the MML
566 language (@pxref{Composing, , Composing, emacs-mime, The Emacs MIME
570 @node Various Commands
571 @section Various Commands
577 @findex message-caesar-buffer-body
578 Caesar rotate (aka. rot13) the current message
579 (@code{message-caesar-buffer-body}). If narrowing is in effect, just
580 rotate the visible portion of the buffer. A numerical prefix says how
581 many places to rotate the text. The default is 13.
585 @findex message-elide-region
586 Elide the text between point and mark (@code{message-elide-region}).
587 The text is killed and an ellipsis (@samp{[...]}) will be inserted in
592 @findex message-kill-to-signature
593 Kill all the text up to the signature, or if that's missing, up to the
594 end of the message (@code{message-kill-to-signature}).
598 @findex message-delete-not-region
599 Delete all text in the body of the message that is outside the region
600 (@code{message-delete-not-region}).
604 @kindex message-newline-and-reformat
605 Insert four newlines, and then reformat if inside quoted text.
610 > This is some quoted text. And here's more quoted text.
613 If point is before @samp{And} and you press @kbd{M-RET}, you'll get:
616 > This is some quoted text.
620 > And here's more quoted text.
623 @samp{*} says where point will be placed.
627 @findex message-insert-to
628 Insert a @code{To} header that contains the @code{Reply-To} or
629 @code{From} header of the message you're following up
630 (@code{message-insert-to}).
634 @findex message-insert-newsgroups
635 Insert a @code{Newsgroups} header that reflects the @code{Followup-To}
636 or @code{Newsgroups} header of the article you're replying to
637 (@code{message-insert-newsgroups}).
641 @findex message-rename-buffer
642 Rename the buffer (@code{message-rename-buffer}). If given a prefix,
643 prompt for a new buffer name.
654 @findex message-send-and-exit
655 Send the message and bury the current buffer
656 (@code{message-send-and-exit}).
661 Send the message (@code{message-send}).
665 @findex message-dont-send
666 Bury the message buffer and exit (@code{message-dont-send}).
670 @findex message-kill-buffer
671 Kill the message buffer and exit (@code{message-kill-buffer}).
678 @section Mail Aliases
682 @vindex message-mail-alias-type
683 The @code{message-mail-alias-type} variable controls what type of mail
684 alias expansion to use. Currently only one form is supported---Message
685 uses @code{mailabbrev} to handle mail aliases. If this variable is
686 @code{nil}, no mail alias expansion will be performed.
688 @code{mailabbrev} works by parsing the @file{/etc/mailrc} and
689 @file{~/.mailrc} files. These files look like:
692 alias lmi "Lars Magne Ingebrigtsen <larsi@@ifi.uio.no>"
693 alias ding "ding@@ifi.uio.no (ding mailing list)"
696 After adding lines like this to your @file{~/.mailrc} file, you should
697 be able to just write @samp{lmi} in the @code{To} or @code{Cc} (and so
698 on) headers and press @kbd{SPC} to expand the alias.
700 No expansion will be performed upon sending of the message---all
701 expansions have to be done explicitly.
709 * Message Headers:: General message header stuff.
710 * Mail Headers:: Customizing mail headers.
711 * Mail Variables:: Other mail variables.
712 * News Headers:: Customizing news headers.
713 * News Variables:: Other news variables.
714 * Various Message Variables:: Other message variables.
715 * Sending Variables:: Variables for sending.
716 * Message Buffers:: How Message names its buffers.
717 * Message Actions:: Actions to be performed when exiting.
721 @node Message Headers
722 @section Message Headers
724 Message is quite aggressive on the message generation front. It has to
725 be -- it's a combined news and mail agent. To be able to send combined
726 messages, it has to generate all headers itself (instead of letting the
727 mail/news system do it) to ensure that mail and news copies of messages
728 look sufficiently similar.
732 @item message-generate-headers-first
733 @vindex message-generate-headers-first
734 If non-@code{nil}, generate all headers before starting to compose the
737 @item message-from-style
738 @vindex message-from-style
739 Specifies how @code{From} headers should look. There are four valid
744 Just the address -- @samp{king@@grassland.com}.
747 @samp{king@@grassland.com (Elvis Parsley)}.
750 @samp{Elvis Parsley <king@@grassland.com>}.
753 Look like @code{angles} if that doesn't require quoting, and
754 @code{parens} if it does. If even @code{parens} requires quoting, use
755 @code{angles} anyway.
759 @item message-deletable-headers
760 @vindex message-deletable-headers
761 Headers in this list that were previously generated by Message will be
762 deleted before posting. Let's say you post an article. Then you decide
763 to post it again to some other group, you naughty boy, so you jump back
764 to the @code{*post-buf*} buffer, edit the @code{Newsgroups} line, and
765 ship it off again. By default, this variable makes sure that the old
766 generated @code{Message-ID} is deleted, and a new one generated. If
767 this isn't done, the entire empire would probably crumble, anarchy would
768 prevail, and cats would start walking on two legs and rule the world.
771 @item message-default-headers
772 @vindex message-default-headers
773 This string is inserted at the end of the headers in all message
776 @item message-subject-re-regexp
777 @vindex message-subject-re-regexp
778 Responses to messages have subjects that start with @samp{Re: }. This
779 is @emph{not} an abbreviation of the English word ``response'', but in
780 Latin, and means ``in response to''. Some illiterate nincompoops have
781 failed to grasp this fact, and have ``internationalized'' their software
782 to use abonimations like @samp{Aw: } (``antwort'') or @samp{Sv: }
783 (``svar'') instead, which is meaningless and evil. However, you may
784 have to deal with users that use these evil tools, in which case you may
785 set this variable to a regexp that matches these prefixes. Myself, I
786 just throw away non-compliant mail.
792 @section Mail Headers
795 @item message-required-mail-headers
796 @vindex message-required-mail-headers
797 @xref{News Headers}, for the syntax of this variable. It is
798 @code{(From Date Subject (optional . In-Reply-To) Message-ID Lines
799 (optional . X-Mailer))} by default.
801 @item message-ignored-mail-headers
802 @vindex message-ignored-mail-headers
803 Regexp of headers to be removed before mailing. The default is
804 @samp{^[GF]cc:\\|^Resent-Fcc:}.
806 @item message-default-mail-headers
807 @vindex message-default-mail-headers
808 This string is inserted at the end of the headers in all message
809 buffers that are initialized as mail.
815 @section Mail Variables
818 @item message-send-mail-function
819 @vindex message-send-mail-function
820 Function used to send the current buffer as mail. The default is
821 @code{message-send-mail-with-sendmail}. If you prefer using MH
822 instead, set this variable to @code{message-send-mail-with-mh}.
824 @item message-mh-deletable-headers
825 @vindex message-mh-deletable-headers
826 Most versions of MH doesn't like being fed messages that contain the
827 headers in this variable. If this variable is non-@code{nil} (which is
828 the default), these headers will be removed before mailing when sending
829 messages via MH. Set it to @code{nil} if your MH can handle these
836 @section News Headers
838 @vindex message-required-news-headers
839 @code{message-required-news-headers} a list of header symbols. These
840 headers will either be automatically generated, or, if that's
841 impossible, they will be prompted for. The following symbols are valid:
847 @findex user-full-name
848 @findex user-mail-address
849 This required header will be filled out with the result of the
850 @code{message-make-from} function, which depends on the
851 @code{message-from-style}, @code{user-full-name},
852 @code{user-mail-address} variables.
856 This required header will be prompted for if not present already.
860 This required header says which newsgroups the article is to be posted
861 to. If it isn't present already, it will be prompted for.
865 This optional header will be filled out depending on the
866 @code{message-user-organization} variable.
867 @code{message-user-organization-file} will be used if this variable is
868 @code{t}. This variable can also be a string (in which case this string
869 will be used), or it can be a function (which will be called with no
870 parameters and should return a string to be used).
874 This optional header will be computed by Message.
878 @vindex mail-host-address
881 This required header will be generated by Message. A unique ID will be
882 created based on the date, time, user name and system name. Message
883 will use @code{system-name} to determine the name of the system. If
884 this isn't a fully qualified domain name (FQDN), Message will use
885 @code{mail-host-address} as the FQDN of the machine.
889 This optional header will be filled out according to the
890 @code{message-newsreader} local variable.
893 This optional header will be filled out according to the
894 @code{message-mailer} local variable, unless there already is an
895 @code{X-Newsreader} header present.
898 This optional header is filled out using the @code{Date} and @code{From}
899 header of the article being replied to.
903 This extremely optional header will be inserted according to the
904 @code{message-expires} variable. It is highly deprecated and shouldn't
905 be used unless you know what you're doing.
909 This optional header is filled out according to the
910 @code{message-distribution-function} variable. It is a deprecated and
911 much misunderstood header.
915 This extremely optional header should probably never be used.
916 However, some @emph{very} old servers require that this header is
917 present. @code{message-user-path} further controls how this
918 @code{Path} header is to look. If it is @code{nil}, use the server name
919 as the leaf node. If it is a string, use the string. If it is neither
920 a string nor @code{nil}, use the user name only. However, it is highly
921 unlikely that you should need to fiddle with this variable at all.
926 In addition, you can enter conses into this list. The car of this cons
927 should be a symbol. This symbol's name is the name of the header, and
928 the cdr can either be a string to be entered verbatim as the value of
929 this header, or it can be a function to be called. This function should
930 return a string to be inserted. For instance, if you want to insert
931 @code{Mime-Version: 1.0}, you should enter @code{(Mime-Version . "1.0")}
932 into the list. If you want to insert a funny quote, you could enter
933 something like @code{(X-Yow . yow)} into the list. The function
934 @code{yow} will then be called without any arguments.
936 If the list contains a cons where the car of the cons is
937 @code{optional}, the cdr of this cons will only be inserted if it is
940 Other variables for customizing outgoing news articles:
944 @item message-syntax-checks
945 @vindex message-syntax-checks
946 Controls what syntax checks should not be performed on outgoing posts.
947 To disable checking of long signatures, for instance, add
950 (signature . disabled)
959 Check the subject for commands.
962 Insert a new @code{Sender} header if the @code{From} header looks odd.
963 @item multiple-headers
964 Check for the existence of multiple equal headers.
967 Check for the existence of version and sendsys commands.
969 Check whether the @code{Message-ID} looks ok.
971 Check whether the @code{From} header seems nice.
974 Check for too long lines.
976 Check for invalid characters.
978 Check for excessive size.
980 Check whether there is any new text in the messages.
982 Check the length of the signature.
985 Check whether the article has an @code{Approved} header, which is
986 something only moderators should include.
988 Check whether the article is empty.
990 Check whether there is any invisible text in the buffer.
992 Check whether any of the headers are empty.
993 @item existing-newsgroups
994 Check whether the newsgroups mentioned in the @code{Newsgroups} and
995 @code{Followup-To} headers exist.
996 @item valid-newsgroups
997 Check whether the @code{Newsgroups} and @code{Followup-to} headers
998 are valid syntactically.
999 @item repeated-newsgroups
1000 Check whether the @code{Newsgroups} and @code{Followup-to} headers
1001 contains repeated group names.
1002 @item shorten-followup-to
1003 Check whether to add a @code{Followup-to} header to shorten the number
1004 of groups to post to.
1007 All these conditions are checked by default.
1009 @item message-ignored-news-headers
1010 @vindex message-ignored-news-headers
1011 Regexp of headers to be removed before posting. The default is@*
1012 @samp{^NNTP-Posting-Host:\\|^Xref:\\|^[BGF]cc:\\|^Resent-Fcc:}.
1014 @item message-default-news-headers
1015 @vindex message-default-news-headers
1016 This string is inserted at the end of the headers in all message
1017 buffers that are initialized as news.
1022 @node News Variables
1023 @section News Variables
1026 @item message-send-news-function
1027 @vindex message-send-news-function
1028 Function used to send the current buffer as news. The default is
1029 @code{message-send-news}.
1031 @item message-post-method
1032 @vindex message-post-method
1033 Gnusish @dfn{select method} (see the Gnus manual for details) used for
1034 posting a prepared news message.
1039 @node Various Message Variables
1040 @section Various Message Variables
1043 @item message-signature-separator
1044 @vindex message-signature-separator
1045 Regexp matching the signature separator. It is @samp{^-- *$} by
1048 @item mail-header-separator
1049 @vindex mail-header-separator
1050 String used to separate the headers from the body. It is @samp{--text
1051 follows this line--} by default.
1053 @item message-directory
1054 @vindex message-directory
1055 Directory used by many mailey things. The default is @file{~/Mail/}.
1057 @item message-signature-setup-hook
1058 @vindex message-signature-setup-hook
1059 Hook run when initializing the message buffer. It is run after the
1060 headers have been inserted but before the signature has been inserted.
1062 @item message-setup-hook
1063 @vindex message-setup-hook
1064 Hook run as the last thing when the message buffer has been initialized,
1065 but before yanked text is inserted.
1067 @item message-header-setup-hook
1068 @vindex message-header-setup-hook
1069 Hook called narrowed to the headers after initializing the headers.
1071 For instance, if you're running Gnus and wish to insert a
1072 @samp{Mail-Copies-To} header in all your news articles and all messages
1073 you send to mailing lists, you could do something like the following:
1076 (defun my-message-header-setup-hook ()
1077 (let ((group (or gnus-newsgroup-name "")))
1078 (when (or (message-fetch-field "newsgroups")
1079 (gnus-group-find-parameter group 'to-address)
1080 (gnus-group-find-parameter group 'to-list))
1081 (insert "Mail-Copies-To: never\n"))))
1083 (add-hook 'message-header-setup-hook
1084 'my-message-header-setup-hook)
1087 @item message-send-hook
1088 @vindex message-send-hook
1089 Hook run before sending messages.
1091 If you want to add certain headers before sending, you can use the
1092 @code{message-add-header} function in this hook. For instance:
1093 @findex message-add-header
1096 (add-hook 'message-send-hook 'my-message-add-content)
1097 (defun my-message-add-content ()
1099 "X-In-No-Sense: Nonsense"
1103 This function won't add the header if the header is already present.
1105 @item message-send-mail-hook
1106 @vindex message-send-mail-hook
1107 Hook run before sending mail messages.
1109 @item message-send-news-hook
1110 @vindex message-send-news-hook
1111 Hook run before sending news messages.
1113 @item message-sent-hook
1114 @vindex message-sent-hook
1115 Hook run after sending messages.
1117 @item message-mode-syntax-table
1118 @vindex message-mode-syntax-table
1119 Syntax table used in message mode buffers.
1121 @item message-send-method-alist
1122 @vindex message-send-method-alist
1124 Alist of ways to send outgoing messages. Each element has the form
1127 (TYPE PREDICATE FUNCTION)
1132 A symbol that names the method.
1135 A function called without any parameters to determine whether the
1136 message is a message of type @var{type}.
1139 A function to be called if @var{predicate} returns non-@code{nil}.
1140 @var{function} is called with one parameter -- the prefix.
1144 ((news message-news-p message-send-via-news)
1145 (mail message-mail-p message-send-via-mail))
1154 @node Sending Variables
1155 @section Sending Variables
1159 @item message-fcc-handler-function
1160 @vindex message-fcc-handler-function
1161 A function called to save outgoing articles. This function will be
1162 called with the name of the file to store the article in. The default
1163 function is @code{message-output} which saves in Unix mailbox format.
1165 @item message-courtesy-message
1166 @vindex message-courtesy-message
1167 When sending combined messages, this string is inserted at the start of
1168 the mailed copy. If the string contains the format spec @samp{%s}, the
1169 newsgroups the article has been posted to will be inserted there. If
1170 this variable is @code{nil}, no such courtesy message will be added.
1171 The default value is @samp{"The following message is a courtesy copy of
1172 an article\nthat has been posted to %s as well.\n\n"}.
1177 @node Message Buffers
1178 @section Message Buffers
1180 Message will generate new buffers with unique buffer names when you
1181 request a message buffer. When you send the message, the buffer isn't
1182 normally killed off. Its name is changed and a certain number of old
1183 message buffers are kept alive.
1186 @item message-generate-new-buffers
1187 @vindex message-generate-new-buffers
1188 If non-@code{nil}, generate new buffers. The default is @code{t}. If
1189 this is a function, call that function with three parameters: The type,
1190 the to address and the group name. (Any of these may be @code{nil}.)
1191 The function should return the new buffer name.
1193 @item message-use-multi-frames
1194 @vindex message-use-multi-frames
1195 If non-@code{nil}, generate new frames. The default is @code{nil}.
1197 @item message-delete-frame-on-exit
1198 @vindex message-delete-frame-on-exit
1199 The @code{message-delete-frame-on-exit} variable says whether to delete
1200 the frame after sending the message or killing the message buffer. If it
1201 is @code{nil} (which is the default), don't delete the frame. If it is
1202 @code{ask}, ask wheter to delete the frame. If it is @code{t}, always
1205 @item message-max-buffers
1206 @vindex message-max-buffers
1207 This variable says how many old message buffers to keep. If there are
1208 more message buffers than this, the oldest buffer will be killed. The
1209 default is 10. If this variable is @code{nil}, no old message buffers
1210 will ever be killed.
1212 @item message-send-rename-function
1213 @vindex message-send-rename-function
1214 After sending a message, the buffer is renamed from, for instance,
1215 @samp{*reply to Lars*} to @samp{*sent reply to Lars*}. If you don't
1216 like this, set this variable to a function that renames the buffer in a
1217 manner you like. If you don't want to rename the buffer at all, you can
1221 (setq message-send-rename-function 'ignore)
1224 @item message-kill-buffer-on-exit
1225 @findex message-kill-buffer-on-exit
1226 If non-@code{nil}, kill the buffer immediately on exit.
1231 @node Message Actions
1232 @section Message Actions
1234 When Message is being used from a news/mail reader, the reader is likely
1235 to want to perform some task after the message has been sent. Perhaps
1236 return to the previous window configuration or mark an article as
1239 @vindex message-kill-actions
1240 @vindex message-postpone-actions
1241 @vindex message-exit-actions
1242 @vindex message-send-actions
1243 The user may exit from the message buffer in various ways. The most
1244 common is @kbd{C-c C-c}, which sends the message and exits. Other
1245 possibilities are @kbd{C-c C-s} which just sends the message, @kbd{C-c
1246 C-d} which postpones the message editing and buries the message buffer,
1247 and @kbd{C-c C-k} which kills the message buffer. Each of these actions
1248 have lists associated with them that contains actions to be executed:
1249 @code{message-send-actions}, @code{message-exit-actions},
1250 @code{message-postpone-actions}, and @code{message-kill-actions}.
1252 Message provides a function to interface with these lists:
1253 @code{message-add-action}. The first parameter is the action to be
1254 added, and the rest of the arguments are which lists to add this action
1255 to. Here's an example from Gnus:
1259 `(set-window-configuration ,(current-window-configuration))
1260 'exit 'postpone 'kill)
1263 This restores the Gnus window configuration when the message buffer is
1264 killed, postponed or exited.
1266 An @dfn{action} can be either: a normal function, or a list where the
1267 @code{car} is a function and the @code{cdr} is the list of arguments, or
1268 a form to be @code{eval}ed.
1272 @chapter Compatibility
1273 @cindex compatibility
1275 Message uses virtually only its own variables---older @code{mail-}
1276 variables aren't consulted. To force Message to take those variables
1277 into account, you can put the following in your @code{.emacs} file:
1280 (require 'messcompat)
1283 This will initialize many Message variables from the values in the
1284 corresponding mail variables.
1291 * Responses:: Standard rules for determining where responses go.
1298 To determine where a message is to go, the following algorithm is used
1303 A @dfn{reply} is when you want to respond @emph{just} to the person who
1304 sent the message via mail. There will only be one recipient. To
1305 determine who the recipient will be, the following headers are
1316 A @dfn{wide reply} is a mail response that includes @emph{all} entities
1317 mentioned in the message you are responded to. All mailboxes from the
1318 following headers will be concatenated to form the outgoing
1319 @code{To}/@code{Cc} headers:
1323 (unless there's a @code{Reply-To}, in which case that is used instead).
1330 If a @code{Mail-Copies-To} header is present, it will also be included
1331 in the list of mailboxes. If this header is @samp{never}, that means
1332 that the @code{From} (or @code{Reply-To}) mailbox will be suppressed.
1336 A @dfn{followup} is a response sent via news. The following headers
1337 (listed in order of precedence) determine where the response is to be
1348 If a @code{Mail-Copies-To} header is present, it will be used as the
1349 basis of the new @code{Cc} header, except if this header is