Basic support is in. Maybe we should open a task on how to improve it.

It's two bugs working hand in hand here.

This was fixed. The check for VS-NfD mode was crashing.

Thanks a lot!
The log shows pretty much whats going wrong. I've opened T3863 for this to have a clear issue for the problem.

This does not require org-feed.el as far as I can tell, but it does require components of current Org Mode HTML export and publishing features which do not appear to be available in the current gnupg.org website build system.

A more recent request for this feature has been made via the devel mailing list:

I've upgraded to 3.1.0 beta 38 and sent an encrypted, non-signed e-mail to myself.
The received e-mail was shown unencrypted in inbox. See log-file below.

Playing around with this a bit: I can get messages to pass if I set the content type of our MOSS attachment to multipart/encrypted .
The problematic thing there is that there is a comment in the code that explicitly states that multipart/signed is needed to activate MSOXSMIME. So we have to be careful, maybe even check the Server Version somehow as I don't want to break older stuff.

Thanks for your report. Sadly I cannot reproduce this, I went back in my archives and even mails from 2015 / touched by Gpg4win 2.x work without a problem.

Thanks. After seeing this report I ran a spellchecker on the translation and found some more typos ;-) Will be fixed in the next version.

This should no longer happen with Gpg4win-3.1.0 as GpgOL now uses gnupg's --locate-key mechanism to find a matching key.

In T3769#111899, @hs wrote:

Behavior is the same as 3.0.3 /3.1.0beta32.
It reads encrypted e-mails if Titus plugin is disables (GpgOL as the only plugin).

Behavior is the same as 3.0.3 /3.1.0beta32.
It reads encrypted e-mails if Titus plugin is disables (GpgOL as the only plugin).
Strange: Both beta32 and beta38 show the recipients box after pressing the send button, but
the messages are sent unencrypted. After downgrading to 3.0.3 messages are sent encryted,
again.

Hi Werner. Did you by any chance already find the time to look into the changes?

Could you please test again with the beta38 (or later) from https://www.gpg4win.org/version3.1-de.html It contains the change now.

I'm closing this as I've got confirmation that one crash was fixed by disabling async encryption again. And a class of general "Crash when encrypting" bugs that were related to the communication between Kleopatra and GpgOL no longer exists as Kleopatra is no longer used when encrypting from GpgOL in gpg4win 3.1.0.

Thanks for your report. This has been fixed for the next version ( https://bugs.kde.org/show_bug.cgi?id=391222 )

2.2.6 will have this feature in --card-edit, as kdf-setup. Please test.