Re: [exim] Recipient verify only for non-authenticated users

Jakob Hirsch wrote:
> W B Hacker, 2011-10-27 13:41:
>
>> Works that way here...
>>
>> 'Course I DO run acl's on ALL phases of the smtp session, so...
>>
>> ... an 'accept' ain't final 'til the Fat Lady sings (end of DATA phase..)
>
> You are mixing two different things. An "accept" finishes the _current_
> ACL, whether you use endpass or not. Other ACLs run after that can still
> "deny", of course. Again, endpass has nothing to do with this.
>
>

*heavy sigh*

Seems to me you missed the entry point, are arguing the obvious...
and demeaning a useful feature..

A triggered 'accept' is not 'permanent' until end of DATA. Period.

A triggered 'deny' class verb is 'permanent' AT ONCE. WHEREVER it is.

An 'endpass' is not needed by an 'accept', but is harmless and supports
consistency in style w/r slef-diocumenting 'reminders' of what is taking
place.

More importantly - 'endpass' IS useful for other branching use. VERY useful.

There are some actions and conditions you just cannot easily 'hang' onto
an 'accept' verb because it marches to the beat of a different drummer
w/r order of evaluation and what it does/does not do before and after it
fires.

Circumstances may be better suited to a 'warn' that has to ascertain
things AND report them AND action others AND manipulate things - that do
not (yet) give rise to a deny, nor (yet) a 'final' accept - but may
have no further need for wasting resources in traversing the *remainder*
of the acl test clauses in a given phase.

Far easier to use an 'endpass' and rely on a stand-alone 'accept' at the
END of each phase to otherwise onpass the 'survivors'.

Works much the same as split verbs in certain SPOKEN languages.

Some things just won't away 'Best Current Practice' or no, go.

;-)

Bill
--
韓家標