On the front lines in the war against spam

After months of rage and resignation, I have been playing with some anti-spam tools lately that actually seem to work. Andy turned me on to MailWasher, which is a client-side tool to help manage spam. MailWasher will check incoming message headers and try to determine which messages are spam. Unlike most mail programs, it's smart about it, using a robust blacklist feature, user-defined filters, built-in heuristics, and open-relay lists provided by ORDB and SpamCop to pick out the spammy stuff. By and large, it works. So long as your e-mail usage patterns jibe with using MailWasher regularly, it's a mighty effective defense.

Using MailWasher, I've been most impressed with the blacklist services provided by ORDB and the like. These services, which maintain lists of SMTP servers left open for spammers to exploit for sending their junk, manage to identify well over 90% of the spam I receive, with very few false positives. I hadn't realized just how effective these tools could be.

However, MailWasher doesn't really work for me. I like to keep my mail program running and checking mail frequently, and having to fiddle with another client-side program is annoying. I went ahead and slapped an ORDB/SpamCop filter on TR's mail server, so that mail sent via open relays can't be delivered to us. We can see in the server logs when messages are bounced, and so far, nothing important has been filtered out¬ójust the pre-processed meat by-products.

So can spam really be fought effectively? Or are we stuck with Nigerian wire fraud schemes involving the deadly cocktail of herbal viagra, human growth hormone, farm animals, and amazingly low mortgage rates?

Tip: You can use the A/Z keys to walk threads.
View options

This discussion is now closed.