On 03.02.17 13:14, Pablo wrote:
> Hello,
> 
> I noticed that Enigmail/Thunderbird wrap the content of encrypted+signed
> messages in one or two multipart/mixed mime-parts (see blow for example).
> 
> I guess it might be related to implementing memoryhole. But memoryhole
> would allow to put the protected headers into the first mime-part,
> regardless of its mime-type.
> 
> Can someone explain what the reson for the nesting is? Is it bound to
> stay like that?
> 

The adding of _two_ multipart/mime layers to a single plaintext message
is a bug (that I plan to fix for the Enigmail 2.0).

However, with Memoryhole, Enigmail will always add one multipart/mime
layer to each message. If that's a simple plaintext message, you will
end up with a multipart/mime message containing the plaintext body; if
the message that Thunderbird produces is already a multipart/mime tree,
then Enimgail will add another mulitpart/mime layer around it. The
reason is that I don't want to modify the string I get from Thunderbird
for adding the Memoryhole header.


> 
> My background is that I'm writing a piece of software that is trying to
> check if a message's content consists of a single text-part or whether
> it has multiple content parts.
> With the mentioned nested mime-structure I have to recursively determine
> if inside the multipart/mixed-part is another single
> multipart/mixed-part, which in the end contains a single
> text/plain-part. Or if on any of those layers there's another mime-part
> to consider as actual content.

And how do you handle multipart/alternative messages containing a
text/plain and a text/html part?


-Patrick

Attachment: 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

Reply via email to