On 20.04.16 14:12, Muri Nicanor wrote: > hi, > > when encrypting a plain text mail with enigmail 1.9, the result is a > plain/text content inside a multipart/mixed content inside a > multipart/mixed content: > >> Content-Type: multipart/mixed; >> boundary="E9et5UOU6KtDxP5xhLR89J6KN4cB9PRqC" >> From: Muri Nicanor <[email protected]> >> To: [email protected] >> Message-ID: <[email protected]> >> Subject: test >> >> --E9et5UOU6KtDxP5xhLR89J6KN4cB9PRqC >> Content-Type: multipart/mixed; >> boundary="3pPODD9crmGBoRO4lFpdwkQfi0jFLSdmp" >> >> --3pPODD9crmGBoRO4lFpdwkQfi0jFLSdmp >> Content-Type: text/plain; charset=utf-8 >> Content-Transfer-Encoding: quoted-printable >> >> test >> --=20 >> muri >> >> --3pPODD9crmGBoRO4lFpdwkQfi0jFLSdmp-- >> >> --E9et5UOU6KtDxP5xhLR89J6KN4cB9PRqC-- > > is this is bug? why not put the plain/text content directly in the first > multipart/mixed content?
It's a _feature_. It repeats some of the important header such that the recipient can determine whether the headers where altered. Future versions of Enigmail and other email software will warn you, when these headers were altered. It's part of the "memory hole" project [1] that tries to standardize the protection of headers. -Patrick [1] https://modernpgp.org/memoryhole/
signature.asc
Description: OpenPGP digital signature
_______________________________________________ enigmail-users mailing list [email protected] To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
