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

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.

Non-overrideable TLS error message on Thunderbird emails

  • 1 reply
  • 4 have this problem
  • 6 views
  • Last reply by gp

graeme.ching
graeme.ching
more options

What are the correct settings for email accounts in Thunderbird? On my new computer my accounts were setup in imap with SSL - but then changed to TLS, but I continually get this message " Non-overridable TLS error occurred. Handshake error or probably the TLS version or certificate used by server imap.actrix.co.nz is incompatible." I have a Dell Vostro 5620 laptop with Windows 11Pro. For my email accounts which settings should be correct for incoming and outgoing? Thanks - Graeme

What are the correct settings for email accounts in Thunderbird? On my new computer my accounts were setup in imap with SSL - but then changed to TLS, but I continually get this message " Non-overridable TLS error occurred. Handshake error or probably the TLS version or certificate used by server imap.actrix.co.nz is incompatible." I have a Dell Vostro 5620 laptop with Windows 11Pro. For my email accounts which settings should be correct for incoming and outgoing? Thanks - Graeme

All Replies (1)

gp
gp
more options

The correct settings should be given by your provider, usually Imaps (using TLS) uses port 993. For the authentication method, there is no real standard, try normal password, if it fails try crypted password, if it fails try Oauth2.