From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: filtering nntp messages
Date: Fri, 23 Oct 2009 17:55:17 -0500 [thread overview]
Message-ID: <87skd9en56.fsf@lifelogs.com> (raw)
In-Reply-To: <874oppivvc.fsf@topper.koldfront.dk>
On Sat, 24 Oct 2009 00:33:11 +0200 asjo@koldfront.dk (Adam Sjøgren) wrote:
AS> On Fri, 23 Oct 2009 12:06:56 -0500, Harry wrote:
>> Some nntp groups I like to frequent like comp.unix.shell have been
>> nearly destroyed by spam. I'm guessing gnus is capable of filtering
>> all that mess... but a few cursory tries at the manual have come up
>> dry.
AS> Uhm, look a scoring?
You can filter nntp with spam.el, same as any other message source. You
just can't move spam articles out of a group, but you can copy them to
another backend or feed directly into the spam.el backends for spam
training.
Statistical spam backends will require fetching every message body,
though, which could be painful. Unfortunately that's the best solution
nowadays. You may want to look into integrating some anti-spam solution
with leafnode on arrival or something like it (I don't know if it's
possible!). Then you can just score on headers, with spam.el or not.
Ted
next prev parent reply other threads:[~2009-10-23 22:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 17:06 Harry Putnam
2009-10-23 22:33 ` Adam Sjøgren
2009-10-23 22:55 ` Ted Zlatanov [this message]
2009-10-24 1:51 ` Harry Putnam
2009-10-24 2:12 ` Harry Putnam
2009-10-24 11:20 ` Adam Sjøgren
2009-10-24 16:22 ` Harry Putnam
2009-10-24 16:48 ` Adam Sjøgren
2009-10-24 19:45 ` Harry Putnam
2009-10-24 5:04 ` Ted Zlatanov
2009-10-24 10:13 ` Steinar Bang
2009-10-24 15:10 ` Harry Putnam
2009-10-24 16:38 ` Adam Sjøgren
2009-10-24 19:55 ` Harry Putnam
2009-10-24 20:12 ` Adam Sjøgren
2009-10-24 22:07 ` Harry Putnam
2009-10-24 22:59 ` Harry Putnam
2009-10-24 22:05 ` Steinar Bang
2009-10-24 22:09 ` Steinar Bang
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=87skd9en56.fsf@lifelogs.com \
--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).