GPGMail: Message not decrypted
Hi,
I received a encrypted message and the mail app only shows 2 attachments: “PGPMIME Version Identification” and “encrypted”.
I can manually decrypt the message with the GPGService.
Best regards
Sebastian Fischer
Expected
A decrypted message I can read ;)
macOS 10.12.5 16F73
GPG Suite 2017.1b3 1812 (d43863c)
GPGMail 2.7b3 1215 (d0b5fa0)
GPG Keychain 1.3.3b2 1271 (028a4a2)
GPGServices 1.11 916 (872e77d)
MacGPG2 2.0.30-1b2 887- (4912d26)
GPGPreferences 2.0.2b3 927 (641418e)
Libmacgpg 0.7 782 (536bf51)
pinentry 0.9.7 4 (b75069d)
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Steve on 03 Jul, 2017 09:44 AM
Hi Sebastian,
welcome to the GPGTools support platform. Sorry you are having problems using GPG Suite.
Could you please download and install our latest GPG Suite nightly build and see if the problem persists. That page also has sig and SHA256 to verify the download.
All the best,
steve
Disclaimer: This is a development version which has not been thoroughly tested yet - bugs or crashes are to be expected. Thanks for helping us test.
2 Posted by Sebastian Fisch... on 03 Jul, 2017 11:14 AM
Hi Steve,
thank you! With the nightly build it's working fine :)
Support Staff 3 Posted by Steve on 03 Jul, 2017 11:53 AM
The issue you were seeing is related MS exchange servers.
Exchange is known to "successfully" mangle signed OpenPGP/MIME mails and invalidate signatures during that process. Why? We honestly do not know. We strongly suggest to get in touch with Microsoft support and report this problem: https://support.microsoft.com.
Please do let us know how they respond. This problem has been persisting over several years. The number of affected users is quite large so let's hope MS will address the problem.
The fix addressing the problem is included in the nightly build and will be release with the next beta release.
Glad, this is solved for you. I'm closing this discussion. Should you need further assistance or have questions you can re-open this discussion here or open a new one any time.
All the best,
steve
Steve closed this discussion on 03 Jul, 2017 11:53 AM.