Mailspring cannot connect to TLS1.3 only IMAP / SMTP servers.

[CRCinAU]

Objective

Mailspring cannot connect to TLS1.3 only IMAP / SMTP servers.

Testing Notes

Tested on Fedora 42 using the RPM install method.

Reported here, as it seems the discourse servers are currently down - leaving no path to report an issue at all.

Log of error shows:

----------IMAP----------
connect <mailcore::IMAPSession:0x7ffca98ea9d0>
ssl connect <imap_mail_server_name> 993 43
connect error 43

[CRCinAU]

Hunting around, this probably relates to:

• Insecure Dependencies Mailspring-Sync#9
• Stop building old versions of curl and OpenSSL into mailsync on Linux Mailspring-Sync#12

[bengotow]

Hey @CRCinAU thanks for posting this, sorry about the Discourse server, I took it down over the weekend to do a major version upgrade and address some issues with spam posts.

If you get a chance could you give this build a spin? https://mailspring-builds.s3.amazonaws.com/client/849c312/linux/mailspring-1.16.0-0.1.x86_64.rpm

I do think you're right that this could be related to the switch over to system OpenSSL, but I'm not 100% sure how offhand. If it launches and the dylib is found, I'd think it would work. 🤔

[CRCinAU]

@bengotow - I did try that built - it has an issue with libtidy as per: Foundry376/Mailspring-Sync#9 (comment)

I'm happy to continue testing in that issue - and leave this one for OpenSSL issues.

The old version of OpenSSL included prior wouldn't have support for TLS1.3 - so that's likely the cause of this issue. If we work on the dependencies in the other issue, it'll likely lead to this one being resolved too.

[randolf]

Is this issue still a work-in-progress? We're planning to move all our SMTP, POP3, and IMAP4 servers to TLS v1.3 minimum in the future, and I'd like to be able to recommend MailSpring to users who need alternative options to other eMail applications that don't support TLS v1.3. Thanks!

[compuguy]

Hey @CRCinAU thanks for posting this, sorry about the Discourse server, I took it down over the weekend to do a major version upgrade and address some issues with spam posts.

If you get a chance could you give this build a spin? https://mailspring-builds.s3.amazonaws.com/client/849c312/linux/mailspring-1.16.0-0.1.x86_64.rpm

I do think you're right that this could be related to the switch over to system OpenSSL, but I'm not 100% sure how offhand. If it launches and the dylib is found, I'd think it would work. 🤔

Yeah I think that Discourse upgrade broke the Lets Encrypt automated cert renewal. See #2511, #2508 and https://community.getmailspring.com/t/the-certificate-has-expired/13995/1

[bengotow]

hey folks, just following up on this one. We're about to release the next version of Mailspring which uses system OpenSSL as well as system libtidy and several others. The libtidy issue above has been fixed on Fedora using dlopen. (It turns out the soname is different between Ubuntu and Fedora.) I believe that the update will resolve this issue, but I'll check back in here when it's been shipped and we can verify

[mrbensley]

Hi @bengotow , do you have a rough idea when the next version will be released?
Currently I can't log in to Outlook and Microsoft 365 accounts due to authentication failing.

[AlessandroTischer]

I'm using latest version (1.17.0), but I still have issues logging into my university M365 account.

[MedLabs]

The same error for Google, GMX, hotmail etc...
Connection Error - Unable to connect to the server / port you provided. (IMAP)
the app is unusable

[alfureu]

Starting to be very annoyed by Mailspring. Lost connection to Google accounts, plus the Flatpak version remains on v1.16 without being updated... The app is indeed unusable

[bengotow]

Hey @CRCinAU,

Thanks for your patience on this one - I know you've been waiting since September. The dependency issues you identified (libtidy soname differences and OpenSSL version) have been addressed in recent releases.

We've implemented runtime dynamic loading for libtidy on Linux (#21, e74d252a) which handles the soname differences between Ubuntu and Fedora that were blocking things. We've also added proper TLS SNI support (#78, 3e4aea3c) and upgraded to OpenSSL 3.6 (#84, 3b963ed9), both of which are required for TLS 1.3 connectivity with modern mail servers.

However, I'm seeing follow-up reports that some users on the latest version (1.17.0) are still experiencing connection failures with Microsoft 365, Google, and other providers. Could you give the latest version a spin and let us know if TLS 1.3-only servers are working for you now? If you're still seeing issues, please share any error logs from the mailsync process.

You can download the latest from https://getmailspring.com/download.

If you continue to experience problems, please post details to https://community.getmailspring.com and we can dig deeper.

Thanks for hanging in there with us on this one.

[CRCinAU]

Hi Ben,

Thanks for the details.

I did try setting things up today using the RPM install on Fedora 43. I get a tray icon, but don't get a main window at all.

Running from the terminal, I get:

$ mailspring 
Running database migrations
App load time: 217ms
/usr/share/mailspring/resources/app.asar.unpacked/mailsync.bin: /lib64/libcurl.so.4: no version information available (required by /usr/share/mailspring/resources/app.asar.unpacked/mailsync.bin)

{"error":null}
[5752:0127/193522.899672:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:273] Unable to set image transfer function.
[5752:0127/193522.899692:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:191] Failed to populate image description for color space {primaries:BT709, transfer:SRGB, matrix:RGB, range:FULL}
[5752:0127/193522.901156:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:273] Unable to set image transfer function.
[5752:0127/193522.901185:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:191] Failed to populate image description for color space {primaries:BT709, transfer:SRGB, matrix:RGB, range:FULL}
Manual update check (updates.getmailspring.com/check/linux/x64/1.17.2-a312df89/anonymous/stable) returned 204
[5752:0127/193523.296717:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:273] Unable to set image transfer function.
[5752:0127/193523.296738:ERROR:ui/ozone/platform/wayland/host/wayland_wp_color_manager.cc:191] Failed to populate image description for color space {primaries:BT709, transfer:SRGB, matrix:RGB, range:FULL}
(node:5752) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.
(Use `mailspring --trace-deprecation ...` to show where the warning was created)

[tianlinzx]

Can this issue be resovled ?

[cfvescovo]

Same issue here

----------IMAP----------
connect <mailcore::IMAPSession:0x7ffd77da6720>
TLS ssl connect <my_mail_server> 993 43
connect error 43