Skip to content

550 5.4.316 Message Expired: Connection Refused Fix

What the 550 5.4.316 message expired, connection refused bounce from Microsoft 365 means, why it arrives late, and how senders and admins deal with it.

Nov 20, 2026 6 min read 1,267 words
550 5.4.316 Message Expired: Connection Refused Fix
550 5.4.316 message expired: connection refused
550 5.4.316 message expired: connection refused

You sent an email from Microsoft 365 a day or two ago. Now a bounce arrives: "550 5.4.316 Message expired, connection refused (Socket error code 10061)". The address looks right. The message just never got there.

This guide explains what the code means, why it comes late, and what to do about it, whether you are the sender or the admin.

What 550 5.4.316 means#

The bounce has two parts. 550 is the SMTP reply code for a permanent failure. The server has stopped trying. 5.4.316 is the enhanced status code. The middle digit, 4, points to a network or routing problem. It is not about the address or your content.

The words tell the rest of the story:

  • Connection refused means the receiving server would not open a connection.
  • Message expired means Microsoft 365 kept trying, but time ran out.
  • Socket error code 10061 is the network error behind it: the other side said no to the connection.

So, in plain words: Microsoft 365 could not reach the recipient's mail server, tried again for a while, and then gave up.

Why the bounce comes so late#

The error starts as a temporary one. Microsoft's list of Exchange Online NDR codes has the code 4.4.316 Connection refused [Message=Socket error code 10061]. It says Microsoft 365 is trying to send to a server outside Microsoft, and every attempt to connect fails.

A 4xx code means "try later". So Exchange Online queues the message and retries. The SMTP standard, RFC 5321, describes this retry process and says senders should keep trying for days, not minutes. When the retry time ends and the server is still down, the temporary error turns into a permanent one. That is when you get the 550 bounce.

This is why the bounce often lands a day or more after you hit send.

Common causes of the connection refused error#

Microsoft says this error almost always points to a problem at the receiving server or its network, outside Microsoft 365. Common reasons:

  • The mail server is down. It crashed, it is being moved, or the service is stopped.
  • A firewall blocks port 25. The server is up, but the firewall drops or refuses mail traffic.
  • The MX record points to the wrong place. The domain's MX record names a host that no longer runs a mail server.

Two more causes are worth a check:

  • The domain moved mail hosts. After a move, the old server is shut off but the MX record still points to it.
  • The domain no longer takes mail. The company closed, changed its name, or let its mail setup lapse.

Only the last cause is about your data. The rest belong to the recipient's IT team.

How to fix 550 5.4.316 as a sender#

You cannot fix the other company's server. But you can find out which case you are in.

Step 1: Read the IP address in the bounce#

Microsoft says the bounce should include the IP address of the server that refused the connection. That tells you who owns the problem.

Step 2: Check the domain's MX record#

Run an MX record lookup on the recipient's domain. If there is no MX record, or it points to an odd host, the domain may not take mail anymore.

Step 3: Test the mail server#

An SMTP test shows whether the server answers on port 25. If it refuses the connection, the fault is on their side.

Step 4: Tell the recipient another way#

Call them or write through LinkedIn or a contact form. Tell them mail to their domain bounces with "connection refused". Send the full bounce, with the IP address.

Step 5: Check the address itself#

If the domain looks dead, the contact may have moved on. Look up the person's current address with an email finder before you send again.

How to fix it as an admin#

If outside senders report this error about your domain, start here:

  1. Check that your mail server is up and that the mail service is running.
  2. Check your firewall and make sure it allows inbound SMTP on port 25 from the internet.
  3. Check your MX records. They must point to the server that runs your mail today.
  4. After a move, keep the old server or a relay running until the new MX record has spread.

If you send from Microsoft 365 and many of your users see this bounce for many domains, check any outbound connector that routes mail through a smart host. A dead smart host gives the same error for every message.

Is this a hard bounce?#

Yes, in the sense that the message failed for good. But the address may still be valid. The mailbox may be fine once the server comes back.

So do not delete the contact at once. Put it on hold. If the domain has no working MX record, or the bounce repeats for weeks, remove it. Our hard vs soft bounce guide explains how each type counts toward your bounce rate.

How to avoid these bounces in outreach#

A server outage on the other side is out of your hands. A dead domain on your list is not.

  • Verify before you send. An email verifier checks the domain and its mail server, and flags domains that do not accept mail.
  • Re-check old lists. Companies close, merge and change domains. A list from last year will have dead domains in it.
  • Group bounces by domain. If every address at one company bounces with this error, the problem is their server.
  • Hold, then retry once. Wait a few days after the company fixes its server, then send one more time.

550 5.4.316 vs other common bounce codes#

Code What it usually means Who fixes it
550 5.4.316 Server refused the connection until the message expired Recipient admin
4.4.316 Same issue, still retrying Wait, or recipient admin
5.4.300 Message expired before delivery Recipient admin
550 5.1.1 Mailbox does not exist Sender

For the full set, see our list of email bounce codes.

Message Expired Checklist#

  • Copy the full bounce, including the IP address
  • Check the domain's MX record
  • Test whether the mail server answers on port 25
  • Tell the recipient through another channel
  • Hold the contact; remove it if the domain is dead
  • Verify the rest of your list before the next send

FAQ#

What does 550 5.4.316 message expired mean?#

It means Microsoft 365 could not connect to the recipient's mail server, kept trying for a while, and then gave up. The cause is on the receiving side.

What is socket error code 10061?#

It is a network error that means the connection was refused. The other server, or a firewall in front of it, said no to the connection.

Why did the bounce arrive a day after I sent the email?#

The error starts as a temporary one. Exchange Online keeps the message in a queue and retries. The bounce only comes once the retry time ends.

Can I fix this error as the sender?#

Not directly. Only the recipient's admin can bring the server back or fix the MX record or firewall. You can check the domain and tell them.

Should I remove the contact from my list?#

Not at once. Hold it. If the domain has no working mail server for weeks, remove the address.

Want fewer dead domains on your next campaign? Check your list with the Tomba Email Verifier before you send.

// start free

See who Tomba finds at any company

Type a company's domain to see its people, their roles and verified work emails, each with the pages it was found on. Free account, no card.

Free plan · No credit card required · GDPR & CCPA

Share
0 clapsEnjoyed it? Give a clap.
AU

// about the author

Tomba Editorial Team

Was this helpful?