Tony Finch wrote: > On Fri, 30 May 2008, Russell Wilton wrote: > >> What I want is a single ratelimit condition on a stanza in the >> smtp_data or predata ACL, after all the recipients have been >> input and verified, that will compare the current $sender_rate >> plus $recipients_count to the $sender_rate_limit and return >> false with no database update if it is over the limit. If it is >> under the limit, return true and update the database not by one, >> but by the $recipients_count value. This seems like the way it >> logically should work, but I haven't been able to find anything >> in the docs (40.35 - 40.39) to confirm that. >> > > Yes, you are right that this is an obvious missing feature from the > current code. I have attached a patch (which has not yet been properly > released) that allows you to do exactly what you want, amongst other > things. I'm afraid it's going to be a few weeks before I'll get back to > work on Exim and release a version with this enhancement. > > There's a general problem with trying to ratelimit MUA clients, in that > the user interface that MUAs provide for message submission problems is > not that great. Your proposed solution sounds like a pretty good > compromise to me. I have been thinking that the way to do it would be to > set a variable when a rate limit is exceeded that causes the affected > email to be quarantined, which you can do with the released code though > it's not as neat as your idea. > > Tony. > Thanks for the patch. It looks like you have done a major rewrite of the rate limiting code. I look forward to Ver 4.70.
Russ -- Russell D. Wilton E-Mail: wilton(at)uleth.ca Info Tech Systems Analyst Voice: (403) 329-2525 University of Lethbridge FAX: (403) 382-7108 4401 University Drive Lethbridge, Alberta, CANADA T1K 3M4 -- ## List details at http://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
