I'll try to reproduce it.

JJworx, thanks but I don't think a log would help me currently. With Gpg4win-3.1.3 I'm down in my main test instance to have these crashes ~0.25% (so I need around 400 verify/decrypt operations).

Strange, this happens when Kleopatra is unable to launch the gpg.exe / gpgsm.exe binaries. But in the log I can see that gpgconf is found and scdaemon / gpg-agent seem to work. So your installation is apparently fine.

Thank you for the report. I can't reproduce this behavior of course :-/ and from a first glance I also don't see any problem in your log. The last line logged says "GpgOL code is done, handing it back to Outlook".

Thanks for your report. Also thanks for trying the beta already. I think I know why this happens. Will be fixed!

@a_p3rson : Yes. I agree that I think that cepxuo meant something differently then you.

Removed the global trust model flag.

I've uploaded a Gpg4win installer with this fix (3.1.4-beta3) to https://files.gpg4win.org/Beta/current/

To avoid a traumatic change to Gpg4win I do not want to change the default trust-model globally. Changing it on demand will provide the freedom to "port" each application using GnuPG to the new trust-model independently.

Something like this was commited.

Yes we had a bug in 3.1.2 that when you had a contact group as recipients gpgol would silently ignore them and don't encrypt to them.

I think this might be a ticket in itself. If I send a PGP signed email to someone who then responds to me, there should ideally not be issues with it - although I think it would be important to separate which parts are signed and which are not.

Received. Thanks, so this is PGP Inline. Encoding handling in PGP Inline is always "Guessing" as it is no where defined which encoding is used for the message.

I've commited a fix and because this and another issue we might do a release sooner than originally planned.

If you like you can help by confirming that it also works for you by installing 2.3.1-beta11-STABLE-BRANCH-2-3 from https://files.gpg4win.org/Beta/gpgol/ as described under: https://wiki.gnupg.org/TroubleShooting#Manually_update_GpgOL_to_a_beta

Mmh no, I can't reproduce this and my initial hunch was wrong. We do in fact handle encoding in that case.

Added gpgol and gpg4win project tags as this is important for these projects.

I was unable to figure out what the difference is between the handling of Office files and other files and why it comes to this error.

Thanks for the report.

I can reproduce the issue and give it high priority. This is a curious problem of Outlook triggered by the improved send code in Gpg4win 3.1.3.

Da wir eine internationale Software sind bevorzugen wir in diesem Tracker Englisch. Ich hoffe das ist ok.

Thanks for the report. I was not aware of this but Indeed the fix should be easy. I think I already know the cause ;-)

Address book integration is in. What is still needed is to respect the overrides in the interactive key selection dialog.

Thanks for the details. I tried to reproduce it but again for me it works. Still I give this high priority as this can be a blocker in deploying GpgOL and we should fix it for the next release.

Gpg4win-3.1.3 was released on 08.31.2018