Gnus development mailing list
 help / color / mirror / Atom feed
From: pinard@iro.umontreal.ca (François Pinard)
Cc: ding <ding@gnus.org>
Subject: Re: spam-stat regeneration notes
Date: 14 Jun 2003 07:57:42 -0400	[thread overview]
Message-ID: <oqznkkg9c9.fsf@titan.progiciels-bpi.ca> (raw)
In-Reply-To: <ruo7k7p4hgl.fsf@billw2lx.wolfram.com>

[Bill White]

> I've been using spam-stat for about 6 months now, and noticed lately
> that spam processing was getting mightly slow

My observation as well.  Things which are ever growing are becoming slow
after some amount of time, progressively, insiduously, yet sometimes sooner
than one expects.  But then, the thing might have gotten fairly big, and
rather quite difficult to clean up or reconstruct properly.  At least, this
summarises _years_ of experience with BBDB. :-)

> - Has anyone else needed to regenerate a Bayesian hash system?

I kludged other methods so it is easy for me to do, and I did it once or
twice in the last few months.  One thing is that you acquire experience over
time at properly sorting ham and spam (especially in some border cases), and
your training databases also get more dependable if you "expire" them
somehow.  As a consequence, regenerating your Bayesian system makes it much
better.  It does not take many wrongly filed messages in the training
databases for significantly weakening the capabilities of Bayesian system.

> - Is there an easy way to run a function over an entire directory
>   tree, while specifying which dirs to include or avoid?

GNU `find' maybe? :-)

In my own case, it did not take long to build the tool I needed, which is
pretty aware of all my little habits...  You might tackle this as well?

-- 
François Pinard   http://www.iro.umontreal.ca/~pinard



  reply	other threads:[~2003-06-14 11:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-14  0:43 Bill White
2003-06-14 11:57 ` François Pinard [this message]
2003-06-15 18:38 ` 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=oqznkkg9c9.fsf@titan.progiciels-bpi.ca \
    --to=pinard@iro.umontreal.ca \
    --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).