Re: mutt-1.5.23_9 && gnupg-2.1.6

2016-03-02 Thread Will Yardley
On Wed, Mar 02, 2016 at 03:17:25PM -0800, Kevin J. McCarthy wrote: > On Tue, Feb 16, 2016 at 11:43:16PM -0800, Will Yardley wrote: > > On Tue, Feb 16, 2016 at 04:32:34PM -0800, Kevin J. McCarthy wrote: > > > On Mon, Feb 15, 2016 at 10:35:35PM -0800, Will Yardley wrote: > > > > Additionally, after

Re: gpgme: ambiguous specification of secret key

2016-03-02 Thread Kevin J. McCarthy
On Wed, Mar 02, 2016 at 11:52:22PM +0100, Gregor Zattler wrote: > * Kevin J. McCarthy [01. Mar. 2016]: > > Mutt is seeing more than one result when querying for secret keys > > matching that fingerprint. When it gets the second result back from > > gpgme, it's aborting with that error. > > > > W

Re: mutt-1.5.23_9 && gnupg-2.1.6

2016-03-02 Thread Kevin J. McCarthy
On Tue, Feb 16, 2016 at 11:43:16PM -0800, Will Yardley wrote: > On Tue, Feb 16, 2016 at 04:32:34PM -0800, Kevin J. McCarthy wrote: > > On Mon, Feb 15, 2016 at 10:35:35PM -0800, Will Yardley wrote: > > > (without passphrase already cached by GPG), use 'limit' to find an > > > encrypted, *traditional

Re: gpgme: ambiguous specification of secret key

2016-03-02 Thread Gregor Zattler
Hi Kevin, * Kevin J. McCarthy [01. Mar. 2016]: > On Tue, Mar 01, 2016 at 11:45:50PM +0100, Gregor Zattler wrote: >> Dear mutt users, I use mutt on debian stretch with gpgme and >> recently gnupg2 was upgraded to version 2.1 >> >> Now when I want to send an signed and encrypted email mutt is >> co