Last week:

• Went through a large backlog of open mails / issue reports.
• Fixed handling of S/MIME mails that were moved in Outlook. So that they have the original message class again and the mime structure is not broken. The actual code was pretty small for it but it required some trickery.

This is generally the better tracker to report Gpg4win / Kleopatra issues. The git systems are linked in a way that I can both automatically add a commit here and in the KDE tracker.
I just noticed the KDE report a bit quicker because there is less traffic, but I would have seen it here within the day.

In T2300#90092, @aheinecke wrote:

Ah nevermind. I think myself that this is nobug and current behavior is correct.

To implement / test the "not literally RFC compliant but in practice better" behavior let us call this now a wish and feature request as there are certificates in the wild other then intevation's and customers in large institutions run into that.

In my debian buster pbuilder enviornment I got the following failure when packaging master (beta195):

Gpg4win-3.1.8 was released.

As far as I know this works.

This works but might have created a regression which is tracked in T4701

I give this normal priority even if it is a whish because I have the same whish and already have some code around that would make it more comfortable, especially if it is used directly in GpgOL.

I still would like to test this some more and work on it. I think the implemnation might still be a bit fragile.

I'll try to look at it this week. Apologies for the delay with this.

Next week I'm on vacation.

Last week I've tried to work more structured and utterly failed. Random stuff kept popping in and I missed the discipline needed. This week I've changed my categories to have more space for "random stuff" in the hopes it will be better.

Mmh, No Data usually means that our parser had a hickup. I'll look at your examples.

Mmh, No Data usually means that our parser had a hickup. I'll look at your examples.

Strange. Can you please go to the command line (cmd.exe) and run gpg --verify "c:\<path to>\gpg4win-3.1.10.exe.sig" "c:\<path to>\gpg4win-3.1.10.exe.sig"

can you hover over the GpgOL Icon and look at the tooltip? Maybe there was an error during validation.

Account disabled and I'm closing this as resolved.

Thanks for reporting this! I've added it to our list of know problematic Addins. https://wiki.gnupg.org/GpgOL/IncompatibleAddons#Mimecast_for_Outlook

I've sent multiple PGP/MIME mails in various formats to a protonmail developer and all worked fine. So we have confirmed that protonmail and GpgOL are generally compatible.

I've sent a mail to a protonmail dev asking if protonmail supports PGP/MIME.