It seems that the RemoteDelivery mailet is trying to connect to the IP address that the DNS returns for the domain, and NOT (one of) the servers listed as the MX host. I am pretty sure of this, based on watching netstat while James is making the connection.
Mike,
This reminds me (again -- I wrote the same thing on October 11, in response to a question) of something I've seen in the finally block in org.apache.james.dnsserver.DNSServer.findMXRecords(hostname). You can see the code below. If the DNS lookup fails to find MX records, then findMXRecords() may return simply the hostname from the email address.
So possibly your MX lookup is not working. I would check first to confirm that you have the nameservers configured correctly.
Rich Hammer
} finally {
//If we found no results, we'll add the original domain name if
//it's a valid DNS entry
if (servers.size () == 0) {
StringBuffer logBuffer =
new StringBuffer(128)
.append("Couldn't resolve MX records for domain ")
.append(hostname)
.append(".");
getLogger().info(logBuffer.toString());
try {
InetAddress.getByName(hostname);
servers.add(hostname);
} catch (UnknownHostException uhe) {
// The original domain name is not a valid host,
// so we can't add it to the server list. In this
// case we return an empty list of servers
logBuffer = new StringBuffer(128)
.append("Couldn't resolve IP address for host ")
.append(hostname)
.append(".");
getLogger().error(logBuffer.toString());
}
}
}
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
