Allow for expansion of rule hash in queue summary

[tommairs]

When running the kcli queue-summary (https://docs.kumomta.com/reference/kcli/queue-summary/), it is handy to see the details, especially when a queue is suspended:

/opt/kumomta/sbin/kcli queue-summary
SITE                              SOURCE      PROTO                                      D T C Q                                                                                                                                      
utils.kumomta.com                 demo        smtp_client                                0 2 0 0 🛑suspend: automation rule: Messages from you are suspended (rule_hash=demo->utils.kumomta.com@smtp_client-3b14917094308e4e531952b91422b795108856db45ae9d29b052c80a2c652573)
http://127.0.0.1:8008.tsa.kumomta unspecified lua:make.http://127.0.0.1:8008.tsa.kumomta 1 0 0 0                                                                                                                                      

SCHEDULED QUEUE                                                         COUNT
[email protected]!smartsink.kumomta.com         0

But the rule that tripped the suspension is a hash that is not easy to identify.

(rule_hash=demo->utils.kumomta.com@smtp_client-3b14917094308e4e531952b91422b795108856db45ae9d29b052c80a2c652573)

Is it possible to make that hash resolve to a specific rule?
Is it possible to put that hash into some tool that could point to exactly which rule caused it?

[wez]

The rule hash is present so that the code that synchronizes the state from TSA can avoid making a duplicate entry. It is a hash, which means that it is not a reversible operation.

I think that what we should do here is expand the interface to the TSA daemon so that you can review which rules are active in TSA. That will play together with also allowing manipulation of the TSA state (eg: cancel, or otherwise clearing the state).