Bounces and errors

What Does 421 4.4.2 Mean, and How Do I Fix It?

Outreach2dayPublished 4 min read
On this page

Short answer

421 4.4.2 is a temporary SMTP error: the connection was open but broke or timed out before the message transaction finished. RFC 3463 calls 4.4.2 a bad connection. A mail server that gets it keeps the message in its queue and retries, so a single 421 4.4.2 needs no action. Look closer when it repeats for one mailbox or for many recipients at one provider.

What the code says

421 is the reply a server sends when it closes the connection. RFC 5321 writes it as "Service not available, closing transmission channel." 4.4.2 is the status RFC 3463 calls "Bad connection": "The outbound connection was established, but was unable to complete the message transaction, either because of time-out, or inadequate connection quality."

The first digit makes it a persistent transient failure, one where "sending in the future may be successful." The code says nothing about the content, the sender or the recipient. The session broke before the transaction ended, and RFC 5321 tells a client whose connection closes unexpectedly to treat it "as if a 451 response had been received": a temporary failure, retried later.

The texts that come with it

Text

Who writes it

What happened

"421 4.4.2 [hostname] Error: timeout exceeded"

A Postfix server

The client stayed silent longer than the server waits

"421 4.4.2 Connection dropped due to SocketError"

Exchange Server, in Queue Viewer

The connection broke; Microsoft documents a failed TLS negotiation

"451 4.4.2 Timeout - closing connection."

Gmail

Gmail closed a session that timed out

Postfix. The 421 4.4.2 timeout exceeded reply is in the Postfix SMTP server code. How long the server waits is the smtpd_timeout setting: "Normally the default limit is 300s, but it changes under overload to just 10s." A busy receiving server cuts slow clients sooner.

Exchange. Microsoft's TLS 1.0 and 1.1 article lists "421 4.4.2 Connection dropped due to SocketError" in Queue Viewer, with "TLS negotiation failed with error SocketError" in the Send connector log. The cause is an on-premises server still on TLS 1.0 or 1.1, which Microsoft 365 has deprecated; the fix is TLS 1.2 on that server. In this case the 421 is the sending server's own record of the broken connection.

Gmail. Google's SMTP error list uses 451 with the same status. Its "421 4.7.0 Connection expired, try reconnecting" is covered in 421 4.7.0.

Where you saw it decides what happens next

In a delay notice or your server's queue. Your mail server keeps the message and tries again. RFC 5321 says the retry interval should be "at least 30 minutes" and the give-up time "generally needs to be at least 4-5 days." If every attempt fails, the server gives up and sends a final bounce. Exchange Online reports that as 4.4.7 "Message expired" in Microsoft's NDR reference: the message stayed in the queue past its expiration time.

In your sending tool's log. Here the tool was handing the email to your mailbox's SMTP server and the connection broke on the way. Check whether the tool marks that email as sent, failed or queued for another attempt before you send anything again.

When to look closer

  • Once, then delivered. Nothing to do; the retry did its job.

  • One mailbox, every send. The fault sits between that mailbox's tool and its SMTP server. Compare the host, port and encryption with a mailbox that sends fine, then send your provider the times and the full error. If the tool shows a 530 instead, the settings are the cause; see 530 5.7.0.

  • Many recipients at one provider or domain. Connections to that provider keep breaking. An outdated TLS version on the sending server is one documented cause. If your provider's servers are current, ask what its logs show and watch whether codes such as 421 4.7.28 appear alongside.

  • Every mailbox and every recipient. The problem is on your provider's sending side or your network. Pause and ask the provider.

Free guide19 min read

Send 100,000 cold emails a month

Domains and mailboxes you need, DNS, warmup, lists, copy and follow-ups, with a launch checklist, sent to your inbox.

Unsubscribe in one click.

What it means for a cold email list

A 421 4.4.2 says nothing about the address, so keep it on the list. Wait for the final result: if the server gives up and the last attempt returns a permanent code such as 550 5.1.1, remove the address then.

Don't resend by hand while the server is still retrying. RFC 5321 warns that a timeout after the end of the message data "would typically result in delivery of multiple copies of the message." For cold email, that is a prospect getting the same first email twice.

Keep temporary errors apart from hard bounces in your numbers. Bounce rate too high sorts bounces into bad addresses, blocks, temporary errors and authentication failures.

Questions

Is 421 4.4.2 a block on my domain or IP?

The code names a connection problem. When Gmail defers mail over reputation or volume, it uses 421 4.7.0 or 421 4.7.28 and says why in the text. A 4.4.2 that keeps coming from one provider for days still needs attention, because the message expires at the end of the retry window.

How long will the server keep retrying?

Each mail server sets its own limit. RFC 5321 favors two connection attempts in the first hour, then one every two or three hours, and a give-up time of at least four to five days.

What we recommend at Outreach2day

Outreach2day analytics shows warmup inbox, spam and bounce rate for every mailbox and splits its sends by recipient provider: Google Workspace, Microsoft 365 and others. Read next to your sending log, that split shows whether a run of 421 4.4.2 belongs to one mailbox or to one recipient provider.

Sources

Deliverability call

Talk to our deliverability team

Book a call with the people who run our mailbox infrastructure. We look at your current setup and tell you what to change.

  • Review your domains, DNS records and current inbox placement
  • Size the setup: domains, mailboxes per domain and daily volume per mailbox
  • Plan warmup and the move from your current provider or sequencer

Free call

See open times in your time zone and book on this page.

Or open the booking page

See deliverability issues before they kill performance

Check each mailbox's daily inbox, spam and bounce rate, replace the weak ones early, and keep warmup, protection, and sending in one place.