Using classic Outlook for Windows in business environments
Our issue has been occurring for approximately 2 weeks now. I contacted Yahoo, and they stated it's either Microsoft or our host (GoDaddy), and GoDaddy states there is nothing wrong on their end. Microsoft doesn't seem to be taking this very seriously.
Who knows where the problem is originating, but it seems to be somewhat widespread, so it would be nice if whoever's system is causing it would do something to fix it. Especially since we are unable to communicate with our customers who have a Yahoo email account, I'm confident we are not the only company dealing with this right now.
I agree!! It's been happening for months and Microsoft isn't addressing it. Even IF it is on the Yahoo end, as widespread as this is and the # of MS users affected, MS should have a vested interest in the resolution. The fact that they don't makes me want to take the company OFF 365 and go back to what we were using before.
It's a multi-layered issue:
- Yahoo implemented more stringent email requirements to better block spam. Ultimately this is the root cause, but the issue is that they changed their requirements and it's OTHER web sites (senders) that are not configured to meet their requirements. It doesn't appear that Yahoo is going to relax their requirements.
- Microsoft 365 email has the capability to comply with the requirements but it has to be enabled. It is not automatic.
- Even once it's enabled within Microsoft 365, any custom domain (i.e. if you own your domain name) has to have those settings also propagated into DNS, which is outside BOTH Microsoft's and (obv) Yahoo's control, so that's something that neither can fix. BTW if you switch to a new email system without making those DNS changes, you may find yourself in the same boat.
As the IT gurus (not me) in this thread have pointed out, this isn't something you can just wait around for Microsoft or Yahoo to fix, because certain portions of it aren't in their control (and the bit that Yahoo controls was a deliberate act). But any reasonably competent IT professional should be able to read this thread and knock out the fix pretty easily. I'm *not* a competent IT professional (just an engineer / computer geek) and the instructions in the various links in this thread made it pretty easy to do even for me.