[Jennifer Mitchell]

Is there a way to correct Error Code: 80048888 without having to delete and recreate your email accounts on Nokia Lumia 920? I'm a windows smartphone power-user. I have utilized all of the 25 email accounts capacity and capabilities on my Nokia Lumia 920. It would be very disappointing to have to delete and recreate each email account. There has to be an easier solution.

Other types of phones such as Android, Symbian, etc allow you to locate the old certificate, delete it and reinstall the new certificate without having to make you delete and recreate each email account. If the solution for windows phone is to delete and recreate each email account, the programmers need to go back to the drawing board and find a better solution. Please advise.

[jfa1]

error code 80048848 - Microsoft Community Have you tried this?

[Jennifer Mitchell]

error code 80048848 - Microsoft Community Have you tried this?

My problem with Error Code: 80048888 does not stem from Messenger. It stems from the use of SSL Certificates on my Nokia Lumia 920. If a certificate expires and then renewed, it causes an error, specifically error code 80048888 even after you try to reinstall the new and valid certificate.

I've tried to reinstall the certificate with the application SSL Tester, it does not work. I have tried to manually install the new and valid certificate, it does not work. I'm at a loss. I didn't want to have to delete and recreate 25 email accounts on my phone which seems to be the only solution that I am finding online at this time

There has got to be an update for the phones with an easy fix. If not, I suggest it.

[Jennifer Mitchell]

How can I recommend the windows phone as an enterprise phone to any company with this issue?

[cr8n]

seriously. I have the same problem. Ridiculous. Can't wait to get my blackberry back next week.

[Huime]

Is there a way to correct Error Code: 80048888 without having to delete and recreate your email accounts on Nokia Lumia 920? I'm a windows smartphone power-user. I have utilized all of the 25 email accounts capacity and capabilities on my Nokia Lumia 920. It would be very disappointing to have to delete and recreate each email account. There has to be an easier solution.

Other types of phones such as Android, Symbian, etc allow you to locate the old certificate, delete it and reinstall the new certificate without having to make you delete and recreate each email account. If the solution for windows phone is to delete and recreate each email account, the programmers need to go back to the drawing board and find a better solution. Please advise.

Isn't that deleting cert and reinstalling takes the same time and effort as to set up the a new account since you just need to retype the email and password?

[markfive]

I didn't want to have to delete and recreate 25 email accounts on my phone which seems to be the only solution that I am finding online at this time
There has got to be an update for the phones with an easy fix. If not, I suggest it.

Can you provide a little more information?

Which version of Exchange in use? (I assume it's Exchange, a cert problem on outlook.com would be affecting lots of people)
Are all the mail accounts you have defined on the phone accessing the same domain?
Have the accounts worked correctly in the past?

[mfarlow]

I have the same problem. One of my POP3 accounts is throwing this error, and even if I delete and reinstall I get the same exact error. I'm not using SSL on this account, so I shouldn't even need a cert.

This is a deal breaker for me if I can't access my mail on the phone.

[Amit Dixit]

I am getting certificate error for m.google.com.. mails are not working.. Lumia 520 with Windows 8

[dlencastre]

Hello,

After a few trials, I was able to see the following issue as all of you.

In my case, I have an internal debian mail incoming ssl att por 993 and outgoing tls att port 465

Sending internal mail to my domain works, but sending to gmail or hotmail it fails and the problem was the error that appears to you.

What worked for me? After I have noticed that there was no place to set the doors, and knowing that ssl993 is common, the only uncommon was tls 465, so, in the sending server after the server name I set, the door. Like this mail.exemple.org:465

It worked.