From: Tomi Ollila <tomi.ollila@iki.fi>
Date: Fri, 4 Dec 2015 15:06:11 +0000 (+0200)
Subject: Re: notmuch-reply doesn't use Reply-To
X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=d8775cc0db34cd81e2cea1900f5872b18586b244;p=notmuch-archives.git

Re: notmuch-reply doesn't use Reply-To
---

diff --git a/5c/9d48dc12677a9df3d79d3e67907bf13f496263 b/5c/9d48dc12677a9df3d79d3e67907bf13f496263
new file mode 100644
index 000000000..7bf94a088
--- /dev/null
+++ b/5c/9d48dc12677a9df3d79d3e67907bf13f496263
@@ -0,0 +1,79 @@
+Return-Path: <tomi.ollila@iki.fi>
+X-Original-To: notmuch@notmuchmail.org
+Delivered-To: notmuch@notmuchmail.org
+Received: from localhost (localhost [127.0.0.1])
+ by arlo.cworth.org (Postfix) with ESMTP id 7FD5B6DE0FF7
+ for <notmuch@notmuchmail.org>; Fri,  4 Dec 2015 07:06:10 -0800 (PST)
+X-Virus-Scanned: Debian amavisd-new at cworth.org
+X-Spam-Flag: NO
+X-Spam-Score: 0.711
+X-Spam-Level: 
+X-Spam-Status: No, score=0.711 tagged_above=-999 required=5 tests=[AWL=0.059, 
+ SPF_NEUTRAL=0.652] autolearn=disabled
+Received: from arlo.cworth.org ([127.0.0.1])
+ by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)
+ with ESMTP id GYIaFM7fcMPT for <notmuch@notmuchmail.org>;
+ Fri,  4 Dec 2015 07:06:04 -0800 (PST)
+Received: from guru.guru-group.fi (guru.guru-group.fi [46.183.73.34])
+ by arlo.cworth.org (Postfix) with ESMTP id 59BCD6DE1009
+ for <notmuch@notmuchmail.org>; Fri,  4 Dec 2015 07:06:03 -0800 (PST)
+Received: from guru.guru-group.fi (localhost [IPv6:::1])
+ by guru.guru-group.fi (Postfix) with ESMTP id C58C4100080
+ for <notmuch@notmuchmail.org>; Fri,  4 Dec 2015 17:06:11 +0200 (EET)
+From: Tomi Ollila <tomi.ollila@iki.fi>
+To: notmuch@notmuchmail.org
+Subject: Re: notmuch-reply doesn't use Reply-To
+In-Reply-To: <8737vi8l7j.fsf@zancas.localnet>
+References: <8737vjcx9b.fsf@cassou.me> <8737vi8l7j.fsf@zancas.localnet>
+User-Agent: Notmuch/0.21+32~g73439f8 (http://notmuchmail.org) Emacs/24.3.1
+ (x86_64-unknown-linux-gnu)
+X-Face: HhBM'cA~<r"^Xv\KRN0P{vn'Y"Kd;zg_y3S[4)KSN~s?O\"QPoL
+ $[Xv_BD:i/F$WiEWax}R(MPS`^UaptOGD`*/=@\1lKoVa9tnrg0TW?"r7aRtgk[F
+ !)g;OY^,BjTbr)Np:%c_o'jj,Z
+Date: Fri, 04 Dec 2015 17:06:11 +0200
+Message-ID: <m28u5a1cf0.fsf@guru.guru-group.fi>
+MIME-Version: 1.0
+Content-Type: text/plain
+X-BeenThere: notmuch@notmuchmail.org
+X-Mailman-Version: 2.1.20
+Precedence: list
+List-Id: "Use and development of the notmuch mail system."
+ <notmuch.notmuchmail.org>
+List-Unsubscribe: <https://notmuchmail.org/mailman/options/notmuch>,
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
+List-Archive: <http://notmuchmail.org/pipermail/notmuch/>
+List-Post: <mailto:notmuch@notmuchmail.org>
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
+List-Subscribe: <https://notmuchmail.org/mailman/listinfo/notmuch>,
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
+X-List-Received-Date: Fri, 04 Dec 2015 15:06:10 -0000
+
+On Fri, Dec 04 2015, David Bremner <david@tethera.net> wrote:
+
+> Damien Cassou <damien@cassou.me> writes:
+>
+>>                    "To" : "rmod@inria.fr",
+>>                    "Reply-To" : "rmod@inria.fr",
+>>                    "From" : "seaside@rmod.inria.fr",
+>>                    "Subject" : "[rmod] [Mm10s] 2015-11-30",
+>>                    "Date" : "Mon, 30 Nov 2015 07:00:01 +0100"
+>
+> A quick look at the code suggests this is falling victim to the
+> "reply-to munging" detection code, which considers a reply-to field
+> redudant if it duplicates one of the other fields. From the source
+>
+>     /* Some mailing lists munge the Reply-To header despite it being A Bad
+>      * Thing, see http://www.unicom.com/pw/reply-to-harmful.html
+>      *
+>      * The munging is easy to detect, because it results in a
+>      * redundant reply-to header, (with an address that already exists
+>      * in either To or Cc). So in this case, we ignore the Reply-To
+>      * field and use the From header. This ensures the original sender
+>      * will get the reply even if not subscribed to the list. Note
+>      * that the address in the Reply-To header will always appear in
+>      * the reply.
+>      */
+
+For anyone who did that feature, Thank You ! :D
+
+Tomi