Can't sign outgoing email
I recently installed GPGMail. When I sent signed messages, the recipients complained that the messages were signed with an invalid certificate. They were right - the certificate is one that GPGMail fetched out of my Mac keychain. I didn't want that, I wanted to sign with the key found in my secring.gpg file. To fix it, I deleted the "bad" certificate from the keychain. Now when I try to sign a message, a very odd thing happens when I click "Send". The compose window disappears, and error dialog appears and disappears, and the compose window reappears, so rapidly that I can't read the error dialog. In the new compose window, the Send button is grey-ed out. If I uncheck the "sign" button, I can send the message by hitting SHIFT-COMMAND-D.
So I can't send signed email.
Why is GPGMail looking in the MAC keychain, and how do I fix it?
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 Luke Le on 01 Feb, 2012 06:41 PM
Hi,
I think what you're experiencing is related to S/MIME rather than OpenPGP.
Mail.app natively supports S/MIME. Those certificates are stored in the Mac keychain. Your GPG keys are in fact stored in secring.gpg and pubring.gpg.
If you check your GPGMail preferences, you should see Composing -> Enable OpenPGP/MIME checked.
If it is not, S/MIME is used to encrypt and sign messages.
Could you verify that the option is checked in preferences?
Also please post any output you find in Console.app regarding Mail.app
If an error happens when GPGMail tries to sign a message, an error should be logged in there.
2 Posted by Alex on 04 Mar, 2012 09:44 PM
I assume this this discussion can be closed...
Alex closed this discussion on 04 Mar, 2012 09:44 PM.