Commit | Line | Data |
---|---|---|
6bf7aab6 DL |
1 | \input texinfo @c -*-texinfo-*- |
2 | ||
a1720df0 | 3 | @setfilename ../info/message |
23f87bed | 4 | @settitle Message Manual |
6bf7aab6 DL |
5 | @synindex fn cp |
6 | @synindex vr cp | |
7 | @synindex pg cp | |
18f952d5 | 8 | @copying |
6bf7aab6 DL |
9 | This file documents Message, the Emacs message composition mode. |
10 | ||
10ace8ea | 11 | Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005 |
23f87bed | 12 | Free Software Foundation, Inc. |
6bf7aab6 | 13 | |
18f952d5 | 14 | @quotation |
9d3d5390 DL |
15 | Permission is granted to copy, distribute and/or modify this document |
16 | under the terms of the GNU Free Documentation License, Version 1.1 or | |
8ac08dea DL |
17 | any later version published by the Free Software Foundation; with no |
18 | Invariant Sections, with the Front-Cover texts being ``A GNU | |
9d3d5390 DL |
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 | |
a03e63d9 | 21 | License'' in the Emacs manual. |
6bf7aab6 | 22 | |
9d3d5390 DL |
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.'' | |
a03e63d9 DL |
26 | |
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. | |
18f952d5 KB |
31 | @end quotation |
32 | @end copying | |
33 | ||
34 | @dircategory Emacs | |
35 | @direntry | |
36 | * Message: (message). Mail and news composition mode that goes with Gnus. | |
37 | @end direntry | |
38 | @iftex | |
39 | @finalout | |
40 | @end iftex | |
41 | @setchapternewpage odd | |
6bf7aab6 | 42 | |
6bf7aab6 | 43 | @titlepage |
23f87bed | 44 | @title Message Manual |
6bf7aab6 DL |
45 | |
46 | @author by Lars Magne Ingebrigtsen | |
47 | @page | |
23f87bed | 48 | |
6bf7aab6 | 49 | @vskip 0pt plus 1filll |
18f952d5 | 50 | @insertcopying |
6bf7aab6 DL |
51 | @end titlepage |
52 | @page | |
53 | ||
6bf7aab6 DL |
54 | @node Top |
55 | @top Message | |
56 | ||
57 | All message composition from Gnus (both mail and news) takes place in | |
58 | Message mode buffers. | |
59 | ||
60 | @menu | |
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. | |
68 | @end menu | |
69 | ||
23f87bed MB |
70 | This manual corresponds to Message v5.10.6. Message is distributed |
71 | with the Gnus distribution bearing the same version number as this | |
72 | manual. | |
6bf7aab6 DL |
73 | |
74 | ||
75 | @node Interface | |
76 | @chapter Interface | |
77 | ||
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 | |
83 | sending it. | |
84 | ||
85 | @menu | |
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. | |
23f87bed | 96 | * Mailing Lists:: Send mail to mailing lists. |
6bf7aab6 DL |
97 | @end menu |
98 | ||
99 | ||
100 | @node New Mail Message | |
101 | @section New Mail Message | |
102 | ||
103 | @findex message-mail | |
9d3d5390 | 104 | The @code{message-mail} command pops up a new message buffer. |
6bf7aab6 DL |
105 | |
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. | |
109 | ||
110 | ||
111 | @node New News Message | |
112 | @section New News Message | |
113 | ||
114 | @findex message-news | |
9d3d5390 | 115 | The @code{message-news} command pops up a new message buffer. |
6bf7aab6 DL |
116 | |
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. | |
120 | ||
121 | ||
122 | @node Reply | |
123 | @section Reply | |
124 | ||
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. | |
128 | ||
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. | |
133 | ||
134 | If you want the replies to go to the @code{Sender} instead of the | |
135 | @code{From}, you could do something like this: | |
136 | ||
137 | @lisp | |
138 | (setq message-reply-to-function | |
139 | (lambda () | |
140 | (cond ((equal (mail-fetch-field "from") "somebody") | |
9d3d5390 DL |
141 | (list (cons 'To (mail-fetch-field "sender")))) |
142 | (t | |
6bf7aab6 DL |
143 | nil)))) |
144 | @end lisp | |
145 | ||
146 | This function will be called narrowed to the head of the article that is | |
147 | being replied to. | |
148 | ||
112d84ef MB |
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. | |
153 | ||
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. | |
6bf7aab6 DL |
158 | |
159 | ||
160 | @node Wide Reply | |
161 | @section Wide Reply | |
162 | ||
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. | |
168 | ||
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 | |
9d3d5390 | 173 | @code{message-reply-to-function} (@pxref{Reply}). |
6bf7aab6 | 174 | |
23f87bed | 175 | @vindex message-dont-reply-to-names |
9d3d5390 | 176 | Addresses that match the @code{message-dont-reply-to-names} regular |
6bf7aab6 DL |
177 | expression will be removed from the @code{Cc} header. |
178 | ||
23f87bed MB |
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}. | |
6bf7aab6 DL |
183 | |
184 | @node Followup | |
185 | @section Followup | |
186 | ||
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. | |
190 | ||
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}). | |
196 | ||
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. | |
203 | ||
204 | ||
205 | @node Canceling News | |
206 | @section Canceling News | |
207 | ||
208 | @findex message-cancel-news | |
209 | The @code{message-cancel-news} command cancels the article in the | |
210 | current buffer. | |
211 | ||
23f87bed MB |
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 | |
215 | article.}. | |
216 | ||
217 | @cindex Cancel Locks | |
218 | @vindex message-insert-canlock | |
219 | @cindex 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 | |
531e5812 | 226 | able to cancel your message. If you want to manage a password yourself, |
8903a9c8 MB |
227 | you can put something like the following in your @file{~/.gnus.el} file: |
228 | ||
229 | @lisp | |
531e5812 | 230 | (setq canlock-password "geheimnis" |
8903a9c8 MB |
231 | canlock-password-for-verify canlock-password) |
232 | @end lisp | |
23f87bed MB |
233 | |
234 | Whether to insert the header or not is controlled by the | |
235 | @code{message-insert-canlock} variable. | |
236 | ||
237 | Not many news servers respect the @code{Cancel-Lock} header yet, but | |
238 | this is expected to change in the future. | |
239 | ||
6bf7aab6 DL |
240 | |
241 | @node Superseding | |
242 | @section Superseding | |
243 | ||
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. | |
247 | ||
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:}. | |
253 | ||
254 | ||
255 | ||
256 | @node Forwarding | |
257 | @section Forwarding | |
258 | ||
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 | |
262 | news. | |
263 | ||
264 | @table @code | |
9d3d5390 DL |
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. | |
6bf7aab6 DL |
268 | |
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. | |
274 | ||
275 | The provided functions are: | |
276 | ||
277 | @table @code | |
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 | |
281 | subject. | |
282 | ||
283 | @item message-forward-subject-fwd | |
284 | Subject of article with @samp{Fwd:} prepended to it. | |
285 | @end table | |
286 | ||
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 | |
9d3d5390 | 290 | the evidence of previous forwards (such as @samp{Fwd:}, @samp{Re:}, |
6bf7aab6 DL |
291 | @samp{(fwd)}) removed before the new subject is |
292 | constructed. The default value is @code{nil}. | |
293 | ||
9d3d5390 DL |
294 | @item message-forward-as-mime |
295 | @vindex message-forward-as-mime | |
296 | If this variable is @code{t} (the default), forwarded messages are | |
23f87bed | 297 | included as inline @acronym{MIME} RFC822 parts. If it's @code{nil}, forwarded |
9d3d5390 | 298 | messages will just be copied inline to the new message, like previous, |
23f87bed MB |
299 | non @acronym{MIME}-savvy versions of Gnus would do. |
300 | ||
301 | @item message-forward-before-signature | |
302 | @vindex message-forward-before-signature | |
303 | If non-@code{nil}, put forwarded message before signature, else after. | |
304 | ||
6bf7aab6 DL |
305 | @end table |
306 | ||
307 | ||
308 | @node Resending | |
309 | @section Resending | |
310 | ||
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. | |
314 | ||
315 | @vindex message-ignored-resent-headers | |
316 | Headers that match the @code{message-ignored-resent-headers} regexp will | |
8903a9c8 | 317 | be removed before sending the message. |
6bf7aab6 DL |
318 | |
319 | ||
320 | @node Bouncing | |
321 | @section Bouncing | |
322 | ||
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 | |
9d3d5390 | 328 | undeliverable. |
6bf7aab6 DL |
329 | |
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\\):}. | |
334 | ||
335 | ||
23f87bed MB |
336 | @node Mailing Lists |
337 | @section Mailing Lists | |
338 | ||
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 | |
343 | useful: | |
344 | ||
345 | @itemize @bullet | |
346 | @item | |
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. | |
350 | ||
351 | @item | |
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. | |
355 | ||
356 | @item | |
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. | |
361 | ||
362 | @end itemize | |
363 | ||
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. | |
367 | ||
368 | @c @menu | |
369 | @c * Honoring an MFT post:: What to do when one already exists | |
370 | @c * Composing with a MFT header:: Creating one from scratch. | |
371 | @c @end menu | |
372 | ||
373 | @c @node Composing with a MFT header | |
374 | @subsection Composing a correct MFT header automagically | |
375 | ||
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. | |
380 | ||
381 | @table @code | |
382 | ||
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: | |
387 | @lisp | |
388 | (setq message-subscribed-addresses | |
389 | '("ding@@gnus.org" "bing@@noose.org")) | |
390 | @end lisp | |
391 | ||
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: | |
397 | @lisp | |
398 | (setq message-subscribed-regexps | |
399 | '("\\(ding@@gnus\\)\\|\\(bing@@noose\\)\\.org") | |
400 | @end lisp | |
401 | ||
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}. | |
407 | ||
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. | |
414 | ||
415 | @lisp | |
416 | (setq message-subscribed-address-functions | |
417 | '(gnus-find-subscribed-addresses)) | |
418 | @end lisp | |
419 | ||
420 | @vindex message-subscribed-address-file | |
421 | @item message-subscribed-address-file | |
422 | You might be one organised 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. | |
425 | ||
426 | @end table | |
427 | ||
428 | You can use one or more of the above variables. All their values are | |
429 | ``added'' in some way that works :-) | |
430 | ||
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: | |
442 | ||
443 | @kindex C-c C-f C-a | |
444 | @findex message-generate-unsubscribed-mail-followup-to | |
445 | @kindex C-c C-f C-m | |
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. | |
456 | ||
457 | @c @node Honoring an MFT post | |
458 | @subsection Honoring an MFT post | |
459 | ||
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: | |
464 | ||
465 | @table @code | |
466 | @item use | |
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. | |
469 | ||
470 | @item nil | |
471 | Always dishonor MFTs (just ignore the darned thing) | |
472 | ||
473 | @item ask | |
474 | Gnus will prompt you for an action. | |
475 | ||
476 | @end table | |
477 | ||
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 | |
480 | better than you do. | |
481 | ||
6bf7aab6 DL |
482 | @node Commands |
483 | @chapter Commands | |
484 | ||
485 | @menu | |
dda5808a | 486 | * Buffer Entry:: Commands after entering a Message buffer. |
23f87bed | 487 | * Header Commands:: Commands for moving headers or changing headers. |
6bf7aab6 DL |
488 | * Movement:: Moving around in message buffers. |
489 | * Insertion:: Inserting things into message buffers. | |
23f87bed MB |
490 | * MIME:: @acronym{MIME} considerations. |
491 | * IDNA:: Non-@acronym{ASCII} domain name considerations. | |
492 | * Security:: Signing and encrypting messages. | |
6bf7aab6 DL |
493 | * Various Commands:: Various things. |
494 | * Sending:: Actually sending the message. | |
495 | * Mail Aliases:: How to use mail aliases. | |
dda5808a | 496 | * Spelling:: Having Emacs check your spelling. |
6bf7aab6 DL |
497 | @end menu |
498 | ||
499 | ||
dda5808a DL |
500 | @node Buffer Entry |
501 | @section Buffer Entry | |
502 | @cindex undo | |
503 | @kindex C-_ | |
504 | ||
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. | |
513 | ||
514 | ||
6bf7aab6 DL |
515 | @node Header Commands |
516 | @section Header Commands | |
517 | ||
23f87bed MB |
518 | @subsection Commands for moving to headers |
519 | ||
520 | These following commands move to the header in question. If it doesn't | |
521 | exist, it will be inserted. | |
6bf7aab6 DL |
522 | |
523 | @table @kbd | |
524 | ||
525 | @item C-c ? | |
526 | @kindex C-c ? | |
23f87bed | 527 | @findex describe-mode |
6bf7aab6 DL |
528 | Describe the message mode. |
529 | ||
530 | @item C-c C-f C-t | |
9d3d5390 | 531 | @kindex C-c C-f C-t |
6bf7aab6 DL |
532 | @findex message-goto-to |
533 | Go to the @code{To} header (@code{message-goto-to}). | |
534 | ||
23f87bed MB |
535 | @item C-c C-f C-o |
536 | @kindex C-c C-f C-o | |
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.) | |
540 | ||
6bf7aab6 | 541 | @item C-c C-f C-b |
9d3d5390 | 542 | @kindex C-c C-f C-b |
6bf7aab6 DL |
543 | @findex message-goto-bcc |
544 | Go to the @code{Bcc} header (@code{message-goto-bcc}). | |
545 | ||
23f87bed MB |
546 | @item C-c C-f C-f |
547 | @kindex C-c C-f C-f | |
6bf7aab6 DL |
548 | @findex message-goto-fcc |
549 | Go to the @code{Fcc} header (@code{message-goto-fcc}). | |
550 | ||
551 | @item C-c C-f C-c | |
9d3d5390 | 552 | @kindex C-c C-f C-c |
6bf7aab6 DL |
553 | @findex message-goto-cc |
554 | Go to the @code{Cc} header (@code{message-goto-cc}). | |
555 | ||
556 | @item C-c C-f C-s | |
9d3d5390 | 557 | @kindex C-c C-f C-s |
6bf7aab6 DL |
558 | @findex message-goto-subject |
559 | Go to the @code{Subject} header (@code{message-goto-subject}). | |
560 | ||
561 | @item C-c C-f C-r | |
9d3d5390 | 562 | @kindex C-c C-f C-r |
6bf7aab6 DL |
563 | @findex message-goto-reply-to |
564 | Go to the @code{Reply-To} header (@code{message-goto-reply-to}). | |
565 | ||
566 | @item C-c C-f C-n | |
9d3d5390 | 567 | @kindex C-c C-f C-n |
6bf7aab6 DL |
568 | @findex message-goto-newsgroups |
569 | Go to the @code{Newsgroups} header (@code{message-goto-newsgroups}). | |
570 | ||
571 | @item C-c C-f C-d | |
9d3d5390 | 572 | @kindex C-c C-f C-d |
6bf7aab6 DL |
573 | @findex message-goto-distribution |
574 | Go to the @code{Distribution} header (@code{message-goto-distribution}). | |
575 | ||
23f87bed MB |
576 | @item C-c C-f C-o |
577 | @kindex C-c C-f C-o | |
6bf7aab6 DL |
578 | @findex message-goto-followup-to |
579 | Go to the @code{Followup-To} header (@code{message-goto-followup-to}). | |
580 | ||
581 | @item C-c C-f C-k | |
9d3d5390 | 582 | @kindex C-c C-f C-k |
6bf7aab6 DL |
583 | @findex message-goto-keywords |
584 | Go to the @code{Keywords} header (@code{message-goto-keywords}). | |
585 | ||
586 | @item C-c C-f C-u | |
9d3d5390 | 587 | @kindex C-c C-f C-u |
6bf7aab6 DL |
588 | @findex message-goto-summary |
589 | Go to the @code{Summary} header (@code{message-goto-summary}). | |
590 | ||
23f87bed MB |
591 | @item C-c C-f C-i |
592 | @kindex C-c C-f C-i | |
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}. | |
599 | ||
600 | @item C-c C-f C-a | |
601 | @kindex C-c C-f C-a | |
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}. | |
611 | ||
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. | |
615 | ||
616 | @end table | |
617 | ||
618 | @subsection Commands to change headers | |
619 | ||
620 | @table @kbd | |
621 | ||
622 | @item C-c C-o | |
623 | @kindex C-c C-o | |
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}). | |
628 | ||
629 | @item C-c C-t | |
630 | @kindex C-c C-t | |
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}). | |
635 | ||
636 | @item C-c C-n | |
637 | @kindex C-c C-n | |
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}). | |
642 | ||
643 | @item C-c C-l | |
644 | @kindex C-c C-l | |
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. | |
648 | ||
649 | @item C-c M-n | |
650 | @kindex C-c M-n | |
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. | |
656 | ||
657 | @item M-x message-insert-importance-high | |
658 | @kindex M-x message-insert-importance-high | |
659 | @findex message-insert-importance-high | |
660 | @cindex Importance | |
661 | Insert an @samp{Importance} header with a value of @samp{high}, | |
662 | deleting headers if necessary. | |
663 | ||
664 | @item M-x message-insert-importance-low | |
665 | @kindex M-x message-insert-importance-low | |
666 | @findex message-insert-importance-low | |
667 | @cindex Importance | |
668 | Insert an @samp{Importance} header with a value of @samp{low}, deleting | |
669 | headers if necessary. | |
670 | ||
671 | @item C-c C-f s | |
672 | @kindex C-c C-f s | |
673 | @findex message-change-subject | |
674 | @cindex 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}). | |
679 | ||
680 | @item C-c C-f x | |
681 | @kindex C-c C-f x | |
682 | @findex message-cross-post-followup-to | |
683 | @vindex message-cross-post-default | |
684 | @cindex X-Post | |
685 | @cindex cross-post | |
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 | |
691 | cross-posted. | |
692 | ||
693 | @item C-c C-f t | |
694 | @kindex C-c C-f t | |
695 | @findex message-reduce-to-to-cc | |
696 | Replace contents of @samp{To} header with contents of @samp{Cc} or | |
697 | @samp{Bcc} header. | |
698 | ||
699 | @item C-c C-f w | |
700 | @kindex C-c C-f w | |
701 | @findex message-insert-wide-reply | |
702 | Insert @samp{To} and @samp{Cc} headers as if you were doing a wide | |
703 | reply. | |
704 | ||
705 | @item C-c C-f a | |
706 | @kindex C-c C-f a | |
707 | @findex message-add-archive-header | |
708 | @vindex message-archive-header | |
709 | @vindex message-archive-note | |
710 | @cindex X-No-Archive | |
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 | |
716 | @code{nil}. | |
717 | ||
6bf7aab6 DL |
718 | @end table |
719 | ||
720 | ||
721 | @node Movement | |
722 | @section Movement | |
723 | ||
724 | @table @kbd | |
725 | @item C-c C-b | |
9d3d5390 | 726 | @kindex C-c C-b |
6bf7aab6 DL |
727 | @findex message-goto-body |
728 | Move to the beginning of the body of the message | |
9d3d5390 | 729 | (@code{message-goto-body}). |
6bf7aab6 DL |
730 | |
731 | @item C-c C-i | |
9d3d5390 | 732 | @kindex C-c C-i |
6bf7aab6 DL |
733 | @findex message-goto-signature |
734 | Move to the signature of the message (@code{message-goto-signature}). | |
735 | ||
23f87bed MB |
736 | @item C-a |
737 | @kindex C-a | |
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 behaviour can be disabled by toggling | |
743 | the variable @code{message-beginning-of-line}. | |
744 | ||
6bf7aab6 DL |
745 | @end table |
746 | ||
747 | ||
748 | @node Insertion | |
749 | @section Insertion | |
750 | ||
751 | @table @kbd | |
752 | ||
753 | @item C-c C-y | |
9d3d5390 | 754 | @kindex C-c C-y |
6bf7aab6 DL |
755 | @findex message-yank-original |
756 | Yank the message that's being replied to into the message buffer | |
9d3d5390 DL |
757 | (@code{message-yank-original}). |
758 | ||
718fb8a1 EZ |
759 | @item C-c C-M-y |
760 | @kindex C-c C-M-y | |
9d3d5390 DL |
761 | @findex message-yank-buffer |
762 | Prompt for a buffer name and yank the contents of that buffer into the | |
763 | message buffer (@code{message-yank-buffer}). | |
6bf7aab6 DL |
764 | |
765 | @item C-c C-q | |
9d3d5390 | 766 | @kindex C-c C-q |
6bf7aab6 DL |
767 | @findex message-fill-yanked-message |
768 | Fill the yanked message (@code{message-fill-yanked-message}). Warning: | |
769 | Can severely mess up the yanked text if its quoting conventions are | |
770 | strange. You'll quickly get a feel for when it's safe, though. Anyway, | |
771 | just remember that @kbd{C-x u} (@code{undo}) is available and you'll be | |
772 | all right. | |
773 | ||
6bf7aab6 | 774 | @item C-c C-w |
9d3d5390 | 775 | @kindex C-c C-w |
6bf7aab6 DL |
776 | @findex message-insert-signature |
777 | Insert a signature at the end of the buffer | |
9d3d5390 DL |
778 | (@code{message-insert-signature}). |
779 | ||
780 | @item C-c M-h | |
781 | @kindex C-c M-h | |
782 | @findex message-insert-headers | |
783 | Insert the message headers (@code{message-insert-headers}). | |
6bf7aab6 | 784 | |
23f87bed MB |
785 | @item C-c M-m |
786 | @kindex C-c M-m | |
787 | @findex message-mark-inserted-region | |
788 | Mark some region in the current article with enclosing tags. | |
789 | See @code{message-mark-insert-begin} and @code{message-mark-insert-end}. | |
6bf7aab6 | 790 | |
23f87bed MB |
791 | @item C-c M-f |
792 | @kindex C-c M-f | |
793 | @findex message-mark-insert-file | |
794 | Insert a file in the current article with enclosing tags. | |
795 | See @code{message-mark-insert-begin} and @code{message-mark-insert-end}. | |
6bf7aab6 DL |
796 | |
797 | @end table | |
798 | ||
6bf7aab6 | 799 | |
9d3d5390 DL |
800 | @node MIME |
801 | @section MIME | |
802 | @cindex MML | |
803 | @cindex MIME | |
804 | @cindex multipart | |
805 | @cindex attachment | |
806 | ||
23f87bed MB |
807 | Message is a @acronym{MIME}-compliant posting agent. The user generally |
808 | doesn't have to do anything to make the @acronym{MIME} happen---Message will | |
9d3d5390 DL |
809 | automatically add the @code{Content-Type} and |
810 | @code{Content-Transfer-Encoding} headers. | |
811 | ||
812 | The most typical thing users want to use the multipart things in | |
23f87bed MB |
813 | @acronym{MIME} for is to add ``attachments'' to mail they send out. This can |
814 | be done with the @kbd{C-c C-a} command, which will prompt for a file | |
815 | name and a @acronym{MIME} type. | |
9d3d5390 | 816 | |
23f87bed | 817 | You can also create arbitrarily complex multiparts using the @acronym{MML} |
9d3d5390 DL |
818 | language (@pxref{Composing, , Composing, emacs-mime, The Emacs MIME |
819 | Manual}). | |
820 | ||
23f87bed MB |
821 | @node IDNA |
822 | @section IDNA | |
823 | @cindex IDNA | |
824 | @cindex internationalized domain names | |
825 | @cindex non-ascii domain names | |
826 | ||
827 | Message is a @acronym{IDNA}-compliant posting agent. The user | |
828 | generally doesn't have to do anything to make the @acronym{IDNA} | |
829 | happen---Message will encode non-@acronym{ASCII} domain names in @code{From}, | |
830 | @code{To}, and @code{Cc} headers automatically. | |
831 | ||
832 | Until @acronym{IDNA} becomes more well known, Message queries you | |
833 | whether @acronym{IDNA} encoding of the domain name really should | |
834 | occur. Some users might not be aware that domain names can contain | |
835 | non-@acronym{ASCII} now, so this gives them a safety net if they accidently | |
836 | typed a non-@acronym{ASCII} domain name. | |
837 | ||
838 | @vindex message-use-idna | |
839 | The @code{message-use-idna} variable control whether @acronym{IDNA} is | |
840 | used. If the variable is @code{nil} no @acronym{IDNA} encoding will | |
841 | ever happen, if it is set to the symbol @code{ask} the user will be | |
842 | queried (the default), and if set to @code{t} @acronym{IDNA} encoding | |
843 | happens automatically. | |
844 | ||
845 | @findex message-idna-to-ascii-rhs | |
846 | If you want to experiment with the @acronym{IDNA} encoding, you can | |
847 | invoke @kbd{M-x message-idna-to-ascii-rhs RET} in the message buffer | |
848 | to have the non-@acronym{ASCII} domain names encoded while you edit the message. | |
849 | ||
850 | Note that you must have @uref{http://www.gnu.org/software/libidn/, GNU | |
851 | Libidn} installed in order to use this functionality. | |
852 | ||
853 | @node Security | |
854 | @section Security | |
855 | @cindex Security | |
856 | @cindex S/MIME | |
857 | @cindex PGP | |
858 | @cindex PGP/MIME | |
859 | @cindex sign | |
860 | @cindex encrypt | |
861 | @cindex secure | |
862 | ||
863 | Using the @acronym{MML} language, Message is able to create digitally | |
864 | signed and digitally encrypted messages. Message (or rather | |
865 | @acronym{MML}) currently support @acronym{PGP} (RFC 1991), | |
866 | @acronym{PGP/MIME} (RFC 2015/3156) and @acronym{S/MIME}. Instructing | |
867 | @acronym{MML} to perform security operations on a @acronym{MIME} part is | |
868 | done using the @kbd{C-c C-m s} key map for signing and the @kbd{C-c C-m | |
869 | c} key map for encryption, as follows. | |
870 | ||
871 | @table @kbd | |
872 | ||
873 | @item C-c C-m s s | |
874 | @kindex C-c C-m s s | |
875 | @findex mml-secure-message-sign-smime | |
876 | ||
877 | Digitally sign current message using @acronym{S/MIME}. | |
878 | ||
879 | @item C-c C-m s o | |
880 | @kindex C-c C-m s o | |
881 | @findex mml-secure-message-sign-pgp | |
882 | ||
883 | Digitally sign current message using @acronym{PGP}. | |
884 | ||
885 | @item C-c C-m s p | |
886 | @kindex C-c C-m s p | |
887 | @findex mml-secure-message-sign-pgpmime | |
888 | ||
889 | Digitally sign current message using @acronym{PGP/MIME}. | |
890 | ||
891 | @item C-c C-m c s | |
892 | @kindex C-c C-m c s | |
893 | @findex mml-secure-message-encrypt-smime | |
894 | ||
895 | Digitally encrypt current message using @acronym{S/MIME}. | |
896 | ||
897 | @item C-c C-m c o | |
898 | @kindex C-c C-m c o | |
899 | @findex mml-secure-message-encrypt-pgp | |
900 | ||
901 | Digitally encrypt current message using @acronym{PGP}. | |
902 | ||
903 | @item C-c C-m c p | |
904 | @kindex C-c C-m c p | |
905 | @findex mml-secure-message-encrypt-pgpmime | |
906 | ||
907 | Digitally encrypt current message using @acronym{PGP/MIME}. | |
908 | ||
909 | @item C-c C-m C-n | |
910 | @kindex C-c C-m C-n | |
911 | @findex mml-unsecure-message | |
912 | Remove security related @acronym{MML} tags from message. | |
913 | ||
914 | @end table | |
915 | ||
916 | These commands do not immediately sign or encrypt the message, they | |
917 | merely insert the proper @acronym{MML} secure tag to instruct the | |
918 | @acronym{MML} engine to perform that operation when the message is | |
919 | actually sent. They may perform other operations too, such as locating | |
920 | and retrieving a @acronym{S/MIME} certificate of the person you wish to | |
921 | send encrypted mail to. When the mml parsing engine converts your | |
922 | @acronym{MML} into a properly encoded @acronym{MIME} message, the secure | |
923 | tag will be replaced with either a part or a multipart tag. If your | |
924 | message contains other mml parts, a multipart tag will be used; if no | |
925 | other parts are present in your message a single part tag will be used. | |
926 | This way, message mode will do the Right Thing (TM) with | |
927 | signed/encrypted multipart messages. | |
928 | ||
929 | Since signing and especially encryption often is used when sensitive | |
930 | information is sent, you may want to have some way to ensure that your | |
931 | mail is actually signed or encrypted. After invoking the above | |
932 | sign/encrypt commands, it is possible to preview the raw article by | |
933 | using @kbd{C-u C-c RET P} (@code{mml-preview}). Then you can | |
934 | verify that your long rant about what your ex-significant other or | |
935 | whomever actually did with that funny looking person at that strange | |
936 | party the other night, actually will be sent encrypted. | |
937 | ||
938 | @emph{Note!} Neither @acronym{PGP/MIME} nor @acronym{S/MIME} encrypt/signs | |
939 | RFC822 headers. They only operate on the @acronym{MIME} object. Keep this | |
940 | in mind before sending mail with a sensitive Subject line. | |
941 | ||
942 | By default, when encrypting a message, Gnus will use the | |
943 | ``signencrypt'' mode, which means the message is both signed and | |
944 | encrypted. If you would like to disable this for a particular | |
945 | message, give the @code{mml-secure-message-encrypt-*} command a prefix | |
946 | argument, e.g., @kbd{C-u C-c C-m c p}. | |
947 | ||
948 | Actually using the security commands above is not very difficult. At | |
949 | least not compared with making sure all involved programs talk with each | |
950 | other properly. Thus, we now describe what external libraries or | |
951 | programs are required to make things work, and some small general hints. | |
952 | ||
953 | @subsection Using S/MIME | |
954 | ||
955 | @emph{Note!} This section assume you have a basic familiarity with | |
956 | modern cryptography, @acronym{S/MIME}, various PKCS standards, OpenSSL and | |
957 | so on. | |
958 | ||
959 | The @acronym{S/MIME} support in Message (and @acronym{MML}) require | |
960 | OpenSSL. OpenSSL performs the actual @acronym{S/MIME} sign/encrypt | |
961 | operations. OpenSSL can be found at @uref{http://www.openssl.org/}. | |
962 | OpenSSL 0.9.6 and later should work. Version 0.9.5a cannot extract mail | |
963 | addresses from certificates, and it insert a spurious CR character into | |
964 | @acronym{MIME} separators so you may wish to avoid it if you would like | |
965 | to avoid being regarded as someone who send strange mail. (Although by | |
966 | sending @acronym{S/MIME} messages you've probably already lost that | |
967 | contest.) | |
968 | ||
969 | To be able to send encrypted mail, a personal certificate is not | |
970 | required. Message (@acronym{MML}) need a certificate for the person to whom you | |
971 | wish to communicate with though. You're asked for this when you type | |
972 | @kbd{C-c C-m c s}. Currently there are two ways to retrieve this | |
973 | certificate, from a local file or from DNS. If you chose a local | |
974 | file, it need to contain a X.509 certificate in @acronym{PEM} format. | |
975 | If you chose DNS, you're asked for the domain name where the | |
976 | certificate is stored, the default is a good guess. To my belief, | |
977 | Message (@acronym{MML}) is the first mail agent in the world to support | |
978 | retrieving @acronym{S/MIME} certificates from DNS, so you're not | |
979 | likely to find very many certificates out there. At least there | |
980 | should be one, stored at the domain @code{simon.josefsson.org}. LDAP | |
981 | is a more popular method of distributing certificates, support for it | |
982 | is planned. (Meanwhile, you can use @code{ldapsearch} from the | |
983 | command line to retrieve a certificate into a file and use it.) | |
984 | ||
985 | As for signing messages, OpenSSL can't perform signing operations | |
986 | without some kind of configuration. Especially, you need to tell it | |
987 | where your private key and your certificate is stored. @acronym{MML} | |
988 | uses an Emacs interface to OpenSSL, aptly named @code{smime.el}, and it | |
989 | contain a @code{custom} group used for this configuration. So, try | |
990 | @kbd{M-x customize-group RET smime RET} and look around. | |
991 | ||
992 | Currently there is no support for talking to a CA (or RA) to create | |
993 | your own certificate. None is planned either. You need to do this | |
994 | manually with OpenSSL or using some other program. I used Netscape | |
995 | and got a free @acronym{S/MIME} certificate from one of the big CA's on the | |
996 | net. Netscape is able to export your private key and certificate in | |
997 | PKCS #12 format. Use OpenSSL to convert this into a plain X.509 | |
998 | certificate in PEM format as follows. | |
999 | ||
1000 | @example | |
1001 | $ openssl pkcs12 -in ns.p12 -clcerts -nodes > key+cert.pem | |
1002 | @end example | |
1003 | ||
1004 | The @file{key+cert.pem} file should be pointed to from the | |
1005 | @code{smime-keys} variable. You should now be able to send signed mail. | |
1006 | ||
1007 | @emph{Note!} Your private key is now stored unencrypted in the file, | |
1008 | so take care in handling it. Storing encrypted keys on the disk are | |
1009 | supported, and Gnus will ask you for a passphrase before invoking | |
1010 | OpenSSL. Read the OpenSSL documentation for how to achieve this. If | |
1011 | you use unencrypted keys (e.g., if they are on a secure storage, or if | |
1012 | you are on a secure single user machine) simply press @code{RET} at | |
1013 | the passphrase prompt. | |
1014 | ||
1015 | @subsection Using PGP/MIME | |
1016 | ||
1017 | @acronym{PGP/MIME} requires an external OpenPGP implementation, such | |
1018 | as @uref{http://www.gnupg.org/, GNU Privacy Guard}. Pre-OpenPGP | |
1019 | implementations such as PGP 2.x and PGP 5.x are also supported. One | |
1020 | Emacs interface to the PGP implementations, PGG (@pxref{Top, ,PGG, | |
1021 | pgg, PGG Manual}), is included, but Mailcrypt and Florian Weimer's | |
1022 | @code{gpg.el} are also supported. | |
1023 | ||
1024 | @vindex gpg-temp-directory | |
1025 | Note, if you are using the @code{gpg.el} you must make sure that the | |
1026 | directory specified by @code{gpg-temp-directory} have permissions | |
1027 | 0700. | |
1028 | ||
1029 | Creating your own key is described in detail in the documentation of | |
1030 | your PGP implementation, so we refer to it. | |
1031 | ||
1032 | If you have imported your old PGP 2.x key into GnuPG, and want to send | |
1033 | signed and encrypted messages to your fellow PGP 2.x users, you'll | |
1034 | discover that the receiver cannot understand what you send. One | |
1035 | solution is to use PGP 2.x instead (i.e., if you use @code{pgg}, set | |
1036 | @code{pgg-default-scheme} to @code{pgp}). If you do want to use | |
1037 | GnuPG, you can use a compatibility script called @code{gpg-2comp} | |
1038 | available from | |
1039 | @uref{http://muppet.faveve.uni-stuttgart.de/~gero/gpg-2comp/}. You | |
1040 | could also convince your fellow PGP 2.x users to convert to GnuPG. | |
1041 | @vindex mml-signencrypt-style-alist | |
1042 | As a final workaround, you can make the sign and encryption work in | |
1043 | two steps; separately sign, then encrypt a message. If you would like | |
1044 | to change this behavior you can customize the | |
1045 | @code{mml-signencrypt-style-alist} variable. For example: | |
1046 | ||
1047 | @lisp | |
1048 | (setq mml-signencrypt-style-alist '(("smime" separate) | |
1049 | ("pgp" separate) | |
1050 | ("pgpauto" separate) | |
1051 | ("pgpmime" separate))) | |
1052 | @end lisp | |
1053 | ||
1054 | This causes to sign and encrypt in two passes, thus generating a | |
1055 | message that can be understood by PGP version 2. | |
1056 | ||
1057 | (Refer to @uref{http://www.gnupg.org/gph/en/pgp2x.html} for more | |
1058 | information about the problem.) | |
6bf7aab6 DL |
1059 | |
1060 | @node Various Commands | |
1061 | @section Various Commands | |
1062 | ||
1063 | @table @kbd | |
1064 | ||
1065 | @item C-c C-r | |
9d3d5390 | 1066 | @kindex C-c C-r |
6bf7aab6 DL |
1067 | @findex message-caesar-buffer-body |
1068 | Caesar rotate (aka. rot13) the current message | |
1069 | (@code{message-caesar-buffer-body}). If narrowing is in effect, just | |
1070 | rotate the visible portion of the buffer. A numerical prefix says how | |
1071 | many places to rotate the text. The default is 13. | |
1072 | ||
1073 | @item C-c C-e | |
1074 | @kindex C-c C-e | |
1075 | @findex message-elide-region | |
23f87bed | 1076 | @vindex message-elide-ellipsis |
6bf7aab6 | 1077 | Elide the text between point and mark (@code{message-elide-region}). |
9d3d5390 | 1078 | The text is killed and replaced with the contents of the variable |
23f87bed | 1079 | @code{message-elide-ellipsis}. The default value is to use an ellipsis |
9d3d5390 | 1080 | (@samp{[...]}). |
6bf7aab6 DL |
1081 | |
1082 | @item C-c C-z | |
1083 | @kindex C-c C-x | |
1084 | @findex message-kill-to-signature | |
1085 | Kill all the text up to the signature, or if that's missing, up to the | |
1086 | end of the message (@code{message-kill-to-signature}). | |
1087 | ||
1088 | @item C-c C-v | |
1089 | @kindex C-c C-v | |
1090 | @findex message-delete-not-region | |
1091 | Delete all text in the body of the message that is outside the region | |
1092 | (@code{message-delete-not-region}). | |
1093 | ||
1094 | @item M-RET | |
1095 | @kindex M-RET | |
23f87bed | 1096 | @findex message-newline-and-reformat |
6bf7aab6 DL |
1097 | Insert four newlines, and then reformat if inside quoted text. |
1098 | ||
1099 | Here's an example: | |
1100 | ||
1101 | @example | |
1102 | > This is some quoted text. And here's more quoted text. | |
1103 | @end example | |
1104 | ||
1105 | If point is before @samp{And} and you press @kbd{M-RET}, you'll get: | |
1106 | ||
1107 | @example | |
1108 | > This is some quoted text. | |
1109 | ||
1110 | * | |
1111 | ||
1112 | > And here's more quoted text. | |
1113 | @end example | |
1114 | ||
9d3d5390 | 1115 | @samp{*} says where point will be placed. |
6bf7aab6 | 1116 | |
6bf7aab6 DL |
1117 | @item C-c M-r |
1118 | @kindex C-c M-r | |
1119 | @findex message-rename-buffer | |
1120 | Rename the buffer (@code{message-rename-buffer}). If given a prefix, | |
1121 | prompt for a new buffer name. | |
1122 | ||
23f87bed MB |
1123 | @item TAB |
1124 | @kindex TAB | |
1125 | @findex message-tab | |
1126 | @vindex message-tab-body-function | |
1127 | If non-@code{nil} execute the function specified in | |
1128 | @code{message-tab-body-function}. Otherwise use the function bound to | |
1129 | @kbd{TAB} in @code{text-mode-map} or @code{global-map}. | |
1130 | ||
6bf7aab6 DL |
1131 | @end table |
1132 | ||
1133 | ||
1134 | @node Sending | |
1135 | @section Sending | |
1136 | ||
1137 | @table @kbd | |
1138 | @item C-c C-c | |
9d3d5390 | 1139 | @kindex C-c C-c |
6bf7aab6 DL |
1140 | @findex message-send-and-exit |
1141 | Send the message and bury the current buffer | |
9d3d5390 | 1142 | (@code{message-send-and-exit}). |
6bf7aab6 DL |
1143 | |
1144 | @item C-c C-s | |
9d3d5390 | 1145 | @kindex C-c C-s |
6bf7aab6 | 1146 | @findex message-send |
9d3d5390 | 1147 | Send the message (@code{message-send}). |
6bf7aab6 DL |
1148 | |
1149 | @item C-c C-d | |
1150 | @kindex C-c C-d | |
1151 | @findex message-dont-send | |
1152 | Bury the message buffer and exit (@code{message-dont-send}). | |
1153 | ||
1154 | @item C-c C-k | |
1155 | @kindex C-c C-k | |
1156 | @findex message-kill-buffer | |
1157 | Kill the message buffer and exit (@code{message-kill-buffer}). | |
1158 | ||
1159 | @end table | |
1160 | ||
1161 | ||
1162 | ||
1163 | @node Mail Aliases | |
1164 | @section Mail Aliases | |
1165 | @cindex mail aliases | |
1166 | @cindex aliases | |
1167 | ||
1168 | @vindex message-mail-alias-type | |
1169 | The @code{message-mail-alias-type} variable controls what type of mail | |
1170 | alias expansion to use. Currently only one form is supported---Message | |
1171 | uses @code{mailabbrev} to handle mail aliases. If this variable is | |
1172 | @code{nil}, no mail alias expansion will be performed. | |
1173 | ||
1174 | @code{mailabbrev} works by parsing the @file{/etc/mailrc} and | |
1175 | @file{~/.mailrc} files. These files look like: | |
1176 | ||
1177 | @example | |
1178 | alias lmi "Lars Magne Ingebrigtsen <larsi@@ifi.uio.no>" | |
1179 | alias ding "ding@@ifi.uio.no (ding mailing list)" | |
1180 | @end example | |
1181 | ||
1182 | After adding lines like this to your @file{~/.mailrc} file, you should | |
1183 | be able to just write @samp{lmi} in the @code{To} or @code{Cc} (and so | |
1184 | on) headers and press @kbd{SPC} to expand the alias. | |
1185 | ||
1186 | No expansion will be performed upon sending of the message---all | |
1187 | expansions have to be done explicitly. | |
1188 | ||
1189 | ||
dda5808a DL |
1190 | @node Spelling |
1191 | @section Spelling | |
1192 | @cindex spelling | |
1193 | @findex ispell-message | |
1194 | ||
1195 | There are two popular ways to have Emacs spell-check your messages: | |
1196 | @code{ispell} and @code{flyspell}. @code{ispell} is the older and | |
1197 | probably more popular package. You typically first write the message, | |
1198 | and then run the entire thing through @code{ispell} and fix all the | |
1199 | typos. To have this happen automatically when you send a message, put | |
1200 | something like the following in your @file{.emacs} file: | |
1201 | ||
1202 | @lisp | |
1203 | (add-hook 'message-send-hook 'ispell-message) | |
1204 | @end lisp | |
1205 | ||
1206 | @vindex ispell-message-dictionary-alist | |
1207 | If you're in the habit of writing in different languages, this can be | |
1208 | controlled by the @code{ispell-message-dictionary-alist} variable: | |
1209 | ||
1210 | @lisp | |
1211 | (setq ispell-message-dictionary-alist | |
1212 | '(("^Newsgroups:.*\\bde\\." . "deutsch8") | |
23f87bed | 1213 | (".*" . "default"))) |
dda5808a DL |
1214 | @end lisp |
1215 | ||
1216 | @code{ispell} depends on having the external @samp{ispell} command | |
1217 | installed. | |
1218 | ||
1219 | The other popular method is using @code{flyspell}. This package checks | |
1220 | your spelling while you're writing, and marks any mis-spelled words in | |
1221 | various ways. | |
1222 | ||
1223 | To use @code{flyspell}, put something like the following in your | |
1224 | @file{.emacs} file: | |
1225 | ||
1226 | @lisp | |
1227 | (defun my-message-setup-routine () | |
1228 | (flyspell-mode 1)) | |
1229 | (add-hook 'message-setup-hook 'my-message-setup-routine) | |
1230 | @end lisp | |
1231 | ||
1232 | @code{flyspell} depends on having the external @samp{ispell} command | |
1233 | installed. | |
1234 | ||
6bf7aab6 DL |
1235 | |
1236 | @node Variables | |
1237 | @chapter Variables | |
1238 | ||
1239 | @menu | |
1240 | * Message Headers:: General message header stuff. | |
1241 | * Mail Headers:: Customizing mail headers. | |
1242 | * Mail Variables:: Other mail variables. | |
1243 | * News Headers:: Customizing news headers. | |
1244 | * News Variables:: Other news variables. | |
23f87bed | 1245 | * Insertion Variables:: Customizing how things are inserted. |
6bf7aab6 DL |
1246 | * Various Message Variables:: Other message variables. |
1247 | * Sending Variables:: Variables for sending. | |
1248 | * Message Buffers:: How Message names its buffers. | |
1249 | * Message Actions:: Actions to be performed when exiting. | |
1250 | @end menu | |
1251 | ||
1252 | ||
1253 | @node Message Headers | |
1254 | @section Message Headers | |
1255 | ||
1256 | Message is quite aggressive on the message generation front. It has to | |
1257 | be -- it's a combined news and mail agent. To be able to send combined | |
1258 | messages, it has to generate all headers itself (instead of letting the | |
1259 | mail/news system do it) to ensure that mail and news copies of messages | |
1260 | look sufficiently similar. | |
1261 | ||
1262 | @table @code | |
1263 | ||
1264 | @item message-generate-headers-first | |
1265 | @vindex message-generate-headers-first | |
23f87bed MB |
1266 | If @code{t}, generate all required headers before starting to |
1267 | compose the message. This can also be a list of headers to generate: | |
1268 | ||
1269 | @lisp | |
1270 | (setq message-generate-headers-first | |
1271 | '(References)) | |
1272 | @end lisp | |
74ac26b2 | 1273 | |
23f87bed MB |
1274 | @vindex message-required-headers |
1275 | The variables @code{message-required-headers}, | |
1276 | @code{message-required-mail-headers} and | |
1277 | @code{message-required-news-headers} specify which headers are | |
1278 | required. | |
1279 | ||
1280 | Note that some headers will be removed and re-generated before posting, | |
1281 | because of the variable @code{message-deletable-headers} (see below). | |
1282 | ||
1283 | @item message-draft-headers | |
1284 | @vindex message-draft-headers | |
1285 | When running Message from Gnus, the message buffers are associated | |
1286 | with a draft group. @code{message-draft-headers} says which headers | |
1287 | should be generated when a draft is written to the draft group. | |
6bf7aab6 DL |
1288 | |
1289 | @item message-from-style | |
1290 | @vindex message-from-style | |
1291 | Specifies how @code{From} headers should look. There are four valid | |
1292 | values: | |
1293 | ||
1294 | @table @code | |
1295 | @item nil | |
1296 | Just the address -- @samp{king@@grassland.com}. | |
1297 | ||
1298 | @item parens | |
1299 | @samp{king@@grassland.com (Elvis Parsley)}. | |
1300 | ||
1301 | @item angles | |
1302 | @samp{Elvis Parsley <king@@grassland.com>}. | |
1303 | ||
1304 | @item default | |
1305 | Look like @code{angles} if that doesn't require quoting, and | |
1306 | @code{parens} if it does. If even @code{parens} requires quoting, use | |
1307 | @code{angles} anyway. | |
1308 | ||
1309 | @end table | |
1310 | ||
1311 | @item message-deletable-headers | |
1312 | @vindex message-deletable-headers | |
1313 | Headers in this list that were previously generated by Message will be | |
1314 | deleted before posting. Let's say you post an article. Then you decide | |
1315 | to post it again to some other group, you naughty boy, so you jump back | |
1316 | to the @code{*post-buf*} buffer, edit the @code{Newsgroups} line, and | |
1317 | ship it off again. By default, this variable makes sure that the old | |
1318 | generated @code{Message-ID} is deleted, and a new one generated. If | |
1319 | this isn't done, the entire empire would probably crumble, anarchy would | |
1320 | prevail, and cats would start walking on two legs and rule the world. | |
9d3d5390 | 1321 | Allegedly. |
6bf7aab6 DL |
1322 | |
1323 | @item message-default-headers | |
1324 | @vindex message-default-headers | |
1325 | This string is inserted at the end of the headers in all message | |
1326 | buffers. | |
1327 | ||
1328 | @item message-subject-re-regexp | |
1329 | @vindex message-subject-re-regexp | |
23f87bed MB |
1330 | @cindex Aw |
1331 | @cindex Sv | |
1332 | @cindex Re | |
6bf7aab6 | 1333 | Responses to messages have subjects that start with @samp{Re: }. This |
dda5808a | 1334 | is @emph{not} an abbreviation of the English word ``response'', but is |
6bf7aab6 DL |
1335 | Latin, and means ``in response to''. Some illiterate nincompoops have |
1336 | failed to grasp this fact, and have ``internationalized'' their software | |
28665d46 | 1337 | to use abominations like @samp{Aw: } (``antwort'') or @samp{Sv: } |
6bf7aab6 DL |
1338 | (``svar'') instead, which is meaningless and evil. However, you may |
1339 | have to deal with users that use these evil tools, in which case you may | |
1340 | set this variable to a regexp that matches these prefixes. Myself, I | |
1341 | just throw away non-compliant mail. | |
1342 | ||
23f87bed MB |
1343 | Here's an example of a value to deal with these headers when |
1344 | responding to a message: | |
1345 | ||
1346 | @lisp | |
1347 | (setq message-subject-re-regexp | |
1348 | (concat | |
1349 | "^[ \t]*" | |
1350 | "\\(" | |
1351 | "\\(" | |
1352 | "[Aa][Nn][Tt][Ww]\\.?\\|" ; antw | |
1353 | "[Aa][Ww]\\|" ; aw | |
1354 | "[Ff][Ww][Dd]?\\|" ; fwd | |
1355 | "[Oo][Dd][Pp]\\|" ; odp | |
1356 | "[Rr][Ee]\\|" ; re | |
1357 | "[Rr][\311\351][Ff]\\.?\\|" ; ref | |
1358 | "[Ss][Vv]" ; sv | |
1359 | "\\)" | |
1360 | "\\(\\[[0-9]*\\]\\)" | |
1361 | "*:[ \t]*" | |
1362 | "\\)" | |
1363 | "*[ \t]*" | |
1364 | )) | |
1365 | @end lisp | |
1366 | ||
1367 | @item message-subject-trailing-was-query | |
1368 | @vindex message-subject-trailing-was-query | |
1369 | @vindex message-subject-trailing-was-ask-regexp | |
1370 | @vindex message-subject-trailing-was-regexp | |
1371 | Controls what to do with trailing @samp{(was: <old subject>)} in subject | |
1372 | lines. If @code{nil}, leave the subject unchanged. If it is the symbol | |
1373 | @code{ask}, query the user what do do. In this case, the subject is | |
1374 | matched against @code{message-subject-trailing-was-ask-regexp}. If | |
1375 | @code{message-subject-trailing-was-query} is t, always strip the | |
1376 | trailing old subject. In this case, | |
1377 | @code{message-subject-trailing-was-regexp} is used. | |
1378 | ||
8ac08dea DL |
1379 | @item message-alternative-emails |
1380 | @vindex message-alternative-emails | |
1381 | A regexp to match the alternative email addresses. The first matched | |
1382 | address (not primary one) is used in the @code{From} field. | |
1383 | ||
23f87bed MB |
1384 | @item message-allow-no-recipients |
1385 | @vindex message-allow-no-recipients | |
1386 | Specifies what to do when there are no recipients other than | |
1387 | @code{Gcc} or @code{Fcc}. If it is @code{always}, the posting is | |
1388 | allowed. If it is @code{never}, the posting is not allowed. If it is | |
1389 | @code{ask} (the default), you are prompted. | |
1390 | ||
1391 | @item message-hidden-headers | |
1392 | @vindex message-hidden-headers | |
1393 | A regexp, a list of regexps, or a list where the first element is | |
1394 | @code{not} and the rest are regexps. It says which headers to keep | |
1395 | hidden when composing a message. | |
1396 | ||
1397 | @lisp | |
1398 | (setq message-hidden-headers | |
1399 | '(not "From" "Subject" "To" "Cc" "Newsgroups")) | |
1400 | @end lisp | |
1401 | ||
1402 | @item message-header-synonyms | |
1403 | @vindex message-header-synonyms | |
1404 | A list of lists of header synonyms. E.g., if this list contains a | |
1405 | member list with elements @code{Cc} and @code{To}, then | |
1406 | @code{message-carefully-insert-headers} will not insert a @code{To} | |
1407 | header when the message is already @code{Cc}ed to the recipient. | |
1408 | ||
6bf7aab6 DL |
1409 | @end table |
1410 | ||
1411 | ||
1412 | @node Mail Headers | |
1413 | @section Mail Headers | |
1414 | ||
1415 | @table @code | |
1416 | @item message-required-mail-headers | |
1417 | @vindex message-required-mail-headers | |
1418 | @xref{News Headers}, for the syntax of this variable. It is | |
1419 | @code{(From Date Subject (optional . In-Reply-To) Message-ID Lines | |
dda5808a | 1420 | (optional . User-Agent))} by default. |
6bf7aab6 DL |
1421 | |
1422 | @item message-ignored-mail-headers | |
1423 | @vindex message-ignored-mail-headers | |
1424 | Regexp of headers to be removed before mailing. The default is | |
23f87bed | 1425 | @samp{^[GF]cc:\\|^Resent-Fcc:\\|^Xref:\\|^X-Draft-From:}. |
6bf7aab6 DL |
1426 | |
1427 | @item message-default-mail-headers | |
1428 | @vindex message-default-mail-headers | |
1429 | This string is inserted at the end of the headers in all message | |
1430 | buffers that are initialized as mail. | |
1431 | ||
1432 | @end table | |
1433 | ||
1434 | ||
1435 | @node Mail Variables | |
9d3d5390 | 1436 | @section Mail Variables |
6bf7aab6 DL |
1437 | |
1438 | @table @code | |
1439 | @item message-send-mail-function | |
1440 | @vindex message-send-mail-function | |
23f87bed MB |
1441 | @findex message-send-mail-with-sendmail |
1442 | @findex message-send-mail-with-mh | |
1443 | @findex message-send-mail-with-qmail | |
1444 | @findex message-smtpmail-send-it | |
1445 | @findex smtpmail-send-it | |
1446 | @findex feedmail-send-it | |
6bf7aab6 | 1447 | Function used to send the current buffer as mail. The default is |
23f87bed MB |
1448 | @code{message-send-mail-with-sendmail}. Other valid values include |
1449 | @code{message-send-mail-with-mh}, @code{message-send-mail-with-qmail}, | |
1450 | @code{message-smtpmail-send-it}, @code{smtpmail-send-it} and | |
1451 | @code{feedmail-send-it}. | |
6bf7aab6 DL |
1452 | |
1453 | @item message-mh-deletable-headers | |
1454 | @vindex message-mh-deletable-headers | |
1455 | Most versions of MH doesn't like being fed messages that contain the | |
1456 | headers in this variable. If this variable is non-@code{nil} (which is | |
1457 | the default), these headers will be removed before mailing when sending | |
1458 | messages via MH. Set it to @code{nil} if your MH can handle these | |
1459 | headers. | |
1460 | ||
23f87bed MB |
1461 | @item message-qmail-inject-program |
1462 | @vindex message-qmail-inject-program | |
1463 | @cindex qmail | |
1464 | Location of the qmail-inject program. | |
1465 | ||
1466 | @item message-qmail-inject-args | |
1467 | @vindex message-qmail-inject-args | |
1468 | Arguments passed to qmail-inject programs. | |
1469 | This should be a list of strings, one string for each argument. It | |
1470 | may also be a function. | |
1471 | ||
1472 | For e.g., if you wish to set the envelope sender address so that bounces | |
1473 | go to the right place or to deal with listserv's usage of that address, you | |
1474 | might set this variable to @code{'("-f" "you@@some.where")}. | |
1475 | ||
1476 | @item message-sendmail-f-is-evil | |
1477 | @vindex message-sendmail-f-is-evil | |
1478 | @cindex sendmail | |
1479 | Non-@code{nil} means don't add @samp{-f username} to the sendmail | |
1480 | command line. Doing so would be even more evil than leaving it out. | |
1481 | ||
1482 | @item message-sendmail-envelope-from | |
1483 | @vindex message-sendmail-envelope-from | |
1484 | When @code{message-sendmail-f-is-evil} is @code{nil}, this specifies | |
1485 | the address to use in the @acronym{SMTP} envelope. If it is | |
1486 | @code{nil}, use @code{user-mail-address}. If it is the symbol | |
1487 | @code{header}, use the @samp{From} header of the message. | |
1488 | ||
1489 | @item message-mailer-swallows-blank-line | |
1490 | @vindex message-mailer-swallows-blank-line | |
1491 | Set this to non-@code{nil} if the system's mailer runs the header and | |
1492 | body together. (This problem exists on SunOS 4 when sendmail is run | |
1493 | in remote mode.) The value should be an expression to test whether | |
1494 | the problem will actually occur. | |
1495 | ||
dda5808a DL |
1496 | @item message-send-mail-partially-limit |
1497 | @vindex message-send-mail-partially-limit | |
23f87bed MB |
1498 | @cindex split large message |
1499 | The limitation of messages sent as message/partial. The lower bound | |
1500 | of message size in characters, beyond which the message should be sent | |
1501 | in several parts. If it is @code{nil}, the size is unlimited. | |
dda5808a | 1502 | |
6bf7aab6 DL |
1503 | @end table |
1504 | ||
1505 | ||
1506 | @node News Headers | |
1507 | @section News Headers | |
1508 | ||
1509 | @vindex message-required-news-headers | |
1510 | @code{message-required-news-headers} a list of header symbols. These | |
1511 | headers will either be automatically generated, or, if that's | |
1512 | impossible, they will be prompted for. The following symbols are valid: | |
1513 | ||
1514 | @table @code | |
1515 | ||
1516 | @item From | |
1517 | @cindex From | |
1518 | @findex user-full-name | |
1519 | @findex user-mail-address | |
1520 | This required header will be filled out with the result of the | |
1521 | @code{message-make-from} function, which depends on the | |
1522 | @code{message-from-style}, @code{user-full-name}, | |
1523 | @code{user-mail-address} variables. | |
1524 | ||
1525 | @item Subject | |
1526 | @cindex Subject | |
9d3d5390 | 1527 | This required header will be prompted for if not present already. |
6bf7aab6 DL |
1528 | |
1529 | @item Newsgroups | |
1530 | @cindex Newsgroups | |
1531 | This required header says which newsgroups the article is to be posted | |
1532 | to. If it isn't present already, it will be prompted for. | |
1533 | ||
1534 | @item Organization | |
1535 | @cindex organization | |
23f87bed MB |
1536 | @vindex message-user-organization |
1537 | @vindex message-user-organization-file | |
6bf7aab6 DL |
1538 | This optional header will be filled out depending on the |
1539 | @code{message-user-organization} variable. | |
1540 | @code{message-user-organization-file} will be used if this variable is | |
1541 | @code{t}. This variable can also be a string (in which case this string | |
1542 | will be used), or it can be a function (which will be called with no | |
1543 | parameters and should return a string to be used). | |
1544 | ||
1545 | @item Lines | |
1546 | @cindex Lines | |
1547 | This optional header will be computed by Message. | |
1548 | ||
1549 | @item Message-ID | |
1550 | @cindex Message-ID | |
23f87bed | 1551 | @vindex message-user-fqdn |
6bf7aab6 | 1552 | @vindex mail-host-address |
23f87bed | 1553 | @vindex user-mail-address |
6bf7aab6 DL |
1554 | @findex system-name |
1555 | @cindex Sun | |
23f87bed | 1556 | @cindex i-did-not-set--mail-host-address--so-tickle-me |
6bf7aab6 | 1557 | This required header will be generated by Message. A unique ID will be |
9b5773bc MB |
1558 | created based on the date, time, user name (for the local part) and the |
1559 | domain part. For the domain part, message will look (in this order) at | |
23f87bed MB |
1560 | @code{message-user-fqdn}, @code{system-name}, @code{mail-host-address} |
1561 | and @code{message-user-mail-address} (i.e. @code{user-mail-address}) | |
1562 | until a probably valid fully qualified domain name (FQDN) was found. | |
6bf7aab6 | 1563 | |
dda5808a DL |
1564 | @item User-Agent |
1565 | @cindex User-Agent | |
6bf7aab6 DL |
1566 | This optional header will be filled out according to the |
1567 | @code{message-newsreader} local variable. | |
1568 | ||
6bf7aab6 DL |
1569 | @item In-Reply-To |
1570 | This optional header is filled out using the @code{Date} and @code{From} | |
1571 | header of the article being replied to. | |
1572 | ||
1573 | @item Expires | |
1574 | @cindex Expires | |
23f87bed | 1575 | @vindex message-expires |
6bf7aab6 DL |
1576 | This extremely optional header will be inserted according to the |
1577 | @code{message-expires} variable. It is highly deprecated and shouldn't | |
1578 | be used unless you know what you're doing. | |
1579 | ||
1580 | @item Distribution | |
1581 | @cindex Distribution | |
23f87bed | 1582 | @vindex message-distribution-function |
6bf7aab6 DL |
1583 | This optional header is filled out according to the |
1584 | @code{message-distribution-function} variable. It is a deprecated and | |
1585 | much misunderstood header. | |
1586 | ||
1587 | @item Path | |
1588 | @cindex path | |
23f87bed | 1589 | @vindex message-user-path |
6bf7aab6 DL |
1590 | This extremely optional header should probably never be used. |
1591 | However, some @emph{very} old servers require that this header is | |
1592 | present. @code{message-user-path} further controls how this | |
1593 | @code{Path} header is to look. If it is @code{nil}, use the server name | |
1594 | as the leaf node. If it is a string, use the string. If it is neither | |
1595 | a string nor @code{nil}, use the user name only. However, it is highly | |
1596 | unlikely that you should need to fiddle with this variable at all. | |
1597 | @end table | |
1598 | ||
1599 | @findex yow | |
1600 | @cindex Mime-Version | |
23f87bed | 1601 | In addition, you can enter conses into this list. The @sc{car} of this cons |
6bf7aab6 | 1602 | should be a symbol. This symbol's name is the name of the header, and |
23f87bed | 1603 | the @sc{cdr} can either be a string to be entered verbatim as the value of |
6bf7aab6 DL |
1604 | this header, or it can be a function to be called. This function should |
1605 | return a string to be inserted. For instance, if you want to insert | |
1606 | @code{Mime-Version: 1.0}, you should enter @code{(Mime-Version . "1.0")} | |
1607 | into the list. If you want to insert a funny quote, you could enter | |
1608 | something like @code{(X-Yow . yow)} into the list. The function | |
1609 | @code{yow} will then be called without any arguments. | |
1610 | ||
23f87bed MB |
1611 | If the list contains a cons where the @sc{car} of the cons is |
1612 | @code{optional}, the @sc{cdr} of this cons will only be inserted if it is | |
6bf7aab6 DL |
1613 | non-@code{nil}. |
1614 | ||
23f87bed MB |
1615 | If you want to delete an entry from this list, the following Lisp |
1616 | snippet might be useful. Adjust accordingly if you want to remove | |
1617 | another element. | |
1618 | ||
1619 | @lisp | |
1620 | (setq message-required-news-headers | |
1621 | (delq 'Message-ID message-required-news-headers)) | |
1622 | @end lisp | |
1623 | ||
6bf7aab6 DL |
1624 | Other variables for customizing outgoing news articles: |
1625 | ||
1626 | @table @code | |
1627 | ||
1628 | @item message-syntax-checks | |
1629 | @vindex message-syntax-checks | |
1630 | Controls what syntax checks should not be performed on outgoing posts. | |
1631 | To disable checking of long signatures, for instance, add | |
1632 | ||
1633 | @lisp | |
1634 | (signature . disabled) | |
1635 | @end lisp | |
1636 | ||
1637 | to this list. | |
1638 | ||
1639 | Valid checks are: | |
1640 | ||
1641 | @table @code | |
9d3d5390 | 1642 | @item subject-cmsg |
6bf7aab6 DL |
1643 | Check the subject for commands. |
1644 | @item sender | |
1645 | @cindex Sender | |
9d3d5390 DL |
1646 | Insert a new @code{Sender} header if the @code{From} header looks odd. |
1647 | @item multiple-headers | |
6bf7aab6 | 1648 | Check for the existence of multiple equal headers. |
9d3d5390 | 1649 | @item sendsys |
6bf7aab6 DL |
1650 | @cindex sendsys |
1651 | Check for the existence of version and sendsys commands. | |
1652 | @item message-id | |
1653 | Check whether the @code{Message-ID} looks ok. | |
1654 | @item from | |
1655 | Check whether the @code{From} header seems nice. | |
9d3d5390 | 1656 | @item long-lines |
6bf7aab6 DL |
1657 | @cindex long lines |
1658 | Check for too long lines. | |
1659 | @item control-chars | |
1660 | Check for invalid characters. | |
1661 | @item size | |
1662 | Check for excessive size. | |
1663 | @item new-text | |
1664 | Check whether there is any new text in the messages. | |
1665 | @item signature | |
1666 | Check the length of the signature. | |
1667 | @item approved | |
1668 | @cindex approved | |
1669 | Check whether the article has an @code{Approved} header, which is | |
1670 | something only moderators should include. | |
1671 | @item empty | |
1672 | Check whether the article is empty. | |
9d3d5390 DL |
1673 | @item invisible-text |
1674 | Check whether there is any invisible text in the buffer. | |
6bf7aab6 DL |
1675 | @item empty-headers |
1676 | Check whether any of the headers are empty. | |
1677 | @item existing-newsgroups | |
9d3d5390 | 1678 | Check whether the newsgroups mentioned in the @code{Newsgroups} and |
6bf7aab6 DL |
1679 | @code{Followup-To} headers exist. |
1680 | @item valid-newsgroups | |
1681 | Check whether the @code{Newsgroups} and @code{Followup-to} headers | |
1682 | are valid syntactically. | |
1683 | @item repeated-newsgroups | |
1684 | Check whether the @code{Newsgroups} and @code{Followup-to} headers | |
1685 | contains repeated group names. | |
1686 | @item shorten-followup-to | |
1687 | Check whether to add a @code{Followup-to} header to shorten the number | |
1688 | of groups to post to. | |
1689 | @end table | |
1690 | ||
1691 | All these conditions are checked by default. | |
1692 | ||
1693 | @item message-ignored-news-headers | |
1694 | @vindex message-ignored-news-headers | |
1695 | Regexp of headers to be removed before posting. The default is@* | |
23f87bed | 1696 | @samp{^NNTP-Posting-Host:\\|^Xref:\\|^[BGF]cc:\\|^Resent-Fcc:\\|^X-Draft-From:}. |
6bf7aab6 DL |
1697 | |
1698 | @item message-default-news-headers | |
1699 | @vindex message-default-news-headers | |
1700 | This string is inserted at the end of the headers in all message | |
1701 | buffers that are initialized as news. | |
1702 | ||
1703 | @end table | |
1704 | ||
1705 | ||
1706 | @node News Variables | |
1707 | @section News Variables | |
1708 | ||
1709 | @table @code | |
1710 | @item message-send-news-function | |
1711 | @vindex message-send-news-function | |
1712 | Function used to send the current buffer as news. The default is | |
9d3d5390 | 1713 | @code{message-send-news}. |
6bf7aab6 DL |
1714 | |
1715 | @item message-post-method | |
1716 | @vindex message-post-method | |
1717 | Gnusish @dfn{select method} (see the Gnus manual for details) used for | |
1718 | posting a prepared news message. | |
1719 | ||
1720 | @end table | |
1721 | ||
1722 | ||
23f87bed MB |
1723 | @node Insertion Variables |
1724 | @section Insertion Variables | |
1725 | ||
1726 | @table @code | |
1727 | @item message-ignored-cited-headers | |
1728 | @vindex message-ignored-cited-headers | |
1729 | All headers that match this regexp will be removed from yanked | |
1730 | messages. The default is @samp{.}, which means that all headers will be | |
1731 | removed. | |
1732 | ||
1733 | @item message-cite-prefix-regexp | |
1734 | @vindex message-cite-prefix-regexp | |
1735 | Regexp matching the longest possible citation prefix on a line. | |
1736 | ||
1737 | @item message-citation-line-function | |
1738 | @vindex message-citation-line-function | |
1739 | @cindex attribution line | |
1740 | Function called to insert the citation line. The default is | |
1741 | @code{message-insert-citation-line}, which will lead to citation lines | |
1742 | that look like: | |
1743 | ||
1744 | @example | |
1745 | Hallvard B Furuseth <h.b.furuseth@@usit.uio.no> writes: | |
1746 | @end example | |
1747 | ||
1748 | Point will be at the beginning of the body of the message when this | |
1749 | function is called. | |
1750 | ||
1751 | Note that Gnus provides a feature where clicking on `writes:' hides the | |
1752 | cited text. If you change the citation line too much, readers of your | |
1753 | messages will have to adjust their Gnus, too. See the variable | |
1754 | @code{gnus-cite-attribution-suffix}. @xref{Article Highlighting, , | |
1755 | Article Highlighting, gnus, The Gnus Manual}, for details. | |
1756 | ||
1757 | @item message-yank-prefix | |
1758 | @vindex message-yank-prefix | |
1759 | @cindex yanking | |
1760 | @cindex quoting | |
1761 | When you are replying to or following up an article, you normally want | |
1762 | to quote the person you are answering. Inserting quoted text is done | |
1763 | by @dfn{yanking}, and each line you yank will have | |
1764 | @code{message-yank-prefix} prepended to it (except for quoted and | |
1765 | empty lines which uses @code{message-yank-cited-prefix}). The default | |
1766 | is @samp{> }. | |
1767 | ||
1768 | @item message-yank-cited-prefix | |
1769 | @vindex message-yank-cited-prefix | |
1770 | @cindex yanking | |
1771 | @cindex cited | |
1772 | @cindex quoting | |
1773 | When yanking text from an article which contains no text or already | |
1774 | cited text, each line will be prefixed with the contents of this | |
1775 | variable. The default is @samp{>}. See also | |
1776 | @code{message-yank-prefix}. | |
1777 | ||
1778 | @item message-indentation-spaces | |
1779 | @vindex message-indentation-spaces | |
1780 | Number of spaces to indent yanked messages. | |
1781 | ||
1782 | @item message-cite-function | |
1783 | @vindex message-cite-function | |
1784 | @findex message-cite-original | |
1785 | @findex sc-cite-original | |
1786 | @findex message-cite-original-without-signature | |
1787 | @cindex Supercite | |
1788 | Function for citing an original message. The default is | |
1789 | @code{message-cite-original}, which simply inserts the original message | |
1790 | and prepends @samp{> } to each line. | |
1791 | @code{message-cite-original-without-signature} does the same, but elides | |
1792 | the signature. You can also set it to @code{sc-cite-original} to use | |
1793 | Supercite. | |
1794 | ||
1795 | @item message-indent-citation-function | |
1796 | @vindex message-indent-citation-function | |
1797 | Function for modifying a citation just inserted in the mail buffer. | |
1798 | This can also be a list of functions. Each function can find the | |
1799 | citation between @code{(point)} and @code{(mark t)}. And each function | |
1800 | should leave point and mark around the citation text as modified. | |
1801 | ||
1802 | @item message-mark-insert-begin | |
1803 | @vindex message-mark-insert-begin | |
1804 | String to mark the beginning of some inserted text. | |
1805 | ||
1806 | @item message-mark-insert-end | |
1807 | @vindex message-mark-insert-end | |
1808 | String to mark the end of some inserted text. | |
1809 | ||
1810 | @item message-signature | |
1811 | @vindex message-signature | |
1812 | String to be inserted at the end of the message buffer. If @code{t} | |
1813 | (which is the default), the @code{message-signature-file} file will be | |
1814 | inserted instead. If a function, the result from the function will be | |
1815 | used instead. If a form, the result from the form will be used instead. | |
1816 | If this variable is @code{nil}, no signature will be inserted at all. | |
1817 | ||
1818 | @item message-signature-file | |
1819 | @vindex message-signature-file | |
1820 | File containing the signature to be inserted at the end of the buffer. | |
1821 | The default is @file{~/.signature}. | |
1822 | ||
1823 | @item message-signature-insert-empty-line | |
1824 | @vindex message-signature-insert-empty-line | |
1825 | If @code{t} (the default value) an empty line is inserted before the | |
1826 | signature separator. | |
1827 | ||
1828 | @end table | |
1829 | ||
1830 | Note that RFC1036bis says that a signature should be preceded by the three | |
1831 | characters @samp{-- } on a line by themselves. This is to make it | |
1832 | easier for the recipient to automatically recognize and process the | |
1833 | signature. So don't remove those characters, even though you might feel | |
1834 | that they ruin your beautiful design, like, totally. | |
1835 | ||
1836 | Also note that no signature should be more than four lines long. | |
1837 | Including @acronym{ASCII} graphics is an efficient way to get | |
1838 | everybody to believe that you are silly and have nothing important to | |
1839 | say. | |
1840 | ||
1841 | ||
6bf7aab6 DL |
1842 | @node Various Message Variables |
1843 | @section Various Message Variables | |
1844 | ||
1845 | @table @code | |
9d3d5390 DL |
1846 | @item message-default-charset |
1847 | @vindex message-default-charset | |
1848 | @cindex charset | |
23f87bed MB |
1849 | Symbol naming a @acronym{MIME} charset. Non-@acronym{ASCII} |
1850 | characters in messages are assumed to be encoded using this charset. | |
1851 | The default is @code{nil}, which means ask the user. (This variable | |
1852 | is used only on non-@sc{mule} Emacsen. @xref{Charset Translation, , | |
1853 | Charset Translation, emacs-mime, Emacs MIME Manual}, for details on | |
1854 | the @sc{mule}-to-@acronym{MIME} translation process. | |
9d3d5390 | 1855 | |
6bf7aab6 DL |
1856 | @item message-signature-separator |
1857 | @vindex message-signature-separator | |
1858 | Regexp matching the signature separator. It is @samp{^-- *$} by | |
9d3d5390 | 1859 | default. |
6bf7aab6 DL |
1860 | |
1861 | @item mail-header-separator | |
1862 | @vindex mail-header-separator | |
1863 | String used to separate the headers from the body. It is @samp{--text | |
1864 | follows this line--} by default. | |
1865 | ||
1866 | @item message-directory | |
1867 | @vindex message-directory | |
9d3d5390 | 1868 | Directory used by many mailey things. The default is @file{~/Mail/}. |
ad136a7c | 1869 | All other mail file variables are derived from @code{message-directory}. |
6bf7aab6 | 1870 | |
23f87bed MB |
1871 | @item message-auto-save-directory |
1872 | @vindex message-auto-save-directory | |
1873 | Directory where Message auto-saves buffers if Gnus isn't running. If | |
1874 | @code{nil}, Message won't auto-save. The default is @file{~/Mail/drafts/}. | |
1875 | ||
6bf7aab6 DL |
1876 | @item message-signature-setup-hook |
1877 | @vindex message-signature-setup-hook | |
1878 | Hook run when initializing the message buffer. It is run after the | |
9d3d5390 | 1879 | headers have been inserted but before the signature has been inserted. |
6bf7aab6 DL |
1880 | |
1881 | @item message-setup-hook | |
1882 | @vindex message-setup-hook | |
1883 | Hook run as the last thing when the message buffer has been initialized, | |
1884 | but before yanked text is inserted. | |
1885 | ||
1886 | @item message-header-setup-hook | |
1887 | @vindex message-header-setup-hook | |
9d3d5390 | 1888 | Hook called narrowed to the headers after initializing the headers. |
6bf7aab6 DL |
1889 | |
1890 | For instance, if you're running Gnus and wish to insert a | |
1891 | @samp{Mail-Copies-To} header in all your news articles and all messages | |
1892 | you send to mailing lists, you could do something like the following: | |
1893 | ||
1894 | @lisp | |
1895 | (defun my-message-header-setup-hook () | |
1896 | (let ((group (or gnus-newsgroup-name ""))) | |
1897 | (when (or (message-fetch-field "newsgroups") | |
1898 | (gnus-group-find-parameter group 'to-address) | |
1899 | (gnus-group-find-parameter group 'to-list)) | |
1900 | (insert "Mail-Copies-To: never\n")))) | |
1901 | ||
1902 | (add-hook 'message-header-setup-hook | |
1903 | 'my-message-header-setup-hook) | |
1904 | @end lisp | |
1905 | ||
1906 | @item message-send-hook | |
1907 | @vindex message-send-hook | |
1908 | Hook run before sending messages. | |
1909 | ||
1910 | If you want to add certain headers before sending, you can use the | |
1911 | @code{message-add-header} function in this hook. For instance: | |
1912 | @findex message-add-header | |
1913 | ||
1914 | @lisp | |
1915 | (add-hook 'message-send-hook 'my-message-add-content) | |
1916 | (defun my-message-add-content () | |
dda5808a DL |
1917 | (message-add-header "X-In-No-Sense: Nonsense") |
1918 | (message-add-header "X-Whatever: no")) | |
6bf7aab6 DL |
1919 | @end lisp |
1920 | ||
1921 | This function won't add the header if the header is already present. | |
1922 | ||
1923 | @item message-send-mail-hook | |
1924 | @vindex message-send-mail-hook | |
23f87bed MB |
1925 | Hook run before sending mail messages. This hook is run very late -- |
1926 | just before the message is actually sent as mail. | |
6bf7aab6 DL |
1927 | |
1928 | @item message-send-news-hook | |
1929 | @vindex message-send-news-hook | |
23f87bed MB |
1930 | Hook run before sending news messages. This hook is run very late -- |
1931 | just before the message is actually sent as news. | |
6bf7aab6 DL |
1932 | |
1933 | @item message-sent-hook | |
1934 | @vindex message-sent-hook | |
1935 | Hook run after sending messages. | |
1936 | ||
23f87bed MB |
1937 | @item message-cancel-hook |
1938 | @vindex message-cancel-hook | |
1939 | Hook run when canceling news articles. | |
1940 | ||
6bf7aab6 DL |
1941 | @item message-mode-syntax-table |
1942 | @vindex message-mode-syntax-table | |
1943 | Syntax table used in message mode buffers. | |
1944 | ||
23f87bed MB |
1945 | @item message-strip-special-text-properties |
1946 | @vindex message-strip-special-text-properties | |
1947 | Emacs has a number of special text properties which can break message | |
1948 | composing in various ways. If this option is set, message will strip | |
1949 | these properties from the message composition buffer. However, some | |
1950 | packages requires these properties to be present in order to work. If | |
1951 | you use one of these packages, turn this option off, and hope the | |
1952 | message composition doesn't break too bad. | |
1953 | ||
6bf7aab6 DL |
1954 | @item message-send-method-alist |
1955 | @vindex message-send-method-alist | |
1956 | ||
1957 | Alist of ways to send outgoing messages. Each element has the form | |
1958 | ||
1959 | @lisp | |
23f87bed | 1960 | (@var{type} @var{predicate} @var{function}) |
6bf7aab6 DL |
1961 | @end lisp |
1962 | ||
1963 | @table @var | |
1964 | @item type | |
1965 | A symbol that names the method. | |
1966 | ||
1967 | @item predicate | |
1968 | A function called without any parameters to determine whether the | |
1969 | message is a message of type @var{type}. | |
1970 | ||
1971 | @item function | |
1972 | A function to be called if @var{predicate} returns non-@code{nil}. | |
1973 | @var{function} is called with one parameter -- the prefix. | |
1974 | @end table | |
1975 | ||
1976 | @lisp | |
1977 | ((news message-news-p message-send-via-news) | |
1978 | (mail message-mail-p message-send-via-mail)) | |
1979 | @end lisp | |
1980 | ||
1981 | ||
1982 | ||
1983 | @end table | |
1984 | ||
1985 | ||
1986 | ||
1987 | @node Sending Variables | |
1988 | @section Sending Variables | |
1989 | ||
1990 | @table @code | |
1991 | ||
9d3d5390 DL |
1992 | @item message-fcc-handler-function |
1993 | @vindex message-fcc-handler-function | |
6bf7aab6 | 1994 | A function called to save outgoing articles. This function will be |
9d3d5390 | 1995 | called with the name of the file to store the article in. The default |
23f87bed | 1996 | function is @code{message-output} which saves in Unix mailbox format. |
6bf7aab6 DL |
1997 | |
1998 | @item message-courtesy-message | |
1999 | @vindex message-courtesy-message | |
2000 | When sending combined messages, this string is inserted at the start of | |
2001 | the mailed copy. If the string contains the format spec @samp{%s}, the | |
2002 | newsgroups the article has been posted to will be inserted there. If | |
2003 | this variable is @code{nil}, no such courtesy message will be added. | |
2004 | The default value is @samp{"The following message is a courtesy copy of | |
23f87bed MB |
2005 | an article\\nthat has been posted to %s as well.\\n\\n"}. |
2006 | ||
2007 | @item message-fcc-externalize-attachments | |
2008 | @vindex message-fcc-externalize-attachments | |
2009 | If @code{nil}, attach files as normal parts in Fcc copies; if it is | |
2010 | non-@code{nil}, attach local files as external parts. | |
2011 | ||
2012 | @item message-interactive | |
2013 | @vindex message-interactive | |
2014 | If non-@code{nil} wait for and display errors when sending a message; | |
2015 | if @code{nil} let the mailer mail back a message to report errors. | |
6bf7aab6 DL |
2016 | |
2017 | @end table | |
2018 | ||
2019 | ||
2020 | @node Message Buffers | |
2021 | @section Message Buffers | |
2022 | ||
2023 | Message will generate new buffers with unique buffer names when you | |
2024 | request a message buffer. When you send the message, the buffer isn't | |
2025 | normally killed off. Its name is changed and a certain number of old | |
2026 | message buffers are kept alive. | |
2027 | ||
2028 | @table @code | |
2029 | @item message-generate-new-buffers | |
2030 | @vindex message-generate-new-buffers | |
2031 | If non-@code{nil}, generate new buffers. The default is @code{t}. If | |
2032 | this is a function, call that function with three parameters: The type, | |
2033 | the to address and the group name. (Any of these may be @code{nil}.) | |
2034 | The function should return the new buffer name. | |
2035 | ||
2036 | @item message-max-buffers | |
2037 | @vindex message-max-buffers | |
2038 | This variable says how many old message buffers to keep. If there are | |
2039 | more message buffers than this, the oldest buffer will be killed. The | |
2040 | default is 10. If this variable is @code{nil}, no old message buffers | |
2041 | will ever be killed. | |
2042 | ||
2043 | @item message-send-rename-function | |
2044 | @vindex message-send-rename-function | |
2045 | After sending a message, the buffer is renamed from, for instance, | |
2046 | @samp{*reply to Lars*} to @samp{*sent reply to Lars*}. If you don't | |
2047 | like this, set this variable to a function that renames the buffer in a | |
2048 | manner you like. If you don't want to rename the buffer at all, you can | |
2049 | say: | |
2050 | ||
2051 | @lisp | |
2052 | (setq message-send-rename-function 'ignore) | |
2053 | @end lisp | |
2054 | ||
2055 | @item message-kill-buffer-on-exit | |
2056 | @findex message-kill-buffer-on-exit | |
2057 | If non-@code{nil}, kill the buffer immediately on exit. | |
2058 | ||
2059 | @end table | |
2060 | ||
2061 | ||
2062 | @node Message Actions | |
2063 | @section Message Actions | |
2064 | ||
2065 | When Message is being used from a news/mail reader, the reader is likely | |
2066 | to want to perform some task after the message has been sent. Perhaps | |
2067 | return to the previous window configuration or mark an article as | |
9d3d5390 | 2068 | replied. |
6bf7aab6 DL |
2069 | |
2070 | @vindex message-kill-actions | |
2071 | @vindex message-postpone-actions | |
2072 | @vindex message-exit-actions | |
2073 | @vindex message-send-actions | |
2074 | The user may exit from the message buffer in various ways. The most | |
2075 | common is @kbd{C-c C-c}, which sends the message and exits. Other | |
2076 | possibilities are @kbd{C-c C-s} which just sends the message, @kbd{C-c | |
2077 | C-d} which postpones the message editing and buries the message buffer, | |
2078 | and @kbd{C-c C-k} which kills the message buffer. Each of these actions | |
2079 | have lists associated with them that contains actions to be executed: | |
2080 | @code{message-send-actions}, @code{message-exit-actions}, | |
9d3d5390 | 2081 | @code{message-postpone-actions}, and @code{message-kill-actions}. |
6bf7aab6 DL |
2082 | |
2083 | Message provides a function to interface with these lists: | |
2084 | @code{message-add-action}. The first parameter is the action to be | |
2085 | added, and the rest of the arguments are which lists to add this action | |
2086 | to. Here's an example from Gnus: | |
2087 | ||
2088 | @lisp | |
2089 | (message-add-action | |
2090 | `(set-window-configuration ,(current-window-configuration)) | |
2091 | 'exit 'postpone 'kill) | |
2092 | @end lisp | |
2093 | ||
2094 | This restores the Gnus window configuration when the message buffer is | |
2095 | killed, postponed or exited. | |
2096 | ||
2097 | An @dfn{action} can be either: a normal function, or a list where the | |
23f87bed | 2098 | @sc{car} is a function and the @sc{cdr} is the list of arguments, or |
6bf7aab6 DL |
2099 | a form to be @code{eval}ed. |
2100 | ||
2101 | ||
2102 | @node Compatibility | |
2103 | @chapter Compatibility | |
2104 | @cindex compatibility | |
2105 | ||
2106 | Message uses virtually only its own variables---older @code{mail-} | |
2107 | variables aren't consulted. To force Message to take those variables | |
23f87bed | 2108 | into account, you can put the following in your @file{.emacs} file: |
6bf7aab6 DL |
2109 | |
2110 | @lisp | |
2111 | (require 'messcompat) | |
2112 | @end lisp | |
2113 | ||
2114 | This will initialize many Message variables from the values in the | |
2115 | corresponding mail variables. | |
2116 | ||
2117 | ||
2118 | @node Appendices | |
2119 | @chapter Appendices | |
2120 | ||
2121 | @menu | |
2122 | * Responses:: Standard rules for determining where responses go. | |
2123 | @end menu | |
2124 | ||
2125 | ||
2126 | @node Responses | |
2127 | @section Responses | |
2128 | ||
2129 | To determine where a message is to go, the following algorithm is used | |
2130 | by default. | |
2131 | ||
2132 | @table @dfn | |
2133 | @item reply | |
2134 | A @dfn{reply} is when you want to respond @emph{just} to the person who | |
2135 | sent the message via mail. There will only be one recipient. To | |
2136 | determine who the recipient will be, the following headers are | |
2137 | consulted, in turn: | |
2138 | ||
2139 | @table @code | |
2140 | @item Reply-To | |
2141 | ||
2142 | @item From | |
2143 | @end table | |
2144 | ||
2145 | ||
2146 | @item wide reply | |
2147 | A @dfn{wide reply} is a mail response that includes @emph{all} entities | |
2148 | mentioned in the message you are responded to. All mailboxes from the | |
2149 | following headers will be concatenated to form the outgoing | |
2150 | @code{To}/@code{Cc} headers: | |
2151 | ||
2152 | @table @code | |
2153 | @item From | |
2154 | (unless there's a @code{Reply-To}, in which case that is used instead). | |
2155 | ||
2156 | @item Cc | |
2157 | ||
2158 | @item To | |
2159 | @end table | |
2160 | ||
2161 | If a @code{Mail-Copies-To} header is present, it will also be included | |
2162 | in the list of mailboxes. If this header is @samp{never}, that means | |
2163 | that the @code{From} (or @code{Reply-To}) mailbox will be suppressed. | |
2164 | ||
2165 | ||
2166 | @item followup | |
2167 | A @dfn{followup} is a response sent via news. The following headers | |
2168 | (listed in order of precedence) determine where the response is to be | |
2169 | sent: | |
2170 | ||
2171 | @table @code | |
2172 | ||
2173 | @item Followup-To | |
2174 | ||
2175 | @item Newsgroups | |
2176 | ||
2177 | @end table | |
2178 | ||
2179 | If a @code{Mail-Copies-To} header is present, it will be used as the | |
2180 | basis of the new @code{Cc} header, except if this header is | |
2181 | @samp{never}. | |
2182 | ||
2183 | @end table | |
2184 | ||
2185 | ||
2186 | ||
2187 | @node Index | |
2188 | @chapter Index | |
2189 | @printindex cp | |
2190 | ||
2191 | @node Key Index | |
2192 | @chapter Key Index | |
2193 | @printindex ky | |
2194 | ||
2195 | @summarycontents | |
2196 | @contents | |
2197 | @bye | |
2198 | ||
2199 | @c End: | |
ab5796a9 MB |
2200 | |
2201 | @ignore | |
2202 | arch-tag: 16ab76af-a281-4e34-aed6-5624569f7601 | |
2203 | @end ignore |