DSPAM v3.2 Beta-1 Released 20
Nuclear Elephant writes "After three months of development, the first public beta of DSPAM v3.2 has been released for testing. New features include SQLite support, A Win32 build supplement, extensions API, and some advanced new processing functionality such as Bill Yerazunis' (CRM114) Sparse Binary Polynomial Hashing and v1.2 of the author's Bayesian Noise Reduction Logic. Accuracy in 3.x has reportedly peaked as high as 99.991% (2 errors in 22,786 messages). Grab the new copy and participate in the request for feedback."
WHAT?!?! (Score:1)
Re:WHAT?!?! (Score:1)
Re:WHAT?!?! (Score:1)
why user infomercial.. (Score:2)
"DSPAM users frequently see between 99.95% (1 error in 2000) all the way up to 99.991% (2 errors in 22,786)."
that could mean just about anything, "frequently see" could mean that they will see succes rates like that if they get the same mail 20 000 times...
or are they trying to 'sell' the the little phb in all of us?
Re:why user infomercial.. (Score:1, Funny)
Re:SpamAssassin vs. DSPAM (Score:3, Informative)
I totally agree. I used DSPAM for a while, gave it a fair shot, participated on the mailing list. I even, at times, got encouraging results. Ultimately, DSPAM required way too much nursemaid work to make it work for my installation and I scrapped it and went back to SA. The general feel I got from the DSPAM crowd was a big dick waving contest with other products, particularly, but not limited to, SA. A typical mailing list message looked like:
Re:And to anyone out there who might believe this. (Score:1)
DSPAM. . . neat at fist, not for long. (Score:4, Informative)
So, then I started using an SQL database. That worked great for a while, except it was slow. Now, admittedly, I'm running my mail server on an old machine (Dual Pentium Pro 200's, with 450MB RAM), but DSPAM was horrible. With more than half a dozen e-mails to process at a time, it would just choke. And the space issue. . . my spam-data database got over 300MB within a couple of weeks! And, yeah, I was processing a lot of mail, but come on. That's just not right.
Finally, I decided it just wasn't worth it. So, I tried an alternative that the DSPAM author has spoken fairly highly of, CRM114 [sourceforge.net]. That thing rocks! Within a few days, it was catching most of the spam, it runs much faster than DSPAM or SA, and it has fixed-sized spam token databases, so unless you explicitely increase the size, they won't grow past what you set them up for.
I can't see myself bothering with any other spam filter anytime soon.
Re:DSPAM. . . neat at fist, not for long. (Score:1, Informative)
Re:DSPAM. . . neat at fist, not for long. (Score:1)
The default purge settings won't even touch the database until tokens and signatures have been in there for at least 14 days. Even after tightening up the purge settings, the database was way too big. In fact, even without purching, the databse should not have been allowed to get that big. I mean, seriously, it processes some 20MB of e-mail, and the spam database from it is over 300MB? There's something wrong with t
Re:DSPAM. . . neat at fist, not for long. (Score:1)
As for it's configuration, I used mostly default settings, although as I mentioned above, I tightened it's purge settings to try to reduce the DB size.
I've used a lot of different spam filters, including a bunch of bayesian style ones, and none o
2 errors in 22,786 (Score:1, Funny)
1 in 11,393 was too easy?