Re: destination_concurrency_limit not respected ?

2 msg	2 postfix server on the same domain in differen...
3 msg	mailer-deamon sends error messages to: question
3 msg	Procmail
15 msg	MAIL FROM timeout with ciphers=high
2 msg	milter, broken pipe
17 msg	How to listen on 587 as well as 25?
6 msg	reject_sender_login_mismatch doesnt work
2 msg	smtp auth
4 msg	Postfix with MYSQL compile error
8 msg	mynetworks=<empty> vs mynetworks=<defa...
3 msg	message_size_limit with ldap search parameter
2 msg	Pipe debugging

destination_concurrency_limit not respected ?
\ Nicolas KOWALSKI (29 Nov 2007)
. \ (Wietse Venema) (29 Nov 2007)
. . \ Nicolas KOWALSKI (29 Nov 2007)
. . . \ (Wietse Venema) (29 Nov 2007)
. . . . \ Nicolas KOWALSKI (29 Nov 2007)
. . . . . \ (Wietse Venema) (29 Nov 2007)
. . . . . . \ Nicolas KOWALSKI (29 Nov 2007)
. . \ Michael Tokarev (29 Nov 2007)
. . . \ Victor Duchovni (29 Nov 2007)
. . . . \ Victor Duchovni (30 Nov 2007)
. . . . . \ Nicolas KOWALSKI (30 Nov 2007)
. . . . . . \ Victor Duchovni (30 Nov 2007)

13 msg	Virtual spam forwarding issues
2 msg	cleaning up deferred queue
2 msg	static nexthop per domain
2 msg	Simple postmap question
9 msg	Issues with Recipient_Canonical mapping
3 msg	Mail server reboot after got flood
3 msg	can't create a virtual domain

Subject:	Re: destination_concurrency_limit not respected ?
Group:	Postfix-users
From:	Victor Duchovni
Date:	30 Nov 2007

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
> case.

Set a lower process limit for "local" not "cyrus", but "1" is likely
too low.

--
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:majordomo?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.