The error 550 5.4.316 Message expired, connection refused indicates that the Outlook.com outbound servers repeatedly tried to connect to the recipient’s mail system (Charter) but could not, so the message eventually expired and was returned as undeliverable.
For Outlook.com, this falls under the category of “Can’t connect to remote server/message expired” or “Connection timed out” delivery failures:
- The problem is typically transient network or server connectivity between Outlook.com’s outbound servers and the recipient’s provider.
- The message may succeed later without any changes on the sender side.
Recommended actions based on Outlook.com guidance:
- Wait and resend
- Wait some time (for example, a few hours) and resend the message.
- If the non‑delivery report (NDR) indicates the recipient’s provider will keep retrying, no action is required until it either succeeds or fails definitively.
- If the problem persists over multiple days
- Since the recipient can receive from others and from a different account, the issue is likely specific to the path from Outlook.com to Charter.
- In that case, the only supported path is escalation via the providers:
- The sender should keep the full bounce message (including headers and the
550 5.4.316 text).
- Contact Outlook.com support through the standard support channel in Outlook.com and provide the full error so they can investigate why their outbound servers cannot deliver to Charter.
- The recipient can also contact Charter support and provide the same NDR so Charter can check if Outlook.com servers are being blocked or rate‑limited.
If a delivery failure message from Outlook.com instead mentions being “blocked” or “listed in” a blacklist service, the resolution would be to contact the recipient’s provider to request unblocking. However, for a pure message expired/connection refused scenario, the primary steps are to retry later and, if ongoing, have both providers investigate using the full NDR details.
References: