On 2/05/14 8:37 PM, Antoine Polatouche wrote: > >> Thus enigmail can't do anythign with it. Being fastitious about > only sending plain-text email > avoids this issue. I'm not sure > what else can be done. This is not the issue: when reopening TB > enigmail decrypt the same message. There is still the multipart > message. The problem is that enigmail seems to ignore the message > at the time TB is receiving it.
Essentially you have two choices: 1) Use PGP/MIME and use whatever composition or encoding you like, including html if you insist. It will also natively support signing and/or encrypting of attachments. 2) Use PGP/in-line and restrict yourself to plain text. There may be some problems with other language character sets. The only real advantage to the latter is when corresponding with people using systems which can't handle PGP/MIME for reasons passing understanding (since pgp/mime has been around for quite some time ... insert pointed look at Android, K9 and APG here). Personally I opt for PGP/MIME with plain text, albeit with UTF-8 encoding and specific rules for the exceptions. Regards, Ben
signature.asc
Description: OpenPGP digital signature
_______________________________________________ enigmail-users mailing list [email protected] https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
