Of course the need for outbound rate limiting is not confined to sending to Gmail/G Suite recipients. For example we see problems when a group here has a fault with one of their software systems and it triggers umpteen emails to their alerts/support address. This is *not* hosted at Gmail/G Suite but the hosting service nevertheless employs rate limiting of incoming messages.
So despite being a profound advocate of Exim, it is a little embarrassing to tell people who ask me about outbound rate limiting that it's so difficult in it, but simple in other MTAs. But I guess it stems from a design decision made early on and hence is difficult to address. Mike B. On 28 February 2018 at 09:59, Jeremy Harris via Exim-users < [email protected]> wrote: > On 28/02/18 09:33, Jasen Betts via Exim-users wrote: > > there may be better solutions but this is the easiest. > > I've put a skeleton description on > https://github.com/Exim/exim/wiki/RatelimitOutbound > > Filling out the detail will required perusing of multiple > separate parts of the manual. (Translation: I haven't > the time or the interest. Dump Gmail.) > -- > Jeremy > > -- > ## List details at https://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/ > -- Systems Administrator & Change Manager IT Services, University of York, Heslington, York YO10 5DD, UK Tel: +44-(0)1904-323811 Web: www.york.ac.uk/it-services Disclaimer: www.york.ac.uk/docs/disclaimer/email.htm -- ## List details at https://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/
