1. Home
  2. SMTP codes
  3. Enhanced status codes
  4. 4.4.2

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 codeX.4.2
Forms in use4.4.2
Registry nameBad connection
Subject4: Network and routing
Permanent or temporary4.x.x persistent transient failure: retrying later may succeed
Associated basic codes421
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

Registry and provider wording is quoted exactly; guidance is written by the SimpleVerifier Team.

SimpleVerifier Team · Last checked against the sources 2026-11-05

Clean your next list before it bounces

100 free email checks when you sign in with Google, no card. Then monthly plans from $9, or one flat price with fair use, never cut off.

100 free checks, no card Cancel anytime Secure payment by Stripe