Bounce storm / backscatter: your server sends bounces to forged senders or bounces loop between servers
Mail systems send non-delivery reports to innocent people (forged senders) or bounce messages ping-pong endlessly.
backscatter spambounce loop null sendermail loops back to myselfDelivery Status Notification floodauto-reply loop mail storm Meaning
Reject invalid recipients during the SMTP transaction instead of accepting and bouncing later (reject_unverified_recipient, smtpd_recipient_restrictions), keep catch-all off, use SPF/DKIM-aware rejects, and set bounce_notice_recipient/2bounce limits. Null sender <> mail shouldn't generate bounces.
Common causes
- Accepting mail for non-existent users then bouncing
- Catch-all domains
- Forged sender spam
- Auto-responders replying to bounces
- Missing loop detection
⚡ Quick fix
- Reject unknown recipients at SMTP time
- Disable catch-all
- Never send auto-replies to
<>orAuto-Submittedmessages
Detailed fix by platform
Shell
postconf -e "smtpd_reject_unlisted_recipient = yes" "unknown_local_recipient_reject_code = 550"
How to diagnose
- Unknown recipients — Rejected at SMTP?
- Catch-all — Off?
- Auto-replies — To <> suppressed?
🔧 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)
- 4.7.28 Gmail: 421 4.7.28 Our system has detected an unusual rate of unsolicited mail originating from your IP address
- 5.7.501 Microsoft 365: 550 5.7.501 Access denied, spam abuse detected — account restricted from sending
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