point list archives to the nmweb frontend

2 files changed, 3 insertions, 3 deletions

diff --git a/contributing.mdwn b/contributing.mdwn
index b5e6cf9..34b7eb6 100644
--- a/contributing.mdwn
+++ b/contributing.mdwn
@@ -158,7 +158,7 @@ If you are submitting a non-trivial set of patches, or if there's any
 extra information you want to share that is not really part of the
 commit messages, it is advisable to write a cover letter to give an
 overview of your work. See the
-[Notmuch mailing list archives](https://notmuchmail.org/pipermail/notmuch/)
+[Notmuch mailing list archives](https://nmbug.notmuchmail.org/nmweb/)
 for examples. Use the `--cover-letter` option of `git format-patch`,
 or `--compose` option of `git send-email`.
 
@@ -180,7 +180,7 @@ usually by one or two developers, depending on the impact of the
 changes. You are expected to follow up on the review comments you
 receive, either by discussing the comments and the code, or modifying
 your patches. Again, see the [Notmuch mailing list
-archives](https://notmuchmail.org/pipermail/notmuch/) for examples.
+archives](https://nmbug.notmuchmail.org/nmweb) for examples.
 
 ## Send another round addressing review comments
 
diff --git a/index.mdwn b/index.mdwn
index 068aea0..9b688af 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -120,7 +120,7 @@ Comments? Please feel free to email the notmuch mailing list:
 also subscribe to the
 [notmuch mailing list](https://nmbug.notmuchmail.org/list/)). You
 can also browse the
-[online list archives](https://notmuchmail.org/pipermail/notmuch/),
+[online list archives](https://nmbug.notmuchmail.org/nmweb/),
 read them as a
 [web forum (nabble)](http://notmuch.198994.n3.nabble.com/), or
 download an [mbox file](https://notmuchmail.org/archives/notmuch.mbox)