--- /dev/null
+Return-Path: <dkg@fifthhorseman.net>\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 111F26DE02A6\r
+ for <notmuch@notmuchmail.org>; Thu, 2 Jun 2016 09:26:24 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.022\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.022 tagged_above=-999 required=5\r
+ tests=[AWL=-0.022] 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 c7PLEoycDnhA for <notmuch@notmuchmail.org>;\r
+ Thu, 2 Jun 2016 09:26:16 -0700 (PDT)\r
+Received: from che.mayfirst.org (che.mayfirst.org [162.247.75.118])\r
+ by arlo.cworth.org (Postfix) with ESMTP id D13B26DE02A9\r
+ for <notmuch@notmuchmail.org>; Thu, 2 Jun 2016 09:26:15 -0700 (PDT)\r
+Received: from fifthhorseman.net (unknown [38.109.115.130])\r
+ by che.mayfirst.org (Postfix) with ESMTPSA id 6C104F99A\r
+ for <notmuch@notmuchmail.org>; Thu, 2 Jun 2016 12:26:15 -0400 (EDT)\r
+Received: by fifthhorseman.net (Postfix, from userid 1000)\r
+ id DABFB20258; Thu, 2 Jun 2016 12:26:14 -0400 (EDT)\r
+From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>\r
+To: Notmuch Mail <notmuch@notmuchmail.org>\r
+Subject: [PATCH 3/5] update link to Chip Rosenthal article about reply-to\r
+ munging\r
+Date: Thu, 2 Jun 2016 12:26:12 -0400\r
+Message-Id: <1464884774-22961-3-git-send-email-dkg@fifthhorseman.net>\r
+X-Mailer: git-send-email 2.8.1\r
+In-Reply-To: <1464884774-22961-1-git-send-email-dkg@fifthhorseman.net>\r
+References: <1464884774-22961-1-git-send-email-dkg@fifthhorseman.net>\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: Thu, 02 Jun 2016 16:26:24 -0000\r
+\r
+The original link is currently returning an internal server error :(\r
+---\r
+ notmuch-reply.c | 2 +-\r
+ 1 file changed, 1 insertion(+), 1 deletion(-)\r
+\r
+diff --git a/notmuch-reply.c b/notmuch-reply.c\r
+index a74194a..457e54a 100644\r
+--- a/notmuch-reply.c\r
++++ b/notmuch-reply.c\r
+@@ -324,7 +324,7 @@ add_recipients_from_message (GMimeMessage *reply,\r
+ unsigned int n = 0;\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
++ * Thing, see http://marc.merlins.org/netrants/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
+-- \r
+2.8.1\r
+\r