On 06/21/2010 11:31 AM, Victor Duchovni wrote:
On Mon, Jun 21, 2010 at 11:08:04AM -0700, Florin Andrei wrote:
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
With a rate delay of 1s, the positive/negative feedback parameters
have no effect. Also the concurrency limit has no effect. Only the
failed_cohort_limit is relevant. If you remove the rate delay, and your
mail stream to Yahoo is not too bursty (not jumbo list mails), then
the feedback controls should suffice to keep mail flowing smoothly. If
you need to spread out bursts from large lists that arrive all at once,
rate delay plus higher cohort limits are the only tools at hand.
My email is very "bursty" - event updates and changes sent to many /
most / all subscribers. So then I should do this, I guess:
yahoo_destination_concurrency_failed_cohort_limit = 20
yahoo_destination_rate_delay = 1s
I think that's exactly what you are suggesting. Hopefully Yahoo doesn't
get annoyed by the high cohort limit, but we'll see.
I can't say I understand *why* the 1s rate delay makes the feedback and
the concurrency limit parameters irrelevant, so I guess it's time for me
to dig deeper into the documentation. :)
--
Florin Andrei
http://florin.myip.org/
