Do you mean, GnuPG fails for a particular message, while it works for other messages?
Or do you mean, GnuPG fails for messages from a particular sender, while it works for messages from other senders?

The new reader arrived. Works find for every message - except obviously this one sender.
See reader https://pcsclite.alioth.debian.org/ccid/supported.html#0x04E60x5116 ti should support large APDU. Same error messages
I think we are on the wrong error track here. It is not the reader. I now tested 4.

There is now also Gpg4win-3.0.2 with that gnupg version available.

The option now has the following logic:

• If encrypted is selected and the message is not signed.

and

• If the message has no attachments.

and

• If the option for inline sending is enabled

Resolved with gpg4win-3.0.2

The problem was with a special attachment that had no file extension. Fixed now.

I can't reproduce this with the above steps. It is sadly a known issue that moving crypto mails does not work as long as they are viewed. (T3459) But for me opening any unencrypted mail and moving it. Or first opening an encrypted mail and then moving an unencrypted mail works.

Pushed rM7b5182f28893

I've been running gnupg-w32-2.2.3_20171207.exe for about as long as it's been available and no hanging whatsoever. Thanks a lot!

Thank you for your cooperation.

This ticket can be closed. No further issue with email decryption after applying the provided patch

I still have trouble beliving it is the reader. Since I tried now 3.
As well I have a 4096 bit key and everybody has been encrypting this with my key. Therefore it does not make sense to me.

Could we please merge it to the stable branch (2.2.3 does not have this patch yet) or it is not tested enough? Existing subkey sellection strategy doesn't play well with mail signing and affects GPGTools/GPGMail users as well as any other users with multiple signing subkeys. Thanks!

Moving on, I will just look to make a stand along project for efl-pinentry interface. I withdraw my previous submission. Welcome to resume and move forward with Mike Blumenkrantz version. Thanks!

Frankly, I doubt that this belongs into gpgme.

Andre can you please apply this?

W/o a special tag in the commit there seems to be no way to mark a patch as applied.

All commited. I created a new installer gnupg-w32-2.2.3_20171207.exe which comes with the new libassuan 2.5.1 and the two required patches for gnupg.

Fixed at last.

Added it. For now it's pretty bare but already an improvement on the old (which only showed "class") and no indication if a signature was revoked.

Prio low, as I noticed that Kleopatra already had some code in there to merge a secret with a public key in a keylisting. This can be used for me.

I pushed this change with the addition of a doc entry and to protect against a not yet initialized socket interface.

I looked into it. The problem is that attachments are opened as "Read Only" so we can't change the message class or handle it ourself. Once opened there is no apparent way to change the message to read only. Only if the message containing the attachment is marked as modifyable: