Sorry if any dupes of this message come through; I've tried to send this a bunch of times but my messages to the list keep getting a delayed-delivery response with what appears to be a related problem to that reported below, even with BOFHCHECKDNS=0. It makes me wonder more how courier accesses dns since everything else on the server is able to resolve names with no issues.
<[email protected]>: <<< DNS lookup failed. Hi All, I've always run with BOFHCHECKDNS successfully, but after recently upgrading my debian packages form courier 0.61 to courier 0.63, courier suddenly started rejecting all domains for both inbound and outbound mail. A small sampling: Jan 25 07:58:25 aloha courieresmtp: id=00000000032E4D3E.000000004B5D8509.00000D76,from=<logch...@*manawiz.com*>,addr=<[email protected]>: DNS lookup failed. Jan 25 09:20:06 aloha courieresmtp: id=00000000031FC00E.000000004B5DEDBA.000064D0,from=<s...@*wisdombell.com*>,addr=<[email protected]>: DNS lookup failed. Jan 24 18:27:41 aloha courieresmtpd: error,relay=::ffff:209.85.210.189,from=<[email protected]>: 417 DNS lookup failure: *gmail.com*. Try again later Jan 24 18:28:02 aloha courieresmtpd: error,relay=::ffff:209.85.222.148,from=<3wr1dswaaeyclyo2zto-mprtyyp23rzzrwpr2z503....@groups.bounces.google.com>: 417 DNS lookup failure: *groups.bounces.google.com*. Try again later. Jan 24 18:49:08 aloha courieresmtpd: error,relay=::ffff:64.79.150.121,from=<[email protected]>: 417 DNS lookup failure: *netbeans.org*. Try again later. Setting BOFHCHECKDNS=0 of course resolves this, but also lets in more spam, so I'd like to find a way to fix the problem. DNS is configured and working fine on the server, e.g.: aloha:/etc/courier# dig +short MX gmail.com 30 alt3.gmail-smtp-in.l.google.com. 40 alt4.gmail-smtp-in.l.google.com. 5 gmail-smtp-in.l.google.com. 10 alt1.gmail-smtp-in.l.google.com. 20 alt2.gmail-smtp-in.l.google.com. aloha:/etc/courier# dig +short A alt3.gmail-smtp-in.l.google.com 209.85.218.11 aloha:/etc/courier# dig +short MX groups.bounces.google.com 5 gmr-smtp-in.l.google.com. 10 alt1.gmr-smtp-in.l.google.com. 10 alt2.gmr-smtp-in.l.google.com. aloha:/etc/courier# dig +short A gmr-smtp-in.l.google.com 209.85.221.205 aloha:/etc/courier# dig +short MX manawiz.com 0 manawiz.com. aloha:/etc/courier# dig +short A manawiz.com 64.34.170.220 aloha:/etc/courier# What could cause this? I've search for prior instances of BOFHCHECKDNS issues and haven't seen anything like this. Nor have I seen a clear explanation of how courier checks DNS or exactly what it checks. That would be illuminating. Thanks for any help, Chuck ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
