GpgOL: Opening a S/MIME encrypted msg file sometimes result in an error
Open, Needs TriagePublic

Assigned To
None
Authored By
timegrid
Fri, Sep 4, 11:36 AM

Description

Opening smime encrypted msg files sometimes (feels like a race condition) displays this error:

Might be related to T8438: GpgOL: Closing an open smime encrypted msg file creates the mail in the inbox.

To reproduce:

  1. Open smime encrypted msg file until the error occurs (maybe each ~10 times in my tests)

Logs:

  • 09:29:46 - open worked
  • 09:29:48 - open displayed the error

Testdata:

  • smime encrypted/signed mail from edward to ted:

Details

Version
vsd-3.4.0-beta1356, gpgol-2.7.5, gpg-2.2.56-beta5 @ win10

Event Timeline

timegrid renamed this task from GpgOL: Opening a S/MIME encrypted mail sometimes result in an error to GpgOL: Opening a S/MIME encrypted msg file sometimes result in an error.Fri, Sep 4, 1:13 PM

Note: Saving attached mails as msg file and opening them is currently a workaround to be able to display them in certain cases, so this should better be fixed.
See T7806: GpgOL: Attached mails are empty if attached mail has encrypted attachments or is in text format and encrypted or signed

it's always possible to save the mail attachment to desktop and open it in outlook (with correct content and security level)