Got it. The reason was a broken translation. I've opened T4054 to fix in general that broken translations can cause crashes.

I can reproduce it with a german windows

Thank you for your detailed report!

Now we have this:

Do you have Tor or the Tor Browser running? Dirmngr will use them instead of a direct or proxy network connection. Di disable this behaviour put

no-use-tor

into dirmngr.conf. If that is not the case we need some more debug info. Put

log-file SOMEFILE
verbose
debug network,dns

into dirmngr.conf and post the log file (or send privately to wk@gnupg.org mentioning T4044 in the subject - no HTML please).

We have two cases:

1. No MDC with a "modern" cipher algo

ASCII Armored CMS files now also use p7m and p7s this is already handled gracefully by Kleopatra and does not require us to register new filetypes.

I don't think that this was ever working the Outlook 2007 code has been pretty much unchanged since 2013.
According to T1137 a workaround seems to be to enable the S/MIME Support in GpgOL.

Thanks very much for your help! Could you please tell me the latest version, that is running without any mistakes on outlook 2007?

Outlook 2007 is no longer supported. Neither by Microsoft nor by GpgOL. Sorry for that. But the 2010 and later GpgOL had a completely different codebase and we had to remove the support at some point.

I'm pretty sure that the running command ist the reloadkeyscommand.

Werner please give an opinion / triage.

The new idea worked! It is now possible to move mails even while their decrypted content is shown!

A new Idea which I'll have to test:
Register an event handler for each folder in which a decrypted item is read. "Mailitem->parent" In this event handler listen to the beforeitemmove event. In that event then close the mail / discard the decrypted contents.

Thanks a lot!

Will be fixed with the next release. With the next release kleopatra will only set "allow-version-check" once except if the user explicitly selects "help -> check for updates".

Right. The only way to disable it is if an update notification pops up. If you then unselect "Show this notification for future updates" it is disabled. And you only get to that dialog if there is an update check.

It's currently enabled again with 27e7dfb1280f314286348a661e057eef5c8ab440 I had another intensive look at the logs from the user where it is crashing but I still don't see a problem.

Am 21.06.2018 um 10:31 schrieb aheinecke (Andre Heinecke):

aheinecke added a comment.

Beware: Beta-7 was bad timing, yesterday I was in the middle of
implementing T3999 https://dev.gnupg.org/T3999 and broke the
internal keycache. If you use "Empfängerschlüssel automatisch
auflösen" please switch back to a different GpgOL Version. I might
upload a new Beta soon but for now I've removed Beta-7. Automatic
resolution will not work with that version and can lead to crashes.

*TASK DETAIL*
https://dev.gnupg.org/T4037

*EMAIL PREFERENCES*
https://dev.gnupg.org/settings/panel/emailpreferences/

*To: *aheinecke

*Cc: *aheinecke, JJworx, Rafixmod, ccharabaruk, Mak, gp_ast

This is an automated email from the GnuPG development hub. If you have
registered in the past at https://bugs.gnupg.org/ your account was
migrated automatically. You can visit https://dev.gnupg.org/ to set a
new password and update your email preferences.

Beware: Beta-7 was bad timing, yesterday I was in the middle of implementing T3999 and broke the internal keycache. If you use "Empfängerschlüssel automatisch auflösen" please switch back to a different GpgOL Version. I might upload a new Beta soon but for now I've removed Beta-7. Automatic resolution will not work with that version and can lead to crashes.

Yes, that did the trick for me!

Nice, then my commit should fix the issue here.

Yes, definitely the real reason is in the inline editor.

I can't confirm the regression yet. For me (albeit with Outlook 2016) preselecting sign / encrypt based on the options works for reply and forward. But only as long as the Mail is opened in a dedicated window.

Thank you for your fast fix!
2.2.1-beta2 works as expected!

Good. I don't think there is any reason to select the ephemeral port in user space (by default).
So, I disabled the feature for all OSes.

@gniibe Thank you very much!
I've tested the change on Windows 7 and Windows 10 and the Firewall warning is indeed gone with this.

I found dirmngr tries to bind some random port. It might be the cause.

As expected it was a very clear bug. We assign a NULL pointer to a string and then use that string.

Thank you for the report and the logs! A minor note: For future reports please leave the priority on "Needs Triage" we use this as a marker for issues no developer has looked at previously.

To avoid releasing incomplete tarballs this release should also be built from the source package and no longer from the git tag.

I'm seeing this as resolved. It's a design decision by the pinentry-gtk maintainer. pinentry-qt is the default pinentry for windows and there pasting works, as you have confirmed.

We did not have more reports about this so I'm resolving it here.

I'm closing this as duplicate of T3459

Has long been in testing. I think it is improved now and CRL's also work.

The fix for this was released with Gpg4win-3.1.1. Forgot to update this task.

I will try to figure out what exactly triggers the firewall. This should really be fixed as it leads to a bad "first contact" with Gpg4win, especially as we do more locate-keys nowadays so the question pops up randomly for the user.

I'm changing this to wishlist as I don't think anymore that we have something new here. When working with unsigned files the user has/had already the same problems as described in the issue.
(Wishlist does not mean that it will be ignored.)

The change was released with Gpg4win-3.1.2