GPG Mail: switching email addresses for a recipient does not trigger GPG to encrypt when possible
Some contacts have multiple email addresses, not all of which have GPG userIDs associated with them. In the case where Mail.app on macOS first selects one of the email addresses that does not have a GPG userID GPGMail will obviously not be able to encrypt the message. However, upon switching the email address to another address that does have a GPG userID GPGMail continues to report it cannot encrypt to the previous address due to there being no public key available. Even after using the drop down to switch from the NonGPGUserID address to the GPGUserID address, GPGMail does not switch over to encrypt the message and continues to report an issue finding a public key for the previous NonGPGUserID address. See (sanitized) screenshots for an illustration.
-
VersionInfo.png
162 KB
-
gpg.png
156 KB
-
mail-to.png
59.5 KB
VersionInfo.png
gpg.png
mail-to.png
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 03 Jul, 2020 06:19 PM
Hey gpg_dude,
thanks for taking the time to report this problem.
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 discussion should you run into further problems or need assistance.
The workaround is, to remove the recipient and enter the email address for which a public key exists.
Have a great weekend,
Steve
Support Staff 2 Posted by Luke Le on 04 Jul, 2020 06:10 PM
Hi gpg_dude,
since we follow Apple's S/MIME implementation here, it is true that simply changing the email address doesn't start a new test if a key is available for the selected email address. What is necessary, is to change into a different field using a tab. So this issue probably is only ever seen if the very last thing you do is changing the email address.
Just to make sure, was changing the email address using the dropdown the very last thing you did?
3 Posted by gpg_dude on 06 Jul, 2020 04:15 PM
That's correct and I can confirm that using tab or the mouse input to switch to another field does trigger the check. Do you expect there will be a fix for this at some point?
Support Staff 4 Posted by Steve on 06 Jul, 2020 04:18 PM
It is in our bug tracker now. But to be transparent here, it is not a high priority or near term roadmap item. There are a few things that have higher priority and where users will benefit more when they are added / fixed. Obviously priorities can change, which is why we generally do not give ETAs and try to stay out of such discussions.
5 Posted by gpg_dude on 06 Jul, 2020 04:21 PM
Sure, I know the drill. Just wanted to confirm Luke's mention of following Apple's S/MIME implementation wasn't code for "can't/won't fix".
Support Staff 6 Posted by Luke Le on 06 Jul, 2020 04:22 PM
The last time I looked at that particular component it was pretty painful to customize it, but maybe we are lucky. I do agree that the correct behavior should be that the check is triggered when the email address changes.
Steve closed this discussion on 27 Jul, 2020 12:25 PM.