diff options
| author | Daniel Kahn Gillmor <dkg@fifthhorseman.net> | 2016-06-02 12:26:12 -0400 |
|---|---|---|
| committer | David Bremner <david@tethera.net> | 2016-06-05 08:26:54 -0300 |
| commit | 385f62baa1df439cb6365101faf31c0f6f2f2935 (patch) | |
| tree | 58d522a5bb0e332e3284c8ee97c6838895d61c7a | |
| parent | 8540c36a96f5270d84d19dcbfbc9f6463f1653fd (diff) | |
update link to Chip Rosenthal article about reply-to munging
The original link is currently returning an internal server error :(
| -rw-r--r-- | notmuch-reply.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/notmuch-reply.c b/notmuch-reply.c index a74194a3..457e54ab 100644 --- 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 |