See chain of notes below from a couple of weeks ago. I finally got a response from Register.com, the owner of the MX record that is in question.
Here is their response: ================================= Thank you for contacting Register.com. We apologize for any incovnenience this may cause, however the mx records for the domain names are valid, and do not need to be changed. The check you are running for the mx record is not required, and works properly with most email providers. We sincerely apologize that the settings we are using are causing a problem for the email services you are using, and some mail is becoming undeliverable however the mx records we use currently are required in this manner due to the services we provide. ================================== So register.com says they are right. You say James is right. I don't know enough to know. All I know is that I have customer using James on my server that can't get email to a client. The error I get from DNSReport is: =================================== 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.229 =================================== Seems pretty straightforward that register.com is wrong if the RFCs indeed say what this report claims. But I don't have enough background on what is happening to argue with them. Would somebody like to draft a reply back to Register.com for me? If Register.com is indeed doing this on all of their records as they indicated, seems to me that more James users than just me would be upset. Help! Thanks. -----Original Message----- From: Stefano Bagnara [mailto:[EMAIL PROTECTED] Sent: Thursday, January 26, 2006 10:45 AM To: James Users List Subject: Re: "Can't find DNS for domain" when domain does exist JWM wrote: > 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?) No. The fix contains the reference to the behaviour that was not implemented in James. The problem fixed was that a host name does not have an MX name associated but it has a CNAME address associated. A compliant SMTP server should resolve the CNAME and ask the MX servers for the CNAME host. That was a COMPLIANCE fix, I don't think it is the same of your case (not as you described it) but I pointed to it because it is the only issue reported against James MX resolution. I think we shouldn't fix the issue you are describing because James seems to be compliant and the dnsreport site confirms that the destination domain dns is bad. The fix for your problem is to write to the DNS mantainer for that domain, attaching the dnsreport response. Stefano > 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 --------------------------------------------------------------------- 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]
