: Guilty as Charged?"> Guilty as Charged? I found it quite humorous that the eWeek Enterprise Update [e-mail newsletter] containing your article on "How to slam spam" was caught by my system as spam. It seems that the mail server address 220.127.116.11 in the message headers is being reported by SpamCop as being blacklisted. The entire range 205.150.6.* appears to belong to DoubleClick, a source of much spam.SpamAssassin User We installed spamassassin pro about a month ago and are extremely pleased with it. Most of the people in our organization have finished "training" their installation, and the amount of spam that makes it to our in-boxes is on the order of two or fewer messages per day, which is down from 60-plus per day. You listed "no central management" and "hodgepodge of sorting policies" as cons for the product. Actually, to us, these were deciding pro factors. I subscribe to many programming lists (a lot from eWeek), and a universal policy would and did block these newsletters, eWeeks included. But with my version of the hodgepodge, I can let them in, while the normal user doesnt have to worry about anything.
Review: Making Short Work of Spam
Review: Cloudmark Banks on Users
Service, Tool Take Meat Out of Spam
Trio Take Different Tacks in Fighting Spam
Anti-Spam Bills in the Works
Pre-Approval for Mass E-Mailers on Tap
New E-Mail Technologies Put Spam in the Cross Hairs
On the bright side, the article was well-written, with much useful information. However, maybe eWeek should reconsider how it is delivering that information.
Jeff Young, MD/Win Corp.
Paul M. Nations, Senior Systems Programmer, Arkansas Department of Higher Education, Little Rock, Ark.Links to Related Articles: