There's no losing as long as you're being the change you want to see. I will always send plaintext emails and I have the technical skill to dig into the raw email and decode the encoded HTML data manually or rip out the relevant authorization URL/strings.
You’ve just made the problem an externality. While you have the skill and desire to do that - and to be clear, as a mu user I do the same dance when I need - inbound messages are rarely the problem for me.
What is a problem is outbound messages. When I try to do (what I think is) the right thing and trim the message and reply inline or bottom post, confusion abounds. I’ve had messages missed because the recipients told me they thought I accidentally sent an empty reply and didn’t scroll past the “on July 24th, superkuh wrote:”
Whose fault is that? Is it the 20 people on the distribution list who learned email protocol from years of Outlook and not “the right places?” I don’t feel comfortable pushing that blame onto them.
> I’ve had messages missed because the recipients told me they thought I accidentally sent an empty reply and didn’t scroll past the "on July 24th, superkuh wrote:"
A common way to handle this when writing to people who aren't likely to expect an inline response is to put "Responses inline below:" at the very beginning, and then respond inline as usual.
I'll admit that, in the past, I passively-agressively did things like respond to emails inline and then use my editor to remove all quoted text before sending my reply.
