IMO the ACL section of exim has sort of evolved into a type of
programming language. With that said, what you have stated reminds me
of some programming techniques that are quite bad. That is passing
data to routines using global variables. You stated this way of
programming (Or
On Sun, 2007-12-09 at 19:33 -0800, Marc Perkel wrote:
How about it Graeme? You're pretty good that this.
I could make the same request of you, Marc. Why not?
Graeme
--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use
Graeme Fowler wrote:
On Sun, 2007-12-09 at 19:33 -0800, Marc Perkel wrote:
How about it Graeme? You're pretty good that this.
I could make the same request of you, Marc. Why not?
Graeme
Seems to me like it would be easy to add. You just have to pick some
internal variable
Or perhaps I've smoked something I shouldn't have and I'm confusing simple
matters (wouldn't be a first)?
This is more a response to the whole thread rather than just you Eli :)
If something so simple as ACLs need to have enough parameters passed to
them that people start thinking it's too
On Mon, Dec 10, 2007 at 06:38:38AM -0800, Marc Perkel said:
Seems to me like it would be easy to add.
You're under the impression that introducing and enforcing scopes and
namespaces is easy? It's certainly not the end of the world, but I
don't think it quite qualifies as easy.
--
Eli Sand wrote:
warnacl=some_acl($var1, $var2)
or keeping with the exim sense:
acl=some_acl{$var1}{$var2}
I figured that would be what a lot of people would think it'd end up looking
like, however where did you get $var1 and $var2 from to pass to the acl?
Ted Cooper wrote:
If something so simple as ACLs need to have enough parameters passed to
them that people start thinking it's too confusing to understand, and
they they are polluting the global namespace, then I think those people
need to change their thinking just a little bit and examine
Eli Sand wrote:
I seem to recall wanting this same functionality myself. I am
currently using acl variables, but I believe it would look much better
if the parameters could be passed in another way. This was written
before there were named acl variables (back when there was just 0-9).
It would be nice if we could pass parameters to ACLs. Parameters would
be accessible in standard names like acl_param1 acl_param2 ...
acl = my_acl test
my_acl
warn logwrite = acl_param1
--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at
It would be nice if we could pass parameters to ACLs. Parameters would
be accessible in standard names like acl_param1 acl_param2 ...
acl = my_acl test
my_acl
warn logwrite = acl_param1
You're kidding, right? Why don't you just use acl variables that already
exist? Don't have enough?
I seem to recall wanting this same functionality myself. I am
currently using acl variables, but I believe it would look much better
if the parameters could be passed in another way. This was written
before there were named acl variables (back when there was just 0-9).
Personally I don't
Eli Sand wrote:
It would be nice if we could pass parameters to ACLs. Parameters would
be accessible in standard names like acl_param1 acl_param2 ...
acl = my_acl test
my_acl
warn logwrite = acl_param1
You're kidding, right? Why don't you just use acl variables that already
12 matches
Mail list logo
