On Wed, Jun 15, 2022 at 10:00:45PM -0600, Bob Proulx wrote:
> But did I get it right?
>
> In master.cf:
>
> gmail unix - - y - - smtp
> -o gmail_destination_concurrency_limit=2
> -o gmail_destination_rate_delay=1s
> -o gmail_destination_recipient_limit=2
No, those settings are used by the queue manager to schedule deliveries
assigned to various delivery agent processes, the delivery agents
themselves only see one message at a time and can do little to affect
concurrency, and related limits.
So these settings go in main.cf:
gmail_destination_concurrency_limit = 2
gmail_destination_rate_delay = 1s
gmail_destination_recipient_limit = 2
> In transport:
>
> gmail.com gmail:
Sure, but the trailing ":" is unnecessary.
> Second is that I have three messages still in the mail queue that list
> 50 recipients all at Google. Is there a way to have Postfix reprocess
> the message and split the delivery up so that it will use the new
> transport rather than the previous?
The recipient limit to a remote destination is *at most* the count
of message recipients, but the queue manager "splits the envelope"
as needed.
> postsuper -r ALL # no effect
Also no need.
> I tried the above but obviously that did not cause Postfix to
> reprocess the message and then use the new transport. Is there a way
> to have Postfix reprocess to use the new transport rules?
No need.
--
Viktor.
