Home → Stable →

GPG Mail: macmail can't read signed emails I've BCC'd to myself

• Edit

ziggy shanklin

25 Sep, 2018 01:20 AM

I’d recently upgraded to GPGMail 2.8 and soon found that each time I tried to read an email I’d sent to myself that macmail would stick “Loading …” the email into the body window.

Emails that came from other users are readable, and emails that I’d BCC’d to myself that were both Signed and Encrypted I could read.

Worse now, macmail is crashing and I can’t even get into my email box

Expected
I should be able to read emails that I’ve BCC’s to myself regardless of whether they are signed, encrypted or both.

macOS                   10.12.6     16G1510
GPG Suite               2018.4      2310    (bc31914)
GPG Mail                2.8         1273    (97139d27)
GPG Keychain            1.4.5       1496    (25530e6)
GPG Services            1.11.5      1033    (86cb937)
MacGPG                  2.2.10      921     (b487092)
GPG Suite Preferences   2.1.3       1057    (966febd)
Libmacgpg               0.8.6       885     (35a18be)
pinentry                0.9.7.1     9       (db18340)

1. 1 Posted by ziggy shanklin on 25 Sep, 2018 01:50 AM

   

   I had to rebuild my macmail database by removing the "Envelope Index" files

   https://c-command.com/spamsieve/help/how-can-i-rebuild-apple

   • Edit

2. 2 Posted by Timm on 25 Sep, 2018 06:24 AM

   

   Also the rebuild of the macmail database did not helped to solve this problem. For me all my sent emails get stuck in the status "loading".
   I hope this will be fixed with an update soon.
   I use Version 2.8 GPGMail Build 1273

   • Edit

3. 3 Posted by ziggy shanklin on 25 Sep, 2018 01:20 PM

   

   I apologize, I didn't mean to imply that rebuilding the macmail database resolved this problem. My macmail crashed and corrupted my mail system while trying to determine the factors that caused macmail to be "stuck" in the "loading ..." state and I was forced to rebuild my email DB. I merely posted the link for the convenience of other users in case this crash was caused by this issue.

   • Edit

4. Support Staff 4 Posted by Steve on 25 Sep, 2018 08:31 PM

   

   Hi Ziggy,

   this is a known regression we are currently looking into.

   To workaround this problem you have the following options:

   1. downgrade to GPG Suite 2018.3, skip the 2018.4 update and wait for 2018.4.1 which we will release soon and which will include a fix for this problem.

   2. wait for the next nightly build - we are looking into this issue but need a little more time to provide a fix.

   We will keep you posted in any way once a fix is available.

   Best,
   steve

   • Edit

5. Support Staff 5 Posted by Steve on 28 Sep, 2018 02:12 PM

   

   Hi Ziggy and Timm,

   this issue has been fixed and the fix will be included in the upcoming GPG Suite 2018.4.1 release. 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. Thanks for helping us test this fix.

   Should the problem persist, please do let us know and re-open this discussion.

   Should you see trouble using GPG Suite in the future, don't hesitate to get in touch and open 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.

   • Edit

6. Steve closed this discussion on 28 Sep, 2018 02:12 PM.