Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Şu anda bakım nedeniyle sitemiz kısıtlı işlevsellik sunmaktadır. Mevcut makaleler sorununuzu çözmediyse ve bize soru sormak isterseniz Twitter’da @FirefoxSupport hesabından ve Reddit’teki /r/firefox subreddit'inden destek gönüllülerimize ulaşabilirsiniz.

Mozilla Destek’te Ara

Destek dolandırıcılığından kaçının. Mozilla sizden asla bir telefon numarasını aramanızı, mesaj göndermenizi veya kişisel bilgilerinizi paylaşmanızı istemez. Şüpheli durumları “Kötüye kullanım bildir” seçeneğini kullanarak bildirebilirsiniz.

Daha Fazlasını Öğren

security exception is being ignored even when permanently stored

  • 3 yanıt
  • 1 kişi bu sorunu yaşıyor
  • 3 gösterim
  • Son yanıtı yazan: Matt

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.

Tüm Yanıtlar (3)

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?

more options

For this account, it is a re-direct.

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?