>Question is, what test should I be running to catch genuine spam? > >I want to be on the safe side to start out. I have (and I am) reading >the manual and I am looking up the entries in the spam log.
Each domain seems to have a different "spam profile", depending on how long the domain has been around, where the addresses are found, and so forth. So different domains may have different needs. The most ideal tests tend to be those that catch a lot of spam, while catching little (if any) legitimate mail. In general, we've found the best test is the BADHEADERS test, because it can catch a lot of spam, while not letting any legitimate mail through (with the exception of mail that is not RFC-compliant, which would come from a broken E-mail client -- but their mail isn't going to make it to many other servers, as well). Another good test is the MAILFROM test, which will catch spam that uses a fake domain in the return address, which also shouldn't catch any legitimate mail. A new DNS-based test that works quite well is the SPAMCOP test. To see how well this and other tests work, you can go to http://www.declude.com/spamtrap.htm . -Scott --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
