Right. Now I see the wks page in advanced setup. In basic setup there is only a minimal wks info page. WKS confirmation email is send in both cases. Good.

Sorry... I tested the current nightly build from today. There is no WKS upload dialog in Enigmail's setup wizard (default setup). And my manually upload test (via context menu from Engimails key management) gets no response...
@kai Can you please check the current state in upstream. Thanks.

@kai Can you say when your patch will be upstream? We wait for a public nightly build of enigmail with all your wkd/wks changes.

We need a more prominent visualisation for compliant keys in key selection dialog of Kleopatra. E.g. as icon.

Tested with GpgOL 1.3.0-beta71 in Outlook 2003:
Still the same problem: "ü" is missing in German Tooltips

It is an IMAP issue in Outlook 2003/2007 that deleted email are marked as
deleted (stroked) but were not deleted permanently. This can be done via Edit
menu (in German: "Gelöschte Nachrichten permanent löschen"), see [1].
So not a GpgOL bug. => Resolved.

https://support.office.com/de-de/article/Permanentes-L%C3%B6schen-von-zum-L%C3%B6schen-markierten-IMAP-Elementen-ac1c51da-31c1-435c-a357-96eb78ad684a?ui=de-DE&rs=de-DE&ad=DE

debug output attached.

Thanks!

Is there a need to backport it to 2.0 ?

No

works with Gpg4win 2.2.0. But there is a failure after decrypting folder with
umlauts: see gpg4win wald issue #6451
(https://wald.intevation.org/tracker/index.php?func=detail&aid=6451&group_id=11&atid=126)

Tested with current gnupg and pinentry-qt4:

pinentry qt4 (git 5190773293bc38550bbc8aeb1b539bfb47a47c78)
qt 4.7 
gpg (GnuPG) 2.1.0-git328ac58
libgcrypt 1.5.0-gitb90be28

Using SMTP with GpgOL and Exchange seems to be work:
http://lists.wald.intevation.org/pipermail/gpg4win-users-en/2010-December/000572.html

The release pinentry 0.8.0 version (from 2010-03-03) is based on svn222 (see
tags(pinentry-0.8.0).

Just to make sure:
I tested with gnupg 2.0.16 + pinentry 0.8.0-svn234.
You say that I should test gnupg 2.0.16 + pinentry 0.8.0-svn237.
Right?
(But in T1237 (wk on Sep 28 2010, 01:05 PM / Roundup) you wrote: "you need a newer gnupg".)

Fix confirmed. Tested with gpg4win 2.1.0-svn1569.
So resolved.

Test works also for gpg4win 2.1.0-beta1 if created an empty file gpg-agent.conf
before gpg-agent is started:

There seems to be a relation if gpg-agent.conf exists or not.

Just to note:
I tested with the debian package pinentry-qt (0.8.0.svn234-0kk1) from
files.kolab.org. It's the same problem with pinentry-qt and pinentry-gtk (see
test below).
You wrote that pinentry-qt works corectly since 0.8.0 (=svn222). I can't confirm
this with my test below. Or do you mean, that the additional changes in gnupg
are required for show the german "Abbrechen" button text in pinentry-qt?

My retest with gnupg 2.0.16...

Sorry, the "set GPG_AGENT_INFO..." line was pasted from my windows test. My
GNU/Linux test starts of course with:

ping, it's important for gpg4win.

$ gpg-agent --version
gpg-agent (GnuPG) 2.0.16

Werner, please note: this issue is kkc.

Tested with gpgol 1.1.2:
Open an openpgp signed+encrypted message with attachments. Outlook 2007 crashes
after double clicking the txt attachment. Gpgol log file attached.

OpenPGP!
Marcus means, we need a similar pinentry message which ask for correctness of
fingerprint of the certificate which the user want to certified (like the
pinentry if you enabled allow-mark-trusted option for S/MIME).

Tested with gpg4win-2.1.0-svn1497 (= gpgol 1.1.2) + kleo 2.1.0-svn1156672:

Tested with different mailer of sender:
An OpenPGP encrypted (or encrypted/signed) email sent by OL2007/GpgOL1.1.1 and
Kontact e35 (GNU/Linux).
Same problem for both emails: OL2007 crashes after opening an attachment.

Still the same problem with gpg4win 2.0.2 (aka GpgOL 1.1.1).

ok, please enable s/mime support by default for next release.

sorry, jroemmler, I have mixed the issue numbers.
Again: I think your issue is the same problem like T1137 (GpgOL could not
decrypt/verify messages in "sent items" folder if sime support is disabled).
Can you confirm it?

Seems to be the same issue like T1110, right?