We\u2019re a PA partner and have clustered Qmail with 4 servers + NFS storage. We\u2019ve seen an issue where Qmail throws the following error:<\/p>\n
failure: Sorry,_I_could_not_find_a_mail_exchanger_or_IP_address._(#5.4.4)\/<\/p>\n
This is a permanent error and means Qmail will not retry, the sender will receive an NDR (Non delivery reply \/ bounce back).<\/p>\n
I\u2019ve seen 3 causes so far that cause this error to appear with Qmail. Other MTAs like Postfix and Exim don\u2019t have this issue.<\/p>\n
1) CNAMEs as MX records and or there being no A record for the $domain.tld in the absence of an MX record.
\n2) smtp fixup is enabled on the cisco pix\/asa firewall where the MX record resides.
\n3) The size of the returned DNS packet from the nameservers of the domain causes Qmail issues.<\/p>\n
Our experience isn\u2019t limited to these scenarios but they are the most common that we\u2019ve seen.<\/p>\n
As we manage quite a number of Cisco ASA firewalls and we have mixed MTAs behind them (qmail, exchange, postfix, exim etc) we always disable Ciscos smtp fixup. I\u2019ve seen too many problems caused by it and it serves no use.<\/p>\n
Parallels should take a leaf out of Postfix\u2019s book as it actually detects this and performs a work around on the fly:<\/p>\n
Jul 8 09:46:00 bk1-relay relay16\/smtp[8773]: 21EDC39803E: enabling PIX workarounds: disable_esmtp delay_dotcrlf for hostname.domain.tld[74.xxx.xxx.xxx]:25<\/p>\n
How do you detect if smtp fixup is enabled?<\/p>\n
Easy telnet to the MX record on port 25 and if the 220 banner returned looks like:<\/p>\n
Escape character is \u2018^]\u2019.
\n220 ***********************<\/p>\n
then it is enabled. I\u2019d advise the end user in question to disable this setting on their firewall(s).<\/p>\n
We\u2019re using the smtproutes fix for domains that refuse to fix their end and it works fine. This is normally located in:<\/p>\n
\/var\/qmail\/control\/
\nor
\n\/usr\/local\/qmail\/shared\/control\/ (typically in clustered configurations)<\/p>\n
If the file \u201csmtproutes\u201d doesn\u2019t exist simply create it and you add the route like this:<\/p>\n
$domain.tld:relay.domain.tld where relay.domain.tld is your non qmail relay server.<\/p>\n","protected":false},"excerpt":{"rendered":"
We\u2019re a PA partner and have clustered Qmail with 4 servers + NFS storage. We\u2019ve seen an issue where Qmail throws the following error:<\/p>\n
failure: Sorry,_I_could_not_find_a_mail_exchanger_or_IP_address._(#5.4.4)\/<\/p>\n
This is a permanent error and means Qmail will not retry, the sender will receive an NDR (Non delivery reply \/ bounce back).<\/p>\n
I\u2019ve seen 3 causes so far […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[32],"tags":[],"_links":{"self":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/3586"}],"collection":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3586"}],"version-history":[{"count":1,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/3586\/revisions"}],"predecessor-version":[{"id":3587,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/3586\/revisions\/3587"}],"wp:attachment":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3586"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3586"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3586"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}