We recieved another mail by a customer about this issue today:

Sample Keys are now openly available at https://wiki.gnupg.org/SampleKeys

In T3577#107074, @aheinecke wrote:

So if the user had a "real" error it might have crashed instead of showing the error.

Thank you for your detailed report and the description for the reproducable setup! We will investigate in that issue!

So to get this straigt:

In T3419#106033, @cdeibert wrote:

Hi, VERY odd: My collegue has the exact same installation and environment (actually software deployment-based), she still is suffering to decrypt Mail encrypted with GPG4Win 2.3.2.

In T3367#106015, @RockyMM wrote:

Treat this as "Cannot Reproduce".

In T3419#105989, @hs wrote:

Just installed Version 3.0.1. From a first glimpse, it seems to work more stable in Outlook context.
But decrypting older plain text messages still fails.

by "just released" I mean: minutes before i wrote that comment. Since you mentioned gpg4win 3.0.0 in your post, I think you worked with the now old stable release.

This error doesn't seem to appear anymore in Version 3.0.1 and it doesn't exist anymore for me.

@cosimo193 ; gpg4win 3.0.1 just was released. May you check if this error still exists with that new version?

Since there was no action for half a year, I think this task can be closed.

@RockyMM Does this issue still persist with the newer Versions of Gpg4win, like 3.0.1?

@cdeibert, can you may check if this error still exists with the freshly released Version 3.0.1 of Gpg4win?

Unfortunately chocolaty is not managed by us and we don't have the knowledge about this. The Chocolaty Forums/Pages are the better place for this.

Hey @pkoevesdi, Gpg4win Version 3.0.1 was just released. Can you may download and install it and check if this issue still exists?

Hey @cprezalor, the new Gpg4win Version was just released. Can you please download it and check if this error still persists?

Hey, while installing the new Version for checking T3476, you may can check if this issue still persists as well?

@uwestoehr - Gpg4win 3.0.1 just hitted and tehre are several bugfixes including invoking kleopatra from the right-click menu. Can you please install the new version and check if the error still persists?

Version 3.0.1 just hitted. @madjari - may you can check if the various bugfixes in that version fixed your issue as well?

@simypat, version 3.0.1 just hitted. I can't recreate this error anymore. Can you verify this?

With the Release of Gpg4win 3.0.1 this error doesn't appear anymore for me while testing.

With the Release of Gpg4win 3.0.1 the Error doesn't appear anymore while testing with Windows 10 (64bit) with Outlook 2016 and Windows 7 (64bit) with Outlook 2010.

Tested with Gpg4win-3.0.0-beta17 with GpgOL-2.0.2-beta8 on Windows 10 (64bit) with Outlook 2016.

I enabled the error and did the following with Gpg4win-3.0.0-beta17 with GpgOL-2.0.2-beta8 on Windows 7 (64bit) with Outlook 2010

In T3442#105339, @aheinecke wrote:

In T3442#104402, @JochenSaalfeld wrote:

1. Mails encrypted with S/MIME are stored with "No Data" in the sent EMail folder, but arrive properly at the recipients (you will recieve a readable copy, if you add yourself to the list of recipients). This Issue breaks the GpgOL Plugin after some time which is leading to the described Problem.

Fixed with 474cc15d8e331c9def298dbbfe3b99e6c8cf8035

Versions Used: Gpg4win-3.0.0-beta17 with GpgOL-2.0.2-beta8 on Windows 10 (64bit) with Outlook 2016.

I tried to melt it down to a specific beta release with which it isn't possible anymore to decrypt send emails.

Since this is a bug that is related to two different parts of the gpg4win package, this bug now only cares about the GpgOL Issue, that GpgOL crashes and cant decrypt messages from the sent folder that are encrypted with S/MIME. All File Based Issues are belonging to Kleopatra are documentet in the KDE Phabricator (https://phabricator.kde.org/T7310).

What Version of Windows do you use? If you use an older Windows (pre 7) please follow this guideline: https://wiki.gnupg.org/Gpg4win/releases/3.0/notes

1. Mails encrypted with S/MIME are stored with "No Data" in the sent EMail folder, but arrive properly at the recipients (you will recieve a readable copy, if you add yourself to the list of recipients). This Issue breaks the GpgOL Plugin after some time which is leading to the described Problem.

2. Files that are Signed and Encrypted to a S/MIME Certificate is broken. When you select a file and encrypt and sign it to a recipient, only a detached signature will be created and the Encrpyted file is missing. (Very similar to Issue 1, but file based).

https://phabricator.kde.org/D8368

There is just another person experiencing the same problem with an Exchange based account on Win10pro x64, Outlook 2016 x86.

This sound like the issue described in https://wald.intevation.org/forum/message.php?msg_id=5265&group_id=11

In T3457#104401, @werner wrote:

gpg --print-mds  FILES
gpg --print-md ALGO FILES

With that in place, I think there is no need to add them to the PATH.

So far we could recreate the following issues:

In what kind of problem should we run by adding it to the path?

The gpg4win 3.0 installer does not have the option to install documentation, therefore the docs are missing on purpose. This is done to lower the footprint of the installer, but they are of coursestill available via the homepage.

Additional report in https://wald.intevation.org/forum/message.php?msg_id=5308

There are more Logfiles:

Then this is a duplicate of T3442 as well! Thank you for you Logfiles and your report!

Are those mails sent by GpgOL with Outlook or recieved? Can you explain your complete Workflow and state what software was used in it?

Can you relate to the issue described in the GPG4win Forums?

Duplicate of T3441.

What menus did you miss? Do you mean the right-click menus or kleopatra/gpa in the start menu?

You could try to use NO-MIME (or PGP/INLINE) instead of the OpenPGP/MIME standard. You can change the way of packaging your encrypted content in the GpgOL Addin Options.

In T3448#104201, @werner wrote:

What is this Chocolatey?

Did you try to sign and encrypt with an X.509 or S/MIME key or with OpenPGP Key?

I added a Workaround in the Wiki: https://wiki.gnupg.org/Gpg4win/releases/3.0/notes

I added the workaround in the Wiki: https://wiki.gnupg.org/Gpg4win/releases/3.0/notes