TL;DR
4.4.5 means mail-system congestion blocked this attempt. Capture the reporting system and delivery stage, retry with a bounded backoff policy, and keep recipient suppression separate from this temporary capacity condition.
What this code means
X.4.5 denotes mail-system congestion: delivery could not proceed because the relevant system was congested. The code is specific about the condition but not which system or resource is affected.
Provider examples
421 4.4.5 Server busy, try again later. For more information, go to About SMTP error messages. - gsmtpTechnical meaning
The reporting mail system could not deliver during the current attempt because of congestion. Under the standard this is a persistent transient failure, not a hard bounce.
Delivery status
The class-4 prefix means the condition may clear. It does not identify a particular capacity resource, prove a recipient problem, or authorize unlimited retrying.
- Class
- Temporary failure
- Retry
- Controlled retry
- Suppression
- Check the full context
Retry decision
Check current recipient eligibility, then retry with idempotency, backoff, jitter, and an attempt/time limit. Stop after success, a permanent result, an eligibility change, or limit exhaustion; investigate persistent congestion.
Suppression decision
Do not suppress based on 4.4.5 alone. This is a temporary capacity result, so suppression requires an independent permanent recipient signal or applicable policy.
Common causes
- The mail system was congested and could not deliver during the attempt.
Diagnostic steps
- Confirm exactly 4.4.5 with a 4xx basic reply.
- Record the response, message, time, reporting system, and delivery stage.
- Inspect available system logs for congestion scope without inferring a specific resource from the code alone.
- Use bounded retries and stop at success, permanent result, recipient-ineligibility change, or the configured limit.
Actions by owner
Sender administrator
- Back off and maintain an idempotent bounded queue instead of adding delivery pressure.
- Group repeats by reporting system and time before escalating evidence.
Recipient administrator
- Inspect congestion in systems you control for the matching time.
- Relieve a confirmed capacity condition and verify a controlled attempt.
Provider
- Inspect managed service load and the reported delivery stage without over-reading the code.
- Restore capacity and retain the exact reply for correct sender retry handling.
Sources
These sources define what this enhanced status code means, mainly through the IANA registry and related RFCs. When provider examples appear on the page, they come from that provider's published documentation. Follow the links to read the original wording in context.
- SMTP Enhanced Status Codes — IANA registry of enhanced mail system status codes.
- RFC 5248 — A Registry for SMTP Enhanced Mail System Status Codes — Creates and governs the IANA enhanced status code registry.
- RFC 2034 — SMTP Service Extension for Returning Enhanced Error Codes — Defines how SMTP returns enhanced status codes to clients.
- RFC 3463 — Enhanced Mail System Status Codes — Defines the class/subject/detail model for enhanced status codes.
- Gmail SMTP errors and codes — Official Gmail Help table of SMTP error messages and status codes.
Last verified:
