[courier-users] esmtproutes is causing - 550 relay not permitted

This has me stumped. I have esmtproutes working fine for two domains - basically all mail for domain1.com is being relayed to newserver.example.com I found that it was best to remove the entry from hosteddomains and run makehosted domains as well. Now I've added a new entry to esmtproutes

Re: [courier-users] esmtproutes is causing - 550 relay not permitted

Kevin Bailey writes: Now I've added a new entry to esmtproutes (and removed it from hosteddomains) but when email is now sent to the the server I'm getting 550 relay not permitted There's no such error message in Courier. pgpCjl4ZQpxfZ.pgp Description: PGP signature

[courier-users] Yet another attempt to fix forwarding

We all know how SPF breaks forwarding. Some even say that forwarding has been broken since rfc1123 deprecated source routing in the envelope return path, in 1989. Anyway, it is broken now. That's why I'm asking to this list for any comments, thoughts, and insights that may lead to fix

Re: [courier-users] Yet another attempt to fix forwarding

Gordon Messmer wrote: Alessandro Vesely wrote: More or less, that's it. The Anti-Spam Research Group might have been a more suitable list for this topic, but I'd rather seek practical advice. Any? Look at SRS? http://www.openspf.org/SRS SRS solves a number of cases for large