9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dave Lukes <davel@anvil.com>
To: 9fans <9fans@cse.psu.edu>
Subject: Re: [9fans] tactic
Date: Fri,  2 Apr 2004 01:26:48 +0100	[thread overview]
Message-ID: <1080865608.1815.220.camel@rea> (raw)
In-Reply-To: <MOBYDICKwBUkzmbQpaU00002277@mobydick.int.entrisphere.com>

First, don't get me wrong: I'm NOT a spamassassin fan, BUT ...
it's the best I've seen, and I've got ~80 people to keep happy.

> I find that spamassassin sucked rocks for filtering my email.

Yeah, it probably did: I've never tried it but
I'm sure it's uneconomical for small workloads.

> I am currently using CRM114: http://crm114.sourceforge.net/

Nice, but ...

> The drawback is that you have to train it before it works very
> well.  In the beginning it's about 50%, but after the first week
> or two it has been well above 98% for me.

And most of the usage I've seen has been on small,
low-volume connections.
i.e. even more than spamassassin it probably works better
in single-mbox situations.

OTOH out-of-the-box spamassassin does~~~80%,
and we've got it up to ~96% (one server for all 80 people),
which is deemed acceptable by the powers that be.

If I tuned it a bit more wrt rbls etc. & did the
per-user profile stuff I'm sure I could hit 99%.
(The only negative there is that the per-user stuff is
 vulnerable to forgery:-(.)

>   It usually miss classifies
> a few messages out of about 150+/day for me.  I should note that
> 3/4 of my email is actually SPAM, so I'm pretty happy with it.

Strangely, we're only getting ~55% crap at the moment.
Maybe 'cos I bounce (not can) spam?

Back to plan9 programming ...,
	Dave.




  reply	other threads:[~2004-04-02  0:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <QKKPXMWZAUGMQBSVGGFUZ@guanajuato.com>
2004-03-31 14:38 ` ron minnich
2004-03-31 17:02   ` Micah Stetson
2004-04-01  3:55     ` ron minnich
2004-03-31 21:05   ` boyd, rounin
2004-04-01 15:10     ` Joel Salomon
2004-04-01 14:30       ` boyd, rounin
2004-04-01 15:47         ` Jon Snader
2004-04-01 17:00           ` Dave Lukes
2004-04-01 17:24             ` Jon Snader
2004-04-01 16:08     ` Dave Lukes
2004-04-01 16:46       ` George Michaelson
2004-04-01 18:24       ` Tad Hunt
2004-04-02  0:26         ` Dave Lukes [this message]
2004-04-01 15:25 Tiit Lankots
2004-04-01 15:26 ` Joel Salomon
2004-04-01 15:32 ` Dave Lukes
2004-04-01 16:13 Tiit Lankots
2004-04-01 16:56 ` Dave Lukes
2004-04-02  9:25 plan9fans

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=1080865608.1815.220.camel@rea \
    --to=davel@anvil.com \
    --cc=9fans@cse.psu.edu \
    /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).