FS#60078 - [offlineimap] imaplib2: SSL error connecting imap.gmail.com: self signed certificate

Attached to Project: Community Packages
Opened by Eli Schwartz (eschwartz) - Sunday, 16 September 2018, 14:09 GMT
Last edited by Morten Linderud (Foxboron) - Thursday, 11 May 2023, 21:00 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Jaroslav Lichtblau (Dragonlord)
Morten Linderud (Foxboron)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No


openssl 1.1.1 automatically adds support for TLS 1.3 which causes some servers, like Google's SMTP servers, to provide invalid self-signed certificates if the client does not send the SNI.


Similar bugs for other software:  FS#60038   FS#60059   FS#60077 

Upstream bug for offlineimap: https://github.com/OfflineIMAP/offlineimap/issues/573
Root cause is imaplib2 (a fallback copy of which is bundled with offlineimap, and we don't provide a system package): https://github.com/imaplib2/imaplib2/issues/5
This task depends upon

Closed by  Morten Linderud (Foxboron)
Thursday, 11 May 2023, 21:00 GMT
Reason for closing:  No response
Comment by Carlos Dagorret (dagorret) - Tuesday, 23 October 2018, 19:37 GMT Comment by Eli Schwartz (eschwartz) - Tuesday, 23 October 2018, 20:48 GMT
No it isn't. That's a fork, which was submitted as a pull request at https://github.com/OfflineIMAP/offlineimap/pull/579

It contains no accreditation for the original work submitted upstream as https://github.com/imaplib2/imaplib2/pull/6

imaplib2 is dead upstream, and it seems like offlineimap wants to fork it in order to no longer be at the mercy of dead upstreams.
Comment by Toolybird (Toolybird) - Tuesday, 18 April 2023, 08:14 GMT
This is pretty old and stale. We are now on openssl 3.x.x and "python-imaplib2" is in the repos. Is it still a thing?