I am not convinced. The issue at hand is that Enigmail _should_ switch to a proper encoding *before* performing the encryption, similar to what Thunderbird does (it offers to switch to a MBCS (UTF-8 being common choice) if it detects a character that it can not encode in the pre-selected encoding. As an alternative Enigmail _could_ provide an option to override the encoding for encrypted in-line messages so that it does not interfere with the rest of Thunderbird's encoding detection. Something similar to 'Always use UTF-8 for In-Line encrypted messages'. I am not trying to force a solution, since this may be a niche problem (for anyone that is not US/GB, and receives a message in a 1-byte incompatible encoding). But if Enigmail injects itself in such a way, that Thunderbird's functionality is short-circuited shouldn't Enigmail provide with a proper alternative? I'm raising this issue, because I often get messages from my colleagues that are forwarded or replied messages from clients/partners and these messages are commonly broken. I'm trying to convince them to use MIME, but there are a few alternative e-mail agents that lack support for PGP/MIME (K9 + APG, but the info may be outdated).
2016-03-06 23:22 GMT+02:00 Daniel Kahn Gillmor <d...@fifthhorseman.net>: > On Wed 2016-03-02 04:27:28 -0500, Lachezar Dobrev wrote: > > My outgoing e-mail is set to send in UTF-8. > > The 'use default encoding' option has a common negative effect: there > are > > numerous encodings that support Cyrillic, and not all mail agents (quite > a > > few web-mail agents) support MBCS properly, hence the use of the original > > encoding that the mail was received with is very useful, and when trying > to > > send a mail with content that does not match the encoding Thunderbird > will > > ask to switch to an Unicode character encoding. The last part is somewhat > > hampered when using Enigmail, it seems that the character encoding > > detection happens after Engimail has performed the encryption. > > > > My preferred solution to this issue (and other) is to send mail in MIME > > format, but I can not force that on other people. > > While you can't force it on other people, you can elect to do it > yourself. If you're sending or receiving text that uses anything other > than 7-bit clean US ASCII characters, character encodings and > inline-PGP-encryption are going to be an unresolvable issue. :( > > PGP/MIME works because it explicitly embeds the character encoding of > the cleartext inside the protected MIME part, so it cannot get out of > sync the way that inline PGP does. > > --dkg >
_______________________________________________ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
