1658636 - migration profile

Status: RESOLVED INVALID

(Thunderbird :: Untriaged, defect)

Description

[[e-mail]]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0

Steps to reproduce:

Unable to import a profile from thunderbird-72 to thunderbird-78. It is possible the 2 profiles, new and old are not compatible. There should be a way to import an
older profile to a new thunderbird, rather than to have to reconfigure the
whole thing.

Actual results:

When importing the profile I get no new emails. The colors for the icons do
not show. Thunderbird does not send mail. I have to reconfigure the smtp
server settings.

Expected results:

I have just done a preliminary test so I am not sure what else does not work.

Comment 1

[Magnus Melin [:mkmelin]]

What do you mean by import? It's not possible to import from Thunderbird to Thunderbird.
Do you mean just starting to use the profile you used with 72 (and was it really 72, that only ever was beta?) now with 78?

Comment 2

[[e-mail]]

Basically what I tried to do is to update Thunderbird from 72.0b2 to 78.8. And I want to use the
same profile so that I don't have to redo all my settings. I hope this is clearer. Would it be better
if I stayed on the Beta channel?

Comment 3

[[e-mail]]

Sorry I meant 78.0. Not 78.8 I made a Typo

Comment 4

[Magnus Melin [:mkmelin]]

The profile should just continue to work yes.

We now require TLS 1.2, and the server is using outdated SSL versions. You can set security.tls.version.min 1 to allow TLS 1.0

nmap --script ssl-enum-ciphers -p 995 mail.ve2cii.com
Starting Nmap 7.80 ( https://nmap.org ) at 2020-08-12 22:20 EEST
Nmap scan report for mail.ve2cii.com (66.159.32.35)
Host is up (0.18s latency).
rDNS record for 66.159.32.35: dns1.canasoft.net

PORT STATE SERVICE
995/tcp open pop3s
| ssl-enum-ciphers:
| SSLv3:
| ciphers:
| TLS_RSA_EXPORT_WITH_DES40_CBC_SHA - E
| TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 - E
| TLS_RSA_EXPORT_WITH_RC4_40_MD5 - E
| TLS_RSA_WITH_3DES_EDE_CBC_SHA (rsa 1024) - D
| TLS_RSA_WITH_AES_128_CBC_SHA (rsa 1024) - A
| TLS_RSA_WITH_AES_256_CBC_SHA (rsa 1024) - A
| TLS_RSA_WITH_DES_CBC_SHA (rsa 1024) - D
| TLS_RSA_WITH_RC4_128_MD5 (rsa 1024) - D
| TLS_RSA_WITH_RC4_128_SHA (rsa 1024) - D
| compressors:
| NULL
| cipher preference: client
| warnings:
| 64-bit block cipher 3DES vulnerable to SWEET32 attack
| 64-bit block cipher DES vulnerable to SWEET32 attack
| 64-bit block cipher DES40 vulnerable to SWEET32 attack
| 64-bit block cipher RC2 vulnerable to SWEET32 attack
| Broken cipher RC4 is deprecated by RFC 7465
| CBC-mode cipher in SSLv3 (CVE-2014-3566)
| Ciphersuite uses MD5 for message integrity
| Forward Secrecy not supported by any cipher
| Weak certificate signature: SHA1
| TLSv1.0:
| ciphers:
| TLS_RSA_EXPORT_WITH_DES40_CBC_SHA - E
| TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 - E
| TLS_RSA_EXPORT_WITH_RC4_40_MD5 - E
| TLS_RSA_WITH_3DES_EDE_CBC_SHA (rsa 1024) - D
| TLS_RSA_WITH_AES_128_CBC_SHA (rsa 1024) - A
| TLS_RSA_WITH_AES_256_CBC_SHA (rsa 1024) - A
| TLS_RSA_WITH_DES_CBC_SHA (rsa 1024) - D
| TLS_RSA_WITH_RC4_128_MD5 (rsa 1024) - D
| TLS_RSA_WITH_RC4_128_SHA (rsa 1024) - D
| compressors:
| NULL
| cipher preference: client
| warnings:
| 64-bit block cipher 3DES vulnerable to SWEET32 attack
| 64-bit block cipher DES vulnerable to SWEET32 attack
| 64-bit block cipher DES40 vulnerable to SWEET32 attack
| 64-bit block cipher RC2 vulnerable to SWEET32 attack
| Broken cipher RC4 is deprecated by RFC 7465
| Ciphersuite uses MD5 for message integrity
| Forward Secrecy not supported by any cipher
| Weak certificate signature: SHA1
|_ least strength: E

Nmap done: 1 IP address (1 host up) scanned in 13.70 seconds

Comment 5

[[e-mail]]

I am working on the TLS issue at the server side. What I would like to do is to take tls ver 1 out of the server side. Since I am in
charge of the server, I can do this, but I need time. Ok I will try it again enabling tls ver 1. Even better I will
disable SSL connections in thunderbird till I can rebuild the server. I will let you know what happens.

Comment 6

[[e-mail]]

Good news, things appear to be working properly now. Might be an idea to have a pop up when
tls version 1 is used.