On Fri, Nov 30, 2007 at 09:57:48AM +0100, Nicolas KOWALSKI wrote:
> On Thu, Nov 29, 2007 at 08:27:01PM -0500, Victor Duchovni wrote:
> > On Thu, Nov 29, 2007 at 05:12:39PM -0500, Victor Duchovni wrote:
> > > > With foo_destination_recipient_limit = $default (50), and
> > > > foo_destination_concurrency_limit = 1, I still see multiple
> > > > parallel deliveries to the same destination.
> > Back the OP's "problem", there are two reasons why his concurrency limit
> > is not effective:
> > - The transport setting is "cyrus" not "cyrus:dummy", so the concurrency
> > limit is per recipient domain, not global.
> > - The transport is a "mailbox_transport", so the queue manager is
> > not actually scheduling "cyrus" deliveries, rather the queue manager
> > is scheduling "local" deliveries (using the appropriate limits) and
> > "local" is forwarding delivery requests to "cyrus".
> Thanks for your explanations.
> > Serializing the "cyrus" deliveries is unwise in this context. Why is
> > it necessary?
> The script calls the Spamassassin client before delivering to Cyrus. SA
> can be really hungry on resources, but the server has really limited
> resources, and I saw it almost halt during minutes because of too many
> concurrent deliveries. Serializing at postfix level could help in this
Set a lower process limit for "local" not "cyrus", but "1" is likely
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
or click the link below:
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.