------- You are receiving this mail because: -------
You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=1031
--- Comment #15 from Jeremy Harris <jgh146exb@???> 2012-06-06 15:36:58 ---
So far it smells like we're considering a generic option that can be used on
either a router or a transport, which calls an ACL.
- Do we need both; would just the router-option do (given enough richness of
information fed to the ACL)?
- How should information be fed to the ACL?
- What information?
- Assuming the option causes a post-router (or transport) ACL call, the final
result of the ACL can be ignored. Do we need a separate pre-router (transport)
method? Would the result be useful in that scenario (eg. as a router
precondition)? Could a more general data return be useful?
- Is the same technique applicable to authenticators?
--
Configure bugmail:
http://bugs.exim.org/userprefs.cgi?tab=email
