> On 24 Jun 2020, at 01:29, Wietse Venema <wie...@porcupine.org> wrote: > > Problem: nqmgr's fairness breaks down for single-recipient bulk mail
You describe the solutions but maybe you could describe the problem first? > Alternative 2: multiple mostly independent scheduling classes > ... > Other benefits: we can choose the class based on other properties, > for example message size, or both size and number of pending delivery > requests per sender, or something else. It seems unlikely that we > will need more than three classes: small, medium, large. Ah, the classes. I remember we have talked about something like this in the past, many years ago. I have spent several weeks of that summer figuring out the proper way of doing this, but when it came to implementation, I have decided I won’t push this forward and put the whole thing on hold. I don’t remember any of it now but maybe I wrote the most important ideas somewhere, so I can have a look. Patrik
