Elliot Foster wrote:
You could also use port 587 (submission) non-ssl if you're just trying to get around port 25 being blocked. That way you wouldn't have to re-route the connections to localhost. You would also be able to retain the connecting IP.
But then I'd have to run a second instance of qpsmtpd in that case (since I don't see any support for running on two ports in the existing code).
I'm assuming the "some stupid admins" part was a joke? Or are they blocking on SPF soft failures?
No joke. I don't think that SPF is ready to be used to block mail (hard *or* soft failure). The one site is running some M$loth anti-spam feature for Exchange and I get no reason back why they are blocking. I have our SPF records set to hard fail and so far I have exactly 1 domain that blocked the mail (which shows exactly how useless SPF is)...
John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748
