This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

security exception is being ignored even when permanently stored

  • 3 பதிலளிப்புகள்
  • 1 இந்த பிரச்சனை உள்ளது
  • 3 views
  • Last reply by Matt

Gary Hooper
Gary Hooper
more options

Whenever I get new messages, I'm being asked to confirm a security exception, even after permanently storing it. This is occurring with two different email accounts. Preferences/Certificates lists both exceptions. The certificates are valid. Both are wildcard certificates, one issued by GoDaddy and the other by DigiCert.

Any ideas why theses exceptions are being ignored?

I'm on a Mac, with no anti-virus running, Thunderbird version 60.4.0.

Whenever I get new messages, I'm being asked to confirm a security exception, even after permanently storing it. This is occurring with two different email accounts. Preferences/Certificates lists both exceptions. The certificates are valid. Both are wildcard certificates, one issued by GoDaddy and the other by DigiCert. Any ideas why theses exceptions are being ignored? I'm on a Mac, with no anti-virus running, Thunderbird version 60.4.0.

All Replies (3)

Matt
Matt
  • Moderator
  • Top 10 Contributor
more options

Why are you being prompted for an exception in the first place? Is the server incorrectly configured or are you using cheap hosting?

Gary Hooper
Gary Hooper கேள்வியின் உரிமையாளர்
more options

For this account, it is a re-direct.

Matt
Matt
  • Moderator
  • Top 10 Contributor
more options

so your saying the server name on the certificate is not the one being connected to? OR is the certificate provider no longer being accepted, like Symantec and their subsidiaries?