On 06/19/2010 05:37 AM, Wietse Venema wrote:
Stefan Foerster:
I don't send any large volumes to Yahoo, but I had to use a dedicated
transport which ignored much more errors for a popular German freemail
provider. Since you are using rate delays, your concurrency limit will
basically be one, and this might very well be related to what you see.
This is a good point.
To compensate for this unwanted side effect of reduced concurrency
INCREASE the fragile_destination_concurrency_failed_cohort_limit
to 10-20 or so (or REDUCE fragile_destination_concurrency_negative_feedback
to 1/10 or 1/20).
What happens if both are used with more moderate values?
E.g., I separated a few big destinations into their own delivery paths
and now this is what I have:
yahoo_destination_concurrency_limit = 4
yahoo_destination_concurrency_failed_cohort_limit = 5
yahoo_destination_rate_delay = 1s
yahoo_destination_concurrency_positive_feedback = 1/3
yahoo_destination_concurrency_negative_feedback = 1/8
I'll have another batch of emails to send pretty soon, I'm still
tweaking parameters until then.
--
Florin Andrei
http://florin.myip.org/
