On 08.08.16 23:26, flapflap wrote:
> Ludwig Hügelschäfer:
>> On 08.08.16 21:51, Valentin wrote:
>>> One of my contacts writes me encrypted mails with (I guess) the Memory Hole
>>> feature[2].
>>
>>> When I receive a new (encrypted) mail, its subject is "Encrypted
>>> message" (like intended). Then I decrypt it and its "real" subject takes
>>> place. Since this subject stays there after my key gets locked, I assume
>>> the decrypted subject gets cached(?).
>>>
>>> However, Thunderbird doesn't recognize mails with encrypted subjects to
>>> belong together.
>>
>> It uses the "References" header. If your partners mail doesn't provide
>> one, Thunderbird can't sort it in threaded view. The "Subject" header is
>> NOT used for constructing the threaded view.
>>
>> Just look at the message source (CTRL-U on windows and Linux) and search
>> for the References header.
> 
> This is a very annoying problem in Thunderbird. (I asked the same thing
> a while back)
> 
> Basically in MemoryHole, the message outer header gets one (fresh,
> unassociated with previous emails) References field and the inner
> message header gets the correct References, matching to the replied to
> email. Enigmail with MemoryHole does all correct.
> The problem is Thunderbird, which uses the outer References field to
> place the email in the tree/hierarchy, then runs the decryption, and
> finally, it can read the inner email header. At this stage, it replaces
> the subject of the outer header with the correct one from the inner
> header. It could also read the References field and rearrange the email
> in the tree, but Thunderbird does not. Hence, you cannot use MemoryHole
> together with the threaded view :(
> 
> Ideally, someone would fix Thunderbird and delay reading the References
> field until the message has been decrypted and the actual References is
> known. However, Patrick Brunschwig replied to my email back then, that
> this is not a trivial task because the References parsing happens so
> early in message processing.

The implementation in the next major version of Enigmail will no longer
encrypt the "References" header automatically (you can still enable it
in a preference). I know this leaks more data than ultimately desired,
but it's still better than nothing.

-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