Using Microsoft Outlook on my PC, Using a Go Daddy Email (Howie@<mod: PII removed>.com) are rejected.

Question

Using Microsoft Outlook on my PC,
365 or office I am not sure (need help knowing)
Using Godaddy Email server(Howie@<mod: PII removed>.com)some emails are rejected (failed) because they were unable to connect to the email server...
Example of error message :3/11/2026 8:50:51 PM - Server at PH0PR08MB6550.namprd08.prod.outlook.com returned '550 5.4.317 Message expired, cannot connect to remote server(451 4.4.0 Socket error: ConnectionReset)' 3/11/2026 8:49:30 PM - Server at 162.130.196.138 (162.130.196.138) returned '450 4.4.317 Cannot establish session with remote server [Message=451 4.4.0 Socket error: ConnectionReset] [LastAttemptedServerName=162.130.1961 38] [LastAttemptedIP=162.130.196.138:25] [SmtpSecurity=-2;-2] [MW1PEPF0001501D.namprd08.prod.outlook.com 2026-03-11T20:49:30.531Z 08DE7DD8C8B597F2]'

Original message headers:

<Moderator: deleted, see comment below.>

                PH0PR08MB6550.namprd08.prod.outlook.
Also, because they don't recognize this email address.....

Answer 1

Do I have to use GoDaddy for my Business Email address "Howie@<mod: PII Removed>.com"?

Answer 2

The error codes in the NDR show a connection problem between Microsoft 365’s outbound servers and the remote SMTP server, not a problem in Outlook on the PC:

• 450 4.4.317 Cannot establish session with remote server [Message=451 4.4.0 Socket error: ConnectionReset]
• 550 5.4.317 Message expired, cannot connect to remote server (451 4.4.0 Socket error: ConnectionReset)

These mean:

• Microsoft 365 accepted the message from Outlook and tried to deliver it.
• When Microsoft 365 tried to open an SMTP session to the destination server (162.130.196.138:25 in the example), the TCP connection was reset or could not be established.
• After multiple retries over the retry window, the message “expired” and a 5.4.317 NDR was generated.

Key points from the headers:

• SPF, DKIM, and DMARC all pass for anewoutdoorliving.com:
  • spf=pass
  • dkim=pass
  • dmarc=pass
• Anti-spam verdict is low (SCL:1; CAT:NONE), so the message is not being rejected as spam.
• X-MS-Exchange-CrossTenant-Network-Message-Id: a027044a-... identifies this specific message in Exchange Online and can be used for message trace.

So the problem is not:

• Outlook profile on the PC.
• Authentication or reputation of anewoutdoorliving.com.
• Microsoft 365 spam filtering.

It is a mail-flow / connectivity issue between Microsoft 365 and the remote SMTP host.

Actionable steps:

1. Confirm Microsoft 365 successfully accepted the message
   • In the Exchange admin center (EAC), run a message trace using the Network Message ID from the header (X-MS-Exchange-CrossTenant-Network-Message-Id).
   • The trace will show the message as delivered to the Microsoft 365 outbound connector and then failing with 4.4.x/5.4.317 when attempting to reach the remote server.
   • This confirms Outlook and your account are working and that the failure is after Microsoft 365 has taken responsibility for delivery.
2. Involve the remote mail server owner (or GoDaddy, if that IP is theirs)
   • The IP 162.130.196.138 in the error is the remote SMTP server Microsoft 365 is trying to reach.
   • The ConnectionReset and Cannot establish session errors indicate that server (or a firewall/load balancer in front of it) is closing or blocking the connection from Microsoft 365.
   • Provide the remote admin with:
     • The error lines:
       • 450 4.4.317 Cannot establish session with remote server [Message=451 4.4.0 Socket error: ConnectionReset] [LastAttemptedIP=162.130.196.138:25]
       • 550 5.4.317 Message expired, cannot connect to remote server (451 4.4.0 Socket error: ConnectionReset)
     • The Network Message ID (a027044a-5515-4b0d-5d40-08de7ee4d011) and timestamps.
   • Ask them to check:
     • Whether port 25 is open and accepting connections from Microsoft 365 IP ranges.
     • Whether any firewall, IDS/IPS, or rate-limiting is dropping or resetting connections from Microsoft 365.
     • Whether their SMTP service is overloaded or intermittently failing.
3. If the destination is your own GoDaddy-hosted domain
   • Open a support case with GoDaddy and provide the same details.
   • Ask them specifically to:
     • Verify SMTP availability on the server handling mail for the affected recipient domain.
     • Confirm they are not blocking or throttling Microsoft 365 outbound IPs.
4. Use message trace for further diagnostics
   • In Exchange Online, use message trace with the Network Message ID to:
     • Confirm which hop failed.
     • See if only certain domains/servers are affected (e.g., only messages to a specific partner or provider).
   • The documentation notes that headers like X-MS-Exchange-CrossTenant-Network-Message-Id can be used with Get-MessageTraceV2 to retrieve all events for this message.
5. About “they don’t recognize this email address”
   • The headers show the message is from anewoutdoorliving.com and passes all authentication checks.
   • If recipients say the address is “not recognized,” that is likely a separate issue (e.g., their internal directory or allow-lists) and must be resolved on their side.

Summary:

• Outlook and your Microsoft 365 tenant are correctly sending and authenticating the email.
• The failures are due to the remote SMTP server (or its network path) resetting or refusing connections from Microsoft 365, leading to 4.4.317/5.4.317.
• Resolution requires the remote mail server owner (or GoDaddy, if they host that server) to fix connectivity from Microsoft 365 IPs; use message trace and the Network Message ID to provide them with precise evidence.

---

References:

• Message trace in the new Exchange admin center in Exchange Online
• Header firewall
• Provision x-headers by using EWS in Exchange
• Sender Support in Outlook.com