Hi All > We recently added, for the first time, a hosted domain to our > long-running Courier-MTA. There was some slightly odd behaviour > regarding DNS lookup on return addresses when sending email from the > hosted domain account. The newly added domain was added to > hosteddomains, and also to esmtpacceptmailfor. I also added it to > /etc/hosts to avoid mail loops for local deliveries. We received mail > correctly to the new mailboxes from inside and outside. However when > sending mail from the hosted domain, it failed to locate the domain in > the reverse DNS lookup, giving "517-Domain does not exist" in the log, > even though nameserver queries from the local machine showed the > domain details correctly. Everything worked fine if we turned off > BOFHCHECKDNS. > As a follow-up to this posting, we discovered that nameserver queries for the new domain returned an MX record pointing to a FQDN, but the way the DNS servers were configured on the local machine meant that the queries could not locate the A record corresponding to this MX record. Simply adding an A record to the local DNS server pointing to the mailserver seems to have solved the problem. The mail loops also disappeared.
Hopefully this may be helpful to someone. Ken ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
