• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

adding blacklist support to exchange 2003

Those are about as good as they get, but I'd include the following as well:

(Spews.org)
sbl.spamhaus.org

(Sorbs.net)
dnsbl.sorbs.net


 
I am using blacklists on a FreeBSD/Sendmail server, with excellent results.

blacklists:
combined.najbl.org
sbl-xbl.spamhaus.org
bl.spamcop.net

This, along with client rulesets and spamassassin has reduced spam by 97%

PM or email me if you want to see todays list of rejected mail hosts😀
 
Ok when you say client rule sets I assume you are using outlook 2003. Also what exactly is spamassassin I here everyone talking about it.
 
SpamAssassin is an anti-spam engine that will check incoming mail and determine if it's spam. My office runs McAffee Spam Killer for Exchange 2000, and it uses Spamassassin to determine if an e-mail is spam or not.
 
spamassassin
It runs on the server, and detects spam by tallying up the various clues that a piece of mail is spam. Once it is determined to be spam, it can be handled many different ways:
It can be wrapped up as a mime attachment, and them forwarded on to the users with anything you want added to the subject.
It can be just forwarded with anything you want added to the subject.

Those are just a few options.
client rules: if I set spamassassin to add ****SPAM**** to subject line, I can make a client rule in any mail client to put that mail in a spam folder. Review the contents to make sure of no false positives, and mass delete.
 
Back
Top