I appear to have all the proper settings and I've added @rogers.com to my username, but I still get the pop-up. See picture below which may take a few minutes to be approved.
If I click continue, my mail works, but I need to click continue each time I launch Outlook (for Mac 2011). There seems to be more to it than adding "@rogers.com" for some people...
For Outlook 2007 Tools - Account Settings - for each email address listed, hit "Change...", then under
User Name: here's where you add @rogers.com to your name, e.g. firstname.lastname@example.org, whereas before it was just "user"
Password: same as before
Hit Next - then Finish.
Was two problems - first they messed the certificate up, then after that was fixed, the new requirement for full user name including @rogers.com became necessary. I've no clue whether they will make it work without that. Thanks though for whomever discovered that!
Never astounds me how often a change in coding for an interface gets changed, and then no one ever tells the customer. We often figure it out on our own.
Not just rogers is guilty of this. It is what happens when we hire lesser quality or trained programmers, and teams to work on changes of any type, then save money by not carrying out communication to users.
Most companies, they call these "bug fixes" and we at least have a general idea what is going on.
The issue of the email will be yahoo, not sure who the certificate issue belongs to.
Using Apple Mail on my iMac, my original User Name (without the "@rogers.com") only appears under "Incoming Mail Server (POP)" [in Preferences > Accounts > Server Settings]. If I try to add the "@rogers.com", I get an error message. In other words, I cannot reconnect to the server if that requires changing my User Name.
As you're all aware, there have been several users with Certificate errors with their POP clients. Yahoo implemented a Change management activity to move existing Post Office Protocol (POP) services to a new POP platform.
As result some clients older than 5 years may prompt the users to accept the new certificate. When users clicked Accept for the new certificate they received Certificate Not Valid error.
There are some work arounds; Users can still receive their email by first logging into their webmail, then logging into the POP client. Also some users were able to resolve their issue by adding @rogers.com to their already existing username in the POP client settings.
We are investigating the problem with Yahoo Engineers and will update the Community once the issues are resolved.
Thanks everyone for your patience and understanding!
I was getting the POP Certificate error all day Wednesday. As of Thursday I get the following error:
Task 'email@example.com - Receiving' reported error (0x800CCC92) : 'Your e-mail server rejected your login. Verify your user name and password for this account in Account Settings. The server responded: -ERR Server error - Please try again later. [SYS/TEMP]'
I was told by help desk that the problem is that Yahoo is not accepting any clients using POP and that they are working on resolving this.
Still not working today. Any idea when this will be fixed?
I use Outlook 2013 on Windows 10.
Here's what I think happened (5 different possibilities)
1) You didn't even check your email while the cert was invalid. And you already had your user name set up correctly, so after that user name change was made required by the system, you were just fine - WORKING FOR YOU NOW
2) You didn't even check your email while the cert was invalid. But since Yahoo now requires the full user name including @rogers.com in the account field and you just had it set to your user name, you had problems. But when you changed this, you were just fine - WORKING FOR YOU NOW
3) While the certificate was invalid, it prompted you to accept the invalid one, and you did NOT accept it. And you already had your user name set up correctly, so after that was made required, you were just fine - WORKING FOR YOU NOW
4) While the certificate was invalid, it prompted you to accept the invalid one, and you did NOT accept it. But since Yahoo now requires the full user name including @rogers.com in the account field and you just had it set to your user name, you had problems. But when you changed this, you were just fine - WORKING FOR YOU NOW
5) While the certificate was invalid, it prompted you to accept the invalid one, and you DID accept it. This messed up your system. Regardless of whether you set you user name or not, it's NOT WORKING FOR YOU NOW. You must clear that messed up certificate somehow on your system or get it to accept the real one again.
I luckily did not accept the invalid cert while the good was invalid. And my story was that I simply had to update my user name.
I'm really not following your logic. I've been with Rogers for several years and my email setup hasn't been changed since Rogers changed POP and SMPT settings long ago. This just started for me yesterday right out of the blue, and I have not changed anything in my account settings.
OK, I looked closer at my settings and added @rogers.com to my user name and it worked. Thank you for taking the time to do that.
Does anyone know if Rogers advised anyone of this change, or are we all shooting in the dark? I haven't seen anything from Rogers myself.