| blob | 5be449e9a6b8a4c08012defa15c4e0dffca66627 |
1 ;;; nnmail.el --- mail support functions for the Gnus mail backends
3 ;; Copyright (C) 1995-2013 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.
47 "Reading mail with Gnus."
51 "Retrieving new mail."
55 "Preparing (or mangling) new mail after retrieval."
59 "Handling of duplicate mail messages."
63 "Organizing the incoming mail in folders."
67 "Mail files."
72 "Expiring old mail."
76 "Interfacing with procmail and other mail agents."
80 "Various mail options."
84 "*Incoming mail will be split according to this variable.
86 If you'd like, for instance, one mail group for mail from the
88 else, you could do something like this:
90 (setq nnmail-split-methods
95 As you can see, this variable is a list of lists, where the first
99 nnmail will try to match on the header to find a fit.
101 The second element can also be a function. In that case, it will be
102 called narrowed to the headers with the first element of the rule as
103 the argument. It should return a non-nil value if it thinks that the
104 mail belongs in that group.
108 This variable can also have a function as its value, and it can
109 also have a fancy split method as its value. See
110 `nnmail-split-fancy' for an explanation of that syntax."
117 ;; Suggested by Erik Selberg <speed@cs.washington.edu>.
119 "If non-nil, do crossposting if several split methods match the mail.
120 If nil, the first match found will be used."
125 "Regexp that matches group names to be ignored when applying `nnmail-split-fancy-with-parent'.
126 This can also be a list of regexps."
134 "Regexp that matches group names to be ignored when inserting message ids into the cache (`nnmail-cache-insert').
135 This can also be a list of regexps."
142 ;; Added by gord@enci.ucalgary.ca (Gordon Matzigkeit).
144 "If non-nil, nnmail will never delete/move a group's last article.
145 It can be marked expirable, so it will be deleted when it is no longer last.
147 You may need to set this variable if other programs are putting
148 new mail into folder numbers that Gnus has marked as expired."
154 "If non-nil the mail backends will use long file and directory names.
161 "Set the mode bits of all new mail files to this integer."
166 "*Expirable articles that are older than this will be expired.
167 This variable can either be a number (which will be interpreted as a
168 number of days) -- this doesn't have to be an integer. This variable
169 can also be `immediate' and `never'."
176 "Variable that holds function to specify how old articles should be before they are expired.
177 The function will be called with the name of the group that the expiry
178 is to be performed in, and it should return an integer that says how
180 It can also return the values `never' and `immediate'.
182 E.g.:
184 \(setq nnmail-expiry-wait-function
185 (lambda (newsgroup)
189 (t 7))))"
195 "*Variable that says where expired messages should end up.
196 The default value is `delete' (which says to delete the messages),
197 but it can also be a string or a function. If it is a string, expired
198 messages end up in that group. If it is a function, the function is
199 called in a buffer narrowed to the message in question. The function
200 receives one argument, the name of the group the message comes from.
201 The return value should be `delete' or a group name (a string)."
205 function
206 string))
209 "Determine expiry target based on articles using fancy techniques.
212 `nnmail-expiry-target' is set to the function
213 `nnmail-fancy-expiry-target' and HEADER of the article matches REGEXP,
214 the message will be expired to a group determined by invoking
215 `format-time-string' with TARGET used as the format string and the
216 time extracted from the articles' Date header (if missing the current
217 time is used).
219 In the special cases that HEADER is the symbol `to-from', the regexp
220 will try to match against both the From and the To header.
222 Example:
224 \(setq nnmail-fancy-expiry-targets
239 regexp
243 "If non-nil, put Message-IDs of Gcc'd articles into the duplicate cache.
244 If non-nil, also update the cache when copy or move articles."
250 ;; revision 5.29 / p0-85 / Gnus 5.9
251 ;; Variable removed in No Gnus v0.7
254 "*If non-nil, re-split incoming procmail sorted mail."
259 "*If non-nil, scan all incoming procmail sorted mails once.
260 It scans low-level sorted spools even when not required."
266 "Function called to delete files in some mail backends."
272 'copy-file
274 "*Function called to create a copy of a file.
275 This is `add-name-to-file' by default, which means that crossposts
276 will use hard links. If your file system doesn't allow hard
277 links, you could set this variable to `copy-file' instead."
286 nil)
287 "*Hook that will be run after the incoming mail has been transferred.
288 The incoming mail is moved from the specified spool file (which normally is
290 directory. This hook is called after the incoming mail box has been
291 emptied, and can be used to call any mail box programs you have
294 E.g.:
296 \(add-hook 'nnmail-read-incoming-hook
297 (lambda ()
300 ;; The incoming mail box file.
301 (expand-file-name (user-login-name)
302 rmail-spool-directory))))
304 If you have xwatch running, this will alert it that mail has been
305 read.
307 If you use `display-time', you could use something like this:
309 \(add-hook 'nnmail-read-incoming-hook
310 (lambda ()
311 ;; Update the displayed time, since that will clear out
312 ;; the flag that says you have mail.
319 "Hook called before treating incoming mail.
320 The hook is run in a buffer with all the new, incoming mail."
325 "Hook called narrowed to the headers of each message.
326 This can be used to remove excessive spaces (and stuff like
327 that) from the headers before splitting and saving the messages."
332 "Hook called narrowed to each message."
337 "Regexp that matches list identifiers to be removed.
338 This can also be a list of regexps."
345 "Hook called just before starting to handle new incoming mail."
350 "Hook called just after finishing handling new incoming mail."
355 "Hook called before deciding where to split an article.
356 The functions in this hook are free to modify the buffer
357 contents in any way they choose -- the buffer contents are
358 discarded after running the split process."
363 "*A hook called when a new article is spooled."
369 "*The number of articles which indicates a large newsgroup or nil.
370 If the number of articles is greater than the value, verbose
371 messages will be shown to indicate the current status."
377 "Base widget for recursive datastructures.
379 This is copy of the `lazy' widget in Emacs 22.1 provided for compatibility."
404 "Widget for customizing splits in the variable of the same name."
418 function
420 )
424 function
428 regexp symbol)
430 regexp
436 regexp))
437 nnmail-split-fancy)
441 "Incoming mail can be split according to this fancy variable.
442 To enable this, set `nnmail-split-methods' to `nnmail-split-fancy'.
444 The format of this variable is SPLIT, where SPLIT can be one of
445 the following:
447 GROUP: Mail will be stored in GROUP (a string).
449 \(FIELD VALUE [- RESTRICT [- RESTRICT [...]]] SPLIT): If the message
450 field FIELD (a regexp) contains VALUE (a regexp), store the messages
451 as specified by SPLIT. If RESTRICT (a regexp) matches some string
452 after FIELD and before the end of the matched VALUE, return nil,
453 otherwise process SPLIT. Multiple RESTRICTs add up, further
454 restricting the possibility of processing SPLIT.
456 \(| SPLIT...): Process each SPLIT expression until one of them matches.
457 A SPLIT expression is said to match if it will cause the mail
458 message to be stored in one or more groups.
460 \(& SPLIT...): Process each SPLIT expression.
462 \(: FUNCTION optional args): Call FUNCTION with the optional args, in
463 the buffer containing the message headers. The return value FUNCTION
464 should be a split, which is then recursively processed.
466 \(! FUNCTION SPLIT): Call FUNCTION with the result of SPLIT. The
467 return value FUNCTION should be a split, which is then recursively
468 processed.
470 junk: Mail will be deleted. Use with care! Do not submerge in water!
471 Example:
472 (setq nnmail-split-fancy
474 ...other.rules.omitted...))
476 FIELD must match a complete field name. VALUE must match a complete
477 word according to the `nnmail-split-fancy-syntax-table' syntax table.
480 FIELD and VALUE can also be Lisp symbols, in that case they are expanded
481 as specified in `nnmail-split-abbrev-alist'.
486 Example:
488 \(setq nnmail-split-methods 'nnmail-split-fancy
489 nnmail-split-fancy
490 ;; Messages from the mailer daemon are not crossposted to any of
491 ;; the ordinary groups. Warnings are put in a separate group
492 ;; from real errors.
495 ;; Non-error messages are crossposted to all relevant
496 ;; groups, but we don't crosspost between the group for the
497 ;; (ding) list and the group for other (ding) related mail.
500 ;; Other mailing lists...
503 ;; Both lists below have the same suffix, so prevent
504 ;; cross-posting to mkpkg.list of messages posted only to
505 ;; the bugs- list, but allow cross-posting when the
506 ;; message was really cross-posted.
509 ;;
510 ;; People...
512 ;; Unmatched mail goes to the catch all group.
524 "*Alist of abbreviations allowed in `nnmail-split-fancy'."
529 "*The approximate number of Message-IDs nnmail will keep in its cache.
530 If this variable is nil, no checking on duplicate messages will be
531 performed."
538 "The file name of the nnmail Message-ID cache."
544 "*If non-nil, nnmail keep a cache of Message-IDs to discover mail duplicates.
545 Three values are valid: nil, which means that nnmail is not to keep a
546 Message-ID cache; `warn', which means that nnmail should insert extra
547 headers to warn the user about the duplication (this is the default);
548 and `delete', which means that nnmail will delete duplicated mails.
550 This variable can also be a function. It will be called from a buffer
551 narrowed to the article in question with the Message-ID as a
552 parameter. It should return nil, `warn' or `delete'."
559 "Extra headers to parse.
560 In addition to the standard headers, these extra headers will be
561 included in NOV headers (and the like) when backends parse headers."
567 "Header lines longer than this limit are excluded from the split function."
573 "Default charset to be used when splitting incoming mail."
579 "Whether the nnmail splitting functionality should MIME decode headers."
585 "Whether to match partial words when fancy splitting.
586 Normally, regexes given in `nnmail-split-fancy' are implicitly surrounded
588 surrounded
589 by anything."
596 This avoids the creation of multiple groups when users send to an address
597 using different case (i.e. mailing-list@domain vs Mailing-List@Domain)."
602 ;;; Internal variables.
612 ;; support the %-hack
614 table)
624 \f
633 mm-text-coding-system
637 ;; This causes Emacs 22.2 and 22.3 to issue a useless warning.
638 ;;(if (and (featurep 'xemacs) (featurep 'file-coding))
641 ;; Work around a bug in many XEmacs 21.5 betas.
642 ;; Cf. http://thread.gmane.org/gmane.emacs.gnus.general/68134
647 "Insert FILE in server buffer safely."
657 t)
661 "Make file name for GROUP."
666 ?. ?_))
668 ;; If this directory exists, we use it directly.
673 ;; If not, we translate dots into slashes.
676 dir))))
680 "Returns an assoc of group names and active ranges.
681 nn*-request-list should have been called before calling this function."
682 ;; Go through all groups from the active list.
687 "Parse the active file in the current buffer and return an alist."
695 group-assoc group max min)
706 group-assoc)))
710 group-assoc))
716 "Save GROUP-ASSOC in ACTIVE-FILE."
724 "Generate an active file from group-alist ALIST."
735 "Find out whether this FILE is to be split into GROUP only.
736 If SOURCE is a directory spec, try to return the group name component."
742 nil)))
743 nil))
748 start message-id content-length do-search end)
758 ;; Skip all the headers in case there are more "From "s...
763 ;; Unquote the ">From " line, if any.
769 ;; Find the Message-ID header.
775 ;; There is no Message-ID here, so we create one.
783 ;; Look for a Content-Length header.
791 ;; We destroy the header, since none of
792 ;; the backends ever use it, and we do not
793 ;; want to confuse other mailers by having
794 ;; a (possibly) faulty header.
807 ;; Go to the beginning of the next article - or to the end
808 ;; of the buffer.
822 count))
825 "Put point at the beginning of the next Unix mbox message."
826 ;; Algorithm used to find the next article in the
827 ;; brain-dead Unix mbox format:
828 ;;
829 ;; 1) Search for "^From ".
830 ;; 2) If we find it, then see whether the previous
831 ;; line is blank and the next line looks like a header.
832 ;; Then it's possible that this is a mail delim, and we use it.
834 found)
854 "Put point at the beginning of the current Unix mbox message."
855 ;; Algorithm used to find the next article in the
856 ;; brain-dead Unix mbox format:
857 ;;
858 ;; 1) Search for "^From ".
859 ;; 2) If we find it, then see whether the previous
860 ;; line is blank and the next line looks like a header.
861 ;; Then it's possible that this is a mail delim, and we use it.
863 found)
885 start message-id content-length end skip head-end)
889 ;; Possibly wrong format?
893 ;; Carry on until the bitter end.
896 end nil)
897 ;; Find the end of the head.
899 start
902 ;; This will never happen, but just to be on the safe side --
903 ;; if there is no head-body delimiter, we search a bit manually.
908 ;; Find the Message-ID header.
916 ;; There is no Message-ID here, so we create one.
919 ;; Look for a Content-Length header.
925 ;; We destroy the header, since none of the backends ever
926 ;; use it, and we do not want to confuse other mailers by
927 ;; having a (possibly) faulty header.
931 ;; Find the end of this article.
935 ;; We try the Content-Length value. The idea: skip over the header
936 ;; separator, then check what happens content-length bytes into the
937 ;; message body. This should be either the end of the buffer, the
938 ;; message separator or a blank line followed by the separator.
939 ;; The blank line should probably be deleted. If neither of the
940 ;; three is met, the content-length header is probably invalid.
955 ;; No Content-Length, so we find the beginning of the next
956 ;; article or the end of the buffer.
960 ;; Allow the backend to save the article.
969 count))
975 start message-id end)
979 ;; Possibly wrong format?
981 ;; Carry on until the bitter end.
984 ;; Find the end of the head.
986 start
989 ;; This will never happen, but just to be on the safe side --
990 ;; if there is no head-body delimiter, we search a bit manually.
995 ;; Find the Message-ID header.
999 ;; There is no Message-ID here, so we create one.
1007 ;; Find the end of this article.
1013 ;; Allow the backend to save the article.
1023 count))
1026 ;; In a maildir, every file contains exactly one mail.
1028 message-id)
1030 ;; Find the end of the head.
1035 ;; This will never happen, but just to be on the safe side --
1036 ;; if there is no head-body delimiter, we search a bit manually.
1041 ;; Find the Message-ID header.
1045 ;; There is no Message-ID here, so we create one.
1053 ;; Allow the backend to save the article.
1064 group artnum-func junk-func)
1065 "Go through the entire INCOMING file and pick out each individual mail.
1066 FUNC will be called with the buffer narrowed to each mail.
1067 INCOMING can also be a buffer object. In that case, the mail
1068 will be copied over from that buffer."
1070 ;; methods to just this group.
1074 nnmail-split-methods))
1076 ;; Insert the incoming file.
1085 0
1088 ;; Handle both babyl, MMDF and unix mail formats, since
1089 ;; movemail will use the former when fetching from a
1090 ;; mailbox, the latter when fetching from a file.
1096 func artnum-func junk-func))
1106 "Look at the headers and return an alist of groups that match.
1107 FUNC will be called with the group name to determine the article number."
1110 group-art method grp)
1114 ;; If there is only just one group to put everything in, we
1115 ;; just return a list with just this one method in.
1118 ;; We do actual comparison.
1119 ;; Copy the article into the work buffer.
1123 ;; Narrow to headers.
1130 ;; Decode MIME headers and charsets.
1134 ;; Fold continuation lines.
1138 ;; Nuke pathologically long headers. Since Gnus applies
1139 ;; pathologically complex regexps to the buffer, lines
1140 ;; that are looong will take longer than the Universe's
1141 ;; existence to process.
1145 nnmail-split-header-length-limit)
1148 ;; Allow washing.
1157 ;; Not a regular split method, so it has to be a
1158 ;; fancy one.
1166 nnmail-split-methods
1170 ;; `nnmail-split-methods' is a function, so we
1171 ;; just call this function here and use the
1172 ;; result.
1182 ;; The article may be "cross-posted" to `junk'. What
1183 ;; to do? Just remove the `junk' spec. Don't really
1184 ;; see anything else to do...
1186 junk-func)
1193 split))))
1194 ;; Go through the split methods to find a match.
1208 nil t)))
1211 pos)
1212 ;; Function to say whether this is a match.
1214 ;; Don't enter the article into the same
1215 ;; group twice.
1218 group-art))
1219 ;; This is the final group, which is used as a
1220 ;; catch-all.
1227 ;; Fall back on "bogus" if all else fails.
1231 ;; Produce a trace if non-empty.
1243 ;; See whether the split methods returned `junk'.
1245 nil
1246 ;; The article may be "cross-posted" to `junk'. What
1247 ;; to do? Just remove the `junk' spec. Don't really
1248 ;; see anything else to do...
1255 "Insert how many lines there are in the body of the mail.
1256 Return the number of characters in the body."
1271 chars)))
1274 "Insert an Xref line based on the (group . article) alist."
1294 ;;; Message washing functions
1297 "Remove excessive whitespace from all headers."
1303 "Remove list identifiers from Subject headers."
1307 nnmail-list-identifiers)))
1312 nil t)
1316 nil t)
1321 "Translate TAB characters into SPACE characters."
1326 "Header line matching mailer producing bogus References lines.
1327 See `nnmail-ignore-broken-references'."
1333 "Ignore the References line and use In-Reply-To
1335 Eudora has a broken References line, but an OK In-Reply-To."
1352 ;;; Utility functions
1358 "Utility function to directly post a message to an nnmail-derived group.
1359 Calls ACCEPT-FUNC (which should be `nnchoke-request-accept-article')
1360 to actually put the message in the right group."
1369 to-newsgroup))
1371 to-newsgroup gnus-command-method)
1373 gnus-command-method))
1380 "Fancy splitting method.
1381 See the documentation for the variable `nnmail-split-fancy' for details."
1386 ;; Alist of split expressions their equivalent regexps.
1389 ;; Return a list of groups matching SPLIT.
1392 ;; nil split
1394 nil)
1396 ;; A group name. Do the \& and \N subs into the string.
1402 ;; Junk the message.
1408 ;; Builtin & operation.
1412 ;; Builtin | operation.
1418 done))
1420 ;; Builtin : operation.
1426 ;; Builtin ! operation.
1430 ;; Check the cache for the regexp for this split.
1443 ;; The searched regexp is \(\(FIELD\).*\)\(VALUE\).
1444 ;; So, start-of-value is the point just before the
1445 ;; beginning of the value, whereas after-header-name
1446 ;; is the point just after the field name.
1449 ;; Start the next search just before the beginning of the
1450 ;; VALUE match.
1452 ;; Handle - RESTRICTs
1454 ;; RESTRICT must start after-header-name and
1455 ;; end after start-of-value, so that, for
1456 ;; (any "foo" - "x-foo" "foo.list")
1457 ;; we do not exclude foo.list just because
1458 ;; the header is: ``To: x-foo, foo''
1461 after-header-name t)
1470 ;; Someone might want to do a \N sub on this match, so get the
1471 ;; correct match positions.
1476 split-result))
1478 ;; Not in cache, compute a regexp for the field/value pair.
1483 partial-front
1484 partial-rear
1485 regexp)
1492 ;; Same trick for the rear of the regexp
1497 ;; Invert the match-partial-words behavior if the optional
1498 ;; last element is specified.
1503 nnmail-split-fancy-match-partial-words)
1509 field)
1513 value
1517 ;; Now that it's in the cache, just call nnmail-split-it again
1518 ;; on the same split, which will find it immediately in the cache.
1524 c expanded beg N did-expand)
1533 ;; We hit a \; expand it.
1540 ;; \ followed by some character we don't expand.
1542 ;; \& or \N
1551 expanded))))
1555 newtext)))
1557 ;; Activate a backend only if it isn't already activated.
1558 ;; If FORCE, re-read the active file even if the backend is
1559 ;; already activated.
1564 force
1567 backend)))))
1574 backend)))
1584 file-time))
1586 t))
1591 ;;;
1592 ;;; nnmail duplicate handling
1593 ;;;
1613 nnmail-treat-duplicates
1617 ;; Weed out the excess number of Message-IDs.
1623 ;; Save the buffer.
1626 t))
1635 ;; this will handle cases like `B r' where the group is nil
1638 id grp subject sender))
1640 ;; Store some information about the group this message is written
1641 ;; to. This is passed in as the grp argument -- all locations this
1642 ;; has been called from have been checked and the group is available.
1643 ;; The only ambiguous case is nnmail-check-duplication which will only
1644 ;; pass the first (of possibly >1) group which matches. -Josh
1655 nnmail-cache-ignore-groups)))
1674 res))
1676 ;; Fetch the group name corresponding to the message id stored in the
1677 ;; cache.
1689 ;; Function for nnmail-split-fancy: look up all references in the
1690 ;; cache and if a match is found, return that group.
1692 "Split this message into the same group as its parent.
1693 This function can be used as an entry in `nnmail-split-fancy', for
1694 example like this: (: nnmail-split-fancy-with-parent)
1695 For a message to be split, it looks for the parent message in the
1696 References or In-Reply-To header and then looks in the message id
1697 cache file (given by the variable `nnmail-message-id-cache-file') to
1698 see which group that message was put in. This group is returned.
1700 See the Info node `(gnus)Fancy Mail Splitting' for more details."
1708 nnmail-split-fancy-with-parent-ignore-groups
1710 nnmail-split-fancy-with-parent-ignore-groups)))
1720 res)))
1737 ;; If this is a duplicate message, then we do not save it.
1743 nnmail-treat-duplicates)
1747 nnmail-treat-duplicates))))
1748 group-art)
1749 ;; We insert a line that says what the mail source is.
1756 ;; Let the backend save the article (or not).
1761 artnum-func nil junk-func))))
1766 ;; We insert a warning.
1778 ;; Add the group-art list to the history list.
1783 ;;; Get new mail.
1794 "Read new incoming mail."
1798 group in-group spool-func)
1800 fetching-sources
1804 source)
1806 sources)
1808 ;; Use group's parameter
1816 group group spool-func))
1818 ;; Hack to only fetch the contents of a single group's spool file.
1821 group)
1825 :predicate
1837 ;; We first activate all the groups.
1839 ;; Allow the user to hook.
1841 ;; Open the message-id cache.
1843 ;; The we go through all the existing mail source specification
1844 ;; and fetch the mail from each.
1849 source
1854 ',spool-func
1857 nil
1866 ;; If we did indeed read any incoming spools, we save all info.
1878 total))
1879 ;; Close the message-id cache.
1881 ;; Allow the user to hook.
1885 "Say whether an article that is TIME old in GROUP should be expired.
1886 If TIME is nil, then return the cutoff time for oldness instead."
1890 t)
1893 nnmail-expiry-wait)))
1896 inhibit))
1897 ;; This isn't an expirable group.
1898 nil)
1900 ;; We expire all articles on sight.
1903 t))
1905 ;; This is an ange-ftp group, and we don't have any dates.
1906 nil)
1909 ;; Compare the time with the current time.
1917 ;; Do not invoke this from nntp-server-buffer! At least nnfolder clears
1918 ;; that buffer if the nnfolder group isn't selected.
1920 ;; Don't enter Message-IDs into cache.
1921 ;; Let users hack it in TARGET function.
1933 "Returns a target expiry group determined by `nnmail-fancy-expiry-targets'."
1950 ;; If the header is to-from then match against the
1951 ;; To or From header
1958 mail-dont-reply-to-names))
1972 "Check (and modify) the syntax of the message in the current buffer."
1980 "Do a `write-region', and then set the file modes."
1986 ;;;
1987 ;;; Status functions
1988 ;;;
1991 "Make status NAME and VALUE part of the current status line."
2003 "Return a status-value alist from STATUS."
2008 ;; Narrow to the status.
2014 ;; Go through all elements and add them to the list.
2019 ;; Implied "yes".
2024 ;; Implied "no".
2026 ;; Unquoted value.
2029 ;; Quoted value.
2032 status)))
2035 "Return a status string from STATUS."
2046 "Generate an overview of where the last mail split put articles."
2056 elem
2061 "Remove all instances of GROUP from `nnmail-split-history'."
2070 "Say whether GROUP has new mail."
2072 found)
2076 his nil)))
2077 found))
2080 "Check to see if point is within the headers of a unix mail message.
2081 Doesn't change point."
2091 ;;; nnmail.el ends here