Bug 428431 - support the "memory hole" spec to encrypt/decrypt mail headers
Summary: support the "memory hole" spec to encrypt/decrypt mail headers
Status: RESOLVED DUPLICATE of bug 396366
Alias: None
Product: kmail2
Classification: Applications
Component: crypto (show other bugs)
Version: 5.13.3
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-10-29 13:13 UTC by m.eik michalke
Modified: 2021-02-22 01:03 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description m.eik michalke 2020-10-29 13:13:15 UTC
for a long time, thunderbird + enigmail offer a feature to move certain mail headers to the encrypted mail body. that way, it was possible to hide information like the mail subject (it's replaced by "..."). with current versions of thunderbird 78, this feature became mandatory for OpenPGP encrypted mails and cannot be disabled. this currently can create a mess in your inbox.


STEPS TO REPRODUCE
1. have someone send you an OpenPGP encrypted mail using thunderbird >= 78

OBSERVED RESULT
kmail shows the subject as "...". when the mail is decrypted, you find the missing headers at the top of the mail body. in grouped folder view, all messages sent by thunderbird users form one huge thread with subject "...", it is literally impossible to quickly find mails or even a particular mail thread.

EXPECTED RESULT
kmail should be able to replace the hidden subject with the actual one. it should also be able to keep the memory hole format in replies.

ADDITIONAL INFORMATION
i personally wouldn't want to use such a feature. but in order to be able to communicate with people who are unable to disable it, kmail should support it so that you can get human readable subject lines back.

here's the spec: https://github.com/autocrypt/memoryhole/blob/master/specs/draft-memoryhole.md
Comment 1 Sandro Knauß 2021-02-22 01:03:37 UTC

*** This bug has been marked as a duplicate of bug 396366 ***