As more MX server operators upgrade their server operating systems to disable SSL and enable TLS - following the mandates of the retirement of SSL as a valid encryption protocol, we are seeing this a lot. In fact, I've spent the last two weeks helping MX server operators sort this out and develop resolutions for their hosted customers.
Some server owners and operators actively applied patches and/or fixes for the SSL/TLS updates. Others used tools - many of which did not do a particularly good job, either; and still others manually manipulated their registry entries to effect the required changes.
The problem was created because the SSL ports, which were formerly valid, are no longer encrypted because the SSL V1.0, V1.1, and V1.2 are not encrypting any longer and the connections fail.
So, now the logical question: did you recently update your server's registry settings to get rid of SSL and enable TLS, per the requirements of the depreciation of SSL as a valid encryption?
If so, are your customers using SSL during their IMAP connection attempts to your SmarterMail server?
If you recently enhanced the security of your server by disabling SSL, and enabled TLS, and your customers are still using SSL IMAP, they should change to TLS IMAP on port 587 because the SSL ports are no longer valid.
Bruce Barnes
ChicagoNetTech Inc
brucecnt@comcast.net
Phonr: (773) 491-9019
Phone: (224) 444-0169
E-Mail and DNS Security Specialist
Network Security Specialist
Customer Service Portal: https://portal.chicagonettech.com
Website: https://www.ChicagoNetTech.com
Security Blog: http://networkbastion.blogspot.com/
Web and E-Mail Hosting, E-Mail Security and Consulting