Re: [exim-dev] [Bug 608] ACL condition with deny called from…

Top Page
Delete this message
Reply to this message
Author: Simon Arlott
Date:  
To: exim-dev
Subject: Re: [exim-dev] [Bug 608] ACL condition with deny called from acl_smtp_quit/ acl_smtp_notquit causes error
On Fri, October 5, 2007 09:36, Graeme Fowler wrote:
> A "deny" in the quit or not_quit acl is superfluous - at this point, the remote
> server has either closed the connection gracefully (ie. sent a QUIT) or has
> terminated unexpectedly, perhaps due to a network problem or (in the case of
> Exim) by dropping the connection on purpose.
>
> This is why the log message says:
>
> ACL for not-QUIT returned ERROR: "deny" is not allowed in a QUIT or not-QUIT
> ACL
>
> This is documented here:
>
> http://www.exim.org/exim-html-current/doc/html/spec_html/ch40.html#SECTQUITACL
>
> The ACL for the SMTP QUIT command is anomalous, in that the outcome of the ACL
> does not affect the response code to QUIT, which is always 221. Thus, the ACL
> does not in fact control any access. For this reason, the only verbs that are
> permitted are accept and warn.
>
> and here:
>
> http://www.exim.org/exim-html-current/doc/html/spec_html/ch40.html#SECTNOTQUITACL
>
> Like the QUIT ACL, this ACL is provided to make it possible to do customized
> logging or to gather statistics, and its outcome is ignored. The delay modifier
> is forbidden in this ACL, and the only permitted verbs are accept and warn.
>
> The fact that you're calling a nested ACL is not relevant - the outcome is a
> "deny", which is an invalid verb for the "parent" ACL.


The outcome of the nested ACL isn't used as the verb in the parent ACL, it's the
result of a condition, so this is still a bug.

> Closing, not a bug.


--
Simon Arlott