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 BA4EC6DE0B00 for ; Mon, 28 Nov 2016 10:56:28 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.006 X-Spam-Level: X-Spam-Status: No, score=-0.006 tagged_above=-999 required=5 tests=[AWL=0.005, SPF_PASS=-0.001, 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 bkGYva1nO19u for ; Mon, 28 Nov 2016 10:56:26 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 9E7876DE0AE5 for ; Mon, 28 Nov 2016 10:56:26 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2) (envelope-from ) id 1cBR5u-0006Wk-Fv; Mon, 28 Nov 2016 13:56:02 -0500 Received: (nullmailer pid 10054 invoked by uid 1000); Mon, 28 Nov 2016 18:56:20 -0000 From: David Bremner To: Eric Skoglund , notmuch@notmuchmail.org Subject: Re: Trouble decrypting multipart/encrypted In-Reply-To: <878ts3v731.fsf@pagefault.se> References: <87lgw41shc.fsf@pagefault.se> <877f7nx1e3.fsf@tethera.net> <878ts3v731.fsf@pagefault.se> Date: Mon, 28 Nov 2016 14:56:20 -0400 Message-ID: <87bmwz1lij.fsf@tesseract.cs.unb.ca> 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: Mon, 28 Nov 2016 18:56:28 -0000 Eric Skoglund writes: >>> >>> Signing and encrypting email via C-c C-m s p and C-c C-m c p works >>> fine. And given that it doesn't work outside of emacs I don't think it >>> is an emacs problem. I'm also able to decrypt the message via the >>> command line using just gpg. >> >> Can you verify signed, non-encrypted messages (notmuch show --verify) ? >> > > I'm not getting any output besides the message when I do --verify (same as > with an unsigned message) so to me it doesn't seem like it is working > per the man page. But I might be wrong here. > 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