Mike Cardwell wrote:
> If I set $acl_m0 to equal something in the rcpt acl I can refer to it in the
> routers. If there is more than one recipient, I'll end up overwriting the
> contents of that acl variable. I need to be able to store information on
> a per recipient basis from the rcpt acl and then pull the relevant data out
> in a router.
> ${extract \
> {column1} \
> {${expand:${extract \
> {$local_part@$domain} \
> {$acl_m0} \
> }}} \
> }
>
> It works in the tests I've done... What have I missed?
I end up wanting this sort of thing too... however I wonder
whther I'm not bending exim out of shape, trying to do
too much directly in ACL code, and not enough in routers.
Yes, some $acl_rN variables would be nice. They'd need
an incompatible change to the spool datafile, though, I
think.
- Jeremy
