Gracefully handle plain text emails following conventions
There are lots of popular email clients/front-ends out there (eg Thunderbird, Sylpheed and even gmail) that follow a time-tested set of conventions for handling plain text mail.
Protonmail currently doesn't follow many of those conventions.
One example. When you reply to a message, the original message should be be block quoted with angle brackets and prefixed with a little header like this:
On <date>, <email_from_field> wrote:
Quoted line 1. Something something.
On line 2 I say something about something.
Plain text emails should be a first class citizen in ProtonMail!
-
G R commented
I think this is working as expected now.
But I feel like the ProtonMail team never cleans up here. -
Tim commented
It would be cool if someone came up with a new system for replies for reducing redundant info. For example, instead of copying the past email (and thus by induction, all past emails in the conversation) the service could simply generate a unique ID for the email and include the ID of the response at the bottom, thus allowing even a tree, not just list, of emails to be linked. Not only that, but there could be a conversation ID associated with every first email. Then replies could simply be marked as part of that set with the ID.
-
sadassads commented
test2
-
Anonymous commented
test1