I've added a gmail.com-specific transport, with a recipient_limit set to 2 (so it does not become per-recipient instead of per-domain), a concurrency limit of 1 and a 10s rate delay. For the amount of email we send this should not be problematic. I'll see if we can then build up a better rep for his domain.
Some good comments here from everyone - thanks all. Simon On Sunday, December 31, 2023 07:30 AEST, Michael Orlitzky via mailop <mailop@mailop.org> wrote: On Sat, 2023-12-30 at 12:48 -0800, Randolf Richardson, Postmaster via mailop wrote: > If that's what the problem is, then that can easily be set with the > following Postfix setting without the need for customization scripts: > > default_destination_recipient_limit = 1 > > It may also be helpful to adjust the delivery rate, which can also > be set in Postfix's "default_destination_rate_delay" setting This will work, but you probably don't want to make your entire MTA inefficient just to appease Google. Those two parameters have per- transport counterparts, * <transport>_destination_concurrency_limit * <transport>_destination_rate_delay where <transport> is the name of your transport. So, for example, you could create a transport called "slow", and then set * slow_destination_concurrency_limit = 1 * slow_destination_rate_delay = 2s after which all you have to do is configure postfix to send to gmail via the "slow" transport instead of the default one. Now gmail is slow, but nobody else suffers. _______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop -- Simon Wilson M: 0400 121 116
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
