/opt/kumomta/sbin/kcli trace-smtp-server doesn’t show anything coming in. so is it picking it backup from a directory somewhere?
if you look in the journal, is it telling you that it is still enumerating the spool?
yup, that’s it exactly
so maybe I was mistaken: the queue was (relatively empty) but I needed to… empty the spool? or prevent it from being pulled into kumomta?
I’m surprised how slow it is going. 7/s
looks like I should maybe just delete the RocksDB spool directory
if you don’t want to log anything and want to nuke the spool fast, yeah, stop kumod then remove the contents of the spool rm rm -rf /var/spool/kumomta/.*
Don’t delete the spool directory itself, because it has special permissions for kumod and restoring those is an extra complication
perfect, thank you. that’s what I was researching (the “correct” way to delete the spool)
hmm. so when I do that rm -rf /var/spool/kumomta/.*
it tells me rm: refusing to remove '.' or '..' directory: skipping '.'
now I know that’s more of a linux issue, but my question is
can I just nuke everything in /var/spool/kumomta or do I need to leave the folder structure too?
you can nuke the contents of that dir
thank you 