Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Ham/Spam how does it work ?
Date: Fri, 13 Jun 2003 10:38:23 -0400	[thread overview]
Message-ID: <4n7k7qcaao.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <plop87smqfqj6y.fsf@gnu-rox.org> (Xavier Maillard's message of "Thu, 12 Jun 2003 19:50:13 +0200")

On Thu, 12 Jun 2003, zedek@gnu-rox.org wrote:
> I am now using spam.el for months and seems I use my Gnus quite
> often, I was expecting spam to be carried out from 'legal' group
> automagically: I mean when fecthing new mails.
> 
> But it is not ! :(
> 
> At least for me. 
> 
> So I know my setup is good (but in case of doubt, I can post it),
> and that marking article as spam, and/or quitting a group do the
> right job (moving spam to the spam group, etc...).

Make sure your spam-destination parameter is set correctly.  What does

(gnus-parameter-spam-process-destination "legal")

return?

> My question is more directed to bogofilter performance than other.
> 
> How can I train easily and without too much effort, bogofilter
> through the Gnus spam-group feature ?
> 
> A friend of mine has recently sent to me a 4Mb tar archives full of
> spam (yeah it rocks), but I don't really know how to play with all
> this stuff.
> 
> The aim behind this is to inject all this s*t into my dedicated
> spam-group group and train bogofilter in it. I am fairly sure that
> the bad quality of the spam detection in my groups comes from this:
> didn't train it enough before.

Right now, you have to do it from the command line.  Mass training
will come into spam.el, it's planned for later this year (patches
welcome, of course).

Ted



      reply	other threads:[~2003-06-13 14:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-12 17:50 Xavier Maillard
2003-06-13 14:38 ` Ted Zlatanov [this message]

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