From: David Z Maze <dmaze@MIT.EDU>
Cc: ding@gnus.org
Subject: Re: Spam/Ham training
Date: Tue, 02 Dec 2003 13:55:09 -0500 [thread overview]
Message-ID: <87d6b7oxrm.fsf@everett.mit.edu> (raw)
In-Reply-To: <4nhe0kfdt0.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Mon, 01 Dec 2003 16:06:35 -0500")
[-- Attachment #1: Type: text/plain, Size: 367 bytes --]
Ted Zlatanov <tzz@lifelogs.com> writes:
> I am considering adding spam *recognition* when you enter a group,
> which would be useful for NNTP groups which have no splitting.
> Unseen articles would be checked against a blacklist, for instance.
Oh, I already have code to do that; I don't use it for nntp, but I do
use it for another [MIT-local] read-only backend.
[-- Attachment #2: Type: application/emacs-lisp, Size: 567 bytes --]
[-- Attachment #3: Type: text/plain, Size: 415 bytes --]
...so the core of this, in dzm-gnus-find-spam, downloads each article
in turn into a temporary buffer, calls spam-split, and sees if the
result is spam-split-group; if so, it marks the message as spam. This
seems to work pretty well in practice.
--
David Maze dmaze@mit.edu http://www.mit.edu/~dmaze/
"Theoretical politics is interesting. Politicking should be illegal."
-- Abra Mitchell
next prev parent reply other threads:[~2003-12-02 18:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-30 20:18 Xavier Maillard
2003-12-01 20:33 ` Kai Grossjohann
2003-12-01 22:52 ` Xavier Maillard
2003-12-01 21:06 ` Ted Zlatanov
2003-12-01 22:53 ` Xavier Maillard
2003-12-02 1:45 ` Ted Zlatanov
2003-12-02 6:29 ` Xavier Maillard
2003-12-02 22:24 ` Ted Zlatanov
2003-12-02 23:56 ` Xavier Maillard
2003-12-03 17:36 ` Ted Zlatanov
2003-12-02 18:55 ` David Z Maze [this message]
2003-12-02 23:57 ` Xavier Maillard
2003-12-10 23:05 ` spam autodetection in NNTP and other backends (was: Spam/Ham training) 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=87d6b7oxrm.fsf@everett.mit.edu \
--to=dmaze@mit.edu \
--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).