Module 12 · Lesson 24 of 25

The five-minute diagnostic ritual

Part of Dovecot: IMAP/POP3 at Production Scale — Troubleshooting, Forensics & Common Errors.

Don't restart Dovecot first. Read first.

1. What's the user-visible symptom? "Can't log in", "messages disappeared", "slow"?

2. Check service status:

systemctl status dovecot
doveconf -n | head -50

3. Tail the right log with the user's pid:

tail -F /var/log/dovecot.log /var/log/dovecot-info.log | grep alice@example.com

4. Replay the failing operation while watching the log. Most issues print a clear error within 5 seconds.

5. Inspect mailbox state:

doveadm mailbox status -u alice@example.com all INBOX
doveadm fetch -u alice@example.com 'uid hdr.subject' mailbox INBOX last 5

doveadm is your Swiss Army knife — read its man page once and refer back forever.

Sign in to keep track of what you have read.

Pulse · self-hosted sending

Own the infrastructure your pipeline depends on.

One install script on your own server. Pulse sets up the MTA, mailboxes, certificates and dashboard; you add domains and start sending.

# on a fresh Ubuntu server
$ cd pulse && sudo ./install.sh
→ docker compose up · kumomta · stalwart · caddy
→ dashboard ready on https://pulse.yourdomain.com
$

Also from us:Beat — monitoring that tells you the fixConsulting — $65/hr, no retainer