From 5b254e173dff63ca80c9d5c9e3bf701f738bba1c Mon Sep 17 00:00:00 2001 From: Jani Nikula Date: Sun, 12 Jan 2014 22:50:53 +0200 Subject: [PATCH] Re: encrypting replies to encrypted mail --- 21/48da8591fe0ad71b895633acbca8718ae628fe | 87 +++++++++++++++++++++++ 1 file changed, 87 insertions(+) create mode 100644 21/48da8591fe0ad71b895633acbca8718ae628fe diff --git a/21/48da8591fe0ad71b895633acbca8718ae628fe b/21/48da8591fe0ad71b895633acbca8718ae628fe new file mode 100644 index 000000000..826563534 --- /dev/null +++ b/21/48da8591fe0ad71b895633acbca8718ae628fe @@ -0,0 +1,87 @@ +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 457CE431E84 + for ; Sun, 12 Jan 2014 12:51:06 -0800 (PST) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: -0.7 +X-Spam-Level: +X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 + tests=[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 mHmupuUwFaT9 for ; + Sun, 12 Jan 2014 12:50:58 -0800 (PST) +Received: from mail-ee0-f43.google.com (mail-ee0-f43.google.com + [74.125.83.43]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client + certificate requested) by olra.theworths.org (Postfix) with ESMTPS id + 6C6BA431E82 for ; Sun, 12 Jan 2014 12:50:58 -0800 + (PST) +Received: by mail-ee0-f43.google.com with SMTP id c41so220871eek.2 + for ; Sun, 12 Jan 2014 12:50:57 -0800 (PST) +X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; + d=1e100.net; s=20130820; + h=x-gm-message-state:from:to:subject:in-reply-to:references + :user-agent:date:message-id:mime-version:content-type; + bh=eQYVyrYWNbVw1rTZSIzUw9XwhUHLX/pYN4DU7jwtun4=; + b=POjUFxxJ1MJVnU9+jwBOxSdmRelHBmbGhE6SYoBC73dU7oGDoZ5NvpY88MaKrvzTzS + OjOWUIB2GLhsBCG+7hzij6AYhNlL+E5/xJMqme8I5emnKmWTiQTYmXTv1cx7Z9dqH+j8 + 1C3gZNbnR7e9kXCrl71q1iOvR8GavetUe4a2QYiBhCMi3CkwUNqIbRLhLr96H8rnA8mI + FPl4iGFaK18yQRk3Ga6LYlpeCXXfyFGsuU+3dhgygQW+jG02/1MoLTQpqEy2UJtjeFfC + NFZaXInxOdwi4hnOoUumzwl/0RSc9SKLoi+Vv0EphjcQR5TL6O/KmkdoO5zGPbmEEeL7 + LAqQ== +X-Gm-Message-State: + ALoCoQnmKhlzviNfSGFko4ViFX/Bt1nCRHNNYst8xaUHEl78M+pGf+GciDuLwiC37yzDipkGLZNR +X-Received: by 10.14.246.202 with SMTP id q50mr23407078eer.58.1389559855734; + Sun, 12 Jan 2014 12:50:55 -0800 (PST) +Received: from localhost (dsl-hkibrasgw2-58c36f-91.dhcp.inet.fi. + [88.195.111.91]) + by mx.google.com with ESMTPSA id u7sm4764457eep.11.2014.01.12.12.50.54 + for + (version=TLSv1.2 cipher=RC4-SHA bits=128/128); + Sun, 12 Jan 2014 12:50:55 -0800 (PST) +From: Jani Nikula +To: Jameson Graef Rollins , + Notmuch Mail +Subject: Re: encrypting replies to encrypted mail +In-Reply-To: <87a9f1c8aq.fsf@servo.finestructure.net> +References: <87a9f1c8aq.fsf@servo.finestructure.net> +User-Agent: Notmuch/0.17~rc2+18~g39a67a6 (http://notmuchmail.org) Emacs/24.3.1 + (x86_64-pc-linux-gnu) +Date: Sun, 12 Jan 2014 22:50:53 +0200 +Message-ID: <87zjn0udoy.fsf@nikula.org> +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, 12 Jan 2014 20:51:06 -0000 + +On Sun, 12 Jan 2014, Jameson Graef Rollins wrote: +> The question is how do we solve this problem. The tricky bit is that +> notmuch-emacs uses message-mode to compose and send messages, and mml to +> handle signing and encrypting, but uses the binary "reply" command to +> generate reply bodies. message-mode therefore does not know if the +> original message was encrypted or not. + +The notmuch reply command structured output formats contain the original +message, with all the information needed to determine whether the +message was signed and/or encrypted. Someone(tm) just needs to write the +code to check that in emacs (probably fits in the quoting loop), and +insert the appropriate mml tag (or whatever it's called) to tell message +mode to encrypt. + +BR, +Jani. + -- 2.26.2