> I realize that by setting initial_destination_concurrency to 1 it's on > a per-domain basis, which is what I believe I need.
That is not what the documentation says. First, it is a different
parameter name that causes the switch in concurrency scheduling,
and second, the behavior is the exact opposite of what you say.
With a per-destination recipient limit of 1, the concurrency
limit is per-recipient instead of per domain.
Wietse
