Re: [exim] Fwd: Rate-limit queue-processing per domain

Top Page
Delete this message
Reply to this message
Author: Jeremy Harris
Date:  
To: exim-users
Subject: Re: [exim] Fwd: Rate-limit queue-processing per domain
I don't need duplicate individual mail to those on the ML.
Please don't.

On 18/10/17 17:51, Charlie Elgholm wrote:
> 2017-10-18 16:41 GMT+02:00 Jeremy Harris <jgh@???>:
>> On 18/10/17 11:42, Charlie Elgholm wrote:
>>> Is there some way to have Exim rate-limit the queue runners, so they only
>>> process - let's say 10 messages per minute - for a domain (like
>>> outlook.com/live.com) - _regardless_ of how the message was put in the
>>> queue.
>>
>> No. The queue-runners just don't do that.
>>
>> You'd need to DIY; something like "take the first 10 id's from the
>> spooldir, once a minute, and run 'exim -M'". Possibly using
>> a named-spool for each class of such mails you wanted to keep separate.
>
> Ok, that's sad.
>
> The infrastructure for it all is already on the code base:
> 1. There's something returning true/false if a mail should be
> processed in the queue (since frozen-messages is skipped).
> 2. There's a rate-limit command already, highly configurable.
> 3. There's a "rule-system" (executed for the ACLs).


You could certainly have a redirect router first in the
chain rigged to expand ::defer:: for anything after the
first few items. With current released Exim.

But you'd still be pointlessly doing this for all of the
spool that you weren't going to deliver. Hardly efficient.


(And if the big providers don't trust you, it's likely
because you have not built up a good reputation with them yet)
--
Jeremy