This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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'
Using Classic Outlook on Windows for personal email, calendar, and contact management
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.
Hi! I'm having this same issue. I don't know much IT jargon, my domain is "@moorelifecounseling.com" Any assistance is appreciated. Thank you.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 12%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ER6%3C/text%3E%3C/svg%3E)
1st record to create:
Record type: CNAME
Name: selector1._domainkey
Value/Data: (whatever was in the text that popped up, should look like below)
selector1-<your_custom_domain>-com._domainkey.<your_OnMicrosoft_domain>.com
2nd record to create:
Record type: CNAME
Name: selector2._domainkey
Value/Data: (whatever was in the 2nd record in the text that popped up, should look like below)
selector2-<your_custom_domain>-com._domainkey.<your_OnMicrosoft_domain>.com
I think this is clearer
selector1-<CustomDomain>-com._domainkey.<CustomDomain>.onmicrosoft.com
selector2-<CustomDomain>-com._domainkey.<CustomDomain>.onmicrosoft.com
Assuming your domain name ends with .com, replace <CustomDomain> with your domain name (without the .com)
Quickest way to get to DKIM settings: https://security.microsoft.com/authentication?viewid=DKIM
B/c that is the correct spf record for my godaddy managed o365 mail. i failed to realize this may be different for different o365 tenants/providers. i assumed it would all be the same b/c it was all o365.
This is what confuses us (mail admins)... changing requirements dynamically. Do you have an article on this "new" requirement?
Nope. I only know it because I have enough customers on various domains and platforms that when it is affecting all of them, I can deduce that yahoo changed it. Since my clients that are running on private exchange servers are not affected, it might be that M365 hosted domains are subject to tougher rules due to the volume of emails that come from those servers. (Yahoo public statement was that everyone needed a minimum of SPF or DKIM, but bulk senders needed both along with DMARC).
My solution previously was to implement SPF, and turn off DKIM on M365. The other possibility of what happened is Microsoft might have gone through and Enabled DKIM on their M365 tenants that didn't have it turned on to try to assist. I found this to be the case on one of my domains. (I had turned off DKIM, but today I found it on). Turning DKIM on without DMARC being setup properly could be the cause of issues for some people, but I'm not going to post turning DKIM off as a solution anymore, since that might not be a permanent solution.
I've fixed 5 M365 Tenants at this point, still have 7 to go.
-Brad
HI EVERYONE,
It seems that on Friday Yahoo moved to goalpost on what was required for sending them emails (again). My private exchange server customers don't have any issues once SPF is implemented, but M365 are going to need the whole kit and kaboodle.
This is what confuses us (mail admins)... changing requirements dynamically. Do you have an article on this "new" requirement?