I just installed James 2.2.0a3 early this morning, everything looks like it's working fine.
Then this morning I saw this in the DNSserver log: 06/06/03 01:48:23 INFO dnsserver: Autodiscovery is enabled - trying to discover your system's DNS Servers 06/06/03 01:48:24 INFO dnsserver: Adding autodiscovered server 64.81.159.2 06/06/03 01:48:24 INFO dnsserver: Adding autodiscovered server 216.231.41.2 06/06/03 01:48:24 INFO dnsserver: DNS Server is: 64.81.159.2 06/06/03 01:48:24 INFO dnsserver: DNS Server is: 216.231.41.2 06/06/03 01:48:24 INFO dnsserver: DNS Server is: 64.81.159.2 06/06/03 01:48:24 INFO dnsserver: DNS Server is: 216.231.41.2 06/06/03 04:05:44 ERROR dnsserver: Couldn't resolve MX records for domain jakarta.apache.org. 06/06/03 04:17:30 ERROR dnsserver: Couldn't resolve MX records for domain ws.apache.org. 06/06/03 04:47:31 ERROR dnsserver: Couldn't resolve MX records for domain jakarta.apache.org. 06/06/03 04:52:09 ERROR dnsserver: Couldn't resolve MX records for domain jakarta.apache.org. 06/06/03 05:07:05 ERROR dnsserver: Couldn't resolve MX records for domain galamail.com. 06/06/03 05:17:50 ERROR dnsserver: Couldn't resolve MX records for domain jakarta.apache.org. 06/06/03 05:35:14 ERROR dnsserver: Couldn't resolve MX records for domain jakarta.apache.org. 06/06/03 05:46:09 ERROR dnsserver: Couldn't resolve MX records for domain ws.apache.org. 06/06/03 05:49:12 ERROR dnsserver: Couldn't resolve MX records for domain jakarta.apache.org. 06/06/03 06:06:08 ERROR dnsserver: Couldn't resolve MX records for domain jakarta.apache.org. 06/06/03 06:17:35 ERROR dnsserver: Couldn't resolve MX records for domain jakarta.apache.org. 06/06/03 06:20:42 ERROR dnsserver: Couldn't resolve MX records for domain moh006.offershouse.com. 06/06/03 06:25:08 ERROR dnsserver: Couldn't resolve MX records for domain jakarta.apache.org. 06/06/03 06:29:30 ERROR dnsserver: Couldn't resolve MX records for domain jakarta.apache.org. 06/06/03 07:04:42 ERROR dnsserver: Couldn't resolve MX records for domain jakarta.apache.org. 06/06/03 07:22:13 ERROR dnsserver: Couldn't resolve MX records for domain jakarta.apache.org. 06/06/03 07:40:28 ERROR dnsserver: Couldn't resolve MX records for domain jakarta.apache.org. 06/06/03 08:00:51 ERROR dnsserver: Couldn't resolve MX records for domain ws.apache.org. So suddenly, I'm worried that mail from apache.org isn't getting through... Yes, if things are still working...please don't even bother mentioning it <g> I don't even see the point of this being an INFO entry if there are no actual problems/issues that need to be known about. Thanks. -Chris > -----Original Message----- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED] > Sent: Friday, June 06, 2003 12:42 AM > To: James-Dev Mailing List > Subject: Logging in the new DNSServer service > > > The new DNS service contains the following: > > //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().error(logBuffer.toString()); > try { > InetAddress.getByName(hostname); > servers.add(hostname); > } catch (UnknownHostException uhe) { ... } > > I am thinking that should be at INFO level, not ERROR level. Anyone > disagree? For example, we get that message for e-mail coming > from the ASF, > because there aren't any MX records. The code goes ahead and > does the right > thing, using the A record. > > --- Noel > > > --------------------------------------------------------------------- > 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]
