Mail.app: S/Mime encrypted attachments are not working under MacOS Sierra

Hi all:

doesn't work for me - unfortunately.

happy that it works for you.

best regards

R.

Did not work for me, either. I've removed the certificate & keys entirely and reinstalled them, removed Mail.app access to the keys and re-added it, no change. It isn't an issue of Mail.app not accessing the keys/certs because, clearly, it can access them using the "save to desktop and reopen from there" procedure that then works to display the attachment. This means that, at least this way, Mail is fully capable of finding & accessing the keys/certs and decrypting the content, just not when the messages are stored in its own database.

Mail.app has been working fine since the upgrade until today for some reason. One attachment wouldn't open a .pdf. . I then had a second but 'rebuilding' seems to have addressed this issue.

Why is Apple seemingly failing on the basic's here? Reading others posts here how was the update passed with a fundamental error within it?

Trying to save the files to the local disk, opening with, preview, etc do not work for me. It appears possibly related to a keychain issue.

I am experiencing this issue as well. I also confirmed that at least five other people that I know are experiencing this as well (we all use SMIME). Drag and drop to the local disk only works part of the time. Reseting my keychain did not work. Granting access control permissions on the SMIME private key did not work. I am in contact with Apple Support now and will get back to this group if any progress is made.

Also, we are not experiencing any problems with SMIME encrypted email messages in Mail.app on IOS 10.

Importing a .p12 file (in pkcs12 format) including key and cert solved my problems with Mail.app in Sierra.

Upgrading to 10.12.1 hasn't fixed the problem.

I also installed 10.12.1 and I can confirm that the problem has not been fixed.

Then I reinstalled the .p12 file containing the private key. Again, no help.

I am having trouble submitting feedback to Apple because of the limit on the number of characters. Can anyone confirm that the limit is 800?

Today I filed bug report 28944722. My hope is that the report will be closed as a duplicate and that this will lead to information about the status of the issue. I will post what I learn here.

Update from my bug filed with Apple on 11 Oct, which is closed as a duplicate:

The original report on this issue is still under investigation. We will notify you when it is closed.

Based on notes in that bug report, you should test with macOS 10.12.2 when it becomes available to you.

Please note that you will not be able to directly view the original report in order to keep its information confidential.

We will do our best to keep you informed as new information becomes available. Please check release notes regularly for changes affecting this issue.

In responce to my bug report 28944722, Apple requested sysdiagnose data which I provided. Subsequently, my bug report was marked a duplicate of bug report 28623389. Both bug reports are open. Perhaps this indicates that Apple is at least working on the problem.

Thank you. Hopefully this will be addressed soon.

macOS 10.12.2 public beta 1 is available. I don't have a crash-and-burn machine on which to install it so I can't easily check to see if it contains the fix to this problem. Bug report 28623389 is still open so I am not hopeful.

+1

Apple: This is a real business feature. I am experiencing send and receive with 0 byte. My solution / workaround for now is to use ... (tadaaa) Microsoft Outlook. Please fell free to be ashamed, Apple developers....