Milter-greylist

Sliding count would be nice and for this we could reuse the existing
database of tuples so no heavy extra effort should be necessary.
The only problem is, that normally those whitelisted tuples are not
stored so implementing this would mean more memory hungry milter-greylist...
Ondrej
Emmanuel Dreyfus wrote:
>
> On Thu, Feb 12, 2009 at 10:02:52AM +0100, Jorge Garc�a Oncins wrote:
> > The syntax in greylist.conf could be something like this:
> >
> > # Each "normal-user" can only send e-mails to 1000 destinations each day
> > # and the sum of all the messages cannot be over 500MB
> > racl greylist from list "normal-user" accounting period 24h
> > message-count-limit 1000 message-size-limit 500MB msg "Daily limit
> > exceeded"
>
> What about defining the accounting rules at the beginning of the config
> file and reuse them later?
>
> # accounting "<rule name>" "<key>" (msgsize|msgcount) <limit> <duration>
> accounting 'usracct" "%f" msgsize >= 300MB 24h
> (...)
> racl blacklist list "users" accounting "usracct" msg "too many messages"
>
> Here we would maintain a size count of messages for each sender (%f).
> The use of a format string enable accounting against whatever you want
> (IP, sendr, receiver...).
>
> Problem: do we just reset counters every <duration> (here, 24h)? Or do
> we try a sliding count? That would be much heavier to implement.
>
> -- 
> Emmanuel Dreyfus
> manu@... <mailto:manu%40netbsd.org>
>
>