From 874cf8cc7abde7f7ebd969a714c8e85aad8439d1 Mon Sep 17 00:00:00 2001 From: Patrick Totzke Date: Fri, 19 Jul 2013 16:14:07 +0100 Subject: [PATCH] Re: [alot] announcing v0.3.5 --- 75/910b967f5a3e78a13f4204a246adebeb68051e | 129 ++++++++++++++++++++++ 1 file changed, 129 insertions(+) create mode 100644 75/910b967f5a3e78a13f4204a246adebeb68051e diff --git a/75/910b967f5a3e78a13f4204a246adebeb68051e b/75/910b967f5a3e78a13f4204a246adebeb68051e new file mode 100644 index 000000000..e9d30c7f4 --- /dev/null +++ b/75/910b967f5a3e78a13f4204a246adebeb68051e @@ -0,0 +1,129 @@ +Return-Path: +X-Original-To: notmuch@notmuchmail.org +Delivered-To: notmuch@notmuchmail.org +Received: from localhost (localhost [127.0.0.1]) + by olra.theworths.org (Postfix) with ESMTP id 3C3AC431FD0 + for ; Fri, 19 Jul 2013 08:12:09 -0700 (PDT) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: -0.799 +X-Spam-Level: +X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5 + tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, + FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled +Received: from olra.theworths.org ([127.0.0.1]) + by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) + with ESMTP id B3+KE9AMOU14 for ; + Fri, 19 Jul 2013 08:12:04 -0700 (PDT) +Received: from mail-ea0-f172.google.com (mail-ea0-f172.google.com + [209.85.215.172]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) + (No client certificate requested) + by olra.theworths.org (Postfix) with ESMTPS id 41BE3431FC2 + for ; Fri, 19 Jul 2013 08:12:04 -0700 (PDT) +Received: by mail-ea0-f172.google.com with SMTP id q10so2448015eaj.17 + for ; Fri, 19 Jul 2013 08:12:03 -0700 (PDT) +DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; + h=content-type:mime-version:content-transfer-encoding:from:user-agent + :to:references:in-reply-to:message-id:subject:date; + bh=sWeaGQ74hWwGMxDza9QVZCgeKZnhceK83kGBB3BATvo=; + b=ydnVuiwP4tP56QDSPGKNJlnFQ7B9VBZiGaa9yLzGpYJflLggIgpMEMNOeP3sZmu0k5 + 9PS4mHB5rwOpD165uHSyjzzHQd2RWndaUfih/Z0d/zf1aWwUV5+dJlWICGWYY6kgXRG8 + x5TVI/Jml/VmLYyQbjAovOybFtxdGLbJhL+BW5Tv9zYEp9H+LUtALh5iY7zr/spLe+xI + s25DiVa2ZP7Gx52kxMZY/Mf71a5yrp9ZWTqzO8qVqTuJ20TQs0ho9WkacWKs/ZaZ94/Y + aaYylIMTMCx0XQBO0sbcP1d+PsMQe6pkbd7G9mVCDPekjysUzkSJjGd4IrtOpEfJwhZ5 + T1gA== +X-Received: by 10.14.209.197 with SMTP id s45mr16503020eeo.108.1374246721757; + Fri, 19 Jul 2013 08:12:01 -0700 (PDT) +Received: from localhost (dhcp-91-036.inf.ed.ac.uk. [129.215.91.36]) + by mx.google.com with ESMTPSA id + l42sm28064985eeo.14.2013.07.19.08.12.00 for + (version=TLSv1.2 cipher=RC4-SHA bits=128/128); + Fri, 19 Jul 2013 08:12:01 -0700 (PDT) +Content-Type: text/plain; charset="utf-8" +MIME-Version: 1.0 +Content-Transfer-Encoding: quoted-printable +From: Patrick Totzke +User-Agent: alot/0.3.4 +To: Ruben Pollan , notmuch@notmuchmail.org +References: <20130718092124.26175.87703@brick> + <20130719134856.6257.70922@hermes> + <20130719140234.25629.48004@megatron> + <20130719150106.6257.25551@hermes> +In-Reply-To: <20130719150106.6257.25551@hermes> +Message-ID: <20130719151407.4427.14142@megatron> +Subject: Re: [alot] announcing v0.3.5 +Date: Fri, 19 Jul 2013 16:14:07 +0100 +X-BeenThere: notmuch@notmuchmail.org +X-Mailman-Version: 2.1.13 +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: Fri, 19 Jul 2013 15:12:09 -0000 + +Quoting Ruben Pollan (2013-07-19 16:01:06) +> Quoting Patrick Totzke (2013-07-19 16:02:34) +> > Hi Rub=C3=A9n, +> > = + +> > thanks for mentioning this. I must have accidentally dropped the corres= +ponding paragraph +> > in the docs (http://alot.readthedocs.org/en/testing/usage/index.html#cr= +yptography). +> > I'm almost certain I saw this documented a while back.. +> > = + +> > Basically, you need a running gpg-agent. Then, decryption of mails shou= +ld happen +> > automatically once you open a thread. The same holds for signature veri= +fication +> > (the status of which will be mentioned in a pseudo-header). +> > This holds for mails that comply PGP/MIME only. "ASCII-armored" text in= + plaintext parts +> > is not dealt with. +> > = + +> > If this does not work, you've found a bug that you should kindly report= + :) +> = + +> Sadly that is not what I see. I'm trying to read an email that mutt repor= +ts as = + +> PGP/MIME but the content appear blank. = + + +Is is possible that this mail's body is ctype 'text/html' and you haven't s= +et up +your mailcap for html (as in FAQ #5 or issue #622)? + +> I guess I have gpg-agent properly = + +> working, because when I send a signed email I get a 'window' asking me fo= +r my = + +> passphrase and it signs it. But it don't asks for the password when I try= + to = + +> read an encrypted email. + +Yes, it seems you have set up gpg-agent correctly then. +> = + +> Do I need any special configuration on gpg-agent for it? + +Not that I know of. + +BTW: why did you not notice this earlier in the 'testing' branch? :P + +I cannot think of anything else atm, sorry. Maybe Justus has an Idea? +Could you open an issue about this with some more details about the mail an= +d your setup? +thx, +/p -- 2.26.2