Page MenuHome GnuPG

GpgOL: Setting category or flagging crypto mails is not possible
Open, NormalPublic


Setting a category on a crypto mail or Flagging it does not work.

This is because GpgOL blocks changes to crypto mails to avoid that decrypted content is sent back to the server and to avoid the temporary changes GpgOL makes (e.g. parsing PGP/MIME) from being saved, which would result in a broken mail structure.

An idea which might work:

  • Detect such a change in the PropertyChange event
  • Close the mail with discard changes.
  • Open the mail again (complicated)
  • Don't parse it this time.
  • Replay the change that was made (complicated).
  • Close the mail with save.
  • Open the mail again.
  • This time decrypt it.

In the past I've tried similar things but I could not get it to work properly.



Revisions and Commits

Event Timeline

I have a workflow now that does this without the openings. The mail is kept open by Outlook anyway when the properties are changed.

Here is what I tried:

It worked really nice for one mail I had in exchange, but for others it did not work properly. Somehow the flag change was corrupted. Probably because the prop changes were called after the close. So we might really have to do the buffer / replay step.

I recently noticed that the old workaround by setting a kategory when it is not visible in the messagelist does not work on a default Outlook 2204 anymore. This raises the priority of this issue.

aheinecke raised the priority of this task from Normal to High.Nov 3 2022, 3:11 PM
aheinecke lowered the priority of this task from High to Normal.May 15 2023, 12:04 PM

With the recent commit the old workaround works reliably again.