Re: [exim-dev] HELO cache

Top Page
Delete this message
Reply to this message
Author: Simon Arlott
Date:  
To: exim-dev
Subject: Re: [exim-dev] HELO cache
On 23/07/06 09:50, Jakob Hirsch wrote:
> Quoting Simon Arlott:
>
>> It could, but then you'd miss the completely bogus HELO names that
>> fail syntactic checks:
>
> What do you mean? They are already catched, partly by Exim's builtin
> checks, partly by ACL rules.
> If you want such HELOs to go into the db, you can do these checks after
> the queries.


If the HELO name is syntactically invalid or rejected for other reasons by Exim itself, the HELO ACL is never run.

HELO blah
SMTP<< HELO blah
blah in helo_lookup_domains? no (end of list)
sender_fullhost = (blah) [0.0.0.0]
sender_rcvhost = [0.0.0.0] (helo=blah)
set_process_info: 22246 handling incoming connection from (blah) [0.0.0.0]
using ACL "acl_check_helo"
processing "accept"
check condition = test
accept: condition test deferred
SMTP>> 451 Temporary local problem - please try later

451 Temporary local problem - please try later
LOG: MAIN REJECT
H=(blah) [0.0.0.0] temporarily rejected EHLO or HELO blah: invalid "condition" value "test"
sender_fullhost = [0.0.0.0]
sender_rcvhost = [0.0.0.0]

HELO blah_blah
SMTP<< HELO blah_blah
host in smtp_accept_max_nonmail_hosts? yes (matched "*")
SMTP>> 501 Syntactically invalid HELO argument(s)

501 Syntactically invalid HELO argument(s)
LOG: MAIN REJECT
rejected HELO from [0.0.0.0]: syntactically invalid argument(s): blah_blah

--
Simon Arlott