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

X.4.1 · Network and routing

SMTP enhanced status code 4.4.1

No answer from host

X.4.1 means your server tried to connect but the remote system did not answer, because it was busy or unreachable. It is a temporary error.

Registry codeX.4.1
Forms in use4.4.1
Registry nameNo answer from host
Subject4: Network and routing
Permanent or temporary4.x.x persistent transient failure: retrying later may succeed
Associated basic codes451
Defined in[RFC 3463]

What the registry says

The outbound connection attempt was not answered, because either the remote system was busy, or was unable to take a call. This is useful only as a persistent transient error.

IANA SMTP Enhanced Status Codes registry, X.4.1

The basic codes it travels with

  • 451 Requested action aborted: local error in processing

In practice

X.4.1 is reported by your own server when the remote MX does not answer, for example because port 25 is filtered, the host is down, or the MX record points at an address nothing listens on. Repeated for days, it ends in an expired message. A domain whose MX hosts never answer is effectively undeliverable, and a verifier marks such addresses as unable to verify rather than valid.

What the sender should do

Let the queue retry. If every address at one domain gets it for days, check whether the domain's MX hosts are reachable at all.

Would verifying the list have prevented 4.4.1?

Partly

The reply is not only about one address, but providers weigh how often a sender hits addresses that do not exist. Removing bad addresses before sending lowers that signal.

How providers use X.4.1

Quoted from each provider’s own error reference.

Common questions

What does 4.4.1 mean?
X.4.1 means your server tried to connect but the remote system did not answer, because it was busy or unreachable. It is a temporary error.
What should I do about 4.4.1?
Let the queue retry. If every address at one domain gets it for days, check whether the domain's MX hosts are reachable at all.
Would an email verifier have caught 4.4.1?
Partly. The reply is not only about one address, but providers weigh how often a sender hits addresses that do not exist. Removing bad addresses before sending lowers that signal.

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