Had a bit trouble reproducing it. It worked for me.

It's nice. Although for now I've only added a message in the legacy_cipher_nomdc case:

I've noticed during testing that GpgOL would not send valid PGP/Inline signed only messages and also failed to verify such messages itself when special characters were in the mix.

Oops. The commits added here belong to T3975

Thanks for your report, but as JJworx already said this is sadly one of the known issues to which we don't yet have a good idea how to fix it. In T3459 there is an animation what is meant by "unselecting" the mails.

Yes, this is actually pretty high on the wishlist but AFAIK there was not yet a task for this.

Can you help me understand what the impact of this is? AFAIK Back in 2007 the problem was that it could be faked that data looked like it was signed.

The gpgme c api already had a convenience function gpgme_data_rewind to do data.seek (0, SEEK_SET); As this is by far the most common seek operation. KMymoney also only uses such seeks.

Uhm, yeah I would be willing to help. But I tried to understand it and don't see the problem.

The best way to send signed or encrypted mail is by using PGP/MIME which is the default.

I've tried to prevent the download of external references selectively for S/MIME Mails. There is PR_BLOCK_STATUS but I was unable to stop the question for the user if she want's to download the external references anyway. :-/

Thanks for your report.

Thanks. I'll look into it. It's possible that in our tests we only changed the complete date.

Thanks for the report.

Thanks for the report. This is indeed a bug.

If you click on the grey question mark in the "Entry field" when adding recipients you get a dialog that lists all keys and also allows for multiple selection.

Have to test it but I think its resolved. The registry path handling is now similar to that of GpgOL and GpgEX.

Please update to Gpg4win-3.1.1 this issue should be resolved. There was a similar issue with Gpg4win 3 T2670 but it has been resolved.

We've analyzed another report of this and the problem turned out to be that with a 64 bit outlook and GnuPG not installed in the standard location it came to this error. ( T3988 )

Yes. For S/MIME we don't have the comfort to change the standards. I also would like to have a quick solution. After much deliberation with Bernhard we think that it is a good compromise from usability vs. security that we further reduce the usability for S/MIME in that we only allow (any) signed content to be displayed as a file or HTML. This is not extending the standard, not changing GPGSM but a design decision in GpgOL.
We don't have full control over our Mail client so we can't prevent the load of external references like KMail does. This suggestion is a compromise and a pragmatic solution.

Thanks for testing. A new Gpg4win release will come soon.

Argh! From the log it looks very much like another incarnation of the issue fixed in T3960 (Same underlying reason)

Thanks for your report!

Zertifikat erneuert.