https://bugs.exim.org/show_bug.cgi?id=1867
Bug ID: 1867
Summary: fail_defer_domains router option ignored under certain
circumstances
Product: Exim
Version: 4.86
Hardware: x86-64
OS: Linux
Status: NEW
Severity: bug
Priority: medium
Component: Routing
Assignee: nigel@???
Reporter: mike.brudenell@???
CC: exim-dev@???
Consider this router:
route_to_smarthost:
driver = dnslookup
domains = ! +local_domains
fail_defer_domains = *
ignore_target_hosts = +loopback_ip_addrs : +private_ip_addrs
transport = remote_smtp_to_smarthost
no_more
According to the Specification I can set the fail_defer_domains router option
to a domainlist; if the domain does not exist or various other conditions the
router would normally decline, but if the domain is listed in the value of
fail_defer_domains the router should instead defer.
However this is not happening when sending a test message to a recipient
address whose domain has neither MX, AAA nor A records, such as
test-account@???
For example
echo test | exim -f goodsender@??? -v -d+all -i
test-account@???
The debugging output produced:
1) shows no indication that fail_defer_domains has been encountered, and
2) the router continues to decline rather than defer.
This results in the recipient/message permfailing as being unrouteable, rather
than being retained in the queue for trying again later.
The problem occurs regardless of whether the fail_defer_domains value is the
wildcard "*" or a specific domain name such as york.ac.ukkkk
I have discussed this with Jeremy Harris, who confirms it is a bug:
"Bug. It works for the case where there's a good MX record but no A
record, but not for your case (missing MX). Despite what the docs say"
I attach a text file containing a minimal configuration file and debugging
output that shows the problem from an attempt to send a message over SMTP to an
"@york.ac.ukkkk" address.
Cheers,
Mike Brudenell
--
You are receiving this mail because:
You are on the CC list for the bug.
