I've now redirected one of my list servers to my new mail host - but I've hit a problem with policy matching.
In the mail log, I'm seeing : cbpolicyd[2409]: module=Quotas, action=defer, ..., reason=quota_match, policy=6, quota=3, limit=11, track=xxx, counter=MessageCumulativeSize, quota=0/10000000 (0.0%) That seem to be saying it's applied the quota for policy ID 6 and it's (correctly) failed - the quota on that policy is insufficient for the volume of mail from that list server. When I look in cbpolicyd.log, I see (amongst all the other stuff) : DEBUG: END RESULT: prio=0 => policy ids: 1 DEBUG: END RESULT: prio=50 => policy ids: 6 DEBUG: END RESULT: prio=55 => policy ids: 9 DEBUG: END RESULT: prio=60 => policy ids: 7 Now that tells me that the message matched two higher priority policies - and both of those have quotas defined which would allow the volume of messages. NOw, having left it over an hour (I was in a meeting) so the quotas are reset, and then flush the queue on the list server, I see in the mail log : module=Quotas, mode=update, ..., reason=quota_update, policy=1, quota=4, limit=5, track=SenderIP:xxx0/24, counter=MessageCount, quota=4/600 (0.7%) module=Quotas, mode=update, ..., reason=quota_update, policy=1, quota=4, limit=6, track=SenderIP:xxx/24, counter=MessageCumulativeSize, quota=0/26214400 (0.0%) module=Quotas, mode=update, ..., reason=quota_update, policy=6, quota=3, limit=4, track=SASLUsername:xxx, counter=MessageCount, quota=4/10 (44.4%) module=Quotas, mode=update, ..., reason=quota_update, policy=6, quota=3, limit=11, track=SASLUsername:xxx, counter=MessageCumulativeSize, quota=0/10000000 (0.0%) module=Quotas, mode=update, ..., reason=quota_update, policy=9, quota=7, limit=9, track=SASLUsername:xxx, counter=MessageCount, quota=4/60 (7.4%) module=Quotas, mode=update, ..., reason=quota_update, policy=9, quota=7, limit=12, track=SASLUsername:xxx, counter=MessageCumulativeSize, quota=0/100000000 (0.0%) module=Quotas, mode=update, ..., reason=quota_update, policy=7, quota=5, limit=7, track=SASLUsername:xxx, counter=MessageCount, quota=4/3600 (0.1%) module=Quotas, mode=update, ..., reason=quota_update, policy=7, quota=5, limit=10, track=SASLUsername:xxx, counter=MessageCumulativeSize, quota=0/10000000 (0.0%) So it appears to be matching the right policies, updating the right quota trackings, but then it's applying the wrong limit. Can anyone tell me why the messages are getting deferred by policy 6, limit 11, when they should be getting allowed by the higher priority policy 7 and limit 7/10 ? -- 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
