Still does not work on vsd-3.3.7-beta90.9 @ win10. Essentially the same behavior as before:

Do I understand this correctly, that on CLI key generation the public key of the designated revoker should be fetched automatically?

Looks good to me on vsd-3.3.7-beta90.9 @ win10:

auto-key-upload should not be triggered on revocation cert import, so everything seems fine.

Looks good to me on vsd-3.3.7-beta90.9 @ win10.

Note: Keyserver has to start with ldap: for this to work, otherwise it is silently ignored.

In general looks good to me on vsd-3.3.90.9 / gpg 2.2.54-beta4.

I once creates this task, which is probably a duplicate now: T7954: Kleopatra: Highlight focused cell in tables

Note: The invalid revocation certificate: Bad signature - rejected line is also shown on vsd 3.3.4, gpg 2.2.53 @ win10 (but revocation works).

Invalid certs (as stated in the status column in Kleopatra) are mainly S/MIME certs (e.g. with missing root cert, CRL check failed, etc). I haven't seen invalid pgp certs yet (might be e.g. very old ones with missing self signature).

Issue 1) should be implemented as already described (on error -> dialog to retry with "always trust" flag)

@ebo and me talked about this and T6701: GpgOL: Use GPGME_ENCRYPT_ALWAYS_TRUST. We think, it's best to have a short meeting to discuss further changes.

With signing only, the retry option is not offered and directly either hangs or shows the "Invalid CRL object" / "Unknown error" error.
Is this intentional?

Ticket for the hang on file encryption: T8187: Kleopatra: File encryption with invalid S/MIME certificate hangs indefinitely

Maybe those smime certs will do:

But the original patch rG1b4ac98de7db: agent: Accept a trustlist with a missing LF at the end. was not working to allow missing newlines in gpg4win-5.0.0 @ win11?

This should also be fixed in 2.2 and 2.4 (if neccessary)

Moving smime encrypted/signed mails with attachments both works with drag&drop and via context menu on gpg4win-5.0.2-beta2 @ win11 with IMAP, so I'm setting this to resolved.

gpgol.log (call trace + data)

On gpg4win-5.0.2-beta-2 @ win11 i can reproduce for signed only mails (smime and pgp):

• drag&drop does work
• move via context menu
  • works for selected mails
  • does not work for unselected mails

I can't resend the mail though.

Luckily I tested T5374: GpgOL: Can't move a signed mail in Outlook from In-Mail folder to any other folder afterwards and found out, that with my current settings in gpg4win-5.0.2-beta2 @ win11 I can reproduce this every time by sending signed only mails (pgp and smime does not matter).
Regarding my settings, I only activated the security dialog:

I have no idea how to reproduce this, there is no pattern. It could as well be, that some server side thing is involved, which is not under our control.
Either I'm lucky and it just happens while the logs are enabled, or I'll try some auto loop with appium one day.

I can't reproduce this on gpg4win-5.0.2-beta2 and vsd-3.3.4.

I cannot reproduce this on gpg4win-5.0.2-beta-2 @ win11 either, so I set this to resolved.

Relevant part from T6793: Cleanup temporary files / dirs with decrypted content:

A message box would be fine.

Should be tested (but unclear, how): ability to read / send (with both organization/personal accounts)

Ok, thanks. Closing the mail in Mailviewer will remove all temporary opened attachment files, so I'll set this to resolved.

Current state: T6793: Cleanup temporary files / dirs with decrypted content

Looks good to me on gpg4win-5.0.2-beta2 @ win11.

• local conf after 2 saves (additional entry in local conf):
  
• local conf after 2 saves (additional entry in global conf):
  

Looks almost good to me on gpg4win-5.0.2-beta2 @ win11.

It doesn't look like much was improved on Kleopatra side in gpg4win-5.0.2-beta-2 @ win11.

Looks good to me on gpg4win-5.0.2-beta2 @ win11:

gpg4win-5.0.2-beta-2 @ win11:

Looks good to me on gpg4win-5.0.2-beta2 @ win11.

Curent state in gpg4win-5.0.2-beta-2 @ win11

• it asks for each subkey
• but no pinentry involved

Looks good to me on gpg4win-5.0.2-beta2 @ win11:

Looks good to me on gpg4win-5.0.2-beta2 @ win11 (no de-vs-compliance filter):

Looks good to me on gpg4win-5.0.2-beta2 @ win11:

Looks good to me on gpg4win-5.0.2-beta2 @ win11:

Looks good to me on gpg4win-5.0.2-beta2 @ win11:

Looks good to me on gpg4win-5.0.2-beta2 @ win11.