1 \input texinfo @c -*-texinfo-*-
4 @settitle T-gnus 6.17 Message Manual
9 This file documents Message, the Emacs message composition mode.
11 Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004,
12 2005 Free Software Foundation, Inc.
15 Permission is granted to copy, distribute and/or modify this document
16 under the terms of the GNU Free Documentation License, Version 1.2 or
17 any later version published by the Free Software Foundation; with no
18 Invariant Sections, with the Front-Cover texts being ``A GNU
19 Manual'', and with the Back-Cover Texts as in (a) below. A copy of the
20 license is included in the section entitled ``GNU Free Documentation
21 License'' in the Emacs manual.
23 (a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify
24 this GNU Manual, like GNU software. Copies published by the Free
25 Software Foundation raise funds for GNU development.''
27 This document is part of a collection distributed under the GNU Free
28 Documentation License. If you want to distribute this document
29 separately from the collection, you can do so by adding a copy of the
30 license to the document, as described in section 6 of the license.
36 * Message: (message). Mail and news composition mode that goes with Gnus.
41 @setchapternewpage odd
44 @title T-gnus 6.17 Message Manual
46 @author by Lars Magne Ingebrigtsen
49 @vskip 0pt plus 1filll
57 All message composition from Gnus (both mail and news) takes place in
61 * Interface:: Setting up message buffers.
62 * Commands:: Commands you can execute in message mode buffers.
63 * Variables:: Customizing the message buffers.
64 * Compatibility:: Making Message backwards compatible.
65 * Appendices:: More technical things.
66 * Index:: Variable, function and concept index.
67 * Key Index:: List of Message mode keys.
70 This manual corresponds to T-gnus 6.17 Message. Message is distributed
71 with the Gnus distribution bearing the same version number as this
78 When a program (or a person) wants to respond to a message---reply,
79 follow up, forward, cancel---the program (or person) should just put
80 point in the buffer where the message is and call the required command.
81 @code{Message} will then pop up a new @code{message} mode buffer with
82 appropriate headers filled out, and the user can edit the message before
86 * New Mail Message:: Editing a brand new mail message.
87 * New News Message:: Editing a brand new news message.
88 * Reply:: Replying via mail.
89 * Wide Reply:: Responding to all people via mail.
90 * Followup:: Following up via news.
91 * Canceling News:: Canceling a news article.
92 * Superseding:: Superseding a message.
93 * Forwarding:: Forwarding a message via news or mail.
94 * Resending:: Resending a mail message.
95 * Bouncing:: Bouncing a mail message.
96 * Mailing Lists:: Send mail to mailing lists.
100 @node New Mail Message
101 @section New Mail Message
104 The @code{message-mail} command pops up a new message buffer.
106 Two optional parameters are accepted: The first will be used as the
107 @code{To} header and the second as the @code{Subject} header. If these
108 are @code{nil}, those two headers will be empty.
111 @node New News Message
112 @section New News Message
115 The @code{message-news} command pops up a new message buffer.
117 This function accepts two optional parameters. The first will be used
118 as the @code{Newsgroups} header and the second as the @code{Subject}
119 header. If these are @code{nil}, those two headers will be empty.
125 @findex message-reply
126 The @code{message-reply} function pops up a message buffer that's a
127 reply to the message in the current buffer.
129 @vindex message-reply-to-function
130 Message uses the normal methods to determine where replies are to go
131 (@pxref{Responses}), but you can change the behavior to suit your needs
132 by fiddling with the @code{message-reply-to-function} variable.
134 If you want the replies to go to the @code{Sender} instead of the
135 @code{From}, you could do something like this:
138 (setq message-reply-to-function
140 (cond ((equal (mail-fetch-field "from") "somebody")
141 (list (cons 'To (mail-fetch-field "sender"))))
146 This function will be called narrowed to the head of the article that is
149 As you can see, this function should return a list. In this case, it
150 returns @code{((To . "Whom"))} if it has an opinion as to what the To
151 header should be. If it does not, it should just return @code{nil}, and
152 the normal methods for determining the To header will be used.
154 Each list element should be a cons, where the @sc{car} should be the
155 name of a header (e.g. @code{Cc}) and the @sc{cdr} should be the header
156 value (e.g. @samp{larsi@@ifi.uio.no}). All these headers will be
157 inserted into the head of the outgoing mail.
163 @findex message-wide-reply
164 The @code{message-wide-reply} pops up a message buffer that's a wide
165 reply to the message in the current buffer. A @dfn{wide reply} is a
166 reply that goes out to all people listed in the @code{To}, @code{From}
167 (or @code{Reply-to}) and @code{Cc} headers.
169 @vindex message-wide-reply-to-function
170 Message uses the normal methods to determine where wide replies are to go,
171 but you can change the behavior to suit your needs by fiddling with the
172 @code{message-wide-reply-to-function}. It is used in the same way as
173 @code{message-reply-to-function} (@pxref{Reply}).
175 @vindex message-dont-reply-to-names
176 Addresses that match the @code{message-dont-reply-to-names} regular
177 expression will be removed from the @code{Cc} header.
179 @vindex message-wide-reply-confirm-recipients
180 If @code{message-wide-reply-confirm-recipients} is non-@code{nil} you
181 will be asked to confirm that you want to reply to multiple
182 recipients. The default is @code{nil}.
187 @findex message-followup
188 The @code{message-followup} command pops up a message buffer that's a
189 followup to the message in the current buffer.
191 @vindex message-followup-to-function
192 Message uses the normal methods to determine where followups are to go,
193 but you can change the behavior to suit your needs by fiddling with the
194 @code{message-followup-to-function}. It is used in the same way as
195 @code{message-reply-to-function} (@pxref{Reply}).
197 @vindex message-use-followup-to
198 The @code{message-use-followup-to} variable says what to do about
199 @code{Followup-To} headers. If it is @code{use}, always use the value.
200 If it is @code{ask} (which is the default), ask whether to use the
201 value. If it is @code{t}, use the value unless it is @samp{poster}. If
202 it is @code{nil}, don't use the value.
206 @section Canceling News
208 @findex message-cancel-news
209 The @code{message-cancel-news} command cancels the article in the
212 @vindex message-cancel-message
213 The value of @code{message-cancel-message} is inserted in the body of
214 the cancel message. The default is @samp{I am canceling my own
218 @vindex message-insert-canlock
220 When Message posts news messages, it inserts @code{Cancel-Lock}
221 headers by default. This is a cryptographic header that ensures that
222 only you can cancel your own messages, which is nice. The downside
223 is that if you lose your @file{.emacs} file (which is where Gnus
224 stores the secret cancel lock password (which is generated
225 automatically the first time you use this feature)), you won't be
226 able to cancel your message. If you want to manage a password yourself,
227 you can put something like the following in your @file{~/.gnus.el} file:
230 (setq canlock-password "geheimnis"
231 canlock-password-for-verify canlock-password)
234 Whether to insert the header or not is controlled by the
235 @code{message-insert-canlock} variable.
237 Not many news servers respect the @code{Cancel-Lock} header yet, but
238 this is expected to change in the future.
244 @findex message-supersede
245 The @code{message-supersede} command pops up a message buffer that will
246 supersede the message in the current buffer.
248 @vindex message-ignored-supersedes-headers
249 Headers matching the @code{message-ignored-supersedes-headers} are
250 removed before popping up the new message buffer. The default is@*
251 @samp{^Path:\\|^Date\\|^NNTP-Posting-Host:\\|^Xref:\\|^Lines:\\|@*
252 ^Received:\\|^X-From-Line:\\|Return-Path:\\|^Supersedes:}.
259 @findex message-forward
260 The @code{message-forward} command pops up a message buffer to forward
261 the message in the current buffer. If given a prefix, forward using
265 @item message-forward-ignored-headers
266 @vindex message-forward-ignored-headers
267 All headers that match this regexp will be deleted when forwarding a message.
269 @item message-make-forward-subject-function
270 @vindex message-make-forward-subject-function
271 A list of functions that are called to generate a subject header for
272 forwarded messages. The subject generated by the previous function is
273 passed into each successive function.
275 The provided functions are:
278 @item message-forward-subject-author-subject
279 @findex message-forward-subject-author-subject
280 Source of article (author or newsgroup), in brackets followed by the
283 @item message-forward-subject-fwd
284 Subject of article with @samp{Fwd:} prepended to it.
287 @item message-wash-forwarded-subjects
288 @vindex message-wash-forwarded-subjects
289 If this variable is @code{t}, the subjects of forwarded messages have
290 the evidence of previous forwards (such as @samp{Fwd:}, @samp{Re:},
291 @samp{(fwd)}) removed before the new subject is
292 constructed. The default value is @code{nil}.
294 @item message-forward-as-mime
295 @vindex message-forward-as-mime
296 If this variable is @code{t} (the default), forwarded messages are
297 included as inline @acronym{MIME} RFC822 parts. If it's @code{nil}, forwarded
298 messages will just be copied inline to the new message, like previous,
299 non @acronym{MIME}-savvy versions of Gnus would do.
301 @item message-forward-before-signature
302 @vindex message-forward-before-signature
303 If non-@code{nil}, put forwarded message before signature, else after.
311 @findex message-resend
312 The @code{message-resend} command will prompt the user for an address
313 and resend the message in the current buffer to that address.
315 @vindex message-ignored-resent-headers
316 Headers that match the @code{message-ignored-resent-headers} regexp will
317 be removed before sending the message.
323 @findex message-bounce
324 The @code{message-bounce} command will, if the current buffer contains a
325 bounced mail message, pop up a message buffer stripped of the bounce
326 information. A @dfn{bounced message} is typically a mail you've sent
327 out that has been returned by some @code{mailer-daemon} as
330 @vindex message-ignored-bounced-headers
331 Headers that match the @code{message-ignored-bounced-headers} regexp
332 will be removed before popping up the buffer. The default is
333 @samp{^\\(Received\\|Return-Path\\):}.
337 @section Mailing Lists
339 @cindex Mail-Followup-To
340 Sometimes while posting to mailing lists, the poster needs to direct
341 followups to the post to specific places. The Mail-Followup-To (MFT)
342 was created to enable just this. Two example scenarios where this is
347 A mailing list poster can use MFT to express that responses should be
348 sent to just the list, and not the poster as well. This will happen
349 if the poster is already subscribed to the list.
352 A mailing list poster can use MFT to express that responses should be
353 sent to the list and the poster as well. This will happen if the poster
354 is not subscribed to the list.
357 If a message is posted to several mailing lists, MFT may also be used
358 to direct the following discussion to one list only, because
359 discussions that are spread over several lists tend to be fragmented
360 and very difficult to follow.
364 Gnus honors the MFT header in other's messages (i.e. while following
365 up to someone else's post) and also provides support for generating
366 sensible MFT headers for outgoing messages as well.
369 @c * Honoring an MFT post:: What to do when one already exists
370 @c * Composing with a MFT header:: Creating one from scratch.
373 @c @node Composing with a MFT header
374 @subsection Composing a correct MFT header automagically
376 The first step in getting Gnus to automagically generate a MFT header
377 in posts you make is to give Gnus a list of the mailing lists
378 addresses you are subscribed to. You can do this in more than one
379 way. The following variables would come in handy.
383 @vindex message-subscribed-addresses
384 @item message-subscribed-addresses
385 This should be a list of addresses the user is subscribed to. Its
386 default value is @code{nil}. Example:
388 (setq message-subscribed-addresses
389 '("ding@@gnus.org" "bing@@noose.org"))
392 @vindex message-subscribed-regexps
393 @item message-subscribed-regexps
394 This should be a list of regexps denoting the addresses of mailing
395 lists subscribed to. Default value is @code{nil}. Example: If you
396 want to achieve the same result as above:
398 (setq message-subscribed-regexps
399 '("\\(ding@@gnus\\)\\|\\(bing@@noose\\)\\.org")
402 @vindex message-subscribed-address-functions
403 @item message-subscribed-address-functions
404 This can be a list of functions to be called (one at a time!!) to
405 determine the value of MFT headers. It is advisable that these
406 functions not take any arguments. Default value is @code{nil}.
408 There is a pre-defined function in Gnus that is a good candidate for
409 this variable. @code{gnus-find-subscribed-addresses} is a function
410 that returns a list of addresses corresponding to the groups that have
411 the @code{subscribed} (@pxref{Group Parameters, ,Group Parameters,
412 gnus, The Gnus Manual}) group parameter set to a non-@code{nil} value.
413 This is how you would do it.
416 (setq message-subscribed-address-functions
417 '(gnus-find-subscribed-addresses))
420 @vindex message-subscribed-address-file
421 @item message-subscribed-address-file
422 You might be one organized human freak and have a list of addresses of
423 all subscribed mailing lists in a separate file! Then you can just
424 set this variable to the name of the file and life would be good.
428 You can use one or more of the above variables. All their values are
429 ``added'' in some way that works :-)
431 Now you are all set. Just start composing a message as you normally do.
432 And just send it; as always. Just before the message is sent out, Gnus'
433 MFT generation thingy kicks in and checks if the message already has a
434 MFT field. If there is one, it is left alone. (Except if it's empty -
435 in that case, the field is removed and is not replaced with an
436 automatically generated one. This lets you disable MFT generation on a
437 per-message basis.) If there is none, then the list of recipient
438 addresses (in the To: and Cc: headers) is checked to see if one of them
439 is a list address you are subscribed to. If none of them is a list
440 address, then no MFT is generated; otherwise, a MFT is added to the
441 other headers and set to the value of all addresses in To: and Cc:
444 @findex message-generate-unsubscribed-mail-followup-to
446 @findex message-goto-mail-followup-to
447 Hm. ``So'', you ask, ``what if I send an email to a list I am not
448 subscribed to? I want my MFT to say that I want an extra copy.'' (This
449 is supposed to be interpreted by others the same way as if there were no
450 MFT, but you can use an explicit MFT to override someone else's
451 to-address group parameter.) The function
452 @code{message-generate-unsubscribed-mail-followup-to} might come in
453 handy. It is bound to @kbd{C-c C-f C-a} by default. In any case, you
454 can insert a MFT of your own choice; @kbd{C-c C-f C-m}
455 (@code{message-goto-mail-followup-to}) will help you get started.
457 @c @node Honoring an MFT post
458 @subsection Honoring an MFT post
460 @vindex message-use-mail-followup-to
461 When you followup to a post on a mailing list, and the post has a MFT
462 header, Gnus' action will depend on the value of the variable
463 @code{message-use-mail-followup-to}. This variable can be one of:
467 Always honor MFTs. The To: and Cc: headers in your followup will be
468 derived from the MFT header of the original post. This is the default.
471 Always dishonor MFTs (just ignore the darned thing)
474 Gnus will prompt you for an action.
478 It is considered good netiquette to honor MFT, as it is assumed the
479 fellow who posted a message knows where the followups need to go
486 * Buffer Entry:: Commands after entering a Message buffer.
487 * Header Commands:: Commands for moving headers or changing headers.
488 * Movement:: Moving around in message buffers.
489 * Insertion:: Inserting things into message buffers.
490 * MIME:: @acronym{MIME} considerations.
491 * IDNA:: Non-@acronym{ASCII} domain name considerations.
492 * Security:: Signing and encrypting messages.
493 * Various Commands:: Various things.
494 * Sending:: Actually sending the message.
495 * Mail Aliases:: How to use mail aliases.
496 * Spelling:: Having Emacs check your spelling.
501 @section Buffer Entry
505 You most often end up in a Message buffer when responding to some other
506 message of some sort. Message does lots of handling of quoted text, and
507 may remove signatures, reformat the text, or the like---depending on
508 which used settings you're using. Message usually gets things right,
509 but sometimes it stumbles. To help the user unwind these stumblings,
510 Message sets the undo boundary before each major automatic action it
511 takes. If you press the undo key (usually located at @kbd{C-_}) a few
512 times, you will get back the un-edited message you're responding to.
515 @node Header Commands
516 @section Header Commands
518 @subsection Commands for moving to headers
520 These following commands move to the header in question. If it doesn't
521 exist, it will be inserted.
527 @findex describe-mode
528 Describe the message mode.
532 @findex message-goto-to
533 Go to the @code{To} header (@code{message-goto-to}).
537 @findex message-goto-from
538 Go to the @code{From} header (@code{message-goto-from}). (The ``o''
539 in the key binding is for Originator.)
543 @findex message-goto-bcc
544 Go to the @code{Bcc} header (@code{message-goto-bcc}).
548 @findex message-goto-fcc
549 Go to the @code{Fcc} header (@code{message-goto-fcc}).
553 @findex message-goto-cc
554 Go to the @code{Cc} header (@code{message-goto-cc}).
558 @findex message-goto-subject
559 Go to the @code{Subject} header (@code{message-goto-subject}).
563 @findex message-goto-reply-to
564 Go to the @code{Reply-To} header (@code{message-goto-reply-to}).
568 @findex message-goto-newsgroups
569 Go to the @code{Newsgroups} header (@code{message-goto-newsgroups}).
573 @findex message-goto-distribution
574 Go to the @code{Distribution} header (@code{message-goto-distribution}).
578 @findex message-goto-followup-to
579 Go to the @code{Followup-To} header (@code{message-goto-followup-to}).
583 @findex message-goto-keywords
584 Go to the @code{Keywords} header (@code{message-goto-keywords}).
588 @findex message-goto-summary
589 Go to the @code{Summary} header (@code{message-goto-summary}).
593 @findex message-insert-or-toggle-importance
594 This inserts the @samp{Importance:} header with a value of
595 @samp{high}. This header is used to signal the importance of the
596 message to the receiver. If the header is already present in the
597 buffer, it cycles between the three valid values according to RFC
598 1376: @samp{low}, @samp{normal} and @samp{high}.
602 @findex message-generate-unsubscribed-mail-followup-to
603 Insert a reasonable @samp{Mail-Followup-To:} header
604 (@pxref{Mailing Lists}) in a post to an
605 unsubscribed list. When making original posts to a mailing list you are
606 not subscribed to, you have to type in a @samp{Mail-Followup-To:} header
607 by hand. The contents, usually, are the addresses of the list and your
608 own address. This function inserts such a header automatically. It
609 fetches the contents of the @samp{To:} header in the current mail
610 buffer, and appends the current @code{user-mail-address}.
612 If the optional argument @code{include-cc} is non-@code{nil}, the
613 addresses in the @samp{Cc:} header are also put into the
614 @samp{Mail-Followup-To:} header.
618 @subsection Commands to change headers
624 @findex message-sort-headers
625 @vindex message-header-format-alist
626 Sort headers according to @code{message-header-format-alist}
627 (@code{message-sort-headers}).
631 @findex message-insert-to
632 Insert a @code{To} header that contains the @code{Reply-To} or
633 @code{From} header of the message you're following up
634 (@code{message-insert-to}).
638 @findex message-insert-newsgroups
639 Insert a @code{Newsgroups} header that reflects the @code{Followup-To}
640 or @code{Newsgroups} header of the article you're replying to
641 (@code{message-insert-newsgroups}).
645 @findex message-to-list-only
646 Send a message to the list only. Remove all addresses but the list
647 address from @code{To:} and @code{Cc:} headers.
651 @findex message-insert-disposition-notification-to
652 Insert a request for a disposition
653 notification. (@code{message-insert-disposition-notification-to}).
654 This means that if the recipient support RFC 2298 she might send you a
655 notification that she received the message.
657 @item M-x message-insert-importance-high
658 @kindex M-x message-insert-importance-high
659 @findex message-insert-importance-high
661 Insert an @samp{Importance} header with a value of @samp{high},
662 deleting headers if necessary.
664 @item M-x message-insert-importance-low
665 @kindex M-x message-insert-importance-low
666 @findex message-insert-importance-low
668 Insert an @samp{Importance} header with a value of @samp{low}, deleting
669 headers if necessary.
673 @findex message-change-subject
675 Change the current @samp{Subject} header. Ask for new @samp{Subject}
676 header and append @samp{(was: <Old Subject>)}. The old subject can be
677 stripped on replying, see @code{message-subject-trailing-was-query}
678 (@pxref{Message Headers}).
682 @findex message-cross-post-followup-to
683 @vindex message-cross-post-default
686 Ask for an additional @samp{Newsgroups} and @samp{FollowUp-To} for a
687 cross-post. @code{message-cross-post-followup-to} mangles
688 @samp{FollowUp-To} and @samp{Newsgroups} header to point to group.
689 If @code{message-cross-post-default} is @code{nil} or if called with a
690 prefix-argument @samp{Follow-Up} is set, but the message is not
695 @findex message-reduce-to-to-cc
696 Replace contents of @samp{To} header with contents of @samp{Cc} or
701 @findex message-insert-wide-reply
702 Insert @samp{To} and @samp{Cc} headers as if you were doing a wide
707 @findex message-add-archive-header
708 @vindex message-archive-header
709 @vindex message-archive-note
711 Insert @samp{X-No-Archive: Yes} in the header and a note in the body.
712 The header and the note can be customized using
713 @code{message-archive-header} and @code{message-archive-note}. When
714 called with a prefix argument, ask for a text to insert. If you don't
715 want the note in the body, set @code{message-archive-note} to
727 @findex message-goto-body
728 Move to the beginning of the body of the message
729 (@code{message-goto-body}).
733 @findex message-goto-signature
734 Move to the signature of the message (@code{message-goto-signature}).
738 @findex message-beginning-of-line
739 @vindex message-beginning-of-line
740 If at beginning of header value, go to beginning of line, else go to
741 beginning of header value. (The header value comes after the header
742 name and the colon.) This behavior can be disabled by toggling
743 the variable @code{message-beginning-of-line}.
755 @findex message-yank-original
756 Yank the message in the buffer @code{gnus-article-copy} into the message
757 buffer. Normally @code{gnus-article-copy} is what you are replying to
758 (@code{message-yank-original}).
762 @findex message-yank-buffer
763 Prompt for a buffer name and yank the contents of that buffer into the
764 message buffer (@code{message-yank-buffer}).
768 @findex message-fill-yanked-message
769 Fill the yanked message (@code{message-fill-yanked-message}). Warning:
770 Can severely mess up the yanked text if its quoting conventions are
771 strange. You'll quickly get a feel for when it's safe, though. Anyway,
772 just remember that @kbd{C-x u} (@code{undo}) is available and you'll be
777 @findex message-insert-signature
778 Insert a signature at the end of the buffer
779 (@code{message-insert-signature}).
783 @findex message-insert-headers
784 Insert the message headers (@code{message-insert-headers}).
788 @findex message-mark-inserted-region
789 Mark some region in the current article with enclosing tags. See
790 @code{message-mark-insert-begin} and @code{message-mark-insert-end}.
791 When called with a prefix argument, use slrn style verbatim marks
792 (@samp{#v+} and @samp{#v-}).
796 @findex message-mark-insert-file
797 Insert a file in the current article with enclosing tags.
798 See @code{message-mark-insert-begin} and @code{message-mark-insert-end}.
799 When called with a prefix argument, use slrn style verbatim marks
800 (@samp{#v+} and @samp{#v-}).
812 Message is a @acronym{MIME}-compliant posting agent. The user generally
813 doesn't have to do anything to make the @acronym{MIME} happen---Message will
814 automatically add the @code{Content-Type} and
815 @code{Content-Transfer-Encoding} headers.
817 The most typical thing users want to use the multipart things in
818 @acronym{MIME} for is to add ``attachments'' to mail they send out.
819 This can be done with the @kbd{C-c C-a} command, which will prompt for
820 a file name and a @acronym{MIME} type.
822 @vindex mml-dnd-protocol-alist
823 @vindex mml-dnd-attach-options
824 If your Emacs supports drag and drop, you can also drop the file in the
825 Message buffer. The variable @code{mml-dnd-protocol-alist} specifies
826 what kind of action is done when you drop a file into the Message
827 buffer. The variable @code{mml-dnd-attach-options} controls which
828 @acronym{MIME} options you want to specify when dropping a file. If it
829 is a list, valid members are @code{type}, @code{description} and
830 @code{disposition}. @code{disposition} implies @code{type}. If it is
831 @code{nil}, don't ask for options. If it is @code{t}, ask the user
832 whether or not to specify options.
834 You can also create arbitrarily complex multiparts using the @acronym{MML}
835 language (@pxref{Composing, , Composing, emacs-mime, The Emacs MIME
841 @cindex internationalized domain names
842 @cindex non-ascii domain names
844 Message is a @acronym{IDNA}-compliant posting agent. The user
845 generally doesn't have to do anything to make the @acronym{IDNA}
846 happen---Message will encode non-@acronym{ASCII} domain names in @code{From},
847 @code{To}, and @code{Cc} headers automatically.
849 Until @acronym{IDNA} becomes more well known, Message queries you
850 whether @acronym{IDNA} encoding of the domain name really should
851 occur. Some users might not be aware that domain names can contain
852 non-@acronym{ASCII} now, so this gives them a safety net if they accidently
853 typed a non-@acronym{ASCII} domain name.
855 @vindex message-use-idna
856 The @code{message-use-idna} variable control whether @acronym{IDNA} is
857 used. If the variable is @code{nil} no @acronym{IDNA} encoding will
858 ever happen, if it is set to the symbol @code{ask} the user will be
859 queried, and if set to @code{t} @acronym{IDNA} encoding happens
860 automatically (the default).
862 @findex message-idna-to-ascii-rhs
863 If you want to experiment with the @acronym{IDNA} encoding, you can
864 invoke @kbd{M-x message-idna-to-ascii-rhs RET} in the message buffer
865 to have the non-@acronym{ASCII} domain names encoded while you edit
868 Note that you must have @uref{http://www.gnu.org/software/libidn/, GNU
869 Libidn} installed in order to use this functionality.
881 Using the @acronym{MML} language, Message is able to create digitally
882 signed and digitally encrypted messages. Message (or rather
883 @acronym{MML}) currently support @acronym{PGP} (RFC 1991),
884 @acronym{PGP/MIME} (RFC 2015/3156) and @acronym{S/MIME}. Instructing
885 @acronym{MML} to perform security operations on a @acronym{MIME} part is
886 done using the @kbd{C-c C-m s} key map for signing and the @kbd{C-c C-m
887 c} key map for encryption, as follows.
893 @findex mml-secure-message-sign-smime
895 Digitally sign current message using @acronym{S/MIME}.
899 @findex mml-secure-message-sign-pgp
901 Digitally sign current message using @acronym{PGP}.
905 @findex mml-secure-message-sign-pgpmime
907 Digitally sign current message using @acronym{PGP/MIME}.
911 @findex mml-secure-message-encrypt-smime
913 Digitally encrypt current message using @acronym{S/MIME}.
917 @findex mml-secure-message-encrypt-pgp
919 Digitally encrypt current message using @acronym{PGP}.
923 @findex mml-secure-message-encrypt-pgpmime
925 Digitally encrypt current message using @acronym{PGP/MIME}.
929 @findex mml-unsecure-message
930 Remove security related @acronym{MML} tags from message.
934 These commands do not immediately sign or encrypt the message, they
935 merely insert the proper @acronym{MML} secure tag to instruct the
936 @acronym{MML} engine to perform that operation when the message is
937 actually sent. They may perform other operations too, such as locating
938 and retrieving a @acronym{S/MIME} certificate of the person you wish to
939 send encrypted mail to. When the mml parsing engine converts your
940 @acronym{MML} into a properly encoded @acronym{MIME} message, the secure
941 tag will be replaced with either a part or a multipart tag. If your
942 message contains other mml parts, a multipart tag will be used; if no
943 other parts are present in your message a single part tag will be used.
944 This way, message mode will do the Right Thing (TM) with
945 signed/encrypted multipart messages.
947 Since signing and especially encryption often is used when sensitive
948 information is sent, you may want to have some way to ensure that your
949 mail is actually signed or encrypted. After invoking the above
950 sign/encrypt commands, it is possible to preview the raw article by
951 using @kbd{C-u C-c RET P} (@code{mml-preview}). Then you can
952 verify that your long rant about what your ex-significant other or
953 whomever actually did with that funny looking person at that strange
954 party the other night, actually will be sent encrypted.
956 @emph{Note!} Neither @acronym{PGP/MIME} nor @acronym{S/MIME} encrypt/signs
957 RFC822 headers. They only operate on the @acronym{MIME} object. Keep this
958 in mind before sending mail with a sensitive Subject line.
960 By default, when encrypting a message, Gnus will use the
961 ``signencrypt'' mode, which means the message is both signed and
962 encrypted. If you would like to disable this for a particular
963 message, give the @code{mml-secure-message-encrypt-*} command a prefix
964 argument, e.g., @kbd{C-u C-c C-m c p}.
966 Actually using the security commands above is not very difficult. At
967 least not compared with making sure all involved programs talk with each
968 other properly. Thus, we now describe what external libraries or
969 programs are required to make things work, and some small general hints.
971 @subsection Using S/MIME
973 @emph{Note!} This section assume you have a basic familiarity with
974 modern cryptography, @acronym{S/MIME}, various PKCS standards, OpenSSL and
977 The @acronym{S/MIME} support in Message (and @acronym{MML}) require
978 OpenSSL. OpenSSL performs the actual @acronym{S/MIME} sign/encrypt
979 operations. OpenSSL can be found at @uref{http://www.openssl.org/}.
980 OpenSSL 0.9.6 and later should work. Version 0.9.5a cannot extract mail
981 addresses from certificates, and it insert a spurious CR character into
982 @acronym{MIME} separators so you may wish to avoid it if you would like
983 to avoid being regarded as someone who send strange mail. (Although by
984 sending @acronym{S/MIME} messages you've probably already lost that
987 To be able to send encrypted mail, a personal certificate is not
988 required. Message (@acronym{MML}) need a certificate for the person to whom you
989 wish to communicate with though. You're asked for this when you type
990 @kbd{C-c C-m c s}. Currently there are two ways to retrieve this
991 certificate, from a local file or from DNS. If you chose a local
992 file, it need to contain a X.509 certificate in @acronym{PEM} format.
993 If you chose DNS, you're asked for the domain name where the
994 certificate is stored, the default is a good guess. To my belief,
995 Message (@acronym{MML}) is the first mail agent in the world to support
996 retrieving @acronym{S/MIME} certificates from DNS, so you're not
997 likely to find very many certificates out there. At least there
998 should be one, stored at the domain @code{simon.josefsson.org}. LDAP
999 is a more popular method of distributing certificates, support for it
1000 is planned. (Meanwhile, you can use @code{ldapsearch} from the
1001 command line to retrieve a certificate into a file and use it.)
1003 As for signing messages, OpenSSL can't perform signing operations
1004 without some kind of configuration. Especially, you need to tell it
1005 where your private key and your certificate is stored. @acronym{MML}
1006 uses an Emacs interface to OpenSSL, aptly named @code{smime.el}, and it
1007 contain a @code{custom} group used for this configuration. So, try
1008 @kbd{M-x customize-group RET smime RET} and look around.
1010 Currently there is no support for talking to a CA (or RA) to create
1011 your own certificate. None is planned either. You need to do this
1012 manually with OpenSSL or using some other program. I used Netscape
1013 and got a free @acronym{S/MIME} certificate from one of the big CA's on the
1014 net. Netscape is able to export your private key and certificate in
1015 PKCS #12 format. Use OpenSSL to convert this into a plain X.509
1016 certificate in PEM format as follows.
1019 $ openssl pkcs12 -in ns.p12 -clcerts -nodes > key+cert.pem
1022 The @file{key+cert.pem} file should be pointed to from the
1023 @code{smime-keys} variable. You should now be able to send signed mail.
1025 @emph{Note!} Your private key is now stored unencrypted in the file,
1026 so take care in handling it. Storing encrypted keys on the disk are
1027 supported, and Gnus will ask you for a passphrase before invoking
1028 OpenSSL. Read the OpenSSL documentation for how to achieve this. If
1029 you use unencrypted keys (e.g., if they are on a secure storage, or if
1030 you are on a secure single user machine) simply press @code{RET} at
1031 the passphrase prompt.
1033 @subsection Using PGP/MIME
1035 @acronym{PGP/MIME} requires an external OpenPGP implementation, such
1036 as @uref{http://www.gnupg.org/, GNU Privacy Guard}. Pre-OpenPGP
1037 implementations such as PGP 2.x and PGP 5.x are also supported. One
1038 Emacs interface to the PGP implementations, PGG (@pxref{Top, ,PGG,
1039 pgg, PGG Manual}), is included, but Mailcrypt and Florian Weimer's
1040 @code{gpg.el} are also supported.
1042 @vindex gpg-temp-directory
1043 Note, if you are using the @code{gpg.el} you must make sure that the
1044 directory specified by @code{gpg-temp-directory} have permissions
1047 Creating your own key is described in detail in the documentation of
1048 your PGP implementation, so we refer to it.
1050 If you have imported your old PGP 2.x key into GnuPG, and want to send
1051 signed and encrypted messages to your fellow PGP 2.x users, you'll
1052 discover that the receiver cannot understand what you send. One
1053 solution is to use PGP 2.x instead (i.e., if you use @code{pgg}, set
1054 @code{pgg-default-scheme} to @code{pgp}). If you do want to use
1055 GnuPG, you can use a compatibility script called @code{gpg-2comp}
1057 @uref{http://muppet.faveve.uni-stuttgart.de/~gero/gpg-2comp/}. You
1058 could also convince your fellow PGP 2.x users to convert to GnuPG.
1059 @vindex mml-signencrypt-style-alist
1060 As a final workaround, you can make the sign and encryption work in
1061 two steps; separately sign, then encrypt a message. If you would like
1062 to change this behavior you can customize the
1063 @code{mml-signencrypt-style-alist} variable. For example:
1066 (setq mml-signencrypt-style-alist '(("smime" separate)
1068 ("pgpauto" separate)
1069 ("pgpmime" separate)))
1072 This causes to sign and encrypt in two passes, thus generating a
1073 message that can be understood by PGP version 2.
1075 (Refer to @uref{http://www.gnupg.org/gph/en/pgp2x.html} for more
1076 information about the problem.)
1078 @node Various Commands
1079 @section Various Commands
1085 @findex message-caesar-buffer-body
1086 Caesar rotate (aka. rot13) the current message
1087 (@code{message-caesar-buffer-body}). If narrowing is in effect, just
1088 rotate the visible portion of the buffer. A numerical prefix says how
1089 many places to rotate the text. The default is 13.
1093 @findex message-elide-region
1094 @vindex message-elide-ellipsis
1095 Elide the text between point and mark (@code{message-elide-region}).
1096 The text is killed and replaced with the contents of the variable
1097 @code{message-elide-ellipsis}. The default value is to use an ellipsis
1102 @findex message-kill-address
1103 Kill the address under point.
1107 @findex message-kill-to-signature
1108 Kill all the text up to the signature, or if that's missing, up to the
1109 end of the message (@code{message-kill-to-signature}).
1113 @findex message-delete-not-region
1114 Delete all text in the body of the message that is outside the region
1115 (@code{message-delete-not-region}).
1119 @findex message-newline-and-reformat
1120 Insert four newlines, and then reformat if inside quoted text.
1125 > This is some quoted text. And here's more quoted text.
1128 If point is before @samp{And} and you press @kbd{M-RET}, you'll get:
1131 > This is some quoted text.
1135 > And here's more quoted text.
1138 @samp{*} says where point will be placed.
1142 @findex message-rename-buffer
1143 Rename the buffer (@code{message-rename-buffer}). If given a prefix,
1144 prompt for a new buffer name.
1149 @vindex message-tab-body-function
1150 If non-@code{nil} execute the function specified in
1151 @code{message-tab-body-function}. Otherwise use the function bound to
1152 @kbd{TAB} in @code{text-mode-map} or @code{global-map}.
1163 @findex message-send-and-exit
1164 Send the message and bury the current buffer
1165 (@code{message-send-and-exit}).
1169 @findex message-send
1170 Send the message (@code{message-send}).
1174 @findex message-dont-send
1175 Bury the message buffer and exit (@code{message-dont-send}).
1179 @findex message-kill-buffer
1180 Kill the message buffer and exit (@code{message-kill-buffer}). It will
1181 delete the message frame if it has been created exclusively for the
1182 message buffer. If the option
1183 @code{message-kill-buffer-and-remove-file} is non-@code{nil} and the
1184 backup file has been created for the message buffer, it will also remove
1185 the file after prompting to the user.
1189 @findex message-mimic-kill-buffer
1190 @vindex message-kill-buffer-and-remove-file
1191 This is an imitation for @code{kill-buffer}
1192 (@code{message-mimic-kill-buffer}). It dynamically binds the variable
1193 @code{message-kill-buffer-and-remove-file} to @code{nil} and calls the
1194 function @code{message-kill-buffer}.
1201 @section Mail Aliases
1202 @cindex mail aliases
1205 @vindex message-mail-alias-type
1206 The @code{message-mail-alias-type} variable controls what type of mail
1207 alias expansion to use. Currently only one form is supported---Message
1208 uses @code{mailabbrev} to handle mail aliases. If this variable is
1209 @code{nil}, no mail alias expansion will be performed.
1211 @code{mailabbrev} works by parsing the @file{/etc/mailrc} and
1212 @file{~/.mailrc} files. These files look like:
1215 alias lmi "Lars Magne Ingebrigtsen <larsi@@ifi.uio.no>"
1216 alias ding "ding@@ifi.uio.no (ding mailing list)"
1219 After adding lines like this to your @file{~/.mailrc} file, you should
1220 be able to just write @samp{lmi} in the @code{To} or @code{Cc} (and so
1221 on) headers and press @kbd{SPC} to expand the alias.
1223 No expansion will be performed upon sending of the message---all
1224 expansions have to be done explicitly.
1230 @findex ispell-message
1232 There are two popular ways to have Emacs spell-check your messages:
1233 @code{ispell} and @code{flyspell}. @code{ispell} is the older and
1234 probably more popular package. You typically first write the message,
1235 and then run the entire thing through @code{ispell} and fix all the
1236 typos. To have this happen automatically when you send a message, put
1237 something like the following in your @file{.emacs} file:
1240 (add-hook 'message-send-hook 'ispell-message)
1243 @vindex ispell-message-dictionary-alist
1244 If you're in the habit of writing in different languages, this can be
1245 controlled by the @code{ispell-message-dictionary-alist} variable:
1248 (setq ispell-message-dictionary-alist
1249 '(("^Newsgroups:.*\\bde\\." . "deutsch8")
1250 (".*" . "default")))
1253 @code{ispell} depends on having the external @samp{ispell} command
1256 The other popular method is using @code{flyspell}. This package checks
1257 your spelling while you're writing, and marks any mis-spelled words in
1260 To use @code{flyspell}, put something like the following in your
1264 (defun my-message-setup-routine ()
1266 (add-hook 'message-setup-hook 'my-message-setup-routine)
1269 @code{flyspell} depends on having the external @samp{ispell} command
1277 * Message Headers:: General message header stuff.
1278 * Mail Headers:: Customizing mail headers.
1279 * Mail Variables:: Other mail variables.
1280 * News Headers:: Customizing news headers.
1281 * News Variables:: Other news variables.
1282 * Insertion Variables:: Customizing how things are inserted.
1283 * Various Message Variables:: Other message variables.
1284 * Sending Variables:: Variables for sending.
1285 * Message Buffers:: How Message names its buffers.
1286 * Message Actions:: Actions to be performed when exiting.
1290 @node Message Headers
1291 @section Message Headers
1293 Message is quite aggressive on the message generation front. It has to
1294 be---it's a combined news and mail agent. To be able to send combined
1295 messages, it has to generate all headers itself (instead of letting the
1296 mail/news system do it) to ensure that mail and news copies of messages
1297 look sufficiently similar.
1301 @item message-generate-headers-first
1302 @vindex message-generate-headers-first
1303 If @code{t}, generate all required headers before starting to
1304 compose the message. This can also be a list of headers to generate:
1307 (setq message-generate-headers-first
1311 @vindex message-required-headers
1312 The variables @code{message-required-headers},
1313 @code{message-required-mail-headers} and
1314 @code{message-required-news-headers} specify which headers are
1317 Note that some headers will be removed and re-generated before posting,
1318 because of the variable @code{message-deletable-headers} (see below).
1320 @item message-draft-headers
1321 @vindex message-draft-headers
1322 When running Message from Gnus, the message buffers are associated
1323 with a draft group. @code{message-draft-headers} says which headers
1324 should be generated when a draft is written to the draft group.
1326 @item message-from-style
1327 @vindex message-from-style
1328 Specifies how @code{From} headers should look. There are four valid
1333 Just the address---@samp{king@@grassland.com}.
1336 @samp{king@@grassland.com (Elvis Parsley)}.
1339 @samp{Elvis Parsley <king@@grassland.com>}.
1342 Look like @code{angles} if that doesn't require quoting, and
1343 @code{parens} if it does. If even @code{parens} requires quoting, use
1344 @code{angles} anyway.
1348 @item message-deletable-headers
1349 @vindex message-deletable-headers
1350 Headers in this list that were previously generated by Message will be
1351 deleted before posting. Let's say you post an article. Then you decide
1352 to post it again to some other group, you naughty boy, so you jump back
1353 to the @code{*post-buf*} buffer, edit the @code{Newsgroups} line, and
1354 ship it off again. By default, this variable makes sure that the old
1355 generated @code{Message-ID} is deleted, and a new one generated. If
1356 this isn't done, the entire empire would probably crumble, anarchy would
1357 prevail, and cats would start walking on two legs and rule the world.
1360 @item message-default-headers
1361 @vindex message-default-headers
1362 This string is inserted at the end of the headers in all message
1365 @item message-subject-re-regexp
1366 @vindex message-subject-re-regexp
1370 Responses to messages have subjects that start with @samp{Re: }. This
1371 is @emph{not} an abbreviation of the English word ``response'', but is
1372 Latin, and means ``in response to''. Some illiterate nincompoops have
1373 failed to grasp this fact, and have ``internationalized'' their software
1374 to use abominations like @samp{Aw: } (``antwort'') or @samp{Sv: }
1375 (``svar'') instead, which is meaningless and evil. However, you may
1376 have to deal with users that use these evil tools, in which case you may
1377 set this variable to a regexp that matches these prefixes. Myself, I
1378 just throw away non-compliant mail.
1380 Here's an example of a value to deal with these headers when
1381 responding to a message:
1384 (setq message-subject-re-regexp
1389 "[Aa][Nn][Tt][Ww]\\.?\\|" ; antw
1391 "[Ff][Ww][Dd]?\\|" ; fwd
1392 "[Oo][Dd][Pp]\\|" ; odp
1394 "[Rr][\311\351][Ff]\\.?\\|" ; ref
1397 "\\(\\[[0-9]*\\]\\)"
1404 @item message-subject-trailing-was-query
1405 @vindex message-subject-trailing-was-query
1406 @vindex message-subject-trailing-was-ask-regexp
1407 @vindex message-subject-trailing-was-regexp
1408 Controls what to do with trailing @samp{(was: <old subject>)} in subject
1409 lines. If @code{nil}, leave the subject unchanged. If it is the symbol
1410 @code{ask}, query the user what do do. In this case, the subject is
1411 matched against @code{message-subject-trailing-was-ask-regexp}. If
1412 @code{message-subject-trailing-was-query} is @code{t}, always strip the
1413 trailing old subject. In this case,
1414 @code{message-subject-trailing-was-regexp} is used.
1416 @item message-alternative-emails
1417 @vindex message-alternative-emails
1418 Regexp matching alternative email addresses. The first address in the
1419 To, Cc or From headers of the original article matching this variable is
1420 used as the From field of outgoing messages, replacing the default From
1423 For example, if you have two secondary email addresses john@@home.net
1424 and john.doe@@work.com and want to use them in the From field when
1425 composing a reply to a message addressed to one of them, you could set
1426 this variable like this:
1429 (setq message-alternative-emails
1430 (regexp-opt '("john@@home.net" "john.doe@@work.com")))
1433 This variable has precedence over posting styles and anything that runs
1434 off @code{message-setup-hook}.
1436 @item message-allow-no-recipients
1437 @vindex message-allow-no-recipients
1438 Specifies what to do when there are no recipients other than
1439 @code{Gcc} or @code{Fcc}. If it is @code{always}, the posting is
1440 allowed. If it is @code{never}, the posting is not allowed. If it is
1441 @code{ask} (the default), you are prompted.
1443 @item message-hidden-headers
1444 @vindex message-hidden-headers
1445 A regexp, a list of regexps, or a list where the first element is
1446 @code{not} and the rest are regexps. It says which headers to keep
1447 hidden when composing a message.
1450 (setq message-hidden-headers
1451 '(not "From" "Subject" "To" "Cc" "Newsgroups"))
1454 Headers are hidden using narrowing, you can use @kbd{M-x widen} to
1455 expose them in the buffer.
1457 @item message-header-synonyms
1458 @vindex message-header-synonyms
1459 A list of lists of header synonyms. E.g., if this list contains a
1460 member list with elements @code{Cc} and @code{To}, then
1461 @code{message-carefully-insert-headers} will not insert a @code{To}
1462 header when the message is already @code{Cc}ed to the recipient.
1468 @section Mail Headers
1471 @item message-required-mail-headers
1472 @vindex message-required-mail-headers
1473 @xref{News Headers}, for the syntax of this variable. It is
1474 @code{(From Date Subject (optional . In-Reply-To) Message-ID Lines
1475 (optional . User-Agent))} by default.
1477 @item message-ignored-mail-headers
1478 @vindex message-ignored-mail-headers
1479 Regexp of headers to be removed before mailing. The default is
1480 @samp{^[GF]cc:\\|^Resent-Fcc:\\|^Xref:\\|^X-Draft-From:}.
1482 @item message-default-mail-headers
1483 @vindex message-default-mail-headers
1484 This string is inserted at the end of the headers in all message
1485 buffers that are initialized as mail.
1487 @item message-generate-hashcash
1488 @vindex message-generate-hashcash
1489 Boolean variable that indicate whether @samp{X-Hashcash} headers
1490 should be computed for the message. @xref{Hashcash, ,Hashcash,gnus,
1496 @node Mail Variables
1497 @section Mail Variables
1500 @item message-send-mail-function
1501 @vindex message-send-mail-function
1502 @findex message-send-mail-with-sendmail
1503 @findex message-send-mail-with-mh
1504 @findex message-send-mail-with-qmail
1505 @findex message-smtpmail-send-it
1506 @findex smtpmail-send-it
1507 @findex feedmail-send-it
1508 Function used to send the current buffer as mail. The default is
1509 @code{message-send-mail-with-sendmail}, or @code{smtpmail-send-it}
1510 according to the system. Other valid values include
1511 @code{message-send-mail-with-mh}, @code{message-send-mail-with-qmail},
1512 @code{message-smtpmail-send-it} and @code{feedmail-send-it}.
1514 @item message-mh-deletable-headers
1515 @vindex message-mh-deletable-headers
1516 Most versions of MH doesn't like being fed messages that contain the
1517 headers in this variable. If this variable is non-@code{nil} (which is
1518 the default), these headers will be removed before mailing when sending
1519 messages via MH. Set it to @code{nil} if your MH can handle these
1522 @item message-qmail-inject-program
1523 @vindex message-qmail-inject-program
1525 Location of the qmail-inject program.
1527 @item message-qmail-inject-args
1528 @vindex message-qmail-inject-args
1529 Arguments passed to qmail-inject programs.
1530 This should be a list of strings, one string for each argument. It
1531 may also be a function.
1533 For e.g., if you wish to set the envelope sender address so that bounces
1534 go to the right place or to deal with listserv's usage of that address, you
1535 might set this variable to @code{'("-f" "you@@some.where")}.
1537 @item message-sendmail-f-is-evil
1538 @vindex message-sendmail-f-is-evil
1540 Non-@code{nil} means don't add @samp{-f username} to the sendmail
1541 command line. Doing so would be even more evil than leaving it out.
1543 @item message-sendmail-envelope-from
1544 @vindex message-sendmail-envelope-from
1545 When @code{message-sendmail-f-is-evil} is @code{nil}, this specifies
1546 the address to use in the @acronym{SMTP} envelope. If it is
1547 @code{nil}, use @code{user-mail-address}. If it is the symbol
1548 @code{header}, use the @samp{From} header of the message.
1550 @item message-mailer-swallows-blank-line
1551 @vindex message-mailer-swallows-blank-line
1552 Set this to non-@code{nil} if the system's mailer runs the header and
1553 body together. (This problem exists on SunOS 4 when sendmail is run
1554 in remote mode.) The value should be an expression to test whether
1555 the problem will actually occur.
1557 @item message-send-mail-partially-limit
1558 @vindex message-send-mail-partially-limit
1559 @cindex split large message
1560 The limitation of messages sent as message/partial. The lower bound
1561 of message size in characters, beyond which the message should be sent
1562 in several parts. If it is @code{nil}, the size is unlimited.
1568 @section News Headers
1570 @vindex message-required-news-headers
1571 @code{message-required-news-headers} a list of header symbols. These
1572 headers will either be automatically generated, or, if that's
1573 impossible, they will be prompted for. The following symbols are valid:
1579 @findex user-full-name
1580 @findex user-mail-address
1581 This required header will be filled out with the result of the
1582 @code{message-make-from} function, which depends on the
1583 @code{message-from-style}, @code{user-full-name},
1584 @code{user-mail-address} variables.
1588 This required header will be prompted for if not present already.
1592 This required header says which newsgroups the article is to be posted
1593 to. If it isn't present already, it will be prompted for.
1596 @cindex organization
1597 @vindex message-user-organization
1598 @vindex message-user-organization-file
1599 This optional header will be filled out depending on the
1600 @code{message-user-organization} variable.
1601 @code{message-user-organization-file} will be used if this variable is
1602 @code{t}. This variable can also be a string (in which case this string
1603 will be used), or it can be a function (which will be called with no
1604 parameters and should return a string to be used).
1608 This optional header will be computed by Message.
1612 @vindex message-user-fqdn
1613 @vindex mail-host-address
1614 @vindex user-mail-address
1617 @cindex i-did-not-set--mail-host-address--so-tickle-me
1618 This required header will be generated by Message. A unique ID will be
1619 created based on the date, time, user name (for the local part) and the
1620 domain part. For the domain part, message will look (in this order) at
1621 @code{message-user-fqdn}, @code{system-name}, @code{mail-host-address}
1622 and @code{message-user-mail-address} (i.e. @code{user-mail-address})
1623 until a probably valid fully qualified domain name (FQDN) was found.
1627 This optional header will be filled out according to the
1628 @code{message-newsreader} local variable.
1631 This optional header is filled out using the @code{Date} and @code{From}
1632 header of the article being replied to.
1636 @vindex message-expires
1637 This extremely optional header will be inserted according to the
1638 @code{message-expires} variable. It is highly deprecated and shouldn't
1639 be used unless you know what you're doing.
1642 @cindex Distribution
1643 @vindex message-distribution-function
1644 This optional header is filled out according to the
1645 @code{message-distribution-function} variable. It is a deprecated and
1646 much misunderstood header.
1650 @vindex message-user-path
1651 This extremely optional header should probably never be used.
1652 However, some @emph{very} old servers require that this header is
1653 present. @code{message-user-path} further controls how this
1654 @code{Path} header is to look. If it is @code{nil}, use the server name
1655 as the leaf node. If it is a string, use the string. If it is neither
1656 a string nor @code{nil}, use the user name only. However, it is highly
1657 unlikely that you should need to fiddle with this variable at all.
1661 @cindex Mime-Version
1662 In addition, you can enter conses into this list. The @sc{car} of this cons
1663 should be a symbol. This symbol's name is the name of the header, and
1664 the @sc{cdr} can either be a string to be entered verbatim as the value of
1665 this header, or it can be a function to be called. This function should
1666 return a string to be inserted. For instance, if you want to insert
1667 @code{Mime-Version: 1.0}, you should enter @code{(Mime-Version . "1.0")}
1668 into the list. If you want to insert a funny quote, you could enter
1669 something like @code{(X-Yow . yow)} into the list. The function
1670 @code{yow} will then be called without any arguments.
1672 If the list contains a cons where the @sc{car} of the cons is
1673 @code{optional}, the @sc{cdr} of this cons will only be inserted if it is
1676 If you want to delete an entry from this list, the following Lisp
1677 snippet might be useful. Adjust accordingly if you want to remove
1681 (setq message-required-news-headers
1682 (delq 'Message-ID message-required-news-headers))
1685 Other variables for customizing outgoing news articles:
1689 @item message-syntax-checks
1690 @vindex message-syntax-checks
1691 Controls what syntax checks should not be performed on outgoing posts.
1692 To disable checking of long signatures, for instance, add
1695 (signature . disabled)
1704 Check the subject for commands.
1707 Insert a new @code{Sender} header if the @code{From} header looks odd.
1708 @item multiple-headers
1709 Check for the existence of multiple equal headers.
1712 Check for the existence of version and sendsys commands.
1714 Check whether the @code{Message-ID} looks ok.
1716 Check whether the @code{From} header seems nice.
1719 Check for too long lines.
1721 Check for invalid characters.
1723 Check for excessive size.
1725 Check whether there is any new text in the messages.
1727 Check the length of the signature.
1730 Check whether the article has an @code{Approved} header, which is
1731 something only moderators should include.
1733 Check whether the article is empty.
1734 @item invisible-text
1735 Check whether there is any invisible text in the buffer.
1737 Check whether any of the headers are empty.
1738 @item existing-newsgroups
1739 Check whether the newsgroups mentioned in the @code{Newsgroups} and
1740 @code{Followup-To} headers exist.
1741 @item valid-newsgroups
1742 Check whether the @code{Newsgroups} and @code{Followup-to} headers
1743 are valid syntactically.
1744 @item repeated-newsgroups
1745 Check whether the @code{Newsgroups} and @code{Followup-to} headers
1746 contains repeated group names.
1747 @item shorten-followup-to
1748 Check whether to add a @code{Followup-to} header to shorten the number
1749 of groups to post to.
1752 All these conditions are checked by default.
1754 @item message-ignored-news-headers
1755 @vindex message-ignored-news-headers
1756 Regexp of headers to be removed before posting. The default is@*
1757 @samp{^NNTP-Posting-Host:\\|^Xref:\\|^[BGF]cc:\\|^Resent-Fcc:\\|^X-Draft-From:}.
1759 @item message-default-news-headers
1760 @vindex message-default-news-headers
1761 This string is inserted at the end of the headers in all message
1762 buffers that are initialized as news.
1767 @node News Variables
1768 @section News Variables
1771 @item message-send-news-function
1772 @vindex message-send-news-function
1773 Function used to send the current buffer as news. The default is
1774 @code{message-send-news}.
1776 @item message-post-method
1777 @vindex message-post-method
1778 Gnusish @dfn{select method} (see the Gnus manual for details) used for
1779 posting a prepared news message.
1784 @node Insertion Variables
1785 @section Insertion Variables
1788 @item message-ignored-cited-headers
1789 @vindex message-ignored-cited-headers
1790 All headers that match this regexp will be removed from yanked
1791 messages. The default is @samp{.}, which means that all headers will be
1794 @item message-cite-prefix-regexp
1795 @vindex message-cite-prefix-regexp
1796 Regexp matching the longest possible citation prefix on a line.
1798 @item message-citation-line-function
1799 @vindex message-citation-line-function
1800 @cindex attribution line
1801 Function called to insert the citation line. The default is
1802 @code{message-insert-citation-line}, which will lead to citation lines
1806 Hallvard B Furuseth <h.b.furuseth@@usit.uio.no> writes:
1809 Point will be at the beginning of the body of the message when this
1812 Note that Gnus provides a feature where clicking on `writes:' hides the
1813 cited text. If you change the citation line too much, readers of your
1814 messages will have to adjust their Gnus, too. See the variable
1815 @code{gnus-cite-attribution-suffix}. @xref{Article Highlighting, ,
1816 Article Highlighting, gnus, The Gnus Manual}, for details.
1818 @item message-yank-prefix
1819 @vindex message-yank-prefix
1822 When you are replying to or following up an article, you normally want
1823 to quote the person you are answering. Inserting quoted text is done by
1824 @dfn{yanking}, and each line you yank will have
1825 @code{message-yank-prefix} prepended to it (except for quoted lines
1826 which use @code{message-yank-cited-prefix} and empty lines which use
1827 @code{message-yank-empty-prefix}). The default is @samp{> }.
1829 @item message-yank-cited-prefix
1830 @vindex message-yank-cited-prefix
1834 When yanking text from an article which contains already cited text,
1835 each line will be prefixed with the contents of this variable. The
1836 default is @samp{>}. See also @code{message-yank-prefix}.
1838 @item message-yank-empty-prefix
1839 @vindex message-yank-empty-prefix
1842 When yanking text from an article, each empty line will be prefixed with
1843 the contents of this variable. The default is @samp{>}. You can set
1844 this variable to an empty string to split the cited text into paragraphs
1845 automatically. See also @code{message-yank-prefix}.
1847 @item message-yank-add-new-references
1848 @vindex message-yank-add-new-references
1850 Non-@code{nil} means new IDs will be added to References field when an
1851 article is yanked by the command @code{message-yank-original}
1852 interactively. If it is a symbol @code{message-id-only}, only an ID
1853 from Message-ID field is used, otherwise IDs extracted from References,
1854 In-Reply-To and Message-ID fields are used.
1856 @item message-list-references-add-position
1857 @vindex message-list-references-add-position
1859 Integer value means position for adding to References field when an
1860 article is yanked by the command @code{message-yank-original}
1863 @item message-indentation-spaces
1864 @vindex message-indentation-spaces
1865 Number of spaces to indent yanked messages.
1867 @item message-cite-function
1868 @vindex message-cite-function
1869 @findex message-cite-original
1870 @findex sc-cite-original
1871 @findex message-cite-original-without-signature
1873 Function for citing an original message. The default is
1874 @code{message-cite-original}, which simply inserts the original message
1875 and prepends @samp{> } to each line.
1876 @code{message-cite-original-without-signature} does the same, but elides
1877 the signature. You can also set it to @code{sc-cite-original} to use
1880 @item message-suspend-font-lock-when-citing
1881 @vindex message-suspend-font-lock-when-citing
1882 If non-@code{nil}, suspend font-lock'ing while citing an original
1883 message. Some lazy demand-driven fontification tools (or Emacs itself)
1884 have a bug that they often miss a buffer to be fontified. It will
1885 mostly occur when Emacs prompts user for any inputs in the minibuffer.
1886 Setting this option to non-@code{nil} may help you to avoid unpleasant
1887 errors even if it is an add-hoc expedient.
1889 @item message-indent-citation-function
1890 @vindex message-indent-citation-function
1891 Function for modifying a citation just inserted in the mail buffer.
1892 This can also be a list of functions. Each function can find the
1893 citation between @code{(point)} and @code{(mark t)}. And each function
1894 should leave point and mark around the citation text as modified.
1896 @item message-mark-insert-begin
1897 @vindex message-mark-insert-begin
1898 String to mark the beginning of some inserted text.
1900 @item message-mark-insert-end
1901 @vindex message-mark-insert-end
1902 String to mark the end of some inserted text.
1904 @item message-signature
1905 @vindex message-signature
1906 String to be inserted at the end of the message buffer. If @code{t}
1907 (which is the default), the @code{message-signature-file} file will be
1908 inserted instead. If a function, the result from the function will be
1909 used instead. If a form, the result from the form will be used instead.
1910 If this variable is @code{nil}, no signature will be inserted at all.
1912 @item message-signature-file
1913 @vindex message-signature-file
1914 File containing the signature to be inserted at the end of the buffer.
1915 The default is @file{~/.signature}.
1917 @item message-signature-insert-empty-line
1918 @vindex message-signature-insert-empty-line
1919 If @code{t} (the default value) an empty line is inserted before the
1920 signature separator.
1924 Note that RFC1036bis says that a signature should be preceded by the three
1925 characters @samp{-- } on a line by themselves. This is to make it
1926 easier for the recipient to automatically recognize and process the
1927 signature. So don't remove those characters, even though you might feel
1928 that they ruin your beautiful design, like, totally.
1930 Also note that no signature should be more than four lines long.
1931 Including @acronym{ASCII} graphics is an efficient way to get
1932 everybody to believe that you are silly and have nothing important to
1936 @node Various Message Variables
1937 @section Various Message Variables
1940 @item message-default-charset
1941 @vindex message-default-charset
1943 Symbol naming a @acronym{MIME} charset. Non-@acronym{ASCII}
1944 characters in messages are assumed to be encoded using this charset.
1945 The default is @code{nil}, which means ask the user. (This variable
1946 is used only on non-@sc{mule} Emacsen. @xref{Charset Translation, ,
1947 Charset Translation, emacs-mime, Emacs MIME Manual}, for details on
1948 the @sc{mule}-to-@acronym{MIME} translation process.
1950 @item message-signature-separator
1951 @vindex message-signature-separator
1952 Regexp matching the signature separator. It is @samp{^-- *$} by
1955 @item mail-header-separator
1956 @vindex mail-header-separator
1957 String used to separate the headers from the body. It is @samp{--text
1958 follows this line--} by default.
1960 @item message-directory
1961 @vindex message-directory
1962 Directory used by many mailey things. The default is @file{~/Mail/}.
1963 All other mail file variables are derived from @code{message-directory}.
1965 @item message-auto-save-directory
1966 @vindex message-auto-save-directory
1967 Directory where Message auto-saves buffers if Gnus isn't running. If
1968 @code{nil}, Message won't auto-save. The default is @file{~/Mail/drafts/}.
1970 @item message-signature-setup-hook
1971 @vindex message-signature-setup-hook
1972 Hook run when initializing the message buffer. It is run after the
1973 headers have been inserted but before the signature has been inserted.
1975 @item message-setup-hook
1976 @vindex message-setup-hook
1977 Hook run as the last thing when the message buffer has been initialized,
1978 but before yanked text is inserted.
1980 @item message-header-setup-hook
1981 @vindex message-header-setup-hook
1982 Hook called narrowed to the headers after initializing the headers.
1984 For instance, if you're running Gnus and wish to insert a
1985 @samp{Mail-Copies-To} header in all your news articles and all messages
1986 you send to mailing lists, you could do something like the following:
1989 (defun my-message-header-setup-hook ()
1990 (let ((group (or gnus-newsgroup-name "")))
1991 (when (or (message-fetch-field "newsgroups")
1992 (gnus-group-find-parameter group 'to-address)
1993 (gnus-group-find-parameter group 'to-list))
1994 (insert "Mail-Copies-To: never\n"))))
1996 (add-hook 'message-header-setup-hook
1997 'my-message-header-setup-hook)
2000 @item message-send-hook
2001 @vindex message-send-hook
2002 Hook run before sending messages.
2004 If you want to add certain headers before sending, you can use the
2005 @code{message-add-header} function in this hook. For instance:
2006 @findex message-add-header
2009 (add-hook 'message-send-hook 'my-message-add-content)
2010 (defun my-message-add-content ()
2011 (message-add-header "X-In-No-Sense: Nonsense")
2012 (message-add-header "X-Whatever: no"))
2015 This function won't add the header if the header is already present.
2017 @item message-send-mail-hook
2018 @vindex message-send-mail-hook
2019 Hook run before sending mail messages. This hook is run very late --
2020 just before the message is actually sent as mail.
2022 @item message-send-news-hook
2023 @vindex message-send-news-hook
2024 Hook run before sending news messages. This hook is run very late --
2025 just before the message is actually sent as news.
2027 @item message-sent-hook
2028 @vindex message-sent-hook
2029 Hook run after sending messages.
2031 @item message-cancel-hook
2032 @vindex message-cancel-hook
2033 Hook run when canceling news articles.
2035 @item message-mode-syntax-table
2036 @vindex message-mode-syntax-table
2037 Syntax table used in message mode buffers.
2039 @item message-cite-articles-with-x-no-archive
2040 @vindex message-cite-articles-with-x-no-archive
2041 If non-@code{nil}, don't strip quoted text from articles that have
2042 @samp{X-No-Archive} set. Even if this variable isn't set, you can
2043 undo the stripping by hitting the @code{undo} keystroke.
2045 @item message-strip-special-text-properties
2046 @vindex message-strip-special-text-properties
2047 Emacs has a number of special text properties which can break message
2048 composing in various ways. If this option is set, message will strip
2049 these properties from the message composition buffer. However, some
2050 packages requires these properties to be present in order to work. If
2051 you use one of these packages, turn this option off, and hope the
2052 message composition doesn't break too bad.
2054 @item message-send-method-alist
2055 @vindex message-send-method-alist
2057 Alist of ways to send outgoing messages. Each element has the form
2060 (@var{type} @var{predicate} @var{function})
2065 A symbol that names the method.
2068 A function called without any parameters to determine whether the
2069 message is a message of type @var{type}.
2072 A function to be called if @var{predicate} returns non-@code{nil}.
2073 @var{function} is called with one parameter---the prefix.
2077 ((news message-news-p message-send-via-news)
2078 (mail message-mail-p message-send-via-mail))
2086 @node Sending Variables
2087 @section Sending Variables
2091 @item message-fcc-handler-function
2092 @vindex message-fcc-handler-function
2093 A function called to save outgoing articles. This function will be
2094 called with the name of the file to store the article in. The default
2095 function is @code{message-output} which saves in Unix mailbox format.
2097 @item message-courtesy-message
2098 @vindex message-courtesy-message
2099 When sending combined messages, this string is inserted at the start of
2100 the mailed copy. If the string contains the format spec @samp{%s}, the
2101 newsgroups the article has been posted to will be inserted there. If
2102 this variable is @code{nil}, no such courtesy message will be added.
2103 The default value is @samp{"The following message is a courtesy copy of
2104 an article\\nthat has been posted to %s as well.\\n\\n"}.
2106 @item message-fcc-externalize-attachments
2107 @vindex message-fcc-externalize-attachments
2108 If @code{nil}, attach files as normal parts in Fcc copies; if it is
2109 non-@code{nil}, attach local files as external parts.
2111 @item message-interactive
2112 @vindex message-interactive
2113 If non-@code{nil} wait for and display errors when sending a message;
2114 if @code{nil} let the mailer mail back a message to report errors.
2119 @node Message Buffers
2120 @section Message Buffers
2122 Message will generate new buffers with unique buffer names when you
2123 request a message buffer. When you send the message, the buffer isn't
2124 normally killed off. Its name is changed and a certain number of old
2125 message buffers are kept alive.
2128 @item message-generate-new-buffers
2129 @vindex message-generate-new-buffers
2130 If non-@code{nil}, generate new buffers. The default is @code{t}. If
2131 this is a function, call that function with three parameters: The type,
2132 the to address and the group name. (Any of these may be @code{nil}.)
2133 The function should return the new buffer name.
2135 @item message-use-multi-frames
2136 @vindex message-use-multi-frames
2137 If non-@code{nil}, generate new frames. The default is @code{nil}.
2139 @item message-delete-frame-on-exit
2140 @vindex message-delete-frame-on-exit
2141 The @code{message-delete-frame-on-exit} variable says whether to delete
2142 the frame after sending the message or killing the message buffer. If it
2143 is @code{nil} (which is the default), don't delete the frame. If it is
2144 @code{ask}, ask wheter to delete the frame. If it is @code{t}, always
2147 @item message-max-buffers
2148 @vindex message-max-buffers
2149 This variable says how many old message buffers to keep. If there are
2150 more message buffers than this, the oldest buffer will be killed. The
2151 default is 10. If this variable is @code{nil}, no old message buffers
2152 will ever be killed.
2154 @item message-send-rename-function
2155 @vindex message-send-rename-function
2156 After sending a message, the buffer is renamed from, for instance,
2157 @samp{*reply to Lars*} to @samp{*sent reply to Lars*}. If you don't
2158 like this, set this variable to a function that renames the buffer in a
2159 manner you like. If you don't want to rename the buffer at all, you can
2163 (setq message-send-rename-function 'ignore)
2166 @item message-kill-buffer-on-exit
2167 @vindex message-kill-buffer-on-exit
2168 If non-@code{nil}, kill the buffer immediately on exit.
2170 @item message-kill-buffer-query-function
2171 @vindex message-kill-buffer-query-function
2172 @findex message-kill-buffer
2173 @findex message-mimic-kill-buffer
2174 Function used to prompt user whether to kill the message buffer when the
2175 command @code{message-kill-buffer} or @code{message-mimic-kill-buffer}
2176 is used. It defaults to @code{yes-or-no-p}. You may alter the value to
2177 @code{y-or-n-p}, @code{nnheader-Y-or-n-p}, etc. If it is @code{t}, the
2178 buffer will be killed without query.
2180 @item message-kill-buffer-and-remove-file
2181 @vindex message-kill-buffer-and-remove-file
2182 @findex message-kill-buffer
2183 @findex message-mimic-kill-buffer
2184 If it is non-@code{nil}, remove the backup file if it exists with a
2185 query to the user, after the message buffer is killed. Otherwise the
2186 file won't be removed. It defaults to @code{t}. However, it is treated
2187 as @code{nil} when the command `message-mimic-kill-buffer' is used.
2192 @node Message Actions
2193 @section Message Actions
2195 When Message is being used from a news/mail reader, the reader is likely
2196 to want to perform some task after the message has been sent. Perhaps
2197 return to the previous window configuration or mark an article as
2200 @vindex message-kill-actions
2201 @vindex message-postpone-actions
2202 @vindex message-exit-actions
2203 @vindex message-send-actions
2204 The user may exit from the message buffer in various ways. The most
2205 common is @kbd{C-c C-c}, which sends the message and exits. Other
2206 possibilities are @kbd{C-c C-s} which just sends the message, @kbd{C-c
2207 C-d} which postpones the message editing and buries the message buffer,
2208 and @kbd{C-c C-k} which kills the message buffer. Each of these actions
2209 have lists associated with them that contains actions to be executed:
2210 @code{message-send-actions}, @code{message-exit-actions},
2211 @code{message-postpone-actions}, and @code{message-kill-actions}.
2213 Message provides a function to interface with these lists:
2214 @code{message-add-action}. The first parameter is the action to be
2215 added, and the rest of the arguments are which lists to add this action
2216 to. Here's an example from Gnus:
2220 `(set-window-configuration ,(current-window-configuration))
2221 'exit 'postpone 'kill)
2224 This restores the Gnus window configuration when the message buffer is
2225 killed, postponed or exited.
2227 An @dfn{action} can be either: a normal function, or a list where the
2228 @sc{car} is a function and the @sc{cdr} is the list of arguments, or
2229 a form to be @code{eval}ed.
2233 @chapter Compatibility
2234 @cindex compatibility
2236 Message uses virtually only its own variables---older @code{mail-}
2237 variables aren't consulted. To force Message to take those variables
2238 into account, you can put the following in your @file{.emacs} file:
2241 (require 'messcompat)
2244 This will initialize many Message variables from the values in the
2245 corresponding mail variables.
2252 * Responses:: Standard rules for determining where responses go.
2259 To determine where a message is to go, the following algorithm is used
2264 A @dfn{reply} is when you want to respond @emph{just} to the person who
2265 sent the message via mail. There will only be one recipient. To
2266 determine who the recipient will be, the following headers are
2277 A @dfn{wide reply} is a mail response that includes @emph{all} entities
2278 mentioned in the message you are responded to. All mailboxes from the
2279 following headers will be concatenated to form the outgoing
2280 @code{To}/@code{Cc} headers:
2284 (unless there's a @code{Reply-To}, in which case that is used instead).
2291 If a @code{Mail-Copies-To} header is present, it will also be included
2292 in the list of mailboxes. If this header is @samp{never}, that means
2293 that the @code{From} (or @code{Reply-To}) mailbox will be suppressed.
2297 A @dfn{followup} is a response sent via news. The following headers
2298 (listed in order of precedence) determine where the response is to be
2309 If a @code{Mail-Copies-To} header is present, it will be used as the
2310 basis of the new @code{Cc} header, except if this header is