Gnus development mailing list
 help / color / mirror / Atom feed
From: (Chris Beggy ) news@kippona.com
Subject: Re: Paul Graham on fighting SPAM
Date: Tue, 20 Aug 2002 21:14:26 -0400	[thread overview]
Message-ID: <87ptwdxbbh.fsf@lackawana.kippona.com> (raw)
In-Reply-To: <vafsn1b8c21.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> prj@po.cwru.edu (Paul Jarc) writes:
>
>> Sounds like it.  Anyone know if this (or another) method generalizes
>> to more than two categories (spam/nonspam)?  If so, it could be used
>> for all mail splitting.  We wouldn't have to manually craft split
>> rules; we'd just seed a new group with the mails we have so far that
>> belong there, and their contents would let the computer guess which
>> new mails belong with them.
>
> I think you can assume that text classifiers can choose one out of N
> categories.  In some cases, this is implemented by having N yes/no
> classifiers and choosing the result from the one with the highest
> confidence value, but this is only an implementation detail.
>
> Using automatic classification for splitting would really be way
> cool.  Are there any mail readers which do this?

Mew does this with its mew-refile-guess-* functions, lists, and
variables.  It's not strictly automatic, but remembers and learns
from previous refiles (splitting, in gnusspeak.)

Chris



  reply	other threads:[~2002-08-21  1:14 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-16 17:10 Danny Siu
2002-08-17 19:43 ` Kai Großjohann
2002-08-19  5:44   ` Paul Jarc
2002-08-19  8:53     ` Kai Großjohann
2002-08-21  1:14       ` news [this message]
2002-08-27 23:03         ` Nathan J. Williams
2002-08-19 10:50     ` Oliver Scholz
2002-08-19 11:06       ` Kai Großjohann
2002-08-19 14:55         ` Alex Schroeder
2002-08-19 17:09           ` Kai Großjohann
2002-08-19 14:12     ` Email filing Scott A Crosby
2002-09-05 16:00       ` clemens fischer
2002-12-29 22:35         ` Lars Magne Ingebrigtsen
2002-08-19  9:23 ` Paul Graham on fighting SPAM Alex Schroeder
2002-08-19 11:29   ` Ted Zlatanov
2002-08-19 15:09     ` Alex Schroeder
2002-08-19 16:23       ` Ted Zlatanov
2002-08-19 22:22         ` Alex Schroeder
2002-08-20  7:42           ` Alex Schroeder
2002-08-20 12:00             ` Ted Zlatanov
2002-08-22  2:21               ` Alex Schroeder
2002-08-22 16:32                 ` Ted Zlatanov
2002-08-22 16:57                   ` Ted Zlatanov
2002-08-22 17:57                     ` Kai Großjohann
2002-08-22 18:42                       ` Ted Zlatanov
2002-08-22 19:59                       ` Alex Schroeder
2002-08-22 20:07                     ` Alex Schroeder
2002-08-22 20:54                       ` Ted Zlatanov
2002-08-26 21:55               ` Alex Schroeder
2002-08-26 23:19                 ` Alex Schroeder
2002-08-28  6:40                 ` Piers Cawley
2002-08-28 18:44                   ` Alex Schroeder
2002-08-29  2:46                 ` Ted Zlatanov
2002-08-19 17:09       ` Kai Großjohann
2002-08-19 22:19         ` Alex Schroeder

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=87ptwdxbbh.fsf@lackawana.kippona.com \
    --to=news@kippona.com \
    --cc=chrisb@kippona.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).