On Tue, Apr 14, 2015 at 1:43 PM, Wietse Venema <wie...@porcupine.org> wrote:
> Andrew Noonan:
>> a delivery problem, nor a Postfix or system capacity problem. I tried
>> turning some knobs with concurrency, but never saw postfix spin up
>> smtp processes to max out those settings. I'm quite certain that the
>> problem here is my config, but I'm not sure how to proceed.
> ...
>> default_destination_concurrency_limit = 20
>
> That is main.cf
>
>> yahoo unix - - n - 25 smtp
>> -o smtp_connection_cache_time_limit=15
>> -o smtp_destination_concurrency_limit=30
>> gmail unix - - n - 50 smtp
>> -o smtp_connection_cache_time_limit=15
>> -o smtp_destination_concurrency_limit=100
>
> As documented, the _destination_concurrency_limit parameters are
> implemented by the QUEUE MANAGER. Therefore setting them with the
> SMTP client programs has no effect.
>
> Wietse
I suspect that this is the root of the problem. As Viktor kindly
pointed out, there are probably other things that should be tweaked,
but as this was pretty much all a/b delay, and not c/d delay. I'll
probably walk the concurrency value (in the right file) up a little
from a default of 20 and make sure that Google doesn't get mad with
me. Is it considered good form to report back, or is that list spam?
