From: Victor Duchovni (Victor.DuchovniMorganStanley.com)
Date: Wed Nov 21 2007 - 12:50:10 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Wed, Nov 21, 2007 at 06:44:55PM +0000, Keean Schupke wrote:

> Hi,
>
> > > > Good point about serialising the authentication requests... I have set
> > > > "default_destination_concurrency_limit" to one in my configuration.
> > >
> > > Is there only one destination from this system? Otherwise I would
> > > recommend a transport-specific setting, with just the broken destination
> > > routed to the serialized transport.
>
> Actually seems neater to just limit the concurrency of the smtp
> transport... no point in restricting things if unnecessarily.
>
> Is it possible to configure a per-transport setting based on the
> transport table then? for example:
>
> abc.com smtp:[broken-relay.com] concurrency(1)
> * smtp:[okay-relay.com]

See the "RESOURCE AND RATE CONTROLS" section of the smtp(8) manpage.
The parameter is actually enforced by the queue manager (which is obvious,
in the mathematical sense of "obvious", i.e. obvious to an expert).

--
        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:majordomopostfix.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.

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]