Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Bogofilter
Date: Fri, 31 Jan 2003 11:46:12 -0500	[thread overview]
Message-ID: <4nznphi7xn.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <84fzrao6gn.fsf@lucy.is.informatik.uni-duisburg.de>

On Thu, 30 Jan 2003, kai.grossjohann@uni-duisburg.de wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:
> 
>> On Wed, 29 Jan 2003, org@acm.isoboroff wrote:
>>> The _right_ thing to do is something like nnir, that is, a
>>> classifier framework that you can plug anything into underneath.
>>
>> I'm sort of working on that right now, it will be a generic
>> framework for spam.el.
> 
> Ian is talking about text classification which could be used for
> general splitting (not just the spam/ham thing that spam.el does).
> 
> This doesn't mean that spam.el is bad, just that it solves a
> different problem.

> I think that the tracking part could be useful for using text
> classification for splitting.  But maybe it's enough to add the
> right hooks to Gnus, and spam.el uses them in one way whereas the
> use-a-classifier-for-splitting thing uses them in another way.

I should have said "I'm working on a generic framework, which will be
used by spam.el".  I want to make it easy to track a message as it
exists in Gnus, and spam.el will use that but other packages can too.
The idea will be to add any data you want to a message ID, and have
that data persist as the message moves around.  spam.el will attach
things like "processed as spam by bogofilter," "moved to group ABC,"
or "split by ifile into group XYZ."

Right now I'm in the "thinking about it" stage, no code yet...

Ted


  reply	other threads:[~2003-01-31 16:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <874r7vclji.fsf@ibook.optushome.com.au>
     [not found] ` <844r7vjc3l.fsf@lucy.is.informatik.uni-duisburg.de>
     [not found]   ` <81k7gq1z6a.fsf@shasta.cs.uiuc.edu>
     [not found]     ` <m2r8ayh7zm.fsf_-_@bluesteel.grierwhite.com>
2003-01-27 19:01       ` Bogofilter David Z Maze
     [not found]         ` <9cfvg09rx37.fsf@rogue.ncsl.nist.gov>
2003-01-29  7:10           ` Bogofilter Kai Großjohann
2003-01-29 19:59             ` Bogofilter Ian Soboroff
     [not found]               ` <4nlm12ehn5.fsf@lockgroove.bwh.harvard.edu>
2003-01-30 18:09                 ` Bogofilter Kai Großjohann
2003-01-31 16:46                   ` Ted Zlatanov [this message]
     [not found] ` <87ptqiodvb.fsf@unix.home>
2003-01-29 11:06   ` spam assassin filtering Alain Picard
2003-01-29 15:35     ` Michael Below
     [not found]       ` <87u1fr7lwn.fsf@jan.korger>
2003-01-29 21:14         ` Vasily Korytov
2003-01-29 21:52           ` Tim Haynes

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=4nznphi7xn.fsf@lockgroove.bwh.harvard.edu \
    --to=tzz@lifelogs.com \
    /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).