> The right choice would be by Fastmail to cooperate directly with Evolution, Thunderbird, K-Mail, Apple Mail and help them were needed.

Funny, I've actually been sitting literally right next to the Apple Mail developers when Fastmail developers (who were sitting on my other side and across from me) helped them make Apple Mail work better with Fastmail and other modern mail servers, in various ways.

Fastmail is very active in the IETF, creating new RFCs that standardize modern email protocols [1] and adapting existing protocols to user needs [2].

Unlike Gmail and Outlook/Exchange cough cough, who I cannot even reach for serious bugs.

> native application (Gtk, Qt, Cocoa)

Do you know a cross-platform app (Windows, Mac, and Linux) that has many millions of users and is implemented natively on each of these platforms (Gtk, Qt, Cocoa, Win32 etc., respectively), not with JavaScript? I can't think of any.

There are limits in the real world. Software teams don't scale well. Corporate agendas are set 5 management levels above the developers. Most of the apps you mention have very serious technical dept that would require a complete rewrite to get out of. I speak from first hand experience of 25 years working on 3+ different mail clients, most of them with millions of users. Seasoned developers usually made their decision after much deliberation. The "right choice" (your words above) is often far more complex than an observer can possibly know.

Please don't throw peanuts at the developers from the peanut gallery [3][4].

[1] https://www.rfc-editor.org/rfc/rfc8621.html [2] Many like https://www.rfc-editor.org/rfc/rfc8474.html [3] https://en.wikipedia.org/wiki/Peanut_gallery [4] https://tenor.com/de/search/muppets-peanut-gallery-gifs

user:	benbucksch
created:	October 13, 2025
karma:	9