Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Spam/Ham training
Date: Tue, 02 Dec 2003 17:24:26 -0500	[thread overview]
Message-ID: <4n4qwig8o5.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <plop87ptf7ohqe.fsf@gnu-rox.org> (Xavier Maillard's message of "Tue, 02 Dec 2003 07:29:13 +0100")

On Tue, 02 Dec 2003, zedek@gnu-rox.org wrote:

> In fact that is not really entering the groups :) In fact in my
> train_spam, I am 100% there are only spams in it. So I do not need
> either enter it or exit it. I just want the SPC sequence to launch a
> training session agains my spam database when trying to enter it.

Oh, now I see, you want to do batch training without looking at the
articles.  I do it on the server, so it's never a problem for me.
There are two ways:

1) process spam when it leaves other groups on its way to train_spam
   - this is the "normal way"

2) enter train_spam, mark all articles as spam, and exit - this will
   process them all with train_spam's spam processor.  This should be
   possible to automate, if (1) is no good for you.

Ted



  reply	other threads:[~2003-12-02 22:24 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
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 [this message]
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=4n4qwig8o5.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).