Peter, What OS version are you using? CentOS 5/6/7?
I've got cname checks removed in updated versions of qmailtoaster according to DJB (https://lists.gt.net/qmail/users/138190)
CentOS 7: ftp://ftp.qmailtoaster.org/pub/repo/qmt/CentOS/7/development/x86_64/qmail-1.03-2.2.qt.el7.x86_64.rpm
CentOS 6: ftp://ftp.qmailtoaster.org/pub/repo/qmt/CentOS/6/development/x86_64/qmail-1.03-1.1.qt.el6.x86_64.rpm
CentOS 5: ftp://ftp.qmailtoaster.org/pub/repo/qmt/CentOS/5/development/i386/qmail-toaster-1.03-1.3.23.i386.rpm
ftp://ftp.qmailtoaster.org/pub/repo/qmt/CentOS/5/development/x86_64/qmail-toaster-1.03-1.3.23.x86_64.rpm Eric On 4/18/2018 9:52 AM, Peter Peltonen wrote:
I am getting this error when sending to the tyks.fi domain: 2018-04-18 18:15:18.787618500 starting delivery 32313: msg 2232943 to remote ***@tyks.fi 2018-04-18 18:16:01.777845500 delivery 32313: deferral: CNAME_lookup_failed_temporarily._(#4.4.3)/ I've been searching for this error and found the following: 1) known error for qmail + bind combination 2) fix is to either patch with qmailtoaster-big-dns.patch or use other recursor than bind Before I can proceed with 2) I have some questions though: * Why is the patch not installed by default in the toaster? I can see Shubert had it: https://github.com/QMailToaster/qmail/blob/master/qmailtoaster-big-dns.patch * As I understood it, the problem is a response too big that BIND cannot handle. I am a bit confused here, as the tyks.fi lookup does not return a big response and it does not have any CNAME records in it. Could this error be caused by something else? * If I would to change resolveer and not to patch, can I both run a BIND server and have a different resolver at the same time on the same server? Best, Peter --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
-- Eric Broch White Horse Technical Consulting (WHTC) --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
