* Florin Andrei <flo...@andrei.myip.org>: > Looking at the Postfix queue graphs in Munin, one thing I noticed is > that when the scheduled emails go out (it's not a continuous > trickle, it's in batches, that's just how the software works), a > fraction, maybe 25%, go into the active queue right away, the rest > seem to be dropped into deferred either immediately or very quickly. > Then they stay in deferred a long time. Then they move to active for > a short while, being delivered at a slow rate, then they fall back > into deferred.
I might be wrong here, but what you describe - "the rest seem to be dropped into deferred either immediately or very quickly" - sounds a little like the "use case" described in http://www.postfix.org/QSHAPE_README.html#backlog The deferrals on Yahoo's part might cause qmgr(8) to mark that destinations as "dead" (so we can't know that for sure, since you didn't post the rejection logs, and the _destination_concurrency_failed_cohort_limit only applies to connection and handshake failures). 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. I don't know if you need to reload postfix and/or requeue the messages with "postsuper -r" after changing transport_destination_concurrency_failed_cohort_limit. Stefan
