I don’t have any problems with Spam Assassin, per se. I mean, we use it to proof outgoing campaigns within our application. However, it’s just like anything else, if you don’t configure it once you drop it on a machine, you are bound to get undesirable results.

I do think it’s funny that it assigns a small score for being registered with Privacy Post and then a much bigger (additional) score for being listed on open-whois.org for being registered with Privacy Post. That’s double dipping for the same *offense*.

If you’re curious, our whois info probably won’t be obscured in the near future as we work out some different options for out private label (branded) accounts.