Re: [Exim] Unrouteable Mail Domain - Why??

Hi!

Now I just have one more eMail which isn't routeable... :-//
OK, here the new -qff -v and later on more to your question
regarding debug output.

=================================
[root@rzvemgw root]# exim -qff -v
Single queue run
LOG: 0 MAIN
Start queue run: pid=2499 -qff
delivering message 17h4eg-0000dN-00 (queue run pid 2499 fd 6)
LOG: 0 MAIN
Unfrozen by forced delivery
LOG: 0 MAIN
** CrstnBremer@???: unrouteable mail domain "aol.com"
LOG: 0 MAIN
Frozen (delivery error message)
delivering message 17h499-0000BP-00 (queue run pid 2499 fd 6)
LOG: 0 MAIN
Unfrozen by forced delivery
LOG: 0 MAIN
** Tine-v-H@???: unrouteable mail domain "t-online.de"
LOG: 0 MAIN
Frozen (delivery error message)
LOG: 0 MAIN
End queue run: pid=2499 -qff
[root@rzvemgw root]#
=================================



The debug output with "exim -d9 -bt Tine-v-H@???"
says the following:

=================================
[root@rzvemgw root]# exim -d9 -bt Tine-v-H@???
Exim version 3.36 debug level 9 uid=0 gid=0
Berkeley DB: Sleepycat Software: Berkeley DB 3.3.11: (July 12, 2001)
Caller is an admin user
Caller is a trusted user
originator: uid=0 gid=0 login=root name=root
sender address = root@???
Address testing: uid=0 gid=0 euid=55 egid=55
>>>>>>>>>>>>>>>>>>>>>>>>
Testing Tine-v-H@???
t-online.de in local_domains? no (end of list)
address Tine-v-H@???
local_part=Tine-v-H domain=t-online.de
domain is not local
>>>>>>>>>>>>>>>>>>>>>>>>
routing Tine-v-H@???, domain t-online.de
amavis_router router called for Tine-v-H@???
route_domain = t-online.de
routelist_item = *
after handling route_lists items, matched = 1
original hostlist= options=
expanded hostlist="" options=
queued for amavis transport: local_part=Tine-v-H domain=t-online.de
errors_to=NULL
domain_data=NULL local_part_data=NULL
routed by amavis_router router:
deliver to Tine-v-H@???
transport: amavis
Tine-v-H@???
deliver to Tine-v-H@???
router = amavis_router, transport = amavis
search_tidyup called
[root@rzvemgw root]#
=================================

Okay, I tried to understand all of it but ehh I think you've got to much
better than me ;-))
So in fact I can't determine if exim is doing an MX lookup...
BTW the resolv.conf is configured to use our internal nameserver.
The exim machine is located in the internet-DMZ, the nameserver
is located in the local network and has the rights to do mx-lookups
and everything you could need on DNS.

Michael