GPGMail: Failure to decrypt key
If you fail to enter the key password too many times, but then successfully enter the password and send your email, the compose window does not close; making it appear as though the email was not sent. As you continue to ‘send’ it, the window remains open, but the message is being sent with each successive press of the ‘Send’ icon or the keyboard shortcuts.
Expected
I expected the compose window to close once the message sent.
macOS 10.12.2 16C67
GPG Suite 2017.1b2 31b
GPGMail 2.7b2 1192b
GPG Keychain 1.3.3b1 1249b
GPGServices 1.11 916
MacGPG2 2.0.30-1b2 887-
GPGPreferences 2.0.2b2 912b
Libmacgpg 0.7 775
pinentry 0.9.7 4
- 2017-01-24_19-17_DebugInfo.gpg 12.3 KB
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
1 Posted by Tim on 25 Jan, 2017 02:44 PM
It looks like this was problematic when using OpenPGP rather than S/MIME. If I chose S/MIME after the OpenPGP option failed, the email would send, but the window remained open. I could see the sent email in my Sent folder. I remembered there is an option to set S/MIME as the default (e.g., efaults write org.gpgtools.gpgmail DefaultSecurityMethod -int 2), which I have done, which may prevent this issue from occurring.
Support Staff 2 Posted by Steve on 20 Feb, 2017 04:17 PM
Hey Tim,
welcome to the GPGTools support platform. Sorry you are having problems using GPG Suite.
The problem you described is known and has already been fixed. Could you please download and install our latest GPG Suite nightly build and see if the problem persists. That page also has sig and SHA1 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.
Support Staff 3 Posted by Steve on 04 May, 2017 02:15 PM
A fix for this problem was release with GPG Suite 2017.1b3.
Steve closed this discussion on 04 May, 2017 02:15 PM.