Was working fine until yesterday but now getting the following error message when I try to send an email from Outlook using my virginmedia.com account
Task 'Bernard - Sending' reported error (0x800CCC1A) : 'Your server does not support the connection encryption type you have specified. Try changing the encryption method. Contact your mail server administrator or Internet service provider (ISP) for additional assistance.'
Also tried the following as I do have an old version of Office.
Enabling TLS 1.1 and 1.2 in Outlook on Windows 7 | Microsoft Learn
still no luck.
I ran the below on virginmedia.com and it does seem to support 1.2 and 1.3
SSL Server Test: virginmedia.com (Powered by Qualys SSL Labs)
| Protocols | |
| TLS 1.3 | Yes |
| TLS 1.2 | Yes |
| TLS 1.1 | No |
| TLS 1.0 | No |
| SSL 3 | No |
| SSL 2 | No |
knighthawk Interesting. How does that stack up with this response from a curl check:
TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (OUT), TLS alert, unknown CA (560):
* SSL certificate problem: self signed certificate in certificate chain
* Closing connection
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* Send failure: Connection was reset
* TLSv1.2 (OUT), TLS alert, unknown CA (560):
curl: (60) SSL certificate problem: self signed certificate in certificate chain
More details here: https://curl.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
C:\Windows\system32>
________________________________
Graham
I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media, I'm a VM customer. There are no guarantees that my advice will work. Please read the FAQs
Have I helped? Click Mark as Helpful Answer or use Kudos to say thank
Very strange.
I have just run the same against pop3 and smtp.virginmedia and that only supports 1.2
I think we just need a definitive answer to what has changed.
| Protocols | |
| TLS 1.3 | No |
| TLS 1.2 | Yes |
| TLS 1.1 | No |
| TLS 1.0 | No |
| SSL 3 | No |
| SSL 2 | No |
Managed to get it working, but only as IMAP, steps below.
1) IISCrypto and enabled all protocols.
2) Removed my previous pop3 and smtp account from outlook 2010.
3) Added a new account and let Outlook discover the settings.
At first it errored, saying it could not connect using encrypted connection, and asked to try an un-encrypted connection, of which I said yes and it setup the IMAP and I now can send and receive email.
Not Ideal but at least it is working.
I added a rule to the IMAP Account and this now moves anything inbound to my Outlook folders.
Regarding 0x800CCC1A error:
I'm already using IMAP and my email has had this fault for a week or more now (I've changed nothing to cause this).
I was using imap.virginmedia.com as incoming mail server -> changed this to imap.ntlworld.com - now working.
On the outgoing side I was using port 465 and SSL -> changed it to 25 None - now working.
Prior to this problem it has been working fine with the settings as they were. I really don't know what VM have been doing (they do!) but it's causing a lot of headaches for their 'customers' Just thought I'd pass this on in case it can help some others
are you using a vm or ntlworld email? Didn't work here with his normal password.
knighthawk wrote:Managed to get it working, but only as IMAP, steps below.
1) IISCrypto and enabled all protocols.
2) Removed my previous pop3 and smtp account from outlook 2010.
3) Added a new account and let Outlook discover the settings.
At first it errored, saying it could not connect using encrypted connection, and asked to try an un-encrypted connection, of which I said yes and it setup the IMAP and I now can send and receive email.
Not Ideal but at least it is working.
I added a rule to the IMAP Account and this now moves anything inbound to my Outlook folders.
No one should be using unencrypted connections to their email servers in this day and age. VM do still allow them (for reasons I disagree with intensely). However the fact is that if you are using unencrypted connections then your password is visible to anyone who can view the traffic between you and the email server.
While it may seem a valid workaround, it puts your security at risk. VM appear to have fixed whatever was breaking encrypted connections so you should go back to using the encrypted settings.
Thank you, I have setup the connection that I have had and it is now working fine.
Mike
I'm trying to fix this on behalf of my father with his old BY email account and having no luck so far. last night it was telling me/him that his encryption was wrong (on outlook 2016) today it's telling me on my machine (office 365) that the logon credentials are wrong, after I went through changing his VM login to a gmail address he never uses, so i could reset the app password. Looks like I now need to log into outlook with the standard imap/SSL settings and his BY address but the app password.....
except I can't get the app password because i don't have his phone on me for MFA, becasue i'm not him! Guess it shows why MFA is necessary!
Forum Team
Hi Robbijay thanks for posting and welcome back to our community.
Sorry to hear that you're having issues getting your father's email to work on outlook and for any inconvenience caused. Have you been able to follow the advice offered by knighthawk? And if so, what has been the outcome?
Regards
Lee_R
Well, despite being an IT admin for almost 20 years I’ve never heard of IIScrypto so I’ve not followed that bit, but I’d already tried with different encryption methods etc on his machine and it didn’t work
I tried setting an account for him on my PC and rather than encryption complaints it said the log in details were wrong (potentially the app pw) and because of MFA, I can’t get any further without taking my laptop to his house to play with his phone (far to complicated to try and talk him through it over the phone)
Robbijay You do need to set up an app password to use 3rd party clients such as Outlook etc.
Settings for all email programs is as follows
POP3
Server: pop3.virginmedia.com
Port: 995
Encryption type: SSL/TLS (SSL on older Outlook Clients)
IMAP (I would use this over POP3)
Server: imap.virginmedia.com
Port:993
Encryption type: SSL/TLS (SSL on older versions of Outlook)
In both cases username and password are as follows
Username: the users full email address - e.g Joe.bloggs@virginmedia.com
Password - App password that is set up on my.virginmedia.com
SMTP
Server: smtp.virginmedia.com
Port: 465
Encryption type: SSL/TLS (SSL on older versions of Outlook)
Authentication
My Server requires Authentication
Use same settings as incoming server
Note - Although older versions of Outlook have both SSL and TLS tick boxes, these are not what people think they are:
SSL = SSL/TLS
TLS = StartTLS
If you are using one of these clients (and you really shouldn't be in 2024) only use the SSL option.
Yeah I'd already set up the app password etc and had it working on a different,newer, system fine (i'm an IT admin so familiar with it but the first time i've had to use it).
There seemed to be two different issues - his system said the encryption method wasn't supported and setting him up on mine said the credentials were wrong. Setting up the app password got it working on my computer but his was still moaning about encryption.
We'd just resigned ourselves to buying my dad newer kit, when the out look password box popped up up (about 4 days after giving up) and i banged it in and it worked on his old stuff
got it to work on my Windows 11 machine with Office 365 straight away with the app password. Still no joy on my dad's Windows 7 computer and Office 2016 though. Can't believe Virgin do this without telling anyone. Its ridiculous.
And just like that…. Outlook asked for a password today. Typed in the new app password I created and set up four days ago and it all started working again!
Forum TeamHi Robbijay
Thanks for your update. We're pleased to hear the issue has now been resolved for you 😊
Hope you have a great weekend.
