I appreciate your listing what you think is a better solution. Why would your editor not whitelist your e-mail address through the Postini Web-based config page? I have not used SpamAssassin for three years now. It does not seem to have changed too much since then. Back then in 2006, I was using SpamAssassin for a medium sized business client. I had it configured with all of the possible options: Using all of the DNSBL lists that were available at the time except for SPEWS and couple of other very aggressive ones, using Razor/Pyzor, Bayesian filtering, extensive whitelists of their customer contacts, and frequent updates to SpamAssassin itself. I went through and configured and tested all of the features and monitored it to make sure that it was working. It never approached the level true positives that we achieved when we switched to Postini. There were lots of false positives too, more than we ever had with Postini. Plus I spent some serious time maintaining SpamAssassin that I no longer needed to spend with Postini. For people with new Postini accounts, I think that it is important to check their Web-based junk mail folder weekly and whitelist any false-positive messages they find. But once you have done that for a couple of months, I find that there are very few false positives after that. I spot check my Postini junk mail folder every two or three months just to make sure there are no false positives that I need to whitelist.