| blob | 71bc916a927090c03ce7c9f35b08ac78bffa13d8 |
1 ;;; nnmail.el --- mail support functions for the Gnus mail backends
3 ;; Copyright (C) 1995-2015 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:
42 "Reading mail with Gnus."
46 "Retrieving new mail."
50 "Preparing (or mangling) new mail after retrieval."
54 "Handling of duplicate mail messages."
58 "Organizing the incoming mail in folders."
62 "Mail files."
67 "Expiring old mail."
71 "Interfacing with procmail and other mail agents."
75 "Various mail options."
79 "*Incoming mail will be split according to this variable.
81 If you'd like, for instance, one mail group for mail from the
83 else, you could do something like this:
85 (setq nnmail-split-methods
90 As you can see, this variable is a list of lists, where the first
94 nnmail will try to match on the header to find a fit.
96 The second element can also be a function. In that case, it will be
97 called narrowed to the headers with the first element of the rule as
98 the argument. It should return a non-nil value if it thinks that the
99 mail belongs in that group.
103 This variable can also have a function as its value, and it can
104 also have a fancy split method as its value. See
105 `nnmail-split-fancy' for an explanation of that syntax."
112 ;; Suggested by Erik Selberg <speed@cs.washington.edu>.
114 "If non-nil, do crossposting if several split methods match the mail.
115 If nil, the first match found will be used."
120 "Regexp that matches group names to be ignored when applying `nnmail-split-fancy-with-parent'.
121 This can also be a list of regexps."
129 "Regexp that matches group names to be ignored when inserting message ids into the cache (`nnmail-cache-insert').
130 This can also be a list of regexps."
137 ;; Added by gord@enci.ucalgary.ca (Gordon Matzigkeit).
139 "If non-nil, nnmail will never delete/move a group's last article.
140 It can be marked expirable, so it will be deleted when it is no longer last.
142 You may need to set this variable if other programs are putting
143 new mail into folder numbers that Gnus has marked as expired."
149 "If non-nil the mail backends will use long file and directory names.
156 "Set the mode bits of all new mail files to this integer."
161 "*Expirable articles that are older than this will be expired.
162 This variable can either be a number (which will be interpreted as a
163 number of days) -- this doesn't have to be an integer. This variable
164 can also be `immediate' and `never'."
171 "Variable that holds function to specify how old articles should be before they are expired.
172 The function will be called with the name of the group that the expiry
173 is to be performed in, and it should return an integer that says how
175 It can also return the values `never' and `immediate'.
177 E.g.:
179 \(setq nnmail-expiry-wait-function
180 (lambda (newsgroup)
184 (t 7))))"
190 "*Variable that says where expired messages should end up.
191 The default value is `delete' (which says to delete the messages),
192 but it can also be a string or a function. If it is a string, expired
193 messages end up in that group. If it is a function, the function is
194 called in a buffer narrowed to the message in question. The function
195 receives one argument, the name of the group the message comes from.
196 The return value should be `delete' or a group name (a string)."
200 function
201 string))
204 "Determine expiry target based on articles using fancy techniques.
207 `nnmail-expiry-target' is set to the function
208 `nnmail-fancy-expiry-target' and HEADER of the article matches REGEXP,
209 the message will be expired to a group determined by invoking
210 `format-time-string' with TARGET used as the format string and the
211 time extracted from the articles' Date header (if missing the current
212 time is used).
214 In the special cases that HEADER is the symbol `to-from', the regexp
215 will try to match against both the From and the To header.
217 Example:
219 \(setq nnmail-fancy-expiry-targets
234 regexp
238 "If non-nil, put Message-IDs of Gcc'd articles into the duplicate cache.
239 If non-nil, also update the cache when copy or move articles."
245 ;; revision 5.29 / p0-85 / Gnus 5.9
246 ;; Variable removed in No Gnus v0.7
249 "*If non-nil, re-split incoming procmail sorted mail."
254 "*If non-nil, scan all incoming procmail sorted mails once.
255 It scans low-level sorted spools even when not required."
261 "Function called to delete files in some mail backends."
267 'copy-file
269 "*Function called to create a copy of a file.
270 This is `add-name-to-file' by default, which means that crossposts
271 will use hard links. If your file system doesn't allow hard
272 links, you could set this variable to `copy-file' instead."
281 nil)
282 "*Hook that will be run after the incoming mail has been transferred.
283 The incoming mail is moved from the specified spool file (which normally is
285 directory. This hook is called after the incoming mail box has been
286 emptied, and can be used to call any mail box programs you have
289 E.g.:
291 \(add-hook 'nnmail-read-incoming-hook
292 (lambda ()
295 ;; The incoming mail box file.
296 (expand-file-name (user-login-name)
297 rmail-spool-directory))))
299 If you have xwatch running, this will alert it that mail has been
300 read.
302 If you use `display-time', you could use something like this:
304 \(add-hook 'nnmail-read-incoming-hook
305 (lambda ()
306 ;; Update the displayed time, since that will clear out
307 ;; the flag that says you have mail.
314 "Hook called before treating incoming mail.
315 The hook is run in a buffer with all the new, incoming mail."
320 "Hook called narrowed to the headers of each message.
321 This can be used to remove excessive spaces (and stuff like
322 that) from the headers before splitting and saving the messages."
327 "Hook called narrowed to each message."
332 "Regexp that matches list identifiers to be removed.
333 This can also be a list of regexps."
340 "Hook called just before starting to handle new incoming mail."
345 "Hook called just after finishing handling new incoming mail."
350 "Hook called before deciding where to split an article.
351 The functions in this hook are free to modify the buffer
352 contents in any way they choose -- the buffer contents are
353 discarded after running the split process."
358 "*A hook called when a new article is spooled."
364 "*The number of articles which indicates a large newsgroup or nil.
365 If the number of articles is greater than the value, verbose
366 messages will be shown to indicate the current status."
372 "Base widget for recursive data structures.
374 This is copy of the `lazy' widget in Emacs 22.1 provided for compatibility."
399 "Widget for customizing splits in the variable of the same name."
413 function
415 )
419 function
423 regexp symbol)
425 regexp
431 regexp))
432 nnmail-split-fancy)
436 "Incoming mail can be split according to this fancy variable.
437 To enable this, set `nnmail-split-methods' to `nnmail-split-fancy'.
439 The format of this variable is SPLIT, where SPLIT can be one of
440 the following:
442 GROUP: Mail will be stored in GROUP (a string).
444 \(FIELD VALUE [- RESTRICT [- RESTRICT [...]]] SPLIT): If the message
445 field FIELD (a regexp) contains VALUE (a regexp), store the messages
446 as specified by SPLIT. If RESTRICT (a regexp) matches some string
447 after FIELD and before the end of the matched VALUE, return nil,
448 otherwise process SPLIT. Multiple RESTRICTs add up, further
449 restricting the possibility of processing SPLIT.
451 \(| SPLIT...): Process each SPLIT expression until one of them matches.
452 A SPLIT expression is said to match if it will cause the mail
453 message to be stored in one or more groups.
455 \(& SPLIT...): Process each SPLIT expression.
457 \(: FUNCTION optional args): Call FUNCTION with the optional args, in
458 the buffer containing the message headers. The return value FUNCTION
459 should be a split, which is then recursively processed.
461 \(! FUNCTION SPLIT): Call FUNCTION with the result of SPLIT. The
462 return value FUNCTION should be a split, which is then recursively
463 processed.
465 junk: Mail will be deleted. Use with care! Do not submerge in water!
466 Example:
467 (setq nnmail-split-fancy
469 ...other.rules.omitted...))
471 FIELD must match a complete field name. VALUE must match a complete
472 word according to the `nnmail-split-fancy-syntax-table' syntax table.
475 FIELD and VALUE can also be Lisp symbols, in that case they are expanded
476 as specified in `nnmail-split-abbrev-alist'.
481 Example:
483 \(setq nnmail-split-methods 'nnmail-split-fancy
484 nnmail-split-fancy
485 ;; Messages from the mailer daemon are not crossposted to any of
486 ;; the ordinary groups. Warnings are put in a separate group
487 ;; from real errors.
490 ;; Non-error messages are crossposted to all relevant
491 ;; groups, but we don't crosspost between the group for the
492 ;; (ding) list and the group for other (ding) related mail.
495 ;; Other mailing lists...
498 ;; Both lists below have the same suffix, so prevent
499 ;; cross-posting to mkpkg.list of messages posted only to
500 ;; the bugs- list, but allow cross-posting when the
501 ;; message was really cross-posted.
504 ;;
505 ;; People...
507 ;; Unmatched mail goes to the catch all group.
519 "*Alist of abbreviations allowed in `nnmail-split-fancy'."
524 "*The approximate number of Message-IDs nnmail will keep in its cache.
525 If this variable is nil, no checking on duplicate messages will be
526 performed."
533 "The file name of the nnmail Message-ID cache."
539 "*If non-nil, nnmail keep a cache of Message-IDs to discover mail duplicates.
540 Three values are valid: nil, which means that nnmail is not to keep a
541 Message-ID cache; `warn', which means that nnmail should insert extra
542 headers to warn the user about the duplication (this is the default);
543 and `delete', which means that nnmail will delete duplicated mails.
545 This variable can also be a function. It will be called from a buffer
546 narrowed to the article in question with the Message-ID as a
547 parameter. It should return nil, `warn' or `delete'."
554 "Extra headers to parse.
555 In addition to the standard headers, these extra headers will be
556 included in NOV headers (and the like) when backends parse headers."
562 "Header lines longer than this limit are excluded from the split function."
568 "Default charset to be used when splitting incoming mail."
574 "Whether the nnmail splitting functionality should MIME decode headers."
580 "Whether to match partial words when fancy splitting.
581 Normally, regexes given in `nnmail-split-fancy' are implicitly surrounded
583 surrounded
584 by anything."
591 This avoids the creation of multiple groups when users send to an address
592 using different case (i.e. mailing-list@domain vs Mailing-List@Domain)."
597 ;;; Internal variables.
607 ;; support the %-hack
609 table)
619 \f
628 mm-text-coding-system
632 ;; This causes Emacs 22.2 and 22.3 to issue a useless warning.
633 ;;(if (and (featurep 'xemacs) (featurep 'file-coding))
636 ;; Work around a bug in many XEmacs 21.5 betas.
637 ;; Cf. http://thread.gmane.org/gmane.emacs.gnus.general/68134
642 "Insert FILE in server buffer safely."
652 t)
656 "Make file name for GROUP."
661 ?. ?_))
663 ;; If this directory exists, we use it directly.
668 ;; If not, we translate dots into slashes.
671 dir))))
675 "Returns an assoc of group names and active ranges.
676 nn*-request-list should have been called before calling this function."
677 ;; Go through all groups from the active list.
682 "Parse the active file in the current buffer and return an alist."
690 group-assoc group max min)
701 group-assoc)))
705 group-assoc))
711 "Save GROUP-ASSOC in ACTIVE-FILE."
719 "Generate an active file from group-alist ALIST."
730 "Find out whether this FILE is to be split into GROUP only.
731 If SOURCE is a directory spec, try to return the group name component."
737 nil)))
738 nil))
743 start message-id content-length do-search end)
753 ;; Skip all the headers in case there are more "From "s...
758 ;; Unquote the ">From " line, if any.
764 ;; Find the Message-ID header.
770 ;; There is no Message-ID here, so we create one.
778 ;; Look for a Content-Length header.
786 ;; We destroy the header, since none of
787 ;; the backends ever use it, and we do not
788 ;; want to confuse other mailers by having
789 ;; a (possibly) faulty header.
802 ;; Go to the beginning of the next article - or to the end
803 ;; of the buffer.
817 count))
820 "Put point at the beginning of the next Unix mbox message."
821 ;; Algorithm used to find the next article in the
822 ;; brain-dead Unix mbox format:
823 ;;
824 ;; 1) Search for "^From ".
825 ;; 2) If we find it, then see whether the previous
826 ;; line is blank and the next line looks like a header.
827 ;; Then it's possible that this is a mail delim, and we use it.
829 found)
849 "Put point at the beginning of the current Unix mbox message."
850 ;; Algorithm used to find the next article in the
851 ;; brain-dead Unix mbox format:
852 ;;
853 ;; 1) Search for "^From ".
854 ;; 2) If we find it, then see whether the previous
855 ;; line is blank and the next line looks like a header.
856 ;; Then it's possible that this is a mail delim, and we use it.
858 found)
880 start message-id content-length end skip head-end)
884 ;; Possibly wrong format?
888 ;; Carry on until the bitter end.
891 end nil)
892 ;; Find the end of the head.
894 start
897 ;; This will never happen, but just to be on the safe side --
898 ;; if there is no head-body delimiter, we search a bit manually.
903 ;; Find the Message-ID header.
911 ;; There is no Message-ID here, so we create one.
914 ;; Look for a Content-Length header.
920 ;; We destroy the header, since none of the backends ever
921 ;; use it, and we do not want to confuse other mailers by
922 ;; having a (possibly) faulty header.
926 ;; Find the end of this article.
930 ;; We try the Content-Length value. The idea: skip over the header
931 ;; separator, then check what happens content-length bytes into the
932 ;; message body. This should be either the end of the buffer, the
933 ;; message separator or a blank line followed by the separator.
934 ;; The blank line should probably be deleted. If neither of the
935 ;; three is met, the content-length header is probably invalid.
950 ;; No Content-Length, so we find the beginning of the next
951 ;; article or the end of the buffer.
955 ;; Allow the backend to save the article.
964 count))
970 start message-id end)
974 ;; Possibly wrong format?
976 ;; Carry on until the bitter end.
979 ;; Find the end of the head.
981 start
984 ;; This will never happen, but just to be on the safe side --
985 ;; if there is no head-body delimiter, we search a bit manually.
990 ;; Find the Message-ID header.
994 ;; There is no Message-ID here, so we create one.
1002 ;; Find the end of this article.
1008 ;; Allow the backend to save the article.
1018 count))
1021 ;; In a maildir, every file contains exactly one mail.
1023 message-id)
1025 ;; Find the end of the head.
1030 ;; This will never happen, but just to be on the safe side --
1031 ;; if there is no head-body delimiter, we search a bit manually.
1036 ;; Find the Message-ID header.
1040 ;; There is no Message-ID here, so we create one.
1048 ;; Allow the backend to save the article.
1059 group artnum-func junk-func)
1060 "Go through the entire INCOMING file and pick out each individual mail.
1061 FUNC will be called with the buffer narrowed to each mail.
1062 INCOMING can also be a buffer object. In that case, the mail
1063 will be copied over from that buffer."
1065 ;; methods to just this group.
1069 nnmail-split-methods))
1071 ;; Insert the incoming file.
1080 0
1083 ;; Handle both babyl, MMDF and unix mail formats, since
1084 ;; movemail will use the former when fetching from a
1085 ;; mailbox, the latter when fetching from a file.
1091 func artnum-func junk-func))
1101 "Look at the headers and return an alist of groups that match.
1102 FUNC will be called with the group name to determine the article number."
1105 group-art method grp)
1109 ;; If there is only just one group to put everything in, we
1110 ;; just return a list with just this one method in.
1113 ;; We do actual comparison.
1114 ;; Copy the article into the work buffer.
1118 ;; Narrow to headers.
1125 ;; Decode MIME headers and charsets.
1129 ;; Fold continuation lines.
1133 ;; Nuke pathologically long headers. Since Gnus applies
1134 ;; pathologically complex regexps to the buffer, lines
1135 ;; that are looong will take longer than the Universe's
1136 ;; existence to process.
1140 nnmail-split-header-length-limit)
1143 ;; Allow washing.
1152 ;; Not a regular split method, so it has to be a
1153 ;; fancy one.
1161 nnmail-split-methods
1165 ;; `nnmail-split-methods' is a function, so we
1166 ;; just call this function here and use the
1167 ;; result.
1177 ;; The article may be "cross-posted" to `junk'. What
1178 ;; to do? Just remove the `junk' spec. Don't really
1179 ;; see anything else to do...
1181 junk-func)
1188 split))))
1189 ;; Go through the split methods to find a match.
1203 nil t)))
1206 pos)
1207 ;; Function to say whether this is a match.
1209 ;; Don't enter the article into the same
1210 ;; group twice.
1213 group-art))
1214 ;; This is the final group, which is used as a
1215 ;; catch-all.
1222 ;; Fall back on "bogus" if all else fails.
1226 ;; Produce a trace if non-empty.
1238 ;; See whether the split methods returned `junk'.
1240 nil
1241 ;; The article may be "cross-posted" to `junk'. What
1242 ;; to do? Just remove the `junk' spec. Don't really
1243 ;; see anything else to do...
1250 "Insert how many lines there are in the body of the mail.
1251 Return the number of characters in the body."
1266 chars)))
1269 "Insert an Xref line based on the (group . article) alist."
1289 ;;; Message washing functions
1292 "Remove excessive whitespace from all headers."
1298 "Remove list identifiers from Subject headers."
1302 nnmail-list-identifiers)))
1307 nil t)
1311 nil t)
1316 "Translate TAB characters into SPACE characters."
1321 "Header line matching mailer producing bogus References lines.
1322 See `nnmail-ignore-broken-references'."
1328 "Ignore the References line and use In-Reply-To
1330 Eudora has a broken References line, but an OK In-Reply-To."
1347 ;;; Utility functions
1353 "Utility function to directly post a message to an nnmail-derived group.
1354 Calls ACCEPT-FUNC (which should be `nnchoke-request-accept-article')
1355 to actually put the message in the right group."
1364 to-newsgroup))
1366 to-newsgroup gnus-command-method)
1368 gnus-command-method))
1375 "Fancy splitting method.
1376 See the documentation for the variable `nnmail-split-fancy' for details."
1381 ;; Alist of split expressions their equivalent regexps.
1384 ;; Return a list of groups matching SPLIT.
1387 ;; nil split
1389 nil)
1391 ;; A group name. Do the \& and \N subs into the string.
1397 ;; Junk the message.
1403 ;; Builtin & operation.
1407 ;; Builtin | operation.
1413 done))
1415 ;; Builtin : operation.
1421 ;; Builtin ! operation.
1425 ;; Check the cache for the regexp for this split.
1428 match-data
1440 ;; The searched regexp is \(\(FIELD\).*\)\(VALUE\).
1441 ;; So, start-of-value is the point just before the
1442 ;; beginning of the value, whereas after-header-name
1443 ;; is the point just after the field name.
1446 ;; Start the next search just before the beginning of the
1447 ;; VALUE match.
1449 ;; Handle - RESTRICTs
1451 ;; RESTRICT must start after-header-name and
1452 ;; end after start-of-value, so that, for
1453 ;; (any "foo" - "x-foo" "foo.list")
1454 ;; we do not exclude foo.list just because
1455 ;; the header is: ``To: x-foo, foo''
1458 after-header-name t)
1464 ;; Someone might want to do a \N sub on this match, so
1465 ;; restore the match data.
1470 split-result))
1472 ;; Not in cache, compute a regexp for the field/value pair.
1477 partial-front
1478 partial-rear
1479 regexp)
1486 ;; Same trick for the rear of the regexp
1491 ;; Invert the match-partial-words behavior if the optional
1492 ;; last element is specified.
1497 nnmail-split-fancy-match-partial-words)
1503 field)
1507 value
1511 ;; Now that it's in the cache, just call nnmail-split-it again
1512 ;; on the same split, which will find it immediately in the cache.
1518 c expanded beg N did-expand)
1527 ;; We hit a \; expand it.
1534 ;; \ followed by some character we don't expand.
1536 ;; \& or \N
1540 ;; We wrapped the searches in parentheses, so we have to
1541 ;; add some parentheses here...
1549 expanded))))
1553 newtext)))
1555 ;; Activate a backend only if it isn't already activated.
1556 ;; If FORCE, re-read the active file even if the backend is
1557 ;; already activated.
1562 force
1565 backend)))))
1572 backend)))
1582 file-time))
1584 t))
1589 ;;;
1590 ;;; nnmail duplicate handling
1591 ;;;
1611 nnmail-treat-duplicates
1615 ;; Weed out the excess number of Message-IDs.
1621 ;; Save the buffer.
1624 t))
1633 ;; this will handle cases like `B r' where the group is nil
1636 id grp subject sender))
1638 ;; Store some information about the group this message is written
1639 ;; to. This is passed in as the grp argument -- all locations this
1640 ;; has been called from have been checked and the group is available.
1641 ;; The only ambiguous case is nnmail-check-duplication which will only
1642 ;; pass the first (of possibly >1) group which matches. -Josh
1653 nnmail-cache-ignore-groups)))
1672 res))
1674 ;; Fetch the group name corresponding to the message id stored in the
1675 ;; cache.
1687 ;; Function for nnmail-split-fancy: look up all references in the
1688 ;; cache and if a match is found, return that group.
1690 "Split this message into the same group as its parent.
1691 This function can be used as an entry in `nnmail-split-fancy', for
1692 example like this: (: nnmail-split-fancy-with-parent)
1693 For a message to be split, it looks for the parent message in the
1694 References or In-Reply-To header and then looks in the message id
1695 cache file (given by the variable `nnmail-message-id-cache-file') to
1696 see which group that message was put in. This group is returned.
1698 See the Info node `(gnus)Fancy Mail Splitting' for more details."
1706 nnmail-split-fancy-with-parent-ignore-groups
1708 nnmail-split-fancy-with-parent-ignore-groups)))
1718 res)))
1735 ;; If this is a duplicate message, then we do not save it.
1741 nnmail-treat-duplicates)
1745 nnmail-treat-duplicates))))
1746 group-art)
1747 ;; We insert a line that says what the mail source is.
1754 ;; Let the backend save the article (or not).
1759 artnum-func nil junk-func))))
1764 ;; We insert a warning.
1776 ;; Add the group-art list to the history list.
1781 ;;; Get new mail.
1792 "Read new incoming mail."
1796 group in-group spool-func)
1798 fetching-sources
1802 source)
1804 sources)
1806 ;; Use group's parameter
1814 group group spool-func))
1816 ;; Hack to only fetch the contents of a single group's spool file.
1819 group)
1823 :predicate
1835 ;; We first activate all the groups.
1837 ;; Allow the user to hook.
1839 ;; Open the message-id cache.
1841 ;; The we go through all the existing mail source specification
1842 ;; and fetch the mail from each.
1847 source
1852 ',spool-func
1855 nil
1864 ;; If we did indeed read any incoming spools, we save all info.
1876 total))
1877 ;; Close the message-id cache.
1879 ;; Allow the user to hook.
1883 "Say whether an article that is TIME old in GROUP should be expired.
1884 If TIME is nil, then return the cutoff time for oldness instead."
1888 t)
1891 nnmail-expiry-wait)))
1894 inhibit))
1895 ;; This isn't an expirable group.
1896 nil)
1898 ;; We expire all articles on sight.
1901 t))
1903 ;; This is an ange-ftp group, and we don't have any dates.
1904 nil)
1907 ;; Compare the time with the current time.
1915 ;; Do not invoke this from nntp-server-buffer! At least nnfolder clears
1916 ;; that buffer if the nnfolder group isn't selected.
1918 ;; Don't enter Message-IDs into cache.
1919 ;; Let users hack it in TARGET function.
1931 "Returns a target expiry group determined by `nnmail-fancy-expiry-targets'."
1948 ;; If the header is to-from then match against the
1949 ;; To or From header
1956 mail-dont-reply-to-names))
1970 "Check (and modify) the syntax of the message in the current buffer."
1978 "Do a `write-region', and then set the file modes."
1984 ;;;
1985 ;;; Status functions
1986 ;;;
1989 "Make status NAME and VALUE part of the current status line."
2001 "Return a status-value alist from STATUS."
2006 ;; Narrow to the status.
2012 ;; Go through all elements and add them to the list.
2017 ;; Implied "yes".
2022 ;; Implied "no".
2024 ;; Unquoted value.
2027 ;; Quoted value.
2030 status)))
2033 "Return a status string from STATUS."
2044 "Generate an overview of where the last mail split put articles."
2054 elem
2059 "Remove all instances of GROUP from `nnmail-split-history'."
2068 "Say whether GROUP has new mail."
2070 found)
2074 his nil)))
2075 found))
2078 "Check to see if point is within the headers of a unix mail message.
2079 Doesn't change point."
2089 ;;; nnmail.el ends here