From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: spam.el: automatically resplitting ham in a spam group?
Date: Wed, 19 Nov 2003 16:24:30 -0500 [thread overview]
Message-ID: <4nu150car5.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <uoev8t6sv.fsf@coas.oregonstate.edu> (Jody Klymak's message of "Wed, 19 Nov 2003 12:57:52 -0800")
On Wed, 19 Nov 2003, jklymak@coas.oregonstate.edu wrote:
> Hello Ted,
>
> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> By the way, recently I added multiple
>> spam/ham-process-destinations. So now from a spam group, you can
>> send ham to "INBOX" and to a "train_ham" group. I find that very
>> useful for training, since "train_ham" will only contain the
>> misclassified messages. With your setup, you may like it too.
>
> What is the rationale behind this? Do you do the training on the
> mail server?
Yes.
> I train locally using bogofilter, and have found simply training on
> misclassified messages to work quite well. ie. only train on spam
> in my ham group and only on ham in my spam group. So I have been
> curious about these train_ham and train_spam groups.
Correct, for local training bogofilter is fine. I can't use it with
my ISP, though.
A change that's coming is that I'll make all the registration
functions batch-oriented - so instead of registering one message at a
time, all of them can be registered at once. That should speed things
up enormously, and it should make remote training possible (you can
save the articles in a file and send it over via ssh or whatever
mechanism you like).
Ted
next prev parent reply other threads:[~2003-11-19 21:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 15:14 Lőrentey Károly
2003-11-19 20:48 ` Ted Zlatanov
2003-11-19 20:57 ` Jody Klymak
2003-11-19 21:24 ` Ted Zlatanov [this message]
2003-11-19 21:48 ` Reiner Steib
2003-11-19 21:58 ` Jody Klymak
2003-11-20 11:17 ` Ted Zlatanov
2003-11-20 14:46 ` Jake Colman
2003-11-20 12:19 ` Lőrentey Károly
2003-11-20 12:48 ` Lőrentey Károly
2003-11-20 13:33 ` Ted Zlatanov
2003-11-20 15:48 ` Lőrentey Károly
2003-11-20 16:22 ` Ted Zlatanov
2003-11-20 18:20 ` Lőrentey Károly
2003-11-23 5:43 ` Ted Zlatanov
2003-12-09 2:02 ` Lőrentey Károly
2003-12-09 22:20 ` Ted Zlatanov
2003-12-09 22:57 ` Lőrentey Károly
2003-12-10 19:57 ` Ted Zlatanov
2003-11-20 13:28 ` Ted Zlatanov
2003-11-20 18:42 ` Lőrentey Károly
2003-11-19 21:51 ` Kai Grossjohann
2003-11-19 21:53 ` Kai Grossjohann
2003-11-19 22:05 ` Josh Huber
2003-11-20 20:30 ` Kai Grossjohann
2003-11-20 21:07 ` Josh Huber
2003-11-20 14:48 ` Jake Colman
2003-11-20 11:22 ` Ted Zlatanov
2003-11-20 12:31 ` Lőrentey Károly
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=4nu150car5.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).