Skip to content
Microsoft (Outlook.com and Microsoft 365) · temporary error

4.4.316: destination server refused the connection

Exchange Online is trying to deliver outside Microsoft 365, but every connection to the receiving server is being refused.

Microsoft
Provider
Temporary (4xx)
Class
Sources checked
Author

At a glance

Code
4.4.316
Temporary or permanent
TemporaryThe sending server keeps the message and tries again later.
Who has to act
The recipient's side. Their mail admin has to change something; you can tell them.
What the server says
4.4.316 Connection refused [Message=Socket error code 10061]

What it means

Exchange Online returns this when it sends to a server outside Microsoft 365 and cannot open an SMTP connection because the remote end refuses it (socket error 10061, connection refused). The code is temporary, so the service keeps the message and retries; if the refusal lasts, it ends as a 4.4.7 expiry. Microsoft notes that the problem almost always lies with the receiving server or its network, and that the error includes the IP address of the server that refused, which tells you whose server it is.

Common causes

  • The receiving mail server is down, or its SMTP service is not listening on port 25.
  • A firewall in front of the receiving server is rejecting connections from Microsoft 365.
  • The MX record points to an address that does not run a mail server.

How to fix it

  1. 01Read the IP address in the report to identify which server refused the connection.
  2. 02Contact the recipient's organization or its mail provider and give them that address and the time of the attempts.
  3. 03The destination admin should check that the server accepts connections on port 25 from Microsoft 365 and that the MX record points to it.

Sources

What this page rests on, checked on 20 Oct 2026. The explanation is ours; the reply text is the server's.

  1. 4.4.7Message expired in the queue.Exchange Online kept retrying a message for a day, the receiving server never accepted it, and the message expired.MicrosoftTemporary
  2. 4.4.1No answer from the receiving server.The sending server tried to connect to the receiving server and got no answer, so it keeps the message and tries again later.StandardTemporary

Further reading

All 111 Microsoft codesEvery code in the wikiPaste your own bounce

Beat · paid monitoring

A heartbeat for your email.

Beat runs every check on this site on a schedule: 41 checks, 33 blacklists and real inbox placement. The moment something breaks, it tells you what broke, why it matters, and the exact fix.

example.comWatching
  • SPFpass
  • DKIMpass
  • DMARCp=none
  • Blacklists0 of 33

Illustrative. Your domain, every few hours.

Also from us:Pulse: your own sending infrastructureConsulting: $65/hr, no retainer