GPG Mail: GPGMailLoader.mailbundle
“GPGMailLoader.mailbundle” cannot be opened because the developer cannot be verified.
Expected the plug-in to be activated without errors.
Can’t figure out how to get GPGMailLoader.mailbundle to be approved to run
macOS 10.15.6 19G2021 GPG Suite 2020.1 2787 (c9e4d273d9) GPG Mail (not loaded) 4.1 1530 (ad7b466590) Decrypt Only Mode GPG Keychain 1.6 1619 (d9f323fe3e) GPG Services 2.0 1116 (0e712c951c) MacGPG 2.2.20 943 (a8c05a09fc) GPG Suite Preferences 2.3 1147 (3676fecd1d) Libmacgpg 1.1 927 (c29e5dab99) pinentry 220.127.116.11 17 (85b3564ea3)
Comments are currently closed for this discussion. You can start a new one.
|?||Show this help|
|ESC||Blurs the current field|
|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 21 Sep, 2020 12:22 PM
welcome to the GPGTools support platform. Sorry you are having problems using GPG Suite.
This is a known issue for users who have their home folder located on an external drive.
As per Apple policy Mail Bundle files cannot be signed, as Mail would not load them. At the same time Apple has increased checks in the last months. That would explain why this only became a problem around June 2020.
Can you please try to disable the checks specifically for the mailbundle files using this command:
Let us know if that brings you back to working state.
2 Posted by len.whyte on 21 Sep, 2020 12:40 PM
Ah, yes, I do indeed have my home directory on a separate partition, although on the internal SSD drive.
I did in fact resolve this by using "spctl —master-disable" and then "spctl —master-enable" on each side of enabling the GPGMail plugin in AppleMail. It seemed that it was a one-time issue just to configure the plugin, which now seems to be enabled just fine.
However, your suggested approach of adding specific Gatekeeper exceptions using "spctl —add" seem like a better idea. I’ll make a note of this in case of future installations.
Support Staff 3 Posted by Steve on 21 Sep, 2020 12:42 PM
Thanks, we were surprised by this change. As often, there was no info from Apple whatsoever about the changes that lead to this changed behaviour.
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.
Steve closed this discussion on 21 Sep, 2020 12:42 PM.