An email bounce-back message tells you that a message was not delivered, but the reason may be temporary, permanent, technical, or policy-related. This guide explains common SMTP error codes, shows how to interpret delivery reports, and provides a practical checklist for correcting the address, reviewing mail server settings, retrying safely, and escalating recurring failures.
Overview
An email bounce, also called a non-delivery report or delivery failure notice, is generated when a mail system cannot accept or deliver a message. The notice usually includes the recipient address, the server that rejected or deferred the message, an SMTP status code, and a plain-language explanation.
The first digit of an SMTP response gives a useful starting point:
- 2xx: The server accepted the message or completed the requested action. This is not a bounce code.
- 4xx: A temporary failure occurred. The sending system may retry automatically, but you should investigate if the problem continues.
- 5xx: A permanent or administrative failure occurred. Retrying the identical message without correcting the cause usually will not help.
The three-digit code is only part of the diagnosis. Providers often add an enhanced status code, such as 5.1.1 for a likely invalid mailbox or 5.7.1 for a policy or permission-related rejection. Wording varies between providers, so read the full diagnostic text and identify which server issued it.
A bounce is different from a delayed-message notice. A delay generally indicates that delivery is still being attempted. A final bounce means the sending system has stopped trying, or the receiving system has explicitly rejected the message.
Checklist by scenario
1. Invalid recipient or unknown mailbox
Common responses include 550, 551, 553, or an enhanced code such as 5.1.1. These can indicate a misspelled address, a deleted account, an invalid domain, or a recipient mailbox that does not exist.
- Compare the address in the bounce report with your original message and contact records.
- Check for extra spaces, incorrect punctuation, a changed domain, or a swapped character.
- Confirm the address through a trusted channel rather than replying to an unfamiliar automated notice.
- Send a short test message only after correcting the address.
If the address is correct and other people at the same domain can receive mail, ask the recipient or domain administrator whether the mailbox is active.
2. Mailbox full or over quota
A notice may mention a full mailbox, insufficient storage, or a quota limit. This is often treated as a temporary problem, but some systems return a permanent-looking failure after repeated attempts. Do not keep resending a large attachment while the mailbox is full.
- Contact the recipient through another known method and ask them to clear space.
- Use a smaller message or an approved file-sharing method if the recipient needs the content urgently.
- Retry once the recipient confirms that the mailbox is available.
3. Temporary server or connection failure
Codes such as 421, 450, 451, and 452 commonly point to temporary unavailability, rate limiting, greylisting, processing problems, or insufficient server resources. Exact meanings depend on the receiving system.
- Wait for the mail client or server to retry if automatic retry is enabled.
- Check whether the failure affects one recipient, one domain, or all outbound mail.
- Review your sending logs for repeated attempts and increasing delays.
- Do not use aggressive manual retries, which can worsen rate-limit or reputation-related blocks.
4. Sender blocked or message rejected by policy
A 550, 553, 554, or 5.7.1 response may indicate a blocked sender, prohibited content, authentication failure, an IP or domain reputation issue, or a recipient-side policy restriction. The code alone does not prove that your message was spam.
Check whether the bounce identifies a policy, blocklist, authentication, or reputation reason. For a business domain, verify that the sending domain is configured with the appropriate SPF, DKIM, and DMARC records. These settings help receiving systems evaluate whether messages are authorized and consistent with the domain. Use your provider's current documentation for exact record formats and alignment requirements.
If only one organization rejects your mail, contact that organization's mail administrator and include the complete diagnostic response. If many unrelated domains reject messages, investigate your outbound mail server, account security, authentication records, and sending patterns before contacting individual recipients.
5. Attachment, size, or content restriction
Messages may be rejected because the total message is too large, an attachment type is prohibited, or a content filter blocks the message. The report may mention size, attachment, content, or policy.
- Remove unnecessary attachments and send a smaller test message.
- Convert a large file to an approved sharing link, if permitted by your organization.
- Do not rename a prohibited file extension to bypass a filter.
- Check the sender and recipient provider limits rather than assuming they are identical.
6. Authentication or mail server configuration failure
Authentication-related failures can occur when a password is incorrect, a sending client uses the wrong port or encryption mode, SMTP access is disabled, or a domain's authentication records do not match the server sending the message. Review the provider's current IMAP and SMTP settings guide, then compare the documented settings with your mail client or application.
For a webmail account, sign in through the provider's verified login page and check for security alerts, account locks, or requests to reauthenticate. If you are unsure whether a notice is legitimate, use the safe webmail login guide rather than clicking an unexpected link in an email.
What to double-check
Before changing configuration or contacting support, preserve the original bounce notice. Record the time, sender address, recipient domain, subject, message ID, SMTP code, enhanced status code, and the server named in the report. Full headers can reveal whether the failure occurred at your outgoing server, an intermediate relay, or the recipient's server.
Use this quick diagnostic sequence:
- Confirm scope: Test whether the failure affects one address, one domain, or all recipients.
- Classify the code: Treat 4xx responses as potentially temporary and 5xx responses as requiring correction or administrator review.
- Check the recipient: Verify spelling, domain, mailbox status, and any known address change.
- Check the message: Review size, attachments, links, formatting, and unusual sending patterns.
- Check authentication: Review SMTP credentials, encryption, SPF, DKIM, and DMARC where applicable.
- Compare results: A successful message to another recipient can help isolate a recipient-side problem, but it does not rule out intermittent issues.
If the bounce contains a suspicious link or asks for credentials, do not use it to troubleshoot. Review the phishing verification checklist and access your account through a known webmail address.
Common mistakes
- Resending repeatedly: This rarely fixes a permanent 5xx rejection and may trigger rate limits.
- Reading only the subject: The useful detail is usually in the diagnostic body, not the notification subject.
- Assuming every 550 means the same thing: A 550 response can represent an unknown user, blocked sender, policy rejection, or another server-specific condition.
- Changing several settings at once: Make one controlled change so you can identify what resolved the issue.
- Ignoring account security: An unexpected delivery failure can accompany unauthorized sending or a compromised account. Review recent activity and secure the account if needed.
- Sharing full headers publicly: Headers can contain addresses, server names, message IDs, and other operational details. Redact sensitive information before posting them for help.
When to revisit
Revisit this checklist whenever a message bounces, a new mail client or application is deployed, a domain changes mail providers, or a recurring recipient begins rejecting messages. It is also useful before seasonal planning cycles, when teams may change sending volumes, shared mailboxes, automated notifications, or campaign workflows.
For administrators, review the workflow when mail server settings, authentication records, security controls, or provider policies change. During a quarterly operational review, verify that support staff know how to capture bounce headers, distinguish 4xx from 5xx responses, and escalate with complete evidence. Keep provider-specific SMTP ports, encryption requirements, message-size limits, and support links in a maintained internal reference rather than relying on memory.
Next action: Save one representative bounce report, identify its exact SMTP and enhanced status codes, and follow the scenario checklist above. Correct the smallest likely cause first, send one controlled test, and escalate only when the evidence shows that the receiving provider or mail administrator must intervene.