On 29/11/2013 21:20, Viktor Dukhovni wrote:
On Fri, Nov 29, 2013 at 12:40:03PM +0200, Birta Levente wrote:

I have special transport for slow destinations. As documented if
transport_destination_rate_delay>1s then applied for the same
domain.
There is no such documentation.  Setting it to "1s" is only different
from setting it to "2s" in the duration of the delay.

Read:

     http://www.postfix.org/postconf.5.html#default_destination_rate_delay

carefully, it talks about a "corresponding recipient limit > 1" not a
"rate delay > 1".
Aha. I get it now.

slow_initial_destination_concurrency=4
slow_destination_concurrency_limit=8
With rate delay > 0, these are always 1, no matter what you set them to.
Good to know. Where this is documented?



slow_destination_recipient_limit=10
slow_destination_rate_delay=2s
slow_destination_concurrency_failed_cohort_limit=100
The cohort limit should probably be closer to 10 than 100.  There's
no point wasting 100 delivery slots trying to connect to a dead
destination.

Can I achieve ex. 1s delay for the same domain? Or more fine tunning
ex. 1.5 sec?
You can set the delay to 1s.  Sub-second granularity is not currently
available.

Thanks for your help!



Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to