[Outlook][PGP Encryption Desktop] GpgOL_MIME_structure.mime

Gpg4win help-en
,
1

Hi,

I’ve encountered an issue when sending encrypted emails using Gpg4win. My colleagues, who use PGP Encryption Desktop, consistently receive my emails with an attachment titled “GpgOL_MIME_structure.mime” and are unable to view the message content directly. To read the email, they must manually import the attachment into the “PGP viewer” provided by PGP Encryption Desktop.

I’ve tried enabling the S/MIME support option in Gpg4win, but this hasn’t resolved the issue. Does anyone know of a solution or workaround that could help my colleagues view the encrypted emails in a clear format without the extra step of using the PGP viewer (if the workaround could be done by gpg4win)?

Thanks,
Acme

2

Hi @acme2024,

what happens if you only sign an email without encrypting it?

Another path could be to look into the logs of PGP Encryption Desktop. The necessary steps are explained in the user guide I linked below. Maybe you or your colleagues can see an entry that explains that behavior.

In the guide I also read something about policies that can be defined for the software. Maybe that is something that needs some adjustment because PGP Encryption Desktop didn’t even try to decrypt the email because of these policies.

Here is the guide: User Guide for PGP Encryption Desktop

1 Like
3

Thank you @cklassen (again!) for the prompt response.

After conducting a test, we’ve discovered that messages which are only signed can be directly viewed by my colleague when they receive the email.
I have already forwarded the documentation link to my colleagues and appreciate having this issue highlighted for us.

In the meantime, I’m assuming there’s nothing more that can be done on my end using Gpg4win to help resolve this issue, correct?

4

Not as far as I know but as your colleagues could decrypt the email with the PGP viewer it seems that the “email stream” - as the guide calls it - doesn’t handle the email correctly.

5

Understood. We will continue to explore if there are any settings on the Desktop that might help resolve this issue. Thank you for the guidance.