From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Spam Management When Using nnimap
Date: Tue, 20 May 2003 14:45:14 -0400 [thread overview]
Message-ID: <4nbrxxcv9h.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <871xyyu9j9.fsf@cag.lcs.mit.edu> (David Z. Maze's message of "Fri, 16 May 2003 12:43:38 -0400")
On Fri, 16 May 2003, dmaze@MIT.EDU wrote:
> Those are the various spam-use-* flags. If you wanted to add your
> own classifier, you'd need to add it to spam-list-of-checks.
I thought the manual was pretty clear about this. Maybe I need a
"starting from scratch with spam.el" section.
> The check functions appear to be called with no parameters with the
> current buffer narrowed to the headers of the article in question,
> and return t if the article is ham, spam-split-group (or another
> group name) if the article is spam, and nil for undecided.
For the statistical checks (see the recently added
spam-list-of-statistical-checks) we widen to the whole article when we
do the check.
Ted
next prev parent reply other threads:[~2003-05-20 18:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 20:10 Jake Colman
2003-05-15 21:05 ` Chris Green
2003-05-15 21:19 ` Jake Colman
2003-05-16 16:43 ` David Z Maze
2003-05-16 19:10 ` Jake Colman
2003-05-17 23:38 ` David Abrahams
2003-05-20 18:45 ` Ted Zlatanov [this message]
2003-05-20 18:41 ` Ted Zlatanov
2003-05-20 18:39 ` Ted Zlatanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4nbrxxcv9h.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).