Sujit Choudhury wrote:
> In the test exim -bh I am getting the following:
> >>> host in host_lookup? yes (matched "0.0.0.0/0")
> >>> looking up host name for 200.44.242.136
> >>> IP address lookup failed: h_errno=1
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >>> host in host_reject_connection? no (option unset)
> >>> host in sender_unqualified_hosts? no (option unset)
> >>> host in recipient_unqualified_hosts? no (option unset)
> >>> host in helo_verify_hosts? no (option unset)
> >>> host in helo_try_verify_hosts? no (option unset)
> >>> host in helo_accept_junk_hosts? no (option unset)
> LOG: SMTP connection from [200.44.242.136]
> 220 garuda.wmin.ac.uk ESMTP Exim 4.12 Fri, 11 Apr 2003 16:22:44 +0100
>
> In all the "problem" e-mail we are finding this same theme. I had to
> go back to 2.12.
Oh no!
Tony: well, now you know another place where they run 2.12 ;)
> Any suggestion?
Sorry, my brain was too slow to think.
A quote from spec.txt:
If the DNS lookup fails, that is, if there is no reverse DNS entry for
the IP address, Exim behaves as if the host does not match the list.
This may not always be what you want to happen. To change Exim's
behaviour, the special item '+include_unknown' may appear in the list
(at top level - it is not recognized in an indirected file). If any
subsequent items require a host name, but no name can be found, Exim
behaves as if the host does match the list. For example,
host_reject_connection = +include_unknown:*.enemy.ex
rejects connections from any host whose name matches "*.enemy.ex", and
also any hosts whose name it cannot find.
You have an ACL that does a similar thing:
deny hosts = !/mail/exim/files/net_reject_except : \
+include_unknown:partial-lsearch;/mail/exim/files/host_reject : \
/mail/exim/files/net_reject
+include_unknown forces rejection of recipients from hosts for which no
hostname can be found.
--
Kirill Miazine, Stud. Jur.
Faculty of Law, University of Oslo
