1 Return-Path: <sojkam1@fel.cvut.cz>
\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 arlo.cworth.org (Postfix) with ESMTP id 6B75F6DE1772
\r
6 for <notmuch@notmuchmail.org>; Tue, 29 Dec 2015 13:54:54 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at cworth.org
\r
11 X-Spam-Status: No, score=-1.494 tagged_above=-999 required=5 tests=[AWL=1.356,
\r
12 RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.55] autolearn=disabled
\r
13 Received: from arlo.cworth.org ([127.0.0.1])
\r
14 by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id lwfC0uhgjIHZ for <notmuch@notmuchmail.org>;
\r
16 Tue, 29 Dec 2015 13:54:51 -0800 (PST)
\r
17 Received: from max.feld.cvut.cz (max.feld.cvut.cz [147.32.192.36])
\r
18 by arlo.cworth.org (Postfix) with ESMTP id 82BBC6DE1767
\r
19 for <notmuch@notmuchmail.org>; Tue, 29 Dec 2015 13:54:51 -0800 (PST)
\r
20 Received: from localhost (unknown [192.168.200.7])
\r
21 by max.feld.cvut.cz (Postfix) with ESMTP id E930A19F4524;
\r
22 Tue, 29 Dec 2015 22:54:48 +0100 (CET)
\r
23 X-Virus-Scanned: IMAP STYX AMAVIS
\r
24 Received: from max.feld.cvut.cz ([192.168.200.1])
\r
25 by localhost (styx.feld.cvut.cz [192.168.200.7]) (amavisd-new, port 10044)
\r
26 with ESMTP id yDJf6pusg0tG; Tue, 29 Dec 2015 22:54:46 +0100 (CET)
\r
27 Received: from imap.feld.cvut.cz (imap.feld.cvut.cz [147.32.192.34])
\r
28 by max.feld.cvut.cz (Postfix) with ESMTP id 9739219F42E4;
\r
29 Tue, 29 Dec 2015 22:54:46 +0100 (CET)
\r
30 Received: from wsh by steelpick.2x.cz with local (Exim 4.86)
\r
31 (envelope-from <sojkam1@fel.cvut.cz>)
\r
32 id 1aE2E9-0003y4-Q4; Tue, 29 Dec 2015 22:54:45 +0100
\r
33 From: Michal Sojka <sojkam1@fel.cvut.cz>
\r
34 To: Jani Nikula <jani@nikula.org>, Damien Cassou <damien@cassou.me>,
\r
35 David Bremner <david@tethera.net>, notmuch@notmuchmail.org
\r
36 Subject: Re: notmuch-reply doesn't use Reply-To
\r
37 In-Reply-To: <87twnygmps.fsf@nikula.org>
\r
38 References: <8737vjcx9b.fsf@cassou.me> <8737vi8l7j.fsf@zancas.localnet>
\r
39 <87fuzi9ng5.fsf@cassou.me> <87twnygmps.fsf@nikula.org>
\r
40 User-Agent: Notmuch/0.21+30~g55c056a (http://notmuchmail.org) Emacs/24.5.1
\r
41 (x86_64-pc-linux-gnu)
\r
42 Date: Tue, 29 Dec 2015 22:54:45 +0100
\r
43 Message-ID: <8760zgdioq.fsf@steelpick.2x.cz>
\r
45 Content-Type: text/plain
\r
46 X-BeenThere: notmuch@notmuchmail.org
\r
47 X-Mailman-Version: 2.1.20
\r
49 List-Id: "Use and development of the notmuch mail system."
\r
50 <notmuch.notmuchmail.org>
\r
51 List-Unsubscribe: <https://notmuchmail.org/mailman/options/notmuch>,
\r
52 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
53 List-Archive: <http://notmuchmail.org/pipermail/notmuch/>
\r
54 List-Post: <mailto:notmuch@notmuchmail.org>
\r
55 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
56 List-Subscribe: <https://notmuchmail.org/mailman/listinfo/notmuch>,
\r
57 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
58 X-List-Received-Date: Tue, 29 Dec 2015 21:54:54 -0000
\r
62 On Fri, Dec 04 2015, Jani Nikula wrote:
\r
63 > On Fri, 04 Dec 2015, Damien Cassou <damien@cassou.me> wrote:
\r
64 >> David Bremner <david@tethera.net> writes:
\r
66 >>> Damien Cassou <damien@cassou.me> writes:
\r
68 >>>> "To" : "rmod@inria.fr",
\r
69 >>>> "Reply-To" : "rmod@inria.fr",
\r
70 >>>> "From" : "seaside@rmod.inria.fr",
\r
71 >>>> "Subject" : "[rmod] [Mm10s] 2015-11-30",
\r
72 >>>> "Date" : "Mon, 30 Nov 2015 07:00:01 +0100"
\r
74 >>> A quick look at the code suggests this is falling victim to the
\r
75 >>> "reply-to munging" detection code, which considers a reply-to field
\r
76 >>> redudant if it duplicates one of the other fields. From the source
\r
78 >>> /* Some mailing lists munge the Reply-To header despite it being A Bad
\r
79 >>> * Thing, see http://www.unicom.com/pw/reply-to-harmful.html
\r
81 >>> * The munging is easy to detect, because it results in a
\r
82 >>> * redundant reply-to header, (with an address that already exists
\r
83 >>> * in either To or Cc). So in this case, we ignore the Reply-To
\r
84 >>> * field and use the From header. This ensures the original sender
\r
85 >>> * will get the reply even if not subscribed to the list. Note
\r
86 >>> * that the address in the Reply-To header will always appear in
\r
91 >> The last sentence seems to contradict my example:
\r
93 >> Note that the address in the Reply-To header will always appear in
\r
96 >> Here is the reply message, and it does not contain the address in Reply-To.
\r
98 > This was true way back when notmuch reply only knew about reply all. For
\r
99 > --reply-to=sender, it's broken. The simplest "fix" might be
\r
101 I don't think that this is broken for two reasons:
\r
103 1. In tests/T230-reply-to-sender.sh, there is "Un-munging Reply-To"
\r
104 test, which checks the same combination of headers as in Damien's
\r
105 case and uses --reply-to=sender. The test passes and the reply has
\r
108 2. When replying to mailing lists using reply-to munging, current
\r
109 notmuch behavior allows me to decide whether to reply 1) privately to
\r
110 the mail sender (--reply-to=sender) or 2) to the mailing list
\r
111 (--reply-to=all). The proposed change would make option 1) harder.
\r
113 Therefore I suggest to fix this by applying the documentation patch from
\r
114 the follow-up mail.
\r