X.4.2 · Network and routing
SMTP enhanced status code 4.4.2
Bad connection
X.4.2 means a connection was made but the transaction could not be finished, because of a timeout or a poor connection. It is a temporary error.
| Registry code | X.4.2 |
|---|---|
| Forms in use | 4.4.2 |
| Registry name | Bad connection |
| Subject | 4: Network and routing |
| Permanent or temporary | 4.x.x persistent transient failure: retrying later may succeed |
| Associated basic codes | 421 |
| Defined in | [RFC 3463] |
What the registry says
The outbound connection was established, but was unable to complete the message transaction, either because of time-out, or inadequate connection quality. This is useful only as a persistent transient error.
IANA SMTP Enhanced Status Codes registry, X.4.2
The basic codes it travels with
- 421 <domain> Service not available, closing transmission channel
In practice
X.4.2 means the session was cut before the transaction finished. Gmail reports 451 4.4.2 for a timeout closing the connection. Common causes are slow sending clients, network problems and receivers that drop connections they consider suspicious. If it happens only with one provider and only at high volume, lower the number of parallel connections.
What the sender should do
Let the queue retry. Repeated 4.4.2 on one route points to network trouble or to the receiver dropping slow or unwelcome connections.
Would verifying the list have prevented 4.4.2?
No
This reply is about your sending setup, the message or the receiving system, not about whether the address exists, so verifying the list will not prevent it.
How providers use X.4.2
Quoted from each provider’s own error reference.
- Gmail 451 4.4.2
Timeout - closing connection. For more information, go to About SMTP error messages.
Common questions
- What does 4.4.2 mean?
- X.4.2 means a connection was made but the transaction could not be finished, because of a timeout or a poor connection. It is a temporary error.
- What should I do about 4.4.2?
- Let the queue retry. Repeated 4.4.2 on one route points to network trouble or to the receiver dropping slow or unwelcome connections.
- Would an email verifier have caught 4.4.2?
- No. This reply is about your sending setup, the message or the receiving system, not about whether the address exists, so verifying the list will not prevent it.
Full guides for this code
Sources
- IANA: SMTP Enhanced Status Codes registry (checked 2026-11-05)
- RFC 3463: Enhanced Mail System Status Codes (checked 2026-11-05)
- RFC 5321: Simple Mail Transfer Protocol, section 4.2.3 (reply codes) (checked 2026-11-05)
- Google Workspace Admin Help: Gmail SMTP errors and codes (checked 2026-11-05)
Registry and provider wording is quoted exactly; guidance is written by the SimpleVerifier Team.
SimpleVerifier Team · Last checked against the sources 2026-11-05