1611017 - V 73.0b1 Unable to login at server - peer using unsupported protocol

Status: RESOLVED INVALID

(Thunderbird :: Untriaged, defect)

Description

[Maurice]

Attachment: Thunderbird-Profile-setup-2.jpg

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:72.0) Gecko/20100101 Firefox/72.0

Steps to reproduce:

Two days ago my thunderbird was updated from 72.0b3 to 73.0b1 (32bit).
POP3 and SMTP settings: STARTTLS and Normal password

Actual results:

The new version is unable to download any new emails from the server even though they can be seen through a web interface: the status message 'connected to mail.tpg.com.au' is displayed for a few seconds and then disappears.
Emails cannot be sent either: 'Sending message failed - peer using unsupported protocol'.
I reinstalled the previous version and was obliged to create a new profile - all worked as expected - emails could be sent and received - but of course earlier emails and contact list were not accessible.
Created a separate installation of 73.0b1 (64bit) and a new profile and the same problems occurred. The attachments show two steps in the creation of the new profile with automatic server configuration. The second shows there was a problem logging into the server using IMAP, but when the protocol was changed to POP3, it was accepted. Nevertheless the installation was unable to receive or send emails.

Comment 1

[Maurice]

Attachment: Thunderbird-Profile-setup.jpg

Comment 2

[Maurice]

In order to use my original profile with 72.0b3 after it had been used with 73.0b1, I had to start with the --allow-downgrade option.
All good, except that I got caught by the automatic update to 73.0b1 again = aaggh. Had to disable auto update and reinstall the old version one more time.

Comment 3

[Magnus Melin [:mkmelin]]

nmap --script ssl-enum-ciphers -p 993 mail.tpg.com.au

... shows that server only supports SSL3 and TLS1.0. Those are now disabled as old and insecure.
As a workaround security.tls.version.min can be set to 1.

Comment 4

[musiquegraeme]

Could you possibly include something somewhere that tells people how to do this? I see that security.tls.version.min was reset when I updated to TB 76. When this comes out in a stable version a lot of people may be looking around for the solution and I didn't find it anywhere but here. Could we be a little more helpful in the error message?

Comment 5

[Magnus Melin [:mkmelin]]

The notifications for that are currently not working due to other changes. Should be working again after bug 1590474.