Could someone please explain how the policy stacking mechanism is > supposed to be configured? In other words, how can I designate that (1) all > applicable policies dictate a limit, and (2) a particular policy > overrides an other policies, even if the other ones are exceed? Or am I > reading too much into the current configuration options? Or do you have > to define a specific exclusion group and include it as one of the groups > in the earlier policy definition so it isn't processed until higher up > the chain (such as giving a user more quota than anyone else on a > specific machine)? >
Well, if the first policy is linked to a limit which rejects mail once exceeded its going to get rejected if its matched, or if both it and your more permissive limit is matched as it would be first. If you only want to match the second policy and use the limit attached to it, then your below exclusion list is the way to go. -N > So a rule with value 10 might be: %Mydomain,!%ExceptedUsers > and a rule with value 20 might be: %ExceptedUsers > > where MyDomain is @mydomain.com and ExceptedUsers might include > [email protected] and [email protected] ?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
