From: asjo@koldfront.dk (Adam Sjøgren)
Subject: CRM114 Mailfilter and spam.el
Date: Thu, 01 Apr 2004 22:54:06 +0200 [thread overview]
Message-ID: <87isgjpggh.fsf@virgil.koldfront.dk> (raw)
Hi.
So, I've begun to take a stab at switcing from spam-stat.el to CRM114
Mailfilter and spam.el.
I followed the instructions in the documentation of spam.el about how
to add another back end ("Extending the Spam ELisp package"), basing
my additions on the bogofilter stuff, as I guess bogofilter has a
similar interface to CRM114 Mailfilter.
I think I've got the spam.el <-> CRM114 Mailfilter part working. I can
do spam-crm114-score and get the number that mailfilter.crm adds to
the header X-CRM114-Status, and splitting puts email in my spam-group
- learning spam seems to work.
Now I just need to figure out how to configure spam.el to call
mailfilter.crm --learnspam/--learnnonspam at the *appropriate* moments
only.
Boxing with adding crm114 to spam.el has made me a little, uhm, less
motivated to experiment further (I'm bad a elisp and it takes a while
to figure out _how_ to debug that for instance '--fileprefix=
blahblah' is very much different from '--fileprefix=blahblah' to
mailfilter.crm...), so here goes my question:
The documentation for CRM114 underlines heavily and repeatedly that
one should *only* train on failures. So I want to only do
mailfilter.crm --learnspam on spam that was classified as ham by
CRM114, and I want to only do mailfilter.crm --learnnonspam on ham
that was classified by CRM114. No learning in any other case.
Also, I don't really want special "training"-groups.
Ideally I'd like to just have a workflow like 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).
* 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.
* 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.
* I would like spam.el *never* to mark *any* message as expirable.
That's it. But how?
Best regards,
--
"Mr. Cotton's... parrot. Same question." Adam Sjøgren
asjo@koldfront.dk
next reply other threads:[~2004-04-01 20:54 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 20:54 Adam Sjøgren [this message]
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
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=87isgjpggh.fsf@virgil.koldfront.dk \
--to=asjo@koldfront.dk \
/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).