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 A3F21431FBC for ; Sun, 13 Apr 2014 13:41:25 -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 k4k6Ya3rS2Ri for ; Sun, 13 Apr 2014 13:41:14 -0700 (PDT) Received: from guru.guru-group.fi (guru.guru-group.fi [46.183.73.34]) by olra.theworths.org (Postfix) with ESMTP id 96F51431FBD for ; Sun, 13 Apr 2014 13:41:14 -0700 (PDT) Received: from guru.guru-group.fi (localhost [IPv6:::1]) by guru.guru-group.fi (Postfix) with ESMTP id 5D00110008F; Sun, 13 Apr 2014 23:41:07 +0300 (EEST) From: Tomi Ollila To: David Bremner , Jameson Graef Rollins , Notmuch Mail Subject: Re: [PATCH] emacs: process crypto for reply only when specified In-Reply-To: <87ob05xu9g.fsf@zancas.localnet> References: <1396689486-19232-1-git-send-email-jani@nikula.org> <1396852814-10338-1-git-send-email-jrollins@finestructure.net> <8761me3st5.fsf@zancas.localnet> <87ob05xu9g.fsf@zancas.localnet> User-Agent: Notmuch/0.17+200~g5c6d42d (http://notmuchmail.org) Emacs/24.3.1 (x86_64-unknown-linux-gnu) X-Face: HhBM'cA~ 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 20:41:25 -0000 On Sun, Apr 13 2014, David Bremner wrote: > 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. Below is what happened to me when I failed to remove the "<#secure method=pgpmime mode=sign>" part from the beginning of the message It is very easy to detect and there is nothing much one can use if they have configured notmuch-crypto-process-mime to be t (like I seem to have ;) --8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<-- notmuch-crypto-process-mime is a variable defined in `one-notmuch.el'. Its value is t Original value was nil --8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<-- Emacs stopped responding my keypresses after C-c C-c; C-g brought control back to me -- and then I tried again... ps output 19028 ? SLs 0:00 /usr/bin/gpg --no-tty --status-fd 1 --yes --command-f 19029 ? SL 0:00 gpg-agent --server 19030 ? RL 0:50 /usr/bin/pinentry-curses 19034 ? SLs 0:00 /usr/bin/gpg --no-tty --status-fd 1 --yes --command-f 19035 ? SL 0:00 gpg-agent --server 19036 ? RL 0:04 /usr/bin/pinentry-curses 19037 pts/6 R+ 0:00 ps x The 'pinentry-curses' and this emacs doesn't play along well (I've seen this happening before when I tried to encrypt some messages). I had to pkill gpg and pinentry-curses to get rid of the above processes. > 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. Well, I set notmuch-crypto-process-mime to nil -- it still wants to sign the message and runs gpg... ... my case may be unique enough no-one else has the same problem; anyway ideas how to automatically kill the gpg process(es) when one aborts send attempt? Tomi