How to Fix Email Bounceback Errors (Non-Delivery Reports)

Diagnose and resolve common email deliverability failures and returned messages.
Common Bounceback Codes
| Error Code | Meaning | Primary Cause | Resolution |
|---|---|---|---|
| 550 5.1.1 | User Unknown | The recipient email address does not exist or was misspelled. | Verify the recipient address for typos and try sending again. |
| 550 5.7.1 | Relaying Denied | Outgoing authentication failed or your server IP is blocked. | Enable SMTP authentication in your email client settings. |
| 552 5.2.2 | Mailbox Full | The recipient mailbox has reached its maximum storage capacity. | Contact the recipient via an alternative method to clear disk space. |
| 554 5.7.1 | Spam Rejected | The message failed spam checks or lacked valid SPF/DKIM records. | Configure valid SPF, DKIM, and DMARC records in your DNS zone. |
1. Check the Non-Delivery Report (NDR)
When an email fails to deliver, the mail server sends an automated response containing diagnostic information:
- Open the returned email message.
- Locate the numeric error code (typically a three-digit code starting with 4 or 5).
- Check the header section for the exact failure reason listed under Diagnostic-Code.
2. Verify Mail Server Authentication
- Open your email client settings (Outlook, Apple Mail, or Thunderbird).
- Access the Outgoing Mail Server (SMTP) properties.
- Ensure Authentication Required is selected.
- Verify that your full email address and password are explicitly set for outgoing authentication.
Temporary vs Permanent Failures: Error codes starting with 4 (e.g. 451) indicate a temporary server delay; your mail server will retry automatically. Error codes starting with 5 (e.g. 550) indicate a permanent failure requiring manual correction before resending.
Next: How to Configure SPF, DKIM and DMARC Records covers the records that stop most bouncebacks happening.
If you have any questions, please contact our support team for assistance.