I just tried it w/ the current master and it works. First, it displays the upload dialog and progress bar. After a second or two a message pops up that the upload was successful and I'll get a confirmation request my mail later. Clicking Ok on the message hides both dialogs.

ENABLE_NLS is not defined as it should be but we still have to define L_ in that case if simple_gettext is used to have some gettext. This was fixed by 6158811304937b592601ef30c29c5a5cdbaa88ea

I would suggest that MUAs who care about privacy do no use S/MIME at all or at least direct GPGME to not consider CRLs during signature verification. We don't have such a feature in GPGME right now but I think that is the right place to add it. X.509 is way to complicated to avoid meta data leaks.

Smartcards and on-disk keys are very different things and handled by different processes.

Please try again with a recent version of GnuPG. We had a dozen more releases since 2.1.11 and we can't spend time on trying to replicate bugs which may have already been fixed in the last 18 month.

Bonus: less memory usage and performance improvement.

I'll look into it

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.

It's only displayed in the advanced mode. Also, what do you mean w/ no response?

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.

So it fails after a timeout. Which probably means that the conf->sync calls timeout which probably means that some gpgme process call to gpgconf hangs. Maybe some IO Flush that does not happen correctly on MIPS. But this is pure guessing.

Talked with Jochen and tested this. Jochen's test forwarded the mail so he ran into T2854

it is: 073bc2b01d1f60c85ba4206f3ff37bc618b4a4a9

@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.

Unfortunately, even building for two Python versions is a bit of a hassle with the existing autoconf framework for Python. I did that when porting the Python bindings back to Python2 after we decided to also support 2 so that people could start to use our bindings even if they still need Python2. I don't see us extending it for more versions.

Merged, thanks for the reminder.

I can't reproduce this issue. I've imported the attached mail with KMail and synced the folder to outlook.
GpgOL did decrypt the mail. It did not set the category correctly (These were two other bugs which I've fixed now) and displayed the wrong status information but decryption happened.

Done. Thank you for stopping by.

Pound/gitweb.cgi was killed by the OOM killer, probably due to a memory leak. Thanks for letting us know.