Bug#389484: exim4-daemon-heavy: expansion variable $host_lookup_deferred does not work

[Andreas Metzler]

On 2006-09-26 Micha Lenk <micha at lenk.info> wrote:
> Package: exim4-daemon-heavy
> Version: 4.62-0bpo1
> Severity: normal

> Hi,

> the expansion variable $host_lookup_deferred does not work as described
> in specification.

> Example: 127.0.0.2 does not resolve to any host:

> $ host 127.0.0.2
> Host 2.0.0.127.in-addr.arpa not found: 3(NXDOMAIN)

> So I would expect that $host_lookup_deferred would expand to 1.
[...]

Afaict, no, it shouldn't. It tried to resolve the host and got the
definitive answers that the host does not exist. There was no timeout
or othr difficulties in looking up the host.

<Quote>
$host_lookup_deferred

This variable normally contains “0”, as does $host_lookup_failed. When
a message comes from a remote host and there is an attempt to look up
the host’s name from its IP address, and the attempt is not
successful, one of these variables is set to “1”.

If the lookup receives a definite negative response (for example, a
DNS lookup succeeded, but no records were found), $host_lookup_failed
is set to “1”.

If there is any kind of problem during the lookup, such that Exim
cannot tell whether or not the host name is defined (for example, a
timeout for a DNS lookup), $host_lookup_deferred is set to “1”.
<unquote>


>     defer	message = Sorry, I can't resolve your IP address. Fix your DNS.
> 		condition = $host_lookup_deferred
> 
> ... but it doesn't work as intended (this ACL should defer SMTP connects
> from IP addresses which do not resolve to any hostname).

I think $host_lookup_failed might do what you want.

cu andreas
-- 
The 'Galactic Cleaning' policy undertaken by Emperor Zhark is a personal
vision of the emperor's, and its inclusion in this work does not constitute
tacit approval by the author or the publisher for any such projects,
howsoever undertaken.                                (c) Jasper Ffforde