1 Return-Path: <novalazy@gmail.com>
\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 6E003431FAF
\r
6 for <notmuch@notmuchmail.org>; Wed, 6 Mar 2013 03:09:08 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0.602 tagged_above=-999 required=5
\r
12 tests=[DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1,
\r
13 FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_LOW=-0.7]
\r
15 Received: from olra.theworths.org ([127.0.0.1])
\r
16 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
17 with ESMTP id DLEd1qZSJrvi for <notmuch@notmuchmail.org>;
\r
18 Wed, 6 Mar 2013 03:08:58 -0800 (PST)
\r
19 Received: from mail-ia0-f174.google.com (mail-ia0-f174.google.com
\r
20 [209.85.210.174]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
\r
21 (No client certificate requested)
\r
22 by olra.theworths.org (Postfix) with ESMTPS id E15A5431FAE
\r
23 for <notmuch@notmuchmail.org>; Wed, 6 Mar 2013 03:08:57 -0800 (PST)
\r
24 Received: by mail-ia0-f174.google.com with SMTP id u20so7148990iag.5
\r
25 for <notmuch@notmuchmail.org>; Wed, 06 Mar 2013 03:08:56 -0800 (PST)
\r
26 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
\r
27 h=x-received:date:message-id:from:to:cc:subject:in-reply-to
\r
28 :references:mime-version:content-type:content-disposition
\r
29 :content-transfer-encoding;
\r
30 bh=6Hltio5o8RaabGKtmD/OHBurA5A2U2XNCVaKZ06EdRY=;
\r
31 b=kUiSS+V84f6N01t11ckF5avHoIz7OfwWLkB9RPD+f9fXA3CRYr9m1jRtyEhiCf8hgK
\r
32 5IzRIKgmXrcBmr80VjFCy9ysuZ+RS5Y3u7wxa8+HOcC1PJF+3rC/ydvbRdTji0MiG1wK
\r
33 /mFva7MtA1IvRqf5kDFuFlBs6G5/ny0hR9i2eq1PqG0f40PNsHzegNFtCFdPMnMD5V2T
\r
34 pLlJhGkRnec2Mc46adFieHX7gVwatAchIauWa0scgDepf808OIic0RGcXvFHhfZ2M/TJ
\r
35 pcdDkBOdtcyIYxGpcWrGsmUhzzNjV6W1pPW049ZW+jU9ytV1h1uLbuIFYJivgHy94RlM
\r
37 X-Received: by 10.50.154.129 with SMTP id vo1mr10127419igb.93.1362568136411;
\r
38 Wed, 06 Mar 2013 03:08:56 -0800 (PST)
\r
39 Received: from localhost (215.42.233.220.static.exetel.com.au.
\r
41 by mx.google.com with ESMTPS id uq1sm21505480igc.5.2013.03.06.03.08.53
\r
42 (version=TLSv1.2 cipher=RC4-SHA bits=128/128);
\r
43 Wed, 06 Mar 2013 03:08:55 -0800 (PST)
\r
44 Date: Wed, 6 Mar 2013 22:08:49 +1100
\r
45 Message-ID: <20130306220849.GB5730@hili.localdomain>
\r
46 From: Peter Wang <novalazy@gmail.com>
\r
47 To: Jani Nikula <jani@nikula.org>
\r
48 Subject: Re: [RFC PATCH 3/3] cli: support Mail-Followup-To: in notmuch reply
\r
49 In-Reply-To: <871ubwdcy7.fsf@nikula.org>
\r
51 <5eaa3acc22ee5513bdce5ab931b7a79ade880e06.1362254104.git.jani@nikula.org>
\r
52 <f9c7258be72bec0b174553db0410c29eba2745fa.1362254104.git.jani@nikula.org>
\r
53 <20130303120745.GA4884@hili.localdomain> <871ubwdcy7.fsf@nikula.org>
\r
55 Content-Type: text/plain; charset=utf-8
\r
56 Content-Disposition: inline
\r
57 Content-Transfer-Encoding: 8bit
\r
58 Cc: notmuch@notmuchmail.org
\r
59 X-BeenThere: notmuch@notmuchmail.org
\r
60 X-Mailman-Version: 2.1.13
\r
62 List-Id: "Use and development of the notmuch mail system."
\r
63 <notmuch.notmuchmail.org>
\r
64 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
65 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
66 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
67 List-Post: <mailto:notmuch@notmuchmail.org>
\r
68 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
69 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
70 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
71 X-List-Received-Date: Wed, 06 Mar 2013 11:09:08 -0000
\r
73 On Sun, 03 Mar 2013 11:56:00 +0200, Jani Nikula <jani@nikula.org> wrote:
\r
74 > I have added the reply.honor_followup_to configuration because, although
\r
75 > widely used, it's not a standard, and therefore some people might not
\r
76 > like to respect that. Although I'd argue if the sender of the message
\r
77 > has added that header, it's the sender's wish it should be respected.
\r
79 > If people think our reply-all should always and unconditionally respect
\r
80 > Mail-Followup-To if it's present, I'd be happy to throw out the config
\r
81 > option. It's ugly.
\r
83 How about making it it optional on the command-line rather than through
\r
84 configuration? Then you don't lose the functionality where you can
\r
85 initiate a reply to all visible From/To/Cc addresses (ready for pruning),
\r
86 regardless of the value of some header you probably don't even see, even
\r
87 if typically you *do* want to respect that header.
\r
89 (Bringing us back to the three reply functions.)
\r