Deferred vs Bounced Email: SMTP 4xx and 5xx

Temporary failure means waiting

A 4xx SMTP response reports a temporary problem. Examples include a rate limit or temporarily unavailable resources. A queued message may be retried within its remaining lifetime. Repeatedly creating new copies or forcing an entire queue to flush can make a receiving limit worse.

Permanent failure needs investigation

A 5xx response normally ends that delivery attempt. Unknown recipient and receiving policy rejection are common examples. Inspect the full server response and receiving logs. Backup MX is not a mechanism for bypassing another server’s recipient or security decision.

Local acceptance is not remote delivery

A notification marked accepted by the local SMTP service has only completed local submission. A remote SMTP acceptance means the next receiving system took responsibility; it still does not prove inbox placement. Spam folders, downstream processing and mailbox rules can affect the final location.

Find the responsible stage

Use the queue ID, recipient, timestamp, destination and complete error. Correlate them with the receiving system. Check whether the message is a customer email, a system notification or a delivery failure notification; these have different purposes and may use different routes.

Keep expiry visible

A message cannot wait indefinitely. Queue age continues during pauses, and expired or deleted messages are not an archive. Consult your domain’s applied lifetime and the current plan conditions. A failure notification can also fail to reach its recipient.

References and service conditions

• SMTP: RFC 5321
• Null MX: RFC 7505
• Current plan limits
• Security responsibilities