On Thu, Jan 17, 2013 at 1:03 PM, Wietse Venema <wie...@porcupine.org> wrote:
> Steve Jenkins: > > yahoo_destination_concurrency_limit = 4 > > yahoo_destination_recipient_limit = 2 > > yahoo_destination_rate_delay = 1s > > As documented, rate_delay enforces a delay BETWEEN deliveries to > the same destination, and therefore, the concurrency to that > destination is always 1. I see no way to enforce delays BETWEEN > simultaneous deliveries to the same destination. > Thanks for clearing that up. So I can tinker with destination concurrency OR rate delay, but not both. So now I suppose my follow-up question is what's more likely to keep the big MTAs happier? Delays between individual deliveries or limited concurrency? > The documentation also has a warning concerning per-destination > recipient limit (the concept of destination depends on the recipient > limit). Different destinations are delivered in parallel. > I read that warning, but wasn't sure I understood it properly. I know that setting destination recipient limit to anything above one defines a "destination" as a domain, so by setting it to 2 we're saying "wait 1s between every delivery to a Yahoo domain," right? And if every message sent is unique, would that mean there'd be no difference between a setting of 2 and the default of 50 in this case?
