Yes, very exactly indeed: It's GPgOL within gpg4win-3.1.1... ;) But you're right, the key itself is a legacy key, created back in 2001 with a commercial PGP Solution and later on the key was "spiced up" cipher-wise...Goal ist to get everybody (also the sender) to gpg4win-3.1.7, but how can I achive not having lots of eMails which one will never be able to decrypt?

Ok, thanks!

Correct, this was also the case before, sorry for the misunderstanding.

PS: And I can confirm that I have a lot of HTML Garbage in my mail body (on the receiver plain text side):

I can confirm that it works for me, too: Fantastic, thanks!

Wow, fast reaction! I'm happy to help evaluate a possible fix for this.

Hi, first of all I want to report back that with beta15 that the following issues did NOT arise anymore, fantastic!

Fantastic! I have these following issues:

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...

We both came from Gpg4win 2.3.2, WE BOTH upgraded to 3.0, as a consequence WE BOTH were unable to decrypt mails once encrypted with Gpg4win 2.3.2 (and actually way older Version of Gpg4win): Please also see https://wald.intevation.org/forum/forum.php?thread_id=1781&forum_id=21&group_id=11 for further description of the issue. Now I AM able to decrypt these mails, my collegue is not (even she also is on 3.0.1).

Unfortunately not, since I am able to decrypt them now (also encrypted with GPG4Win 2.3.2) AFTER the upgrade from 3.0 to 3.0.1 (we both went from 2.3.2 to 3.0 to 3.0.1).

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.

Hi, also installed 3.0.1. For me decrypting older plain text messages now works!

Confirmed, this is the exact same problem!