Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Spam/Ham training
Date: Mon, 01 Dec 2003 16:06:35 -0500	[thread overview]
Message-ID: <4nhe0kfdt0.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <plop87smk5wqy7.fsf@gnu-rox.org> (Xavier Maillard's message of "Sun, 30 Nov 2003 21:18:24 +0100")

On Sun, 30 Nov 2003, zedek@gnu-rox.org wrote:

> There is maybe something missing for me. How can I tell gnus to
> train my anti-spam software (ie bogofilter) whenever I enter a list
> of group ?

You can't, currently.  You can only train when you exit a group.

I am considering adding spam *recognition* when you enter a group,
which would be useful for NNTP groups which have no splitting.
Unseen articles would be checked against a blacklist, for instance.

> I now have one dedicated group to hold spams. I want it to expire
> such a way it sends its content into another group so that I can
> train my bogofilter.

You may want to look at past traffic on the ding list and see if my
posts about training groups answer your question.  I do training for
spam/ham and it works pretty well.

Ted



  parent reply	other threads:[~2003-12-01 21:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-30 20:18 Xavier Maillard
2003-12-01 20:33 ` Kai Grossjohann
2003-12-01 22:52   ` Xavier Maillard
2003-12-01 21:06 ` Ted Zlatanov [this message]
2003-12-01 22:53   ` Xavier Maillard
2003-12-02  1:45     ` Ted Zlatanov
2003-12-02  6:29       ` Xavier Maillard
2003-12-02 22:24         ` Ted Zlatanov
2003-12-02 23:56           ` Xavier Maillard
2003-12-03 17:36             ` Ted Zlatanov
2003-12-02 18:55   ` David Z Maze
2003-12-02 23:57     ` Xavier Maillard
2003-12-10 23:05     ` spam autodetection in NNTP and other backends (was: Spam/Ham training) Ted Zlatanov

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=4nhe0kfdt0.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).