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]
