Comment by sombragris
14 days ago
> However, on more practical level, what are other options? Outlook, the desktop application works really well with local copies, is pretty low bandwidth and very familiar to end users.
Claws-mail (https://claws-mail.org) has a good working Windows version. Native desktop app, lightweight, extremely fast, able to handle multigigabyte inboxes for breakfast. The only drawback for some would be that it does not compose (although it can display them just fine) HTML mail, only text-only mail. This is an architectural decision.
I used this for a while. It doesn't display HTML emails just fine. It only supports a subset of stuff which -- as a geek is awesome because it protects me -- but would be hideous to give to a normal user. Literally less than half of my emails were readable.
As someone with deep experience in MIME encoding/parts, HTML for emails, and email client support for different HTML/CSS/image content, this is a sinkhole.
The world will be better off when we fork HTML so there is one standard email-safe version that all modern email clients support natively. There’s entirely too much security surface area to put arbitrary HTML into emails and expect any 2 email clients to render it correctly / the same.
Email needs its “no more IE6” moment.
> There’s entirely too much security surface area to put arbitrary HTML into emails ...
We manage it with browsers though.
Don't get me wrong, I've never liked html in emails to begin with. It's the same issue that markdown and every other rich text system has regarding where to draw the line. HN even strips most emojis (and I think that's a good thing).
2 replies →
Hopefully they are not getting exquisitely crafted newsletters in space.
Would it matter for this particular use?
Are you sure? You used the the Fancy HTML Viewer plugin, which uses WebkitGTK2? I never had any problems with HTML Mail rendering in Claws. Your experience must be clearly peculiar to yourself.