2005/9/26, Thomas Kirchner <[EMAIL PROTECTED]>: > * On Sep 26 16:24, Ow Mun Heng ([email protected]) wrote: > > Now, I'm wondering how to properly configure Dspam. Dspam seems to work > > well enough but I"m having trouble with dspam not properly > > tagging/recognising SPAM. SPAMassassin seems to do fine. > > I was really excited about trying DSPAM, but I had the same result as > you - it just couldn't tag spam. I scoured the manuals and mailing > lists, learned all about the configuration system, but DSPAM just > couldn't be anywhere near as accurate as Spamassassin. Spamassassin is a > bit slower to run, but it just simply does a better job. I, too, liked > the CGI interface, but if it's an interface to a failing spam filter, > what's the point?
As far as I know about DSPAM (anybody correct me if I'm wrong), you must train it in order to begin detecting spam. I have never configured it, but I'm using it, and it provides two special addresses per user: [EMAIL PROTECTED] and [EMAIL PROTECTED] Whenever you receive spam not detected by DSPAM you must forward it to the first address. Whenever DSPAM incorrectly tags a mail as SPAM you must forward it to the second address (false positive). The more you train it, the more accurate it gets. HTH, best regards Jose -- [email protected] mailing list
