Re: encrypting replies to encrypted mail

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