>>> You do not want a policy to be instantly activated on a system processing >>> 100+ mails per second. It defaults to disabled so you can set it up, >>> attach groups, members, whatever, configure the modules, then activate it. >> >> >> Is there some kinda config option to fix this as well then...Seems that if >> I have the default quota set, and also a specific quota set for a user. its >> tracking that user in the "default" quota as well as the specific user's >> quota, causing the email to get blocked if the default limit is ever >> reached regardless of the user's specifc quota. Am i missing something >> here? > > Thats correct, you have two policies, both match. > > I may not be thinking straight (long day), but if you put the email addies > you want to override the quota for into groups, then exclude these groups > from the default one. > > Another option may be is to add a flag to the quota, indicating that if > another quota is matched it shouldn't match, it would then just have to be at > the end of the priority list. > > Let me know if you come right or have difficulties.
Tried setting up 2 diffrent policies, one for the "catch all" for all users and one for users that have specific quotas set. Set the priority for the catch all to 20 and the specific users one to 10. Still seems to be doing both. Now it seems to do them in the correct order .. user quota then all users but its still doing both... Is there some way to tell it if it matches the first policy then to not move on to the next policy? -- Jordan Tardif DreamHost _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
