From: Karl Eichwalder <keichwa@gmx.net>
Subject: Re: spam-split with bogofilter
Date: Fri, 21 Mar 2003 07:23:11 +0100 [thread overview]
Message-ID: <shu1dx6xww.fsf@tux.gnu.franken.de> (raw)
In-Reply-To: <4nznnp918e.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Thu, 20 Mar 2003 16:28:33 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
Thanks for your help! This morning, with a sudden, it starts working.
Strange. But now it's to overzealous ;) All mail did end in the spam
box.
There is/was also an additional problem: "~/Mail/nnml:spambox" (Gnus
name: "nnml:nnml:spambox") was used instead of "~/Mail/spambox".
> 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.
Yes, now it does; for example:
$ bogofilter -v </tmp/30495
X-Bogosity: Yes, tests=bogofilter, spamicity=0.666327, version=0.10.3.1
But this was a good message -- obviously, bogofilter needs more
training...
I must reread the docs.
--
ke@suse.de (work) / keichwa@gmx.net (home): |
http://www.gnu.franken.de/ke/ | ,__o
Free Translation Project: | _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/ | (*)/'(*)
next prev parent reply other threads:[~2003-03-21 6:23 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
2003-03-21 6:23 ` Karl Eichwalder [this message]
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=shu1dx6xww.fsf@tux.gnu.franken.de \
--to=keichwa@gmx.net \
/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).