]> code.delx.au - gnu-emacs/blob - man/rmail.texi
Update years in copyright notice; nfc.
[gnu-emacs] / man / rmail.texi
1 @c This is part of the Emacs manual.
2 @c Copyright (C) 1985, 1986, 1987, 1993, 1994, 1995, 1997, 2001, 2002,
3 @c 2003, 2004, 2005, 2006 Free Software Foundation, Inc.
4 @c See file emacs.texi for copying conditions.
5 @node Rmail, Dired, Sending Mail, Top
6 @chapter Reading Mail with Rmail
7 @cindex Rmail
8 @cindex reading mail
9 @findex rmail
10 @findex rmail-mode
11 @vindex rmail-mode-hook
12
13 Rmail is an Emacs subsystem for reading and disposing of mail that you
14 receive. Rmail stores mail messages in files called Rmail files.
15 Reading the message in an Rmail file is done in a special major mode,
16 Rmail mode, which redefines most letters to run commands for managing
17 mail. The command @code{rmail-mode} is used to switch into Rmail mode,
18 and it runs the hook @code{rmail-mode-hook} as usual, but don't run this
19 command by hand; it can't do a reasonable job unless the buffer is
20 visiting a proper Rmail file.
21
22 @menu
23 * Basic: Rmail Basics. Basic concepts of Rmail, and simple use.
24 * Scroll: Rmail Scrolling. Scrolling through a message.
25 * Motion: Rmail Motion. Moving to another message.
26 * Deletion: Rmail Deletion. Deleting and expunging messages.
27 * Inbox: Rmail Inbox. How mail gets into the Rmail file.
28 * Files: Rmail Files. Using multiple Rmail files.
29 * Output: Rmail Output. Copying message out to files.
30 * Labels: Rmail Labels. Classifying messages by labeling them.
31 * Attrs: Rmail Attributes. Certain standard labels, called attributes.
32 * Reply: Rmail Reply. Sending replies to messages you are viewing.
33 * Summary: Rmail Summary. Summaries show brief info on many messages.
34 * Sort: Rmail Sorting. Sorting messages in Rmail.
35 * Display: Rmail Display. How Rmail displays a message; customization.
36 * Coding: Rmail Coding. How Rmail handles decoding character sets.
37 * Editing: Rmail Editing. Editing message text and headers in Rmail.
38 * Digest: Rmail Digest. Extracting the messages from a digest message.
39 * Out of Rmail:: Converting an Rmail file to mailbox format.
40 * Rot13: Rmail Rot13. Reading messages encoded in the rot13 code.
41 * Movemail:: More details of fetching new mail.
42 * Remote Mailboxes:: Retrieving Mail from Remote Mailboxes.
43 * Other Mailbox Formats:: Retrieving Mail from Local Mailboxes in
44 Various Formats
45 @end menu
46
47 @node Rmail Basics
48 @section Basic Concepts of Rmail
49
50 @cindex primary Rmail file
51 @vindex rmail-file-name
52 Using Rmail in the simplest fashion, you have one Rmail file
53 @file{~/RMAIL} in which all of your mail is saved. It is called your
54 @dfn{primary Rmail file}. The command @kbd{M-x rmail} reads your primary
55 Rmail file, merges new mail in from your inboxes, displays the first
56 message you haven't read yet, and lets you begin reading. The variable
57 @code{rmail-file-name} specifies the name of the primary Rmail file.
58
59 Rmail uses narrowing to hide all but one message in the Rmail file.
60 The message that is shown is called the @dfn{current message}. Rmail
61 mode's special commands can do such things as delete the current
62 message, copy it into another file, send a reply, or move to another
63 message. You can also create multiple Rmail files and use Rmail to move
64 messages between them.
65
66 @cindex message number
67 Within the Rmail file, messages are normally arranged sequentially in
68 order of receipt; you can specify other ways to sort them. Messages are
69 assigned consecutive integers as their @dfn{message numbers}. The
70 number of the current message is displayed in Rmail's mode line,
71 followed by the total number of messages in the file. You can move to a
72 message by specifying its message number with the @kbd{j} key
73 (@pxref{Rmail Motion}).
74
75 @kindex s @r{(Rmail)}
76 @findex rmail-expunge-and-save
77 Following the usual conventions of Emacs, changes in an Rmail file
78 become permanent only when the file is saved. You can save it with
79 @kbd{s} (@code{rmail-expunge-and-save}), which also expunges deleted
80 messages from the file first (@pxref{Rmail Deletion}). To save the
81 file without expunging, use @kbd{C-x C-s}. Rmail also saves the Rmail
82 file after merging new mail from an inbox file (@pxref{Rmail Inbox}).
83
84 @kindex q @r{(Rmail)}
85 @findex rmail-quit
86 @kindex b @r{(Rmail)}
87 @findex rmail-bury
88 You can exit Rmail with @kbd{q} (@code{rmail-quit}); this expunges
89 and saves the Rmail file, then buries the Rmail buffer as well as its
90 summary buffer, if present (@pxref{Rmail Summary}). But there is no
91 need to ``exit'' formally. If you switch from Rmail to editing in
92 other buffers, and never happen to switch back, you have exited. Just
93 make sure to save the Rmail file eventually (like any other file you
94 have changed). @kbd{C-x s} is a good enough way to do this
95 (@pxref{Save Commands}). The Rmail command @kbd{b}, @code{rmail-bury},
96 buries the Rmail buffer and its summary buffer without expunging and
97 saving the Rmail file.
98
99 @node Rmail Scrolling
100 @section Scrolling Within a Message
101
102 When Rmail displays a message that does not fit on the screen, you
103 must scroll through it to read the rest. You could do this with
104 @kbd{C-v}, @kbd{M-v} and @kbd{M-<}, but in Rmail scrolling is so
105 frequent that it deserves to be easier to type.
106
107 @table @kbd
108 @item @key{SPC}
109 Scroll forward (@code{scroll-up}).
110 @item @key{DEL}
111 Scroll backward (@code{scroll-down}).
112 @item .
113 Scroll to start of message (@code{rmail-beginning-of-message}).
114 @end table
115
116 @kindex SPC @r{(Rmail)}
117 @kindex DEL @r{(Rmail)}
118 Since the most common thing to do while reading a message is to scroll
119 through it by screenfuls, Rmail makes @key{SPC} and @key{DEL} synonyms of
120 @kbd{C-v} (@code{scroll-up}) and @kbd{M-v} (@code{scroll-down})
121
122 @kindex . @r{(Rmail)}
123 @findex rmail-beginning-of-message
124 The command @kbd{.} (@code{rmail-beginning-of-message}) scrolls back to the
125 beginning of the selected message. This is not quite the same as @kbd{M-<}:
126 for one thing, it does not set the mark; for another, it resets the buffer
127 boundaries to the current message if you have changed them.
128
129 @node Rmail Motion
130 @section Moving Among Messages
131
132 The most basic thing to do with a message is to read it. The way to
133 do this in Rmail is to make the message current. The usual practice is
134 to move sequentially through the file, since this is the order of
135 receipt of messages. When you enter Rmail, you are positioned at the
136 first message that you have not yet made current (that is, the first one
137 that has the @samp{unseen} attribute; @pxref{Rmail Attributes}). Move
138 forward to see the other new messages; move backward to re-examine old
139 messages.
140
141 @table @kbd
142 @item n
143 Move to the next nondeleted message, skipping any intervening deleted
144 messages (@code{rmail-next-undeleted-message}).
145 @item p
146 Move to the previous nondeleted message
147 (@code{rmail-previous-undeleted-message}).
148 @item M-n
149 Move to the next message, including deleted messages
150 (@code{rmail-next-message}).
151 @item M-p
152 Move to the previous message, including deleted messages
153 (@code{rmail-previous-message}).
154 @item j
155 Move to the first message. With argument @var{n}, move to
156 message number @var{n} (@code{rmail-show-message}).
157 @item >
158 Move to the last message (@code{rmail-last-message}).
159 @item <
160 Move to the first message (@code{rmail-first-message}).
161
162 @item M-s @var{regexp} @key{RET}
163 Move to the next message containing a match for @var{regexp}
164 (@code{rmail-search}).
165
166 @item - M-s @var{regexp} @key{RET}
167 Move to the previous message containing a match for @var{regexp}.
168 @end table
169
170 @kindex n @r{(Rmail)}
171 @kindex p @r{(Rmail)}
172 @kindex M-n @r{(Rmail)}
173 @kindex M-p @r{(Rmail)}
174 @findex rmail-next-undeleted-message
175 @findex rmail-previous-undeleted-message
176 @findex rmail-next-message
177 @findex rmail-previous-message
178 @kbd{n} and @kbd{p} are the usual way of moving among messages in
179 Rmail. They move through the messages sequentially, but skip over
180 deleted messages, which is usually what you want to do. Their command
181 definitions are named @code{rmail-next-undeleted-message} and
182 @code{rmail-previous-undeleted-message}. If you do not want to skip
183 deleted messages---for example, if you want to move to a message to
184 undelete it---use the variants @kbd{M-n} and @kbd{M-p}
185 (@code{rmail-next-message} and @code{rmail-previous-message}). A
186 numeric argument to any of these commands serves as a repeat
187 count.@refill
188
189 In Rmail, you can specify a numeric argument by typing just the
190 digits. You don't need to type @kbd{C-u} first.
191
192 @kindex M-s @r{(Rmail)}
193 @findex rmail-search
194 @cindex searching in Rmail
195 The @kbd{M-s} (@code{rmail-search}) command is Rmail's version of
196 search. The usual incremental search command @kbd{C-s} works in Rmail,
197 but it searches only within the current message. The purpose of
198 @kbd{M-s} is to search for another message. It reads a regular
199 expression (@pxref{Regexps}) nonincrementally, then searches starting at
200 the beginning of the following message for a match. It then selects
201 that message. If @var{regexp} is empty, @kbd{M-s} reuses the regexp
202 used the previous time.
203
204 To search backward in the file for another message, give @kbd{M-s} a
205 negative argument. In Rmail you can do this with @kbd{- M-s}.
206
207 It is also possible to search for a message based on labels.
208 @xref{Rmail Labels}.
209
210 @kindex j @r{(Rmail)}
211 @kindex > @r{(Rmail)}
212 @kindex < @r{(Rmail)}
213 @findex rmail-show-message
214 @findex rmail-last-message
215 @findex rmail-first-message
216 To move to a message specified by absolute message number, use @kbd{j}
217 (@code{rmail-show-message}) with the message number as argument. With
218 no argument, @kbd{j} selects the first message. @kbd{<}
219 (@code{rmail-first-message}) also selects the first message. @kbd{>}
220 (@code{rmail-last-message}) selects the last message.
221
222 @node Rmail Deletion
223 @section Deleting Messages
224
225 @cindex deletion (Rmail)
226 When you no longer need to keep a message, you can @dfn{delete} it. This
227 flags it as ignorable, and some Rmail commands pretend it is no longer
228 present; but it still has its place in the Rmail file, and still has its
229 message number.
230
231 @cindex expunging (Rmail)
232 @dfn{Expunging} the Rmail file actually removes the deleted messages.
233 The remaining messages are renumbered consecutively. Expunging is the only
234 action that changes the message number of any message, except for
235 undigestifying (@pxref{Rmail Digest}).
236
237 @table @kbd
238 @item d
239 Delete the current message, and move to the next nondeleted message
240 (@code{rmail-delete-forward}).
241 @item C-d
242 Delete the current message, and move to the previous nondeleted
243 message (@code{rmail-delete-backward}).
244 @item u
245 Undelete the current message, or move back to a deleted message and
246 undelete it (@code{rmail-undelete-previous-message}).
247 @item x
248 Expunge the Rmail file (@code{rmail-expunge}).
249 @end table
250
251 @kindex d @r{(Rmail)}
252 @kindex C-d @r{(Rmail)}
253 @findex rmail-delete-forward
254 @findex rmail-delete-backward
255 There are two Rmail commands for deleting messages. Both delete the
256 current message and select another message. @kbd{d}
257 (@code{rmail-delete-forward}) moves to the following message, skipping
258 messages already deleted, while @kbd{C-d} (@code{rmail-delete-backward})
259 moves to the previous nondeleted message. If there is no nondeleted
260 message to move to in the specified direction, the message that was just
261 deleted remains current. @kbd{d} with a numeric argument is
262 equivalent to @kbd{C-d}.
263
264 @vindex rmail-delete-message-hook
265 Whenever Rmail deletes a message, it runs the hook
266 @code{rmail-delete-message-hook}. When the hook functions are invoked,
267 the message has been marked deleted, but it is still the current message
268 in the Rmail buffer.
269
270 @cindex undeletion (Rmail)
271 @kindex x @r{(Rmail)}
272 @findex rmail-expunge
273 @kindex u @r{(Rmail)}
274 @findex rmail-undelete-previous-message
275 To make all the deleted messages finally vanish from the Rmail file,
276 type @kbd{x} (@code{rmail-expunge}). Until you do this, you can still
277 @dfn{undelete} the deleted messages. The undeletion command, @kbd{u}
278 (@code{rmail-undelete-previous-message}), is designed to cancel the
279 effect of a @kbd{d} command in most cases. It undeletes the current
280 message if the current message is deleted. Otherwise it moves backward
281 to previous messages until a deleted message is found, and undeletes
282 that message.
283
284 You can usually undo a @kbd{d} with a @kbd{u} because the @kbd{u}
285 moves back to and undeletes the message that the @kbd{d} deleted. But
286 this does not work when the @kbd{d} skips a few already-deleted messages
287 that follow the message being deleted; then the @kbd{u} command
288 undeletes the last of the messages that were skipped. There is no clean
289 way to avoid this problem. However, by repeating the @kbd{u} command,
290 you can eventually get back to the message that you intend to
291 undelete. You can also select a particular deleted message with
292 the @kbd{M-p} command, then type @kbd{u} to undelete it.
293
294 A deleted message has the @samp{deleted} attribute, and as a result
295 @samp{deleted} appears in the mode line when the current message is
296 deleted. In fact, deleting or undeleting a message is nothing more than
297 adding or removing this attribute. @xref{Rmail Attributes}.
298
299 @node Rmail Inbox
300 @section Rmail Files and Inboxes
301 @cindex inbox file
302
303 When you receive mail locally, the operating system places incoming
304 mail for you in a file that we call your @dfn{inbox}. When you start
305 up Rmail, it runs a C program called @code{movemail} to copy the new
306 messages from your local inbox into your primary Rmail file, which
307 also contains other messages saved from previous Rmail sessions. It
308 is in this file that you actually read the mail with Rmail. This
309 operation is called @dfn{getting new mail}. You can get new mail at
310 any time in Rmail by typing @kbd{g}.
311
312 @vindex rmail-primary-inbox-list
313 @cindex @env{MAIL} environment variable
314 The variable @code{rmail-primary-inbox-list} contains a list of the
315 files which are inboxes for your primary Rmail file. If you don't set
316 this variable explicitly, it is initialized from the @env{MAIL}
317 environment variable, or, as a last resort, set to @code{nil}, which
318 means to use the default inbox. The default inbox is
319 @file{/var/mail/@var{username}}, @file{/usr/spool/mail/@var{username}},
320 or @file{/usr/mail/@var{username}}, depending on your operating system.
321
322 To see what the default is on your system, use @kbd{C-h v
323 rmail-primary-inbox-list @key{RET}}. You can specify the inbox file(s) for
324 any Rmail file with the command @code{set-rmail-inbox-list}; see
325 @ref{Rmail Files}.
326
327 There are two reasons for having separate Rmail files and inboxes.
328
329 @enumerate
330 @item
331 The inbox file format varies between operating systems and according to
332 the other mail software in use. Only one part of Rmail needs to know
333 about the alternatives, and it need only understand how to convert all
334 of them to Rmail's own format.
335
336 @item
337 It is very cumbersome to access an inbox file without danger of losing
338 mail, because it is necessary to interlock with mail delivery.
339 Moreover, different operating systems use different interlocking
340 techniques. The strategy of moving mail out of the inbox once and for
341 all into a separate Rmail file avoids the need for interlocking in all
342 the rest of Rmail, since only Rmail operates on the Rmail file.
343 @end enumerate
344
345 Rmail was written to use Babyl format as its internal format. Since
346 then, we have recognized that the usual inbox format on Unix and GNU
347 systems is adequate for the job, and we plan to change Rmail to use that
348 as its internal format. However, the Rmail file will still be separate
349 from the inbox file, even on systems where their format is the same.
350
351 @vindex rmail-preserve-inbox
352 When getting new mail, Rmail first copies the new mail from the inbox
353 file to the Rmail file; then it saves the Rmail file; then it truncates
354 the inbox file. This way, a system crash may cause duplication of mail
355 between the inbox and the Rmail file, but cannot lose mail. If
356 @code{rmail-preserve-inbox} is non-@code{nil}, then Rmail will copy new
357 mail from the inbox file to the Rmail file without truncating the inbox
358 file. You may wish to set this, for example, on a portable computer you
359 use to check your mail via POP while traveling, so that your mail will
360 remain on the server and you can save it later on your workstation.
361
362 In some cases, Rmail copies the new mail from the inbox file
363 indirectly. First it runs the @code{movemail} program to move the mail
364 from the inbox to an intermediate file called
365 @file{~/.newmail-@var{inboxname}}. Then Rmail merges the new mail from
366 that file, saves the Rmail file, and only then deletes the intermediate
367 file. If there is a crash at the wrong time, this file continues to
368 exist, and Rmail will use it again the next time it gets new mail from
369 that inbox.
370
371 If Rmail is unable to convert the data in
372 @file{~/.newmail-@var{inboxname}} into Babyl format, it renames the file
373 to @file{~/RMAILOSE.@var{n}} (@var{n} is an integer chosen to make the
374 name unique) so that Rmail will not have trouble with the data again.
375 You should look at the file, find whatever message confuses Rmail
376 (probably one that includes the control-underscore character, octal code
377 037), and delete it. Then you can use @kbd{1 g} to get new mail from
378 the corrected file.
379
380 @node Rmail Files
381 @section Multiple Rmail Files
382
383 Rmail operates by default on your @dfn{primary Rmail file}, which is named
384 @file{~/RMAIL} and receives your incoming mail from your system inbox file.
385 But you can also have other Rmail files and edit them with Rmail. These
386 files can receive mail through their own inboxes, or you can move messages
387 into them with explicit Rmail commands (@pxref{Rmail Output}).
388
389 @table @kbd
390 @item i @var{file} @key{RET}
391 Read @var{file} into Emacs and run Rmail on it (@code{rmail-input}).
392
393 @item M-x set-rmail-inbox-list @key{RET} @var{files} @key{RET}
394 Specify inbox file names for current Rmail file to get mail from.
395
396 @item g
397 Merge new mail from current Rmail file's inboxes
398 (@code{rmail-get-new-mail}).
399
400 @item C-u g @var{file} @key{RET}
401 Merge new mail from inbox file @var{file}.
402 @end table
403
404 @kindex i @r{(Rmail)}
405 @findex rmail-input
406 To run Rmail on a file other than your primary Rmail file, you may use
407 the @kbd{i} (@code{rmail-input}) command in Rmail. This visits the file
408 in Rmail mode. You can use @kbd{M-x rmail-input} even when not in
409 Rmail.
410
411 The file you read with @kbd{i} should normally be a valid Rmail file.
412 If it is not, Rmail tries to decompose it into a stream of messages in
413 various known formats. If it succeeds, it converts the whole file to an
414 Rmail file. If you specify a file name that doesn't exist, @kbd{i}
415 initializes a new buffer for creating a new Rmail file.
416
417 @vindex rmail-secondary-file-directory
418 @vindex rmail-secondary-file-regexp
419 You can also select an Rmail file from a menu. Choose first the menu
420 bar Classify item, then from the Classify menu choose the Input Rmail
421 File item; then choose the Rmail file you want. The variables
422 @code{rmail-secondary-file-directory} and
423 @code{rmail-secondary-file-regexp} specify which files to offer in the
424 menu: the first variable says which directory to find them in; the
425 second says which files in that directory to offer (all those that match
426 the regular expression). These variables also apply to choosing a file
427 for output (@pxref{Rmail Output}).
428
429 @findex set-rmail-inbox-list
430 Each Rmail file can contain a list of inbox file names; you can specify
431 this list with @kbd{M-x set-rmail-inbox-list @key{RET} @var{files}
432 @key{RET}}. The argument can contain any number of file names, separated
433 by commas. It can also be empty, which specifies that this file should
434 have no inboxes. Once a list of inboxes is specified, the Rmail file
435 remembers it permanently until you specify a different list.
436
437 As a special exception, if your primary Rmail file does not specify any
438 inbox files, it uses your standard system inbox.
439
440 @kindex g @r{(Rmail)}
441 @findex rmail-get-new-mail
442 The @kbd{g} command (@code{rmail-get-new-mail}) merges mail into the
443 current Rmail file from its specified inboxes. If the Rmail file
444 has no inboxes, @kbd{g} does nothing. The command @kbd{M-x rmail}
445 also merges new mail into your primary Rmail file.
446
447 To merge mail from a file that is not the usual inbox, give the
448 @kbd{g} key a numeric argument, as in @kbd{C-u g}. Then it reads a file
449 name and merges mail from that file. The inbox file is not deleted or
450 changed in any way when @kbd{g} with an argument is used. This is,
451 therefore, a general way of merging one file of messages into another.
452
453 @node Rmail Output
454 @section Copying Messages Out to Files
455
456 These commands copy messages from an Rmail file into another file.
457
458 @table @kbd
459 @item o @var{file} @key{RET}
460 Append a copy of the current message to the file @var{file}, using Rmail
461 file format by default (@code{rmail-output-to-rmail-file}).
462
463 @item C-o @var{file} @key{RET}
464 Append a copy of the current message to the file @var{file}, using
465 system inbox file format by default (@code{rmail-output}).
466
467 @item w @var{file} @key{RET}
468 Output just the message body to the file @var{file}, taking the default
469 file name from the message @samp{Subject} header.
470 @end table
471
472 @kindex o @r{(Rmail)}
473 @findex rmail-output-to-rmail-file
474 @kindex C-o @r{(Rmail)}
475 @findex rmail-output
476 The commands @kbd{o} and @kbd{C-o} copy the current message into a
477 specified file. This file may be an Rmail file or it may be in system
478 inbox format; the output commands ascertain the file's format and write
479 the copied message in that format.
480
481 The @kbd{o} and @kbd{C-o} commands differ in two ways: each has its
482 own separate default file name, and each specifies a choice of format to
483 use when the file does not already exist. The @kbd{o} command uses
484 Rmail format when it creates a new file, while @kbd{C-o} uses system
485 inbox format for a new file. The default file name for @kbd{o} is the
486 file name used last with @kbd{o}, and the default file name for
487 @kbd{C-o} is the file name used last with @kbd{C-o}.
488
489 If the output file is an Rmail file currently visited in an Emacs buffer,
490 the output commands copy the message into that buffer. It is up to you
491 to save the buffer eventually in its file.
492
493 @kindex w @r{(Rmail)}
494 @findex rmail-output-body-to-file
495 Sometimes you may receive a message whose body holds the contents of a
496 file. You can save the body to a file (excluding the message header)
497 with the @kbd{w} command (@code{rmail-output-body-to-file}). Often
498 these messages contain the intended file name in the @samp{Subject}
499 field, so the @kbd{w} command uses the @samp{Subject} field as the
500 default for the output file name. However, the file name is read using
501 the minibuffer, so you can specify a different name if you wish.
502
503 You can also output a message to an Rmail file chosen with a menu.
504 Choose first the menu bar Classify item, then from the Classify menu
505 choose the Output Rmail File menu item; then choose the Rmail file you want.
506 This outputs the current message to that file, like the @kbd{o} command.
507 The variables @code{rmail-secondary-file-directory} and
508 @code{rmail-secondary-file-regexp} specify which files to offer in the
509 menu: the first variable says which directory to find them in; the
510 second says which files in that directory to offer (all those that match
511 the regular expression).
512
513 @vindex rmail-delete-after-output
514 Copying a message with @kbd{o} or @kbd{C-o} gives the original copy
515 of the message the @samp{filed} attribute, so that @samp{filed}
516 appears in the mode line when such a message is current. @kbd{w}
517 gives it the @samp{stored} attribute. If you like to keep just a
518 single copy of every mail message, set the variable
519 @code{rmail-delete-after-output} to @code{t}; then the @kbd{o},
520 @kbd{C-o} and @kbd{w} commands delete the original message after
521 copying it. (You can undelete the original afterward if you wish.)
522
523 Copying messages into files in system inbox format uses the header
524 fields that are displayed in Rmail at the time. Thus, if you use the
525 @kbd{t} command to view the entire header and then copy the message, the
526 entire header is copied. @xref{Rmail Display}.
527
528 @vindex rmail-output-file-alist
529 The variable @code{rmail-output-file-alist} lets you specify
530 intelligent defaults for the output file, based on the contents of the
531 current message. The value should be a list whose elements have this
532 form:
533
534 @example
535 (@var{regexp} . @var{name-exp})
536 @end example
537
538 @noindent
539 If there's a match for @var{regexp} in the current message, then the
540 default file name for output is @var{name-exp}. If multiple elements
541 match the message, the first matching element decides the default file
542 name. The subexpression @var{name-exp} may be a string constant giving
543 the file name to use, or more generally it may be any Lisp expression
544 that returns a file name as a string. @code{rmail-output-file-alist}
545 applies to both @kbd{o} and @kbd{C-o}.
546
547 @node Rmail Labels
548 @section Labels
549 @cindex label (Rmail)
550 @cindex attribute (Rmail)
551
552 Each message can have various @dfn{labels} assigned to it as a means
553 of classification. Each label has a name; different names are different
554 labels. Any given label is either present or absent on a particular
555 message. A few label names have standard meanings and are given to
556 messages automatically by Rmail when appropriate; these special labels
557 are called @dfn{attributes}.
558 @ifinfo
559 (@xref{Rmail Attributes}.)
560 @end ifinfo
561 All other labels are assigned only by users.
562
563 @table @kbd
564 @item a @var{label} @key{RET}
565 Assign the label @var{label} to the current message (@code{rmail-add-label}).
566 @item k @var{label} @key{RET}
567 Remove the label @var{label} from the current message (@code{rmail-kill-label}).
568 @item C-M-n @var{labels} @key{RET}
569 Move to the next message that has one of the labels @var{labels}
570 (@code{rmail-next-labeled-message}).
571 @item C-M-p @var{labels} @key{RET}
572 Move to the previous message that has one of the labels @var{labels}
573 (@code{rmail-previous-labeled-message}).
574 @item l @var{labels} @key{RET}
575 @itemx C-M-l @var{labels} @key{RET}
576 Make a summary of all messages containing any of the labels @var{labels}
577 (@code{rmail-summary-by-labels}).
578 @end table
579
580 @kindex a @r{(Rmail)}
581 @kindex k @r{(Rmail)}
582 @findex rmail-add-label
583 @findex rmail-kill-label
584 The @kbd{a} (@code{rmail-add-label}) and @kbd{k}
585 (@code{rmail-kill-label}) commands allow you to assign or remove any
586 label on the current message. If the @var{label} argument is empty, it
587 means to assign or remove the same label most recently assigned or
588 removed.
589
590 Once you have given messages labels to classify them as you wish, there
591 are two ways to use the labels: in moving and in summaries.
592
593 @kindex C-M-n @r{(Rmail)}
594 @kindex C-M-p @r{(Rmail)}
595 @findex rmail-next-labeled-message
596 @findex rmail-previous-labeled-message
597 The command @kbd{C-M-n @var{labels} @key{RET}}
598 (@code{rmail-next-labeled-message}) moves to the next message that has
599 one of the labels @var{labels}. The argument @var{labels} specifies one
600 or more label names, separated by commas. @kbd{C-M-p}
601 (@code{rmail-previous-labeled-message}) is similar, but moves backwards
602 to previous messages. A numeric argument to either command serves as a
603 repeat count.
604
605 The command @kbd{C-M-l @var{labels} @key{RET}}
606 (@code{rmail-summary-by-labels}) displays a summary containing only the
607 messages that have at least one of a specified set of labels. The
608 argument @var{labels} is one or more label names, separated by commas.
609 @xref{Rmail Summary}, for information on summaries.@refill
610
611 If the @var{labels} argument to @kbd{C-M-n}, @kbd{C-M-p} or
612 @kbd{C-M-l} is empty, it means to use the last set of labels specified
613 for any of these commands.
614
615 @node Rmail Attributes
616 @section Rmail Attributes
617
618 Some labels such as @samp{deleted} and @samp{filed} have built-in
619 meanings and are assigned to or removed from messages automatically at
620 appropriate times; these labels are called @dfn{attributes}. Here is a
621 list of Rmail attributes:
622
623 @table @samp
624 @item unseen
625 Means the message has never been current. Assigned to messages when
626 they come from an inbox file, and removed when a message is made
627 current. When you start Rmail, it initially shows the first message
628 that has this attribute.
629 @item deleted
630 Means the message is deleted. Assigned by deletion commands and
631 removed by undeletion commands (@pxref{Rmail Deletion}).
632 @item filed
633 Means the message has been copied to some other file. Assigned by the
634 @kbd{o} and @kbd{C-o} file output commands (@pxref{Rmail Output}).
635 @item stored
636 Assigned by the @kbd{w} file output command (@pxref{Rmail Output}).
637 @item answered
638 Means you have mailed an answer to the message. Assigned by the @kbd{r}
639 command (@code{rmail-reply}). @xref{Rmail Reply}.
640 @item forwarded
641 Means you have forwarded the message. Assigned by the @kbd{f} command
642 (@code{rmail-forward}). @xref{Rmail Reply}.
643 @item edited
644 Means you have edited the text of the message within Rmail.
645 @xref{Rmail Editing}.
646 @item resent
647 Means you have resent the message. Assigned by the command @kbd{M-x
648 rmail-resend}. @xref{Rmail Reply}.
649 @end table
650
651 All other labels are assigned or removed only by the user, and have no
652 standard meaning.
653
654 @node Rmail Reply
655 @section Sending Replies
656
657 Rmail has several commands that use Mail mode to send outgoing mail.
658 @xref{Sending Mail}, for information on using Mail mode, including
659 certain features meant to work with Rmail. What this section documents
660 are the special commands of Rmail for entering Mail mode. Note that the
661 usual keys for sending mail---@kbd{C-x m}, @kbd{C-x 4 m}, and @kbd{C-x 5
662 m}---are available in Rmail mode and work just as they usually do.
663
664 @table @kbd
665 @item m
666 Send a message (@code{rmail-mail}).
667 @item c
668 Continue editing the already started outgoing message (@code{rmail-continue}).
669 @item r
670 Send a reply to the current Rmail message (@code{rmail-reply}).
671 @item f
672 Forward the current message to other users (@code{rmail-forward}).
673 @item C-u f
674 Resend the current message to other users (@code{rmail-resend}).
675 @item M-m
676 Try sending a bounced message a second time (@code{rmail-retry-failure}).
677 @end table
678
679 @kindex r @r{(Rmail)}
680 @findex rmail-reply
681 @cindex reply to a message
682 The most common reason to send a message while in Rmail is to reply to
683 the message you are reading. To do this, type @kbd{r}
684 (@code{rmail-reply}). This displays the @samp{*mail*} buffer in another
685 window, much like @kbd{C-x 4 m}, but preinitializes the @samp{Subject},
686 @samp{To}, @samp{CC} and @samp{In-reply-to} header fields based on the
687 message you are replying to. The @samp{To} field starts out as the
688 address of the person who sent the message you received, and the
689 @samp{CC} field starts out with all the other recipients of that
690 message.
691
692 @vindex rmail-dont-reply-to-names
693 You can exclude certain recipients from being placed automatically in
694 the @samp{CC}, using the variable @code{rmail-dont-reply-to-names}. Its
695 value should be a regular expression (as a string); any recipient that
696 the regular expression matches, is excluded from the @samp{CC} field.
697 The default value matches your own name, and any name starting with
698 @samp{info-}. (Those names are excluded because there is a convention
699 of using them for large mailing lists to broadcast announcements.)
700
701 To omit the @samp{CC} field completely for a particular reply, enter
702 the reply command with a numeric argument: @kbd{C-u r} or @kbd{1 r}.
703
704 Once the @samp{*mail*} buffer has been initialized, editing and
705 sending the mail goes as usual (@pxref{Sending Mail}). You can edit the
706 presupplied header fields if they are not right for you. You can also
707 use the commands of Mail mode (@pxref{Mail Mode}), including @kbd{C-c
708 C-y} which yanks in the message that you are replying to. You can
709 switch to the Rmail buffer, select a different message there, switch
710 back, and yank the new current message.
711
712 @kindex M-m @r{(Rmail)}
713 @findex rmail-retry-failure
714 @cindex retrying a failed message
715 @vindex rmail-retry-ignored-headers
716 Sometimes a message does not reach its destination. Mailers usually
717 send the failed message back to you, enclosed in a @dfn{failure
718 message}. The Rmail command @kbd{M-m} (@code{rmail-retry-failure})
719 prepares to send the same message a second time: it sets up a
720 @samp{*mail*} buffer with the same text and header fields as before. If
721 you type @kbd{C-c C-c} right away, you send the message again exactly
722 the same as the first time. Alternatively, you can edit the text or
723 headers and then send it. The variable
724 @code{rmail-retry-ignored-headers}, in the same format as
725 @code{rmail-ignored-headers} (@pxref{Rmail Display}), controls which
726 headers are stripped from the failed message when retrying it.
727
728 @kindex f @r{(Rmail)}
729 @findex rmail-forward
730 @cindex forwarding a message
731 Another frequent reason to send mail in Rmail is to @dfn{forward} the
732 current message to other users. @kbd{f} (@code{rmail-forward}) makes
733 this easy by preinitializing the @samp{*mail*} buffer with the current
734 message as the text, and a subject designating a forwarded message. All
735 you have to do is fill in the recipients and send. When you forward a
736 message, recipients get a message which is ``from'' you, and which has
737 the original message in its contents.
738
739 @findex unforward-rmail-message
740 Forwarding a message encloses it between two delimiter lines. It also
741 modifies every line that starts with a dash, by inserting @w{@samp{- }}
742 at the start of the line. When you receive a forwarded message, if it
743 contains something besides ordinary text---for example, program source
744 code---you might find it useful to undo that transformation. You can do
745 this by selecting the forwarded message and typing @kbd{M-x
746 unforward-rmail-message}. This command extracts the original forwarded
747 message, deleting the inserted @w{@samp{- }} strings, and inserts it
748 into the Rmail file as a separate message immediately following the
749 current one.
750
751 @findex rmail-resend
752 @dfn{Resending} is an alternative similar to forwarding; the
753 difference is that resending sends a message that is ``from'' the
754 original sender, just as it reached you---with a few added header fields
755 @samp{Resent-From} and @samp{Resent-To} to indicate that it came via
756 you. To resend a message in Rmail, use @kbd{C-u f}. (@kbd{f} runs
757 @code{rmail-forward}, which is programmed to invoke @code{rmail-resend}
758 if you provide a numeric argument.)
759
760 @kindex m @r{(Rmail)}
761 @findex rmail-mail
762 The @kbd{m} (@code{rmail-mail}) command is used to start editing an
763 outgoing message that is not a reply. It leaves the header fields empty.
764 Its only difference from @kbd{C-x 4 m} is that it makes the Rmail buffer
765 accessible for @kbd{C-c C-y}, just as @kbd{r} does. Thus, @kbd{m} can be
766 used to reply to or forward a message; it can do anything @kbd{r} or @kbd{f}
767 can do.@refill
768
769 @kindex c @r{(Rmail)}
770 @findex rmail-continue
771 The @kbd{c} (@code{rmail-continue}) command resumes editing the
772 @samp{*mail*} buffer, to finish editing an outgoing message you were
773 already composing, or to alter a message you have sent.@refill
774
775 @vindex rmail-mail-new-frame
776 If you set the variable @code{rmail-mail-new-frame} to a
777 non-@code{nil} value, then all the Rmail commands to start sending a
778 message create a new frame to edit it in. This frame is deleted when
779 you send the message, or when you use the @samp{Cancel} item in the
780 @samp{Mail} menu.
781
782 All the Rmail commands to send a message use the mail-composition
783 method that you have chosen (@pxref{Mail Methods}).
784
785 @node Rmail Summary
786 @section Summaries
787 @cindex summary (Rmail)
788
789 A @dfn{summary} is a buffer containing one line per message to give
790 you an overview of the mail in an Rmail file. Each line shows the
791 message number and date, the sender, the line count, the labels, and
792 the subject. Moving point in the summary buffer selects messages as
793 you move to their summary lines. Almost all Rmail commands are valid
794 in the summary buffer also; when used there, they apply to the message
795 described by the current line of the summary.
796
797 A summary buffer applies to a single Rmail file only; if you are
798 editing multiple Rmail files, each one can have its own summary buffer.
799 The summary buffer name is made by appending @samp{-summary} to the
800 Rmail buffer's name. Normally only one summary buffer is displayed at a
801 time.
802
803 @menu
804 * Rmail Make Summary:: Making various sorts of summaries.
805 * Rmail Summary Edit:: Manipulating messages from the summary.
806 @end menu
807
808 @node Rmail Make Summary
809 @subsection Making Summaries
810
811 Here are the commands to create a summary for the current Rmail file.
812 Once the Rmail file has a summary buffer, changes in the Rmail file
813 (such as deleting or expunging messages, and getting new mail)
814 automatically update the summary.
815
816 @table @kbd
817 @item h
818 @itemx C-M-h
819 Summarize all messages (@code{rmail-summary}).
820 @item l @var{labels} @key{RET}
821 @itemx C-M-l @var{labels} @key{RET}
822 Summarize messages that have one or more of the specified labels
823 (@code{rmail-summary-by-labels}).
824 @item C-M-r @var{rcpts} @key{RET}
825 Summarize messages that have one or more of the specified recipients
826 (@code{rmail-summary-by-recipients}).
827 @item C-M-t @var{topic} @key{RET}
828 Summarize messages that have a match for the specified regexp
829 @var{topic} in their subjects (@code{rmail-summary-by-topic}).
830 @item C-M-s @var{regexp}
831 Summarize messages whose headers and the subject line match the
832 specified regular expression @var{regexp}
833 (@code{rmail-summary-by-regexp}).
834 @end table
835
836 @kindex h @r{(Rmail)}
837 @findex rmail-summary
838 The @kbd{h} or @kbd{C-M-h} (@code{rmail-summary}) command fills the summary buffer
839 for the current Rmail file with a summary of all the messages in the file.
840 It then displays and selects the summary buffer in another window.
841
842 @kindex l @r{(Rmail)}
843 @kindex C-M-l @r{(Rmail)}
844 @findex rmail-summary-by-labels
845 @kbd{C-M-l @var{labels} @key{RET}} (@code{rmail-summary-by-labels}) makes
846 a partial summary mentioning only the messages that have one or more of the
847 labels @var{labels}. @var{labels} should contain label names separated by
848 commas.@refill
849
850 @kindex C-M-r @r{(Rmail)}
851 @findex rmail-summary-by-recipients
852 @kbd{C-M-r @var{rcpts} @key{RET}} (@code{rmail-summary-by-recipients})
853 makes a partial summary mentioning only the messages that have one or more
854 of the recipients @var{rcpts}. @var{rcpts} should contain mailing
855 addresses separated by commas.@refill
856
857 @kindex C-M-t @r{(Rmail)}
858 @findex rmail-summary-by-topic
859 @kbd{C-M-t @var{topic} @key{RET}} (@code{rmail-summary-by-topic})
860 makes a partial summary mentioning only the messages whose subjects have
861 a match for the regular expression @var{topic}.
862
863 @kindex C-M-s @r{(Rmail)}
864 @findex rmail-summary-by-regexp
865 @kbd{C-M-s @var{regexp} @key{RET}} (@code{rmail-summary-by-regexp})
866 makes a partial summary which mentions only the messages whose headers
867 (including the date and the subject lines) match the regular
868 expression @var{regexp}.
869
870 Note that there is only one summary buffer for any Rmail file; making one
871 kind of summary discards any previously made summary.
872
873 @vindex rmail-summary-window-size
874 @vindex rmail-summary-line-count-flag
875 The variable @code{rmail-summary-window-size} says how many lines to
876 use for the summary window. The variable
877 @code{rmail-summary-line-count-flag} controls whether the summary line
878 for a message should include the line count of the message.
879
880 @node Rmail Summary Edit
881 @subsection Editing in Summaries
882
883 You can use the Rmail summary buffer to do almost anything you can do
884 in the Rmail buffer itself. In fact, once you have a summary buffer,
885 there's no need to switch back to the Rmail buffer.
886
887 You can select and display various messages in the Rmail buffer, from
888 the summary buffer, just by moving point in the summary buffer to
889 different lines. It doesn't matter what Emacs command you use to move
890 point; whichever line point is on at the end of the command, that
891 message is selected in the Rmail buffer.
892
893 Almost all Rmail commands work in the summary buffer as well as in the
894 Rmail buffer. Thus, @kbd{d} in the summary buffer deletes the current
895 message, @kbd{u} undeletes, and @kbd{x} expunges. (However, in the
896 summary buffer, a numeric argument to @kbd{d}, @kbd{C-d} and @kbd{u}
897 serves as a repeat count. A negative argument reverses the meaning of
898 @kbd{d} and @kbd{C-d}.) @kbd{o} and @kbd{C-o} output the current
899 message to a file; @kbd{r} starts a reply to it. You can scroll the
900 current message while remaining in the summary buffer using @key{SPC}
901 and @key{DEL}.
902
903 The Rmail commands to move between messages also work in the summary
904 buffer, but with a twist: they move through the set of messages included
905 in the summary. They also ensure the Rmail buffer appears on the screen
906 (unlike cursor motion commands, which update the contents of the Rmail
907 buffer but don't display it in a window unless it already appears).
908 Here is a list of these commands:
909
910 @table @kbd
911 @item n
912 Move to next line, skipping lines saying `deleted', and select its
913 message.
914 @item p
915 Move to previous line, skipping lines saying `deleted', and select
916 its message.
917 @item M-n
918 Move to next line and select its message.
919 @item M-p
920 Move to previous line and select its message.
921 @item >
922 Move to the last line, and select its message.
923 @item <
924 Move to the first line, and select its message.
925 @item j
926 @itemx @key{RET}
927 Select the message on the current line (ensuring that the RMAIL buffer
928 appears on the screen). With argument @var{n}, select message number
929 @var{n} and move to its line in the summary buffer; this signals an
930 error if the message is not listed in the summary buffer.
931 @item M-s @var{pattern} @key{RET}
932 Search through messages for @var{pattern} starting with the current
933 message; select the message found, and move point in the summary buffer
934 to that message's line.
935 @end table
936
937 @vindex rmail-redisplay-summary
938 Deletion, undeletion, and getting new mail, and even selection of a
939 different message all update the summary buffer when you do them in the
940 Rmail buffer. If the variable @code{rmail-redisplay-summary} is
941 non-@code{nil}, these actions also bring the summary buffer back onto
942 the screen.
943
944 @kindex Q @r{(Rmail summary)}
945 @findex rmail-summary-wipe
946 @kindex q @r{(Rmail summary)}
947 @findex rmail-summary-quit
948 When you are finished using the summary, type @kbd{Q}
949 (@code{rmail-summary-wipe}) to delete the summary buffer's window. You
950 can also exit Rmail while in the summary: @kbd{q}
951 (@code{rmail-summary-quit}) deletes the summary window, then exits from
952 Rmail by saving the Rmail file and switching to another buffer.
953
954 @node Rmail Sorting
955 @section Sorting the Rmail File
956
957 @table @kbd
958 @item M-x rmail-sort-by-date
959 Sort messages of current Rmail file by date.
960
961 @item M-x rmail-sort-by-subject
962 Sort messages of current Rmail file by subject.
963
964 @item M-x rmail-sort-by-author
965 Sort messages of current Rmail file by author's name.
966
967 @item M-x rmail-sort-by-recipient
968 Sort messages of current Rmail file by recipient's names.
969
970 @item M-x rmail-sort-by-correspondent
971 Sort messages of current Rmail file by the name of the other
972 correspondent.
973
974 @item M-x rmail-sort-by-lines
975 Sort messages of current Rmail file by size (number of lines).
976
977 @item M-x rmail-sort-by-keywords @key{RET} @var{labels} @key{RET}
978 Sort messages of current Rmail file by labels. The argument
979 @var{labels} should be a comma-separated list of labels. The order of
980 these labels specifies the order of messages; messages with the first
981 label come first, messages with the second label come second, and so on.
982 Messages which have none of these labels come last.
983 @end table
984
985 The Rmail sort commands perform a @emph{stable sort}: if there is no
986 reason to prefer either one of two messages, their order remains
987 unchanged. You can use this to sort by more than one criterion. For
988 example, if you use @code{rmail-sort-by-date} and then
989 @code{rmail-sort-by-author}, messages from the same author appear in
990 order by date.
991
992 With a numeric argument, all these commands reverse the order of
993 comparison. This means they sort messages from newest to oldest, from
994 biggest to smallest, or in reverse alphabetical order.
995
996 @node Rmail Display
997 @section Display of Messages
998
999 Rmail reformats the header of each message before displaying it for
1000 the first time. Reformatting hides uninteresting header fields to
1001 reduce clutter. You can use the @kbd{t} command to show the entire
1002 header or to repeat the header reformatting operation.
1003
1004 @table @kbd
1005 @item t
1006 Toggle display of complete header (@code{rmail-toggle-header}).
1007 @end table
1008
1009 @vindex rmail-ignored-headers
1010 Reformatting the header involves deleting most header fields, on the
1011 grounds that they are not interesting. The variable
1012 @code{rmail-ignored-headers} holds a regular expression that specifies
1013 which header fields to hide in this way---if it matches the beginning of
1014 a header field, that whole field is hidden.
1015
1016 @kindex t @r{(Rmail)}
1017 @findex rmail-toggle-header
1018 Rmail saves the complete original header before reformatting; to see
1019 it, use the @kbd{t} command (@code{rmail-toggle-header}). This
1020 discards the reformatted headers of the current message and displays it
1021 with the original header. Repeating @kbd{t} reformats the message
1022 again. Selecting the message again also reformats.
1023
1024 One consequence of this is that if you edit the reformatted header
1025 (using @kbd{e}; @pxref{Rmail Editing}), subsequent use of @kbd{t} will
1026 discard your edits. On the other hand, if you use @kbd{e} after
1027 @kbd{t}, to edit the original (unreformatted) header, those changes are
1028 permanent.
1029
1030 When the @kbd{t} command has a prefix argument, a positive argument
1031 means to show the reformatted header, and a zero or negative argument
1032 means to show the full header.
1033
1034 @vindex rmail-highlighted-headers
1035 When the terminal supports multiple fonts or colors, Rmail
1036 highlights certain header fields that are especially interesting---by
1037 default, the @samp{From} and @samp{Subject} fields. The variable
1038 @code{rmail-highlighted-headers} holds a regular expression that
1039 specifies the header fields to highlight; if it matches the beginning
1040 of a header field, that whole field is highlighted.
1041
1042 If you specify unusual colors for your text foreground and
1043 background, the colors used for highlighting may not go well with
1044 them. If so, specify different colors for the face
1045 @code{rmail-highlight-face}. @xref{Faces}, for how to do this. To
1046 turn off highlighting entirely in Rmail, set
1047 @code{rmail-highlighted-headers} to @code{nil}.
1048
1049 You can highlight and activate URLs in incoming messages by adding
1050 the function @code{goto-address} to the hook
1051 @code{rmail-show-message-hook}. Then you can browse these URLs by
1052 clicking on them with @kbd{Mouse-2} (or @kbd{Mouse-1} quickly) or by
1053 moving to one and typing @kbd{C-c @key{RET}}. @xref{Goto-address,
1054 Activating URLs, Activating URLs}.
1055
1056 @node Rmail Coding
1057 @section Rmail and Coding Systems
1058
1059 @cindex decoding mail messages (Rmail)
1060 Rmail automatically decodes messages which contain non-@acronym{ASCII}
1061 characters, just as Emacs does with files you visit and with subprocess
1062 output. Rmail uses the standard @samp{charset=@var{charset}} header in
1063 the message, if any, to determine how the message was encoded by the
1064 sender. It maps @var{charset} into the corresponding Emacs coding
1065 system (@pxref{Coding Systems}), and uses that coding system to decode
1066 message text. If the message header doesn't have the @samp{charset}
1067 specification, or if @var{charset} is not recognized,
1068 Rmail chooses the coding system with the usual Emacs heuristics and
1069 defaults (@pxref{Recognize Coding}).
1070
1071 @cindex fixing incorrectly decoded mail messages
1072 Occasionally, a message is decoded incorrectly, either because Emacs
1073 guessed the wrong coding system in the absence of the @samp{charset}
1074 specification, or because the specification was inaccurate. For
1075 example, a misconfigured mailer could send a message with a
1076 @samp{charset=iso-8859-1} header when the message is actually encoded
1077 in @code{koi8-r}. When you see the message text garbled, or some of
1078 its characters displayed as empty boxes, this may have happened.
1079
1080 @findex rmail-redecode-body
1081 You can correct the problem by decoding the message again using the
1082 right coding system, if you can figure out or guess which one is
1083 right. To do this, invoke the @kbd{M-x rmail-redecode-body} command.
1084 It reads the name of a coding system, encodes the message body using
1085 whichever coding system was used to decode it before, then redecodes
1086 it using the coding system you specified. If you specified the right
1087 coding system, the result should be readable.
1088
1089 Decoding and encoding using the wrong coding system is lossless for
1090 most encodings, in particular with 8-bit encodings such as iso-8859 or
1091 koi8. So, if the initial attempt to redecode the message didn't
1092 result in a legible text, you can try other coding systems until you
1093 succeed.
1094
1095 With some coding systems, notably those from the iso-2022 family,
1096 information can be lost in decoding, so that encoding the message
1097 again won't bring back the original incoming text. In such a case,
1098 @code{rmail-redecode-body} cannot work. However, the problems that
1099 call for use of @code{rmail-redecode-body} rarely occur with those
1100 coding systems. So in practice the command works when you need it.
1101
1102 @node Rmail Editing
1103 @section Editing Within a Message
1104
1105 Most of the usual Emacs commands are available in Rmail mode, though a
1106 few, such as @kbd{C-M-n} and @kbd{C-M-h}, are redefined by Rmail for
1107 other purposes. However, the Rmail buffer is normally read only, and
1108 most of the letters are redefined as Rmail commands. If you want to
1109 edit the text of a message, you must use the Rmail command @kbd{e}.
1110
1111 @table @kbd
1112 @item e
1113 Edit the current message as ordinary text.
1114 @end table
1115
1116 @kindex e @r{(Rmail)}
1117 @findex rmail-edit-current-message
1118 The @kbd{e} command (@code{rmail-edit-current-message}) switches from
1119 Rmail mode into Rmail Edit mode, another major mode which is nearly the
1120 same as Text mode. The mode line indicates this change.
1121
1122 In Rmail Edit mode, letters insert themselves as usual and the Rmail
1123 commands are not available. When you are finished editing the message and
1124 are ready to go back to Rmail, type @kbd{C-c C-c}, which switches back to
1125 Rmail mode. Alternatively, you can return to Rmail mode but cancel all the
1126 editing that you have done, by typing @kbd{C-c C-]}.
1127
1128 @vindex rmail-edit-mode-hook
1129 Entering Rmail Edit mode runs the hook @code{text-mode-hook}; then it
1130 runs the hook @code{rmail-edit-mode-hook} (@pxref{Hooks}). It adds the
1131 attribute @samp{edited} to the message. It also displays the full
1132 headers of the message, so that you can edit the headers as well as the
1133 body of the message, and your changes in the headers will be
1134 permanent.
1135
1136 @node Rmail Digest
1137 @section Digest Messages
1138 @cindex digest message
1139 @cindex undigestify
1140
1141 A @dfn{digest message} is a message which exists to contain and carry
1142 several other messages. Digests are used on some moderated mailing
1143 lists; all the messages that arrive for the list during a period of time
1144 such as one day are put inside a single digest which is then sent to the
1145 subscribers. Transmitting the single digest uses much less computer
1146 time than transmitting the individual messages even though the total
1147 size is the same, because the per-message overhead in network mail
1148 transmission is considerable.
1149
1150 @findex undigestify-rmail-message
1151 When you receive a digest message, the most convenient way to read it is
1152 to @dfn{undigestify} it: to turn it back into many individual messages.
1153 Then you can read and delete the individual messages as it suits you.
1154 To do this, select the digest message and type the command @kbd{M-x
1155 undigestify-rmail-message}. This extracts the submessages as separate
1156 Rmail messages, and inserts them following the digest. The digest
1157 message itself is flagged as deleted.
1158
1159 @node Out of Rmail
1160 @section Converting an Rmail File to Inbox Format
1161 @cindex Babyl format to Inbox format
1162 @cindex converting Rmail file to mailbox format
1163
1164 @findex unrmail
1165 The command @kbd{M-x unrmail} converts a file in Rmail format to inbox
1166 format (also known as the system mailbox, or mbox, format), so that
1167 you can use it with other mail-editing tools. You must specify two
1168 arguments, the name of the Rmail file and the name to use for the
1169 converted file. @kbd{M-x unrmail} does not alter the Rmail file itself.
1170
1171 @pindex b2m
1172 @kbd{M-x unrmail} is useful if you can run Emacs on the machine
1173 where the Rmail file resides, or can access the Rmail file remotely
1174 (@pxref{Remote Files}) from a machine where Emacs is installed. If
1175 accessing Rmail files from Emacs is impossible, you can use the
1176 @command{b2m} program instead. @command{b2m} is part of the Emacs
1177 distribution, it is installed into the same directory where all the
1178 other auxiliary programs (@command{etags} etc.) are installed, and its
1179 source is available in the Emacs source distribution, so that you
1180 could copy the source to the target machine and compile it there.
1181
1182 To convert a file @file{@var{babyl-file}} into @file{@var{mbox-file}},
1183 invoke @command{b2m} like this:
1184
1185 @example
1186 b2m < @var{babyl-file} > @var{mbox-file}
1187 @end example
1188
1189 @node Rmail Rot13
1190 @section Reading Rot13 Messages
1191 @cindex rot13 code
1192
1193 Mailing list messages that might offend some readers are sometimes
1194 encoded in a simple code called @dfn{rot13}---so named because it
1195 rotates the alphabet by 13 letters. This code is not for secrecy, as it
1196 provides none; rather, it enables those who might be offended to avoid
1197 ever seeing the real text of the message.
1198
1199 @findex rot13-other-window
1200 To view a buffer using the rot13 code, use the command @kbd{M-x
1201 rot13-other-window}. This displays the current buffer in another window
1202 which applies the code when displaying the text.
1203
1204 @node Movemail
1205 @section @code{movemail} program
1206 @cindex @code{movemail} program
1207
1208 When invoked for the first time, Rmail attempts to locate the
1209 @code{movemail} program and determine its version. There are two
1210 versions of @code{movemail} program: the native one, shipped with GNU
1211 Emacs (the ``emacs version'') and the one included in GNU mailutils
1212 (the ``mailutils version,'' @pxref{movemail,,,mailutils,GNU
1213 mailutils}). They support the same command line syntax and the same
1214 basic subset of options. However, the @samp{mailutils} version offers
1215 additional features.
1216
1217 The Emacs version of @code{movemail} is able to retrieve mail from
1218 usual UNIX mailbox formats and from remote mailboxes using the POP3
1219 protocol.
1220
1221 The Mailutils version is able to handle a wide set of mailbox
1222 formats, such as plain UNIX mailboxes, @code{maildir} and @code{MH}
1223 mailboxes, etc. It is able to retrieve remote mail using POP3 or
1224 IMAP4 protocol, and can retrieve mail from them using a TLS encrypted
1225 channel. It also accepts mailbox argument in the @acronym{URL} form.
1226 The detailed description of mailbox @acronym{URL}s can be found in
1227 @ref{URL,,,mailutils,Mailbox URL Formats}. In short, a @acronym{URL}
1228 is:
1229
1230 @smallexample
1231 @var{proto}://[@var{user}[:@var{password}]@@]@var{host-or-file-name}
1232 @end smallexample
1233
1234 @noindent
1235 where square brackets denote optional elements.
1236
1237 @table @var
1238 @item proto
1239 Specifies the @dfn{mailbox protocol}, or @dfn{format} to
1240 use. The exact semantics of the rest of @acronym{URL} elements depends
1241 on the actual value of @var{proto}.
1242
1243 @item user
1244 User name to access the remote mailbox.
1245
1246 @item password
1247 User password to access the remote mailbox.
1248
1249 @item host-or-file-name
1250 Hostname of the remote server for remote mailboxes or file name of a
1251 local mailbox.
1252 @end table
1253
1254 @var{Proto} can be one of:
1255
1256 @table @asis
1257 @item mbox
1258 Usual UNIX mailbox format. In this case, neither @var{user} nor
1259 @var{pass} are used, and @var{host-or-file-name} denotes the file name of
1260 the mailbox file, e.g., @code{mbox://var/spool/mail/smith}.
1261
1262 @item mh
1263 A local mailbox in the @acronym{MH} format. @var{User} and
1264 @var{pass} are not used. @var{Host-or-file-name} denotes the name of
1265 @acronym{MH} folder, e.g., @code{mh://Mail/inbox}.
1266
1267 @item maildir
1268 A local mailbox in the @acronym{maildir} format. @var{User} and
1269 @var{pass} are not used, and @var{host-or-file-name} denotes the name of
1270 @code{maildir} mailbox, e.g., @code{maildir://mail/inbox}.
1271
1272 @item file
1273 Any local mailbox format. Its actual format is detected automatically
1274 by @code{movemail}.
1275
1276 @item pop
1277 A remote mailbox to be accessed via POP3 protocol. @var{User}
1278 specifies the remote user name to use, @var{pass} may be used to
1279 specify the user password, @var{host-or-file-name} is the name or IP
1280 address of the remote mail server to connect to; e.g.,
1281 @code{pop://smith:guessme@@remote.server.net}.
1282
1283 @item imap
1284 A remote mailbox to be accessed via IMAP4 protocol. @var{User}
1285 specifies the remote user name to use, @var{pass} may be used to
1286 specify the user password, @var{host-or-file-name} is the name or IP
1287 address of the remote mail server to connect to;
1288 e.g., @code{imap://smith:guessme@@remote.server.net}.
1289 @end table
1290
1291 Alternatively, you can specify the file name of the mailbox to use.
1292 This is equivalent to specifying the @samp{file} protocol:
1293
1294 @smallexample
1295 /var/spool/mail/@var{user} @equiv{} file://var/spool/mail/@var{user}
1296 @end smallexample
1297
1298 @vindex rmail-movemail-program
1299 @vindex rmail-movemail-search-path
1300 The variable @code{rmail-movemail-program} controls which version of
1301 @code{movemail} to use. If that is a string, it specifies the
1302 absolute file name of the @code{movemail} executable. If it is
1303 @code{nil}, Rmail searches for @code{movemail} in the directories
1304 listed in @code{rmail-movemail-search-path} and @code{exec-path}, then
1305 in @code{exec-directory}.
1306
1307 @node Remote Mailboxes
1308 @section Retrieving Mail from Remote Mailboxes
1309 @pindex movemail
1310
1311 Some sites use a method called POP for accessing users' inbox data
1312 instead of storing the data in inbox files. The @code{Emacs
1313 movemail} can work with POP if you compile it with the macro
1314 @code{MAIL_USE_POP} defined. (You can achieve that by specifying
1315 @samp{--with-pop} when you run @code{configure} during the
1316 installation of Emacs.)
1317
1318 The @code{Mailutils movemail} by default supports POP, unless configured
1319 with @samp{--disable-pop} option.
1320
1321 Both versions of @code{movemail} only work with POP3, not with older
1322 versions of POP.
1323
1324 @cindex @env{MAILHOST} environment variable
1325 @cindex POP mailboxes
1326 No matter which flavor of @code{movemail} you use, you can specify
1327 POP inbox by using POP @dfn{URL} (@pxref{Movemail}). A POP
1328 @acronym{URL} is a ``file name'' of the form
1329 @samp{pop://@var{username}@@@var{hostname}}, where
1330 @var{hostname} is the host name or IP address of the remote mail
1331 server and @var{username} is the user name on that server.
1332 Additionally, you may specify the password in the mailbox @acronym{URL}:
1333 @samp{pop://@var{username}:@var{password}@@@var{hostname}}. In this
1334 case, @var{password} takes preference over the one set by
1335 @code{rmail-remote-password}. This is especially useful if you have
1336 several remote mailboxes with different passwords.
1337
1338 For backward compatibility Rmail also supports two alternative ways
1339 of specifying remote POP mailboxes. Specifying inbox name in the form
1340 @samp{po:@var{username}:@var{hostname}} is equivalent to
1341 @samp{pop://@var{username}@@@var{hostname}}. Alternatively, you may set
1342 a ``file name'' of @samp{po:@var{username}} in the inbox list of an
1343 Rmail file. @code{Movemail} will handle such a name by opening a
1344 connection to the POP server. The @env{MAILHOST} environment variable
1345 will in this case specify the machine to look for the server on.
1346
1347 @cindex IMAP mailboxes
1348 Another method for accessing remote mailboxes is IMAP. This method is
1349 supported only by the @code{mailutils movemail}. To specify an IMAP
1350 mailbox in the inbox list, use the following mailbox @acronym{URL}:
1351 @samp{imap://@var{username}[:@var{password}]@@@var{hostname}}. The
1352 @var{password} part is optional, as described above.
1353
1354 @vindex rmail-remote-password
1355 @vindex rmail-remote-password-required
1356 @vindex rmail-pop-password
1357 @vindex rmail-pop-password-required
1358 Accessing a remote mailbox may require a password. Rmail uses the
1359 following algorithm to retrieve it:
1360
1361 @enumerate
1362 @item
1363 If the @var{password} is present in mailbox URL (see above), it is
1364 used.
1365 @item
1366 If the variable @code{rmail-remote-password} is non-@code{nil}, its
1367 value is used.
1368 @item
1369 Otherwise, if @code{rmail-remote-password-required} is non-@code{nil},
1370 then Rmail will ask you for the password to use.
1371 @item
1372 Otherwise, Rmail assumes no password is required.
1373 @end enumerate
1374
1375 For compatibility with previous versions, @code{rmail-pop-password}
1376 and @code{rmail-pop-password-required} may be used instead of
1377 @code{rmail-remote-password} and @code{rmail-remote-password-required}.
1378
1379 @vindex rmail-movemail-flags
1380 If you need to pass additional command-line flags to @code{movemail},
1381 set the variable @code{rmail-movemail-flags} a list of the flags you
1382 wish to use. Do not use this variable to pass the @samp{-p} flag to
1383 preserve your inbox contents; use @code{rmail-preserve-inbox} instead.
1384
1385 @cindex Kerberos POP authentication
1386 The @code{movemail} program installed at your site may support
1387 Kerberos authentication. If it is
1388 supported, it is used by default whenever you attempt to retrieve
1389 POP mail when @code{rmail-pop-password} and
1390 @code{rmail-pop-password-required} are unset.
1391
1392 @cindex reverse order in POP inboxes
1393 Some POP servers store messages in reverse order. If your server does
1394 this, and you would rather read your mail in the order in which it was
1395 received, you can tell @code{movemail} to reverse the order of
1396 downloaded messages by adding the @samp{-r} flag to
1397 @code{rmail-movemail-flags}.
1398
1399 @cindex TLS encryption (Rmail)
1400 @code{Mailutils movemail} supports TLS encryption. If you wish to
1401 use it, add the @samp{--tls} flag to @code{rmail-movemail-flags}.
1402
1403 @node Other Mailbox Formats
1404 @section Retrieving Mail from Local Mailboxes in Various Formats
1405
1406 If your incoming mail is stored on a local machine in a format other
1407 than UNIX mailbox, you will need the @code{mailutils movemail} to retrieve
1408 it. @xref{Movemail}, for the detailed description of @code{movemail}
1409 versions.
1410
1411 For example, to retrieve mail from a @code{maildir} inbox located in
1412 @file{/var/spool/mail/in}, you would set the following in Rmail inbox list:
1413
1414 @smallexample
1415 maildir://var/spool/mail/in
1416 @end smallexample
1417
1418 @ignore
1419 arch-tag: 034965f6-38df-47a2-a9f1-b8bc8ab37e23
1420 @end ignore