I am using an Antergos Linux (Arch Linux).

Implemented with https://commits.kde.org/kleopatra/805f5cfafe9f464de6f6a22619a74062ae781bfd

Please do not paste such long debug messages - they are not helpful. Please try to explain the error. From what I can see from that long dump the DNS server failed.

Indeed, this was lost by switching to the new dialog. Fixed with: https://commits.kde.org/kleopatra/005a28149fcb7f318676de47aee3014fc83b3f78

I can no longer reproduce this. We had another report about this were we also tested this and it's ok with recent GpgOL 2.x versions. -> Resolved

Fixed with https://cgit.kde.org/kleopatra.git/commit/?id=59ebe7da257131757f98e77912e39b3fd14ae3af Kleopatra was too agressive in the dialogs and always tried to stay on top. This makes sense for the Certificate selection dialog in GpgOL but not for the file dialog.

Nevermind. The keylist can be accessed by activating the line action (clicking on the button)

Suppose a client which connects stopped task of server on Windows. In this situation, if the client blocks on closesocket, that is, some user space work is needed for server side for closing socket of client side, this bug can be explained.

Does not happen for current GpgOL versions and OL < 2010 support in GpgOL is no longer maintained -> resolved

Fixed / Workarounded with https://commits.kde.org/kleopatra/9bef188fd2a2b820a63e9c7ed130c0990b7f3ce5
I was unable to reproduce this on Linux so no Valgrind / GDB. Fix is not pretty but works and ultimately we want to replace that dialog anyway.

If disable-check-own-socket can stop hanging, D454: assuan_close with nPth could be related.

Mostly done

Problem was indeed that QFile::Rename does not work across partitions.

It would be very helpful if you could export ("Save As") such a mail in Outlook and attach it here / send it to me. I don't have to be able to decrypt it but I would probably be able to figure out why it's not detected as a crypto mail.

The connection is a POP3 connection. Email server is a 3rd party email service provider. I doubt is an Exchange server (I believe they run a Linux server).
Switching to a different mail and back makes no difference - no email body displayed for the encrypted email.

I have created the file "gpg-agent.conf" in the path "C:\Users\<my user>\AppData\Roaming\gnupg\" with the following content:

It's working for me now with that config file as well so far. I'll keep watching too.

I added "disable-check-own-socket" to gpg-agent.conf .
Since 8 hours no "hanging".
I will watch it furthermore...

Could confirm a similar behavior with Windows 7 and Outlook 2010 using GPG4Win 3.0.1.
Time frame for loosing the decryption ability is about one hour or more.
Setting disable-check-own-socket in gpg.conf (didn't find gpg-agent.conf) resulted in "no data" error on all
encrypted e-mails.

As the crash is fixed and awaits release I think this issue is resolved. But that does not mean that we support G Suite sync. I don't see a quick fix :-/

Priority High as we should decide for the next release in which direction we should move.

Fantastic! I have these following issues:

Thanks for the confirmation.

Hi, sorry for coming back so late due to lack of time - but good news is: With GPGol 2.0.4-beta15 decryption now also works for us, great! Now we only have to check for a Outlook 2016 stability issue...

For reference here is @mcgrof's dump in a directly readable format:

00:29:33.472844 IP 192.168.4.7.10218 > 192.168.4.1.domain: 53039+ SRV? _pgpkey-https._tcp.hkps.pool.sks-keyservers.net. (65)
00:29:33.879268 IP 192.168.4.1.domain > 192.168.4.7.10218: 53039 FormErr 0/0/0 (65)
00:29:33.880719 IP 192.168.4.7.10218 > 192.168.4.1.domain: 51133+ Type0 (Class 8448)? _pgpkey-https._tcp.hkps.pool.sks-keyservers.net. (66)
00:29:33.902115 IP 192.168.4.1.domain > 192.168.4.7.10218: 51133 FormErr 0/0/0 (65)

I tried a bit to find a Workaround. As far as I can tell Outlooks built in S/MIME Support does not even work with GSync. If anyone can send S/MIME encrypted or validly signed mails trough GSync please let me know.

If more fine-grained control is needed with suspend-to-ram, we need to write kernel driver for USB access.

In T3378#106503, @raysatiro wrote:

I assume it goes in %APPDATA%\gnupg\gpg-agent.conf.

I learned suspend-to-ram functionality. Currently, for Linux, if we have USB driver in kernel, there are methods to handle suspend-to-ram and resume events. For user space driver by libusb, there is nothing and it should all work well by reseting after resume.

In T3378#106440, @werner wrote:

Can someone please add

disable-check-own-socket

to gpg-agent.conf to test whether this is the cause for the problem. ( note that I asked for this also in T3401)

Sorry for the delay, been a busy busy couple of weeks..

the warning message is probably too cryptic.

Many thanks! This bug is fixed in Gpg4win 3.0.1.

Can you please install the new version and check if the error still persists?

In T3424#106481, @aheinecke wrote:

Noticed one problem already. Google rewrites the PGP/MIME Mails we send into a multipart/mixed mail with the PGP Data as an attachment. I'll see if I can find a workaround :-/

In T3424#106481, @aheinecke wrote:

Noticed one problem already. Google rewrites the PGP/MIME Mails we send into a multipart/mixed mail with the PGP Data as an attachment. I'll see if I can find a workaround :-/

In T3424#106451, @aheinecke wrote:

Already handled the crash in: T3540

I need to get a test setup with google sync. Any chance someone has a test account for me?

I'll try to register myself for the free trial period.

IIRC, I red some hints on using a powershell module to switch the output to binary. I tries to find that mode, or weel its source or scrip) but to no success. It seems to be a common problem with powershell because it is not a real shell as we are used to (where many commands have a /b switch but that switching could also be done using setmode() ).

You're the hero!!!!

Noticed one problem already. Google rewrites the PGP/MIME Mails we send into a multipart/mixed mail with the PGP Data as an attachment. I'll see if I can find a workaround :-/

So I went through the google app sync setup and now have a test account.

I can reproduce the problem.

@aheinecke From a first glimpse, I think we got it. Great work!
I replaced both versions of gpgol.dll as adviced (surprisingly /bin was locked, I expected /bin_64 ).
Thereafter Outlook decrypted all "old" message instantly and without any problems.
Thanks for the effort you spent and the fast reaction time!

Setting this to resolved until we get reports to the contrary.

It was released.

Kleopatra will only expose the values that are settable through gpgconf. Messing with preferred hash algorithms is nothing a user should do as the defaults are thought through and discussed. Mostly such changes come from bad recommendations. So the GUI / gpgconf does not offer this prominently as we don't want to create problems for users.

As GpgEX only queries a UI Server (GPA or Kleopatra) this is a Kleopatra or GPA problem.
With Gpg4win-3.0 Kleopatra got the option "Encrypt with password" in the file encryption dialog, which does symmetric encryption. GPA does not offer this but as Kleopatra is our main UI for GpgEX I think this feature request is done.

The overhead of the start should be reduced by kleopatra as it uses a static c++ object that is only read once. Yes that might contain stale values but we don't expect users to meddle with config files while they have kleopatra open to edit the config.
Similar for GpgOL. Stuff like compliance is only queried once, (maybe twice?) during startup.

Can't reproduce and there were tons of fixes to gpgol in the meantime -> invalid.

Already handled the crash in: T3540

Thanks for the efforts. I will subscribe there to be up to date :-)

Oops I just noticed that this was already reported in T3424 which I somehow overlooked. Let's handle it there as there are more subscribers in that report and it's older.

So both your mails did show the exact same behavior for me. The PGP MESSAGE was shown in the mail and not attempted to decrypt.

Two versions of the same message as shown in the comment of 24th Nov.

I did some experiments with HTML Mails, Leading Text, Trailing Text etc. Everything worked fine for me.