I have something of a weird problem with an address not being allowed into
our relay servers (which are running 1.82, but I can also duplicate this
on 2.02). Basically whats happening is the MX lookup for the FQDN returns
a "TRY_AGAIN" and exim gives up at that point. However, on another address
without MX records, that MX lookup returns "NO_DATA" and exim procedes to
check the A records and accepts the mail in. Arguably the "TRY_AGAIN"
response is the inappropriate response, but shouldn't exim procede to
check the A record as well in that case?
Below are the results of two exim -d9 -bt commands which show this
behavior.
TIA,
Tabor
Shore.Net
> exim -d9 -bt mikeh@???
Exim version 2.02 debug level 9 uid=0 gid=1
probably Berkeley DB version 1.8x (native mode)
Actual local interface address is 127.0.0.1
Actual local interface address is 10.8.0.30
Actual local interface address is 207.244.127.244
Actual local interface address is 192.168.254.11
Address testing: uid=0 gid=1 euid=27 egid=27
Testing mikeh@???
search_open: dbm "/usr/local/etc/exim/dbm/virtual.db"
search_find: file="/usr/local/etc/exim/dbm/virtual.db"
type=dbm key="clientsys.computac.com" partial=-1
internal_search_find: file="/usr/local/etc/exim/dbm/virtual.db"
type=dbm key="clientsys.computac.com"
file lookup required for clientsys.computac.com
in /usr/local/etc/exim/dbm/virtual.db
lookup failed
address mikeh@???
local_part=mikeh domain=clientsys.computac.com
domain is not local
>>>>>>>>>>>>>>>>>>>>>>>>
routing mikeh@???, domain clientsys.computac.com
lookuphost router called for mikeh@???
dns lookup: route_domain = clientsys.computac.com
DNS lookup of clientsys.computac.com (MX) gave TRY_AGAIN
lookuphost router deferred clientsys.computac.com
message: host lookup did not complete
mikeh@??? cannot be resolved at this time:
host lookup did not complete
search_tidyup called
> exim -d9 -bt tmcdonou@???
Exim version 2.02 debug level 9 uid=0 gid=1
probably Berkeley DB version 1.8x (native mode)
Actual local interface address is 127.0.0.1
Actual local interface address is 10.8.0.30
Actual local interface address is 207.244.127.244
Actual local interface address is 192.168.254.11
Address testing: uid=0 gid=1 euid=27 egid=27
Testing tmcdonou@???
search_open: dbm "/usr/local/etc/exim/dbm/virtual.db"
search_find: file="/usr/local/etc/exim/dbm/virtual.db"
type=dbm key="burlma1-smrt1.gtei.net" partial=-1
internal_search_find: file="/usr/local/etc/exim/dbm/virtual.db"
type=dbm key="burlma1-smrt1.gtei.net"
file lookup required for burlma1-smrt1.gtei.net
in /usr/local/etc/exim/dbm/virtual.db
lookup failed
address tmcdonou@???
local_part=tmcdonou domain=burlma1-smrt1.gtei.net
domain is not local
>>>>>>>>>>>>>>>>>>>>>>>>
routing tmcdonou@???, domain burlma1-smrt1.gtei.net
lookuphost router called for tmcdonou@???
dns lookup: route_domain = burlma1-smrt1.gtei.net
DNS lookup of burlma1-smrt1.gtei.net (MX) gave NO_DATA
DNS lookup of burlma1-smrt1.gtei.net (A) succeeded
Actual local interface address is 127.0.0.1
Actual local interface address is 10.8.0.30
Actual local interface address is 207.244.127.244
Actual local interface address is 192.168.254.11
fully qualified name = burlma1-smrt1.gtei.net
burlma1-smrt1.gtei.net 4.2.35.10 -1 -56
queued for remote_smtp transport: local_part=tmcdonou
domain=burlma1-smrt1.gtei.net
routed by lookuphost router:
deliver to tmcdonou@???
transport: remote_smtp
host burlma1-smrt1.gtei.net [4.2.35.10]
tmcdonou@???
deliver to tmcdonou@???
router = lookuphost, transport = remote_smtp
host burlma1-smrt1.gtei.net [4.2.35.10]
search_tidyup called
--
________________________________________________________________________
Tabor J. Wells twells@???
Shore.Net Systems Admin. Just another victim of the ambient morality
--
*** Exim information can be found at
http://www.exim.org/ ***
