Postfix queue keeps growing: many deferred messages (postqueue -p, flush, find the reason)
Mail piles up in the deferred queue because deliveries keep failing temporarily.
Postfix deferred queue growingpostqueue -p thousands of messages deferred(delivery temporarily suspended: connect to ...: Connection timed out)mailq shows many deferred emailsPostfix queue full of deferred mail Meaning
Read the reason on each deferred message (postqueue -p, postcat -q ID, mail.log): connection timed out, DNS, blocked port 25, greylisting, remote 4xx. Fix the cause, then postqueue -f to retry. Use postsuper -d ALL deferred only for spam floods. Limit concurrency and set sensible lifetimes.
Common causes
- Outbound port 25 blocked
- DNS resolver failing
- Remote server rejecting with 4xx (greylist/rate limit)
- Compromised account flooding the queue
- Disk/IO problems
⚡ Quick fix
postqueue -p | headand read the deferral reasons- Fix DNS/firewall/reputation, then
postqueue -f - Remove spam:
postsuper -d ALL deferred
Detailed fix by platform
Shell
- bash
postqueue -p | tail -5 mailq | grep -c "^[A-F0-9]" sudo postqueue -f
How to diagnose
- Reason — Which?
- Size — Growing?
- Source — Spam?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 4.4.7 554 4.4.7 Message expired: unable to deliver in 840 minutes (delivery timeout)
- Exim retry Exim: retry time not reached for any host (message deferred, previous failure still in the retry window)
- frozen Exim: message is frozen — recipient or sender can't be bounced (frozen bounce messages pile up)
Most viewed in Email / SMTP
- 550 5.7.1 550 5.7.1 Relaying denied / Message rejected as spam / Unauthenticated email not accepted
- Laravel: Connection could not be established with host Laravel: Symfony\Component\Mailer\Exception\TransportException: Connection could not be established with host "smtp.mailtrap.io:2525": stream_socket_client(): Unable to connect
- SES: Maximum sending rate exceeded Amazon SES: Throttling — Maximum sending rate exceeded (454 Throttling failure)
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026