On Thu, Mar 05, 2009 at 12:20:06PM +0100, Santiago Romero wrote:
> Well, I'm using postfix's ubuntu package, so it's not compiled from source
> code because I need all my ~=100 Linux machines to be easily updatable
> (apt-get update && apt-get upgrade).
>
> In this case, I'm going to recompile .deb source package including your
> patch to see if that solves the problem ...
>
> Please, allow me a couple of days to recompile / install it (it's a
> production system, I need to find a working window with customers). I'll
> inform you in this list if the problem happens again or if the patch seemed
> to fix the problem. Do you want any kind of aditional change / logging /
> config to make the "problem" more easy to happen?
Please wait for an updated patch, we believe we have identified the
cause and reproduced the symptoms (in that order). I have a candidate
patch, but I expect Wietse will send an updated more polished version
in the not too distant future.
The issue found applies only to "rate-limited" transports, if you are
not using such transports, you don't need the patch. The patch ensures
that work done at the completion of a delivery with a "normal" transport
is correctly split between "before suspend" and "after resume".
The original 2.5.x code is correct for "oqmgr", but not for "qmgr"
(aka "nqmgr"), which requires additional internal state adjustments
when destinations are blocked and unblocked.
--
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.
