Steve on 27 Apr, 2019 10:30 PM
welcome to the GPGTools support platform. Sorry you are having problems using GPG Suite.
If you have recently upgraded to macOS Mojave and can‘t find any signs of GPG Mail or if this is your first install on Mojave: Apple disables any installed plugins after installation and they have to be enabled manually.
Yes, I had already enabled the GPGMailLoader.mailbundle plug-in via the General tab in my Mail account settings - still no icons showing. I have also tried restarting Mail and restarting the computer. Still no icons showing.
/usr/local/bin/gpg --version gpg (GnuPG/MacGPG2) 2.2.10
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later https://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Steve on 29 Apr, 2019 12:42 PM
This is really odd.
Still thinking what could be wrong with your setup. gpg seems to work fine as you described using GPG Services successfully.
Could you disable and re-enable the mail account in question, then restart Mail.app and see if GPG Mail picks up on that info?
Which color do you see for the bubble in Mail > Preferences > GPG Mail?
Your debug log suggest you are using various email addresses. Could you create a test key for one of the other email addresses and see if you are able to use GPG Mail with that account after key creation. Do not upload the public key. You can then just delete that key after testing it.
So, after actually letting myself muck about with it - creating keys for the other accounts, plus deleting the original key altogether and creating a new key for it - I've managed to get it working. I think it must have been a problem with the initial key I had created for the initial email account.
Steve on 29 Apr, 2019 03:04 PM
That's still really odd. If you want to keep digging, you can export the new keep and create a few additional keys and see if you are able to reproduce the initial situation. If you are able to we can try to debug this further.
Besides that, good to hear this is now working as expected.