Mail Queue
The Mail Queue page is a window into Postfix's delivery queue: every message the server has accepted but not yet delivered, why it is waiting, and the tools to unstick it. When a customer says "my mail never arrived", this is where the answer usually is.
Email → Mail Queuehttps://YOUR-SERVER-IP:8443/email/queue| Queue ID | Sender | Recipients | Status | Actions |
|---|---|---|---|---|
4XkQ2r1jz9 | [email protected] | [email protected] | deferred connection timed out | view · hold · requeue · delete |
Reading the queue
Messages arrive in three states: active (being delivered right now), deferred (a delivery attempt failed and Postfix will retry on its backoff schedule; the failure reason is shown right under the status), and hold (parked by an administrator, untouched until released). Cards at the top count each state plus the queue's total size, the list auto-refreshes every 30 seconds (toggleable), and you can search and filter by state.
View opens the whole message: envelope facts, all headers in a table, and the body. HTML mail renders inside a sandboxed frame that cannot run scripts, so inspecting a suspicious message is safe (remote images may still load; scripts never run).
Acting on it
Per message: Hold parks it, Release frees a held message, Requeue asks Postfix to re-evaluate it immediately (useful after fixing the DNS or firewall problem that deferred it), and Delete discards it after a confirmation. Queue-wide: Flush attempts delivery of everything now, Delete Deferred clears only the failed backlog, and Delete All empties the queue, each behind its own confirmation, with the toast reporting how many messages were actually removed.
postqueue -p for the listing (parsed including hold and deferred markers and the per-message reason), postqueue -f for flush, postsuper -d / -r / -h / -H for delete, requeue, hold and release (with ALL and ALL deferred variants), and postcat -q for full message content. Nothing is mirrored into a database: what you see is Postfix's own live state.Access
Behind the email license feature and the local mail requirement, and by default a ROOT/ADMIN page. One thing to know that differs from most pages: the queue itself is not scoped per owner. It is the whole server's Postfix queue, so anyone allowed onto this page sees and can act on every message, not just their own. That is why it defaults to administrators; if you grant the page to another role from Page Permissions, understand that you are granting server-wide queue access. See roles and permissions. Queue operations are also exposed on the External API under server scopes.