The server connects to a BIND DNS server. However, this CNAME issue
apparently has been a problem for a long, long time as noted in the link
Eric provided.
Jeff
On 11/30/2017 9:55 AM, Chris wrote:
Is the server that is having the issues using djbdns or BIND? There
was a thread on June 21 that discussed the differences in the way
djbdns handles CNAMES and EDNS, vs the way BIND does, and why it
causes delivery issues for qmail.
-Chris
On Wed, Nov 29, 2017 at 9:02 PM, Eric Broch <[email protected]
<mailto:[email protected]>> wrote:
I'll see if I can have a patched version for separate download out
tomorrow. It's interesting that I never see these errors on my
servers. How often do you see them, and is mail not delivered?
On 11/29/2017 9:24 PM, Jeff Koch wrote:
Hi Eric:
I read the link you provided and agree with the patch to remove
the CNAME lookups. Jeff
On 11/29/2017 11:05 PM, Eric Broch wrote:
Hi Jeff,
I've been reading some about this and on one site
<https://lists.gt.net/qmail/users/138190> Dan Bernstein
recommended in 2012 or there about that the CNAME lookup should
be commented out in the code. I might do this and make it
available sometime soon.
Eric
On 11/29/2017 8:44 PM, Jeff Koch wrote:
Hi Group:
We are seeing some errors like this in the qmail logs:
2017-11-23 17:14:55
info msg 6891411: bytes 3794956 from <[email protected]>
<mailto:[email protected]> qp 27142 uid 89
starting delivery 144153: msg 6891411 to remote
[email protected] <mailto:[email protected]>
delivery 144153: deferral:
CNAME_lookup_failed_temporarily._(#4.4.3)/
Doing a little research says that it's often resolved by
installing the big dns patch - but I believe QMT already has
that patch. Could anything else cause this error?
Also, why is qmail even trying to do a CNAME lookup when the MX
record is what's needed ?
Jeff
--
Eric Broch
White Horse Technical Consulting (WHTC)
--
Eric Broch
White Horse Technical Consulting (WHTC)
