>> I just want to follow up. If quota's windows is behaved like my >> test(I could sent to 16 recipients in 5 minutes with a quota limit >> at 8 recipients), I know this far-fetched in real environment. How >> hard is to tweet the formula to block at exactly or close to the >> quota limit. > Why do you need an "exact" quota ?
Actually ... this is EXACT quota using a dynamic window ... the only way to make it more exact is much much bigger floating point numbers :D Fixed window quotas is imho alot less accurate ..... 10:55 => 11:00 , allow 10 mails .... that means you can send 10 mails at 10:59 and 10 again at 11:00. Thats 20 in a 2 minute period. > Doing anything other than the rate > based method used now is a lot harder and computationally more > expensive* - which gives a fair approximation over a period. If you > user tries to send messages continuously, then they will in fact be > throttled to a rate of approximately 8/300s - it's just that if they > have a gap, they can initially burst an additional 8 messages out > before the rate limiting cuts in. 2.0.11RC1 + Robert Anderson's patch should have no bugs and is extensively tested. If you having any problem with 2.0.10 I'd strongly suggest trying 2.0.11RC1 + patch. If you have any problems with that we'll investigate and fix in a priority fashion. I'm going to be releasing RC2 in the very near future, hearing people say "works, awesome" motivates :) -N
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
