Will not work on macOSX Sierra
Note from GPGTools, December 30
yesterday, December 29th, we have sent an email to all of the
watchers in this discussion.
Unfortunately we couldn't simply use our support platform to notify all watchers, since we were told that if the number of watchers exceeds a certain amount, no more email notifications will be sent.
Once we have received some feedback from our users, we will release the beta on our website and also through our beta update channel.
To clarify some things mentioned in this discussion:
Crash reporting is optional. You will be asked if you want to opt-in the first time GPGMail discovers a crash.
The reports certainly do not include any keys (neither secret nor public). They are standard macOS crash reports and you can find them under ~/Library/Logs/DiagnosticReports/ to see what they look like
For those who just recently subscribed to the discussion, the email from yesterday is reproduced in full below.
Hope you all have a good start into the new year. Enjoy your celebrations!
<3 and ☀
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 GPGMail for macOS 10.12 Sierra (Beta 1) ======================================= A long year is coming to an end and we are all looking forward to some cosy and fun festivities to welcome the new year. But before, we wanted to finally reward your patience. So after a painful and long waiting time, extensive reverse engineering and re-writing of major parts of our codebase, we are very happy to share the first beta of GPGMail for macOS Sierra with you. Download: https://releases.gpgtools.org/GPG_Suite-2016.12b1.dmg SHA256: 2bb29067e7f2705a51b22f23080ca767bba4735ce16711a7d950e582737e8aaf GPG Signature: https://releases.gpgtools.org/GPG_Suite-2016.12b1.dmg.sig As with every beta we don't recommend using it in a production environment just yet, since bugs and crashes may occur. Please report any bugs you find via System Preferences > GPGPreferences > Send Report. We have added optional crash reporting to GPGMail in order for us to better understand when and where crashes are occuring. We wish you the very best and happy festivities, your GPGTools Team ===== KNOWN ISSUES * If multiple private keys are available for the same email address, GPGMail currently picks one at random to sign the message * Some messages might not load correctly. If you can provide us with an example .eml file we'd love to debug the issue. * If you cancel the pinentry request for signing upon sending a message it might lead to unexpected behavior * Inline PGP is currently not supported at all, PGP/MIME will be used instead * "BCC" recpients are currently not treated differently from "TO" or "CC" recipients (gnupg --hidden-recipients option not currently in use) * The GPGMail Preferences layout is a bit wonky (Mail -> Preferences -> GPGMail) * Keys that are imported using gnupg cli or GPG Keychain might require a restart of Mail in order to be picked up by GPGMail * Mail rules for signed or encrypted messages will not work for PGP/MIME signed/encryted messages. To receive further betas, make sure you are on the beta update channel. Open System Preferenes > GPGPreferences and in the Updates section check the option to 'Include beta builds'. Consider enabling auto-updates to ensure you receive notifications about further beta updates. -----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJYZpW7AAoJEOimZEgNnkP1HHIP+wVHNmbR7C5bT6MH0QYK3wwL l2BoRVRsp81aAQNdZ8U81F0+ecxtVtk/xmlzCB+k5pdCpWwBE9P/vZSjjsiYgCJy dIozrkWLZVrF1n5YgSBJlqZlZiwK6+xgX9Wg4x16I33j6VEvMoTcc/FhNXI0aTni az0mEp4Imi4yCPvMELP8FSsspF3kIOxRiluClvQStoJk+N3cQZEIFNI6CPTsIJ6s 4Nl5iMhQzmya6P/HwLQBS5JiCTfXlvTSRUoCe6mt7smAX2+lCq/ODXOLxoXfYT4y pAiKHZDSxMObMegGJlNAeweed01E/0jzpD/sAV3msk6NJcoOwi4Jtx7cArVn5tKw imtEQQyJF5nPpVw5zGC+vxNKtzTBd7Ol8o2ZbUMTWNmCNRWdgxyUAncrYSjnmE3A K0VGB3MO4Q0bFw8KYJ3xoLM058HnrllWCzRsje+gdSfGI0H0UCbGnA75TVapRg+i 3iKCMwMtTgqx37alBmwFZ6NmXCFch9uRJZAWZqCHndhpUrQtmkRcNHX7abdErLAd U+imrXSBN+rb/9GJiODHbzESvE4K7SIFp5Z5ARH8e0Pm9yHDhYruGBLv+WnVdfVp Eh9SQ2iVPKkWS/TTUzHrfNomF6hV2Uqj+GLIChS1L+v/duBYr6O13r846Ya908pX xTWCtFU9Px/B0jx4/+AR =vGSV -----END PGP SIGNATURE-----
Original first post was:
The entire suit will not work on macOSX Sierra. Hope you have went throught your way from Yosemite to El Capitain to Sierra.
Comments are currently closed for this discussion. You can start a new one.
|?||Show this help|
|ESC||Blurs the current field|
|r||Focus the comment reply box|
|^ + ↩||Submit the comment|
You can use
Command ⌘ instead of
Control ^ on Mac
1 Posted by ediz.turcan on 15 Jun, 2016 08:33 AM
Looking forward that macOS Sierra compatibility will come soon.
2 Posted by Tim Chambers on 15 Jun, 2016 08:38 PM
A bit ahead if you ask me. El Capitan still is not working, so working on Sierra seems a bit perplexing.
3 Posted by Enrico Marconi on 16 Jun, 2016 11:34 AM
Well, for me the entire suite has been working even since before El Capitan came out officially. Since then (last August) it did its job flawlessly. It's funny seeing the landing page of gpgtools saying "El Capitan, we're (almost) ready! - Sept. 24th, 2015"...
At least for now GPGPrefferences and GPG Keychain apps still work in Sierra, although updating fails. It's the GPGMail Plugin that is being disabled every time Mail 10.0 launches.
If I recall correctly there had been a workaround to force Mail to use an unsupported Plugin, though I can't find it right now...
Support Staff 4 Posted by Steve on 16 Jun, 2016 01:08 PM
if you depend on GPGMail for your every day work, please refrain from updating to macOS Sierra until further notice. We will announce any pre-release version as soon as one is ready.
Thanks for understanding,
steve and team
5 Posted by Frederick D. on 21 Jun, 2016 04:17 AM
You could try http://code2k.net and MailPluginFix. A description of the product, which is free, is here: https://www.macupdate.com/app/mac/37804/mailpluginfix
I hope this helps.
6 Posted by ediz.turcan on 21 Jun, 2016 10:53 AM
Unfortunately MailPluginFix does not work.
It doesn't detects gpg mail plugin to fix it.
Support Staff 7 Posted by Luke Le on 21 Jun, 2016 12:05 PM
A simple "fixing" plugin won't help in this situation, since Apple heavily changed the internals of Mail (as with every new release) and thus, the "fixer" might get GPGMail to load, but soon after Mail would crash.
We'll let you know as soon as possible if we have news, in here.
8 Posted by prich on 23 Jun, 2016 11:08 PM
Support folk, if you need donations, don't be bashful. Happy to support you, happy you support us
9 Posted by dtich on 11 Jul, 2016 01:30 PM
eagerly awaiting. thx
10 Posted by ediz.turcan on 09 Aug, 2016 03:03 PM
is there something new here?
11 Posted by michaeltbarrett on 09 Aug, 2016 03:05 PM
No irradiated other threats and we are all waiting on update to be Sierra compatible.
server security level -3
12 Posted by stevieo on 13 Aug, 2016 08:35 PM
Hi guys, +1 for 'waiting for macOS Sierra fix' on gpgmail.
13 Posted by Lilly on 03 Sep, 2016 04:37 PM
I think this is what you are looking for:
It worked last year and so does now, just tried ;)
14 Posted by stevieo on 03 Sep, 2016 04:40 PM
I am not Enrico…?
15 Posted by Lilly on 03 Sep, 2016 05:51 PM
Hi Steve, this was adressed to the author of post #3, but now I think he was looking for something different.
I purged the GPGMail.mailbundle like described and if I need encryption I use Thunderbird & Enigmail in the meantime, but of course, meee too is looking forward to the new version of GPGTools supporting Sierra ;)
16 Posted by dmahoney on 06 Sep, 2016 05:16 AM
Guys, the apple keynote is tomorrow. The "real" sierra is likely to drop soon.
Right now, I have a backup shell account where I have honest-to-god gpg installed, as a backup to this.
I use GPG in my every day work. Is there any way I can help this effort?
17 Posted by dmz on 07 Sep, 2016 08:44 PM
Given that Sierra GM is actually available to developers now, and is being publicly released September 20, I would hope that this will be done soon... any news? betas? anything?
18 Posted by kolargol on 08 Sep, 2016 07:29 AM
quite disappointed seeing that people want to help in an effort to bring gpgtools to macOS sierra and no response from the team ...
(another one who waits for 10.12 release)
19 Posted by dtich on 08 Sep, 2016 09:13 PM
20 Posted by bnied on 09 Sep, 2016 01:58 PM
+1; it's concerning that we haven't heard anything in some time, with the release of Sierra right around the corner. :-/
21 Posted by Piotr on 11 Sep, 2016 09:26 PM
+1, but in few days when official Sierra will be available you will have +10000. When is it possible to have upgrade?
22 Posted by prich on 12 Sep, 2016 04:27 AM
Maybe those of us interested should consider funding this at a level which would enable greater support
23 Posted by me on 12 Sep, 2016 04:32 AM
I'd throw some money at it. Sierra comes out soon.
24 Posted by ediz.turcan on 12 Sep, 2016 06:09 AM
I also would pay for this but please, do something...
25 Posted by dmz on 12 Sep, 2016 06:14 AM
The fact that they haven't received any funding for this is nobody's fault but theirs... last year at this time they talked about adding a maintenance/license fee for gpgmail, but that idea never went anywhere. I'd gladly have paid something reasonable, as I'm sure would many others.
26 Posted by luis on 13 Sep, 2016 06:05 AM
You were talking about adding license for your product.
Please ..DO IT
I will pay you ..i think that thousands of users will pay too if this will increase performance of releases.
27 Posted by Jan on 13 Sep, 2016 07:03 AM
There has always been the possibility to donate money : https://gpgtools.org/donate.html
In case you guys really wanted to throw some money at the problem, go ahead !
28 Posted by ediz.turcan on 13 Sep, 2016 07:04 AM
There is a difference between donations to an unmotivated development team and pay for something and expect updates in time.
29 Posted by luis on 13 Sep, 2016 07:11 AM
I agree with ediz.turcan.
There is a HUGE difference between donations to an unmotivated development team and pay for something and expect updates in time.
I just send you 50 EURO. ...is this is ok? Will it help :) ?
30 Posted by kolargol on 13 Sep, 2016 10:35 AM
Guys, your money is not an issue, it does not matter if you donete here or not. Looks like this project need to be rebooted by other people. If someone is not interested in leading it, then he should just let it go and seek for new dev team.
I appreciate work on gpgtools but it need to be continuously developed, and not stalled by almost 2 releases.