update link to Chip Rosenthal article about reply-to munging

The original link is currently returning an internal server error :(

diff --git a/notmuch-reply.c b/notmuch-reply.c
index a74194a31e4fc7be9505659a973146fc70a295b2..457e54ab07f5df7b29591b5a84606ee89533e566 100644 (file)
--- a/notmuch-reply.c
+++ b/notmuch-reply.c
@@ -324,7 +324,7 @@ add_recipients_from_message (GMimeMessage *reply,
     unsigned int n = 0;
 
     /* Some mailing lists munge the Reply-To header despite it being A Bad
-     * Thing, see http://www.unicom.com/pw/reply-to-harmful.html
+     * Thing, see http://marc.merlins.org/netrants/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