On 9/3/2012 10:43 AM, Viktor Dukhovni wrote: > On Sun, Sep 02, 2012 at 08:07:21PM -0700, Joey Prestia wrote: > >> yahoo_destination_concurrency_limit = 20 > > This setting is trumpted by the setting below: > >> yahoo_destination_rate_delay = 1s > > You have serialized deliveries to Yahoo, they happen one at a time. > Given that each delivery takes ~5s, there is not much point in > doing that, you can instead set a low concurrency, and get a bunch > more throughput by not setting an explicit rate limit. (perhaps > 2 deliveries per second with a concurrency of 10, rather than 1 > delivery every 5 seconds).
So what I would need then is in main.cf and in master.cf in my transport would be this? yahoo_destination_concurrency_limit = 10 -o smtp_connection_cache_on_demand=no > > For more throughput, you need more IP addresses, perhaps even in > distint address blocks, ... > > Sadly, Yahoo discriminates the Postfix connection cache which limits > connection re-use by time rather than delivery count. Limiting by > delivery count behaves poorly when one or more of the MX hosts for > a site is slower than the rest, it becomes a connection "attractor", > so Postfix uses a better strategy. > I thought we were making good use of our connection caching? > You can just disable connection caching with Yahoo, they rarely > have unreachable MX hosts, your deliveries are just as slow whether > connections are cached or not. >
