> > Your problem is URIBL_BLOCKED. The usual cause of this is running a mail > system that relies on a public-access DNS resolver, although if you have > substantial volume on your system you can have this happen with your own DNS > infrastructure. See http://uribl.com/refused.shtml for details. > > Note that if you have a mail system pointed at a free public resolver like > those operated by Google or OpenDNS, you are getting a view of DNS that is > manipulated by the operator to suit their business interests and a usage > model consisting primarily of web browsing with a seasoning of other personal > client uses. Such resolvers are not intended for use by mail servers and > often respond by design in ways that make them grossly unfit for use by mail > servers. >
Ah…. the lightbulb illuminates! Thanks. I now see this to be the problem, and I was using Google DNS. I can fix this.
