From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 5F5BE6DE12DA for ; Tue, 29 Nov 2016 09:43:34 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.005 X-Spam-Level: X-Spam-Status: No, score=-0.005 tagged_above=-999 required=5 tests=[AWL=0.005, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I2PXCJbI4yrz for ; Tue, 29 Nov 2016 09:43:31 -0800 (PST) Received: from pagefault.se (pagefault.se [31.7.186.167]) by arlo.cworth.org (Postfix) with ESMTP id 5F8AD6DE12C3 for ; Tue, 29 Nov 2016 09:43:31 -0800 (PST) Received: from localhost (c-8459e055.07-19-73746f67.cust.bredbandsbolaget.se [85.224.89.132]) by pagefault.se (Postfix) with ESMTPSA id 11F839220076; Tue, 29 Nov 2016 17:43:29 +0000 (UTC) From: Eric Skoglund To: David Bremner , notmuch@notmuchmail.org Subject: Re: Trouble decrypting multipart/encrypted In-Reply-To: <8760n61hiu.fsf@tesseract.cs.unb.ca> References: <87lgw41shc.fsf@pagefault.se> <877f7nx1e3.fsf@tethera.net> <878ts3v731.fsf@pagefault.se> <87bmwz1lij.fsf@tesseract.cs.unb.ca> <8760n6x2rv.fsf@pagefault.se> <8760n61hiu.fsf@tesseract.cs.unb.ca> Date: Tue, 29 Nov 2016 18:43:28 +0100 Message-ID: <87twaqgp1b.fsf@pagefault.se> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Nov 2016 17:43:34 -0000 David Bremner writes: > Eric Skoglund writes: > >> David Bremner writes: >> >>> >>> Yeah, --verify only works with one of the structured output formats >>> (json or sexp). I suppose that's probably a documentation bug. >>> >>> try >>> >>> % notmuch show --format=json --verify $message >> >> Yes that did work, getting "sigstatus : [ { 'status': 'good' .... }]". > > OK, so notmuch can talk to gpg. I'm only guessing, but it seems like > some kind of problem with pinentry, or access to private keys. One > potential issue is having multiple versions of gpg installed. > > % notmuch config get crypto.gpg_path > > should give the same path as the gpg you normally use (so, 2.1.13 as you > said). > Thank you David! Seems like notmuch used the gpg1 binary (that fedora has installed by default also), I switched the gpg binary to gpg2 and it now works like a charm! Thank you so much for your help. // Eric Skoglund