Re: notmuch-reply doesn't use Reply-To
authorTomi Ollila <tomi.ollila@iki.fi>
Fri, 4 Dec 2015 15:06:11 +0000 (17:06 +0200)
committerW. Trevor King <wking@tremily.us>
Sat, 20 Aug 2016 21:50:06 +0000 (14:50 -0700)
5c/9d48dc12677a9df3d79d3e67907bf13f496263 [new file with mode: 0644]

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