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