@lbutlr:
> On 2018-03-16 (05:10 MDT), Wietse Venema <wie...@porcupine.org> wrote:
> >=20
> > @lbutlr:
> >>=20
> >> This could be done with a queue scheduler that pre-processes the =
> queue when "a lot" of messages get queued for sending and then sorts =
> them based on destination and the destinations that exceed some =
> pre-defined threshold get shunted to a separate process.
> >=20
> > Currently, the Postfix scheduler will read all your 1000 recipients =
> from the queue (the read limit is 20000). Currently, Postfix will =
> deliver all your 400 to gmail.com AND AT THE SAME TIME deliver 600 to =
> other destinations.
> >=20
> > With your proposal, Postfix will deliver 400 to gmail.com (leaving =
> many Postfix delivery agents unused) and ignore those 600 until the 400 =
> are delivered. That would be a regression.
>
> That's certainly not what I meant by "a separate process".
I hope you did not mean 'one' process, becasue that would be slow.
Perhaps something that is more similar to creating a temporary
master.cf transport, with a limited collection of delivery agents.
Wietse
> Anyway, it's not a feature I need/want/care about, I was just suggesting =
> a way I thought it *could* be made to work.
>
>
> --=20
> Because you liked "The Very Hungry Caterpillar" may we suggest "The=20
> Human Centipede"?
>
>
