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: Mon, 13 Jan 2003 14:16:10 -0500	[thread overview]
Message-ID: <4n4r8c5091.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <m38yxrop7i.fsf@c18072.rivrw2.nsw.optusnet.com.au> (Malcolm Purvis's message of "Sat, 11 Jan 2003 23:17:37 +1100")

On Sat, 11 Jan 2003, malcolmpurvis@optushome.com.au wrote:
>>>>>> "Ted" == Ted Zlatanov <tzz@lifelogs.com> writes:
> 
> Ted> Can you check to see if 0.9.1.2 has the same flags as 0.4?
> 
> Alas, I think that version 0.4 is no longer available (it's not kept
> in the SourceForge project archives as far as I can see).  However
> all the flags you pass to bogofilter are still there so it should
> work (and indeed, the group exit processing works fine).

I'm thinking of a rewrite of the bogofilter functionality into
something that looks more like the ifile functionality - cleaner,
takes articles as strings, etc.

> One question: Within spam-check-bogofilter, the message being looked
> at is refered to via gnus-summary-article-number.  Is this valid
> within the context of a fancy split?  The description of what
> environment is available to functions within a fancy split is, ahh,
> skimpy at best but since I get split errors on startup, and there is
> no summary buffer then, perhaps this is the cause?

I didn't write the bogofilter functionality, so I'm not familiar with
all the assumptions it makes.  I think the rewrite will be better in
that it will only work with the current article buffer, like all split
functions are supposed to.  It may have *other* bugs but this one will
be gone.  Hurrah for progress :)

I'll probably get around to it today or tomorrow...

Ted



  reply	other threads:[~2003-01-13 19:16 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
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 [this message]
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=4n4r8c5091.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).