Your message dated Tue, 26 Sep 2006 20:38:07 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#389484: exim4-daemon-heavy: expansion variable
$host_lookup_deferred does not work
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
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.
But if I run Exim like this:
$ exim4 -bh 127.0.0.2 -d-all+expand
I see following (shortened to the essential parts):
Exim version 4.62 uid=0 gid=0 pid=8539 D=100
Berkeley DB: Sleepycat Software: Berkeley DB 4.3.27: (December 22, 2004)
Support for: crypteq iconv() IPv6 PAM Perl GnuTLS move_frozen_messages
Content_Scanning Old_Demime
[...]
**** SMTP testing session as if from host 127.0.0.2
**** but without any ident (RFC 1413) callback.
**** This is not for real!
host in hosts_connection_nolog? no (option unset)
LOG: smtp_connection MAIN
SMTP connection from [127.0.0.2]
host in host_lookup? yes (matched "*")
looking up host name for 127.0.0.2
IP address lookup using gethostbyaddr()
IP address lookup failed: h_errno=1
LOG: host_lookup_failed MAIN
no host name found for IP address 127.0.0.2
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)
using ACL "smtp_connect"
[...]
processing "defer"
expanding: $host_lookup_deferred
result: 0
check condition = $host_lookup_deferred
= 0
defer: condition test failed
[...]
The corresponding ACL statement looks like this:
smtp_connect:
[...]
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).
Since I'm using a Sarge backport it might be a backport specific bug
(though unlikely). So, please check first if this occurs in any other
package (etch?) too.
Have a nice day
Micha
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-sorgfalt
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages exim4-daemon-heavy depends on:
ii exim4-base 4.62-0bpo1 support files for all exim MTA (v4
ii libc6 2.3.2.ds1-22sarge4 GNU C Library: Shared libraries an
ii libdb4.3 4.3.27-2 Berkeley v4.3 Database Libraries [
ii libgnutls11 1.0.16-13.2sarge2 GNU TLS library - runtime library
ii libldap2 2.1.30-8 OpenLDAP libraries
ii libmysqlclient14 4.1.11a-4sarge7 mysql database client library
ii libpam0g 0.76-22 Pluggable Authentication Modules l
ii libpcre3 4.5-1.2sarge1 Perl 5 Compatible Regular Expressi
ii libperl5.8 5.8.4-8sarge5 Shared Perl library
ii libpq3 7.4.7-6sarge3 PostgreSQL C client library
ii libsasl2 2.1.19.dfsg1-0sarge2 Authentication abstraction library
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi.
Andreas Metzler wrote:
> On 2006-09-26 Micha Lenk <[EMAIL PROTECTED]> 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.
[...]
>
> I think $host_lookup_failed might do what you want.
Sorry, I were confused because I didn't realize that the specification
is talking about two different options. It definitely was to late. :-}
Thanks for clarification.
Micha
--- End Message ---
