Think it already handles that?
Check your queue summary. They may be in the scheduled queue
one sec
But it is very possible you got them all
Just a few messages for Gmail in the scheduled queue
Interesting, yeah. It looks like the kcli bounce worked fine?
And even deleted the messages from scheduled queue
Anwyay
Thanks Tom!
Appreciate the help
Maybe an idea for the future.
/opt/kumomta/sbin/kcli bounce --campaign u1 --reason 'felt like it' --duration 50s
Should all PAST messages and FUTURE messages for 50 seconds. I shouldn’t need to rebind the queue after. This should pretty much nuke all messages matching the criteria
Just setting the duration long will catch all future messages
Including what is in schedules
the bounce command operates primarily on the scheduled queue that matches the specified critiera. There are a couple of check points in/around the ready queue processing that also check for active bounces and will match and remove them from those flows.
A bounce is active for the duration specified so that it can apply both at the moment that you enable it, and for the specified duration afterwards, so that it can catch and apply to messages that are moving through other states in the system
So the bounce will affect current and future queued messages. A rebind is not necessary when bouncing, if you set a sufficiently large duration for the bounce.
And this is why I should not answer questions at midnight. Thank you for the correction Wez.
Thank you so much guys ![]()