A temporary failure can require an immediate repair even though the message remains retryable. A permanent failure can disappear after a legitimate configuration correction even though the original failed attempt should not be repeated unchanged. Treat the SMTP class as a handling instruction and the diagnostic text as evidence for the investigation.
Read the class at the failed stage
RFC 5321 distinguishes positive completion, intermediate replies, transient negative completion and permanent negative completion. A 4xx response permits normal later retry handling. A 5xx response means the requested action was not taken and the same request should not be repeated unchanged. The exact stage matters: a rejected recipient, a rejected DATA command and a rejection after the message content have different transaction boundaries. RFC 5321 sections 4.2 and 4.5.4.
A final positive response after DATA transfers responsibility for the accepted message to that SMTP receiver. It does not establish placement in an inbox. Conversely, a connection failure after the client transmitted the final terminator but before it saw the reply can leave the outcome uncertain. Blind manual resubmission can create duplicates if the first copy was accepted.
Build a queue timeline
Record the first attempt, every relevant response, last attempt, next scheduled attempt, queue age, recipient state and expiry decision. Include the message's business usefulness: an expired login link and an invoice do not have the same useful lifetime. Preserve the sending system's actual retry policy rather than inventing a universal provider delay.
RFC 5321 supplies queueing guidance, including delayed retries rather than continuous attempts. Apply the current platform's supported queue controls and the organization's delivery requirements. Do not use a tight retry loop to test whether a remote restriction has cleared. Separate new production traffic from queued retries when assessing load and recovery.
Compare three hypothetical outcomes
These are invented diagnostic cases, not captured mail transactions. Case A receives 451 at RCPT TO, so that recipient was not accepted. Keep the item under the sending service's retry policy while investigating the stated condition. If a later attempt reaches final DATA acceptance, record which recipient and message it covers; that single result does not settle every queued item.
Case B receives 550 5.1.1 for an invalid recipient. Stop unchanged routine retries and confirm the address through a trusted contact. Case C sends the DATA terminator but loses the connection before seeing the final reply. Unlike A or B, its acceptance is unknown. Look for receiver and queue evidence before creating another copy; the same Message-ID does not guarantee deduplication.
Match remediation to the cause
For temporary DNS, network or service failures, investigate the failing dependency while the queue remains bounded. For authentication-related deferrals, repair the named authentication problem rather than simply waiting. For a permanent invalid-recipient response, verify the address through an existing legitimate channel before creating a corrected message.
When acceptance is uncertain, reconcile the queue and receiving logs before resubmitting business-critical mail. Keep the original Message-ID and transaction evidence for investigation, while avoiding unsupported assumptions about deduplication. Close the incident only when queue growth has stopped, representative intended messages complete and expired or failed messages have an explicit disposition. Recovery of one test message does not prove the entire backlog was delivered.
Choose retry, repair or reconciliation
- 4xx with known non-acceptance: keep the item under supported queue policy and investigate the dependency.
- 5xx: stop unchanged routine attempts and confirm a legitimate correction.
- Missing final DATA reply: treat acceptance as unknown; reconcile receiver evidence before manual resubmission.
- Closure: record outcomes for every affected recipient, including expired messages and possible duplicates.