On Friday 04 August 2006 15:04, Tom Brown wrote: > We had trouble sending to a particular domain because their MX records were > incorrect. So, I added a line to esmtproutes to get around the problem. > Now, we can send to this domain. However, we cannot receive email from the > domain because of the MX records. I am seeing this error in the log: > > 517-MX records for xxx.com violate section 3.3.9 of RFC 1035 > > Why is courier checking the MX records for incoming mail and checking > esmtproutes for outgoing mail? > > Is there a way around this besided getting the domain to fix their MX > records?
I think I've found the answer to my own question. I found it in the archives in a 2004 post. "esmtproutes affects outgoing mail, and has nothing to do with incoming mail. ... Your only option is to turn off BOFHCHECKDNS, which turns off ALL dns checking, letting in all sorts of crap." Is this still the case? Thanks, Tom ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
