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.

I prefer plain git patches. Thanks.

That should be emitted only in verbose mode. I have verbose almost always enabled so I didn't caught it. Thanks.

I created a Differential request for this change; not sure which you prefer.

I am building on a CentOS system that comes with gnupg 2.0 and I'm trying to make an isolated test install of 2.2. It would probably work fine with the right PATH, but I thought the --with-*-pgm options might help assure the new install was used.

Multiple bugs fixed here:

Tested with Gpg4win-3.0.0-beta17 with GpgOL-2.0.2-beta8 on Windows 10 (64bit) with Outlook 2016.

The Documentation is installed. You can find it under Help -> Gpg4win Compendium in Kleopatras menu.

I enabled the error and did the following with Gpg4win-3.0.0-beta17 with GpgOL-2.0.2-beta8 on Windows 7 (64bit) with Outlook 2010

In T3442#105339, @aheinecke wrote:

In T3442#104402, @JochenSaalfeld wrote:

1. Mails encrypted with S/MIME are stored with "No Data" in the sent EMail folder, but arrive properly at the recipients (you will recieve a readable copy, if you add yourself to the list of recipients). This Issue breaks the GpgOL Plugin after some time which is leading to the described Problem.

Fixed with 474cc15d8e331c9def298dbbfe3b99e6c8cf8035

Versions Used: Gpg4win-3.0.0-beta17 with GpgOL-2.0.2-beta8 on Windows 10 (64bit) with Outlook 2016.

That is the same as a key generated from a passphrase. We have already have a task T169 for this. Thus I merge them.

What is your use case for these configure option?

@tstreibl thanks for helping with your feedback!
Please note that this issue (T3442) still has the status "testing", because we want to perform some more tests before declaring it resolved. :)

In T3442#105466, @tstreibl wrote:

Starting Outlook still bring up the "Fehler in der Benutzeroberfläche von XML von "GpgOL .....Unbekannte Office.Steuerelemente-ID: TabComposerTool" Message Box.

Sorry for my inpatience...but it's a little bit hard to understand why the above, very simple test procedure obviously isn't reproducible on your systems.

Starting Outlook still bring up the "Fehler in der Benutzeroberfläche von XML von "GpgOL .....Unbekannte Office.Steuerelemente-ID: TabComposerTool" Message Box.

tested your new .dll. Created a new email. Choosed "sign". Pasted an email adress from outlook address book into the "an" field. Outlook crashs. Took me 2 seconds to test. What the hell are you testing?

Thank you very much. Both the signed only and the encrypted mail are fully valid for me (checked on the IMAP server and with kmail) and don't contain any references to gpgolXXX.dat. This means they were correctly converted to valid PGP/MIME Mails.

Dear Andre

Thanks for the report. This is indeed badly broken. I'll work on this now.
I can reproduce and also have a reproducable crash when trying to encrypt a special folder. This must be a recent regression because I tested this some months ago and it worked fine.

Indeed this was a todo that was overlooked.

Ok for me to just have it in master. It should be fixed but is not super important imo.

Hmm. I am fine changing this for master. But for 2.2 I am nut sure. Asking on gnupg-devel?

@aa: Please do us a favor and comment only relevant stuff. The bug tracker is not chitchat. Thanks.