From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: How many people mark spam in gmane groups?
Date: Tue, 29 Apr 2003 13:19:15 -0400 [thread overview]
Message-ID: <4nvfwxql0s.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <87of2urq7l.fsf@jpl.nasa.gov> (Jon Ericson's message of "Fri, 25 Apr 2003 18:40:30 -0700")
On Fri, 25 Apr 2003, Jon.Ericson@jpl.nasa.gov wrote:
> Is there an easy way to set up the group properties for all of my
> Gmane groups?
Put all of them under a topic and then customize the topic properties
like you would customize a group. It works very nicely.
> I couldn't get spam-report-gmane-regex to work for some reason.[1]
> It seems like this should be a property of the server, not the
> individual groups. Or perhaps we are really looking at a new sort
> of protocol built on top of nntp. At any rate, I would prefer not
> to have to twiddle with the properties of each new Gmane group I
> add.
> But enough of my griping; this stuff is great. I might even see
> about ditching my current nnmail-split-fancy system and try the
> other bits of spam.el.
>
> Jon
>
> Footnotes: [1] Most likely I screwed up the regex. I'd rather set
> properties in any case, 'cause it seems less of a hack.
spam-report.el doesn't really do anything automatic, you have to load
spam.el for that. When you load spam.el, you can use the Gmane spam
processor for the Gmane groups (there is a list of spam processors per
group/topic/regex you can customize). Then, when you exit the group,
spam-report-gmane will be called for every article you marked as spam
in the group.
spam.el is harmless if you don't use any spam/ham processors, and
don't use spam-split in your mail splitting.
On its own, spam-report.el could be used if you manually iterate over
the list of spam articles in the gnus-newsgroup-spam-marked list at
summary exit. That's what spam.el does, it just automates things.
Thanks
Ted
next prev parent reply other threads:[~2003-04-29 17:19 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
2003-04-26 1:40 ` Jon Ericson
2003-04-29 17:19 ` Ted Zlatanov [this message]
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=4nvfwxql0s.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).