Emails can be automatically displayed in threads¹ and proper clients do so (e.g. Apple Mail) with the help of Message-ID and In-Reply-To headers. There are no r

Emails can be automatically displayed in threads¹ and proper clients do so (e.g. Apple Mail) with the help of Message-ID and In-Reply-To headers. There are no reason to "hard-code" every previous message body into new message body when replying, i.e. quoting all the previous messages below/above your content. That's just plain stupid. Let the client do that for you in much better way. If you need to give more context in your reply, you can quote a line or two in the above of your text. This is usually only needed for long messages. An example: > This is a snipped from the message being replied to, i.e. quote. > Just a line or two to give some context. This is your text, where you you address the above concern. [More text...] > Another quote regarding some other issue. Your text here. The rule of thumb is to keep the quote shorter than your text. I know there exist many broken email clients, but the solution is not to adapt for them but just keep following good practises. That's the only way to get the bad clients fixed. In the long run, everything else leads to more broken situation. [1] https://cr.yp.to/immhf/thread.html https://cr.yp.to/immhf/thread.html