From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: How many people mark spam in gmane groups?
Date: Wed, 16 Apr 2003 12:33:39 -0400 [thread overview]
Message-ID: <4n4r4y1jx8.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <4n4r5aowwm.fsf@chubby.bwh.harvard.edu> (Ted Zlatanov's message of "Mon, 07 Apr 2003 16:49:45 -0400")
On Mon, 07 Apr 2003, tzz@lifelogs.com wrote:
> - add a group parameter (global through a regex or specific for that
> group) for the spam-processor. The spam-processor takes whatever
> messages are marked as spam at summary exit and does something to
> them (for instance, train Bogofilter).
>
> - mark messages as spam in that group
>
> - exit the group - the spam-processor will be automatically invoked
>
> The first one would be done just once, of course.
This is now set up through spam-report.el and spam.el; you can use the
spam-report-gmane function in spam-report.el on its own if you wish or
you can add the gnus-group-spam-exit-processor-report-gmane processor
to the exit spam processors of your Gmane groups. The Gmane groups
have to be NNTP groups, I think, in order for the code to work (it
uses nntp-server-buffer). It seemed to work OK for me; I looked at
the network traffic and saw the acknowledgment from gmane.org arriving
for each reported article, so I'm pretty sure it reports the spam
properly.
There are variables you can customize in spam-report.el, for instance
reporting can be done through the fast inference of the X-Report-Spam
URL from the article number (default), or through the slower parsing
of the article itself for those whose article numbers don't correspond
to the Gmane article numbers.
It should be very easy to add more spam reporters to spam-report.el,
and I can glue them into spam.el as we go. I don't know much about
spam reporters, but there seem to be many of them and a lot of
incidental code for using them from Gnus.
Ted
next prev parent reply other threads:[~2003-04-16 16:33 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-02 15:59 Ted Stern
2003-04-02 16:54 ` Reiner Steib
2003-04-02 20:58 ` Jon Ericson
2003-04-05 13:20 ` Ted Zlatanov
2003-04-05 23:16 ` Reiner Steib
2003-04-07 20:49 ` Ted Zlatanov
2003-04-12 15:50 ` Andreas Fuchs
2003-04-12 20:58 ` Lars Magne Ingebrigtsen
2003-04-13 10:56 ` Andreas Fuchs
2003-04-13 13:31 ` Lars Magne Ingebrigtsen
2003-04-14 19:33 ` Ted Zlatanov
2003-04-14 21:03 ` Andreas Fuchs
2003-04-14 21:05 ` Reiner Steib
2003-04-14 23:32 ` Ted Zlatanov
2003-04-15 14:24 ` Reiner Steib
2003-04-15 5:34 ` Steinar Bang
2003-04-15 14:23 ` Reiner Steib
2003-04-15 19:33 ` Ted Zlatanov
2003-04-15 21:42 ` Andreas Fuchs
2003-04-15 22:31 ` Lars Magne Ingebrigtsen
2003-04-16 6:02 ` Andreas Fuchs
2003-04-16 16:33 ` Ted Zlatanov [this message]
2003-04-26 1:40 ` Jon Ericson
2003-04-29 17:19 ` Ted Zlatanov
2003-04-29 17:48 ` Jon Ericson
2003-04-29 18:04 ` Ted Zlatanov
2003-04-29 19:48 ` Jon Ericson
2003-04-30 18:28 ` Ted Zlatanov
2003-04-30 21:37 ` Jon Ericson
2003-05-01 17:34 ` Ted Zlatanov
2003-04-26 2:49 ` Jon Ericson
2003-04-27 3:41 ` Lars Magne Ingebrigtsen
2003-04-28 18:36 ` Jon Ericson
2003-04-29 17:12 ` Ted Zlatanov
2003-04-30 18:37 ` Jon Ericson
2003-04-02 19:32 ` Raja R Harinath
2003-04-13 1:31 ` Daniel Néri
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=4n4r4y1jx8.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
/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).