From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: spam-split with bogofilter
Date: Thu, 20 Mar 2003 16:28:33 -0500 [thread overview]
Message-ID: <4nznnp918e.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <shbs05amjl.fsf@tux.gnu.franken.de> (Karl Eichwalder's message of "Thu, 20 Mar 2003 20:02:54 +0100")
On Thu, 20 Mar 2003, keichwa@gmx.net wrote:
> My next project is to make use of spam.el and bogofilter (version
> 0.10.3.1); in *Messages* I can already see the good will of involved
> tools:
>
> And I can mark spam with M-d and when I leave a mail group with spam
> marked mails, the mails will we move to the spam group. Now I want
> spam.el/bogofilter to jump in earlier -- how can I make them storing
> incoming spam mail straight away in a special spam group? I'm using
> these settings:
[...]
> Must I call bogofilter via .procmailrc?
No, spam-use-bogofilter calls bogofilter for you (although for local
mail, spam-use-bogofilter-headers is also OK if you pre-process with
Bogofilter in the .procmailrc).
Your rules are OK. The spam should be going to "nnml:spambox". Does
a message get misclassified? Go to the message's buffer and do t M-:
(spam-split) (note that the 't' command is to show the full message in
the buffer). Does that return the value of spam-split-group? Also
try saving the message in a file and run bogofilter on it, to see if
it thinks the message is spam.
Also, this is obvious, but make sure that spam-bogofilter-path is
correct. It should be automatically set to (find-executable "bogofilter").
Finally, note that (unfortunately) ham will be registered with
Bogofilter multiple times, I'll fix that when I get the registry
working.
Let me know if you need more help
Ted
next prev parent reply other threads:[~2003-03-20 21:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 19:02 Karl Eichwalder
2003-03-20 21:28 ` Ted Zlatanov [this message]
2003-03-21 6:23 ` Karl Eichwalder
2003-03-21 8:13 ` Stefan Reichör
2003-03-21 17:25 ` Karl Eichwalder
2003-03-21 18:49 ` Ted Zlatanov
2003-03-21 19:28 ` Karl Eichwalder
2003-03-21 20:35 ` Ted Zlatanov
2003-03-22 18:40 ` Karl Eichwalder
2003-03-23 23:08 ` Ted Zlatanov
2003-03-21 18:44 ` Ted Zlatanov
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=4nznnp918e.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).