Forum Discussion
Sending to Yahoo e mail accounts from my Outlook e mail
I have been able to send from my Outlook account to other e mail users that have a Yahoo account. about 4 weeks ago it has changed and I get error messages when I send to a person with a Yahoo mail account but they can send to me. I get an email back to me that says Delivery failed to the recipient. Would anyone know why this would happen all of a sudden. Thanks David675
48 Replies
- bestbreadmakerstCopper ContributorI also encountered the same situation for my company, I am looking to find a solution, thank you
- mjtnycCopper Contributor
For everyone reading this post here is the simplest way to add DKIM records, which I have found fixes the issue of sending to yahoo and aol accounts.
You will need access to whoever host your domain's DNS (for example godaddy.com)
Sign into your Office 365 tenant with an admin account https://admin.microsoft.com
Go to the Security Admin center https://security.microsoft.com
from here go to Policies & rules -> Threat Policies -> Email authentication settings
click on DKIM
Select your main domain which should bring up a new box. ENABLE "sign messages for this domain with DKIM signatures" Most likely you won't have DKIM records setup, so it will fail but it should give you the records you need. They will look like this (but with your own domain):
HOST: selector1._domainkey
TARGET: selector1-domain-com._domainkey.domain.onmicrosoft.com
HOST: selector2._domainkey
TARGET: selector2-domain-com._domainkey.domain.onmicrosoft.com
where domain-com is your own domain (with a dash not a dot) and the end part is your "onmicrosoft.com" domain setup when you first created your 365 account.
Add these records to your DNS and then go back to Office 365 tenant and enable again. (you may have to wait 5 - 10 minutes first) Once enabled you are all set!
Mike
- JP_DavenCopper ContributorThanks for this! Ive been trying to figure this out and this was these were the best instructions. Super straight forward and seemed to have worked!
- mjmcufCopper Contributormjtnyc
Thanks for the above on the Sector 1 and 2, I have entered those as well, but possibly not correct. I'm going to go out and double check that they are correct. Part of the problem in checking is that I'm logged into work via 365 and the account I have to check is not associated with work but still runs on 365, and as we all know 365 gets confused even if you log out and log in as a new "person" on the same machine. I'll try this, log in as Admin into 365 and see if I've entered the correct Sector 1&2 info. Thanks for the help. Cheers, MJ- mjtnycCopper Contributor
mjmcufTry logging into the Office 365 (with admin credentials) in an incognito window. That way it won't conflict with your own account. If you have created the CNAME records correctly then you will be able to enable DKIM. If they aren't correct, then it should tell you what it expects.
- DLutchy365AssistBrass ContributorLast year Google and Yahoo made a joint announcement that will effectively change how commercial email will be sent and received on a global scale forever. Both Yahoo and Google email platforms will begin to block and aggressively filter incoming email traffic that doesn’t meet new message authentication and procedural requirements. Additionally, they also included some infrastructure and performance thresholds associated with commercial email best practices.
Announcement from Yahoo - https://blog.postmaster.yahooinc.com/post/730172167494483968/more-secure-less-spam
Announcement from Google - https://blog.google/products/gmail/gmail-security-authentication-spam-protection/ - DRHinvestmentsCopper Contributor
David675 we are having the same issue for a few weeks. Getting an “undeliverable” a few days later. returned '550 5.4.300 Message expired -> 421 4.4.2 Connection dropped due to SocketError'
Unable to email to AOL or Yahoo email accounts. For some reason we have another domain with Google and are able to send emails from there. Microsoft please fix this issue or we will port to Google.
- joe_tonerCopper Contributor
I resolved this issue by adding a dmarc record with my dns registrar. it would look something like this below. it took 48 hours to propagate
_dmarc."your domain name.com"
value "v=DMARC1: p=none; rua=mailto:"any email address you control"; pct=25;"
TTL 300 Seconds
Simple routing
no quotes with the domain or email address example below
_dmarc.microsoft.com "v=DMARC1; p=none; rua=mailto:email address removed for privacy reasons; pct=25;"
use an email address you don't care about expect emails daily with dmarc summary reports
- JeffSparksCopper Contributor
You bring up a good point about switching to Google. In going to look at their pricing if it's comparable see you later Microsoft. Im not going to pay for an unusable email service.
- TinaMMSPCopper ContributorI'm in Australia and exact same issue - so frustrating.
- RDAAdminCopper Contributor
We are experiencing this as well in Australia, very frustrating. However have noted that email direct we get the same error, email via MYOB finance software and it goes through??
Anyone heard of a fix yet or ETA on a fix?
- JeffSparksCopper Contributor
We cannot currently send to yahoo, aol, and a few other domains. We get the same bounceback message everyone else in this thread is receiving.
- cgrafner1580Copper Contributor
Same issue with a client in TN. 3 different accounts, 2 Yahoo and 1 AOL. Same exact message.
What's strange is that the bounce the client sent me today has a time stamp 5 hours in the future. Client recieved the bounce at about 11am Eastern Time time in the message is about 4PM same date. Either something is very wrong or message sent from another time zone outside the US?
Client using Office 365 email
- cgrafnerCopper ContributorI was able to fix my issue yesterday. The bounce back is misleading but my problem ended up being that my SPF record was missing. It was there before but I was checking something else in the O365 Admin portal and decided to quickly check the domain health and sure enough my SPF record was gone. I gained access to the DNS host and put this back in place. Client is working fine now. I also checked my dkim and dmarc records. So I would make sure that your SPF is there and correct.
- DRHinvestmentsCopper ContributorThis SOLVED my issue! Cannot thank everyone enough. I put a TXT record into DNS for this. After doing DMARC and DKIM this finally got e-mail going back to Yahoo!. Much appreciated.
" v=spf1 include:spf.protection.outlook.com -all "
- DLutchy365AssistBrass Contributor
I also have a client with this problem.
They are receiving a bounce with this error -
Remote server returned '550 5.4.300 Message expired -> 451 [RL01] Message temporarily deferred'
- ctwanner1355Copper ContributorHaving the same issue and include AOL and Verizon.net. Which probably means Verizon and Microsoft are having some sort of issue since VZ owns both AOL and Yahoo. This is what we get
1/17/2024 5:21:49 PM - Server at DM6PR16MB3672.namprd16.prod.outlook.com returned '550 5.4.300 Message expired -> 421 4.4.2 Connection dropped due to SocketError'
1/17/2024 5:18:28 PM - Server at mta6.am0.yahoodns.net (67.195.228.106) returned '421 4.4.2 Connection dropped due to SocketError'- David675Copper Contributor