On 9/16/22 10:49, Dan Caballero wrote:
We're seeing some messages having the .bak files in the out queue for up to 30, 40 or even 60 minutes. I've increased the number of in and out runners to 8 each. Is there a way to know which runner has which message?
If the .bak files eventually go away, this is because the message has a large number of recipients and delivery to the MTA is slow.
For the out runner, look in Mailman's smtp.log for messages of the form:
<message-id> smtp to <list> for nn recips, completed in tt.ttt seconds
to see how long it's taking. If it seems too long (even with full VERP, it should be at least 5 to 10 recips per second), there are things you can do in the MTA to speed processing. In particular, don't do recipient validation at incoming smtp time - possibly configure an alternate submission port for Mailman to use.
It shouldn't be necessary to slice the in runner and it processes very quickly.
To answer your question, queue entries have a name of the form <timestamp>+<hex hash> with a .pck or .bak extension. The entry is assigned to a particular runner based on the first bits of the hash. For 8 slices this is the first 3 bits of the hash, so if the first hex digit of the hash is 0 or 1, that out queue entry will be processed by the out:0:8 runner; if it's 2 or 3, that out queue entry will be processed by the out:1:8 runner and so on through e or f processed by the out:7:8 runner.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan