I admit I have not looked at DSPAM since I first was hooked on ASSP in February after reading the HOWTOFORGE article on ASSP. My Clients could not handle the spam load at the client anymore. (not a good idea to accept it all, then classify it, aka DSPAM)
Im going to go back as re-eval DSPAM, but as I remember: DSPAM is a Bayesian filter only. In other words, all those Hello, DNS, BL, PB, and incredible powers of PCRE checks in ASSP simply dont exist in DSPAM. DPAM lets ALL the spam through, then tries to figure out if it is spam with ONLY ONE METHOD. the CRM114 Classifier written by a Univ prof. Bayes is also the most CPU-intensive method. This is dumb design. Fritz and John have it right: do the easy, simple-to-execute (helo checks come to mind) checking then, after all the OBVIOUS things are done, run Bayes. DSPAM does NONE OF THESE Checks. It works hard to achieve its score. ASSP works smart to achieve its score. Plus DSPAM has one option: on or off. ASSP has this: http://www.magicvillage.de/~Fritz_Borgstedt/assp/ASSP-Admin-GUI/ http://www.magicvillage.de/~Fritz_Borgstedt/assp/ASSP-Admin-GUI/ -- View this message in context: http://www.nabble.com/Replacing-the-bayesian-engine-with-DSPAM--tf3702920.html#a14037849 Sent from the assp-user mailing list archive at Nabble.com. ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
