> Yes i have the reason for ur problem :) > > As per logs, policyd also set limit as you see limit=1, so after limit > will reached, over messages will be dropped. I hope u got it now. >
That is the ID of the limit, not the value. Regards Nigel > > On Tue, Jul 6, 2010 at 9:28 PM, Juan A Moyano <[email protected] > <mailto:[email protected]>> wrote: > > Hi there > > I'm trying to set quota to authenticated users. Just for testing I > fixed count limit to 3 messages, getting in log file in the > fourth mail delivery: > > [2010/07/06-13:21:29 - 8296] [CORE] INFO: module=Quotas, > mode=update, host=192.168.2.105, helo=[127.0.1.1], > from=...@xxxxxxx, to=...@xxxxxxx, reason=quota_update, policy=5, > quota=1, limit=1, track=SASLUsername:j...@xxxxxxx, > counter=MessageCount, quota=4/3 (132.4%) > > I don't understand why mode=update when message is already > overlimit ( 4/3 ) > > Any clues? >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
