Okay, decryption now gives only a warning.

Ah! I can now also reproduce it on Linux, I had two gpgme's installed and the wrong one was picked up. Bisect here I come :-)

I would say this is okay now. We switch to the Windows system directory which is unlikely to have non-ascii characters. If we ever need to change this, this can now be done in gnupg-chdir and the new gnupg_daemon_rootdir functions.

This needs to be changed. See the comments for the commit.

Can somebody test 78ebc6260 under Windows? I think this would fix it.

The diff was commited. A general review of the ldap fetching on Windows is still pending but I think this can be resolved for now and we revisit this topic when we see new problems.

Commited with https://commits.kde.org/kleopatra/bfb379a204dc36e86689685b2c56727c87128cdb

Your report does not have a lot of information, but I tried the settings dialog in gpa and kleopatra. gpa does have a upper checkbox for advanced settings, and it works as expected. This is with the latest version.

Well, we don't maintain a wiki, so I think this should be tracked elsewhere.

No. But as of 3.0 GpgOL for Outlook 2003 and 2007 is no longer maintained and the support for this will be removed in some future version. This bug only affects new installations of GpgOL on the unmaintained (by Microsoft) Outlook 2003 and Outlook 2007 Versions. So -> Wontfix.

@aheinecke did you change the default?

werner says it's not a bug.

gnupg uses LC_ALL, LC_MESSAGES, LANG and the system default determined with GetThreadLocale() on Windows. Can you please check if you have set any of these environment variables?

Given that 2.0 reaches EOL in 6 months and the bug has been here for ages, I won't backport it to 2.0 anymore.

No I don't recall any such problems, sorry.

I just tried with Windows 7 DE SP1 and GPG4Win 2.3.3 and it just worked fine.

Thanks for reporting this, but there isn't really anything we can do about it for several reasons, one is that we don't have Symantec Enterprise Vault to try to reproduce it.

The TOFU trust model gives some more information about certificate usage. Beyond that I don't think this is well defined to be actionable in the backend.

@werner The backport to 2.0 didn't happen, I think. Is this still relevant. @justus Do you recall any more problems in the tests?

Thanks for letting us know, but there is nothing we can do about it, so I am closing it here.

PGP/MIME is supported since Gpg4win 2.3.

According to the linked discussion forum, this was a misconfiguration.

No response for years.

Kleopatra for now only shows TOFU info in cert details.

GpgOL has even been revamped 2 times since then.

No response anymore, and we can not reproduce.

Thanks for the fast response!

we don't use GPG4Win anymore ... so, honestly I don't know - if you want I can verify that. Or you simply close the topic ...

Is this still an issue?

Is this still an issue?

The commit resolved this.

Fixed with https://commits.kde.org/libkleo/aec263d7ff0ea727a730f657439e4945ba88b18a