Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Avatar for Username

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Ko téma oñeñongatúma. Ejapo porandu pyahu eikotevẽramo pytyvõ.

Confirm Security Exception [hangs] self signed cert

  • 2 Mbohovái
  • 1 oguereko ko apañuái
  • 2 Hecha
  • Mbohovái ipaháva Casey

joeywpg
joeywpg
more options

Hi there, I created a self signed certificate for use with sending and receiving emails. However, when I try to send or receive I get the following error message: "Unknown Identity" The certificate is not trusted because it hasn't been verified as issued by a trusted authority using a secure signature." When I click "Confirm Security Exception" it just hangs. On the server side the error is: fatal bad certificate. SSL alert number 42 any suggestions would be appreciated. Thanks

Hi there, I created a self signed certificate for use with sending and receiving emails. However, when I try to send or receive I get the following error message: "Unknown Identity" The certificate is not trusted because it hasn't been verified as issued by a trusted authority using a secure signature." When I click "Confirm Security Exception" it just hangs. On the server side the error is: fatal bad certificate. SSL alert number 42 any suggestions would be appreciated. Thanks

Opaite Mbohovái (2)

Matt
Matt
  • Moderator
  • Top 10 Contributor
more options

self signed certificates are getting like the dodo finding anyone that will allow them.

You might try disabling OCSP on preferences and see if disabling the validity checking helps. it makes things less secure, but ask others to trust your certificates really is not all that secure anyway.

Casey
Casey
more options

Had the same problem but was able to fix it using the ip address instead of the hostname at the servername. FYI: I am using a Dovecot server with a self-signed certificate. After changing this you should do File -> Get New Messages for -> Imap server and confirm the security exception (that should work now). Going back to the inbox should prompt you for the password (as you have a "new" server now).

After that it worked fine for me (in Thunderbird 102).