From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id BAE771396D9 for ; Fri, 20 Oct 2017 15:48:27 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 40804E0D88; Fri, 20 Oct 2017 15:48:22 +0000 (UTC) Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id BDFB3E0CB9 for ; Fri, 20 Oct 2017 15:48:21 +0000 (UTC) Received: by mail-wm0-x235.google.com with SMTP id b189so22628777wmd.4 for ; Fri, 20 Oct 2017 08:48:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:reply-to:subject:date:message-id:in-reply-to:references :mime-version; bh=kJ6Uszxy+iaQEYTeUfDe6RiotM/Zr5A/5TlXopTY6UE=; b=a5mEs4QruavtLfNJDO3l5y1VmU1WeiLJIi9/kgJZBi3oB0gE5q9VJvAvK4vfi4HLgF xBmNJoa8ngUmucF+gHTbT2XeJMZ5mbisb0ar5qFWDFIElM1OEi9zUtOFvHONZzE/oPi5 4wb5KG/Ts0G9WnDfjf9Py3mrMRusX23+32QdJ1tjhjaVLEAbwE8ty6wgbXbWYTwlp/pi UE8xzh+9lL6ULhdcFhNXhagQfbXq2pJkouOrV15JZADiDayr+uoYwDCGj4JwmV+mNnJ5 Xm8NuF/BLrmDpc8K7ZrabfIpSsBoYmc+fB5g1crvfYnYBKZ8LcTkMdMi7aRR+Q01MtB6 r0PA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:reply-to:subject:date:message-id :in-reply-to:references:mime-version; bh=kJ6Uszxy+iaQEYTeUfDe6RiotM/Zr5A/5TlXopTY6UE=; b=gCvuWt5Jrc7jCIN3w2U+hUizhO22t44M/bao9oDsQhXtrF8xtKfov/diQZGOcYfomY lUPc9wItCFLWf3wGpHdvnVOEJf1G9l8Tv8LFlDOTkRKMGI4zNiL5SxkzcDVUikNfLl9X Nxcc9+4Ob/SC5aQA3o+rJtq2Sad8bzP4FgvrTrFs0O8/BCuM2Z1lgzYuHTayoBnHXzc5 A1bCSbSjBzziWwEC5CEKxAasvdG6vf5DBQ9sQDqtZ5FXkBAvvql+kOtRlx8Ko5LA8ilR TnpAbpcIxWOj7hXrIM57S+EfpHJQwNgZy60/9MjQRdT7j/1ku7Or3+nUTOVwtPai6h9n zfcg== X-Gm-Message-State: AMCzsaVS8iPV+tItZ653DeStWt4ykcZKHockZ8YmzgsD7FJzmuUVZ6Lv uvIDUGv74p5lG1YnwVVg6rraBg== X-Google-Smtp-Source: ABhQp+TgYu4mUu8bR0iM55QQg1sowy7zJIlxxAUugd02PzSce25+JQ3RIqrTR0l/PhLdoE27pheh4g== X-Received: by 10.28.17.77 with SMTP id 74mr1821015wmr.66.1508514500232; Fri, 20 Oct 2017 08:48:20 -0700 (PDT) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa. [217.169.3.230]) by smtp.gmail.com with ESMTPSA id n89sm1437240wmi.33.2017.10.20.08.48.19 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Oct 2017 08:48:19 -0700 (PDT) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Mutt not displaying encrypted attachments Date: Fri, 20 Oct 2017 16:48:14 +0100 Message-ID: <1663968.bziXCnOS0p@dell_xps> In-Reply-To: <20171020153533.t2xq3w4f2nfg4yfh@matica.foolinux.mooo.com> References: <59e8adc4.e3249f0a.b009.8534@mx.google.com> <3571237.JYDBrQFoO6@dell_xps> <20171020153533.t2xq3w4f2nfg4yfh@matica.foolinux.mooo.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2262184.I2hRqUXY5p"; micalg="pgp-sha256"; protocol="application/pgp-signature" X-Archives-Salt: 0845bc69-62ac-42e6-9364-a4cf50089b50 X-Archives-Hash: 21d961ee9e189ec63e81263549a2472f --nextPart2262184.I2hRqUXY5p Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" On Friday, 20 October 2017 16:35:34 BST Ian Zimmerman wrote: > On 2017-10-20 10:08, Mick wrote: > > I suspect something in my configuration has deviated from vanilla and > > this is causing the problem of 'set crypt_use_gpgme' not being enough. > > This is what I'm running here: > > > > mail-client/mutt-1.7.2 > > > > I haven't tried troubleshooting gpgme when running mutt to see what > > the logs spew out. xsession-errors and syslog does not reveal > > anything. I should give this some attention when I get a free moment. > > Classic mutt had known problems in this area. For example, from the > mutt.org frontpage: > > Mutt 1.8.2 was released on April 18, 2017. This is a bug-fix release, > fixing a regression involving GnuPG agent in the 1.8.1 release. > > You may want to try upgrading to latest (1.9.1), or to neomutt if you > feel like an adventure. > > Otherwise, if you really want to debug your current configuration, I > would start by commenting out the gpgme line. That should give you the > original environment where mutt interacts with GPG directly; one fewer > variable to consider. Then, once you get that working, uncomment gpgme > and comment out all the hairy gpg command lines. LOL! You made me laugh! I've highjacked to some extent the OP's request, but since his problem was fixed by using gpgme I guess I could carry on. I have no problem using gpg with mutt as long as I include the "hairy gpg command lines". :-) The gpgme line alone does not work on my current version. I will update to a later version soon and then see what I get. Thank you for your help. -- Regards, Mick --nextPart2262184.I2hRqUXY5p Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEt7MNaGaS6HvTUrEz6WnU8jC95dcFAlnqGr4ACgkQ6WnU8jC9 5dd8Tg/+MEXod5RLbFEICHP5PfGy9ptrDBLVqeULcakT3IN+FxMYfPMNtQerssnM dnrGhRCaLSdsfySYs3TB+HgT2p2KEwGikABUUoUNdftk19y98BZlOp8mEDz1m1bl xm+eQi0e2fRbPbynhL1ulyg4ddFM/Njq+vjVNfB02+2PMFL4b1RJrIN7t6NUeWdd upL2BCzEwWEwxivT2zcBkY6KS6TAa941srSeZZA3APQrVtxbBWjL6tRPcKqn2Cf7 HuT1SBvD/BY7648qpRn9WBAQKE284EOzeXPT/D+bn6UtVYP3BBz159EZeLpD2h5i bZ7KJOXpCTUi55Yzbjl22wwPTEV7Fegh6xrFQnqYx4NBNUnMYEU4GTi0T18PWPM2 mc8Vp/1mdMOHdGpTXnmji1aZXbqwlle91q7hz2Rg47rCxvcTEtzezbi6HVwutlV7 K84gu3SNxQT7v5WOaATll7w4Rvo3rdD7ciRlglSxMe+JRNaor2G2r0gm4viZOW0F 43vLU0mns9PwwrbYDGhQH9rWsfdRHZvMIDsevXgQ4zkqBc+wZ7y1EJpz3oCZrGYA BBsSiHlzcaSTNnPh2YAIjT5LsFi1TgX3QOHU1m1kXTX/JMCw2v0OBBVL8FK1v8OQ mSyfhmoCHWXBeP13hAhaAiJHXLp8bd0jh4fS6Zs/VWKXa8UXiGU= =LZ9m -----END PGP SIGNATURE----- --nextPart2262184.I2hRqUXY5p--