| blob | 5c5481095e20ef5fde27cb19183d182c9789c382 |
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:
43 "Reading mail with Gnus."
47 "Retrieving new mail."
51 "Preparing (or mangling) new mail after retrieval."
55 "Handling of duplicate mail messages."
59 "Organizing the incoming mail in folders."
63 "Mail files."
68 "Expiring old mail."
72 "Interfacing with procmail and other mail agents."
76 "Various mail options."
80 "*Incoming mail will be split according to this variable.
82 If you'd like, for instance, one mail group for mail from the
84 else, you could do something like this:
86 (setq nnmail-split-methods
91 As you can see, this variable is a list of lists, where the first
95 nnmail will try to match on the header to find a fit.
97 The second element can also be a function. In that case, it will be
98 called narrowed to the headers with the first element of the rule as
99 the argument. It should return a non-nil value if it thinks that the
100 mail belongs in that group.
104 This variable can also have a function as its value, and it can
105 also have a fancy split method as its value. See
106 `nnmail-split-fancy' for an explanation of that syntax."
113 ;; Suggested by Erik Selberg <speed@cs.washington.edu>.
115 "If non-nil, do crossposting if several split methods match the mail.
116 If nil, the first match found will be used."
121 "Regexp that matches group names to be ignored when applying `nnmail-split-fancy-with-parent'.
122 This can also be a list of regexps."
130 "Regexp that matches group names to be ignored when inserting message ids into the cache (`nnmail-cache-insert').
131 This can also be a list of regexps."
138 ;; Added by gord@enci.ucalgary.ca (Gordon Matzigkeit).
140 "If non-nil, nnmail will never delete/move a group's last article.
141 It can be marked expirable, so it will be deleted when it is no longer last.
143 You may need to set this variable if other programs are putting
144 new mail into folder numbers that Gnus has marked as expired."
150 "If non-nil the mail backends will use long file and directory names.
157 "Set the mode bits of all new mail files to this integer."
162 "*Expirable articles that are older than this will be expired.
163 This variable can either be a number (which will be interpreted as a
164 number of days) -- this doesn't have to be an integer. This variable
165 can also be `immediate' and `never'."
172 "Variable that holds function to specify how old articles should be before they are expired.
173 The function will be called with the name of the group that the expiry
174 is to be performed in, and it should return an integer that says how
176 It can also return the values `never' and `immediate'.
178 E.g.:
180 \(setq nnmail-expiry-wait-function
181 (lambda (newsgroup)
185 (t 7))))"
191 "*Variable that says where expired messages should end up.
192 The default value is `delete' (which says to delete the messages),
193 but it can also be a string or a function. If it is a string, expired
194 messages end up in that group. If it is a function, the function is
195 called in a buffer narrowed to the message in question. The function
196 receives one argument, the name of the group the message comes from.
197 The return value should be `delete' or a group name (a string)."
201 function
202 string))
205 "Determine expiry target based on articles using fancy techniques.
208 `nnmail-expiry-target' is set to the function
209 `nnmail-fancy-expiry-target' and HEADER of the article matches REGEXP,
210 the message will be expired to a group determined by invoking
211 `format-time-string' with TARGET used as the format string and the
212 time extracted from the articles' Date header (if missing the current
213 time is used).
215 In the special cases that HEADER is the symbol `to-from', the regexp
216 will try to match against both the From and the To header.
218 Example:
220 \(setq nnmail-fancy-expiry-targets
235 regexp
239 "If non-nil, put Message-IDs of Gcc'd articles into the duplicate cache.
240 If non-nil, also update the cache when copy or move articles."
246 ;; revision 5.29 / p0-85 / Gnus 5.9
247 ;; Variable removed in No Gnus v0.7
250 "*If non-nil, re-split incoming procmail sorted mail."
255 "*If non-nil, scan all incoming procmail sorted mails once.
256 It scans low-level sorted spools even when not required."
262 "Function called to delete files in some mail backends."
268 'copy-file
270 "*Function called to create a copy of a file.
271 This is `add-name-to-file' by default, which means that crossposts
272 will use hard links. If your file system doesn't allow hard
273 links, you could set this variable to `copy-file' instead."
282 nil)
283 "*Hook that will be run after the incoming mail has been transferred.
284 The incoming mail is moved from the specified spool file (which normally is
286 directory. This hook is called after the incoming mail box has been
287 emptied, and can be used to call any mail box programs you have
290 E.g.:
292 \(add-hook 'nnmail-read-incoming-hook
293 (lambda ()
296 ;; The incoming mail box file.
297 (expand-file-name (user-login-name)
298 rmail-spool-directory))))
300 If you have xwatch running, this will alert it that mail has been
301 read.
303 If you use `display-time', you could use something like this:
305 \(add-hook 'nnmail-read-incoming-hook
306 (lambda ()
307 ;; Update the displayed time, since that will clear out
308 ;; the flag that says you have mail.
315 "Hook called before treating incoming mail.
316 The hook is run in a buffer with all the new, incoming mail."
321 "Hook called narrowed to the headers of each message.
322 This can be used to remove excessive spaces (and stuff like
323 that) from the headers before splitting and saving the messages."
328 "Hook called narrowed to each message."
333 "Regexp that matches list identifiers to be removed.
334 This can also be a list of regexps."
341 "Hook called just before starting to handle new incoming mail."
346 "Hook called just after finishing handling new incoming mail."
351 "Hook called before deciding where to split an article.
352 The functions in this hook are free to modify the buffer
353 contents in any way they choose -- the buffer contents are
354 discarded after running the split process."
359 "*A hook called when a new article is spooled."
365 "*The number of articles which indicates a large newsgroup or nil.
366 If the number of articles is greater than the value, verbose
367 messages will be shown to indicate the current status."
373 "Base widget for recursive data structures.
375 This is copy of the `lazy' widget in Emacs 22.1 provided for compatibility."
400 "Widget for customizing splits in the variable of the same name."
414 function
416 )
420 function
424 regexp symbol)
426 regexp
432 regexp))
433 nnmail-split-fancy)
437 "Incoming mail can be split according to this fancy variable.
438 To enable this, set `nnmail-split-methods' to `nnmail-split-fancy'.
440 The format of this variable is SPLIT, where SPLIT can be one of
441 the following:
443 GROUP: Mail will be stored in GROUP (a string).
445 \(FIELD VALUE [- RESTRICT [- RESTRICT [...]]] SPLIT): If the message
446 field FIELD (a regexp) contains VALUE (a regexp), store the messages
447 as specified by SPLIT. If RESTRICT (a regexp) matches some string
448 after FIELD and before the end of the matched VALUE, return nil,
449 otherwise process SPLIT. Multiple RESTRICTs add up, further
450 restricting the possibility of processing SPLIT.
452 \(| SPLIT...): Process each SPLIT expression until one of them matches.
453 A SPLIT expression is said to match if it will cause the mail
454 message to be stored in one or more groups.
456 \(& SPLIT...): Process each SPLIT expression.
458 \(: FUNCTION optional args): Call FUNCTION with the optional args, in
459 the buffer containing the message headers. The return value FUNCTION
460 should be a split, which is then recursively processed.
462 \(! FUNCTION SPLIT): Call FUNCTION with the result of SPLIT. The
463 return value FUNCTION should be a split, which is then recursively
464 processed.
466 junk: Mail will be deleted. Use with care! Do not submerge in water!
467 Example:
468 (setq nnmail-split-fancy
470 ...other.rules.omitted...))
472 FIELD must match a complete field name. VALUE must match a complete
473 word according to the `nnmail-split-fancy-syntax-table' syntax table.
476 FIELD and VALUE can also be Lisp symbols, in that case they are expanded
477 as specified in `nnmail-split-abbrev-alist'.
482 Example:
484 \(setq nnmail-split-methods 'nnmail-split-fancy
485 nnmail-split-fancy
486 ;; Messages from the mailer daemon are not crossposted to any of
487 ;; the ordinary groups. Warnings are put in a separate group
488 ;; from real errors.
491 ;; Non-error messages are crossposted to all relevant
492 ;; groups, but we don't crosspost between the group for the
493 ;; (ding) list and the group for other (ding) related mail.
496 ;; Other mailing lists...
499 ;; Both lists below have the same suffix, so prevent
500 ;; cross-posting to mkpkg.list of messages posted only to
501 ;; the bugs- list, but allow cross-posting when the
502 ;; message was really cross-posted.
505 ;;
506 ;; People...
508 ;; Unmatched mail goes to the catch all group.
520 "*Alist of abbreviations allowed in `nnmail-split-fancy'."
525 "*The approximate number of Message-IDs nnmail will keep in its cache.
526 If this variable is nil, no checking on duplicate messages will be
527 performed."
534 "The file name of the nnmail Message-ID cache."
540 "*If non-nil, nnmail keep a cache of Message-IDs to discover mail duplicates.
541 Three values are valid: nil, which means that nnmail is not to keep a
542 Message-ID cache; `warn', which means that nnmail should insert extra
543 headers to warn the user about the duplication (this is the default);
544 and `delete', which means that nnmail will delete duplicated mails.
546 This variable can also be a function. It will be called from a buffer
547 narrowed to the article in question with the Message-ID as a
548 parameter. It should return nil, `warn' or `delete'."
555 "Extra headers to parse.
556 In addition to the standard headers, these extra headers will be
557 included in NOV headers (and the like) when backends parse headers."
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.
1429 match-data
1441 ;; The searched regexp is \(\(FIELD\).*\)\(VALUE\).
1442 ;; So, start-of-value is the point just before the
1443 ;; beginning of the value, whereas after-header-name
1444 ;; is the point just after the field name.
1447 ;; Start the next search just before the beginning of the
1448 ;; VALUE match.
1450 ;; Handle - RESTRICTs
1452 ;; RESTRICT must start after-header-name and
1453 ;; end after start-of-value, so that, for
1454 ;; (any "foo" - "x-foo" "foo.list")
1455 ;; we do not exclude foo.list just because
1456 ;; the header is: ``To: x-foo, foo''
1459 after-header-name t)
1465 ;; Someone might want to do a \N sub on this match, so
1466 ;; restore the match data.
1471 split-result))
1473 ;; Not in cache, compute a regexp for the field/value pair.
1478 partial-front
1479 partial-rear
1480 regexp)
1487 ;; Same trick for the rear of the regexp
1492 ;; Invert the match-partial-words behavior if the optional
1493 ;; last element is specified.
1498 nnmail-split-fancy-match-partial-words)
1504 field)
1508 value
1512 ;; Now that it's in the cache, just call nnmail-split-it again
1513 ;; on the same split, which will find it immediately in the cache.
1519 c expanded beg N did-expand)
1528 ;; We hit a \; expand it.
1535 ;; \ followed by some character we don't expand.
1537 ;; \& or \N
1541 ;; We wrapped the searches in parentheses, so we have to
1542 ;; add some parentheses here...
1550 expanded))))
1554 newtext)))
1556 ;; Activate a backend only if it isn't already activated.
1557 ;; If FORCE, re-read the active file even if the backend is
1558 ;; already activated.
1563 force
1566 backend)))))
1573 backend)))
1583 file-time))
1585 t))
1590 ;;;
1591 ;;; nnmail duplicate handling
1592 ;;;
1612 nnmail-treat-duplicates
1616 ;; Weed out the excess number of Message-IDs.
1622 ;; Save the buffer.
1625 t))
1634 ;; this will handle cases like `B r' where the group is nil
1637 id grp subject sender))
1639 ;; Store some information about the group this message is written
1640 ;; to. This is passed in as the grp argument -- all locations this
1641 ;; has been called from have been checked and the group is available.
1642 ;; The only ambiguous case is nnmail-check-duplication which will only
1643 ;; pass the first (of possibly >1) group which matches. -Josh
1654 nnmail-cache-ignore-groups)))
1673 res))
1675 ;; Fetch the group name corresponding to the message id stored in the
1676 ;; cache.
1688 ;; Function for nnmail-split-fancy: look up all references in the
1689 ;; cache and if a match is found, return that group.
1691 "Split this message into the same group as its parent.
1692 This function can be used as an entry in `nnmail-split-fancy', for
1693 example like this: (: nnmail-split-fancy-with-parent)
1694 For a message to be split, it looks for the parent message in the
1695 References or In-Reply-To header and then looks in the message id
1696 cache file (given by the variable `nnmail-message-id-cache-file') to
1697 see which group that message was put in. This group is returned.
1699 See the Info node `(gnus)Fancy Mail Splitting' for more details."
1707 nnmail-split-fancy-with-parent-ignore-groups
1709 nnmail-split-fancy-with-parent-ignore-groups)))
1719 res)))
1736 ;; If this is a duplicate message, then we do not save it.
1742 nnmail-treat-duplicates)
1746 nnmail-treat-duplicates))))
1747 group-art)
1748 ;; We insert a line that says what the mail source is.
1755 ;; Let the backend save the article (or not).
1760 artnum-func nil junk-func))))
1765 ;; We insert a warning.
1777 ;; Add the group-art list to the history list.
1782 ;;; Get new mail.
1793 "Read new incoming mail."
1797 group in-group spool-func)
1799 fetching-sources
1803 source)
1805 sources)
1807 ;; Use group's parameter
1815 group group spool-func))
1817 ;; Hack to only fetch the contents of a single group's spool file.
1820 group)
1824 :predicate
1836 ;; We first activate all the groups.
1838 ;; Allow the user to hook.
1840 ;; Open the message-id cache.
1842 ;; The we go through all the existing mail source specification
1843 ;; and fetch the mail from each.
1848 source
1853 ',spool-func
1856 nil
1865 ;; If we did indeed read any incoming spools, we save all info.
1877 total))
1878 ;; Close the message-id cache.
1880 ;; Allow the user to hook.
1884 "Say whether an article that is TIME old in GROUP should be expired.
1885 If TIME is nil, then return the cutoff time for oldness instead."
1889 t)
1892 nnmail-expiry-wait)))
1895 inhibit))
1896 ;; This isn't an expirable group.
1897 nil)
1899 ;; We expire all articles on sight.
1902 t))
1904 ;; This is an ange-ftp group, and we don't have any dates.
1905 nil)
1908 ;; Compare the time with the current time.
1916 ;; Do not invoke this from nntp-server-buffer! At least nnfolder clears
1917 ;; that buffer if the nnfolder group isn't selected.
1919 ;; Don't enter Message-IDs into cache.
1920 ;; Let users hack it in TARGET function.
1932 "Returns a target expiry group determined by `nnmail-fancy-expiry-targets'."
1949 ;; If the header is to-from then match against the
1950 ;; To or From header
1957 mail-dont-reply-to-names))
1971 "Check (and modify) the syntax of the message in the current buffer."
1979 "Do a `write-region', and then set the file modes."
1985 ;;;
1986 ;;; Status functions
1987 ;;;
1990 "Make status NAME and VALUE part of the current status line."
2002 "Return a status-value alist from STATUS."
2007 ;; Narrow to the status.
2013 ;; Go through all elements and add them to the list.
2018 ;; Implied "yes".
2023 ;; Implied "no".
2025 ;; Unquoted value.
2028 ;; Quoted value.
2031 status)))
2034 "Return a status string from STATUS."
2045 "Generate an overview of where the last mail split put articles."
2055 elem
2060 "Remove all instances of GROUP from `nnmail-split-history'."
2069 "Say whether GROUP has new mail."
2071 found)
2075 his nil)))
2076 found))
2079 "Check to see if point is within the headers of a unix mail message.
2080 Doesn't change point."
2090 ;;; nnmail.el ends here