Outlook 2016 - Cannot display signed email in sent folder
Open, NormalPublic

Description

Hi!

After having signed the email, it will get into the sent folder automatically. In my case, the email content cannot be displayed (in Outlook 2016 on my notebook). But the signed message got to the recipient (with my public key 'noname.asc').

When I synchronize the emails with my email client on my smartphone, the email content can be displayed.

Has anyone an idea, how I can fix the display issue on my notebook?

Best regards,
matoid

Details

Version
Kleopatra Version 3.0.2-gpg4win-3.0.3
aheinecke triaged this task as High priority.Jan 18 2018, 8:05 AM
aheinecke added a subscriber: aheinecke.

Damn I thought we had all these kinds of display issues fixed now with 3.0.3. Is this really GpgOL 2.0.6? (you can take a look at the option dialog of gpgol to confirm this)

Can you please enable logging in GpgOL as described in section 23.2 of https://www.gpg4win.org/doc/en/gpg4win-compendium_29.html then start outlook and look at the mail that is not displayed. And then attach the log file here.

You might want to check the log for private data. Ideally use a test mail.

Thanks!
Andre

Hi Andre, thanks for your help.


It is GpgOL 2.0.6 which is indicated in the log file as well as in the option dialog of gpgol in Outlook 2016.

Log file attachment:

I am looking forward to your help.

Thank, matoid

From your log I can see that the verification fails with "Unsupported Protocol" which is weird in itself. But at least with the fixes for T3538 (they are included already in your version) it should then show the unverified body. So this is a second problem. I tried to reproduce this for sent mails but even if deliberately break them they are displayed correctly.

Unsupported Protocol can mean that your GnuPG installation somehow does not work, or more likely the parser in GpgOL somehow parses bad data as the signature.

Could you please try to verify a signed message on the Command Line (in cmd.exe) :

echo Test | gpg -su testusera@example.com | gpg --verify

With testusera@example.com replaced by the userid of your key.
This should tell us if your GnuPG (The crypto backend) installation generally works.

Then to analyze the parser better: Please change the value in the Registry (HKCU\Software\GNU\GpgOL) of "enableDebug" from 1 to 1922 and run the test again and attach the log.
But be aware: This is very verbose logging that prints out everything the parser sees, so it will include the Mail data!

Thanks!

This comment was removed by matoid.
aheinecke lowered the priority of this task from High to Normal.Mar 8 2018, 8:34 AM

I'm lowering the priority to Normal. I've done a lot of GpgOL work and Testing for the upcoming 3.1.0 release and have not seen this problem.

Did you run the test I suggested? / Can you provide the debug log?

Hi,

We've analyzed another report of this and the problem turned out to be that with a 64 bit outlook and GnuPG not installed in the standard location it came to this error. ( T3988 )

If you have installed GnuPG/Gpg4win not in the default location you can create:

HEKY_LOCAL_MACHINE\Software\GnuPG with the string "Install Directory" with the path to the GnuPG install directory.

It would be great if you could confirm or not if this is also your problem.

Thanks,
Andre