From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 28175431FBD for ; Sun, 13 Apr 2014 05:56:59 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] 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 bj8BZ9nNSdEN for ; Sun, 13 Apr 2014 05:56:51 -0700 (PDT) Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 0A08D431FBC for ; Sun, 13 Apr 2014 05:56:51 -0700 (PDT) Received: from remotemail by yantan.tethera.net with local (Exim 4.80) (envelope-from ) id 1WZJxn-0004b5-En; Sun, 13 Apr 2014 09:56:47 -0300 Received: (nullmailer pid 11537 invoked by uid 1000); Sun, 13 Apr 2014 12:56:43 -0000 From: David Bremner To: Tomi Ollila , Jameson Graef Rollins , Notmuch Mail Subject: Re: [PATCH] emacs: process crypto for reply only when specified In-Reply-To: References: <1396689486-19232-1-git-send-email-jani@nikula.org> <1396852814-10338-1-git-send-email-jrollins@finestructure.net> <8761me3st5.fsf@zancas.localnet> User-Agent: Notmuch/0.17+180~g8977b1a (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Sun, 13 Apr 2014 09:56:43 -0300 Message-ID: <87ob05xu9g.fsf@zancas.localnet> MIME-Version: 1.0 Content-Type: text/plain 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: Sun, 13 Apr 2014 12:56:59 -0000 Tomi Ollila writes: > > Code looks OK. +1. I'm interested to see whether replies to signed emails > work on this system where sign/(de|en)cryption just doesn't work (out of > the box) :D > It's a good point. I need to insert my smartcard to sign things, which I'm sometimes too lazy to do. In my case, maybe I should stop being so lazy; I suspect my particular case is a but unusual. Perhaps people with no ability to sign are less likely to have "notmuch-crypto-process-mime" set? Or we can add another configuration variable initialized from notmuch-crypto-process-mime, but allowing people to shut this off.