[Exim] sender verify problems

Pàgina inicial
Delete this message
Reply to this message
Autor: Giuliano Gavazzi
Data:  
A: exim-users
Assumpte: [Exim] sender verify problems
I am seeing some problems with sender verify.
I have done a test with a domain that, as I verified with nslookup, does not have an MX record:

[drum:~] g% telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 drum.humph.com ESMTP Exim 4.11 Sun, 05 Jan 2003 02:41:47 +0000
helo localhost
250 drum.humph.com Hello localhost [127.0.0.1]
mail from: popo@???
250 OK
rcpt to: some_local_user
451 Temporary local problem - please try later

resulting in the log:

2003-01-05 02:42:42 H=localhost [127.0.0.1] sender verify defer for <popo@???>: host lookup did not complete
2003-01-05 02:42:42 H=localhost [127.0.0.1] F=<popo@???> temporarily rejected RCPT some_local_user: Could not complete sender verify

but:

[drum:~] g% nslookup
Default Server: localhost.humph.com
Address: 127.0.0.1

> set type=mx
> iprolink.com

Server: localhost.humph.com
Address: 127.0.0.1

*** localhost.humph.com can't find iprolink.com: Non-existent host/domain


So, why is this not giving an error 550 as it does for other senders with no MX?

Is it be because the authoritative servers for that domain are giving the same Not-existent... for the SOA of that domain thus contradicting their status of authoritative servers?


For instance, look at this garbage:

> set type=ns
> iprolink.com

Server: IPROLINK.CO.NZ
Address: 202.36.121.1

Non-authoritative answer:
iprolink.com    nameserver = NS1.IPROLINK.CH
iprolink.com    nameserver = NS2.IPROLINK.CH
iprolink.com    nameserver = IPROLINK.CO.NZ


Authoritative answers can be found from:
NS1.IPROLINK.CH internet address = 194.41.63.1
NS2.IPROLINK.CH internet address = 194.41.63.19
IPROLINK.CO.NZ internet address = 202.36.121.1
>


(this is the sort of stuff that gives named "lame server" log lines)

Giuliano