On Thu, Jan 29, 2009 at 07:32:57PM -0800, Jacky Chan wrote:

> Jan 30 11:16:36 mailgw1 postfix-slow/smtp[16362]: 6EB522EDD17:
> to=<jacky1128...@yahoo.com.hk>, relay=d.mx.mail.yahoo.com[66.196.82.7]:25,
> delay=214, delays=0.11/176/35/2.3, dsn=2.0.0, status=sent (250 ok dirdel 4/1)
>
> Jan 30 11:16:36 mailgw1 postfix/qmgr[16150]: qmgr_queue_unthrottle: queue
> yahoo.com.hk: limit 1 window 1 success 0 failure 0 fail_cohorts 0

So far, so good.

> Jan 30 11:22:23 mailgw1 postfix-slow/smtp[16498]: 78DBD2EDD1A:
> to=<jacky1128...@yahoo.com.hk>,
> relay=g.mx.mail.yahoo.com[206.190.53.191]:25, delay=560,
> delays=0.14/514/46/0, dsn=4.0.0, status=deferred
> (host g.mx.mail.yahoo.com[206.190.53.191] refused to talk to me:
> 421 Message from (161.64.2.15) temporarily deferred - 4.16.50.
> Please refer to http://help.yahoo.com/help/us/mail/defer/defer-06.html)
>
> Jan 30 11:22:23 mailgw1 postfix/qmgr[16150]: qmgr_queue_throttle: queue
> yahoo.com.hk: limit 1 window 0 success 0 failure 0 fail_cohorts 1

This queue got throttled. The value shown is not the limit, it is the
observed number of failed cohorts, the question is, why did the transport
get throttled...

> slow      unix  -       -       n       -       1       smtp
>         -o syslog_name=postfix-slow
>         -o smtp_helo_timeout=10
>         -o default_destination_concurrency_failed_cohort_limit=0

This is a queue manager setting, not a delivery agent setting, so no
point putting it in master.cf. Wrong variable also.

> or in main.cf
> slow_destination_concurrency_failed_cohort_limit = 0

This is what you should have in main.cf, however there is a bug
in either the implementation or the documentation and the queue manager
is looking for:

        slow_concurrency_failed_cohort_limit

    not

        slow_destination_concurrency_failed_cohort_limit

This applies also to

    <transport>_concurrency_positive_feedback
    <transport>_concurrency_negative_feedback

which are documented to be:

        <transport>_destination_concurrency_positive_feedback
        <transport>_concurrency_negative_feedback

but the "_destination" was left out of the implementation. Sorry about
that. Thanks for uncovering the bug. For now you can set both variables:

    # Temporary alias, to work around 2.5.5 scheduler parameter name bug
    slow_concurrency_failed_cohort_limit =
        $slow_destination_concurrency_failed_cohort_limit
    # Documented interface
    slow_destination_concurrency_failed_cohort_limit = 0

-- 
        Viktor.

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.

To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majord...@postfix.org?body=unsubscribe%20postfix-users>

If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.

Reply via email to