|
Now things are clear! The fact that priorities are not working as they should is what was confusing a bit of assembly rules. I think this may be viewed as a system bug that priorities have lost a little sense if we imagine not working or at least had a warning about how the priorities work in their documentation. Simon Hobson escreveu: Nixon Girard - Metaweb Host Center wrote:I appreciate your help but your explanation was a bit confusing to meYou mean I should not use $ * in the States and specify each user groups Ex: Default outbound Members: $ <mailto:[email protected]>[email protected] | $ <mailto:[email protected]>[email protected] and policies "high volume" Members: $ <mailto:[email protected]>[email protected]No, but I'll need to refer to the system at work, so it might a day or two before I can get back to you with more precise details. I'll try and clarify. I have a group (lets call it "large volume"), with members like [email protected] and [email protected] I have a policy, with membership criteria of "is member of 'large volume'" - and you apply the rules to allow them to be heavy mail senders. Then I have a policy with membership of : SASL $* ! member of 'large volume' ie two membership criteria. Thus whilst [email protected] matches the SASL criteria for the second policy, it doesn't match (note the "!") the second element and so the policy isn't matched. IIRC, mail quotas don't work as you'd hope - instead of inheriting from higher priority policies but applying the different quotas, if a client matches two policies, then both quotas are applied. |
_______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
