Can someone please add

In T3537#106396, @Xv wrote:

I have some progress and a step back.
Turns out that one of the installed plugins was causing the problem: "PDF Converter 7.1 Outlook Add-in".
I disabled all plugins (except GpgOL) and then enabled them back one by one.
With PDF Converter add-in disabled I'm now able to see the decrypted email body (sent from myself).

Can someone please add

Hi, thanks for the test. This sounds a bit like T3378 if the central component "gpg-agent" hangs everything relying on it may also hang. :-/

We have similar reports in our message board.

I put it at high priority because i want to check / fix this before the next release.

Ok I'm pretty sure that the Google MAPI provider is the problem because it likely has some different Data structures.
For Sender we already have three fallbacks as it's saved differently for Exchange over MAPI, Exchange Active Sync and IMAP. So we probably need another fallback for Google Sync >.<

Thank you, too for the report and testing.

Tested GpgOL 2.0.4-beta6 with Outlook 2010 32bit and Outlook 2013 32bit on Win 10 1709 64bit.

I have some progress and a step back.
Turns out that one of the installed plugins was causing the problem: "PDF Converter 7.1 Outlook Add-in".
I disabled all plugins (except GpgOL) and then enabled them back one by one.
With PDF Converter add-in disabled I'm now able to see the decrypted email body (sent from myself).

I introduce GnuPG to my friend, yesterday. I saw this problem. It's on Windows 7, gpg4win 3.0.1 and enigmail.
Looking through this report, Windows 7 is common factor.

I use the Google Sync plugin to connect with our company Google Apps account. It also synchronizes the calendar entries as well as all other special stuff.
I'm quite sure that the standard POP/IMAP mechanisms in Outlook might not deliver the sender's address (however the receipient's address is contained in the logs above - my googlemail.com address).

I'm using the same Outlook 16.0.0.8625 on Windows 10 with a Gmail Account over IMAP and I have the Google Apps Sync plugin enabled. Everything works fine :-(
What is your senders account? Is that also GMail or something different. In the log I only see that the recipient is GMail.

I'm currently triaging. I give this high priority even if it is testing. We probably need a new GpgOL release soon as there were already some bugs fixed (e.g. Selecting many messages)

Thanks.
So GpgOL can neither figure out the sender's address nor the recpients. It then fails to do crypto because kleo does not know who it should encrypt to.

For now low priority until we receive additional information. From the report now I don't really understand the problem. Maybe T3459 ? as the report mentiones moving mails.

Done. Now Outlook does not crash anymore, but GPGOL emits an error dialog:

Dirmngr should no longer run as a system service. It's now started with user privileges on demand. The

12:33:30/13972/oomhelp.cpp:get_oom_int: Property 'BodyFormat' not found: 0x80040108
12:33:30/13972/oomhelp.cpp:get_oom_string: Property 'HTMLBody' not found: 0x80040108

To keep the tracker clean I'm closing this as a duplicate of T3476 since both problems are very much related. GpgEx would print Internal Error if Kleopatra crashes or behaves unexpectedly.

Here you are

The only way I can think of that this fails if that there are some old files from a gpg4win installation that was not cleanly removed lying around and failing to start.

Strange, do you have any other addons? Maybe some interference.

Indeed the PGP Inline handling should be more robust. If there is leading of following text it should not error out. But as there will always be problems with that I really recommend that you use a standard format (PGP/MIME) to communicate. Then the key would be just an attachment that could be imported in Kleopatra and all the data would be encrypted / signed.

tried to answer in the text with ###:

Normal priority as this should be looked into but is not dramatic.

What Kind of File were you attempting to Verify (e.g. S/MIME or openpgp, detached or embedded). Ideally if it was a public file I could try to reproduce.

Normal priority for now until we get more reports of this. For now we have to assume that while this problem is disastrous it happens rarely as we did not get many reports about this.

Thank you very much for your good and detailed report.

I need to look at the code. I remember that we used to flag executables as GUI applications so that they do not show the console at all.

So the error handling is improved now. We restore the original body on error and show the error in the tooltip of the GpgOL Status Icon.

I can reproduce it if I send and receive with Outlook 2010. I have some working mails in my Outlook 2010 though, this is the reason why I first thought that it did not happen for me. Looking at the same mails in Outlook 2016 works fine.

Thanks for the detailed report. I can't reproduce this behavior. Neither on my Outlook 2010 test system or my Outlook 2016 test system.
I can see several verification errors in the Log. First todo: Communicate the error and restore the original body.

While testing more I find this issue very irritating.

So the selftest fails and then Kleopatra crashes? Mmh I'll try to break my gpg4win installation in a similar manner.

Priority Low as it's partly a question and We can't reproduce (for me keygen is reasonably fast)

@PaulJ this sounds like a different problem. For you it does not show. In this report the pinentry open's in the background for file sign / encrypt.

I'm giving this normal priority because I can't reproduce this.

I'm closing this as a duplicate of T3459 even if this bug is older we used it to discuss side topics.

Hi, sorry this is a known issue. To quote the README:

I have installed the update now @JochenSaalfeld and will observe the behaviour over the coming days.
Somehow my Outlook in combination with the plugin messed with the registry. I could only permanently re-enable the plugin after removing all related registry entries in HKEY_CURRENT_USER. Otherwise it would not load on start anymore even if activated by me.

Thanks for the test!

Hello Jochen,

After having a look at the code base I guess this behaviour is intentional.

It could depend on the formatting in Outlook (changing hyphens etc.), e.g.
-----BEGIN PGP MESSAGE----- looks sometimes different in Messages.

Great, I'll do it :)

I fixed the problem with multiselection that caused a very similar log for me. The fix is now in 2.0.4-beta6

I'm pretty sure I've fixed it. It would be great if you could try with the latest beta (currently 2.0.4-beta6) from https://files.gpg4win.org/Beta/gpgol/ (just replace your gpgol.dll in the gpg4win/bin or bin_64 folder with the one from there. To confirm that it's fixed.

As I reported this myself and fixed it. -> resolved.

Well the key resolution handling and dialog needs some love. Thats on the todo. But this issue here can be resolved as the op says.

I think this can be resolved.
GpgOL in gpg4win 3.0 supports HTML Mails. There is no extra setting which variant is preferred for multipart/alternative mails because GpgOL reads that setting from Outlook and prefers the same that Outlook would prefer.

I can reproduce a similar behavior when selecting all mails in a large folder. This was for T3433 It's not a loop it's just a huge load of "Read" events Outlook sends GpgOL and GpgOL looks at every mail.

Thanks. I'll give that a go. The only issue here is that it takes quite a long, random time to happen so chances are a successful fix is one where I never revisit this ticket :-)

Indeed indeed. I can reproduce and see that GpgOL is very active when many mails are selected. This is a regression, it worked with an older MIME enabled version. I'll look at it.

The symbols are coming from the message class and are only updated when the mail is viewed and afterwards unselected. It might be that Outlook sometimes does not update the symbol when the message class changes after the message has been read once.

Somehow I expected such a report (too many open fds). We will need to replace our select based code by poll. However, I think this is more related to T3529.

I think I fixed your problem. We had a similar problem in the past and the fix there was not to invalidate the UI (Update GpgOL's status button) so quickly when the selection changed.

Hi,
thanks for your report. We already have this on our todo with high priority: T3514
I'm resolving this report as a duplicate.