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.
790 See @code{message-mark-insert-begin} and @code{message-mark-insert-end}.
794 @findex message-mark-insert-file
795 Insert a file in the current article with enclosing tags.
796 See @code{message-mark-insert-begin} and @code{message-mark-insert-end}.
808 Message is a @acronym{MIME}-compliant posting agent. The user generally
809 doesn't have to do anything to make the @acronym{MIME} happen---Message will
810 automatically add the @code{Content-Type} and
811 @code{Content-Transfer-Encoding} headers.
813 The most typical thing users want to use the multipart things in
814 @acronym{MIME} for is to add ``attachments'' to mail they send out.
815 This can be done with the @kbd{C-c C-a} command, which will prompt for
816 a file name and a @acronym{MIME} type.
818 @vindex mml-dnd-protocol-alist
819 @vindex mml-dnd-attach-options
820 If your Emacs supports drag and drop, you can also drop the file in the
821 Message buffer. The variable @code{mml-dnd-protocol-alist} specifies
822 what kind of action is done when you drop a file into the Message
823 buffer. The variable @code{mml-dnd-attach-options} controls which
824 @acronym{MIME} options you want to specify when dropping a file. If it
825 is a list, valid members are @code{type}, @code{description} and
826 @code{disposition}. @code{disposition} implies @code{type}. If it is
827 @code{nil}, don't ask for options. If it is @code{t}, ask the user
828 whether or not to specify options.
830 You can also create arbitrarily complex multiparts using the @acronym{MML}
831 language (@pxref{Composing, , Composing, emacs-mime, The Emacs MIME
837 @cindex internationalized domain names
838 @cindex non-ascii domain names
840 Message is a @acronym{IDNA}-compliant posting agent. The user
841 generally doesn't have to do anything to make the @acronym{IDNA}
842 happen---Message will encode non-@acronym{ASCII} domain names in @code{From},
843 @code{To}, and @code{Cc} headers automatically.
845 Until @acronym{IDNA} becomes more well known, Message queries you
846 whether @acronym{IDNA} encoding of the domain name really should
847 occur. Some users might not be aware that domain names can contain
848 non-@acronym{ASCII} now, so this gives them a safety net if they accidently
849 typed a non-@acronym{ASCII} domain name.
851 @vindex message-use-idna
852 The @code{message-use-idna} variable control whether @acronym{IDNA} is
853 used. If the variable is @code{nil} no @acronym{IDNA} encoding will
854 ever happen, if it is set to the symbol @code{ask} the user will be
855 queried, and if set to @code{t} @acronym{IDNA} encoding happens
856 automatically (the default).
858 @findex message-idna-to-ascii-rhs
859 If you want to experiment with the @acronym{IDNA} encoding, you can
860 invoke @kbd{M-x message-idna-to-ascii-rhs RET} in the message buffer
861 to have the non-@acronym{ASCII} domain names encoded while you edit
864 Note that you must have @uref{http://www.gnu.org/software/libidn/, GNU
865 Libidn} installed in order to use this functionality.
877 Using the @acronym{MML} language, Message is able to create digitally
878 signed and digitally encrypted messages. Message (or rather
879 @acronym{MML}) currently support @acronym{PGP} (RFC 1991),
880 @acronym{PGP/MIME} (RFC 2015/3156) and @acronym{S/MIME}. Instructing
881 @acronym{MML} to perform security operations on a @acronym{MIME} part is
882 done using the @kbd{C-c C-m s} key map for signing and the @kbd{C-c C-m
883 c} key map for encryption, as follows.
889 @findex mml-secure-message-sign-smime
891 Digitally sign current message using @acronym{S/MIME}.
895 @findex mml-secure-message-sign-pgp
897 Digitally sign current message using @acronym{PGP}.
901 @findex mml-secure-message-sign-pgpmime
903 Digitally sign current message using @acronym{PGP/MIME}.
907 @findex mml-secure-message-encrypt-smime
909 Digitally encrypt current message using @acronym{S/MIME}.
913 @findex mml-secure-message-encrypt-pgp
915 Digitally encrypt current message using @acronym{PGP}.
919 @findex mml-secure-message-encrypt-pgpmime
921 Digitally encrypt current message using @acronym{PGP/MIME}.
925 @findex mml-unsecure-message
926 Remove security related @acronym{MML} tags from message.
930 These commands do not immediately sign or encrypt the message, they
931 merely insert the proper @acronym{MML} secure tag to instruct the
932 @acronym{MML} engine to perform that operation when the message is
933 actually sent. They may perform other operations too, such as locating
934 and retrieving a @acronym{S/MIME} certificate of the person you wish to
935 send encrypted mail to. When the mml parsing engine converts your
936 @acronym{MML} into a properly encoded @acronym{MIME} message, the secure
937 tag will be replaced with either a part or a multipart tag. If your
938 message contains other mml parts, a multipart tag will be used; if no
939 other parts are present in your message a single part tag will be used.
940 This way, message mode will do the Right Thing (TM) with
941 signed/encrypted multipart messages.
943 Since signing and especially encryption often is used when sensitive
944 information is sent, you may want to have some way to ensure that your
945 mail is actually signed or encrypted. After invoking the above
946 sign/encrypt commands, it is possible to preview the raw article by
947 using @kbd{C-u C-c RET P} (@code{mml-preview}). Then you can
948 verify that your long rant about what your ex-significant other or
949 whomever actually did with that funny looking person at that strange
950 party the other night, actually will be sent encrypted.
952 @emph{Note!} Neither @acronym{PGP/MIME} nor @acronym{S/MIME} encrypt/signs
953 RFC822 headers. They only operate on the @acronym{MIME} object. Keep this
954 in mind before sending mail with a sensitive Subject line.
956 By default, when encrypting a message, Gnus will use the
957 ``signencrypt'' mode, which means the message is both signed and
958 encrypted. If you would like to disable this for a particular
959 message, give the @code{mml-secure-message-encrypt-*} command a prefix
960 argument, e.g., @kbd{C-u C-c C-m c p}.
962 Actually using the security commands above is not very difficult. At
963 least not compared with making sure all involved programs talk with each
964 other properly. Thus, we now describe what external libraries or
965 programs are required to make things work, and some small general hints.
967 @subsection Using S/MIME
969 @emph{Note!} This section assume you have a basic familiarity with
970 modern cryptography, @acronym{S/MIME}, various PKCS standards, OpenSSL and
973 The @acronym{S/MIME} support in Message (and @acronym{MML}) require
974 OpenSSL. OpenSSL performs the actual @acronym{S/MIME} sign/encrypt
975 operations. OpenSSL can be found at @uref{http://www.openssl.org/}.
976 OpenSSL 0.9.6 and later should work. Version 0.9.5a cannot extract mail
977 addresses from certificates, and it insert a spurious CR character into
978 @acronym{MIME} separators so you may wish to avoid it if you would like
979 to avoid being regarded as someone who send strange mail. (Although by
980 sending @acronym{S/MIME} messages you've probably already lost that
983 To be able to send encrypted mail, a personal certificate is not
984 required. Message (@acronym{MML}) need a certificate for the person to whom you
985 wish to communicate with though. You're asked for this when you type
986 @kbd{C-c C-m c s}. Currently there are two ways to retrieve this
987 certificate, from a local file or from DNS. If you chose a local
988 file, it need to contain a X.509 certificate in @acronym{PEM} format.
989 If you chose DNS, you're asked for the domain name where the
990 certificate is stored, the default is a good guess. To my belief,
991 Message (@acronym{MML}) is the first mail agent in the world to support
992 retrieving @acronym{S/MIME} certificates from DNS, so you're not
993 likely to find very many certificates out there. At least there
994 should be one, stored at the domain @code{simon.josefsson.org}. LDAP
995 is a more popular method of distributing certificates, support for it
996 is planned. (Meanwhile, you can use @code{ldapsearch} from the
997 command line to retrieve a certificate into a file and use it.)
999 As for signing messages, OpenSSL can't perform signing operations
1000 without some kind of configuration. Especially, you need to tell it
1001 where your private key and your certificate is stored. @acronym{MML}
1002 uses an Emacs interface to OpenSSL, aptly named @code{smime.el}, and it
1003 contain a @code{custom} group used for this configuration. So, try
1004 @kbd{M-x customize-group RET smime RET} and look around.
1006 Currently there is no support for talking to a CA (or RA) to create
1007 your own certificate. None is planned either. You need to do this
1008 manually with OpenSSL or using some other program. I used Netscape
1009 and got a free @acronym{S/MIME} certificate from one of the big CA's on the
1010 net. Netscape is able to export your private key and certificate in
1011 PKCS #12 format. Use OpenSSL to convert this into a plain X.509
1012 certificate in PEM format as follows.
1015 $ openssl pkcs12 -in ns.p12 -clcerts -nodes > key+cert.pem
1018 The @file{key+cert.pem} file should be pointed to from the
1019 @code{smime-keys} variable. You should now be able to send signed mail.
1021 @emph{Note!} Your private key is now stored unencrypted in the file,
1022 so take care in handling it. Storing encrypted keys on the disk are
1023 supported, and Gnus will ask you for a passphrase before invoking
1024 OpenSSL. Read the OpenSSL documentation for how to achieve this. If
1025 you use unencrypted keys (e.g., if they are on a secure storage, or if
1026 you are on a secure single user machine) simply press @code{RET} at
1027 the passphrase prompt.
1029 @subsection Using PGP/MIME
1031 @acronym{PGP/MIME} requires an external OpenPGP implementation, such
1032 as @uref{http://www.gnupg.org/, GNU Privacy Guard}. Pre-OpenPGP
1033 implementations such as PGP 2.x and PGP 5.x are also supported. One
1034 Emacs interface to the PGP implementations, PGG (@pxref{Top, ,PGG,
1035 pgg, PGG Manual}), is included, but Mailcrypt and Florian Weimer's
1036 @code{gpg.el} are also supported.
1038 @vindex gpg-temp-directory
1039 Note, if you are using the @code{gpg.el} you must make sure that the
1040 directory specified by @code{gpg-temp-directory} have permissions
1043 Creating your own key is described in detail in the documentation of
1044 your PGP implementation, so we refer to it.
1046 If you have imported your old PGP 2.x key into GnuPG, and want to send
1047 signed and encrypted messages to your fellow PGP 2.x users, you'll
1048 discover that the receiver cannot understand what you send. One
1049 solution is to use PGP 2.x instead (i.e., if you use @code{pgg}, set
1050 @code{pgg-default-scheme} to @code{pgp}). If you do want to use
1051 GnuPG, you can use a compatibility script called @code{gpg-2comp}
1053 @uref{http://muppet.faveve.uni-stuttgart.de/~gero/gpg-2comp/}. You
1054 could also convince your fellow PGP 2.x users to convert to GnuPG.
1055 @vindex mml-signencrypt-style-alist
1056 As a final workaround, you can make the sign and encryption work in
1057 two steps; separately sign, then encrypt a message. If you would like
1058 to change this behavior you can customize the
1059 @code{mml-signencrypt-style-alist} variable. For example:
1062 (setq mml-signencrypt-style-alist '(("smime" separate)
1064 ("pgpauto" separate)
1065 ("pgpmime" separate)))
1068 This causes to sign and encrypt in two passes, thus generating a
1069 message that can be understood by PGP version 2.
1071 (Refer to @uref{http://www.gnupg.org/gph/en/pgp2x.html} for more
1072 information about the problem.)
1074 @node Various Commands
1075 @section Various Commands
1081 @findex message-caesar-buffer-body
1082 Caesar rotate (aka. rot13) the current message
1083 (@code{message-caesar-buffer-body}). If narrowing is in effect, just
1084 rotate the visible portion of the buffer. A numerical prefix says how
1085 many places to rotate the text. The default is 13.
1089 @findex message-elide-region
1090 @vindex message-elide-ellipsis
1091 Elide the text between point and mark (@code{message-elide-region}).
1092 The text is killed and replaced with the contents of the variable
1093 @code{message-elide-ellipsis}. The default value is to use an ellipsis
1098 @findex message-kill-address
1099 Kill the address under point.
1103 @findex message-kill-to-signature
1104 Kill all the text up to the signature, or if that's missing, up to the
1105 end of the message (@code{message-kill-to-signature}).
1109 @findex message-delete-not-region
1110 Delete all text in the body of the message that is outside the region
1111 (@code{message-delete-not-region}).
1115 @findex message-newline-and-reformat
1116 Insert four newlines, and then reformat if inside quoted text.
1121 > This is some quoted text. And here's more quoted text.
1124 If point is before @samp{And} and you press @kbd{M-RET}, you'll get:
1127 > This is some quoted text.
1131 > And here's more quoted text.
1134 @samp{*} says where point will be placed.
1138 @findex message-rename-buffer
1139 Rename the buffer (@code{message-rename-buffer}). If given a prefix,
1140 prompt for a new buffer name.
1145 @vindex message-tab-body-function
1146 If non-@code{nil} execute the function specified in
1147 @code{message-tab-body-function}. Otherwise use the function bound to
1148 @kbd{TAB} in @code{text-mode-map} or @code{global-map}.
1159 @findex message-send-and-exit
1160 Send the message and bury the current buffer
1161 (@code{message-send-and-exit}).
1165 @findex message-send
1166 Send the message (@code{message-send}).
1170 @findex message-dont-send
1171 Bury the message buffer and exit (@code{message-dont-send}).
1175 @findex message-kill-buffer
1176 Kill the message buffer and exit (@code{message-kill-buffer}). It will
1177 delete the message frame if it has been created exclusively for the
1178 message buffer. If the option
1179 @code{message-kill-buffer-and-remove-file} is non-@code{nil} and the
1180 backup file has been created for the message buffer, it will also remove
1181 the file after prompting to the user.
1185 @findex message-mimic-kill-buffer
1186 @vindex message-kill-buffer-and-remove-file
1187 This is an imitation for @code{kill-buffer}
1188 (@code{message-mimic-kill-buffer}). It dynamically binds the variable
1189 @code{message-kill-buffer-and-remove-file} to @code{nil} and calls the
1190 function @code{message-kill-buffer}.
1197 @section Mail Aliases
1198 @cindex mail aliases
1201 @vindex message-mail-alias-type
1202 The @code{message-mail-alias-type} variable controls what type of mail
1203 alias expansion to use. Currently only one form is supported---Message
1204 uses @code{mailabbrev} to handle mail aliases. If this variable is
1205 @code{nil}, no mail alias expansion will be performed.
1207 @code{mailabbrev} works by parsing the @file{/etc/mailrc} and
1208 @file{~/.mailrc} files. These files look like:
1211 alias lmi "Lars Magne Ingebrigtsen <larsi@@ifi.uio.no>"
1212 alias ding "ding@@ifi.uio.no (ding mailing list)"
1215 After adding lines like this to your @file{~/.mailrc} file, you should
1216 be able to just write @samp{lmi} in the @code{To} or @code{Cc} (and so
1217 on) headers and press @kbd{SPC} to expand the alias.
1219 No expansion will be performed upon sending of the message---all
1220 expansions have to be done explicitly.
1226 @findex ispell-message
1228 There are two popular ways to have Emacs spell-check your messages:
1229 @code{ispell} and @code{flyspell}. @code{ispell} is the older and
1230 probably more popular package. You typically first write the message,
1231 and then run the entire thing through @code{ispell} and fix all the
1232 typos. To have this happen automatically when you send a message, put
1233 something like the following in your @file{.emacs} file:
1236 (add-hook 'message-send-hook 'ispell-message)
1239 @vindex ispell-message-dictionary-alist
1240 If you're in the habit of writing in different languages, this can be
1241 controlled by the @code{ispell-message-dictionary-alist} variable:
1244 (setq ispell-message-dictionary-alist
1245 '(("^Newsgroups:.*\\bde\\." . "deutsch8")
1246 (".*" . "default")))
1249 @code{ispell} depends on having the external @samp{ispell} command
1252 The other popular method is using @code{flyspell}. This package checks
1253 your spelling while you're writing, and marks any mis-spelled words in
1256 To use @code{flyspell}, put something like the following in your
1260 (defun my-message-setup-routine ()
1262 (add-hook 'message-setup-hook 'my-message-setup-routine)
1265 @code{flyspell} depends on having the external @samp{ispell} command
1273 * Message Headers:: General message header stuff.
1274 * Mail Headers:: Customizing mail headers.
1275 * Mail Variables:: Other mail variables.
1276 * News Headers:: Customizing news headers.
1277 * News Variables:: Other news variables.
1278 * Insertion Variables:: Customizing how things are inserted.
1279 * Various Message Variables:: Other message variables.
1280 * Sending Variables:: Variables for sending.
1281 * Message Buffers:: How Message names its buffers.
1282 * Message Actions:: Actions to be performed when exiting.
1286 @node Message Headers
1287 @section Message Headers
1289 Message is quite aggressive on the message generation front. It has to
1290 be---it's a combined news and mail agent. To be able to send combined
1291 messages, it has to generate all headers itself (instead of letting the
1292 mail/news system do it) to ensure that mail and news copies of messages
1293 look sufficiently similar.
1297 @item message-generate-headers-first
1298 @vindex message-generate-headers-first
1299 If @code{t}, generate all required headers before starting to
1300 compose the message. This can also be a list of headers to generate:
1303 (setq message-generate-headers-first
1307 @vindex message-required-headers
1308 The variables @code{message-required-headers},
1309 @code{message-required-mail-headers} and
1310 @code{message-required-news-headers} specify which headers are
1313 Note that some headers will be removed and re-generated before posting,
1314 because of the variable @code{message-deletable-headers} (see below).
1316 @item message-draft-headers
1317 @vindex message-draft-headers
1318 When running Message from Gnus, the message buffers are associated
1319 with a draft group. @code{message-draft-headers} says which headers
1320 should be generated when a draft is written to the draft group.
1322 @item message-from-style
1323 @vindex message-from-style
1324 Specifies how @code{From} headers should look. There are four valid
1329 Just the address---@samp{king@@grassland.com}.
1332 @samp{king@@grassland.com (Elvis Parsley)}.
1335 @samp{Elvis Parsley <king@@grassland.com>}.
1338 Look like @code{angles} if that doesn't require quoting, and
1339 @code{parens} if it does. If even @code{parens} requires quoting, use
1340 @code{angles} anyway.
1344 @item message-deletable-headers
1345 @vindex message-deletable-headers
1346 Headers in this list that were previously generated by Message will be
1347 deleted before posting. Let's say you post an article. Then you decide
1348 to post it again to some other group, you naughty boy, so you jump back
1349 to the @code{*post-buf*} buffer, edit the @code{Newsgroups} line, and
1350 ship it off again. By default, this variable makes sure that the old
1351 generated @code{Message-ID} is deleted, and a new one generated. If
1352 this isn't done, the entire empire would probably crumble, anarchy would
1353 prevail, and cats would start walking on two legs and rule the world.
1356 @item message-default-headers
1357 @vindex message-default-headers
1358 This string is inserted at the end of the headers in all message
1361 @item message-subject-re-regexp
1362 @vindex message-subject-re-regexp
1366 Responses to messages have subjects that start with @samp{Re: }. This
1367 is @emph{not} an abbreviation of the English word ``response'', but is
1368 Latin, and means ``in response to''. Some illiterate nincompoops have
1369 failed to grasp this fact, and have ``internationalized'' their software
1370 to use abominations like @samp{Aw: } (``antwort'') or @samp{Sv: }
1371 (``svar'') instead, which is meaningless and evil. However, you may
1372 have to deal with users that use these evil tools, in which case you may
1373 set this variable to a regexp that matches these prefixes. Myself, I
1374 just throw away non-compliant mail.
1376 Here's an example of a value to deal with these headers when
1377 responding to a message:
1380 (setq message-subject-re-regexp
1385 "[Aa][Nn][Tt][Ww]\\.?\\|" ; antw
1387 "[Ff][Ww][Dd]?\\|" ; fwd
1388 "[Oo][Dd][Pp]\\|" ; odp
1390 "[Rr][\311\351][Ff]\\.?\\|" ; ref
1393 "\\(\\[[0-9]*\\]\\)"
1400 @item message-subject-trailing-was-query
1401 @vindex message-subject-trailing-was-query
1402 @vindex message-subject-trailing-was-ask-regexp
1403 @vindex message-subject-trailing-was-regexp
1404 Controls what to do with trailing @samp{(was: <old subject>)} in subject
1405 lines. If @code{nil}, leave the subject unchanged. If it is the symbol
1406 @code{ask}, query the user what do do. In this case, the subject is
1407 matched against @code{message-subject-trailing-was-ask-regexp}. If
1408 @code{message-subject-trailing-was-query} is @code{t}, always strip the
1409 trailing old subject. In this case,
1410 @code{message-subject-trailing-was-regexp} is used.
1412 @item message-alternative-emails
1413 @vindex message-alternative-emails
1414 Regexp matching alternative email addresses. The first address in the
1415 To, Cc or From headers of the original article matching this variable is
1416 used as the From field of outgoing messages, replacing the default From
1419 For example, if you have two secondary email addresses john@@home.net
1420 and john.doe@@work.com and want to use them in the From field when
1421 composing a reply to a message addressed to one of them, you could set
1422 this variable like this:
1425 (setq message-alternative-emails
1426 (regexp-opt '("john@@home.net" "john.doe@@work.com")))
1429 This variable has precedence over posting styles and anything that runs
1430 off @code{message-setup-hook}.
1432 @item message-allow-no-recipients
1433 @vindex message-allow-no-recipients
1434 Specifies what to do when there are no recipients other than
1435 @code{Gcc} or @code{Fcc}. If it is @code{always}, the posting is
1436 allowed. If it is @code{never}, the posting is not allowed. If it is
1437 @code{ask} (the default), you are prompted.
1439 @item message-hidden-headers
1440 @vindex message-hidden-headers
1441 A regexp, a list of regexps, or a list where the first element is
1442 @code{not} and the rest are regexps. It says which headers to keep
1443 hidden when composing a message.
1446 (setq message-hidden-headers
1447 '(not "From" "Subject" "To" "Cc" "Newsgroups"))
1450 Headers are hidden using narrowing, you can use @kbd{M-x widen} to
1451 expose them in the buffer.
1453 @item message-header-synonyms
1454 @vindex message-header-synonyms
1455 A list of lists of header synonyms. E.g., if this list contains a
1456 member list with elements @code{Cc} and @code{To}, then
1457 @code{message-carefully-insert-headers} will not insert a @code{To}
1458 header when the message is already @code{Cc}ed to the recipient.
1464 @section Mail Headers
1467 @item message-required-mail-headers
1468 @vindex message-required-mail-headers
1469 @xref{News Headers}, for the syntax of this variable. It is
1470 @code{(From Date Subject (optional . In-Reply-To) Message-ID Lines
1471 (optional . User-Agent))} by default.
1473 @item message-ignored-mail-headers
1474 @vindex message-ignored-mail-headers
1475 Regexp of headers to be removed before mailing. The default is
1476 @samp{^[GF]cc:\\|^Resent-Fcc:\\|^Xref:\\|^X-Draft-From:}.
1478 @item message-default-mail-headers
1479 @vindex message-default-mail-headers
1480 This string is inserted at the end of the headers in all message
1481 buffers that are initialized as mail.
1483 @item message-generate-hashcash
1484 @vindex message-generate-hashcash
1485 Boolean variable that indicate whether @samp{X-Hashcash} headers
1486 should be computed for the message. @xref{Hashcash, ,Hashcash,gnus,
1492 @node Mail Variables
1493 @section Mail Variables
1496 @item message-send-mail-function
1497 @vindex message-send-mail-function
1498 @findex message-send-mail-with-sendmail
1499 @findex message-send-mail-with-mh
1500 @findex message-send-mail-with-qmail
1501 @findex message-smtpmail-send-it
1502 @findex smtpmail-send-it
1503 @findex feedmail-send-it
1504 Function used to send the current buffer as mail. The default is
1505 @code{message-send-mail-with-sendmail}, or @code{smtpmail-send-it}
1506 according to the system. Other valid values include
1507 @code{message-send-mail-with-mh}, @code{message-send-mail-with-qmail},
1508 @code{message-smtpmail-send-it} and @code{feedmail-send-it}.
1510 @item message-mh-deletable-headers
1511 @vindex message-mh-deletable-headers
1512 Most versions of MH doesn't like being fed messages that contain the
1513 headers in this variable. If this variable is non-@code{nil} (which is
1514 the default), these headers will be removed before mailing when sending
1515 messages via MH. Set it to @code{nil} if your MH can handle these
1518 @item message-qmail-inject-program
1519 @vindex message-qmail-inject-program
1521 Location of the qmail-inject program.
1523 @item message-qmail-inject-args
1524 @vindex message-qmail-inject-args
1525 Arguments passed to qmail-inject programs.
1526 This should be a list of strings, one string for each argument. It
1527 may also be a function.
1529 For e.g., if you wish to set the envelope sender address so that bounces
1530 go to the right place or to deal with listserv's usage of that address, you
1531 might set this variable to @code{'("-f" "you@@some.where")}.
1533 @item message-sendmail-f-is-evil
1534 @vindex message-sendmail-f-is-evil
1536 Non-@code{nil} means don't add @samp{-f username} to the sendmail
1537 command line. Doing so would be even more evil than leaving it out.
1539 @item message-sendmail-envelope-from
1540 @vindex message-sendmail-envelope-from
1541 When @code{message-sendmail-f-is-evil} is @code{nil}, this specifies
1542 the address to use in the @acronym{SMTP} envelope. If it is
1543 @code{nil}, use @code{user-mail-address}. If it is the symbol
1544 @code{header}, use the @samp{From} header of the message.
1546 @item message-mailer-swallows-blank-line
1547 @vindex message-mailer-swallows-blank-line
1548 Set this to non-@code{nil} if the system's mailer runs the header and
1549 body together. (This problem exists on SunOS 4 when sendmail is run
1550 in remote mode.) The value should be an expression to test whether
1551 the problem will actually occur.
1553 @item message-send-mail-partially-limit
1554 @vindex message-send-mail-partially-limit
1555 @cindex split large message
1556 The limitation of messages sent as message/partial. The lower bound
1557 of message size in characters, beyond which the message should be sent
1558 in several parts. If it is @code{nil}, the size is unlimited.
1564 @section News Headers
1566 @vindex message-required-news-headers
1567 @code{message-required-news-headers} a list of header symbols. These
1568 headers will either be automatically generated, or, if that's
1569 impossible, they will be prompted for. The following symbols are valid:
1575 @findex user-full-name
1576 @findex user-mail-address
1577 This required header will be filled out with the result of the
1578 @code{message-make-from} function, which depends on the
1579 @code{message-from-style}, @code{user-full-name},
1580 @code{user-mail-address} variables.
1584 This required header will be prompted for if not present already.
1588 This required header says which newsgroups the article is to be posted
1589 to. If it isn't present already, it will be prompted for.
1592 @cindex organization
1593 @vindex message-user-organization
1594 @vindex message-user-organization-file
1595 This optional header will be filled out depending on the
1596 @code{message-user-organization} variable.
1597 @code{message-user-organization-file} will be used if this variable is
1598 @code{t}. This variable can also be a string (in which case this string
1599 will be used), or it can be a function (which will be called with no
1600 parameters and should return a string to be used).
1604 This optional header will be computed by Message.
1608 @vindex message-user-fqdn
1609 @vindex mail-host-address
1610 @vindex user-mail-address
1613 @cindex i-did-not-set--mail-host-address--so-tickle-me
1614 This required header will be generated by Message. A unique ID will be
1615 created based on the date, time, user name (for the local part) and the
1616 domain part. For the domain part, message will look (in this order) at
1617 @code{message-user-fqdn}, @code{system-name}, @code{mail-host-address}
1618 and @code{message-user-mail-address} (i.e. @code{user-mail-address})
1619 until a probably valid fully qualified domain name (FQDN) was found.
1623 This optional header will be filled out according to the
1624 @code{message-newsreader} local variable.
1627 This optional header is filled out using the @code{Date} and @code{From}
1628 header of the article being replied to.
1632 @vindex message-expires
1633 This extremely optional header will be inserted according to the
1634 @code{message-expires} variable. It is highly deprecated and shouldn't
1635 be used unless you know what you're doing.
1638 @cindex Distribution
1639 @vindex message-distribution-function
1640 This optional header is filled out according to the
1641 @code{message-distribution-function} variable. It is a deprecated and
1642 much misunderstood header.
1646 @vindex message-user-path
1647 This extremely optional header should probably never be used.
1648 However, some @emph{very} old servers require that this header is
1649 present. @code{message-user-path} further controls how this
1650 @code{Path} header is to look. If it is @code{nil}, use the server name
1651 as the leaf node. If it is a string, use the string. If it is neither
1652 a string nor @code{nil}, use the user name only. However, it is highly
1653 unlikely that you should need to fiddle with this variable at all.
1657 @cindex Mime-Version
1658 In addition, you can enter conses into this list. The @sc{car} of this cons
1659 should be a symbol. This symbol's name is the name of the header, and
1660 the @sc{cdr} can either be a string to be entered verbatim as the value of
1661 this header, or it can be a function to be called. This function should
1662 return a string to be inserted. For instance, if you want to insert
1663 @code{Mime-Version: 1.0}, you should enter @code{(Mime-Version . "1.0")}
1664 into the list. If you want to insert a funny quote, you could enter
1665 something like @code{(X-Yow . yow)} into the list. The function
1666 @code{yow} will then be called without any arguments.
1668 If the list contains a cons where the @sc{car} of the cons is
1669 @code{optional}, the @sc{cdr} of this cons will only be inserted if it is
1672 If you want to delete an entry from this list, the following Lisp
1673 snippet might be useful. Adjust accordingly if you want to remove
1677 (setq message-required-news-headers
1678 (delq 'Message-ID message-required-news-headers))
1681 Other variables for customizing outgoing news articles:
1685 @item message-syntax-checks
1686 @vindex message-syntax-checks
1687 Controls what syntax checks should not be performed on outgoing posts.
1688 To disable checking of long signatures, for instance, add
1691 (signature . disabled)
1700 Check the subject for commands.
1703 Insert a new @code{Sender} header if the @code{From} header looks odd.
1704 @item multiple-headers
1705 Check for the existence of multiple equal headers.
1708 Check for the existence of version and sendsys commands.
1710 Check whether the @code{Message-ID} looks ok.
1712 Check whether the @code{From} header seems nice.
1715 Check for too long lines.
1717 Check for invalid characters.
1719 Check for excessive size.
1721 Check whether there is any new text in the messages.
1723 Check the length of the signature.
1726 Check whether the article has an @code{Approved} header, which is
1727 something only moderators should include.
1729 Check whether the article is empty.
1730 @item invisible-text
1731 Check whether there is any invisible text in the buffer.
1733 Check whether any of the headers are empty.
1734 @item existing-newsgroups
1735 Check whether the newsgroups mentioned in the @code{Newsgroups} and
1736 @code{Followup-To} headers exist.
1737 @item valid-newsgroups
1738 Check whether the @code{Newsgroups} and @code{Followup-to} headers
1739 are valid syntactically.
1740 @item repeated-newsgroups
1741 Check whether the @code{Newsgroups} and @code{Followup-to} headers
1742 contains repeated group names.
1743 @item shorten-followup-to
1744 Check whether to add a @code{Followup-to} header to shorten the number
1745 of groups to post to.
1748 All these conditions are checked by default.
1750 @item message-ignored-news-headers
1751 @vindex message-ignored-news-headers
1752 Regexp of headers to be removed before posting. The default is@*
1753 @samp{^NNTP-Posting-Host:\\|^Xref:\\|^[BGF]cc:\\|^Resent-Fcc:\\|^X-Draft-From:}.
1755 @item message-default-news-headers
1756 @vindex message-default-news-headers
1757 This string is inserted at the end of the headers in all message
1758 buffers that are initialized as news.
1763 @node News Variables
1764 @section News Variables
1767 @item message-send-news-function
1768 @vindex message-send-news-function
1769 Function used to send the current buffer as news. The default is
1770 @code{message-send-news}.
1772 @item message-post-method
1773 @vindex message-post-method
1774 Gnusish @dfn{select method} (see the Gnus manual for details) used for
1775 posting a prepared news message.
1780 @node Insertion Variables
1781 @section Insertion Variables
1784 @item message-ignored-cited-headers
1785 @vindex message-ignored-cited-headers
1786 All headers that match this regexp will be removed from yanked
1787 messages. The default is @samp{.}, which means that all headers will be
1790 @item message-cite-prefix-regexp
1791 @vindex message-cite-prefix-regexp
1792 Regexp matching the longest possible citation prefix on a line.
1794 @item message-citation-line-function
1795 @vindex message-citation-line-function
1796 @cindex attribution line
1797 Function called to insert the citation line. The default is
1798 @code{message-insert-citation-line}, which will lead to citation lines
1802 Hallvard B Furuseth <h.b.furuseth@@usit.uio.no> writes:
1805 Point will be at the beginning of the body of the message when this
1808 Note that Gnus provides a feature where clicking on `writes:' hides the
1809 cited text. If you change the citation line too much, readers of your
1810 messages will have to adjust their Gnus, too. See the variable
1811 @code{gnus-cite-attribution-suffix}. @xref{Article Highlighting, ,
1812 Article Highlighting, gnus, The Gnus Manual}, for details.
1814 @item message-yank-prefix
1815 @vindex message-yank-prefix
1818 When you are replying to or following up an article, you normally want
1819 to quote the person you are answering. Inserting quoted text is done by
1820 @dfn{yanking}, and each line you yank will have
1821 @code{message-yank-prefix} prepended to it (except for quoted lines
1822 which use @code{message-yank-cited-prefix} and empty lines which use
1823 @code{message-yank-empty-prefix}). The default is @samp{> }.
1825 @item message-yank-cited-prefix
1826 @vindex message-yank-cited-prefix
1830 When yanking text from an article which contains already cited text,
1831 each line will be prefixed with the contents of this variable. The
1832 default is @samp{>}. See also @code{message-yank-prefix}.
1834 @item message-yank-empty-prefix
1835 @vindex message-yank-empty-prefix
1838 When yanking text from an article, each empty line will be prefixed with
1839 the contents of this variable. The default is @samp{>}. You can set
1840 this variable to an empty string to split the cited text into paragraphs
1841 automatically. See also @code{message-yank-prefix}.
1843 @item message-yank-add-new-references
1844 @vindex message-yank-add-new-references
1846 Non-@code{nil} means new IDs will be added to References field when an
1847 article is yanked by the command @code{message-yank-original}
1848 interactively. If it is a symbol @code{message-id-only}, only an ID
1849 from Message-ID field is used, otherwise IDs extracted from References,
1850 In-Reply-To and Message-ID fields are used.
1852 @item message-list-references-add-position
1853 @vindex message-list-references-add-position
1855 Integer value means position for adding to References field when an
1856 article is yanked by the command @code{message-yank-original}
1859 @item message-indentation-spaces
1860 @vindex message-indentation-spaces
1861 Number of spaces to indent yanked messages.
1863 @item message-cite-function
1864 @vindex message-cite-function
1865 @findex message-cite-original
1866 @findex sc-cite-original
1867 @findex message-cite-original-without-signature
1869 Function for citing an original message. The default is
1870 @code{message-cite-original}, which simply inserts the original message
1871 and prepends @samp{> } to each line.
1872 @code{message-cite-original-without-signature} does the same, but elides
1873 the signature. You can also set it to @code{sc-cite-original} to use
1876 @item message-suspend-font-lock-when-citing
1877 @vindex message-suspend-font-lock-when-citing
1878 If non-@code{nil}, suspend font-lock'ing while citing an original
1879 message. Some lazy demand-driven fontification tools (or Emacs itself)
1880 have a bug that they often miss a buffer to be fontified. It will
1881 mostly occur when Emacs prompts user for any inputs in the minibuffer.
1882 Setting this option to non-@code{nil} may help you to avoid unpleasant
1883 errors even if it is an add-hoc expedient.
1885 @item message-indent-citation-function
1886 @vindex message-indent-citation-function
1887 Function for modifying a citation just inserted in the mail buffer.
1888 This can also be a list of functions. Each function can find the
1889 citation between @code{(point)} and @code{(mark t)}. And each function
1890 should leave point and mark around the citation text as modified.
1892 @item message-mark-insert-begin
1893 @vindex message-mark-insert-begin
1894 String to mark the beginning of some inserted text.
1896 @item message-mark-insert-end
1897 @vindex message-mark-insert-end
1898 String to mark the end of some inserted text.
1900 @item message-signature
1901 @vindex message-signature
1902 String to be inserted at the end of the message buffer. If @code{t}
1903 (which is the default), the @code{message-signature-file} file will be
1904 inserted instead. If a function, the result from the function will be
1905 used instead. If a form, the result from the form will be used instead.
1906 If this variable is @code{nil}, no signature will be inserted at all.
1908 @item message-signature-file
1909 @vindex message-signature-file
1910 File containing the signature to be inserted at the end of the buffer.
1911 The default is @file{~/.signature}.
1913 @item message-signature-insert-empty-line
1914 @vindex message-signature-insert-empty-line
1915 If @code{t} (the default value) an empty line is inserted before the
1916 signature separator.
1920 Note that RFC1036bis says that a signature should be preceded by the three
1921 characters @samp{-- } on a line by themselves. This is to make it
1922 easier for the recipient to automatically recognize and process the
1923 signature. So don't remove those characters, even though you might feel
1924 that they ruin your beautiful design, like, totally.
1926 Also note that no signature should be more than four lines long.
1927 Including @acronym{ASCII} graphics is an efficient way to get
1928 everybody to believe that you are silly and have nothing important to
1932 @node Various Message Variables
1933 @section Various Message Variables
1936 @item message-default-charset
1937 @vindex message-default-charset
1939 Symbol naming a @acronym{MIME} charset. Non-@acronym{ASCII}
1940 characters in messages are assumed to be encoded using this charset.
1941 The default is @code{nil}, which means ask the user. (This variable
1942 is used only on non-@sc{mule} Emacsen. @xref{Charset Translation, ,
1943 Charset Translation, emacs-mime, Emacs MIME Manual}, for details on
1944 the @sc{mule}-to-@acronym{MIME} translation process.
1946 @item message-signature-separator
1947 @vindex message-signature-separator
1948 Regexp matching the signature separator. It is @samp{^-- *$} by
1951 @item mail-header-separator
1952 @vindex mail-header-separator
1953 String used to separate the headers from the body. It is @samp{--text
1954 follows this line--} by default.
1956 @item message-directory
1957 @vindex message-directory
1958 Directory used by many mailey things. The default is @file{~/Mail/}.
1959 All other mail file variables are derived from @code{message-directory}.
1961 @item message-auto-save-directory
1962 @vindex message-auto-save-directory
1963 Directory where Message auto-saves buffers if Gnus isn't running. If
1964 @code{nil}, Message won't auto-save. The default is @file{~/Mail/drafts/}.
1966 @item message-signature-setup-hook
1967 @vindex message-signature-setup-hook
1968 Hook run when initializing the message buffer. It is run after the
1969 headers have been inserted but before the signature has been inserted.
1971 @item message-setup-hook
1972 @vindex message-setup-hook
1973 Hook run as the last thing when the message buffer has been initialized,
1974 but before yanked text is inserted.
1976 @item message-header-setup-hook
1977 @vindex message-header-setup-hook
1978 Hook called narrowed to the headers after initializing the headers.
1980 For instance, if you're running Gnus and wish to insert a
1981 @samp{Mail-Copies-To} header in all your news articles and all messages
1982 you send to mailing lists, you could do something like the following:
1985 (defun my-message-header-setup-hook ()
1986 (let ((group (or gnus-newsgroup-name "")))
1987 (when (or (message-fetch-field "newsgroups")
1988 (gnus-group-find-parameter group 'to-address)
1989 (gnus-group-find-parameter group 'to-list))
1990 (insert "Mail-Copies-To: never\n"))))
1992 (add-hook 'message-header-setup-hook
1993 'my-message-header-setup-hook)
1996 @item message-send-hook
1997 @vindex message-send-hook
1998 Hook run before sending messages.
2000 If you want to add certain headers before sending, you can use the
2001 @code{message-add-header} function in this hook. For instance:
2002 @findex message-add-header
2005 (add-hook 'message-send-hook 'my-message-add-content)
2006 (defun my-message-add-content ()
2007 (message-add-header "X-In-No-Sense: Nonsense")
2008 (message-add-header "X-Whatever: no"))
2011 This function won't add the header if the header is already present.
2013 @item message-send-mail-hook
2014 @vindex message-send-mail-hook
2015 Hook run before sending mail messages. This hook is run very late --
2016 just before the message is actually sent as mail.
2018 @item message-send-news-hook
2019 @vindex message-send-news-hook
2020 Hook run before sending news messages. This hook is run very late --
2021 just before the message is actually sent as news.
2023 @item message-sent-hook
2024 @vindex message-sent-hook
2025 Hook run after sending messages.
2027 @item message-cancel-hook
2028 @vindex message-cancel-hook
2029 Hook run when canceling news articles.
2031 @item message-mode-syntax-table
2032 @vindex message-mode-syntax-table
2033 Syntax table used in message mode buffers.
2035 @item message-cite-articles-with-x-no-archive
2036 @vindex message-cite-articles-with-x-no-archive
2037 If non-@code{nil}, don't strip quoted text from articles that have
2038 @samp{X-No-Archive} set. Even if this variable isn't set, you can
2039 undo the stripping by hitting the @code{undo} keystroke.
2041 @item message-strip-special-text-properties
2042 @vindex message-strip-special-text-properties
2043 Emacs has a number of special text properties which can break message
2044 composing in various ways. If this option is set, message will strip
2045 these properties from the message composition buffer. However, some
2046 packages requires these properties to be present in order to work. If
2047 you use one of these packages, turn this option off, and hope the
2048 message composition doesn't break too bad.
2050 @item message-send-method-alist
2051 @vindex message-send-method-alist
2053 Alist of ways to send outgoing messages. Each element has the form
2056 (@var{type} @var{predicate} @var{function})
2061 A symbol that names the method.
2064 A function called without any parameters to determine whether the
2065 message is a message of type @var{type}.
2068 A function to be called if @var{predicate} returns non-@code{nil}.
2069 @var{function} is called with one parameter---the prefix.
2073 ((news message-news-p message-send-via-news)
2074 (mail message-mail-p message-send-via-mail))
2082 @node Sending Variables
2083 @section Sending Variables
2087 @item message-fcc-handler-function
2088 @vindex message-fcc-handler-function
2089 A function called to save outgoing articles. This function will be
2090 called with the name of the file to store the article in. The default
2091 function is @code{message-output} which saves in Unix mailbox format.
2093 @item message-courtesy-message
2094 @vindex message-courtesy-message
2095 When sending combined messages, this string is inserted at the start of
2096 the mailed copy. If the string contains the format spec @samp{%s}, the
2097 newsgroups the article has been posted to will be inserted there. If
2098 this variable is @code{nil}, no such courtesy message will be added.
2099 The default value is @samp{"The following message is a courtesy copy of
2100 an article\\nthat has been posted to %s as well.\\n\\n"}.
2102 @item message-fcc-externalize-attachments
2103 @vindex message-fcc-externalize-attachments
2104 If @code{nil}, attach files as normal parts in Fcc copies; if it is
2105 non-@code{nil}, attach local files as external parts.
2107 @item message-interactive
2108 @vindex message-interactive
2109 If non-@code{nil} wait for and display errors when sending a message;
2110 if @code{nil} let the mailer mail back a message to report errors.
2115 @node Message Buffers
2116 @section Message Buffers
2118 Message will generate new buffers with unique buffer names when you
2119 request a message buffer. When you send the message, the buffer isn't
2120 normally killed off. Its name is changed and a certain number of old
2121 message buffers are kept alive.
2124 @item message-generate-new-buffers
2125 @vindex message-generate-new-buffers
2126 If non-@code{nil}, generate new buffers. The default is @code{t}. If
2127 this is a function, call that function with three parameters: The type,
2128 the to address and the group name. (Any of these may be @code{nil}.)
2129 The function should return the new buffer name.
2131 @item message-use-multi-frames
2132 @vindex message-use-multi-frames
2133 If non-@code{nil}, generate new frames. The default is @code{nil}.
2135 @item message-delete-frame-on-exit
2136 @vindex message-delete-frame-on-exit
2137 The @code{message-delete-frame-on-exit} variable says whether to delete
2138 the frame after sending the message or killing the message buffer. If it
2139 is @code{nil} (which is the default), don't delete the frame. If it is
2140 @code{ask}, ask wheter to delete the frame. If it is @code{t}, always
2143 @item message-max-buffers
2144 @vindex message-max-buffers
2145 This variable says how many old message buffers to keep. If there are
2146 more message buffers than this, the oldest buffer will be killed. The
2147 default is 10. If this variable is @code{nil}, no old message buffers
2148 will ever be killed.
2150 @item message-send-rename-function
2151 @vindex message-send-rename-function
2152 After sending a message, the buffer is renamed from, for instance,
2153 @samp{*reply to Lars*} to @samp{*sent reply to Lars*}. If you don't
2154 like this, set this variable to a function that renames the buffer in a
2155 manner you like. If you don't want to rename the buffer at all, you can
2159 (setq message-send-rename-function 'ignore)
2162 @item message-kill-buffer-on-exit
2163 @vindex message-kill-buffer-on-exit
2164 If non-@code{nil}, kill the buffer immediately on exit.
2166 @item message-kill-buffer-query-function
2167 @vindex message-kill-buffer-query-function
2168 @findex message-kill-buffer
2169 @findex message-mimic-kill-buffer
2170 Function used to prompt user whether to kill the message buffer when the
2171 command @code{message-kill-buffer} or @code{message-mimic-kill-buffer}
2172 is used. It defaults to @code{yes-or-no-p}. You may alter the value to
2173 @code{y-or-n-p}, @code{nnheader-Y-or-n-p}, etc. If it is @code{t}, the
2174 buffer will be killed without query.
2176 @item message-kill-buffer-and-remove-file
2177 @vindex message-kill-buffer-and-remove-file
2178 @findex message-kill-buffer
2179 @findex message-mimic-kill-buffer
2180 If it is non-@code{nil}, remove the backup file if it exists with a
2181 query to the user, after the message buffer is killed. Otherwise the
2182 file won't be removed. It defaults to @code{t}. However, it is treated
2183 as @code{nil} when the command `message-mimic-kill-buffer' is used.
2188 @node Message Actions
2189 @section Message Actions
2191 When Message is being used from a news/mail reader, the reader is likely
2192 to want to perform some task after the message has been sent. Perhaps
2193 return to the previous window configuration or mark an article as
2196 @vindex message-kill-actions
2197 @vindex message-postpone-actions
2198 @vindex message-exit-actions
2199 @vindex message-send-actions
2200 The user may exit from the message buffer in various ways. The most
2201 common is @kbd{C-c C-c}, which sends the message and exits. Other
2202 possibilities are @kbd{C-c C-s} which just sends the message, @kbd{C-c
2203 C-d} which postpones the message editing and buries the message buffer,
2204 and @kbd{C-c C-k} which kills the message buffer. Each of these actions
2205 have lists associated with them that contains actions to be executed:
2206 @code{message-send-actions}, @code{message-exit-actions},
2207 @code{message-postpone-actions}, and @code{message-kill-actions}.
2209 Message provides a function to interface with these lists:
2210 @code{message-add-action}. The first parameter is the action to be
2211 added, and the rest of the arguments are which lists to add this action
2212 to. Here's an example from Gnus:
2216 `(set-window-configuration ,(current-window-configuration))
2217 'exit 'postpone 'kill)
2220 This restores the Gnus window configuration when the message buffer is
2221 killed, postponed or exited.
2223 An @dfn{action} can be either: a normal function, or a list where the
2224 @sc{car} is a function and the @sc{cdr} is the list of arguments, or
2225 a form to be @code{eval}ed.
2229 @chapter Compatibility
2230 @cindex compatibility
2232 Message uses virtually only its own variables---older @code{mail-}
2233 variables aren't consulted. To force Message to take those variables
2234 into account, you can put the following in your @file{.emacs} file:
2237 (require 'messcompat)
2240 This will initialize many Message variables from the values in the
2241 corresponding mail variables.
2248 * Responses:: Standard rules for determining where responses go.
2255 To determine where a message is to go, the following algorithm is used
2260 A @dfn{reply} is when you want to respond @emph{just} to the person who
2261 sent the message via mail. There will only be one recipient. To
2262 determine who the recipient will be, the following headers are
2273 A @dfn{wide reply} is a mail response that includes @emph{all} entities
2274 mentioned in the message you are responded to. All mailboxes from the
2275 following headers will be concatenated to form the outgoing
2276 @code{To}/@code{Cc} headers:
2280 (unless there's a @code{Reply-To}, in which case that is used instead).
2287 If a @code{Mail-Copies-To} header is present, it will also be included
2288 in the list of mailboxes. If this header is @samp{never}, that means
2289 that the @code{From} (or @code{Reply-To}) mailbox will be suppressed.
2293 A @dfn{followup} is a response sent via news. The following headers
2294 (listed in order of precedence) determine where the response is to be
2305 If a @code{Mail-Copies-To} header is present, it will be used as the
2306 basis of the new @code{Cc} header, except if this header is