Outlook emails not deliverable to yahoo and aol

Anonymous
2024-01-13T17:14:45+00:00

Starting this week, our emails to yahoo and aol accounts are not being delivered, but emails to other email accounts are working. Here is one of the yahoo error message: 1/12/2024 9:27:16 PM - Server at SJ2PR02MB10076.namprd02.prod.outlook.com returned '550 5.4.300 Message expired -> 421 4.4.2 Connection dropped due to SocketError' 1/12/2024 9:26:15 PM - Server at mta5.am0.yahoodns.net (67.195.204.73) returned '421 4.4.2 Connection dropped due to SocketError'

And here is the aol error message: 1/12/2024 9:27:38 PM - Server at PH0PR02MB7367.namprd02.prod.outlook.com returned '550 5.4.300 Message expired -> 421 4.4.2 Connection dropped due to SocketError'
1/12/2024 9:15:15 PM - Server at mx-aol.mail.gm0.yahoodns.net (67.195.204.80) returned '421 4.4.2 Connection dropped due to SocketError'

Outlook | Windows | Classic Outlook for Windows | For home

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

221 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2024-02-26T18:18:59+00:00

    @mark gibb

    @Ron6576

    We're having the same problem. Microsoft says our records are all valid, but we're still having mail flow issues, specifically that when an external user (Gmail primarily) sends a message to a distribution list, they get a bounce message from Yahoo:

    '421 4.4.2 Connection dropped due to SocketError'

    and we're hearing from Yahoo email users that they are not receiving our messages.

    our domain is

    uugrassvalley.org

    and I am the only one 'in charge' here, with limited experience in the world of email admin... I keep getting passed between our DNS, cPanel, and Microsoft support, each claiming it's the other's fault :/

    Thanks for any help!

    Was this answer helpful?

    0 comments
  2. Ron-6928 4,991 Reputation points
    2024-02-16T15:54:17+00:00

    All records look valid. What is the problem?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-02-16T15:39:48+00:00

    Sure

    marlborough-lions.com

    Mark

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-02-15T16:08:24+00:00

    As Ron pointed out, you are not using Microsoft 365 as your email server. Your email server seems to be provided by Network Solutions. Since they also have your domain, their support should be able to assist with the solution. If you are tackling it alone, then working through the steps to setup a DMARC record is your next step.

    If you are doing some sort of hybrid setup where you have your domain emails being forwarded to an Outlook account, I'd try logging in directly to the Network Solutions webmail and see if you can email the addresses that are bouncing back will work from there.

    Good luck!

    -Brad

    Was this answer helpful?

    0 comments
  5. Ron-6928 4,991 Reputation points
    2024-02-15T06:26:12+00:00

    Your MX record (mail servers responsible for your domain email traffic) shows this:

    mx001.netsol.xion.oxcs.net

    mx002.netsol.xion.oxcs.net

    That tells me you aren't using Microsoft service to host your mail server. The solution is the same. Your SPF record looks valid but you don't have a DMARC record https://easydmarc.com/tools/dmarc-lookup?domain=pallmed.us

    You might need to create a TXT (DMARC) record at Network Solutions.

    Was this answer helpful?

    0 comments