Stephano, Thanks. That appears to be the situation. Does this fix that you reference make james follow a cname in the mx record even though it's an unsupported behaviour? (i.e. make james work despite the error?)
Is there any way to patch this fix into my existing installation of James (e.g. replace one jar file, etc), or do I need to do a complete reinstall of the latest version? I just don't have the bandwidth in my schedule now to risk a massive upgrade. Thanks for the info. Jerry -----Original Message----- From: Stefano Bagnara [mailto:[EMAIL PROTECTED] Sent: Thursday, January 26, 2006 3:18 AM To: James Users List Subject: Re: "Can't find DNS for domain" when domain does exist Jerry Malcolm wrote: > I'm getting a bounce when trying to send mail to a valid domain. I get an > error in the log that says it can't find the dns entry. The dns entry is > clearly there when I do an nslookup. > > However, I went to dnsreport.com and got the following error when it > analyzed the DNS for the domain: > > =============== > > FAIL MX A lookups have no CNAMEs WARNING: One or more of your MX records > points to a CNAME. CNAMEs are prohibited in MX records, according to RFC974, > RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3. The problem MX record(s) are: > mxmail.register.com.->rcom-outblaze-com.mr.outblaze.com.->205.158.62.206 > > =============== > > OK, seems pretty obvious that there's something wrong with the DNS. But is > this what's causing James to be unable to send the mail? Even if the error I would say yes: DNS is the routing information for the mail systems. If it's wrong mail systems will not deliver messages. The only bug I found in James about DNS handling is described here: http://issues.apache.org/jira/browse/JAMES-413 If this is your case then it's fixed in the current trunk. Many MTA will follow the CNAME anyway, but this is an unsupported behaviour and not standard. They should fix their MX. Send the dnsreport result to the "bad" domain owner and let him know he's loosing mail because of this misconfiguration and he will be happy to ask his provider to fix this. Stefano > is with the destination, my customer tells me other people have no problem > emailing this person. So the question is, how can make James not be so > overly sensitive to this problem? > > Thanks. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
