GPGMail: Apple Mail warning msg: “This message cannot be encrypted because Mail has not finished finding public keys for all participants. Do you want to send the message without encryption?
Hi Steve,
I have someone reporting this issue consistently when forwarding messages using GPG 2018.5 & High Sierra 10.13.6. So far, it seems to always happen at least once, maybe twice - and always with unencrypted messages being forwarded to people they already have public keys for.
After checking with some other users, they report seeing this message frequently and not just when forwarding but also when replying or composing new messages.
I have never seen the error personally, but I am running Sierra 10.12.6
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 11 Dec, 2018 11:11 PM
Hi gpg_dude,
thanks for taking the time to report this.
We've received a few reports about this problem but have been unable to reliably reproduce and fix the issue at hand.
Are all users you were in touch with on macOS 10.13.x? Or do you know if some are also running macOS 10.14?
It seems all reports we've received are from users running High Sierra.
We have a ticket for this problem. I connected this discussion with the existing ticket. That means, should this discussion get closed, it will be re-opened as soon as the ticket is closed. That way you'll stay in the loop and get notified as soon as we have news. Feel free to open a new discussions should you run into further problems or need assistance.
As per our policy to have a discussion per user, I've split your comment into a separate discussion.
We'll get back to you as soon as we have news.
Best,
Steve
2 Posted by permezel on 07 Feb, 2019 03:38 AM
This just hit me. I am sending a message to an alias I have. Default is BCC: me.
If I send a message just to the alias, it works, which is to say: signed and encrypted.
If I send a message just to me, it works.
I do have SpamSieve plugin.
I am on GPG Suite 2018.5: latest.
I am on latest OSX.
I just tried to send failing message by deleting the BCC: --- failed.
I changed the From: address to use the same @address.com as the alias.
This address has a userID on the key. IE: same pub key for me. This succeeded.
Subsequently, trying to send (forward, actually) the message with the original failing set of recipients: [email blocked], BCC:@me.com, From: @me.com works.
3 Posted by gpg_dude on 07 Feb, 2019 04:21 AM
Steve - I missed this update from you in December. I have heard this from Mohave users as well.
Support Staff 4 Posted by Steve on 14 Aug, 2019 12:42 PM
Hi gpg_dude & permezel,
this issue should be fixed. If you want to test the fix, please download our latest hotfix GPG Suite. That page also has Signature file and SHA1 to verify the download.
We are in the midst of preparing the next release so feedback would be highly appreciated. If you have a few minutes please take the latest nightly (currently 2505n) for a spin.
Best,
Steve
Disclaimer: This is a development version which has not been thoroughly tested yet, so bugs or crashes are to be expected.
Steve closed this discussion on 14 Aug, 2019 12:42 PM.