"Re:" prefix on subject line disappears when editing encrypted, saved draft
OpenPGP addon for Mozilla Thunderbird
Brought to you by:
pbrunschwig
Note tht the "Re:" is removed from the Subject line of the opened draft editing window.
This is presumably a side-effect of the change in Enigmail 2 to encrypt subject lines.
I am experiencing this too. Enigmail 2.0.2 and Thunderbird 52.7.0 (64-bit) in Debian 9.
I found that it affects all my TB mail accounts (both email and Usenet accounts) regardless of whether I have Enigmail enabled on those accounts or not.
It affects both draft messages that user intends to send encrypted and draft messages that user intends to send unencrypted.
It is most disconcerting when posting messages to Usenet since it can often lead to broken discussion threads, a crime punishable by waterboarding.
I found a temporary workaround is to uncheck the box "Encrypt Draft messages on saving".
Thank you, Patrick, for a wonderful plugin and for your continued maintenance!
Last edit: SEC3 2018-04-21
fixed on master and 2.0-branch
The Send Later who originally reported this issue to me now reports (as of April 21), "Now when I click replied messages in my drafts folder that are awaiting to be sent later, another "Re:" is prepended, so the subjects become "Re: Re:"…"
But now Enigmail does not modify the subject for drafts anymore...
Hello, "Re:" prefixes are reproducibly removed from the subject when using "edit as new" even with the current version 2.0.7 of Enigmail, and though "encrypt saved drafts" is unchecked. Obviously, there's still something going wrong in this case.
Changed status to "open" since subject is inadvertently modified with "edit as new" function.
Hello? Knock knock? Is this thing on? This just bit me again today when I edited a message as new and it removed the Re: prefix from the Subject line without my noticing. This is email corruption. Can somebody please pay some attention here?
It's still on my to-do list. I haven't found a proper solution yet that works in all scenarios.
fixed on master. As far as I can tell, the remaining error concerned emails where the subject was not protected.