Page MenuHome GnuPG
Create Task
Maniphest T4553

Compatibilty with encrypted mails sent to SecurePIM
Testing, HighPublic
Actions

Description

SecurePIM (v6.9.1-armabi-v7a) sometimes does not show our messages because of connection errors.

These happen to me when I switch between test mails very regularly.

In that case SecurePIM also no longer syncs mails. So the best way to test for a broken state is to send a mail to yourself because SecurePIM does not often show connection errors when syncing. They are shown only sometimes. Even restarting the App does not unblock it. Only waiting seems to help.

This seems to happen more often with mails that we classify as IPM.Note.SMIME so as a workaround we also classify encrypted Mails now as IPM.Note.SMIME.MultipartSigned. Maybe that helps.

Details

Version
2.3.3

Revisions and Commits

rO GpgOL
rO7323a82d1f8d Only use IPM.Note.SMIME.MultipartSigned for SMIME

Related Objects
Search...

Event Timeline

aheinecke created this task.Jun 3 2019, 3:24 PM
aheinecke added a commit: rO7323a82d1f8d: Only use IPM.Note.SMIME.MultipartSigned for SMIME.Jun 3 2019, 3:26 PM
aheinecke added a subtask: T4389: Gpg4win 3.1.8.Jun 3 2019, 3:28 PM
aheinecke changed the task status from Testing to Open.Jun 4 2019, 1:34 PM

The change in message class did not help.

aheinecke closed this task as Resolved.Jul 14 2019, 11:15 AM

It turned out to be a downstream issue and the change in message class was enough from our side.

aheinecke closed subtask T4389: Gpg4win 3.1.8 as Resolved.Sep 9 2019, 11:27 AM
aheinecke reopened this task as Testing.Aug 7 2023, 9:40 AM

I am reopening this at least for testing as we have reports that another client is facing the issue with recent versions and also with verified mails .

A good test for this was that if you look into the Outlook Web Interface "sent mails" it should try to decrypt / verify them with the Outlook internal S/MIME handling. Then it should also work with other clients. And I remember changing some of the MessageClass handling code again because we had some issues afterwards to move S/MIME files with that message class from one folder to another since Outlook had activated some "Oh these are S/MIME Mails" code for them internally. So that might have broken this again.