From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: CRM114 Mailfilter and spam.el
Date: Fri, 02 Apr 2004 12:06:04 -0500 [thread overview]
Message-ID: <4n65ci5myr.fsf@lifelogs.com> (raw)
In-Reply-To: <87isgjpggh.fsf@virgil.koldfront.dk> (Adam =?iso-8859-1?q?Sj=F8gren's?= message of "Thu, 01 Apr 2004 22:54:06 +0200")
On Thu, 01 Apr 2004, asjo@koldfront.dk wrote:
> So, I've begun to take a stab at switcing from spam-stat.el to
> CRM114 Mailfilter and spam.el.
Great! Just so you know, I plan to add a better way to add backends
to spam.el; something like (spam-add-statistical-backend) for
instance. It's not going to be ready for a while, but it's been on
my mind.
> Now I just need to figure out how to configure spam.el to call
> mailfilter.crm --learnspam/--learnnonspam at the *appropriate*
> moments only.
Yes, this is very important and I've been trying to get the
gnus-registry to cooperate with spam.el on this.
> * Email comes in, and is split with spam-split. Spam goes into
> "nnml:spam", ham goes through my usual, other splitrules (bbdb
> and stuff).
OK.
> * If a spam is misclassified as ham, I would like to mark that
> message in some way, so that it is moved to nnml:spam and
> mailfilter.crm is called with --learnspam on it.
Set the spam-mark on the message. When you exit the group, the spam
message will be moved to the group named by spam-process-destination
(multiples are OK). Also, the exit spam processor will be invoked on
the spam message - so set your exit spam processor to crm114.
> * If a ham is misclassified as spam, and therefore is split into
> nnml:spam, I would like to move it to the correct group and have
> mailfilter.crm called on it with --learnnonspam.
Set a ham-mark (usually the tick mark) on the message. The ham
message, when you quit the group, will be moved to the
ham-process-destination (which can be multiple groups) and processed
with the ham exit processor.
If you set spam-mark-ham-unread-before-move-from-spam-group, the ham
will also be marked unread before it's moved out of the spam group.
> * I would like spam.el *never* to mark *any* message as expirable.
This is hardcoded right now in
spam-mark-spam-as-expired-and-move-routine:
(gnus-summary-mark-article article gnus-expirable-mark)
but it could be changed. Why would you NOT want to expire spam?
Ted
next prev parent reply other threads:[~2004-04-02 17:06 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 20:54 Adam Sjøgren
2004-04-02 6:22 ` Kai Grossjohann
2004-04-02 16:04 ` Adam Sjøgren
2004-04-03 13:28 ` Kai Grossjohann
2004-04-03 14:01 ` Adam Sjøgren
2004-04-05 13:21 ` Ted Zlatanov
2004-04-02 16:06 ` Adam Sjøgren
2004-04-02 17:14 ` Ted Zlatanov
2004-04-03 21:10 ` Adam Sjøgren
2004-04-03 21:19 ` Adam Sjøgren
2004-04-03 21:48 ` Adam Sjøgren
2004-04-03 21:58 ` Adam Sjøgren
2004-04-03 13:29 ` Kai Grossjohann
2004-04-03 13:49 ` Adam Sjøgren
2004-04-06 8:12 ` Kai Grossjohann
2004-04-06 21:40 ` Adam Sjøgren
2004-04-02 16:10 ` Jody Klymak
2004-04-02 17:07 ` Ted Zlatanov
2004-04-02 17:06 ` Ted Zlatanov [this message]
2004-04-02 17:26 ` Adam Sjøgren
2004-04-02 17:44 ` Ted Zlatanov
2004-04-03 14:22 ` Adam Sjøgren
2004-04-03 14:24 ` Adam Sjøgren
2004-04-03 23:59 ` Adam Sjøgren
2004-04-04 1:59 ` Jesper Harder
2004-04-04 13:07 ` Adam Sjøgren
2004-04-05 13:24 ` Ted Zlatanov
2004-04-05 15:50 ` Jesper Harder
2004-04-06 21:36 ` Adam Sjøgren
2004-05-20 18:39 ` Ted Zlatanov
2004-05-20 19:19 ` Adam Sjøgren
2004-05-22 23:44 ` Lars Magne Ingebrigtsen
2004-05-23 13:44 ` Adam Sjøgren
2004-05-26 16:23 ` Ted Zlatanov
2004-05-26 20:30 ` Adam Sjøgren
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=4n65ci5myr.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).