NS Name=email.virginmedia.com DNS Name=webmail.virginmedia.com DNS Name=mail.virginmedia.com DNS Name=mail2.virginmedia.com DNS Name=mail3.virginmedia.com DNS Name=pop.virginmedia.com DNS Name=pop3.virginmedia.com DNS Name=imap.virginmedia.com DNS Name=imap4.virginmedia.com DNS Name=smtp.virginmedia.com DNS Name=autoconfig.virginmedia.com DNS Name=autodiscover.virginmedia.com
Well that's definitely not the correct certificate. ALTHOUGH I did uninstall Norton and install AVG myself. I got similar to yourself in terms of the certificate BUT in my case the connection to imap.virginmedia.com on port 993 still worked with no issues.
Whatever is going on, it's not an issue with the certificate itself..
I've seen one possible fix for this issue mentioned BUT:
1. It wouldn't be an option on Virgin Media's system. 2. You shouldn't need to do it anyway.
Based on the error message the client doesn't seem to be using the SAN list correctly and only authenticating using the CN (Common Name) on the certificate however this is just supposition on my part.
I've tested this server with Outlook 365, sTunnel, and OpenSSL's s_client tool and for me it's working on each.
I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more
Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks
use an up to date email client; Microsoft ceased supporting Outlook 2007 as of 10 October 2017
continue manually accepting the certificate
BTW: I agree with @ravenstar68 that the likely cause is incorrect processing of the Subject Alternative Name (SAN). Not sure why the issue was not occurring earlier other than maybe a recent update to Windows 10.