All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Masover <ninja@slaphack.com>
To: Tomasz Chmielewski <mangoo@mch.one.pl>
Cc: "Łukasz Mierzwa" <prymitive@pcserwis.net>, reiserfs-list@namesys.com
Subject: Re: why does reiserfs list get so much spam?
Date: Fri, 16 Sep 2005 13:51:39 -0500	[thread overview]
Message-ID: <432B143B.8030808@slaphack.com> (raw)
In-Reply-To: <432B0FAC.4050905@mch.one.pl>

Tomasz Chmielewski wrote:
> David Masover schrieb:
> 
> (...)
> 
>>> If You will look in the headers of messages that You get from this list
>>> You will see that there is spamassassin running on thebsh.namesys.com,
>>> it's just that it is not configured good enough.
>>
>>
>>
>> Can spamassassin be configured "good" enough?
>>
>> I use dspam:
>>
>> http://www.nuclearelephant.com/projects/dspam/
>>
>> There are some articles about why dspam has a fundamentally better
>> design than spamassassin, and why in general statistical filters beat
>> manual-rule-based ones like spamassassin.
> 
> 
> Yeah spamassassin can work extremely well.
> 
> I guess these articles are based on the quality of spamassassin which 
> checks spam from this list? :)
> 
> And it's not really true that spamassassin is a manual-rule-based filter 
> only.

Right, but the statistical/learning component of spamassassin is just 
that -- a component, to be combined with razor/pyzor, manual rules, and 
anything else they can think of.  I think dspam does a much better job 
at being a statistical filter, and that's all it does -- and that's all 
it needs to.  Some people have reported 99.997% accuracy from dspam, 
beating humans.

Anyway, the articles are about the principle of the thing.  A 
statistical filter will beat a manual one every time, because it's 
faster and better at coming up with rules, and you don't need to update 
your definitions to start filtering the new spam -- just train on two or 
three mails, and you're done.

  reply	other threads:[~2005-09-16 18:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-16 10:18 why does reiserfs list get so much spam? Tomasz Chmielewski
2005-09-16 10:41 ` Ingo Bormuth
2005-09-16 10:52   ` Tomasz Chmielewski
2005-09-16 11:03     ` Lexington Luthor
2005-09-16 11:08     ` Grzegorz Kulewski
2005-09-16 11:19       ` Tomasz Chmielewski
2005-09-16 12:40         ` Gregory Maxwell
2005-09-16 12:46           ` Łukasz Mierzwa
2005-09-16 14:12             ` Bruce Israel
     [not found]             ` <20050916135217.GA12930@kruemel>
2005-09-16 14:41               ` Łukasz Mierzwa
2005-09-16 18:24             ` David Masover
2005-09-16 18:32               ` Tomasz Chmielewski
2005-09-16 18:51                 ` David Masover [this message]
2005-09-16 19:11                   ` Tomasz Chmielewski
2005-09-16 19:51                   ` Łukasz Mierzwa
2005-09-16 19:54                     ` David Masover
2005-09-16 14:00         ` Grzegorz Kulewski

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=432B143B.8030808@slaphack.com \
    --to=ninja@slaphack.com \
    --cc=mangoo@mch.one.pl \
    --cc=prymitive@pcserwis.net \
    --cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.