It would have been wonderful to know what the problem was originally so that we could point to it, but that information doesn't seem to be forthcoming. I would have thought this " receive" issue would be easy to solve in light of the earlier " send" problem, but probably the same people are not involved, so we have to start over.Ĩ Here's a link to the previous thread discussing the " send" problem: It really bugs me (and probably you too) is that Yahoo/Rogers makes a change, yet we have to spend hours and hours troubleshooting to get our e-mail clients working again. Since they were able to solve the " send" problem around April 10, they should be able to track down and solve the "receive" problem we are now encountering. They probably tested with the most recent version, or Outlook 2016, etc.
I then PM'd the mods here again and restated that the problem is still there and that it may be due to specific (older) e-mail clients, like my Outlook for Mac 2011.
I received an automated call back a couple of hours later saying that they had tested and everything was fine at their end. I PM'd the mods here and they issued a ticket. This way the mail application will fetch the email from the server on both devices, and sync it. Since April 29, the issue has been permanent and all of my e-mail addresses can no longer receive (on Outlook for Mac 2011. On iDevice (iPhone in this case) open Settings > Contacts, Calendar & Email > Add new account and follow the instructions inserting the same credentials as you gave when adding account to Mac. Earlier this week - around April 28 I saw that some of my e-mails were not able to receive e-mails with the same error message as before, except "Unable to Receive, Error 150", instead of " send" as indicated above.Ĥ. After significant back and forth with Rogers Moderators here and with Technical Support by phone, that send issue was resolved for me around April 10.ģ.
The problem started about a month ago in early April (April 3?) with not being able to send messages on my Outlook for Mac 2011.Ģ. It looks like this problem now has its own thread (one of my earlier posts in this thread now "points to a non-existent post).