Live data from Hacker News

Known Bad Email Clients

emailprivacytester.com

31–40 of 69 posts

Re: Known Bad Email Clients

#31
So much text instead of mentioning the WebKitGtk doesn't provides that feature (currently). WebKitGtk is a good engine but somebody should to address that issue. Feels like a developer had only Epiphany as web-browser in consideration and forgot, that mail-clients prefer to not load images.

Evolution is a good mail client in general.

PS: Prefer always text-mail. When sending. When receiving.

Re: Known Bad Email Clients

#32
post #3

If only he made that much effort to get Chromium to fix the issue. The source of the problem is with a dependency of the email clients, not the email clients themselves. He is bothering small free software projects so that those small free software projects ask Chromium to fix the issue.

There is no dependency on Chromium. The projects are using WebKitGtk.

PS: I'm thankful that they don't use that thing from Google.

Re: Known Bad Email Clients

#33
post #21
post #6

Evolution is the only client on Linux (that I’m aware of) that fully supports Microsoft exchange and Google out of the box without any plugins. I used thunderbird for a long time, however I got frustrated so many times after things broke after every update because essential plugins stopped working. Yes, you may say Evolution UI is old, but the software is rock solid and softwares in general are more than their GUI. I…

Thunderbird has reportedly added experimental Exchange support in 140. Though I haven't figured out how to enable and test it :)

The support is only for the EWS protocol (MS Graph will probably come next year). You can enable it in beta by going to Config Editor (this is primarily for advanced users), searching for the preference "experimental.mail.ews.enabled" and setting it to true.

You would have to manually add the account. Currently only mail is supported. No calendar support.

See https://blog.thunderbird.net/2025/07/thunderbird-monthly-dev...

Re: Known Bad Email Clients

#34
post #3

If only he made that much effort to get Chromium to fix the issue. The source of the problem is with a dependency of the email clients, not the email clients themselves. He is bothering small free software projects so that those small free software projects ask Chromium to fix the issue.

[deleted]

Re: Known Bad Email Clients

#35

I wasn't aware of Balsa or Geary, but it's interesting to note that the author has mentioned that they are affected by GNOME's culture. I also have found the GNOME devs to have issues with admitting any fault at all, security or otherwise, but I wasn't aware of them being linked to any email clients other than Evolution - which I have been using. What's a good app for Exchange on Linux? I could use the web app, which…

A few years ago while working at a company that required Exchange, I was using Thunderbird with an addon called Owl. It was a paid addon, I think in the neighborhood of $10 to $20, and very much worth it. Full calendar integration and everything. Outlook users would be interested in my setup.

Re: Known Bad Email Clients

#36
post #21
post #6

Evolution is the only client on Linux (that I’m aware of) that fully supports Microsoft exchange and Google out of the box without any plugins. I used thunderbird for a long time, however I got frustrated so many times after things broke after every update because essential plugins stopped working. Yes, you may say Evolution UI is old, but the software is rock solid and softwares in general are more than their GUI. I…

Thunderbird has reportedly added experimental Exchange support in 140. Though I haven't figured out how to enable and test it :)

It was postponed. The release page is wrong :)

Probably Thunderbird tries it again with 141.

Re: Known Bad Email Clients

#37

[flagged]

You forgot to say anything about the fact that they've been sitting on a privacy bug for 15 months and have done nothing to address it. You forgot to say anything about the multiple things that the bug report says they can do, to warn their users and patch over the problem on their side. You forgot to say anything about how those suggestions were met with arrogant clown and face-palm emojis. You prefer to concentrate…

[flagged]

Re: Known Bad Email Clients

#38
post #3

If only he made that much effort to get Chromium to fix the issue. The source of the problem is with a dependency of the email clients, not the email clients themselves. He is bothering small free software projects so that those small free software projects ask Chromium to fix the issue.

It’s their product, IMHO it’s their responsibility. They can pressure the upstream library developers (good luck with that) or submit a patch, or switch to another library. The “not my problem” attitude from these projects is likely another good reason to avoid these projects.

Re: Known Bad Email Clients

#39
post #6

Evolution is the only client on Linux (that I’m aware of) that fully supports Microsoft exchange and Google out of the box without any plugins. I used thunderbird for a long time, however I got frustrated so many times after things broke after every update because essential plugins stopped working. Yes, you may say Evolution UI is old, but the software is rock solid and softwares in general are more than their GUI. I…

Same here. Nowadays we've switched from Exchange and use IMAP. I stay with Evolution because the client and integration is good. I like some design decisions in the UI. Evolution allows to use client-side decorations and a traditional menu bar, at the same time. And they've added integrated Markdown support lately. While an upgrade to Gtk4 is hopefully coming. I would love to see support for notes via IMAP, similar to how iOS does for many years.

PS: If your E-Mails are stored on an Exchange-Server (or: worse Azure) the discussed problem is the least issue.

Re: Known Bad Email Clients

#40
post #29

[flagged]

Evidently you did not read the linked issue very carefully as: 1. The issue still persists in the most recent upstream code of Evolution, having nothing to do with Debian or any other distribution 2. No patch is available to correct the security issue, and despite the puck passing it is not actually the responsibility of distro packagers to fix your own security bugs.

In upstream-unsupported versions, which are bore than 2 years old? Sure it is responsibility of the distro.

Even if it is unpatched upstream, it's perfectly fine to push the fix to master branch only and let distros backport. That's also why the bugs should be filed downstream, and distro maintainers will forward the bug upstream but only if not already fixed (so upstream won't get N duplicate bugs, where N is the number of packages).

At in any case, distro maintainers tend to behave better in upstream bugtrackers.

Post reply on HN