DN Singh:
[ Charset UTF-8 unsupported, converting... ]
> On Sep 11, 2012 8:43 PM, "Wietse Venema" <wie...@porcupine.org> wrote:
> >
> > DN Singh:
> > > We some trouble with rediff deliveries, and therefore were trying this
> > > combination. While searching the archives, we found that rediff does not
> > > like connection caching, and about the recipient_limit option. The rate
> >
> > With recipient_limit=1, the Postfix scheduler will try to deliver
> > different recipents in parallel. The concurrency is limited only
> > by the process limit (in master.cf) for the message delivery
> > transport.
> >
> > You can set that process limit to 1, but that will not change how
> > the rate delay works. As before, it will enforce the delay between
> > deliveries for the same recipient.
> >
> > Wietse
> Will transport_destination_concurrency work in this case? I am asking
> because I had created this transport for the purpose of throttling.
With recipient_limit=1,
transport_destination_mumble controls the mumble for deliveries to
the same recipient. Different recipients are delivered in parallel
subject to the process limit in master.cf.
Wietse
