On Tuesday 31 October 2006 15:02, Stephen Gran took the opportunity to say:
> On Tue, Oct 31, 2006 at 09:05:21PM +0800, W B Hacker said:
> > Marc Haber wrote:
> > > While we're at it - has somebody thought about address_data_foo and
> > > address_data_bar as a similiar concept to named acl variables?
> > >
> > Last time I looked we were calling them 'acl_r' variables...
> >
> > As in acl_c = 'Connect', acl_m = 'Message', acl_r = 'Routing'
>
> steve@gashuffer:~$ zgrep -i acl_r /usr/share/doc/exim4-base/spec.txt.gz
> steve@gashuffer:~$
>
> It appears we're not calling them anyting, at the moment.
Jeremy Harris suggested $acl_r* variables (r for recipient) on February 28, in
the thread entitled "acl variables per recipient rather than per message".
They would still be set in ACLs, not in routers, and so are out of scope of
the original question. The difference between address_data and ACL variables
is that ACL variables are stored on the spool, whereas address_data is set on
each routing occasion.
--
Magnus Holmgren holmgren@???
(No Cc of list mail needed, thanks)
