Home → Beta →

GPGMail: GPG Not Encrypting Mail Messages

• Edit

matt

31 Jan, 2017 08:06 AM

Hello,

In the version 2.7b2 build 1192b of GPG Mail, the component is NOT encrypting my mail messages when instructed to do so.

I create a message addressed to someone who’s public key I have, and the “encrypt” control activates in Mail. I select “encrypt”, and send the message. I’m asked for my passphrase, which I enter correctly. The mail is then sent — but it is not encrypted, which I determine by both inspecting the source, and Mail does not flag the message as encrypted.

So the only way I can currently encrypt a message is manually selecting all the text, and then using the OS service to encrypt.

Expected
I expected the message to be encrypted when I configured it so.

macOS           10.12.3     16D32
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-31_08-06_DebugInfo.gpg 20.8 KB

1. 1 Posted by matt on 03 Feb, 2017 08:19 AM

   

   Not encrypting an email's content when it says it will seems like a pretty serious issue. Is anyone reviewing the reported issues? Perhaps they are, and I just can't see that from the ticket?

   • Edit

2. Support Staff 2 Posted by Steve on 19 Feb, 2017 06:35 PM

   

   Hey Matt,

   welcome to the GPGTools support platform. Sorry you are having problems using GPG Suite.

   Please excuse the slow response. Are you using other plugins in Mail.app besides GPGMail?

   There is a known issue with Mail Act-On. In that case try temporarily disabling Mail Act-On and then send an encrypted test message to yourself.

   All the best,
   steve

   • Edit

3. 3 Posted by matt on 19 Feb, 2017 06:57 PM

   

   Hello Steve,

   Thanks for the reply. Yes, I also use Mail Act-On, so I’ll try disabling that, and will follow up to let you know.

   Talk soon!

   • Edit

4. Support Staff 4 Posted by Steve on 19 Feb, 2017 07:04 PM

   

   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.

   • Edit

5. 5 Posted by matt on 19 Feb, 2017 08:19 PM

   

   Hi Steve,

   Do you have a link to that other discussion? I just checked this ticket, and could figure out where the link is to be found. Thanks again.

   • Edit

6. 6 Posted by matt on 19 Feb, 2017 08:22 PM

   

   Steve,

   Just a quick follow-up: Disabling Mail Act-on resulted in my mail being encrypted as expected. So that’s definitely the issue.

   Best,

   — Matt

   • Edit

7. Support Staff 7 Posted by Steve on 20 Feb, 2017 01:47 PM

   

   Hey Matt,

   which other discussion are you referring to?

   We'll update this discussion here as soon as we have news regarding this specific issue with Mail Act-on.

   Kindly,
   steve

   • Edit

8. 8 Posted by matt on 20 Feb, 2017 01:59 PM

   

   Hi Steve,

   You wrote, “We have a ticket for this problem. I connected this discussion with the existing ticket.” I understood from that there was another (earlier) ticket specifically related to the Mail Act-On conflict, and that you’d linked my ticket to that one?

   Seems like I was confused. :) So I now understand that my own ticket will get updated whenever there’s news, so that sounds perfect.

   Thanks again for the effort you guys have and continue to put into making GPG Tools available. It’s very much appreciated!

   • Edit

9. Support Staff 9 Posted by Steve on 20 Feb, 2017 02:11 PM

   

   Ah ok, we are on our support forum which has discussions on a per case basis. We connect discussions to existing or new tickets per bug. Those tickets live in a different system, our bug tracker. So this discussion here is connected to GPGMail ticket #888.

   Once we find a solution we update all connected discussions to inform users about the fix.

   Hope this clarifies the situation.

   • Edit

10. Support Staff 10 Posted by Steve on 19 Mar, 2017 11:35 PM

    

    Hi Matt,

    this issue has been fixed. If you want to test the fix, please download our latest nightly GPG Suite. That page also has sig and SHA1 to verify the download.

    Should the problem persist, please re-open this discussion and let us know. For more questions that are not related to this specific problem, you are welcome to create a new discussion any time.

    Best, steve

    Disclaimer: This is a development version which has not been thoroughly tested yet, so bugs or crashes are to be expected. Thanks for helping us test this fix.

    • Edit

11. Steve closed this discussion on 19 Mar, 2017 11:35 PM.

12. matt re-opened this discussion on 20 Mar, 2017 07:55 AM

13. 11 Posted by matt on 20 Mar, 2017 07:56 AM

    

    Hello Steve,

    I just installed this build, and ran into the following problem. I tried sending myself an encrypted mail, and received an error saying that I don't have the public key:

    http://d.dafacto.com/qwET

    As far as I can tell, in GPG Keychain, I do have my own public key:

    http://d.dafacto.com/GDTd

    Any idea what could be happening here?

    • Edit

14. Support Staff 12 Posted by Steve on 20 Mar, 2017 12:53 PM

    

    Thanks a lot for helping to test this. We are looking into the regression you reported at the moment.

    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.

    • Edit

15. Support Staff 13 Posted by Steve on 22 Mar, 2017 09:41 PM

    

    Hey Matt,

    GPG Suite 2017.1b3 has just been released. Could you please update to the new release and let us know if your problem persists using the latest beta.

    All the best,
    steve

    • Edit

16. 14 Posted by matt on 23 Mar, 2017 08:37 AM

    

    Hello Steve,

    The new version resolved the issue I was seeing (i.e. claims that my public key is unavailable), and so far I’ve not run into additional issues.

    Thanks so much for your efforts. I would love to express my appreciation for your work through a donation. Does your organization accept bitcoin?

    • Edit

17. Support Staff 15 Posted by Steve on 23 Mar, 2017 10:26 AM

    

    No we're not accepting bitoins. The current options are wire transfer or paypal:
    https://gpgtools.org/donate.html

    That's great news. Glad to hear the problems are solved in the latest beta release.

    'm closing this discussion. Should you need further assistance or have questions you can re-open this discussion here or open a new one any time.

    Have a great day,
    steve

    • Edit

18. Steve closed this discussion on 23 Mar, 2017 10:26 AM.

19. matt re-opened this discussion on 24 Mar, 2017 08:14 PM

20. 16 Posted by matt on 24 Mar, 2017 08:14 PM

    

    Hello Steve,

    I just emailed someone an encrypted email, and when they replied, also encrypted, their mail was encrypted to the public key of one of my old GPG keys, i.e. not the key specified as the default key in GPG Preference Pane.

    Any chance this is a regression, or more likely user error somehow on my part?

    Thanks,

    — matt

    • Edit

21. Support Staff 17 Posted by Steve on 27 Mar, 2017 02:40 PM

    

    Hey Matt,

    a few things regarding this issue:

    • when searching the key servers for '[email blocked]' I find 2 valid keys. One from 2015 and one from 2000
    • if you can, you should probably revoke the old key: This KB-article explains how to revoke a key
    • should you be unable to revoke the old key, please tell your contact to download the correct key from the key servers and disable the old key - in GPG Keychain that is fairly simple: double click pub key, on the first tab tick the box to "Disable" the key
    • to ensure the correct keys are used on both sides, this KB-article explains how to verify and sign a key

    Let me know if any of that was helpful.

    Kindly,
    steve

    • Edit

22. Support Staff 18 Posted by Steve on 24 May, 2017 04:59 PM

    

    Closing, since no further user feedback was received. Should your problem persist, feel free to re-open this discussion any time.

    All the best, steve

    • Edit

23. Steve closed this discussion on 24 May, 2017 04:59 PM.