Windows 7: Thunderbird: Add Security Exception
I was using Mozilla Thunderbird 10.0 for email. I suddenly got this message:
Add Security ExceptionBelow that, there was an option to "Permanently store this exception" and buttons to Confirm Security Exception or else Cancel. Canceling didn't achieve anything: the same dialog came right back. I was afraid to click anything else. The site in question was linked to Indiana University, which seemed legit. I had gotten something like this before, using an earlier version of Thunderbird, but there the problematic email account had been Hotmail.
You are about to override how Thunderbird identifies this site.
Legitimate banks, stores, and other public sites will not ask you to do this.
Server Location: imap.exchange.iu.edu:993
Certificate Status
This site attempts to identify itself with invalid information.
Wrong Site
Certificate belongs to a different site, which could indicate an identity theft.
I wasn't sure why I was getting this. A Mozilla page said, "The problem usually arises when the mail server's certificate is invalid for some reason. . . . Often this problem takes care of itself, in that the mail server provider will realize that they have made an error with their certificate and will replace it with a corrected version." I had started getting this program maybe a year earlier. I didn't know if this meant that I was the only person at Indiana University using Thunderbird, or what the explanation might have been.
I didn't find anything on point in Indiana's knowledgebase. A search led to advice to make a change in Server Settings. To get there, I had to click Cancel with the "Permanently store this exception" box checked; otherwise the dialog wouldn't budge. Even so, I had to click Cancel a bunch of times to get out of there. I went into Thunderbird > Tools > Account Settings. I went to the Server Settings heading under the listing for the Indiana University account on the left side. The advice seemed to be that, in that area, I should go to the Security Settings area and set Connection Security to None, instead of its present setting of "SSL/TLS." Doing that changed the Authentication Method from "Normal password" to "Password, transmitted insecurely."
I wasn't sure about that. I looked further down that same thread. Someone else seemed to be saying that the address should be imap.exchange.iu.edu.:993, with a period before the colon. Staying in the Account Settings dialog, and looking specifically at the list of options on the left side, I moved from the Server Settings option down to "Security," the last option for the Indiana University email account. There, I went into Certificates > View Certificates > Servers tab. I saw that I had certificates here for Mozilla, Google, Yahoo, etc. It seemed like a legitimate list. I decided to go with the advice, which was to go into Add Exception and type https://imap.exchange.iu.edu.:993.
Before I finished that, I took another look at the Mozilla page. They said that the mail server provider (i.e., IU) should provide the necessary connection information. They said that the Add Security Exception option that I was just about to finish would make my email through that account nonencrypted and visible to third parties. Writers in another recent thread indicated that they, too, were having this problem. The list of certificates (for e.g., Google, Yahoo) seemed to indicate that they had done what was necessary to provide email security at some level, but Indiana University had not. I tried another search, but it led to surprisingly few hits, among which the main relevant reaction was puzzlement.
The Mozilla page seemed to be saying that you have three options in this kind of case. You can ask the mail server people to get it together. You can add a security exception -- or, as it appeared in my case at least, you would have to add a security exception if you wanted the program to be usable. Or you could switch to a different account. I wasn't sure whether switching to a different email program would provide another possible solution.
0 comments:
Post a Comment