1 Return-Path: <m.walters@qmul.ac.uk>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id BA73C431FAF
\r
6 for <notmuch@notmuchmail.org>; Sun, 5 Feb 2012 04:49:41 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-1.098 tagged_above=-999 required=5
\r
12 tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001,
\r
13 NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_MED=-2.3] autolearn=disabled
\r
14 Received: from olra.theworths.org ([127.0.0.1])
\r
15 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
16 with ESMTP id tbCbtCxh5QSe for <notmuch@notmuchmail.org>;
\r
17 Sun, 5 Feb 2012 04:49:41 -0800 (PST)
\r
18 Received: from mail2.qmul.ac.uk (mail2.qmul.ac.uk [138.37.6.6])
\r
19 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
\r
20 (No client certificate requested)
\r
21 by olra.theworths.org (Postfix) with ESMTPS id 0964B431FAE
\r
22 for <notmuch@notmuchmail.org>; Sun, 5 Feb 2012 04:49:41 -0800 (PST)
\r
23 Received: from smtp.qmul.ac.uk ([138.37.6.40])
\r
24 by mail2.qmul.ac.uk with esmtp (Exim 4.71)
\r
25 (envelope-from <m.walters@qmul.ac.uk>)
\r
26 id 1Ru1XH-0002Zx-CD; Sun, 05 Feb 2012 12:49:39 +0000
\r
27 Received: from 94-192-233-223.zone6.bethere.co.uk ([94.192.233.223]
\r
29 by smtp.qmul.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69)
\r
30 (envelope-from <m.walters@qmul.ac.uk>)
\r
31 id 1Ru1XH-0002Ac-31; Sun, 05 Feb 2012 12:49:39 +0000
\r
32 From: Mark Walters <markwalters1009@gmail.com>
\r
33 To: Dmitry Kurochkin <dmitry.kurochkin@gmail.com>, notmuch@notmuchmail.org
\r
34 Subject: Re: [Patch v2 0/4] Control selection of From: header when replying
\r
35 In-Reply-To: <87ipjlix6r.fsf@gmail.com>
\r
36 References: <1328388317-20161-1-git-send-email-markwalters1009@gmail.com>
\r
37 <87ipjlix6r.fsf@gmail.com>
\r
38 User-Agent: Notmuch/0.11+154~ged6d37e (http://notmuchmail.org) Emacs/23.2.1
\r
40 Date: Sun, 05 Feb 2012 12:50:49 +0000
\r
41 Message-ID: <87y5shv3yu.fsf@qmul.ac.uk>
\r
43 Content-Type: text/plain; charset=us-ascii
\r
44 X-Sender-Host-Address: 94.192.233.223
\r
45 X-QM-SPAM-Info: Sender has good ham record. :)
\r
46 X-QM-Body-MD5: b180ffd8aa6828dd892f2d912cc73a41 (of first 20000 bytes)
\r
47 X-SpamAssassin-Score: -1.8
\r
48 X-SpamAssassin-SpamBar: -
\r
49 X-SpamAssassin-Report: The QM spam filters have analysed this message to
\r
51 spam. We require at least 5.0 points to mark a message as spam.
\r
52 This message scored -1.8 points.
\r
53 Summary of the scoring:
\r
54 * -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/,
\r
56 * [138.37.6.40 listed in list.dnswl.org]
\r
57 * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail
\r
58 provider * (markwalters1009[at]gmail.com)
\r
59 * -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
\r
61 * 0.5 AWL AWL: From: address is in the auto white-list
\r
62 X-QM-Scan-Virus: ClamAV says the message is clean
\r
63 X-BeenThere: notmuch@notmuchmail.org
\r
64 X-Mailman-Version: 2.1.13
\r
66 List-Id: "Use and development of the notmuch mail system."
\r
67 <notmuch.notmuchmail.org>
\r
68 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
69 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
70 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
71 List-Post: <mailto:notmuch@notmuchmail.org>
\r
72 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
73 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
74 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
75 X-List-Received-Date: Sun, 05 Feb 2012 12:49:41 -0000
\r
77 On Sun, 05 Feb 2012 10:58:04 +0400, Dmitry Kurochkin <dmitry.kurochkin@gmail.com> wrote:
\r
80 > I am not sure I like this solution. My concerns are:
\r
82 > * New option looks too complex, too specific.
\r
84 > * There are more aspects of notmuch reply behavior which users would
\r
85 > like to change (e.g. which part to quote). If we add an option for
\r
86 > each, we complicate both nomtuch show UI and code.
\r
88 > The problem is that notmuch show output format is too limiting. Instead
\r
89 > of providing myriad of options for tweaking notmuch show text format
\r
90 > behavior, we should add JSON format for notmuch reply similar to nomtuch
\r
91 > show. That would allow notmuch reply to produce structured output with
\r
92 > required additional information, which should be enough for users to
\r
93 > construct whatever reply they want.
\r
95 > In this particular case, notmuch reply JSON format could have
\r
96 > "from-source" attribute that would indicate how it was guessed.
\r
98 > Now the best part. Not so long ago, Adam (in Cc) provided a patch for
\r
99 > improving nomtuch reply for HTML-only emails. At first he added an
\r
100 > option for notmuch reply, like you did for from-guessing. I suggested
\r
101 > him to implement it based on the JSON format instead and he did. AFAIK
\r
102 > the latest version of his patches is [1]. I did not look at the code
\r
103 > though. It seems that it is waiting for more review.
\r
105 > So, instead of adding more nomtuch show options, I think a better
\r
106 > solution is to work with Adam to get the notmuch reply JSON format to
\r
107 > master and then fix the from-guessing issue by adding an attribute to
\r
108 > notmuch reply JSON format.
\r
110 Yes I think you are quite right: this would be a better solution
\r
111 (particularly as Adam has already done all the hard work!)
\r