Steps to reproduce: send a s/mime encrypted mail and after that disable s/mime in the GpgOL settings.
Click on and decrypt the s/mime mail in the sent folder. Change to another mail. Change to the s/mime mail again.
-> mail is decrypted
Expected: message that the mail can not be decrypted.
aheinecke says cause is 91c86d7cd53a190fa73f1b62372d74e331887a1c
I would give this low priority as we default to "S/MIME disabled" and this issue is no longer that relevant. But as it is a regression and I am pretty sure I know why it happens -> Normal.
Hello,
no, SMIME was not activated, the error still appeared and only when the GPG plugin was completely deactivated could Outlook read SMIME properly
In that case could you please attach a basic log from selecting an S/MIME Mail with S/MIME disabled? Activatable under GpgOL options / logging
Could it be that someone else in your company viewed the Mail with S/MIME in GpgOL enabled before you viewed it? E.g. in a shared folder?