tag:gpgtools.tenderapp.com,2011-11-04:/discussions/beta/155-beta-expired-problem-still-persists-with-790GPGTools: Discussion 2017-09-11T15:16:37Ztag:gpgtools.tenderapp.com,2011-11-04:Comment/352544122014-11-12T08:43:37Z2014-11-12T08:43:37ZBeta expired problem still persists with 790<div><p>Hi Chris,</p>
<p>we've seen this with one other user where permission problems
where at fault.<br>
Could you please open Console.app and check for any messages
related to Mail or gnupg.</p>
<p>In addition, please try to start Mail.app from command line with
the following command and post the output:</p>
<pre>
<code>/Applications/Mail.app/Contents/MacOS/Mail -DebugLog</code>
</pre>
<p>Thanks!</p></div>Luke Letag:gpgtools.tenderapp.com,2011-11-04:Comment/352544122014-11-12T08:49:33Z2014-11-12T08:49:33ZBeta expired problem still persists with 790<div><p>Console log does not show gnupg errors and Mail.app console
errors are the same as the debug log via the cli</p></div>Christag:gpgtools.tenderapp.com,2011-11-04:Comment/352544122014-11-12T08:53:26Z2014-11-12T08:53:26ZBeta expired problem still persists with 790<div><p>I found the problem. I used an old version of GPGTools Suite. I
upgraded to the b1 of the tool suite, thereafter I reinstalled the
270.</p>
<p>The error is solved now.</p>
<p>Sorry. Totally my fault I guess.</p></div>Christag:gpgtools.tenderapp.com,2011-11-04:Comment/352544122014-11-12T08:56:17Z2014-11-12T08:56:17ZBeta expired problem still persists with 790<div><p>Ah, just wanted to write that.<br>
The problem is, that GPGMail to properly check its code signature
uses a new sub key of our team's key which was not included in
older versions of GPG Suite.<br>
And while a installation of GPG Suite includes that key, the
GPGMail build I linked to in the discussion, does not.</p>
<p>Very glad it's solved now.</p></div>Luke Le