Non-overridable TLS Error Occurred trying to connect to imap.plus.net
Categories
(Thunderbird :: Security, defect)
Tracking
(Not tracked)
People
(Reporter: mark, Unassigned)
References
()
Details
(Whiteboard: [support])
Attachments
(1 file)
|
10.13 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.23 Safari/537.36
Steps to reproduce:
Updated to beta 86
Actual results:
Error occurred on initial "Get Messages".
Expected results:
Retrieved emails (imap)
Unable to retrieve emails
Comment 2•5 years ago
•
|
||
Hello Mark,
- From which version of TB were you updating?
- What are your server settings?
≡ > Account Settings > YourAccount > Server Settings - Are they matching the provider's instructions? https://www.plus.net/help/email-guides/how-to-set-up-plusnet-email/
Trying to ping imap.plus.net, it was not responding - maybe down sometimes?
Ran nmap on this and the supported TLS version is 1.2, so that should be fine.
nmap -p 993 -Pn --script ssl-enum-ciphers imap.plus.net #imapSSL
| TLSv1.2:
| ciphers:
| TLS_RSA_WITH_3DES_EDE_CBC_SHA (rsa 2048) - C
| TLS_RSA_WITH_AES_128_CBC_SHA (rsa 2048) - A
| TLS_RSA_WITH_AES_128_CBC_SHA256 (rsa 2048) - A
| TLS_RSA_WITH_AES_128_GCM_SHA256 (rsa 2048) - A
| TLS_RSA_WITH_AES_256_CBC_SHA (rsa 2048) - A
| TLS_RSA_WITH_AES_256_CBC_SHA256 (rsa 2048) - A
| TLS_RSA_WITH_AES_256_GCM_SHA384 (rsa 2048) - A
| TLS_RSA_WITH_CAMELLIA_128_CBC_SHA (rsa 2048) - A
| TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (rsa 2048) - A
| TLS_RSA_WITH_RC4_128_MD5 (rsa 2048) - C
| TLS_RSA_WITH_RC4_128_SHA (rsa 2048) - C
| TLS_RSA_WITH_SEED_CBC_SHA (rsa 2048) - A
| compressors:
| NULL
| cipher preference: client
| warnings:
| 64-bit block cipher 3DES 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
Imap works on Blue Mail Android 11 and Outlook (I've had to revert to Outlook reluctantly).
There was an TB beta version yesterday and it hasn't worked since.
Settings have not changed.
So I've no idea what has happened but I turned TLS off, which was always on, an it now works. Not sure if it's a TB issues or and ISP one.
Hello
I have the same problem but right now.
By upgrading to thunderbird 91.4.0 (64-bit), I add problem connecting to imap.laposte.net
Non-overridabe TLS error occurred. Handshake error or probably the TLS version or certificate used by server imap.laposte.net is incompatible.
I use imap.laposte.net:993
If I change settings to Server setting > Connection setting > Connection security to NONE, it works
Switching again to SSL/TLS in Server setting > Connection setting > Connection security, it stops working
$ openssl s_client -showcerts -connect imap.laposte.net:993 -servername imap.laposte.net
No problem seeing in this command, same here: https://www.sslshopper.com/ssl-checker.html#hostname=imap.laposte.net:993
Comment 7•4 years ago
|
||
I have the same problem, and when i view tcp packet via wireshark, it seems that TB has to have full certificate chain for tls connection.
Below is the detail decrition:
Running TB 98b2, I can confirm this bug running on Win 10 Pro x64 21H1.
Using FairMail on my Android smartphone (with all available TLS hardening turned on), receiving & sending mail works flawlessly.
Using my mail server's web UI, same result applies.
Forgot to mention:
- Using @Jeremy's link in comment #5, that site states perfectly valid configuration of both, my cert (issued by Let's Encrypt) & the mail server itself.
- Same applies to https://www.ssllabs.com/ssltest/analyze.html which tests way more regarding the cert & the server's security in general.
- My cert is an ECC-based one with a key length of 384 bits & OCSP stapling set to being required, but while Firefox is perfectly fine with this cert, TB fails to connect.
Until this bug is fixed, TB remains unusable for me.
Comment 10•4 years ago
|
||
@Wayne Mery, can you please update this bug's details so that it gets the proper dev's attention - after all, it's an S2 bug according to that severity's definition:
S2 | (Serious) Major functionality/product severely impaired or a high impact issue and a satisfactory workaround does not exist
Comment 11•4 years ago
|
||
I'm not really in a position to judge how this should move forward. But let's move it to a better place.
Comment 12•4 years ago
|
||
Thanks for the update, but please help me help you (not "you" personally, but "you" as TB dev team) to get this picking up pace way more than right now, i. e. confirmed & proper severity status - after all, the reporter (Mark), Jeremy & I can't use TB at all until this bug is resolved.
So, what needs to be done or who needs to be contacted where & how to get this done? I'd expect to resolve this within 2 weeks max.
Comment 13•4 years ago
•
|
||
This person seems to have a conflict created after a Windows OS update.
I would like to draw attention to this link:
https://www.askwoody.com/forums/topic/tls-error-when-running-thunderbird-daily-accessing-outlook-office365-com-server/
Person was experiencing same issue based on image they posted. They were using 'Daily', but you should reinstall same version as you are currently using. This issue also occurred after a Windows OS update.
I located this comment:
Issue has been resolved.
I uninstalled all Windows Updates from Jan 11 onward (2022-01 Feature update to Windows 10 21H2 and 2022-01 Quality Update to Windows 10 21H2), and also uninstalled Daily.
I then reinstalled Daily from Jan 11 and let it update, and let Windows Update bring that up to date. Everything is working properly now. Not sure what the issue was, but it is now solved.
Could all of those people effected by this problem try the same process to see if it resolves the problem and report back on your findings.
Comment 14•4 years ago
•
|
||
Attention for all those effected - you may like to try the following before following my previous comment.
try the following and report back on results
In Config Editor - set preference:
'security.tls.version.min' to 2
restart to test
If not working then set:
security.tls.version.enable-deprecated = true
Please report back on results.
In 'Config Editor'
Type : tls
please post image showing the all contents, so all settings are known for those with issues.
Comment 15•4 years ago
|
||
(In reply to Anje from comment #13)
(...)
Person was experiencing same issue based on image they posted. They were using 'Daily', but you should reinstall same version as you are currently using. This issue also occurred after a Windows OS update.
I neither use "Thunderbird Daily" nor do I even know what it is. To me, it seems like that's a mail account or some news site the person over at your link uses in conjunction with TB.
(...)
Could all of those people effected by this problem try the same process to see if it resolves the problem and report back on your findings.
No, I can't. Besides, it's not an OS issue & not even a mail server issue.
The person over at your link simple did the "classical" sweeping blow, i. e. stuff that neither fixes nor helps fixing the issue in question.
(In reply to Anje from comment #14)
(...)
try the following and report back on results
In Config Editor - set preference:
'security.tls.version.min' to 2restart to test
If not working then set:
security.tls.version.enable-deprecated = truePlease report back on results.
None of the above fixed the issue.
(...)
please post image showing the all contents, so all settings are known for those with issues.
Pressing CTRL+V didn't insert any screenshot picture, but the settings are all unset anyway, i. e. remain with TB's default values.
Is there any "debug switch" or advanced preference to toggle connection debug output, at least in the activity manager and/or dev tools console, so that I finally get to know the actual hiccup that causes the handshake error?
Because the message is pretty useless anyway as it does not tell what caused the handshake to fail..
Comment 16•4 years ago
|
||
(In reply to Martin from comment #15)
(In reply to Anje from comment #13)
(...)
Person was experiencing same issue based on image they posted. They were using 'Daily', but you should reinstall same version as you are currently using. This issue also occurred after a Windows OS update.I neither use "Thunderbird Daily" nor do I even know what it is. To me, it seems like that's a mail account or some news site the person over at your link uses in conjunction with TB.
There are different versions of Thunderbird - Daily and Release and Beta
As I said "They were using 'Daily', but you should reinstall same version as you are currently using. "
You report running beta versions which I presume you do as a means of helping sort out potential problems.
(...)
Could all of those people effected by this problem try the same process to see if it resolves the problem and report back on your findings.No, I can't. Besides, it's not an OS issue & not even a mail server issue.
The person over at your link simple did the "classical" sweeping blow, i. e. stuff that neither fixes nor helps fixing the issue in question.
Uninstalling and reinstalling Thunderbird does not involve a 'sweeping' blow as it has no effect on Profiles.
That case at the link occured immediately after a Windows OS update, but it is unknown if that occurred in your case. But you are using Windows OS and also a TB beta version. It would be useful to know if the Windows update was involved with this problem. You could check your computer update history to see if anything coincided.
(In reply to Anje from comment #14)
(...)
try the following and report back on results
In Config Editor - set preference:
'security.tls.version.min' to 2restart to test
If not working then set:
security.tls.version.enable-deprecated = truePlease report back on results.
None of the above fixed the issue.
Thanks for feedback.
(...)
please post image showing the all contents, so all settings are known for those with issues.Pressing CTRL+V didn't insert any screenshot picture, but the settings are all unset anyway, i. e. remain with TB's default values.
You would use the screenshot to create a jpg image file using a simple program like 'Paint' and then upload the image - at the top of this bug report is the 'Attachments' section - click on 'Attach new file'
Comment 17•4 years ago
|
||
(In reply to Anje from comment #16)
There are different versions of Thunderbird - Daily and Release and Beta
As I said "They were using 'Daily', but you should reinstall same version as you are currently using. "
You report running beta versions which I presume you do as a means of helping sort out potential problems.
Ah, I see. It's a misnamed nightly build then.
I don't use that version, I'm on the beta channel - not due to the reason you suspected, but anyway: reinstalling the latest beta version didn't fix the issue.
Uninstalling and reinstalling Thunderbird does not involve a 'sweeping' blow as it has no effect on Profiles.
That would still suggest it's an issue solved by simply copying the exact same binaries used prior to the reinstall - which to me seems pointless.
That case at the link occured immediately after a Windows OS update, but it is unknown if that occurred in your case. But you are using Windows OS and also a TB beta version. It would be useful to know if the Windows update was involved with this problem. You could check your computer update history to see if anything coincided.
That link's case talks about Windows 10 21H2 while I'm at 21H1 (didn't receive the update, yet).
So, that's an actual difference. But instead of further "digging around", I already asked for a toggle in order to reveal the actual step that failed in the TLS handshake process.
Thanks for feedback.
You're welcome.
You would use the screenshot to create a jpg image file using a simple program like 'Paint' and then upload the image - at the top of this bug report is the 'Attachments' section - click on 'Attach new file'
I'll guess, I'm too much used to GitHub & StackOverflow.com which both allow for CTRL + V paste an image by doing the upload process silently in the background.
Anyway, settings are still as they were upon installation several years ago. Do you really need a screenshot then?
Description
•