rms approved.
[bpt/emacs.git] / man / sending.texi
1 @c This is part of the Emacs manual.
2 @c Copyright (C) 1985, 86, 87, 93, 94, 95, 97, 2000
3 @c Free Software Foundation, Inc.
4 @c See file emacs.texi for copying conditions.
5 @node Sending Mail, Rmail, Picture, Top
6 @chapter Sending Mail
7 @cindex sending mail
8 @cindex mail
9 @cindex message
10
11 To send a message in Emacs, you start by typing a command (@kbd{C-x m})
12 to select and initialize the @samp{*mail*} buffer. Then you edit the text
13 and headers of the message in this buffer, and type another command
14 (@kbd{C-c C-s} or @kbd{C-c C-c}) to send the message.
15
16 @table @kbd
17 @item C-x m
18 Begin composing a message to send (@code{compose-mail}).
19 @item C-x 4 m
20 Likewise, but display the message in another window
21 (@code{compose-mail-other-window}).
22 @item C-x 5 m
23 Likewise, but make a new frame (@code{compose-mail-other-frame}).
24 @item C-c C-s
25 In Mail mode, send the message (@code{mail-send}).
26 @item C-c C-c
27 Send the message and bury the mail buffer (@code{mail-send-and-exit}).
28 @end table
29
30 @kindex C-x m
31 @findex compose-mail
32 @kindex C-x 4 m
33 @findex compose-mail-other-window
34 @kindex C-x 5 m
35 @findex compose-mail-other-frame
36 The command @kbd{C-x m} (@code{compose-mail}) selects a buffer named
37 @samp{*mail*} and initializes it with the skeleton of an outgoing
38 message. @kbd{C-x 4 m} (@code{compose-mail-other-window}) selects the
39 @samp{*mail*} buffer in a different window, leaving the previous current
40 buffer visible. @kbd{C-x 5 m} (@code{compose-mail-other-frame}) creates
41 a new frame to select the @samp{*mail*} buffer.
42
43 Because the mail-composition buffer is an ordinary Emacs buffer, you can
44 switch to other buffers while in the middle of composing mail, and switch
45 back later (or never). If you use the @kbd{C-x m} command again when you
46 have been composing another message but have not sent it, you are asked to
47 confirm before the old message is erased. If you answer @kbd{n}, the
48 @samp{*mail*} buffer is left selected with its old contents, so you can
49 finish the old message and send it. @kbd{C-u C-x m} is another way to do
50 this. Sending the message marks the @samp{*mail*} buffer ``unmodified,''
51 which avoids the need for confirmation when @kbd{C-x m} is next used.
52
53 If you are composing a message in the @samp{*mail*} buffer and want to
54 send another message before finishing the first, rename the
55 @samp{*mail*} buffer using @kbd{M-x rename-uniquely} (@pxref{Misc
56 Buffer}). Then you can use @kbd{C-x m} or its variants described above
57 to make a new @samp{*mail*} buffer. Once you've done that, you can work
58 with each mail buffer independently.
59
60 @cindex directory servers
61 @cindex LDAP
62 @cindex PH/QI
63 @cindex names and addresses
64 There is an interface to directory servers using various protocols such
65 as LDAP or the CCSO white pages directory system (PH/QI), described in a
66 separate manual. It may be useful for looking up names and addresses.
67 @xref{Top,,EUDC, eudc, EUDC Manual}.
68
69 @menu
70 * Format: Mail Format. Format of the mail being composed.
71 * Headers: Mail Headers. Details of permitted mail header fields.
72 * Aliases: Mail Aliases. Abbreviating and grouping mail addresses.
73 * Mode: Mail Mode. Special commands for editing mail being composed.
74 * Spook: Distracting NSA. How to distract the NSA's attention.
75 * Fortune:: `Fortune' items in signatures.
76 * Footnotes: Mail Footnotes. Making footnotes in messages.
77 * Methods: Mail Methods. Using alternative mail-composition methods.
78 @end menu
79
80 @node Mail Format
81 @section The Format of the Mail Buffer
82
83 In addition to the @dfn{text} or @dfn{body}, a message has @dfn{header
84 fields} which say who sent it, when, to whom, why, and so on. Some
85 header fields, such as @samp{Date} and @samp{Sender}, are created
86 automatically when you send the message. Others, such as the recipient
87 names, must be specified by you in order to send the message properly.
88
89 Mail mode provides a few commands to help you edit some header fields,
90 and some are preinitialized in the buffer automatically at times. You can
91 insert and edit header fields using ordinary editing commands.
92
93 The line in the buffer that says
94
95 @example
96 --text follows this line--
97 @end example
98
99 @noindent
100 is a special delimiter that separates the headers you have specified from
101 the text. Whatever follows this line is the text of the message; the
102 headers precede it. The delimiter line itself does not appear in the
103 message actually sent. The text used for the delimiter line is controlled
104 by the variable @code{mail-header-separator}.
105
106 Here is an example of what the headers and text in the mail buffer
107 might look like.
108
109 @example
110 To: gnu@@gnu.org
111 CC: lungfish@@spam.org, byob@@spam.org
112 Subject: The Emacs Manual
113 --Text follows this line--
114 Please ignore this message.
115 @end example
116
117 @node Mail Headers
118 @section Mail Header Fields
119 @cindex headers (of mail message)
120
121 A header field in the mail buffer starts with a field name at the
122 beginning of a line, terminated by a colon. Upper and lower case are
123 equivalent in field names (and in mailing addresses also). After the
124 colon and optional whitespace comes the contents of the field.
125
126 You can use any name you like for a header field, but normally people
127 use only standard field names with accepted meanings. Here is a table
128 of fields commonly used in outgoing messages.
129
130 @table @samp
131 @item To
132 This field contains the mailing addresses to which the message is
133 addressed. If you list more than one address, use commas, not spaces,
134 to separate them.
135
136 @item Subject
137 The contents of the @samp{Subject} field should be a piece of text
138 that says what the message is about. The reason @samp{Subject} fields
139 are useful is that most mail-reading programs can provide a summary of
140 messages, listing the subject of each message but not its text.
141
142 @item CC
143 This field contains additional mailing addresses to send the message to,
144 like @samp{To} except that these readers should not regard the message
145 as directed at them.
146
147 @item BCC
148 This field contains additional mailing addresses to send the message to,
149 which should not appear in the header of the message actually sent.
150 Copies sent this way are called @dfn{blind carbon copies}.
151
152 @vindex mail-self-blind
153 To send a blind carbon copy of every outgoing message to yourself, set
154 the variable @code{mail-self-blind} to @code{t}.
155
156 @item FCC
157 This field contains the name of one file and directs Emacs to append a
158 copy of the message to that file when you send the message. If the file
159 is in Rmail format, Emacs writes the message in Rmail format; otherwise,
160 Emacs writes the message in system mail file format.
161
162 @vindex mail-archive-file-name
163 To put a fixed file name in the @samp{FCC} field each time you start
164 editing an outgoing message, set the variable
165 @code{mail-archive-file-name} to that file name. Unless you remove the
166 @samp{FCC} field before sending, the message will be written into that
167 file when it is sent.
168
169 @item From
170 Use the @samp{From} field to say who you are, when the account you are
171 using to send the mail is not your own. The contents of the @samp{From}
172 field should be a valid mailing address, since replies will normally go
173 there. If you don't specify the @samp{From} field yourself, Emacs uses
174 the value of @code{user-mail-address} as the default.
175
176 @item Reply-to
177 Use this field to direct replies to a different address. Most
178 mail-reading programs (including Rmail) automatically send replies to
179 the @samp{Reply-to} address in preference to the @samp{From} address.
180 By adding a @samp{Reply-to} field to your header, you can work around
181 any problems your @samp{From} address may cause for replies.
182
183 @cindex @env{REPLYTO} environment variable
184 @vindex mail-default-reply-to
185 To put a fixed @samp{Reply-to} address into every outgoing message, set
186 the variable @code{mail-default-reply-to} to that address (as a string).
187 Then @code{mail} initializes the message with a @samp{Reply-to} field as
188 specified. You can delete or alter that header field before you send
189 the message, if you wish. When Emacs starts up, if the environment
190 variable @env{REPLYTO} is set, @code{mail-default-reply-to} is
191 initialized from that environment variable.
192
193 @item In-reply-to
194 This field contains a piece of text describing a message you are
195 replying to. Some mail systems can use this information to correlate
196 related pieces of mail. Normally this field is filled in by Rmail
197 when you reply to a message in Rmail, and you never need to
198 think about it (@pxref{Rmail}).
199
200 @item References
201 This field lists the message IDs of related previous messages. Rmail
202 sets up this field automatically when you reply to a message.
203 @end table
204
205 The @samp{To}, @samp{CC}, @samp{BCC} and @samp{FCC} header fields can
206 appear any number of times, and each such header field can contain
207 multiple addresses, separated by commas. This way, you can specify any
208 number of places to send the message. A @samp{To}, @samp{CC}, or
209 @samp{BCC} field can also have continuation lines: one or more lines
210 starting with whitespace, following the starting line of the field, are
211 considered part of the field. Here's an example of a @samp{To} field
212 with a continuation line:@refill
213
214 @example
215 @group
216 To: foo@@here.net, this@@there.net,
217 me@@gnu.cambridge.mass.usa.earth.spiral3281
218 @end group
219 @end example
220
221 @vindex mail-from-style
222 When you send the message, if you didn't write a @samp{From} field
223 yourself, Emacs puts in one for you. The variable
224 @code{mail-from-style} controls the format:
225
226 @table @code
227 @item nil
228 Use just the email address, as in @samp{king@@grassland.com}.
229 @item parens
230 Use both email address and full name, as in @samp{king@@grassland.com (Elvis
231 Parsley)}.
232 @item angles
233 Use both email address and full name, as in @samp{Elvis Parsley
234 <king@@grassland.com>}.
235 @item system-default
236 Allow the system to insert the @samp{From} field.
237 @end table
238
239 @node Mail Aliases
240 @section Mail Aliases
241 @cindex mail aliases
242 @cindex @file{.mailrc} file
243 @cindex mailrc file
244
245 You can define @dfn{mail aliases} in a file named @file{~/.mailrc}.
246 These are short mnemonic names which stand for mail addresses or groups of
247 mail addresses. Like many other mail programs, Emacs expands aliases
248 when they occur in the @samp{To}, @samp{From}, @samp{CC}, @samp{BCC}, and
249 @samp{Reply-to} fields, plus their @samp{Resent-} variants.
250
251 To define an alias in @file{~/.mailrc}, write a line in the following
252 format:
253
254 @example
255 alias @var{shortaddress} @var{fulladdresses}
256 @end example
257
258 @noindent
259 Here @var{fulladdresses} stands for one or more mail addresses for
260 @var{shortaddress} to expand into. Separate multiple addresses with
261 spaces; if an address contains a space, quote the whole address with a
262 pair of double-quotes.
263
264 For instance, to make @code{maingnu} stand for
265 @code{gnu@@gnu.org} plus a local address of your own, put in
266 this line:@refill
267
268 @example
269 alias maingnu gnu@@gnu.org local-gnu
270 @end example
271
272 Emacs also recognizes include commands in @samp{.mailrc} files.
273 They look like this:
274
275 @example
276 source @var{filename}
277 @end example
278
279 @noindent
280 The file @file{~/.mailrc} is used primarily by other mail-reading
281 programs; it can contain various other commands. Emacs ignores
282 everything in it except for alias definitions and include commands.
283
284 @findex define-mail-alias
285 Another way to define a mail alias, within Emacs alone, is with the
286 @code{define-mail-alias} command. It prompts for the alias and then the
287 full address. You can use it to define aliases in your @file{.emacs}
288 file, like this:
289
290 @example
291 (define-mail-alias "maingnu" "gnu@@gnu.org")
292 @end example
293
294 @vindex mail-aliases
295 @code{define-mail-alias} records aliases by adding them to a
296 variable named @code{mail-aliases}. If you are comfortable with
297 manipulating Lisp lists, you can set @code{mail-aliases} directly. The
298 initial value of @code{mail-aliases} is @code{t}, which means that
299 Emacs should read @file{.mailrc} to get the proper value.
300
301 @vindex mail-personal-alias-file
302 You can specify a different file name to use instead of
303 @file{~/.mailrc} by setting the variable
304 @code{mail-personal-alias-file}.
305
306 @findex expand-mail-aliases
307 Normally, Emacs expands aliases when you send the message. You do not
308 need to expand mail aliases before sending the message, but you can
309 expand them if you want to see where the mail will actually go. To do
310 this, use the command @kbd{M-x expand-mail-aliases}; it expands all mail
311 aliases currently present in the mail headers that hold addresses.
312
313 If you like, you can have mail aliases expand as abbrevs, as soon as
314 you type them in (@pxref{Abbrevs}). To enable this feature, execute the
315 following:
316
317 @example
318 (add-hook 'mail-setup-hook 'mail-abbrevs-setup)
319 @end example
320
321 @noindent
322 @findex define-mail-abbrev
323 @vindex mail-abbrevs
324 This can go in your @file{.emacs} file. @xref{Hooks}. If you use this
325 feature, you must use @code{define-mail-abbrev} instead of
326 @code{define-mail-alias}; the latter does not work with this package.
327 Note that the mail abbreviation package uses the variable
328 @code{mail-abbrevs} instead of @code{mail-aliases}, and that all alias
329 names are converted to lower case.
330
331 @kindex C-c C-a @r{(Mail mode)}
332 @findex mail-interactive-insert-alias
333 The mail abbreviation package also provides the @kbd{C-c C-a}
334 (@code{mail-interactive-insert-alias}) command, which reads an alias
335 name (with completion) and inserts its definition at point. This is
336 useful when editing the message text itself or a header field such as
337 @samp{Subject} in which Emacs does not normally expand aliases.
338
339 Note that abbrevs expand only if you insert a word-separator character
340 afterward. However, you can rebind @kbd{C-n} and @kbd{M->} to cause
341 expansion as well. Here's how to do that:
342
343 @smallexample
344 (add-hook 'mail-setup-hook
345 '(lambda ()
346 (substitute-key-definition
347 'next-line 'mail-abbrev-next-line
348 mail-mode-map global-map)
349 (substitute-key-definition
350 'end-of-buffer 'mail-abbrev-end-of-buffer
351 mail-mode-map global-map)))
352 @end smallexample
353
354 @node Mail Mode
355 @section Mail Mode
356 @cindex Mail mode
357 @cindex mode, Mail
358
359 The major mode used in the mail buffer is Mail mode, which is much
360 like Text mode except that various special commands are provided on the
361 @kbd{C-c} prefix. These commands all have to do specifically with
362 editing or sending the message. In addition, Mail mode defines the
363 character @samp{%} as a word separator; this is helpful for using the
364 word commands to edit mail addresses.
365
366 Mail mode is normally used in buffers set up automatically by the
367 @code{mail} command and related commands. However, you can also switch
368 to Mail mode in a file-visiting buffer. That is a useful thing to do if
369 you have saved draft message text in a file.
370
371 @menu
372 * Mail Sending:: Commands to send the message.
373 * Header Editing:: Commands to move to header fields and edit them.
374 * Citing Mail:: Copying all or part of a message you are replying to.
375 * Mail Mode Misc:: Spell checking, signatures, etc.
376 @end menu
377
378 @node Mail Sending
379 @subsection Mail Sending
380
381 Mail mode has two commands for sending the message you have been
382 editing:
383
384 @table @kbd
385 @item C-c C-s
386 Send the message, and leave the mail buffer selected (@code{mail-send}).
387 @item C-c C-c
388 Send the message, and select some other buffer (@code{mail-send-and-exit}).
389 @end table
390
391 @kindex C-c C-s @r{(Mail mode)}
392 @kindex C-c C-c @r{(Mail mode)}
393 @findex mail-send
394 @findex mail-send-and-exit
395 @kbd{C-c C-s} (@code{mail-send}) sends the message and marks the mail
396 buffer unmodified, but leaves that buffer selected so that you can
397 modify the message (perhaps with new recipients) and send it again.
398 @kbd{C-c C-c} (@code{mail-send-and-exit}) sends and then deletes the
399 window or switches to another buffer. It puts the mail buffer at the
400 lowest priority for reselection by default, since you are finished with
401 using it. This is the usual way to send the message.
402
403 In a file-visiting buffer, sending the message does not clear the
404 modified flag, because only saving the file should do that. As a
405 result, you don't get a warning if you try to send the same message
406 twice.
407
408 @vindex sendmail-coding-system
409 When you send a message that contains non-ASCII characters, they need
410 to be encoded with a coding system (@pxref{Coding Systems}). Usually
411 the coding system is specified automatically by your chosen language
412 environment (@pxref{Language Environments}). You can explicitly specify
413 the coding system for outgoing mail by setting the variable
414 @code{sendmail-coding-system}.
415
416 If the coding system thus determined does not handle the characters in
417 a particular message, Emacs asks you to select the coding system to use,
418 showing a list of possible coding systems.
419
420 @node Header Editing
421 @subsection Mail Header Editing
422
423 Mail mode provides special commands to move to particular header
424 fields and to complete addresses in headers.
425
426 @table @kbd
427 @item C-c C-f C-t
428 Move to the @samp{To} header field, creating one if there is none
429 (@code{mail-to}).
430 @item C-c C-f C-s
431 Move to the @samp{Subject} header field, creating one if there is
432 none (@code{mail-subject}).
433 @item C-c C-f C-c
434 Move to the @samp{CC} header field, creating one if there is none
435 (@code{mail-cc}).
436 @item C-c C-f C-b
437 Move to the @samp{BCC} header field, creating one if there is none
438 (@code{mail-bcc}).
439 @item C-c C-f C-f
440 Move to the @samp{FCC} header field, creating one if there is none
441 (@code{mail-fcc}).
442 @item M-@key{TAB}
443 Complete a mailing address (@code{mail-complete}).
444 @end table
445
446 @kindex C-c C-f C-t @r{(Mail mode)}
447 @findex mail-to
448 @kindex C-c C-f C-s @r{(Mail mode)}
449 @findex mail-subject
450 @kindex C-c C-f C-c @r{(Mail mode)}
451 @findex mail-cc
452 @kindex C-c C-f C-b @r{(Mail mode)}
453 @findex mail-bcc
454 @kindex C-c C-f C-f @r{(Mail mode)}
455 @findex mail-fcc
456 There are five commands to move point to particular header fields, all
457 based on the prefix @kbd{C-c C-f} (@samp{C-f} is for ``field''). They
458 are listed in the table above. If the field in question does not exist,
459 these commands create one. We provide special motion commands for these
460 particular fields because they are the fields users most often want to
461 edit.
462
463 @findex mail-complete
464 @kindex M-TAB @r{(Mail mode)}
465 While editing a header field that contains mailing addresses, such as
466 @samp{To:}, @samp{CC:} and @samp{BCC:}, you can complete a mailing
467 address by typing @kbd{M-@key{TAB}} (@code{mail-complete}). It inserts
468 the full name corresponding to the address, if it can determine the full
469 name. The variable @code{mail-complete-style} controls whether to insert
470 the full name, and what style to use, as in @code{mail-from-style}
471 (@pxref{Mail Headers}).
472
473 For completion purposes, the valid mailing addresses are taken to be
474 the local users' names plus your personal mail aliases. You can specify
475 additional sources of valid addresses; use the customization buffer
476 to see the options for this.
477
478 If you type @kbd{M-@key{TAB}} in the body of the message, it invokes
479 @code{ispell-complete-word}, as in Text mode.
480
481 @node Citing Mail
482 @subsection Citing Mail
483 @cindex citing mail
484
485 Mail mode also has commands for yanking or @dfn{citing} all or part of
486 a message that you are replying to. These commands are active only when
487 you started sending a message using an Rmail command.
488
489 @table @kbd
490 @item C-c C-y
491 Yank the selected message from Rmail (@code{mail-yank-original}).
492 @item C-c C-r
493 Yank the region from the Rmail buffer (@code{mail-yank-region}).
494 @item C-c C-q
495 Fill each paragraph cited from another message
496 (@code{mail-fill-yanked-message}).
497 @end table
498
499 @kindex C-c C-y @r{(Mail mode)}
500 @findex mail-yank-original
501 When mail sending is invoked from the Rmail mail reader using an Rmail
502 command, @kbd{C-c C-y} can be used inside the mail buffer to insert
503 the text of the message you are replying to. Normally it indents each line
504 of that message three spaces and eliminates most header fields. A numeric
505 argument specifies the number of spaces to indent. An argument of just
506 @kbd{C-u} says not to indent at all and not to eliminate anything.
507 @kbd{C-c C-y} always uses the current message from the Rmail buffer,
508 so you can insert several old messages by selecting one in Rmail,
509 switching to @samp{*mail*} and yanking it, then switching back to
510 Rmail to select another.
511
512 @vindex mail-yank-prefix
513 You can specify the text for @kbd{C-c C-y} to insert at the beginning
514 of each line: set @code{mail-yank-prefix} to the desired string. (A
515 value of @code{nil} means to use indentation; this is the default.)
516 However, @kbd{C-u C-c C-y} never adds anything at the beginning of the
517 inserted lines, regardless of the value of @code{mail-yank-prefix}.
518
519 @kindex C-c C-r @r{(Mail mode)}
520 @findex mail-yank-region
521 To yank just a part of an incoming message, set the region in Rmail to
522 the part you want; then go to the @samp{*Mail*} message and type
523 @kbd{C-c C-r} (@code{mail-yank-region}). Each line that is copied is
524 indented or prefixed according to @code{mail-yank-prefix}.
525
526 @kindex C-c C-q @r{(Mail mode)}
527 @findex mail-fill-yanked-message
528 After using @kbd{C-c C-y} or @kbd{C-c C-r}, you can type @kbd{C-c C-q}
529 (@code{mail-fill-yanked-message}) to fill the paragraphs of the yanked
530 old message or messages. One use of @kbd{C-c C-q} fills all such
531 paragraphs, each one individually. To fill a single paragraph of the
532 quoted message, use @kbd{M-q}. If filling does not automatically
533 handle the type of citation prefix you use, try setting the fill prefix
534 explicitly. @xref{Filling}.
535
536 @node Mail Mode Misc
537 @subsection Mail Mode Miscellany
538
539 @table @kbd
540 @item C-c C-t
541 Move to the beginning of the message body text (@code{mail-text}).
542 @item C-c C-w
543 Insert the file @file{~/.signature} at the end of the message text
544 (@code{mail-signature}).
545 @item C-c C-i @var{file} @key{RET}
546 Insert the contents of @var{file} at the end of the outgoing message
547 (@code{mail-attach-file}).
548 @item M-x ispell-message
549 Do spelling correction on the message text, but not on citations from
550 other messages.
551 @end table
552
553 @kindex C-c C-t @r{(Mail mode)}
554 @findex mail-text
555 @kbd{C-c C-t} (@code{mail-text}) moves point to just after the header
556 separator line---that is, to the beginning of the message body text.
557
558 @kindex C-c C-w @r{(Mail mode)}
559 @findex mail-signature
560 @vindex mail-signature
561 @kbd{C-c C-w} (@code{mail-signature}) adds a standard piece of text at
562 the end of the message to say more about who you are. The text comes
563 from the file @file{~/.signature} in your home directory. To insert
564 your signature automatically, set the variable @code{mail-signature} to
565 @code{t}; then starting a mail message automatically inserts the
566 contents of your @file{~/.signature} file. If you want to omit your
567 signature from a particular message, delete it from the buffer before
568 you send the message.
569
570 You can also set @code{mail-signature} to a string; then that string
571 is inserted automatically as your signature when you start editing a
572 message to send. If you set it to some other Lisp expression, the
573 expression is evaluated each time, and its value (which should be a
574 string) specifies the signature.
575
576 @findex ispell-message
577 You can do spelling correction on the message text you have written
578 with the command @kbd{M-x ispell-message}. If you have yanked an
579 incoming message into the outgoing draft, this command skips what was
580 yanked, but it checks the text that you yourself inserted. (It looks
581 for indentation or @code{mail-yank-prefix} to distinguish the cited
582 lines from your input.) @xref{Spelling}.
583
584 @kindex C-c C-i @r{(Mail mode)}
585 @findex mail-attach-file
586 To include a file in the outgoing message, you can use @kbd{C-x i},
587 the usual command to insert a file in the current buffer. But it is
588 often more convenient to use a special command, @kbd{C-c C-i}
589 (@code{mail-attach-file}). This command inserts the file contents at
590 the end of the buffer, after your signature if any, with a delimiter
591 line that includes the file name.
592
593 @vindex mail-mode-hook
594 @vindex mail-setup-hook
595 Turning on Mail mode (which @kbd{C-x m} does automatically) runs the
596 normal hooks @code{text-mode-hook} and @code{mail-mode-hook}.
597 Initializing a new outgoing message runs the normal hook
598 @code{mail-setup-hook}; if you want to add special fields to your mail
599 header or make other changes to the appearance of the mail buffer, use
600 that hook. @xref{Hooks}.
601
602 The main difference between these hooks is just when they are
603 invoked. Whenever you type @kbd{M-x mail}, @code{mail-mode-hook} runs
604 as soon as the @samp{*mail*} buffer is created. Then the
605 @code{mail-setup} function puts in the default contents of the buffer.
606 After these default contents are inserted, @code{mail-setup-hook} runs.
607
608 @node Distracting NSA
609 @section Distracting the NSA
610
611 @findex spook
612 @cindex NSA
613 @kbd{M-x spook} adds a line of randomly chosen keywords to an outgoing
614 mail message. The keywords are chosen from a list of words that suggest
615 you are discussing something subversive.
616
617 The idea behind this feature is the suspicion that the
618 NSA@footnote{The US National Security Agency.} snoops on
619 all electronic mail messages that contain keywords suggesting they might
620 find them interesting. (The NSA says they don't, but that's what they
621 @emph{would} say.) The idea is that if lots of people add suspicious
622 words to their messages, the NSA will get so busy with spurious input
623 that they will have to give up reading it all.
624
625 Here's how to insert spook keywords automatically whenever you start
626 entering an outgoing message:
627
628 @example
629 (add-hook 'mail-setup-hook 'spook)
630 @end example
631
632 Whether or not this confuses the NSA, it at least amuses people.
633
634 @node Fortune
635 @section Putting @code{fortune} Items in Signatures
636
637 @pindex fortune
638 @findex fortune-to-signature
639 @findex fortune-from-region
640 @cindex signatures, mail/news
641 @cindex fortune cookies
642 You can use the @code{fortune} program to create signatures for mail or
643 network news messages. (@code{fortune} prints a random---with luck,
644 interesting---adage, originally inspired by `fortune cookie' messages.)
645 To generate signatures, add @code{fortune-to-signature} to
646 @code{mail-setup-hook} and/or @code{message-setup-hook} as appropriate.
647 You can automatically cut regions to a Fortune file with @kbd{M-x
648 fortune-from-region} and compile your own Fortune database.
649
650 @node Mail Footnotes
651 @section Making Footnotes
652 @cindex footnotes
653
654 @findex footnote-mode
655 @kbd{M-x footnote-mode} toggles a minor mode for making footnotes in
656 mail or network news messages. It is intended for use specifically with
657 Message mode but is not specific to that. It provides commands and
658 keybindings to insert footnotes, go to a given note, delete a note and
659 renumber notes. See the group @code{footnote} for customization and the
660 mode's documentation for keybindings. To set up Footnote mode for all
661 messages, add @code{footnote-mode} to @code{mail-mode-hook} and/or
662 @code{message-mode-hook} as appropriate.
663
664 @node Mail Methods
665 @section Mail-Composition Methods
666 @cindex mail-composition methods
667
668 This chapter describes the usual Emacs mode for editing and sending
669 mail---Mail mode. Emacs has alternative facilities for editing and
670 sending mail, including
671 @cindex MH mail interface
672 @cindex Message mode for sending mail
673 MH-E and Message mode, not documented in this manual.
674 @xref{,MH-E,,mh-e, The Emacs Interface to MH}. @xref{,Message,,message,
675 Message Manual}. You can choose any of them as your preferred method.
676 The commands @code{C-x m}, @code{C-x 4 m} and @code{C-x 5 m} use
677 whichever agent you have specified. So do various other Emacs commands
678 and facilities that send mail.
679
680 @vindex mail-user-agent
681 To specify your mail-composition method, set the variable
682 @code{mail-user-agent}. Currently legitimate values include
683 @code{sendmail-user-agent}, @code{mh-e-user-agent}, and
684 @code{message-user-agent}.
685
686 If you select a different mail-composition method, the information in
687 this chapter about the @samp{*mail*} buffer and Mail mode does not
688 apply; other methods may use completely different commands with a
689 different format in a differently named buffer.
690