Forgot to mention this bug in the commit addressing this. ( 278893850ed926d4646929ee97576a8d09fd4998 )

You may have other changes on your system as well.

Should avoid the problem. Then import or create n OpenPGp key first and the next time you should(tm) not be bnotered by the bug.

Okay, I took your suggestion but also improved the documentation. Fixed in 2.2

Thanks for your reports.
I can finally reproduce this on a new Test VM which I gave little resources. Most of the time it does not work. Sometimes it works. Looks like a timing issue, on my main development VM which is fairly quick it always works. I'll work on it.

Oh that is not good. A passed arg should not be closed by the called fucntion unless that fucntion is documented as gaining ownership of it. Let me check.

Sorry for the confusion. We tried to reduce the interactions necessary to encrypt a file and our rationale was that users mostly want to either always use textmode or never. (Also See T3486 )

Thanks for your feedback. But this is intentional. There were two problems with with this:

Thank you Werner. Do you know when the next release will be? Is there a way for me to temporarily fix the current version in the code?

But this does not explain why it works on the same system with GPG 2.1.11 instead of 2.2.2.
Here is what happens after applying the suggested quick fixes:

--- ~ » sudo pcscd
--- ~ » sudo chown enno /dev/bus/usb/002/005                        1 ↵
--- ~ » sudo chgrp users /dev/bus/usb/002/005                      2 ↵
--- ~ » ls -l /dev/bus/usb/002/005
crw-rw-r-- 1 enno users 189, 132 16 nov.  15:17 /dev/bus/usb/002/005
--- ~ » gpg --card-status
gpg: selecting openpgp failed: Aucun périphérique de ce type
gpg: la carte OpenPGP n'est pas disponible : Aucun périphérique de ce type

So you either need to start pcscd or you fix the permission of the device so that GnuPG's scdaemon can access the card reader using its internal access method. There are probably some udev rules which need to be adjusted. For a quick check you can manually change the owner or group to your own user or one of your groups. Then it should work again.

Dear Werner,

Entering on the shell

lsusb | grep USB

This is verly likely be fixed with commit 5ecef193bc2144e6d51a6bd5727bfd08a0d28b66 which will be released with the next gpg4win version.

Add the tag of npth (forgotten).

Done for libassuan

This has been fixed a while ago my having dirmngr print a hint on the possible problem. gpg will then print a warning about a problem with the Tor configuration and with --verbose print the hint on solving this as well.

I am connected via IMAP. Sometimes Outlook also crashes when I handle a message that is in a local inbox not directly associated with an account. It may be relevant that I have two IMAP accounts configured that run on different key pairs and all messages are shifted to a local inbox on arrival.

Revisiting this I don't think there is anything to do. The ChnageLog-2011 files already carry a note explaining there purpose and that the more recent logs are either in the git or in a file ChangeLog.

This was only for multipart/alternative HTML mails which was a fairly recent feature for GpgOL.
The encoding for html mails was handled incorrectly as it took the encoding of the text/plain part and not the text/html part. Fixed now.

Merged into master. Lets test it for a few days before I backport it.

Indeed. Thanks for your report I can reproduce this. Funny how this was missed through all the Beta's and pre release testing.

How are you connected to your server? I mean IMAP, or Exchange MAPI or is it a Hotmai / Outlook.com account?

Changes were merged from the Git patches on T3501

Not possible to replace it through config as we can't "check" like with sha1sum and the format differs.

Outlook 2007 is deprecated and we will only fix security issues there (or remove it altogether in the future as Outlook 2007 is no longer maintained by MS). GpgOL for Outlook 2010 and Later in Gpg4win 3 has HTML Mail support.

FWIW, I added a gpgtar.1

I resolve this. If it is not displayed anymore it means that outlook should handle it.

Pushed to 2.2

Thanks for noticing. I've changed it and clarified that GpgOL is for Windows only and not for the Outlook Web App / Android or Mac.

You could use the --directory option. However< I agree that your suggested changes is less surprising then the current behaviour. Thus I would consider this a bug fix. Can you please apply to 2.2?

In Kleopatra this should be possible through the Checksum definition config without any code changes. I'll look into it.

That does not look like a GnuPG or GPGME bug but more like an incompatibility in python-gnupg. Please report this to the maintainers of python-gnupg. I would have suggested to use the GPGME Python bindings but unfortunately we don't have a Windows version on them yet.