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 8FC1B431FBD
\r
6 for <notmuch@notmuchmail.org>; Sat, 2 Mar 2013 17:07:52 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5
\r
12 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
\r
13 FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 qgHu2+Cpxj8M for <notmuch@notmuchmail.org>;
\r
17 Sat, 2 Mar 2013 17:07:52 -0800 (PST)
\r
18 Received: from mail-pb0-f45.google.com (mail-pb0-f45.google.com
\r
19 [209.85.160.45]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
\r
20 (No client certificate requested)
\r
21 by olra.theworths.org (Postfix) with ESMTPS id 01F99431FAF
\r
22 for <notmuch@notmuchmail.org>; Sat, 2 Mar 2013 17:07:51 -0800 (PST)
\r
23 Received: by mail-pb0-f45.google.com with SMTP id ro8so2432653pbb.18
\r
24 for <notmuch@notmuchmail.org>; Sat, 02 Mar 2013 17:07:51 -0800 (PST)
\r
25 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
\r
26 h=x-received:date:message-id:from:to:cc:subject:in-reply-to
\r
27 :references:mime-version:content-type:content-disposition
\r
28 :content-transfer-encoding;
\r
29 bh=Yw6jyLo4T2qD9BVoK5vTGA7MbZRztmxMk/xN4JbaQhc=;
\r
30 b=uVXkRGa3fw0MlQtFGHhbUE43WFbtGoesRYX3bq2MeeL6Ilde9Bwyw+Dv9oby2iW0mc
\r
31 4Hjq5Ohb8p592zdotM7HzQ15fA9WqT0KveT0hR603fRvdx2xZB75w6Rqodo93Ty+WRMP
\r
32 awVxOkVd1Z6U+lS5P6PVjo1mac8N21eIFPWNV2Wsz+qRbmsPry7PMuFQGM0ivI/Bodg7
\r
33 npRvol6pISOEDxowm/FauztuvbaZh0Lnebloc/AycmHzEiRlCz9qaIF5YP7MHKOkkCaP
\r
34 ZPL3UGeyjz08EMpv2xM5FazJ2mv/L7+GB04tj52NrxGeBq1XjKcCsWuEsESkFV6ZGkW3
\r
36 X-Received: by 10.66.4.193 with SMTP id m1mr25243093pam.214.1362272871134;
\r
37 Sat, 02 Mar 2013 17:07:51 -0800 (PST)
\r
38 Received: from localhost (215.42.233.220.static.exetel.com.au.
\r
39 [220.233.42.215]) by mx.google.com with ESMTPS id
\r
40 rr14sm17045838pbb.34.2013.03.02.17.07.48
\r
41 (version=TLSv1.2 cipher=RC4-SHA bits=128/128);
\r
42 Sat, 02 Mar 2013 17:07:49 -0800 (PST)
\r
43 Date: Sun, 3 Mar 2013 12:07:45 +1100
\r
44 Message-ID: <20130303120745.GA4884@hili.localdomain>
\r
45 From: Peter Wang <novalazy@gmail.com>
\r
46 To: Jani Nikula <jani@nikula.org>
\r
47 Subject: Re: [RFC PATCH 3/3] cli: support Mail-Followup-To: in notmuch reply
\r
49 <f9c7258be72bec0b174553db0410c29eba2745fa.1362254104.git.jani@nikula.org>
\r
51 <5eaa3acc22ee5513bdce5ab931b7a79ade880e06.1362254104.git.jani@nikula.org>
\r
52 <f9c7258be72bec0b174553db0410c29eba2745fa.1362254104.git.jani@nikula.org>
\r
54 Content-Type: text/plain; charset=utf-8
\r
55 Content-Disposition: inline
\r
56 Content-Transfer-Encoding: 8bit
\r
57 Cc: notmuch@notmuchmail.org
\r
58 X-BeenThere: notmuch@notmuchmail.org
\r
59 X-Mailman-Version: 2.1.13
\r
61 List-Id: "Use and development of the notmuch mail system."
\r
62 <notmuch.notmuchmail.org>
\r
63 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
64 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
65 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
66 List-Post: <mailto:notmuch@notmuchmail.org>
\r
67 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
68 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
69 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
70 X-List-Received-Date: Sun, 03 Mar 2013 01:07:52 -0000
\r
72 On Sat, 2 Mar 2013 21:55:21 +0200, Jani Nikula <jani@nikula.org> wrote:
\r
73 > Use Mail-Followup-To header to determine recipients according to
\r
74 > http://cr.yp.to/proto/replyto.html if configured and present in the
\r
75 > message being replied to.
\r
77 I would like to see an option to --reply-to=list that, as far as
\r
78 possible, does the right thing. If we had that, do we need
\r
79 reply.honor_followup_to?
\r