--- /dev/null
+Return-Path: <m.walters@qmul.ac.uk>\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 BA73C431FAF\r
+ for <notmuch@notmuchmail.org>; Sun, 5 Feb 2012 04:49:41 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -1.098\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-1.098 tagged_above=-999 required=5\r
+ tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001,\r
+ NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_MED=-2.3] 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 tbCbtCxh5QSe for <notmuch@notmuchmail.org>;\r
+ Sun, 5 Feb 2012 04:49:41 -0800 (PST)\r
+Received: from mail2.qmul.ac.uk (mail2.qmul.ac.uk [138.37.6.6])\r
+ (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id 0964B431FAE\r
+ for <notmuch@notmuchmail.org>; Sun, 5 Feb 2012 04:49:41 -0800 (PST)\r
+Received: from smtp.qmul.ac.uk ([138.37.6.40])\r
+ by mail2.qmul.ac.uk with esmtp (Exim 4.71)\r
+ (envelope-from <m.walters@qmul.ac.uk>)\r
+ id 1Ru1XH-0002Zx-CD; Sun, 05 Feb 2012 12:49:39 +0000\r
+Received: from 94-192-233-223.zone6.bethere.co.uk ([94.192.233.223]\r
+ helo=localhost)\r
+ by smtp.qmul.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69)\r
+ (envelope-from <m.walters@qmul.ac.uk>)\r
+ id 1Ru1XH-0002Ac-31; Sun, 05 Feb 2012 12:49:39 +0000\r
+From: Mark Walters <markwalters1009@gmail.com>\r
+To: Dmitry Kurochkin <dmitry.kurochkin@gmail.com>, notmuch@notmuchmail.org\r
+Subject: Re: [Patch v2 0/4] Control selection of From: header when replying\r
+In-Reply-To: <87ipjlix6r.fsf@gmail.com>\r
+References: <1328388317-20161-1-git-send-email-markwalters1009@gmail.com>\r
+ <87ipjlix6r.fsf@gmail.com>\r
+User-Agent: Notmuch/0.11+154~ged6d37e (http://notmuchmail.org) Emacs/23.2.1\r
+ (i486-pc-linux-gnu)\r
+Date: Sun, 05 Feb 2012 12:50:49 +0000\r
+Message-ID: <87y5shv3yu.fsf@qmul.ac.uk>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+X-Sender-Host-Address: 94.192.233.223\r
+X-QM-SPAM-Info: Sender has good ham record. :)\r
+X-QM-Body-MD5: b180ffd8aa6828dd892f2d912cc73a41 (of first 20000 bytes)\r
+X-SpamAssassin-Score: -1.8\r
+X-SpamAssassin-SpamBar: -\r
+X-SpamAssassin-Report: The QM spam filters have analysed this message to\r
+ determine if it is\r
+ spam. We require at least 5.0 points to mark a message as spam.\r
+ This message scored -1.8 points.\r
+ Summary of the scoring: \r
+ * -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/,\r
+ * medium trust\r
+ * [138.37.6.40 listed in list.dnswl.org]\r
+ * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail\r
+ provider * (markwalters1009[at]gmail.com)\r
+ * -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay\r
+ * domain\r
+ * 0.5 AWL AWL: From: address is in the auto white-list\r
+X-QM-Scan-Virus: ClamAV says the message is clean\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, 05 Feb 2012 12:49:41 -0000\r
+\r
+On Sun, 05 Feb 2012 10:58:04 +0400, Dmitry Kurochkin <dmitry.kurochkin@gmail.com> wrote:\r
+> Hi Mark.\r
+> \r
+> I am not sure I like this solution. My concerns are:\r
+> \r
+> * New option looks too complex, too specific.\r
+> \r
+> * There are more aspects of notmuch reply behavior which users would\r
+> like to change (e.g. which part to quote). If we add an option for\r
+> each, we complicate both nomtuch show UI and code.\r
+> \r
+> The problem is that notmuch show output format is too limiting. Instead\r
+> of providing myriad of options for tweaking notmuch show text format\r
+> behavior, we should add JSON format for notmuch reply similar to nomtuch\r
+> show. That would allow notmuch reply to produce structured output with\r
+> required additional information, which should be enough for users to\r
+> construct whatever reply they want.\r
+> \r
+> In this particular case, notmuch reply JSON format could have\r
+> "from-source" attribute that would indicate how it was guessed.\r
+> \r
+> Now the best part. Not so long ago, Adam (in Cc) provided a patch for\r
+> improving nomtuch reply for HTML-only emails. At first he added an\r
+> option for notmuch reply, like you did for from-guessing. I suggested\r
+> him to implement it based on the JSON format instead and he did. AFAIK\r
+> the latest version of his patches is [1]. I did not look at the code\r
+> though. It seems that it is waiting for more review.\r
+> \r
+> So, instead of adding more nomtuch show options, I think a better\r
+> solution is to work with Adam to get the notmuch reply JSON format to\r
+> master and then fix the from-guessing issue by adding an attribute to\r
+> notmuch reply JSON format.\r
+\r
+Yes I think you are quite right: this would be a better solution\r
+(particularly as Adam has already done all the hard work!)\r
+\r
+Many thanks\r
+\r
+Mark\r
projects / notmuch-archives.git / commitdiff