Ofer Inbar wrote: > Yahoo told us that we were not anywhere close to sending them messages > too quickly, and we should be able to send more quickly, but it's just > a slower process to deliver to yahoo than to the other large ISPs, it > seems, so sending more messages at a time is apparently the solution. > > Settings for this yahoo-specific transport: > yahoo_destination_concurrency_limit = 500 > yahoo_connect_timeout = 5s > yahoo_data_done_timeout = 120s > yahoo_data_init_timeout = 60s > yahoo_helo_timeout = 120s > yahoo_mail_timeout = 120s > yahoo_quit_timeout = 120s > yahoo_rcpt_timeout = 120s > yahoo_rset_timeout = 120s > > I had previously tried testing by changing the concurrency limit from > 20 to 40 but that had a small effect, if any. A large change has a > dramatic effect.
I find this quite interesting. Based on the vague guidelines that Yahoo publishes, it sounds like they consider lots of concurrent connections to also be abusive. If you can really get away with such high concurrency it may well be worth trying out. You mentioned going from a couple of hundred messages per minute, to a few thousand per minute; are these mostly Yahoo addresses, or was mail to Yahoo just holding up the rest of the queue? I don't suppose you have any messages-per-minute figures for that yahoo-specific transport?
signature.asc
Description: OpenPGP digital signature
