1 \input texinfo @c -*-texinfo-*-
4 @settitle Message (Oort) Manual
10 * Message: (message). Mail and news composition mode that goes with Gnus.
15 @setchapternewpage odd
19 This file documents Message, the Emacs message composition mode.
21 Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002 Free Software Foundation, Inc.
23 Permission is granted to copy, distribute and/or modify this document
24 under the terms of the GNU Free Documentation License, Version 1.1 or
25 any later version published by the Free Software Foundation; with no
26 Invariant Sections, with the Front-Cover texts being ``A GNU
27 Manual'', and with the Back-Cover Texts as in (a) below. A copy of the
28 license is included in the section entitled ``GNU Free Documentation
29 License'' in the Emacs manual.
31 (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify
32 this GNU Manual, like GNU software. Copies published by the Free
33 Software Foundation raise funds for GNU development.''
35 This document is part of a collection distributed under the GNU Free
36 Documentation License. If you want to distribute this document
37 separately from the collection, you can do so by adding a copy of the
38 license to the document, as described in section 6 of the license.
44 @title Message (Oort) Manual
46 @author by Lars Magne Ingebrigtsen
49 @vskip 0pt plus 1filll
50 Copyright @copyright{} 1996, 1997, 1998, 1999, 2000
51 Free Software Foundation, Inc.
53 Permission is granted to copy, distribute and/or modify this document
54 under the terms of the GNU Free Documentation License, Version 1.1 or
55 any later version published by the Free Software Foundation; with the
56 Invariant Sections being none, with the Front-Cover texts being ``A GNU
57 Manual'', and with the Back-Cover Texts as in (a) below. A copy of the
58 license is included in the section entitled ``GNU Free Documentation
59 License'' in the Emacs manual.
61 (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify
62 this GNU Manual, like GNU software. Copies published by the Free
63 Software Foundation raise funds for GNU development.''
65 This document is part of a collection distributed under the GNU Free
66 Documentation License. If you want to distribute this document
67 separately from the collection, you can do so by adding a copy of the
68 license to the document, as described in section 6 of the license.
77 All message composition from Gnus (both mail and news) takes place in
81 * Interface:: Setting up message buffers.
82 * Commands:: Commands you can execute in message mode buffers.
83 * Variables:: Customizing the message buffers.
84 * Compatibility:: Making Message backwards compatible.
85 * Appendices:: More technical things.
86 * Index:: Variable, function and concept index.
87 * Key Index:: List of Message mode keys.
90 This manual corresponds to Oort Message. Message is distributed with
91 the Gnus distribution bearing the same version number as this manual.
97 When a program (or a person) wants to respond to a message -- reply,
98 follow up, forward, cancel -- the program (or person) should just put
99 point in the buffer where the message is and call the required command.
100 @code{Message} will then pop up a new @code{message} mode buffer with
101 appropriate headers filled out, and the user can edit the message before
105 * New Mail Message:: Editing a brand new mail message.
106 * New News Message:: Editing a brand new news message.
107 * Reply:: Replying via mail.
108 * Wide Reply:: Responding to all people via mail.
109 * Followup:: Following up via news.
110 * Canceling News:: Canceling a news article.
111 * Superseding:: Superseding a message.
112 * Forwarding:: Forwarding a message via news or mail.
113 * Resending:: Resending a mail message.
114 * Bouncing:: Bouncing a mail message.
115 * Mailing Lists:: Send mail to mailing lists.
119 @node New Mail Message
120 @section New Mail Message
123 The @code{message-mail} command pops up a new message buffer.
125 Two optional parameters are accepted: The first will be used as the
126 @code{To} header and the second as the @code{Subject} header. If these
127 are @code{nil}, those two headers will be empty.
130 @node New News Message
131 @section New News Message
134 The @code{message-news} command pops up a new message buffer.
136 This function accepts two optional parameters. The first will be used
137 as the @code{Newsgroups} header and the second as the @code{Subject}
138 header. If these are @code{nil}, those two headers will be empty.
144 @findex message-reply
145 The @code{message-reply} function pops up a message buffer that's a
146 reply to the message in the current buffer.
148 @vindex message-reply-to-function
149 Message uses the normal methods to determine where replies are to go
150 (@pxref{Responses}), but you can change the behavior to suit your needs
151 by fiddling with the @code{message-reply-to-function} variable.
153 If you want the replies to go to the @code{Sender} instead of the
154 @code{From}, you could do something like this:
157 (setq message-reply-to-function
159 (cond ((equal (mail-fetch-field "from") "somebody")
160 (list (cons 'To (mail-fetch-field "sender"))))
165 This function will be called narrowed to the head of the article that is
168 As you can see, this function should return a string if it has an
169 opinion as to what the To header should be. If it does not, it should
170 just return @code{nil}, and the normal methods for determining the To
173 This function can also return a list. In that case, each list element
174 should be a cons, where the car should be the name of an header
175 (eg. @code{Cc}) and the cdr should be the header value
176 (eg. @samp{larsi@@ifi.uio.no}). All these headers will be inserted into
177 the head of the outgoing mail.
183 @findex message-wide-reply
184 The @code{message-wide-reply} pops up a message buffer that's a wide
185 reply to the message in the current buffer. A @dfn{wide reply} is a
186 reply that goes out to all people listed in the @code{To}, @code{From}
187 (or @code{Reply-to}) and @code{Cc} headers.
189 @vindex message-wide-reply-to-function
190 Message uses the normal methods to determine where wide replies are to go,
191 but you can change the behavior to suit your needs by fiddling with the
192 @code{message-wide-reply-to-function}. It is used in the same way as
193 @code{message-reply-to-function} (@pxref{Reply}).
195 @findex message-dont-reply-to-names
196 Addresses that match the @code{message-dont-reply-to-names} regular
197 expression will be removed from the @code{Cc} header.
203 @findex message-followup
204 The @code{message-followup} command pops up a message buffer that's a
205 followup to the message in the current buffer.
207 @vindex message-followup-to-function
208 Message uses the normal methods to determine where followups are to go,
209 but you can change the behavior to suit your needs by fiddling with the
210 @code{message-followup-to-function}. It is used in the same way as
211 @code{message-reply-to-function} (@pxref{Reply}).
213 @vindex message-use-followup-to
214 The @code{message-use-followup-to} variable says what to do about
215 @code{Followup-To} headers. If it is @code{use}, always use the value.
216 If it is @code{ask} (which is the default), ask whether to use the
217 value. If it is @code{t}, use the value unless it is @samp{poster}. If
218 it is @code{nil}, don't use the value.
222 @section Canceling News
224 @findex message-cancel-news
225 The @code{message-cancel-news} command cancels the article in the
232 @findex message-supersede
233 The @code{message-supersede} command pops up a message buffer that will
234 supersede the message in the current buffer.
236 @vindex message-ignored-supersedes-headers
237 Headers matching the @code{message-ignored-supersedes-headers} are
238 removed before popping up the new message buffer. The default is@*
239 @samp{^Path:\\|^Date\\|^NNTP-Posting-Host:\\|^Xref:\\|^Lines:\\|@*
240 ^Received:\\|^X-From-Line:\\|Return-Path:\\|^Supersedes:}.
247 @findex message-forward
248 The @code{message-forward} command pops up a message buffer to forward
249 the message in the current buffer. If given a prefix, forward using
253 @item message-forward-ignored-headers
254 @vindex message-forward-ignored-headers
255 All headers that match this regexp will be deleted when forwarding a message.
257 @item message-make-forward-subject-function
258 @vindex message-make-forward-subject-function
259 A list of functions that are called to generate a subject header for
260 forwarded messages. The subject generated by the previous function is
261 passed into each successive function.
263 The provided functions are:
266 @item message-forward-subject-author-subject
267 @findex message-forward-subject-author-subject
268 Source of article (author or newsgroup), in brackets followed by the
271 @item message-forward-subject-fwd
272 Subject of article with @samp{Fwd:} prepended to it.
275 @item message-wash-forwarded-subjects
276 @vindex message-wash-forwarded-subjects
277 If this variable is @code{t}, the subjects of forwarded messages have
278 the evidence of previous forwards (such as @samp{Fwd:}, @samp{Re:},
279 @samp{(fwd)}) removed before the new subject is
280 constructed. The default value is @code{nil}.
282 @item message-forward-as-mime
283 @vindex message-forward-as-mime
284 If this variable is @code{t} (the default), forwarded messages are
285 included as inline MIME RFC822 parts. If it's @code{nil}, forwarded
286 messages will just be copied inline to the new message, like previous,
287 non MIME-savvy versions of gnus would do.
294 @findex message-resend
295 The @code{message-resend} command will prompt the user for an address
296 and resend the message in the current buffer to that address.
298 @vindex message-ignored-resent-headers
299 Headers that match the @code{message-ignored-resent-headers} regexp will
300 be removed before sending the message. The default is
301 @samp{^Return-receipt}.
307 @findex message-bounce
308 The @code{message-bounce} command will, if the current buffer contains a
309 bounced mail message, pop up a message buffer stripped of the bounce
310 information. A @dfn{bounced message} is typically a mail you've sent
311 out that has been returned by some @code{mailer-daemon} as
314 @vindex message-ignored-bounced-headers
315 Headers that match the @code{message-ignored-bounced-headers} regexp
316 will be removed before popping up the buffer. The default is
317 @samp{^\\(Received\\|Return-Path\\):}.
321 @section Mailing Lists
323 Sometimes while posting to mailing lists, the poster needs to direct
324 followups to the post to specific places. The Mail-Followup-To (MFT)
325 was created to enable just this. Two example scenarios where this is
330 A mailing list poster can use MFT to express that responses should be
331 sent to just the list, and not the poster as well. This will happen
332 if the poster is already subscribed to the list.
335 If a message is posted to several mailing lists, MFT may also be used
336 to direct the following discussion to one list only, because
337 discussions that are spread over several lists tend to be fragmented
338 and very difficult to follow.
342 Gnus honors the MFT header in other's messages (i.e. while following
343 up to someone else's post) and also provides support for generating
344 sensible MFT headers for outgoing messages as well.
347 @c * Honoring an MFT post:: What to do when one already exists
348 @c * Composing with a MFT header:: Creating one from scratch.
351 @c @node Composing with a MFT header
352 @subsection Composing a correct MFT header automagically
354 The first step in getting Gnus to automagically generate a MFT header
355 in posts you make is to give Gnus a list of the mailing lists
356 addresses you are subscribed to. You can do this in more than one
357 way. The following variables would come in handy.
361 @item message-subscribed-addresses
362 This should be a list of addresses the user is subscribed to. Its
363 default value is @code{nil}. Example:
365 (setq message-subscribed-addresses
366 '("ding@@gnus.org" "bing@@noose.org"))
369 @item message-subscribed-regexps
370 This should be a list of regexps denoting the addresses of mailing
371 lists subscribed to. Default value is @code{nil}. Example: If you
372 want to achieve the same result as above:
374 (setq message-subscribed-regexps
375 '("[bd]ing@@\\(gnus\\|noose\\)\\.org"))
378 @item message-subscribed-address-functions
379 This can be a list of functions to be called (one at a time!!) to
380 determine the value of MFT headers. It is advisable that these
381 functions not take any arguments. Default value is @code{nil}.
383 @item message-subscribed-address-file
384 You might be one organised human freak and have a list of addresses of
385 all subscribed mailing lists in a separate file! Then you can just
386 set this variable to the name of the file and life would be good.
390 You can use one or more of the above variables. All their values are
391 ``added'' in some way that works :-)
393 Now you are all set. Just start composing a message as you normally
394 do. And just send it; as always. Just before the message is sent
395 out, Gnus' MFT generation thingy kicks in and checks if the message
396 already has a MFT header. If there is one, the header is left alone.
397 If not then the list of recipient addresses (in the To: and Cc:
398 headers) is checked to see if one of them is a list address you are
399 subscribed to. If none of them is a list address, then no MFT is
400 generated; otherwise, a MFT is added to the other headers and set to
401 the value of all addresses in To: and Cc:
403 Hm. ``So'', you ask, ``what if I send an email to a list I am not
404 subscribed to?'' Well, the kind folks at Gnus Towers are working on a
405 database of all known mailing list addresses that can be used for this
406 purpose. Till then, you could, like, insert a MFT header manually,
407 with the help of @kbd{C-c C-f m} !!
409 @c @node Honoring an MFT post
410 @subsection Honoring an MFT post
412 When you followup to a post on a mailing list, and the post has a MFT
413 header, Gnus' action will depend on the value of the variable
414 @code{message-use-mail-followup-to}. This variable can be one of:
418 Always honor MFTs. The To: and Cc: headers in your followup will be
419 derived from the MFT header of the original post.
422 Always dishonor MFTs (just ignore the darned thing)
425 Gnus will prompt you for an action. This is the default.
429 It is considered good nettiquette to honor MFT, as it is assumed the
430 fellow who posted a message knows where the followups need to go
437 * Buffer Entry:: Commands after entering a Message buffer.
438 * Header Commands:: Commands for moving to headers.
439 * Movement:: Moving around in message buffers.
440 * Insertion:: Inserting things into message buffers.
441 * MIME:: @sc{mime} considerations.
442 * Security:: Signing and encrypting messages.
443 * Various Commands:: Various things.
444 * Sending:: Actually sending the message.
445 * Mail Aliases:: How to use mail aliases.
446 * Spelling:: Having Emacs check your spelling.
451 @section Buffer Entry
455 You most often end up in a Message buffer when responding to some other
456 message of some sort. Message does lots of handling of quoted text, and
457 may remove signatures, reformat the text, or the like---depending on
458 which used settings you're using. Message usually gets things right,
459 but sometimes it stumbles. To help the user unwind these stumblings,
460 Message sets the undo boundary before each major automatic action it
461 takes. If you press the undo key (usually located at @kbd{C-_}) a few
462 times, you will get back the un-edited message you're responding to.
465 @node Header Commands
466 @section Header Commands
468 All these commands move to the header in question (except for the
469 @samp{Importance:} related commands). If it doesn't exist, it will be
476 @findex describe-mode
477 Describe the message mode.
481 @findex message-goto-to
482 Go to the @code{To} header (@code{message-goto-to}).
486 @findex message-goto-from
487 Go to the @code{From} header (@code{message-goto-from}). (The ``o''
488 in the key binding is for Originator.)
492 @findex message-goto-bcc
493 Go to the @code{Bcc} header (@code{message-goto-bcc}).
497 @findex message-goto-fcc
498 Go to the @code{Fcc} header (@code{message-goto-fcc}).
502 @findex message-goto-cc
503 Go to the @code{Cc} header (@code{message-goto-cc}).
507 @findex message-goto-subject
508 Go to the @code{Subject} header (@code{message-goto-subject}).
512 @findex message-goto-reply-to
513 Go to the @code{Reply-To} header (@code{message-goto-reply-to}).
517 @findex message-goto-newsgroups
518 Go to the @code{Newsgroups} header (@code{message-goto-newsgroups}).
522 @findex message-goto-distribution
523 Go to the @code{Distribution} header (@code{message-goto-distribution}).
527 @findex message-goto-followup-to
528 Go to the @code{Followup-To} header (@code{message-goto-followup-to}).
532 @findex message-goto-keywords
533 Go to the @code{Keywords} header (@code{message-goto-keywords}).
537 @findex message-goto-summary
538 Go to the @code{Summary} header (@code{message-goto-summary}).
542 @findex message-insert-or-toggle-importance
543 This inserts the @samp{Importance:} header with a value of
544 @samp{high}. This header is used to signal the importance of the
545 message to the receiver. If the header is already present in the
546 buffer, it cycles between the three valid values according to RFC
547 1376: @samp{low}, @samp{normal} and @samp{high}.
549 @item M-x message-insert-importance-high
550 @kindex M-x message-insert-importance-high
551 @findex message-insert-importance-high
552 Insert a @samp{Importance:} header with a value of @samp{high},
553 deleting headers if necessary.
555 @item M-x message-insert-importance-low
556 @kindex M-x message-insert-importance-low
557 @findex message-insert-importance-low
558 Insert a @samp{Importance:} header with a value of @samp{low},
559 deleting headers if necessary.
570 @findex message-goto-body
571 Move to the beginning of the body of the message
572 (@code{message-goto-body}).
576 @findex message-goto-signature
577 Move to the signature of the message (@code{message-goto-signature}).
581 @findex message-beginning-of-line
582 If at beginning of header value, go to beginning of line, else go to
583 beginning of header value. (The header value comes after the header
596 @findex message-yank-original
597 Yank the message that's being replied to into the message buffer
598 (@code{message-yank-original}).
602 @findex message-yank-buffer
603 Prompt for a buffer name and yank the contents of that buffer into the
604 message buffer (@code{message-yank-buffer}).
608 @findex message-fill-yanked-message
609 Fill the yanked message (@code{message-fill-yanked-message}). Warning:
610 Can severely mess up the yanked text if its quoting conventions are
611 strange. You'll quickly get a feel for when it's safe, though. Anyway,
612 just remember that @kbd{C-x u} (@code{undo}) is available and you'll be
617 @findex message-insert-signature
618 Insert a signature at the end of the buffer
619 (@code{message-insert-signature}).
623 @findex message-insert-headers
624 Insert the message headers (@code{message-insert-headers}).
628 @findex message-insert-disposition-notification-to
629 Insert a request for a disposition
630 notification. (@code{message-insert-disposition-notification-to}).
631 This means that if the recipient support RFC 2298 she might send you a
632 notification that she received the message.
644 Message is a @sc{mime}-compliant posting agent. The user generally
645 doesn't have to do anything to make the @sc{mime} happen---Message will
646 automatically add the @code{Content-Type} and
647 @code{Content-Transfer-Encoding} headers.
649 The most typical thing users want to use the multipart things in
650 @sc{mime} for is to add ``attachments'' to mail they send out. This can
651 be done with the @code{C-c C-a} command, which will prompt for a file
652 name and a @sc{mime} type.
654 You can also create arbitrarily complex multiparts using the MML
655 language (@pxref{Composing, , Composing, emacs-mime, The Emacs MIME
667 Using the MML language, Message is able to create digitally signed and
668 digitally encrypted messages. Message (or rather MML) currently
669 support PGP (RFC 1991), PGP/MIME (RFC 2015/3156) and S/MIME.
670 Instructing MML to perform security operations on a MIME part is done
671 using the @code{C-c C-m s} key map for signing and the @code{C-c C-m
672 c} key map for encryption, as follows.
678 @findex mml-secure-sign-smime
680 Digitally sign current MIME part using S/MIME.
684 @findex mml-secure-sign-pgp
686 Digitally sign current MIME part using PGP.
690 @findex mml-secure-sign-pgp
692 Digitally sign current MIME part using PGP/MIME.
696 @findex mml-secure-encrypt-smime
698 Digitally encrypt current MIME part using S/MIME.
702 @findex mml-secure-encrypt-pgp
704 Digitally encrypt current MIME part using PGP.
708 @findex mml-secure-encrypt-pgpmime
710 Digitally encrypt current MIME part using PGP/MIME.
714 These commands do not immediately sign or encrypt the message, they
715 merely insert proper MML tags to instruct the MML engine to perform that
716 operation when the message is actually sent. They may perform other
717 operations too, such as locating and retrieving a S/MIME certificate of
718 the person you wish to send encrypted mail to.
720 Since signing and especially encryption often is used when sensitive
721 information is sent, you may want to have some way to ensure that your
722 mail is actually signed or encrypted. After invoking the above
723 sign/encrypt commands, it is possible to preview the raw article by
724 using @code{C-u C-m P} (@code{mml-preview}). Then you can verify that
725 your long rant about what your ex-significant other or whomever actually
726 did with that funny looking person at that strange party the other
727 night, actually will be sent encrypted.
729 @emph{Note!} Neither PGP/MIME nor S/MIME encrypt/signs RFC822 headers.
730 They only operate on the MIME object. Keep this in mind before sending
731 mail with a sensitive Subject line.
733 Actually using the security commands above is not very difficult. At
734 least not compared with making sure all involved programs talk with each
735 other properly. Thus, we now describe what external libraries or
736 programs are required to make things work, and some small general hints.
738 @subsection Using S/MIME
740 @emph{Note!} This section assume you have a basic familiarity with
741 modern cryptography, S/MIME, various PKCS standards, OpenSSL and so on.
743 The S/MIME support in Message (and MML) require OpenSSL. OpenSSL
744 perform the actual S/MIME sign/encrypt operations. OpenSSL can be found
745 at @uref{http://www.openssl.org/}. OpenSSL 0.9.6 and later should work.
746 Version 0.9.5a cannot extract mail addresses from certificates, and it
747 insert a spurious CR character into MIME separators so you may wish to
748 avoid it if you would like to avoid being regarded as someone who send
749 strange mail. (Although by sending S/MIME messages you've probably
750 already lost that contest.)
752 To be able to send encrypted mail, a personal certificate is not
753 required. Message (MML) need a certificate for the person to whom you
754 wish to communicate with though. You're asked for this when you type
755 @code{C-c C-m c s}. Currently there are two ways to retrieve this
756 certificate, from a local file or from DNS. If you chose a local file,
757 it need to contain a X.509 certificate in PEM format. If you chose DNS,
758 you're asked for the domain name where the certificate is stored, the
759 default is a good guess. To my belief, Message (MML) is the first mail
760 agent in the world to support retrieving S/MIME certificates from DNS,
761 so you're not likely to find very many certificates out there. At least
762 there should be one, stored at the domain @code{simon.josefsson.org}.
763 LDAP is a more popular method of distributing certificates, support for
764 it is planned. (Meanwhile, you can use @code{ldapsearch} from the
765 command line to retrieve a certificate into a file and use it.)
767 As for signing messages, OpenSSL can't perform signing operations
768 without some kind of configuration. Especially, you need to tell it
769 where your private key and your certificate is stored. MML uses an
770 Emacs interface to OpenSSL, aptly named @code{smime.el}, and it contain
771 a @code{custom} group used for this configuration. So, try @code{M-x
772 customize-group RET smime RET} and look around.
774 Currently there is no support for talking to a CA (or RA) to create your
775 own certificate. None is planned either. You need to do this manually
776 with OpenSSL or using some other program. I used Netscape and got a
777 free S/MIME certificate from one of the big CA's on the net. Netscape
778 is able to export your private key and certificate in PKCS #12 format.
779 Use OpenSSL to convert this into a plain X.509 certificate in PEM format
783 $ openssl pkcs12 -in ns.p12 -clcerts -nodes > key+cert.pem
786 The @code{key+cert.pem} file should be pointed to from the
787 @code{smime-keys} variable. You should now be able to send signed mail.
789 @emph{Note!} Your private key is store unencrypted in the file, so take
792 @subsection Using PGP/MIME
794 PGP/MIME requires an external OpenPGP implementation, such as GNU
795 Privacy Guard (@uref{http://www.gnupg.org/}). It also requires an Emacs
796 interface to it, such as Mailcrypt (available from
797 @uref{http://www.nb.net/~lbudney/linux/software/mailcrypt.html}) or
798 Florian Weimer's @code{gpg.el}.
800 @vindex gpg-temp-directory
801 Note, if you are using the @code{gpg.el} you must make sure that the
802 path specified by @code{gpg-temp-directory} have permissions 0700.
804 Creating your own OpenPGP key is described in detail in the
805 documentation of your OpenPGP implementation, so we refer to it.
807 @node Various Commands
808 @section Various Commands
814 @findex message-caesar-buffer-body
815 Caesar rotate (aka. rot13) the current message
816 (@code{message-caesar-buffer-body}). If narrowing is in effect, just
817 rotate the visible portion of the buffer. A numerical prefix says how
818 many places to rotate the text. The default is 13.
822 @findex message-elide-region
823 Elide the text between point and mark (@code{message-elide-region}).
824 The text is killed and replaced with the contents of the variable
825 @code{message-elide-ellipsis}. The default value is to use an ellipsis
830 @findex message-kill-to-signature
831 Kill all the text up to the signature, or if that's missing, up to the
832 end of the message (@code{message-kill-to-signature}).
836 @findex message-delete-not-region
837 Delete all text in the body of the message that is outside the region
838 (@code{message-delete-not-region}).
842 @findex message-newline-and-reformat
843 Insert four newlines, and then reformat if inside quoted text.
848 > This is some quoted text. And here's more quoted text.
851 If point is before @samp{And} and you press @kbd{M-RET}, you'll get:
854 > This is some quoted text.
858 > And here's more quoted text.
861 @samp{*} says where point will be placed.
865 @findex message-insert-to
866 Insert a @code{To} header that contains the @code{Reply-To} or
867 @code{From} header of the message you're following up
868 (@code{message-insert-to}).
872 @findex message-insert-newsgroups
873 Insert a @code{Newsgroups} header that reflects the @code{Followup-To}
874 or @code{Newsgroups} header of the article you're replying to
875 (@code{message-insert-newsgroups}).
879 @findex message-rename-buffer
880 Rename the buffer (@code{message-rename-buffer}). If given a prefix,
881 prompt for a new buffer name.
892 @findex message-send-and-exit
893 Send the message and bury the current buffer
894 (@code{message-send-and-exit}).
899 Send the message (@code{message-send}).
903 @findex message-dont-send
904 Bury the message buffer and exit (@code{message-dont-send}).
908 @findex message-kill-buffer
909 Kill the message buffer and exit (@code{message-kill-buffer}).
916 @section Mail Aliases
920 @vindex message-mail-alias-type
921 The @code{message-mail-alias-type} variable controls what type of mail
922 alias expansion to use. Currently only one form is supported---Message
923 uses @code{mailabbrev} to handle mail aliases. If this variable is
924 @code{nil}, no mail alias expansion will be performed.
926 @code{mailabbrev} works by parsing the @file{/etc/mailrc} and
927 @file{~/.mailrc} files. These files look like:
930 alias lmi "Lars Magne Ingebrigtsen <larsi@@ifi.uio.no>"
931 alias ding "ding@@ifi.uio.no (ding mailing list)"
934 After adding lines like this to your @file{~/.mailrc} file, you should
935 be able to just write @samp{lmi} in the @code{To} or @code{Cc} (and so
936 on) headers and press @kbd{SPC} to expand the alias.
938 No expansion will be performed upon sending of the message---all
939 expansions have to be done explicitly.
945 @findex ispell-message
947 There are two popular ways to have Emacs spell-check your messages:
948 @code{ispell} and @code{flyspell}. @code{ispell} is the older and
949 probably more popular package. You typically first write the message,
950 and then run the entire thing through @code{ispell} and fix all the
951 typos. To have this happen automatically when you send a message, put
952 something like the following in your @file{.emacs} file:
955 (add-hook 'message-send-hook 'ispell-message)
958 @vindex ispell-message-dictionary-alist
959 If you're in the habit of writing in different languages, this can be
960 controlled by the @code{ispell-message-dictionary-alist} variable:
963 (setq ispell-message-dictionary-alist
964 '(("^Newsgroups:.*\\bde\\." . "deutsch8")
968 @code{ispell} depends on having the external @samp{ispell} command
971 The other popular method is using @code{flyspell}. This package checks
972 your spelling while you're writing, and marks any mis-spelled words in
975 To use @code{flyspell}, put something like the following in your
979 (defun my-message-setup-routine ()
981 (add-hook 'message-setup-hook 'my-message-setup-routine)
984 @code{flyspell} depends on having the external @samp{ispell} command
992 * Message Headers:: General message header stuff.
993 * Mail Headers:: Customizing mail headers.
994 * Mail Variables:: Other mail variables.
995 * News Headers:: Customizing news headers.
996 * News Variables:: Other news variables.
997 * Insertion Variables:: Customizing how things are inserted.
998 * Various Message Variables:: Other message variables.
999 * Sending Variables:: Variables for sending.
1000 * Message Buffers:: How Message names its buffers.
1001 * Message Actions:: Actions to be performed when exiting.
1005 @node Message Headers
1006 @section Message Headers
1008 Message is quite aggressive on the message generation front. It has to
1009 be -- it's a combined news and mail agent. To be able to send combined
1010 messages, it has to generate all headers itself (instead of letting the
1011 mail/news system do it) to ensure that mail and news copies of messages
1012 look sufficiently similar.
1016 @item message-generate-headers-first
1017 @vindex message-generate-headers-first
1018 If non-@code{nil}, generate all required headers before starting to
1019 compose the message.
1021 The variables @code{message-required-mail-headers} and
1022 @code{message-required-news-headers} specify which headers are required.
1024 Note that some headers will be removed and re-generated before posting,
1025 because of the variable @code{message-deletable-headers} (see below).
1027 @item message-from-style
1028 @vindex message-from-style
1029 Specifies how @code{From} headers should look. There are four valid
1034 Just the address -- @samp{king@@grassland.com}.
1037 @samp{king@@grassland.com (Elvis Parsley)}.
1040 @samp{Elvis Parsley <king@@grassland.com>}.
1043 Look like @code{angles} if that doesn't require quoting, and
1044 @code{parens} if it does. If even @code{parens} requires quoting, use
1045 @code{angles} anyway.
1049 @item message-deletable-headers
1050 @vindex message-deletable-headers
1051 Headers in this list that were previously generated by Message will be
1052 deleted before posting. Let's say you post an article. Then you decide
1053 to post it again to some other group, you naughty boy, so you jump back
1054 to the @code{*post-buf*} buffer, edit the @code{Newsgroups} line, and
1055 ship it off again. By default, this variable makes sure that the old
1056 generated @code{Message-ID} is deleted, and a new one generated. If
1057 this isn't done, the entire empire would probably crumble, anarchy would
1058 prevail, and cats would start walking on two legs and rule the world.
1061 @item message-default-headers
1062 @vindex message-default-headers
1063 This string is inserted at the end of the headers in all message
1066 @item message-subject-re-regexp
1067 @vindex message-subject-re-regexp
1071 Responses to messages have subjects that start with @samp{Re: }. This
1072 is @emph{not} an abbreviation of the English word ``response'', but is
1073 Latin, and means ``in response to''. Some illiterate nincompoops have
1074 failed to grasp this fact, and have ``internationalized'' their software
1075 to use abonimations like @samp{Aw: } (``antwort'') or @samp{Sv: }
1076 (``svar'') instead, which is meaningless and evil. However, you may
1077 have to deal with users that use these evil tools, in which case you may
1078 set this variable to a regexp that matches these prefixes. Myself, I
1079 just throw away non-compliant mail.
1081 Here's an example of a value to deal with these headers when
1082 responding to a message:
1085 (setq message-subject-re-regexp
1086 "^\\(\\(\\([Rr][Ee]\\|[Ss][Vv]\\|[Aa][Ww]\\): *\\)+\\))
1089 @item message-alternative-emails
1090 @vindex message-alternative-emails
1091 A regexp to match the alternative email addresses. The first matched
1092 address (not primary one) is used in the @code{From} field.
1098 @section Mail Headers
1101 @item message-required-mail-headers
1102 @vindex message-required-mail-headers
1103 @xref{News Headers}, for the syntax of this variable. It is
1104 @code{(From Date Subject (optional . In-Reply-To) Message-ID Lines
1105 (optional . User-Agent))} by default.
1107 @item message-ignored-mail-headers
1108 @vindex message-ignored-mail-headers
1109 Regexp of headers to be removed before mailing. The default is
1110 @samp{^[GF]cc:\\|^Resent-Fcc:\\|^Xref:\\|^X-Draft-From:}.
1112 @item message-default-mail-headers
1113 @vindex message-default-mail-headers
1114 This string is inserted at the end of the headers in all message
1115 buffers that are initialized as mail.
1120 @node Mail Variables
1121 @section Mail Variables
1124 @item message-send-mail-function
1125 @vindex message-send-mail-function
1126 @findex message-send-mail-with-sendmail
1127 @findex message-send-mail-with-mh
1128 @findex message-send-mail-with-qmail
1129 @findex smtpmail-send-it
1130 @findex feedmail-send-it
1131 Function used to send the current buffer as mail. The default is
1132 @code{message-send-mail-with-sendmail}. Other valid values include
1133 @code{message-send-mail-with-mh}, @code{message-send-mail-with-qmail},
1134 @code{smtpmail-send-it} and @code{feedmail-send-it}.
1136 @item message-mh-deletable-headers
1137 @vindex message-mh-deletable-headers
1138 Most versions of MH doesn't like being fed messages that contain the
1139 headers in this variable. If this variable is non-@code{nil} (which is
1140 the default), these headers will be removed before mailing when sending
1141 messages via MH. Set it to @code{nil} if your MH can handle these
1144 @item message-send-mail-partially-limit
1145 @vindex message-send-mail-partially-limit
1146 The limitation of messages sent as message/partial.
1147 The lower bound of message size in characters, beyond which the message
1148 should be sent in several parts. If it is nil, the size is unlimited.
1154 @section News Headers
1156 @vindex message-required-news-headers
1157 @code{message-required-news-headers} a list of header symbols. These
1158 headers will either be automatically generated, or, if that's
1159 impossible, they will be prompted for. The following symbols are valid:
1165 @findex user-full-name
1166 @findex user-mail-address
1167 This required header will be filled out with the result of the
1168 @code{message-make-from} function, which depends on the
1169 @code{message-from-style}, @code{user-full-name},
1170 @code{user-mail-address} variables.
1174 This required header will be prompted for if not present already.
1178 This required header says which newsgroups the article is to be posted
1179 to. If it isn't present already, it will be prompted for.
1182 @cindex organization
1183 This optional header will be filled out depending on the
1184 @code{message-user-organization} variable.
1185 @code{message-user-organization-file} will be used if this variable is
1186 @code{t}. This variable can also be a string (in which case this string
1187 will be used), or it can be a function (which will be called with no
1188 parameters and should return a string to be used).
1192 This optional header will be computed by Message.
1196 @vindex mail-host-address
1199 This required header will be generated by Message. A unique ID will be
1200 created based on the date, time, user name and system name. Message
1201 will use @code{system-name} to determine the name of the system. If
1202 this isn't a fully qualified domain name (FQDN), Message will use
1203 @code{mail-host-address} as the FQDN of the machine.
1207 This optional header will be filled out according to the
1208 @code{message-newsreader} local variable.
1211 This optional header is filled out using the @code{Date} and @code{From}
1212 header of the article being replied to.
1216 This extremely optional header will be inserted according to the
1217 @code{message-expires} variable. It is highly deprecated and shouldn't
1218 be used unless you know what you're doing.
1221 @cindex Distribution
1222 This optional header is filled out according to the
1223 @code{message-distribution-function} variable. It is a deprecated and
1224 much misunderstood header.
1228 This extremely optional header should probably never be used.
1229 However, some @emph{very} old servers require that this header is
1230 present. @code{message-user-path} further controls how this
1231 @code{Path} header is to look. If it is @code{nil}, use the server name
1232 as the leaf node. If it is a string, use the string. If it is neither
1233 a string nor @code{nil}, use the user name only. However, it is highly
1234 unlikely that you should need to fiddle with this variable at all.
1238 @cindex Mime-Version
1239 In addition, you can enter conses into this list. The car of this cons
1240 should be a symbol. This symbol's name is the name of the header, and
1241 the cdr can either be a string to be entered verbatim as the value of
1242 this header, or it can be a function to be called. This function should
1243 return a string to be inserted. For instance, if you want to insert
1244 @code{Mime-Version: 1.0}, you should enter @code{(Mime-Version . "1.0")}
1245 into the list. If you want to insert a funny quote, you could enter
1246 something like @code{(X-Yow . yow)} into the list. The function
1247 @code{yow} will then be called without any arguments.
1249 If the list contains a cons where the car of the cons is
1250 @code{optional}, the cdr of this cons will only be inserted if it is
1253 Other variables for customizing outgoing news articles:
1257 @item message-syntax-checks
1258 @vindex message-syntax-checks
1259 Controls what syntax checks should not be performed on outgoing posts.
1260 To disable checking of long signatures, for instance, add
1263 (signature . disabled)
1272 Check the subject for commands.
1275 Insert a new @code{Sender} header if the @code{From} header looks odd.
1276 @item multiple-headers
1277 Check for the existence of multiple equal headers.
1280 Check for the existence of version and sendsys commands.
1282 Check whether the @code{Message-ID} looks ok.
1284 Check whether the @code{From} header seems nice.
1287 Check for too long lines.
1289 Check for invalid characters.
1291 Check for excessive size.
1293 Check whether there is any new text in the messages.
1295 Check the length of the signature.
1298 Check whether the article has an @code{Approved} header, which is
1299 something only moderators should include.
1301 Check whether the article is empty.
1302 @item invisible-text
1303 Check whether there is any invisible text in the buffer.
1305 Check whether any of the headers are empty.
1306 @item existing-newsgroups
1307 Check whether the newsgroups mentioned in the @code{Newsgroups} and
1308 @code{Followup-To} headers exist.
1309 @item valid-newsgroups
1310 Check whether the @code{Newsgroups} and @code{Followup-to} headers
1311 are valid syntactically.
1312 @item repeated-newsgroups
1313 Check whether the @code{Newsgroups} and @code{Followup-to} headers
1314 contains repeated group names.
1315 @item shorten-followup-to
1316 Check whether to add a @code{Followup-to} header to shorten the number
1317 of groups to post to.
1320 All these conditions are checked by default.
1322 @item message-ignored-news-headers
1323 @vindex message-ignored-news-headers
1324 Regexp of headers to be removed before posting. The default is@*
1325 @samp{^NNTP-Posting-Host:\\|^Xref:\\|^[BGF]cc:\\|^Resent-Fcc:\\|^X-Draft-From:}.
1327 @item message-default-news-headers
1328 @vindex message-default-news-headers
1329 This string is inserted at the end of the headers in all message
1330 buffers that are initialized as news.
1335 @node News Variables
1336 @section News Variables
1339 @item message-send-news-function
1340 @vindex message-send-news-function
1341 Function used to send the current buffer as news. The default is
1342 @code{message-send-news}.
1344 @item message-post-method
1345 @vindex message-post-method
1346 Gnusish @dfn{select method} (see the Gnus manual for details) used for
1347 posting a prepared news message.
1352 @node Insertion Variables
1353 @section Insertion Variables
1356 @item message-ignored-cited-headers
1357 @vindex message-ignored-cited-headers
1358 All headers that match this regexp will be removed from yanked
1359 messages. The default is @samp{.}, which means that all headers will be
1362 @item message-cite-prefix-regexp
1363 @vindex message-cite-prefix-regexp
1364 Regexp matching the longest possible citation prefix on a line.
1366 @item message-citation-line-function
1367 @vindex message-citation-line-function
1368 @cindex attribution line
1369 Function called to insert the citation line. The default is
1370 @code{message-insert-citation-line}, which will lead to citation lines
1374 Hallvard B Furuseth <h.b.furuseth@@usit.uio.no> writes:
1377 Point will be at the beginning of the body of the message when this
1380 Note that Gnus provides a feature where clicking on `writes:' hides the
1381 cited text. If you change the citation line too much, readers of your
1382 messages will have to adjust their Gnus, too. See the variable
1383 @code{gnus-cite-attribution-suffix}. @xref{Article Highlighting, ,
1384 Article Highlighting, gnus}, for details.
1386 @item message-yank-prefix
1387 @vindex message-yank-prefix
1390 When you are replying to or following up an article, you normally want
1391 to quote the person you are answering. Inserting quoted text is done
1392 by @dfn{yanking}, and each line you yank will have
1393 @code{message-yank-prefix} prepended to it (except for quoted and
1394 empty lines which uses @code{message-yank-cited-prefix}). The default
1397 @item message-yank-cited-prefix
1398 @vindex message-yank-cited-prefix
1402 When yanking text from a article which contains no text or already
1403 cited text, each line will be prefixed with the contents of this
1404 variable. The default is @samp{>}. See also
1405 @code{message-yank-prefix}.
1407 @item message-indentation-spaces
1408 @vindex message-indentation-spaces
1409 Number of spaces to indent yanked messages.
1411 @item message-cite-function
1412 @vindex message-cite-function
1413 @findex message-cite-original
1414 @findex sc-cite-original
1415 @findex message-cite-original-without-signature
1417 Function for citing an original message. The default is
1418 @code{message-cite-original}, which simply inserts the original message
1419 and prepends @samp{> } to each line.
1420 @code{message-cite-original-without-signature} does the same, but elides
1421 the signature. You can also set it to @code{sc-cite-original} to use
1424 @item message-indent-citation-function
1425 @vindex message-indent-citation-function
1426 Function for modifying a citation just inserted in the mail buffer.
1427 This can also be a list of functions. Each function can find the
1428 citation between @code{(point)} and @code{(mark t)}. And each function
1429 should leave point and mark around the citation text as modified.
1431 @item message-signature
1432 @vindex message-signature
1433 String to be inserted at the end of the message buffer. If @code{t}
1434 (which is the default), the @code{message-signature-file} file will be
1435 inserted instead. If a function, the result from the function will be
1436 used instead. If a form, the result from the form will be used instead.
1437 If this variable is @code{nil}, no signature will be inserted at all.
1439 @item message-signature-file
1440 @vindex message-signature-file
1441 File containing the signature to be inserted at the end of the buffer.
1442 The default is @samp{~/.signature}.
1446 Note that RFC1036bis says that a signature should be preceded by the three
1447 characters @samp{-- } on a line by themselves. This is to make it
1448 easier for the recipient to automatically recognize and process the
1449 signature. So don't remove those characters, even though you might feel
1450 that they ruin your beautiful design, like, totally.
1452 Also note that no signature should be more than four lines long.
1453 Including ASCII graphics is an efficient way to get everybody to believe
1454 that you are silly and have nothing important to say.
1457 @node Various Message Variables
1458 @section Various Message Variables
1461 @item message-default-charset
1462 @vindex message-default-charset
1464 Symbol naming a @sc{mime} charset. Non-ASCII characters in messages are
1465 assumed to be encoded using this charset. The default is @code{nil},
1466 which means ask the user. (This variable is used only on non-@sc{mule}
1468 @xref{Charset Translation, , Charset Translation, emacs-mime,
1469 Emacs MIME Manual}, for details on the @sc{mule}-to-@sc{mime}
1470 translation process.
1472 @item message-signature-separator
1473 @vindex message-signature-separator
1474 Regexp matching the signature separator. It is @samp{^-- *$} by
1477 @item mail-header-separator
1478 @vindex mail-header-separator
1479 String used to separate the headers from the body. It is @samp{--text
1480 follows this line--} by default.
1482 @item message-directory
1483 @vindex message-directory
1484 Directory used by many mailey things. The default is @file{~/Mail/}.
1486 @item message-signature-setup-hook
1487 @vindex message-signature-setup-hook
1488 Hook run when initializing the message buffer. It is run after the
1489 headers have been inserted but before the signature has been inserted.
1491 @item message-setup-hook
1492 @vindex message-setup-hook
1493 Hook run as the last thing when the message buffer has been initialized,
1494 but before yanked text is inserted.
1496 @item message-header-setup-hook
1497 @vindex message-header-setup-hook
1498 Hook called narrowed to the headers after initializing the headers.
1500 For instance, if you're running Gnus and wish to insert a
1501 @samp{Mail-Copies-To} header in all your news articles and all messages
1502 you send to mailing lists, you could do something like the following:
1505 (defun my-message-header-setup-hook ()
1506 (let ((group (or gnus-newsgroup-name "")))
1507 (when (or (message-fetch-field "newsgroups")
1508 (gnus-group-find-parameter group 'to-address)
1509 (gnus-group-find-parameter group 'to-list))
1510 (insert "Mail-Copies-To: never\n"))))
1512 (add-hook 'message-header-setup-hook
1513 'my-message-header-setup-hook)
1516 @item message-send-hook
1517 @vindex message-send-hook
1518 Hook run before sending messages.
1520 If you want to add certain headers before sending, you can use the
1521 @code{message-add-header} function in this hook. For instance:
1522 @findex message-add-header
1525 (add-hook 'message-send-hook 'my-message-add-content)
1526 (defun my-message-add-content ()
1527 (message-add-header "X-In-No-Sense: Nonsense")
1528 (message-add-header "X-Whatever: no"))
1531 This function won't add the header if the header is already present.
1533 @item message-send-mail-hook
1534 @vindex message-send-mail-hook
1535 Hook run before sending mail messages.
1537 @item message-send-news-hook
1538 @vindex message-send-news-hook
1539 Hook run before sending news messages.
1541 @item message-sent-hook
1542 @vindex message-sent-hook
1543 Hook run after sending messages.
1545 @item message-mode-syntax-table
1546 @vindex message-mode-syntax-table
1547 Syntax table used in message mode buffers.
1549 @item message-send-method-alist
1550 @vindex message-send-method-alist
1552 Alist of ways to send outgoing messages. Each element has the form
1555 (TYPE PREDICATE FUNCTION)
1560 A symbol that names the method.
1563 A function called without any parameters to determine whether the
1564 message is a message of type @var{type}.
1567 A function to be called if @var{predicate} returns non-@code{nil}.
1568 @var{function} is called with one parameter -- the prefix.
1572 ((news message-news-p message-send-via-news)
1573 (mail message-mail-p message-send-via-mail))
1582 @node Sending Variables
1583 @section Sending Variables
1587 @item message-fcc-handler-function
1588 @vindex message-fcc-handler-function
1589 A function called to save outgoing articles. This function will be
1590 called with the name of the file to store the article in. The default
1591 function is @code{message-output} which saves in Unix mailbox format.
1593 @item message-courtesy-message
1594 @vindex message-courtesy-message
1595 When sending combined messages, this string is inserted at the start of
1596 the mailed copy. If the string contains the format spec @samp{%s}, the
1597 newsgroups the article has been posted to will be inserted there. If
1598 this variable is @code{nil}, no such courtesy message will be added.
1599 The default value is @samp{"The following message is a courtesy copy of
1600 an article\\nthat has been posted to %s as well.\\n\\n"}.
1605 @node Message Buffers
1606 @section Message Buffers
1608 Message will generate new buffers with unique buffer names when you
1609 request a message buffer. When you send the message, the buffer isn't
1610 normally killed off. Its name is changed and a certain number of old
1611 message buffers are kept alive.
1614 @item message-generate-new-buffers
1615 @vindex message-generate-new-buffers
1616 If non-@code{nil}, generate new buffers. The default is @code{t}. If
1617 this is a function, call that function with three parameters: The type,
1618 the to address and the group name. (Any of these may be @code{nil}.)
1619 The function should return the new buffer name.
1621 @item message-max-buffers
1622 @vindex message-max-buffers
1623 This variable says how many old message buffers to keep. If there are
1624 more message buffers than this, the oldest buffer will be killed. The
1625 default is 10. If this variable is @code{nil}, no old message buffers
1626 will ever be killed.
1628 @item message-send-rename-function
1629 @vindex message-send-rename-function
1630 After sending a message, the buffer is renamed from, for instance,
1631 @samp{*reply to Lars*} to @samp{*sent reply to Lars*}. If you don't
1632 like this, set this variable to a function that renames the buffer in a
1633 manner you like. If you don't want to rename the buffer at all, you can
1637 (setq message-send-rename-function 'ignore)
1640 @item message-kill-buffer-on-exit
1641 @findex message-kill-buffer-on-exit
1642 If non-@code{nil}, kill the buffer immediately on exit.
1647 @node Message Actions
1648 @section Message Actions
1650 When Message is being used from a news/mail reader, the reader is likely
1651 to want to perform some task after the message has been sent. Perhaps
1652 return to the previous window configuration or mark an article as
1655 @vindex message-kill-actions
1656 @vindex message-postpone-actions
1657 @vindex message-exit-actions
1658 @vindex message-send-actions
1659 The user may exit from the message buffer in various ways. The most
1660 common is @kbd{C-c C-c}, which sends the message and exits. Other
1661 possibilities are @kbd{C-c C-s} which just sends the message, @kbd{C-c
1662 C-d} which postpones the message editing and buries the message buffer,
1663 and @kbd{C-c C-k} which kills the message buffer. Each of these actions
1664 have lists associated with them that contains actions to be executed:
1665 @code{message-send-actions}, @code{message-exit-actions},
1666 @code{message-postpone-actions}, and @code{message-kill-actions}.
1668 Message provides a function to interface with these lists:
1669 @code{message-add-action}. The first parameter is the action to be
1670 added, and the rest of the arguments are which lists to add this action
1671 to. Here's an example from Gnus:
1675 `(set-window-configuration ,(current-window-configuration))
1676 'exit 'postpone 'kill)
1679 This restores the Gnus window configuration when the message buffer is
1680 killed, postponed or exited.
1682 An @dfn{action} can be either: a normal function, or a list where the
1683 @code{car} is a function and the @code{cdr} is the list of arguments, or
1684 a form to be @code{eval}ed.
1688 @chapter Compatibility
1689 @cindex compatibility
1691 Message uses virtually only its own variables---older @code{mail-}
1692 variables aren't consulted. To force Message to take those variables
1693 into account, you can put the following in your @code{.emacs} file:
1696 (require 'messcompat)
1699 This will initialize many Message variables from the values in the
1700 corresponding mail variables.
1707 * Responses:: Standard rules for determining where responses go.
1714 To determine where a message is to go, the following algorithm is used
1719 A @dfn{reply} is when you want to respond @emph{just} to the person who
1720 sent the message via mail. There will only be one recipient. To
1721 determine who the recipient will be, the following headers are
1732 A @dfn{wide reply} is a mail response that includes @emph{all} entities
1733 mentioned in the message you are responded to. All mailboxes from the
1734 following headers will be concatenated to form the outgoing
1735 @code{To}/@code{Cc} headers:
1739 (unless there's a @code{Reply-To}, in which case that is used instead).
1746 If a @code{Mail-Copies-To} header is present, it will also be included
1747 in the list of mailboxes. If this header is @samp{never}, that means
1748 that the @code{From} (or @code{Reply-To}) mailbox will be suppressed.
1752 A @dfn{followup} is a response sent via news. The following headers
1753 (listed in order of precedence) determine where the response is to be
1764 If a @code{Mail-Copies-To} header is present, it will be used as the
1765 basis of the new @code{Cc} header, except if this header is