Tony Finch wrote: > On Wed, 13 Feb 2008, Renaud Allard wrote:
>> So this should not produce the "re-routed" effect AFAIK. I really don't
>> see any place where it could even find the wallonie.be suffix, except
>> maybe in "qualify_domain" and in local_domains.
>>
>> Do you have something else for me to test to find out why such
>> re-routing occurs?
>
> Does exim -d -bt correction@wallex provide enlightenment?
>
Yes, indeed. I didn't know that.
Here is some info if some people have the same problem.
dnslookup router called for correction@wallex
domain = wallex
DNS lookup of wallex (MX) gave NO_DATA
returning DNS_NODATA
DNS lookup of wallex (AAAA) gave NO_DATA
returning DNS_NODATA
DNS lookup of wallex (A) succeeded
157.164.136.240 in "0.0.0.0 : 127.0.0.0/8 : 192.168.0.0/16 :
172.16.0.0/12 : 10.
0.0.0/8 : 169.254.0.0/16"? no (end of list)
fully qualified name = wallex.wallonie.be
wallex.wallonie.be 157.164.136.240 mx=-1 sort=-52
domain changed to wallex.wallonie.be
rewriting header lines
re-routed to correction@???
If I try to resolve it via all nameservers:
grep ^nameserver /etc/resolv.conf | awk '{ print $2 }' | xargs -n 1 host
-t A wallex | grep wallex
Host wallex not found: 3(NXDOMAIN)
Host wallex not found: 3(NXDOMAIN)
Host wallex not found: 3(NXDOMAIN)
But ping wallex works
ping -c 1 wallex
PING wallex.wallonie.be (157.164.136.240): 56 data bytes
64 bytes from 157.164.136.240: icmp_seq=0 ttl=62 time=0.928 ms
--- wallex.wallonie.be ping statistics ---
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.928/0.928/0.928/0.000 ms
There is no search or domain in /etc/resolv.conf and nothing in /etc/hosts
In fact the hostname is sufficient to do a search through the domain
name. If I do "hostname smtp68" (instead of smtp68.wallonie.be), and
then reissue a ping, wallex doesn't work anymore.
