Re: [exim] Adding a per-recipient message header

Quoting Philip Hazel:

>>> This problem wouldn't exist if there were some inbuilt functions for
>>> working with hash style acl variables, other than extracting from
>>> them.
>> Agreed. I'd love to see that in future exim versions...
> The next release of Exim allows you to make up your own names for ACL
> variables, and there is no (reasonable :-) limit to how many you can
> have.

Which is really nice! :)
The mentioned hash functions would have the advantage, that one can use
dynamic keys. Hopefully nobody comes up with expansion of acl variable
names now...
I don't see why anybody would want that (you want to access the value
later, so you have to now the key).

It could be nice for address_data though. extract{ works most of the
time, but it seems more like a crutch. It would be more useful to have
"set acl_X_something = ..." in routers, I think.