Re: [exim-dev] [Bug 2358] outbound ratelimit support
On Thu, 27 Dec 2018, admin--- via Exim-dev wrote: https://bugs.exim.org/show_bug.cgi?id=2358 --- Comment #2 from Jeremy Harris --- It depends how complex you want it; for the simplest case place this class of messages in an alternate named queue, set up the queue-runner to run M times per hour and have a queue_run_stop router triggering after n/M messages. Thanks. I understand the proposal now. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[exim-dev] [Bug 2358] outbound ratelimit support
https://bugs.exim.org/show_bug.cgi?id=2358 --- Comment #2 from Jeremy Harris --- It depends how complex you want it; for the simplest case place this class of messages in an alternate named queue, set up the queue-runner to run M times per hour and have a queue_run_stop router triggering after n/M messages. In case it wasn't clear, these are design ideas - not something that yet exists. -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[exim-dev] [Bug 2358] outbound ratelimit support
https://bugs.exim.org/show_bug.cgi?id=2358 Andrew Aitchison changed: What|Removed |Added CC||e...@aitchison.me.uk --- Comment #1 from Andrew Aitchison --- Is this supposed to share info between successive queue runs ? For an n-messages/second limit the queue-runner process can keep track, but for an n-messages/hour limit we need persistent counters; I guess that the retry database could be used to store this ? Is the rate controlled by the config file, or by parsing server responses ? -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
