From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Backend specific spam filtering
Date: Thu, 21 Nov 2002 22:13:52 -0500 [thread overview]
Message-ID: <m3n0o2qosv.fsf@heechee.beld.net> (raw)
In-Reply-To: <84of8ihcln.fsf@lucy.cs.uni-dortmund.de> (kai.grossjohann@uni-duisburg.de's message of "Thu, 21 Nov 2002 21:49:56 +0100")
On Thu, 21 Nov 2002, kai.grossjohann@uni-duisburg.de wrote:
> Maybe regexes aren't necessary anymore now that we have the variable
> gnus-parameters. What do people think?
I'm all for using gnus-parameters. Can anyone suggest additions or
improvements to the list below, especially variable names? All the
parameters would be t or nil, except for to-group-processed-spam and
group-is-spam.
(note that ham == non-spam in spam.el lingo)
- group-is-spam: whether this group holds only spam (parallels
spam-junk-mailgroups, all unread messages get marked as spam on
summary entry, nil by default, can be t for a spam group or 'none
for an explicit ham group)
Setting group-is-spam to 'none is useful for whitelist and BBDB
seeding, see below. We thus explicitly say that the group contains
only ham.
Entering a group with group-is-spam set to t automatically gives all
unread messages the spam mark.
- to-group-processed-spam: whether spam articles from this group
should be moved to another group, marked as read, after being
processed (this would be a string value, nil, or 'expire to expire
processed articles, nil by default)
- spam-process-with-ifile: whether ifile should be used to process
spam articles on summary exit (nil by default)
- spam-process-with-bofogilter: whether bogofilter should be used to
process spam articles on summary exit (t by default, but note that
spam-process is nil by default, so this wouldn't be activated)
- spam-process-to-blacklist: whether the blacklist should be filled
with spam message senders on summary exit, instead of when the
message is marked as spam (nil by default)
- spam-process-ham-to-whitelist: whether the whitelist should be filled with ham message senders on
summary exit if this is a ham group with group-is-spam set to 'none
(nil by default)
- spam-process-ham-to-BBDB: whether the BBDB should be filled with ham
message senders on summary exit if this is a ham group with
group-is-spam set to 'none (nil by default)
- spam-process: whether spam will be processed at summary exit (nil by
default)
Maybe I should give a little pseudo-algorithm :) See below.
Ted
---------------------------------------------------------------------
At summary entry:
if (group-is-spam is t)
set the spam mark on all unread articles
endif
At summary exit:
if (spam-process is t)
if (group-is-spam is t or nil)
check and do spam-process-with-ifile on spam-marked articles
check and do spam-process-with-bogofilter on spam-marked articles
check and do spam-process-to-blacklist on spam-marked articles
elsif (group-is-spam is 'none)
check and do spam-process-ham-to-whitelist on unread articles
check and do spam-process-ham-to-BBDB on unread articles
endif
endif
if (to-group-processed-spam is a string)
set article mark to read on spam-marked articles
move spam-marked articles to to-group-processed-spam
elsif (to-group-processed-spam is 'expire)
set article mark to expired on spam-marked articles
endif
prev parent reply other threads:[~2002-11-22 3:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-19 13:21 Piers Cawley
2002-11-21 15:28 ` Ted Zlatanov
2002-11-21 20:49 ` Kai Großjohann
2002-11-22 3:13 ` Ted Zlatanov [this message]
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=m3n0o2qosv.fsf@heechee.beld.net \
--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).