Info: February 20, 2008 Posted by: Jay 3 comments

I use Thunderbird 2.x to check my office mail at home, and one of the so-called security improvements is that it is much more strict about SSL errors than Thunderbird 1.x or Outlook. That is to say, if it hits an SSL error, it just won’t connect. At all.
Over this past weekend, an update to our mail server clobbered the SSL certs, making them invalid. Encryption works as normal, but the certificate is not valid. So Thunderbird stopped working. That’s all well and good guys, but I still need my email.
I found out that you can set up exceptions by going to:
Tools | Options | Advanced | Certificates | View Certificates | Servers | Add Exception
(yeah, that’s easy to find)
Once there you have to enter the path to the mail server. Except that it only takes https:// addresses (as far as I could tell), and the exceptions are made on a port-by-port basis, so you can’t actually make an IMAP exception this way. But that’s ok, we’ll figure it out. Go ahead and make an exception for the https:// address (assuming your mail server has webmail and that it is using the same certificate).

Now here’s the trick, click ok to the 50 dialog boxes you opened up to get to this point, and close out of Thunderbird. Go to your Thunderbird profile, on windows that would be %appdata%\Thunderbird\profiles\[some random characters].default
Locate the file cert_override.txt and open it in a file editor that understands linux style linebreaks (i.e. not notepad; wordpad is a worthy consideration).
Ignore this line:

# This is a generated file! Do not edit.

The next line down should be your mail server followed by a bunch of certificate information. It should start like this: mail.server.com:443.
You need to change the 443 to the port your mail server uses, in my case, 993. If you want it to work for 443 and 993, just duplicate the line, leave the old one at 443 and make the new one 993.

Save the file and start Thunderbird. Voila!