From one user I have received a debug log of the current beta where it apparently crashes in the dtor of the mail object after send.

Cool! Thanks for testing :-)

Thanks for the help,

I still don't have any clue what could be wrong here.

I can't reproduce this. I sent myself a Mail with capitalized "Andre.Heinecke@intevation.de" while my key only has an identity for "andre.heinecke@intevation.de" and it worked as expected:

Mh, that is strange and indeed a bug if that is so. GpgOL should do some simple normalisation which should prevent exactly such a problem. I'll look into it.

With 3.1 ( https://www.gpg4win.org/version3.1.html ) the problem should be gone. We still have to block outlook when the inline editor is used but that left no artifacts in the past. And if a Mail Window is opened we do not block outlook anymore. We only disable it to show a modal dialog.

As this is easy to test and I tested it myself I think I can mark it as resolved.

Thanks for your help / report.

With Gpg4win 3.1.0 ( https://files.gpg4win.org/Beta/gpg4win-3.1.0-beta-current.exe ) GpgOL no longer uses Kleopatra for signing. So this problem can no longer exist.

I'm lowering the priority to Normal. I've done a lot of GpgOL work and Testing for the upcoming 3.1.0 release and have not seen this problem.

We have this now. There might be bugs but in general this works.

I installed 3.1.0-beta and tested all use cases, everything is working properly now.

Should work with the current beta: https://files.gpg4win.org/Beta/gpg4win-3.1.0-beta-current.exe Although the window mangement is still a bit "iffy" but we at least switch back the focus.

I've uploaded a beta for the upcoming 3.1.0 Version: https://files.gpg4win.org/Beta/gpg4win-3.1.0-beta-current.exe

Version 3.1.0 now supports sign & encrypt and sign only for G Suite accounts as long as there are no attachments on the mail.

Great.
I'll wait for v3.1.0 then.

From the log I can see that GpgOL picks up the wrong "Sender" address. It thinks that you sent the mail yourself and then the mail address <> signature does not match. So it is not flagged as Trusted.

I've started adding a workaround, but shelved it for now. Any workaround would not work for plain signed mails and would not be interoperable with other clients.

Ok, thanks!

Sadly this is a known problem, the workaround is to unselect the mail and then move / modify it through the right click menu.

Hi Andre

I'm not a fan of memoryhole. To say my criticism in one sentence: "Memoryhole is trying to sell the hide of the boar before it has been hunted."

The only other add-in that I use is Skype, but I`ve disabled that and re-uploaded the log. We are using Exchange 2010 SP3

Thanks. Error is there:

Thanks, file attached

That is weird, I've never heard of that before.

The button shows and I can select Sign or Encrypt but they don't register / stay selected they just have a grey highlighted background whilst hovering over them... they do not toggle / stay selected.

What do you mean by "Does nothing"? The button should toggle and then when you send the mail kleopatra should show a dialog to select the signing / encryption keys.

Hi aheinecke,
I did some tests with 2.0.7-beta10 and still found some issues.
The message I attached as a test case in previous comment is now properly handled, I see no "signature.asc" attachment and message is correctly tagged as trusted sender; this test message was sent from Evolution and I sent it to myself (sorry for not pointing this out before).

My test works now with this commit.

I think the problem is with the selction change event. When we query for selection item (1) we trigger an itemLoad event which apparently causes this behavior. I've disabled everything else in our event handling code so we don't touch the mail at all (non crypto mails we never touch much).

Thanks for the test and the example mail. Should also be fixed now.
While testing I also noticed that the sender email address was also not parsed correctly for these kind of mails and added some code to fix that.

I just tested version 2.0.7-beta8 x64 and I can confirm the bug is fixed, GpgOL can decrypt messages properly. Messages also appear to be properly signed.

Thank you. With that message I could reproduce the problem and have a fix. I now get to decryption failed / no secret key as it should be.

You can find the message attached.
Message has been saved from Outlook 2013.

Thanks for your report and analysis.

My first GUI Idea does not work. From the Ribbon I don't see a way to find the currently used account. I could only look at all accounts that are configured and check the WKS publishing state for all of them.

This is coming along nicely. It might take longer then with Kleopatra if the key is large (as the new resolver does a full keylisting on every start) but that should be OK and we have plans to optimize that anyway.

In my tests this is resolved with the commits mentioned here.

I think the reason for this is not Exchange Online but that I was using two explorer Windows and switched between Mails while the decryption on the slow exchange folder was still running. This triggered an invalidate_ui while the parsing was active and that then triggered a write / unload just like in T3523

My current idea is that if GpgOL detects that the provider supports a web key service and one of the following is true:

So I tried this on Outlook 2016 MSO (16.0.4639.1000) 32-Bit

Steps 1. and 2. are now implemented in the async-enc branch of GpgOL. The keyresolver patches are updated for me and partially commited.

I have not seen this. But I suspect that it would be fixed if our encryption no longer causes Outlook to become "unresponsive". I'm already working on this for T3509 and have a development version which already does the encryption in a way that the pinentry / key resolution are just a modal dialog over outlook and no longer block the GUI of Outlook completely.

1. Collect all data in OOM, then start a thread to do the encryption.
2. Do a proof of concept that this actually works and outlook lets us do it with our usual window message async handling.
3. Update my Keyresolver patches in Libkleo and build a "libkleo-tool" to do the key resolving.
4. Figure out Window Management / Create a Qt Overlay over the Mail window to block it from closing while encryption happens. This will resolve all bugs related to window mangement of the current key resolution.

From your log I can see that the verification fails with "Unsupported Protocol" which is weird in itself. But at least with the fixes for T3538 (they are included already in your version) it should then show the unverified body. So this is a second problem. I tried to reproduce this for sent mails but even if deliberately break them they are displayed correctly.

Hi Andre, thanks for your help.

I can understand your reasoning, it makes sense.

We are always looking for ways to improve the messaging but the idea here was no keep it as simple as possible.

Depends: Not everything you see has been protected by the signature. Thus such a description would need to go into more detail.

The fix was released with Gpg4win-3.0.3

as your behavior is unusual please verify that no other Addons interfere, we are still trying to figure out if there are incompatible other addons. So please try to disable any other addons and try again.

No more reports of this since 3.0.2. With 3.0.3 I fixed an additional memleak which should further improve this. Resolved for now.

Multiple confirmations -> Resolved.

With git bisect I tracked it down to a0326ffb755c4a49a259cea3d83831d9ede7d5d9

Hi @aheinecke
Its also german:

GpgOL should use the same language detection code that GnuPG also uses. If you open a command line (cmd) and run "gpg" in that command line is it also in german?

I've noticed that myself and the cause for this is the code which we use to ensure that the key resolution dialog of Kleopatra opens in the foreground.

Thanks again for the test, your patience and the report :-)

:-)
I can confirm, that 2.0.6-beta14 is working and until now, Outlook did not crash :-)
Great work, thanks!

Ok so I found out that you could even trigger this bug without persistent options just by activating and deactivating any S/MIME option on a mail. This somehow changed the behavior of Outlook.