Bug ID: 2358
Summary: outbound ratelimit support
Component: Delivery in general
Ideas to help with assembling an outbound ratelimit solution :-
- Variable counting queue-runner message delivery attempts. This would be
maintained by the queue_run() loop and available to the subprocesses running
- New router type "queue_run_stop" (actual name TBD) which forces that action
when triggered. This will require passing back that info from delivery
to queue-runner process; we have an existing pipe though it it currently not
used for any data (only the closure condition, for all-children dead).
Example usage triggers on the above variable exceeding some batch size.
Preferably the message being handled would be released without being marked
as having been tried, so that a retry time would not be enforced on it.
- Variable counting queue-runner message delivery attempts resulting in defer.
Requires additional info passed back as above. Usage would be to halt a
batch early if the destination is rate-limiting input, via the router as
above. Query: do we need to distinguish host- from message- from recipient-
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/ ##