Nigel Kukard wrote: >Ok .... a message matches a policy. > >A policy can contain various specifiers, like [email protected], >@example.org, 192.168.0.0/24 or %group .... where %group is a group. > >Group members are matched a OR b OR c OR d, where a b c are members of >that group. > >Policy members are matched a AND b AND c AND d, where a b c d are >members of that policy. > >You then attach a feature to a policy, wither an ACL, greylisting or >maybe quotas.
Thanks, it's a bit clearer now - plus I've turned on the "detail logging" for policy and it now gives more clues about what it's doing. So it evaluates each policy, and creates a list of policies that have at least one member that matches. Then picks the highest priority policy, then executes each feature. This last step, does it execute them in turn until one say YES (with an inferred reject at the end), or until one says NO (with an inferred accept at the end), or something else ? Another question. Am I right in thinking that the Amavis test can't add any headers to the email ? IIRC I read somewhere that this is a limitation of the Postfix policy protocol. -- Simon Hobson Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed author Gladys Hobson. Novels - poetry - short stories - ideal as Christmas stocking fillers. Some available as e-books. _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
