Patrick Brunschwig:
> On 15.04.16 12:04, flapflap wrote:
>> Hi,
>>
>> out if curiosity I tried the memory hole feature [0] in Enigmail by
>> switching extensions.enigmail.protectHeaders on in about:config.
>>
>> I noticed that the Message ID and References header fields are
>> (correctly) stripped from the outmost header but they are also missing
>> in the inner header.
>> As a result, protected headers/memory hole breaks email threading.
>>
>> Is it technically possible to resolve that problem, or is it a deeper
>> issue with the used RFCs?
> 
> Are you sure that the message ID header is stripped from the mail? I
> have in mind that I don't have write access to it, so I can't remove it.

Oh I'm sorry.  Yes, the Message-ID still exists in the outer header.

> The "references" header should be moved to the internal header. However,

That's correct as well: when decrypting a message from its source, I see
the References header.

> the problem is that once Enigmail decrypts this header, Thunderbird is
> already done, and there is no way to feed it back to Thunderbird. This

So that's then probably the reason why I didn't see the References
header in the "Header" view (above the message text) in thunderbird.

> is actually true for all headers; I had to implement quite some hacks to
> display the other headers in the GUI.
> 
> In other words, in the current state of Thunderbird, there is no way
> that message threading based on "References" could work if the header is
> stripped.

Are there plans/capacities to fix this in thunderbird?
Is there an alternative way to get message threading than using References?

~flapflap

_______________________________________________
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