I'll admit I haven't read the whole planning document so this may be
addressed in some bit that I haven't yet digested but it seems to me
that this bit...
---- start copy ----
The (new) second section of the configuration file contains any number
of Access Control Lists. Each list begins with a name that is terminated
by a colon. The lines that follow, up to the next name line or the `end'
line, comprise the named list. For example:
local_acl:
accept recipient = +local_domains : verify : verify_sender
relay_acl:
accept recipient = +relay_domains
accept authenticated
The colons in individual ACLs are interpreted as `and'. The ACLs are
used by being referred to from options in other parts of the
configuration. For incoming messages, the accept_recipient option lists
the ACLs to apply to the arguments of RCPT commands. For example,
accept_recipient = local_acl : relay_acl
The colons in these lists are interpreted as `or'. In this example, the
recipient is accepted if either of the two ACLs accepts it. ACLs can
also be referred to from other ACLs. (There will a check to prevent
looping.)
---- end copy----
is likely to lead to confusion. In particular, having a : in one ACL place
mean 'and' and in another ACL place mean 'or' is going to confuse the
heck out of some people. Would it be that much more work to explicitly
spell out 'and' and 'or'? It's only between 1 and 4 more characters to
type :-) Alternately, how about the C style & and | for 'and' and 'or'.
Just my 2 cents from a small time user.
+---------------------------------------------------------------------+
Bruce Bowler +1.207.633.9600 BBowler@???
Everybody is ignorant, only on different subjects.
- Will Rogers
+---------------------------------------------------------------------+
