With the Async encryption code I saw it multiple times that the message window stayed open when sending a message and then you could click send a second time.
This is confusing at the very least. Because I also saw once that this leaked plaintext when hitting send a second time I will disable Async encryption again for the Gpg4win-3.1.16 release.
| rW Gpg4win | |||
| rWe62daa2720b8 Disable async encryption in GpgOL again | |||
| rW09b4ba3a5a9a Disable async encryption in GpgOL again | |||
| rO GpgOL | |||
| rOaae2120d3e68 Enable sync encryption again | |||
In T6701 it was reported that this also occurs if we block outlook long enough in the send event and not only if we disable the window like we do with the async encryption.
I'm quite sure, that I have seen this multiple times on current versions. Not sure, if one could send it again, I think at least the body is empty.
I have no idea how to reproduce this, there is no pattern. It could as well be, that some server side thing is involved, which is not under our control.
Either I'm lucky and it just happens while the logs are enabled, or I'll try some auto loop with appium one day.
Luckily I tested T5374: GpgOL: Can't move a signed mail in Outlook from In-Mail folder to any other folder afterwards and found out, that with my current settings in gpg4win-5.0.2-beta2 @ win11 I can reproduce this every time by sending signed only mails (pgp and smime does not matter).
Regarding my settings, I only activated the security dialog:
To reproduce:
In the remaining window, the mail content is removed:
