vi...@vheuser.com:
> On 2020/06/16 13:42 PM, Wietse Venema wrote:
> > vi...@vheuser.com:
> >> Obviously I am above my pay grade here,
> >> but can this? "Adding some artificial 'cost' value" currently be done?
> > No. There is an existing solution that works for multi-recipient
> > list mail. That solution does not work for single-recipient list mail,
> > which we suspect is your use case.
> >
> > Viktor proposes to schedule single-recipient list mail from the
> > same sender as if it is multi-recipient list mail (post-facto grouping).
> >
> > I'm proposing to just put a cost on each delivery request, initially
> > based on how many other requests a sender already has in flight,
> > that decays over time until the request is selected for delivery.
> > This guarantees that all mail will eventually be delivered.
> >
> > This also would give us the option to make the scheduling dependent
> > on message size, or quality-of-service indicators.
> >
> > Wietse
> Just fyi -
> Mailman domain concurrency is a yes/no/full option.
> I've limited postfix to 5 and set Mailman to yes
> and that sped things up dramatically
> with no rejections from TWC.
Perhaps you set some Postfix xxx_destination_recipient_limit=1. As
documented that makes the Postfix concurrency limit a per-recipient
property, which increases the total concurrency for a destinaion domain.
Wietse
