Wietse Venema:
> There is a rough idea of how to enforce strict connection counts
> when connection caching is turned on. But it would not help in your
> case, where the number of competing domains is 100x the number of
> allowed concurrent connections. Under those conditions the feature
> would behave as if connection reuse is turned off.
An easier fix may be to change the scheduler and suspend round-robin
destination selection until a destination is blocked (concurrency
limit reached) or drained.
This would be less fair in the general case of mixed email flows,
but mass email is different enough that people can expect to need
some confguration for fastest delivery.
Wietse
