From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: spam-split doesn't split
Date: Tue, 09 Dec 2003 17:29:10 -0500 [thread overview]
Message-ID: <4nvfop39s9.fsf@collins.bwh.harvard.edu> (raw)
In-Reply-To: <86r7zdvp9d.fsf@oumu.wohnheimb.uni-frankfurt.de> (Adam Duck's message of "Tue, 09 Dec 2003 19:07:26 +0100")
On Tue, 09 Dec 2003, duck@informatik.uni-frankfurt.de wrote:
> Hi all,
>
> perhaps I'm a little to naïve but the info says to do this:
>
> (setq spam-use-bogofilter t)
> (require 'spam)
>
> and then bogofilter should work. That's how I read it. Now, I have
> some spam, some ham, bogofilter dbs seem ok and I get some scores
> around 1 for spam. That's good. But spam-split doesn't move them.
>
> `nnmail-split-fancy' is a variable declared in Lisp.
> -- loaded from "nnmail"
>
> Value: (:spam-split)
>
> looks OK to me but all the mails end up in the "bogus" folder.
You need to provide a fall-through, because spam-split will return
'nil' if the mail is not spam. That's the first step.
> Plus, if I M-x spam-split, nothing happens except "spam-split:
> calling the spam-check-bogofilter function".
>
> What's wrong?
Turn up gnus-verbose to 10 and see if the messages are sensible. Test
a few messages manually with Bogofilter, through the
spam-bogofilter-score function, and see if they get scored properly.
Check the other items in the spam-bogofilter configuration group,
especially that the "bogofilter" executable is correctly found.
Ted
next prev parent reply other threads:[~2003-12-09 22:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-09 18:07 Adam Duck
2003-12-09 22:29 ` Ted Zlatanov [this message]
2003-12-11 16:16 ` Adam Duck
2003-12-11 19:15 ` Ted Zlatanov
2003-12-11 23:35 ` Adam Duck
2003-12-12 18:28 ` Xavier Maillard
2003-12-12 21:56 ` Ted Zlatanov
2003-12-13 10:29 ` Adam Duck
2003-12-13 17:54 ` Xavier Maillard
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=4nvfop39s9.fsf@collins.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).