| blob | 8906a036779d1124f8630e469c89b1b63aec031a |
1 ;;; nnmail.el --- mail support functions for the Gnus mail backends
3 ;; Copyright (C) 1995-2011 Free Software Foundation, Inc.
5 ;; Author: Lars Magne Ingebrigtsen <larsi@gnus.org>
6 ;; Keywords: news, mail
8 ;; This file is part of GNU Emacs.
10 ;; GNU Emacs is free software: you can redistribute it and/or modify
11 ;; it under the terms of the GNU General Public License as published by
12 ;; the Free Software Foundation, either version 3 of the License, or
13 ;; (at your option) any later version.
15 ;; GNU Emacs is distributed in the hope that it will be useful,
16 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
17 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
18 ;; GNU General Public License for more details.
20 ;; You should have received a copy of the GNU General Public License
21 ;; along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>.
23 ;;; Commentary:
25 ;;; Code:
27 ;; For Emacs <22.2 and XEmacs.
45 "Reading mail with Gnus."
49 "Retrieving new mail."
53 "Preparing (or mangling) new mail after retrieval."
57 "Handling of duplicate mail messages."
61 "Organizing the incoming mail in folders."
65 "Mail files."
70 "Expiring old mail."
74 "Interfacing with procmail and other mail agents."
78 "Various mail options."
82 "*Incoming mail will be split according to this variable.
84 If you'd like, for instance, one mail group for mail from the
86 else, you could do something like this:
88 (setq nnmail-split-methods
93 As you can see, this variable is a list of lists, where the first
97 nnmail will try to match on the header to find a fit.
99 The second element can also be a function. In that case, it will be
100 called narrowed to the headers with the first element of the rule as
101 the argument. It should return a non-nil value if it thinks that the
102 mail belongs in that group.
106 This variable can also have a function as its value, and it can
107 also have a fancy split method as its value. See
108 `nnmail-split-fancy' for an explanation of that syntax."
115 ;; Suggested by Erik Selberg <speed@cs.washington.edu>.
117 "If non-nil, do crossposting if several split methods match the mail.
118 If nil, the first match found will be used."
123 "Regexp that matches group names to be ignored when applying `nnmail-split-fancy-with-parent'.
124 This can also be a list of regexps."
132 "Regexp that matches group names to be ignored when inserting message ids into the cache (`nnmail-cache-insert').
133 This can also be a list of regexps."
140 ;; Added by gord@enci.ucalgary.ca (Gordon Matzigkeit).
142 "If non-nil, nnmail will never delete/move a group's last article.
143 It can be marked expirable, so it will be deleted when it is no longer last.
145 You may need to set this variable if other programs are putting
146 new mail into folder numbers that Gnus has marked as expired."
152 "If non-nil the mail backends will use long file and directory names.
159 "Set the mode bits of all new mail files to this integer."
164 "*Expirable articles that are older than this will be expired.
165 This variable can either be a number (which will be interpreted as a
166 number of days) -- this doesn't have to be an integer. This variable
167 can also be `immediate' and `never'."
174 "Variable that holds function to specify how old articles should be before they are expired.
175 The function will be called with the name of the group that the expiry
176 is to be performed in, and it should return an integer that says how
178 It can also return the values `never' and `immediate'.
180 Eg.:
182 \(setq nnmail-expiry-wait-function
183 (lambda (newsgroup)
187 (t 7))))"
193 "*Variable that says where expired messages should end up.
194 The default value is `delete' (which says to delete the messages),
195 but it can also be a string or a function. If it is a string, expired
196 messages end up in that group. If it is a function, the function is
197 called in a buffer narrowed to the message in question. The function
198 receives one argument, the name of the group the message comes from.
199 The return value should be `delete' or a group name (a string)."
203 function
204 string))
207 "Determine expiry target based on articles using fancy techniques.
210 `nnmail-expiry-target' is set to the function
211 `nnmail-fancy-expiry-target' and HEADER of the article matches REGEXP,
212 the message will be expired to a group determined by invoking
213 `format-time-string' with TARGET used as the format string and the
214 time extracted from the articles' Date header (if missing the current
215 time is used).
217 In the special cases that HEADER is the symbol `to-from', the regexp
218 will try to match against both the From and the To header.
220 Example:
222 \(setq nnmail-fancy-expiry-targets
237 regexp
241 "If non-nil, put Message-IDs of Gcc'd articles into the duplicate cache.
242 If non-nil, also update the cache when copy or move articles."
248 ;; revision 5.29 / p0-85 / Gnus 5.9
249 ;; Variable removed in No Gnus v0.7
252 "*If non-nil, re-split incoming procmail sorted mail."
257 "*If non-nil, scan all incoming procmail sorted mails once.
258 It scans low-level sorted spools even when not required."
264 "Function called to delete files in some mail backends."
270 'copy-file
272 "*Function called to create a copy of a file.
273 This is `add-name-to-file' by default, which means that crossposts
274 will use hard links. If your file system doesn't allow hard
275 links, you could set this variable to `copy-file' instead."
284 nil)
285 "*Hook that will be run after the incoming mail has been transferred.
286 The incoming mail is moved from the specified spool file (which normally is
288 directory. This hook is called after the incoming mail box has been
289 emptied, and can be used to call any mail box programs you have
292 Eg.
294 \(add-hook 'nnmail-read-incoming-hook
295 (lambda ()
298 ;; The incoming mail box file.
299 (expand-file-name (user-login-name)
300 rmail-spool-directory))))
302 If you have xwatch running, this will alert it that mail has been
303 read.
305 If you use `display-time', you could use something like this:
307 \(add-hook 'nnmail-read-incoming-hook
308 (lambda ()
309 ;; Update the displayed time, since that will clear out
310 ;; the flag that says you have mail.
317 "Hook called before treating incoming mail.
318 The hook is run in a buffer with all the new, incoming mail."
323 "Hook called narrowed to the headers of each message.
324 This can be used to remove excessive spaces (and stuff like
325 that) from the headers before splitting and saving the messages."
330 "Hook called narrowed to each message."
335 "Regexp that matches list identifiers to be removed.
336 This can also be a list of regexps."
343 "Hook called just before starting to handle new incoming mail."
348 "Hook called just after finishing handling new incoming mail."
353 "Hook called before deciding where to split an article.
354 The functions in this hook are free to modify the buffer
355 contents in any way they choose -- the buffer contents are
356 discarded after running the split process."
361 "*A hook called when a new article is spooled."
367 "*The number of articles which indicates a large newsgroup or nil.
368 If the number of articles is greater than the value, verbose
369 messages will be shown to indicate the current status."
375 "Base widget for recursive datastructures.
377 This is copy of the `lazy' widget in Emacs 22.1 provided for compatibility."
402 "Widget for customizing splits in the variable of the same name."
416 function
418 )
422 function
426 regexp symbol)
428 regexp
434 regexp))
435 nnmail-split-fancy)
439 "Incoming mail can be split according to this fancy variable.
440 To enable this, set `nnmail-split-methods' to `nnmail-split-fancy'.
442 The format of this variable is SPLIT, where SPLIT can be one of
443 the following:
445 GROUP: Mail will be stored in GROUP (a string).
447 \(FIELD VALUE [- RESTRICT [- RESTRICT [...]]] SPLIT): If the message
448 field FIELD (a regexp) contains VALUE (a regexp), store the messages
449 as specified by SPLIT. If RESTRICT (a regexp) matches some string
450 after FIELD and before the end of the matched VALUE, return nil,
451 otherwise process SPLIT. Multiple RESTRICTs add up, further
452 restricting the possibility of processing SPLIT.
454 \(| SPLIT...): Process each SPLIT expression until one of them matches.
455 A SPLIT expression is said to match if it will cause the mail
456 message to be stored in one or more groups.
458 \(& SPLIT...): Process each SPLIT expression.
460 \(: FUNCTION optional args): Call FUNCTION with the optional args, in
461 the buffer containing the message headers. The return value FUNCTION
462 should be a split, which is then recursively processed.
464 \(! FUNCTION SPLIT): Call FUNCTION with the result of SPLIT. The
465 return value FUNCTION should be a split, which is then recursively
466 processed.
468 junk: Mail will be deleted. Use with care! Do not submerge in water!
469 Example:
470 (setq nnmail-split-fancy
472 ...other.rules.omitted...))
474 FIELD must match a complete field name. VALUE must match a complete
475 word according to the `nnmail-split-fancy-syntax-table' syntax table.
478 FIELD and VALUE can also be Lisp symbols, in that case they are expanded
479 as specified in `nnmail-split-abbrev-alist'.
484 Example:
486 \(setq nnmail-split-methods 'nnmail-split-fancy
487 nnmail-split-fancy
488 ;; Messages from the mailer daemon are not crossposted to any of
489 ;; the ordinary groups. Warnings are put in a separate group
490 ;; from real errors.
493 ;; Non-error messages are crossposted to all relevant
494 ;; groups, but we don't crosspost between the group for the
495 ;; (ding) list and the group for other (ding) related mail.
498 ;; Other mailing lists...
501 ;; Both lists below have the same suffix, so prevent
502 ;; cross-posting to mkpkg.list of messages posted only to
503 ;; the bugs- list, but allow cross-posting when the
504 ;; message was really cross-posted.
507 ;;
508 ;; People...
510 ;; Unmatched mail goes to the catch all group.
522 "*Alist of abbreviations allowed in `nnmail-split-fancy'."
527 "*The approximate number of Message-IDs nnmail will keep in its cache.
528 If this variable is nil, no checking on duplicate messages will be
529 performed."
536 "The file name of the nnmail Message-ID cache."
542 "*If non-nil, nnmail keep a cache of Message-IDs to discover mail duplicates.
543 Three values are valid: nil, which means that nnmail is not to keep a
544 Message-ID cache; `warn', which means that nnmail should insert extra
545 headers to warn the user about the duplication (this is the default);
546 and `delete', which means that nnmail will delete duplicated mails.
548 This variable can also be a function. It will be called from a buffer
549 narrowed to the article in question with the Message-ID as a
550 parameter. It should return nil, `warn' or `delete'."
557 "*Extra headers to parse."
563 "Header lines longer than this limit are excluded from the split function."
569 "Default charset to be used when splitting incoming mail."
575 "Whether the nnmail splitting functionality should MIME decode headers."
581 "Whether to match partial words when fancy splitting.
582 Normally, regexes given in `nnmail-split-fancy' are implicitly surrounded
584 surrounded
585 by anything."
592 This avoids the creation of multiple groups when users send to an address
593 using different case (i.e. mailing-list@domain vs Mailing-List@Domain)."
598 ;;; Internal variables.
608 ;; support the %-hack
610 table)
620 \f
629 mm-text-coding-system
633 ;; This causes Emacs 22.2 and 22.3 to issue a useless warning.
634 ;;(if (and (featurep 'xemacs) (featurep 'file-coding))
637 ;; Work around a bug in many XEmacs 21.5 betas.
638 ;; Cf. http://thread.gmane.org/gmane.emacs.gnus.general/68134
643 "Insert FILE in server buffer safely."
653 t)
657 "Make file name for GROUP."
662 ?. ?_))
664 ;; If this directory exists, we use it directly.
669 ;; If not, we translate dots into slashes.
672 dir))))
676 "Returns an assoc of group names and active ranges.
677 nn*-request-list should have been called before calling this function."
678 ;; Go through all groups from the active list.
683 "Parse the active file in the current buffer and return an alist."
691 group-assoc group max min)
702 group-assoc)))
706 group-assoc))
712 "Save GROUP-ASSOC in ACTIVE-FILE."
720 "Generate an active file from group-alist ALIST."
731 "Find out whether this FILE is to be split into GROUP only.
732 If SOURCE is a directory spec, try to return the group name component."
738 nil)))
739 nil))
744 start message-id content-length do-search end)
754 ;; Skip all the headers in case there are more "From "s...
759 ;; Unquote the ">From " line, if any.
765 ;; Find the Message-ID header.
771 ;; There is no Message-ID here, so we create one.
779 ;; Look for a Content-Length header.
787 ;; We destroy the header, since none of
788 ;; the backends ever use it, and we do not
789 ;; want to confuse other mailers by having
790 ;; a (possibly) faulty header.
803 ;; Go to the beginning of the next article - or to the end
804 ;; of the buffer.
818 count))
821 "Put point at the beginning of the next Unix mbox message."
822 ;; Algorithm used to find the next article in the
823 ;; brain-dead Unix mbox format:
824 ;;
825 ;; 1) Search for "^From ".
826 ;; 2) If we find it, then see whether the previous
827 ;; line is blank and the next line looks like a header.
828 ;; Then it's possible that this is a mail delim, and we use it.
830 found)
850 "Put point at the beginning of the current Unix mbox message."
851 ;; Algorithm used to find the next article in the
852 ;; brain-dead Unix mbox format:
853 ;;
854 ;; 1) Search for "^From ".
855 ;; 2) If we find it, then see whether the previous
856 ;; line is blank and the next line looks like a header.
857 ;; Then it's possible that this is a mail delim, and we use it.
859 found)
881 start message-id content-length end skip head-end)
885 ;; Possibly wrong format?
889 ;; Carry on until the bitter end.
892 end nil)
893 ;; Find the end of the head.
895 start
898 ;; This will never happen, but just to be on the safe side --
899 ;; if there is no head-body delimiter, we search a bit manually.
904 ;; Find the Message-ID header.
912 ;; There is no Message-ID here, so we create one.
915 ;; Look for a Content-Length header.
921 ;; We destroy the header, since none of the backends ever
922 ;; use it, and we do not want to confuse other mailers by
923 ;; having a (possibly) faulty header.
927 ;; Find the end of this article.
931 ;; We try the Content-Length value. The idea: skip over the header
932 ;; separator, then check what happens content-length bytes into the
933 ;; message body. This should be either the end of the buffer, the
934 ;; message separator or a blank line followed by the separator.
935 ;; The blank line should probably be deleted. If neither of the
936 ;; three is met, the content-length header is probably invalid.
951 ;; No Content-Length, so we find the beginning of the next
952 ;; article or the end of the buffer.
956 ;; Allow the backend to save the article.
965 count))
971 start message-id end)
975 ;; Possibly wrong format?
977 ;; Carry on until the bitter end.
980 ;; Find the end of the head.
982 start
985 ;; This will never happen, but just to be on the safe side --
986 ;; if there is no head-body delimiter, we search a bit manually.
991 ;; Find the Message-ID header.
995 ;; There is no Message-ID here, so we create one.
1003 ;; Find the end of this article.
1009 ;; Allow the backend to save the article.
1019 count))
1022 ;; In a maildir, every file contains exactly one mail.
1024 message-id)
1026 ;; Find the end of the head.
1031 ;; This will never happen, but just to be on the safe side --
1032 ;; if there is no head-body delimiter, we search a bit manually.
1037 ;; Find the Message-ID header.
1041 ;; There is no Message-ID here, so we create one.
1049 ;; Allow the backend to save the article.
1060 group artnum-func junk-func)
1061 "Go through the entire INCOMING file and pick out each individual mail.
1062 FUNC will be called with the buffer narrowed to each mail.
1063 INCOMING can also be a buffer object. In that case, the mail
1064 will be copied over from that buffer."
1066 ;; methods to just this group.
1070 nnmail-split-methods))
1072 ;; Insert the incoming file.
1081 0
1084 ;; Handle both babyl, MMDF and unix mail formats, since
1085 ;; movemail will use the former when fetching from a
1086 ;; mailbox, the latter when fetching from a file.
1092 func artnum-func junk-func))
1102 "Look at the headers and return an alist of groups that match.
1103 FUNC will be called with the group name to determine the article number."
1106 group-art method grp)
1110 ;; If there is only just one group to put everything in, we
1111 ;; just return a list with just this one method in.
1114 ;; We do actual comparison.
1115 ;; Copy the article into the work buffer.
1119 ;; Narrow to headers.
1126 ;; Decode MIME headers and charsets.
1130 ;; Fold continuation lines.
1134 ;; Nuke pathologically long headers. Since Gnus applies
1135 ;; pathologically complex regexps to the buffer, lines
1136 ;; that are looong will take longer than the Universe's
1137 ;; existence to process.
1141 nnmail-split-header-length-limit)
1144 ;; Allow washing.
1153 ;; Not a regular split method, so it has to be a
1154 ;; fancy one.
1162 nnmail-split-methods
1166 ;; `nnmail-split-methods' is a function, so we
1167 ;; just call this function here and use the
1168 ;; result.
1178 ;; The article may be "cross-posted" to `junk'. What
1179 ;; to do? Just remove the `junk' spec. Don't really
1180 ;; see anything else to do...
1182 junk-func)
1189 split))))
1190 ;; Go through the split methods to find a match.
1204 nil t)))
1207 pos)
1208 ;; Function to say whether this is a match.
1210 ;; Don't enter the article into the same
1211 ;; group twice.
1214 group-art))
1215 ;; This is the final group, which is used as a
1216 ;; catch-all.
1223 ;; Fall back on "bogus" if all else fails.
1227 ;; Produce a trace if non-empty.
1239 ;; See whether the split methods returned `junk'.
1241 nil
1242 ;; The article may be "cross-posted" to `junk'. What
1243 ;; to do? Just remove the `junk' spec. Don't really
1244 ;; see anything else to do...
1251 "Insert how many lines there are in the body of the mail.
1252 Return the number of characters in the body."
1267 chars)))
1270 "Insert an Xref line based on the (group . article) alist."
1290 ;;; Message washing functions
1293 "Remove excessive whitespace from all headers."
1299 "Remove list identifiers from Subject headers."
1303 nnmail-list-identifiers)))
1308 nil t)
1312 nil t)
1317 "Translate TAB characters into SPACE characters."
1322 "Header line matching mailer producing bogus References lines.
1323 See `nnmail-ignore-broken-references'."
1329 "Ignore the References line and use In-Reply-To
1331 Eudora has a broken References line, but an OK In-Reply-To."
1348 ;;; Utility functions
1354 "Utility function to directly post a message to an nnmail-derived group.
1355 Calls ACCEPT-FUNC (which should be `nnchoke-request-accept-article')
1356 to actually put the message in the right group."
1365 to-newsgroup))
1367 to-newsgroup gnus-command-method)
1369 gnus-command-method))
1376 "Fancy splitting method.
1377 See the documentation for the variable `nnmail-split-fancy' for details."
1382 ;; Alist of split expressions their equivalent regexps.
1385 ;; Return a list of groups matching SPLIT.
1388 ;; nil split
1390 nil)
1392 ;; A group name. Do the \& and \N subs into the string.
1398 ;; Junk the message.
1404 ;; Builtin & operation.
1408 ;; Builtin | operation.
1414 done))
1416 ;; Builtin : operation.
1422 ;; Builtin ! operation.
1426 ;; Check the cache for the regexp for this split.
1439 ;; The searched regexp is \(\(FIELD\).*\)\(VALUE\).
1440 ;; So, start-of-value is the point just before the
1441 ;; beginning of the value, whereas after-header-name
1442 ;; is the point just after the field name.
1445 ;; Start the next search just before the beginning of the
1446 ;; VALUE match.
1448 ;; Handle - RESTRICTs
1450 ;; RESTRICT must start after-header-name and
1451 ;; end after start-of-value, so that, for
1452 ;; (any "foo" - "x-foo" "foo.list")
1453 ;; we do not exclude foo.list just because
1454 ;; the header is: ``To: x-foo, foo''
1457 after-header-name t)
1466 ;; Someone might want to do a \N sub on this match, so get the
1467 ;; correct match positions.
1472 split-result))
1474 ;; Not in cache, compute a regexp for the field/value pair.
1479 partial-front
1480 partial-rear
1481 regexp)
1488 ;; Same trick for the rear of the regexp
1493 ;; Invert the match-partial-words behavior if the optional
1494 ;; last element is specified.
1499 nnmail-split-fancy-match-partial-words)
1505 field)
1509 value
1513 ;; Now that it's in the cache, just call nnmail-split-it again
1514 ;; on the same split, which will find it immediately in the cache.
1520 c expanded beg N did-expand)
1529 ;; We hit a \; expand it.
1536 ;; \ followed by some character we don't expand.
1538 ;; \& or \N
1547 expanded))))
1551 newtext)))
1553 ;; Activate a backend only if it isn't already activated.
1554 ;; If FORCE, re-read the active file even if the backend is
1555 ;; already activated.
1560 force
1563 backend)))))
1570 backend)))
1580 file-time))
1582 t))
1587 ;;;
1588 ;;; nnmail duplicate handling
1589 ;;;
1609 nnmail-treat-duplicates
1613 ;; Weed out the excess number of Message-IDs.
1619 ;; Save the buffer.
1622 t))
1631 ;; this will handle cases like `B r' where the group is nil
1634 id grp subject sender))
1636 ;; Store some information about the group this message is written
1637 ;; to. This is passed in as the grp argument -- all locations this
1638 ;; has been called from have been checked and the group is available.
1639 ;; The only ambiguous case is nnmail-check-duplication which will only
1640 ;; pass the first (of possibly >1) group which matches. -Josh
1651 nnmail-cache-ignore-groups)))
1670 res))
1672 ;; Fetch the group name corresponding to the message id stored in the
1673 ;; cache.
1685 ;; Function for nnmail-split-fancy: look up all references in the
1686 ;; cache and if a match is found, return that group.
1688 "Split this message into the same group as its parent.
1689 This function can be used as an entry in `nnmail-split-fancy', for
1690 example like this: (: nnmail-split-fancy-with-parent)
1691 For a message to be split, it looks for the parent message in the
1692 References or In-Reply-To header and then looks in the message id
1693 cache file (given by the variable `nnmail-message-id-cache-file') to
1694 see which group that message was put in. This group is returned.
1696 See the Info node `(gnus)Fancy Mail Splitting' for more details."
1704 nnmail-split-fancy-with-parent-ignore-groups
1706 nnmail-split-fancy-with-parent-ignore-groups)))
1716 res)))
1733 ;; If this is a duplicate message, then we do not save it.
1739 nnmail-treat-duplicates)
1743 nnmail-treat-duplicates))))
1744 group-art)
1745 ;; We insert a line that says what the mail source is.
1752 ;; Let the backend save the article (or not).
1757 artnum-func nil junk-func))))
1762 ;; We insert a warning.
1774 ;; Add the group-art list to the history list.
1779 ;;; Get new mail.
1790 "Read new incoming mail."
1794 group in-group spool-func)
1796 fetching-sources
1800 incoming incomings source)
1802 sources)
1804 ;; Use group's parameter
1812 group group spool-func))
1814 ;; Hack to only fetch the contents of a single group's spool file.
1817 group)
1821 :predicate
1833 ;; We first activate all the groups.
1835 ;; Allow the user to hook.
1837 ;; Open the message-id cache.
1839 ;; The we go through all the existing mail source specification
1840 ;; and fetch the mail from each.
1844 source
1849 ',spool-func
1852 nil
1857 ;; If we did indeed read any incoming spools, we save all info.
1869 total))
1870 ;; Close the message-id cache.
1872 ;; Allow the user to hook.
1876 "Say whether an article that is TIME old in GROUP should be expired.
1877 If TIME is nil, then return the cutoff time for oldness instead."
1881 t)
1884 nnmail-expiry-wait)))
1887 inhibit))
1888 ;; This isn't an expirable group.
1889 nil)
1891 ;; We expire all articles on sight.
1894 t))
1896 ;; This is an ange-ftp group, and we don't have any dates.
1897 nil)
1900 ;; Compare the time with the current time.
1908 ;; Do not invoke this from nntp-server-buffer! At least nnfolder clears
1909 ;; that buffer if the nnfolder group isn't selected.
1911 ;; Don't enter Message-IDs into cache.
1912 ;; Let users hack it in TARGET function.
1924 "Returns a target expiry group determined by `nnmail-fancy-expiry-targets'."
1941 ;; If the header is to-from then match against the
1942 ;; To or From header
1959 "Check (and modify) the syntax of the message in the current buffer."
1967 "Do a `write-region', and then set the file modes."
1973 ;;;
1974 ;;; Status functions
1975 ;;;
1978 "Make status NAME and VALUE part of the current status line."
1990 "Return a status-value alist from STATUS."
1995 ;; Narrow to the status.
2001 ;; Go through all elements and add them to the list.
2006 ;; Implied "yes".
2011 ;; Implied "no".
2013 ;; Unquoted value.
2016 ;; Quoted value.
2019 status)))
2022 "Return a status string from STATUS."
2033 "Generate an overview of where the last mail split put articles."
2043 elem
2048 "Remove all instances of GROUP from `nnmail-split-history'."
2057 "Say whether GROUP has new mail."
2059 found)
2063 his nil)))
2064 found))
2067 "Check to see if point is within the headers of a unix mail message.
2068 Doesn't change point."
2078 ;;; nnmail.el ends here