Debugging Friendlier Stalwart

It is practically impossible to debug stalwart. We have problems, the database is blobs, no way to check and verify settings, no way (AFAIK) to i.e. check where the stalwart-set but “mailbox does not exist” e-Mail may be somewhere blocked by an orphaned information. After more than a week, we are unable to resolve the issue. Incl. having removed both related accounts for the user, creating them fresh with all “Actions” done, plus restart stalwart, plus restart system in between, just to avoid all PEBKAS. Then reinstall. Same procedure. Still, stalwart shows the mail, either as two mail accounts or as planned as main mail plus alias. I’m truly about to reinstall good old postfix/dovecot team, at least that allows debugging and we never had such problems as stalwart confronts us with.

The problem is in another thread. My call is to dramatically improve ability to debug locally. This is becoming a killer problem. And no, I do not want to fallback. But if I can’t get our project manager’s alternate mail to run by the weekend, I have a weekend of unplanned work ahead of me.

I have to echo this view… but then… I’ve been using ClaudeCode to debug assist by pumping the logs to ClaudeCode

Perhaps debugging MCP 0_o

Also part of this issue is the lack of partial text search in user and domain lists. ie. that “mailbox not existing” it most probably is a mistypo, but trying to find the typo would be much easir in a 600+ user list in the webui when a partial text search could be done, as now I need to drop to CLI again… not the ideal when you have call-centre type agents that wants to use cPanel ;(

Stalwart emits structured logs, so generally using journalctl -u stalwart.service -o verbose will give you a wider picture for what’s going on.