On 30 Jul 2019 19:21, Sherman Dickman wrote: > We see a lot of this, mostly Yahoo but also AOL, Verizon, etc. We do > not provide access to the config editor, so we're adding the > strictly.mime pref to the UI in Postbox 7. They are all part of the same club of what I call the "incapable". > > Just curious... would there be any harm in making strictly.mime = true > the default? What would the negative consequences be? Blow up e-mail by a factor of three? Compare 0xA0, one byte, to the string =A0. If someone writes in ISO/Greek, so using all 8bit characters from that code page, you have a factor of three throughout the entire message, not just sporadic characters. Same is true for UTF-8 if someone writes in non-ASCII, so Greek, Hebrew, CJK, Thai, etc. That's all 8bit stuff multiplied by 3. Also, for developers it's a nightmare to debug the e-mail source. Jörg.

Jörg Knobloch wrote on 30.07.19 19:28: > On 30 Jul 2019 19:21, Sherman Dickman wrote: >> We see a lot of this, mostly Yahoo but also AOL, Verizon, etc. We do >> not provide access to the config editor, so we're adding the >> strictly.mime pref to the UI in Postbox 7. > > They are all part of the same club of what I call the "incapable". It's all the same company https://en.wikipedia.org/wiki/Verizon_Media And... they lost a lot of customers since Verizon purchased them. Including myself.

This certainly affects more than just the Verizon conglomerate. A former employer had an Exchange environment with something called Proofpoint that did message scanning and mangling. Certain ways of sending an email with Thunderbird would trigger bugs like this. I had to enable the mentioned config setting to ensure all of my messages were readable. Unfortunately, IT did not support Thunderbird officially, and there were enough other problems with their setup that I was eventually told to "just use Outlook" like everyone else so I didn't waste any more time. I don't know if I have a point here, just sharing a user story. It would be nice for sure to have a preference to change versus going into about:config. If we have a blacklist, making it easily customizable like the cookies settings in Firefox seems like the way to go. -rob On Wed, Jul 31, 2019, at 00:01, Ben Bucksch wrote: > Jörg Knobloch wrote on 30.07.19 19:28: > > On 30 Jul 2019 19:21, Sherman Dickman wrote: > >> We see a lot of this, mostly Yahoo but also AOL, Verizon, etc. We do > >> not provide access to the config editor, so we're adding the > >> strictly.mime pref to the UI in Postbox 7. > > > > They are all part of the same club of what I call the "incapable". > > > It's all the same company https://en.wikipedia.org/wiki/Verizon_Media > > And... they lost a lot of customers since Verizon purchased them. > Including myself. > > > > _______________________________________________ > Maildev mailing list > Maildev@lists.thunderbird.net > http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net > -- Rob Lemley Build Engineer Thunderbird.net