In T6725#175868, @ikloecker wrote:

No. Windows has a file selection dialog where you can only select files and a folder selection dialog where you can only select folders. We cannot change Windows (and we will not use a non-native file dialog).

This is a release blocker for me.

Ingo can you investigate? This is very important because this is a regression caused by the change to pass filenames directly. I wonder if we pass this as UTF-8 and gpgtar needs a fix or if we pass it somehow else.

The Qt 6 bindings will now be compiled with the -mno-direct-extern-access flag if --enable-no-direct-extern-access is passed to configure.

Fixed by ingo

Could we then clarify this for the user somehow? Maybe both
a) add "Sign/Encrypt Folder" to the default menu bar - it would need an icon added for that, too
b) make it clear in the documentation

In T6696#175866, @antonio-rojas wrote:

This is a Qt issue. Reported at https://bugreports.qt.io/browse/QTBUG-117398

Sure. That's why I wrote that my fix needs to be checked on Windows. And if the regression T6726 wouldn't have blocked the test of my local fix for Windows, ....

No. Windows has a file selection dialog where you can only select files and a folder selection dialog where you can only select folders. We cannot change Windows (and we will not use a non-native file dialog).

This is a Qt issue. Reported at https://bugreports.qt.io/browse/QTBUG-117398

There has been another report on the Gpg4win Forum which might be related that mails now cause endless syncs and might even break further when they are saved back to the same exchange server as there is no MAPI to MIME conversion done anymore and other clients cannot read the mime structure.

For clarification: encrypting a file via Kleopatra (not GpgEX) with unicode characters in name works, only the folders don't

As eva wrote the problem is that if you decrypt only the archive and not immediately extract it, which is an option for our users this results in a broken extension. And it also looks wrong even at first glance so it does not look like we intended this. Also wouldn't we then need mime types for the tar.p7m tar.p7s, too and tar.pgp?

I'm using the standard pinentry provided by Homebrew: https://formulae.brew.sh/formula/pinentry#default

This is a serious regression.

This is as intended, in Kleopatra you either encrypt files or folders (via File-> Sign/Encrypt Folder).

gpg -v -K does not require a pinentry. You can check this by adding debug-pinentry and log-file /some/file to the gpg-agent.conf - you should not see any pinentry invocation.

that's really cool :) .. I tested now with a mail whole having the Warning message, I press "Show Mail" and it indeed open .. see the pic.
very nice feature indeed.

Meanwhile, can you please share how to use the new feature "open the mail from the Kleopatra menu" would be nice to test it.

The most difficult thing here was to actually support the case where the user then sees the keyresolver dialog and selects "yes i do not wish to sign" this never worked.

Thanks a lot Andre ... I believe it's solved.

Now when I try to encrypt to expired certificate this message comes up:

So the default error is now:

Yes I think this makes sense and a little safeguard from weird situtations where users won't know how to resolve a problem. I think we should also check for that when ever a group is opened that it does not contain such keys. In case someone "revoked" there encryption key or more commonly the encryption subkey expired. In that case a message box might make sense telling the user which key / keys are not suitable for decryption.

Maybe its not a com addin but one of the New JavaScript webapi addins? They have a different menu to disable. Definetly not an outlook feature its this protectit thingy. But have you now Trierdto open the mail from the Kleopatra menu? That is the cool New feature we are currently working on.

I disable all Addons (see screenshots) and restarted the Outlook, but still getting the same warning when trying to open the email.

Ah wait, in the first of your screenshots it is obvious which addin is modifying your mail so that we don't see it as an encrypted mail anymore. It is that warning text from the protection Addin that you should report that mail if you are unsure where it came from. That would cause such problems because when it inserts this text the type of the mail is changed and it is no longer detected as an encrypted mail.