Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Problems with spam filtering and bogofilter.
Date: Fri, 10 Jan 2003 07:56:04 -0500	[thread overview]
Message-ID: <m3vg0xgo4b.fsf@heechee.beld.net> (raw)
In-Reply-To: <m3hechb2wz.fsf@c18072.rivrw2.nsw.optusnet.com.au> (Malcolm Purvis's message of "Fri, 10 Jan 2003 23:33:00 +1100")

On Fri, 10 Jan 2003, malcolmpurvis@optushome.com.au wrote:
> All this discussion about spam filtering has made me try spam.el, in
> my case with bogofilter and POP.
> 
> However, if I add (: spam-split) to the start of nnmail-split-fancy,
> errors are produced during the split and all my mail gets sent to
> the bogus group.
> 
> I am using a fresh version of gnus and the latest version of
> bogofilter from SourceForce (0.9.1.2).  I see that spam.el's
> documentation refers to version 0.4 so perhaps there is come
> incompatibility?  In particular, the output of bogosort -v is:
> 
>          X-Bogosity: No, tests=bogofilter, spamicity=0.355906,
>          version=0.9.1.2
> 
> while spam-check-bogofilter is searching for 
> 
> 	    (re-search-forward "Spamicity: \\(0\\.9\\|1\\.0\\)" nil t)
> 
> This is all running under XEmacs 21.4.11 on PPC Linux.

Yes, you need 0.4 currently.  The bogofilter functionality is older
than the more modular implementation I did for ifile and spam-stat, so
it's a little more outdated.  The question is, should I expend the
effort to keep up with bogofilter?  Can you check to see if 0.9.1.2
has the same flags as 0.4?  If so, and all I need to fix is the regex,
no big deal, but if the interface has changed then maybe I need to
rewrite the bogofilter section of spam.el anyway.

This will have to wait until Monday so I hope you don't have urgent
spam meanwhile :)

Ted




  reply	other threads:[~2003-01-10 12:56 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-10 12:33 Malcolm Purvis
2003-01-10 12:56 ` Ted Zlatanov [this message]
2003-01-10 17:24   ` Raja R Harinath
2003-01-13 19:17     ` Ted Zlatanov
2003-01-15 19:31     ` Ted Zlatanov
2003-01-15 21:17       ` Raja R Harinath
2003-01-16  0:11         ` new Bogofilter functionality (was: Problems with spam filtering and bogofilter.) Ted Zlatanov
2003-01-16 11:00           ` new Bogofilter functionality Malcolm Purvis
2003-01-16 11:55             ` Ted Zlatanov
2003-01-11 12:17   ` Problems with spam filtering and bogofilter Malcolm Purvis
2003-01-13 19:16     ` Ted Zlatanov
2003-01-13 21:24       ` requesting articles from a nnxyz backend: what's the fastest Ted Zlatanov
2003-01-14  7:22         ` Kai Großjohann
2003-01-14 16:42           ` Ted Zlatanov
2003-01-14 20:39             ` Kai Großjohann
2003-01-15 17:27               ` Ted Zlatanov
2003-01-16 11:56                 ` Kai Großjohann
2003-01-16 12:30                   ` Ted Zlatanov
2003-01-16 12:48                     ` Kai Großjohann
2003-01-16 13:51                       ` Ted Zlatanov
2003-01-14 18:16         ` Lars Magne Ingebrigtsen
2003-01-14 20:42           ` Kai Großjohann
2003-01-15 19:21           ` Ted Zlatanov
2003-01-15 20:10             ` Lars Magne Ingebrigtsen
2003-01-15 22:14               ` Ted Zlatanov
2003-01-17 17:46             ` Paul Jarc

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=m3vg0xgo4b.fsf@heechee.beld.net \
    --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).