The thread about adding forwarding headers makes me think about how
verification is done in the context of forwarding. I'm looking at
section 44.25 of the spec where it talks about "generated child
addresses" and how it is decided if these are also recursively
verified. It doesn't say but it sounds as if this is about addresses
generated by a redirect router with a data option, such as one
handling the traditional /etc/aliases file.
But what about forwarding resulting from rules in user .forward files
in either exim filter or sieve format? Since the rules can mention
headers, they can't be evaluated at RCPT time, so "child address
generation" this way doesn't even make sense if the verification is
done from the ACL that runs at this stage. So does it mean such
destinations are not recursively verified? And does this mean the
recommended method of gathering info for the forwarding headers won't
work in this situation?
--
Ian
--
## subscription configuration (requires account):
##
https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-users-unsubscribe@???
## Exim details at
http://www.exim.org/
## Please use the Wiki with this list -
http://wiki.exim.org/
