1 Return-Path: <tomi.ollila@iki.fi>
\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 7FD5B6DE0FF7
\r
6 for <notmuch@notmuchmail.org>; Fri, 4 Dec 2015 07:06:10 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at cworth.org
\r
11 X-Spam-Status: No, score=0.711 tagged_above=-999 required=5 tests=[AWL=0.059,
\r
12 SPF_NEUTRAL=0.652] 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 GYIaFM7fcMPT for <notmuch@notmuchmail.org>;
\r
16 Fri, 4 Dec 2015 07:06:04 -0800 (PST)
\r
17 Received: from guru.guru-group.fi (guru.guru-group.fi [46.183.73.34])
\r
18 by arlo.cworth.org (Postfix) with ESMTP id 59BCD6DE1009
\r
19 for <notmuch@notmuchmail.org>; Fri, 4 Dec 2015 07:06:03 -0800 (PST)
\r
20 Received: from guru.guru-group.fi (localhost [IPv6:::1])
\r
21 by guru.guru-group.fi (Postfix) with ESMTP id C58C4100080
\r
22 for <notmuch@notmuchmail.org>; Fri, 4 Dec 2015 17:06:11 +0200 (EET)
\r
23 From: Tomi Ollila <tomi.ollila@iki.fi>
\r
24 To: notmuch@notmuchmail.org
\r
25 Subject: Re: notmuch-reply doesn't use Reply-To
\r
26 In-Reply-To: <8737vi8l7j.fsf@zancas.localnet>
\r
27 References: <8737vjcx9b.fsf@cassou.me> <8737vi8l7j.fsf@zancas.localnet>
\r
28 User-Agent: Notmuch/0.21+32~g73439f8 (http://notmuchmail.org) Emacs/24.3.1
\r
29 (x86_64-unknown-linux-gnu)
\r
30 X-Face: HhBM'cA~<r"^Xv\KRN0P{vn'Y"Kd;zg_y3S[4)KSN~s?O\"QPoL
\r
31 $[Xv_BD:i/F$WiEWax}R(MPS`^UaptOGD`*/=@\1lKoVa9tnrg0TW?"r7aRtgk[F
\r
32 !)g;OY^,BjTbr)Np:%c_o'jj,Z
\r
33 Date: Fri, 04 Dec 2015 17:06:11 +0200
\r
34 Message-ID: <m28u5a1cf0.fsf@guru.guru-group.fi>
\r
36 Content-Type: text/plain
\r
37 X-BeenThere: notmuch@notmuchmail.org
\r
38 X-Mailman-Version: 2.1.20
\r
40 List-Id: "Use and development of the notmuch mail system."
\r
41 <notmuch.notmuchmail.org>
\r
42 List-Unsubscribe: <https://notmuchmail.org/mailman/options/notmuch>,
\r
43 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
44 List-Archive: <http://notmuchmail.org/pipermail/notmuch/>
\r
45 List-Post: <mailto:notmuch@notmuchmail.org>
\r
46 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
47 List-Subscribe: <https://notmuchmail.org/mailman/listinfo/notmuch>,
\r
48 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
49 X-List-Received-Date: Fri, 04 Dec 2015 15:06:10 -0000
\r
51 On Fri, Dec 04 2015, David Bremner <david@tethera.net> wrote:
\r
53 > Damien Cassou <damien@cassou.me> writes:
\r
55 >> "To" : "rmod@inria.fr",
\r
56 >> "Reply-To" : "rmod@inria.fr",
\r
57 >> "From" : "seaside@rmod.inria.fr",
\r
58 >> "Subject" : "[rmod] [Mm10s] 2015-11-30",
\r
59 >> "Date" : "Mon, 30 Nov 2015 07:00:01 +0100"
\r
61 > A quick look at the code suggests this is falling victim to the
\r
62 > "reply-to munging" detection code, which considers a reply-to field
\r
63 > redudant if it duplicates one of the other fields. From the source
\r
65 > /* Some mailing lists munge the Reply-To header despite it being A Bad
\r
66 > * Thing, see http://www.unicom.com/pw/reply-to-harmful.html
\r
68 > * The munging is easy to detect, because it results in a
\r
69 > * redundant reply-to header, (with an address that already exists
\r
70 > * in either To or Cc). So in this case, we ignore the Reply-To
\r
71 > * field and use the From header. This ensures the original sender
\r
72 > * will get the reply even if not subscribed to the list. Note
\r
73 > * that the address in the Reply-To header will always appear in
\r
77 For anyone who did that feature, Thank You ! :D
\r