Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

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.

GMAIL certificate failure after latest update of TB. Suspect Local Profile of previous version.

  • 1 reply
  • 1 has this problem
  • 5 views
  • Last reply by Matt

bondo
bondo
more options

The previous version of TB did not get an invalid certificate for Google's GMAIL SMTP server. The latest version (V78.12)after it was auto updated now gets this error (see attachment). I uninstalled and reinstalled TB. I checked the box to remove all user data when I uninstalled. Gets same error on reinstall and adding account information

I took a second laptop out that has never had TB installed and downloaded the current release and entered the same GMAIL user account. Everything works fine.

So it's not the user account. It's not Google GMAIL SMTP certificate. It's something that TB has wrong in the persistent data stored on the computer.

I get the same error with accounts on Outlook.com, Hotmail, Apple and Yahoo too.

I found a work around by making a change in the about:config for allowing the port number, but that doesn't work for more than one email SMTP server since they use different port number.

The previous version of TB did not get an invalid certificate for Google's GMAIL SMTP server. The latest version (V78.12)after it was auto updated now gets this error (see attachment). I uninstalled and reinstalled TB. I checked the box to remove all user data when I uninstalled. Gets same error on reinstall and adding account information I took a second laptop out that has never had TB installed and downloaded the current release and entered the same GMAIL user account. Everything works fine. So it's not the user account. It's not Google GMAIL SMTP certificate. It's something that TB has wrong in the persistent data stored on the computer. I get the same error with accounts on Outlook.com, Hotmail, Apple and Yahoo too. I found a work around by making a change in the about:config for allowing the port number, but that doesn't work for more than one email SMTP server since they use different port number.
Attached screenshots

All Replies (1)

Matt
Matt
  • Top 10 Contributor
  • Moderator
more options

why is it that this comes up with monotonous regularity and every time someone has to ask who issued the certificate which it found by clicking the view button. The vast majority of these certificates are issued by anti virus products (avast and others) and turning off mail scanning or approaching their support once they are identified as the issuer is the standard fix.