atom feed6 messages in net.sourceforge.lists.courier-usersRe: [courier-users] BOFHCHECKDNS and RFC
FromSent OnAttachments
FMFeb 26, 2008 7:05 am 
niclasFeb 26, 2008 7:51 am 
Sam VarshavchikFeb 26, 2008 4:16 pm 
Alessandro VeselyFeb 26, 2008 10:56 pm 
Gordon MessmerFeb 28, 2008 11:48 pm 
FMMar 2, 2008 6:18 pm 
Subject:Re: [courier-users] BOFHCHECKDNS and RFC
From:Gordon Messmer (yiny@eburg.com)
Date:Feb 28, 2008 11:48:25 pm
List:net.sourceforge.lists.courier-users

FM wrote:

I ha to temporarily disable this option because of bad DNS config from one of our clients. Now the client argue that this setting is not in any RFC so it does not want to fix the MX - PTR issue ! Is there a RFC or a good document that I can you to prove my point :)

http://www.courier-mta.org/FAQ.html#esmtperr http://www.rfc-editor.org/rfc/rfc1035.txt

Section 3.3.9 defines the "exchange" value as a <domain-name>. It defines <domain-name> as a series of labels, and not as IP addresses. The RFC notes that MX records cause type A additional processing, and does not specify that type CNAME additional processing is allowed.

RFC 974 may further recommend that aliases are never used in the data section of MX RRs.

In the end, though, your client's attitude won't get mail delivered. Using names that resolve to A records will. One of those things is useful. Tell him to suck it up and cooperate a little.