Default sign enabled breaks HTML body

Hello,

For the last weeks we have worked to enable a key solution at our company, combined with default signing enabled. This unfortunately breaks HTML content. Resulting in a loss of branding capabilities to our external recipients.

Is there a way to perhaps only sign to available/known keys? Or perhaps a ruleset that only signs to one specific top level domain automatically?

Or a setting that would keep the HTML untouched?

Thanks!

Alex

html-body-breaks.png

Hello Alex,

For the last weeks we have worked to enable a key solution at our company, combined with default signing enabled. This unfortunately breaks HTML content. Resulting in a loss of branding capabilities to our external recipients.

Which version of Gpg4win are you using?

Is there a way to perhaps only sign to available/known keys? Or perhaps a ruleset that only signs to one specific top level domain automatically?

No.

Or a setting that would keep the HTML untouched?

I guess it’s not as easy as that :wink:

It would be great if you could log the bug (https://wiki.gnupg.org/TroubleShooting/LoggingWithGpgOL) and upload the log file here (or even better directly in a new bug report on https://dev.gnupg.org). This way you would help the developers to find the cause for this bug.

With regards,
Christoph

Hi Christoph,

Which version of Gpg4win are you using? → 4.1.0

I will log a bug, thanks for pointing that out

gpgol.txt (547 KB)

Thanks for sharing that log file! Before I report that bug to the developers: Can you please check if you installed any incompatible add-ins for Outlook? You can find a list of incompatible add-ins on this page: https://wiki.gnupg.org/GpgOL/IncompatibleAddons

Hi Christoph,

I believe that I dont have any of the culprits in my list. I added a screenshot of my addons.

add-ons.png

Thanks Alex, I created a report (https://dev.gnupg.org/T6419), where you can follow the progress for solving this problem.