doc: fix links to our mailing lists

Their implementation was changed.
Fortunately I was able to find the message in Google's cache
and thus discover easily which one it is in the new archive.

NEWS

@@ -624,7 +624,7 @@ Incompatible changes
   it will be later reworked to reflect development in IEFT dnsop working group
 - version module was permanently removed because it was not really used by users;
   if you want to receive notifications about new releases please subscribe to
-  https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-resolver-announce
+  https://lists.nic.cz/postorius/lists/knot-resolver-announce.lists.nic.cz/
 
 Bugfixes
 --------

README.md

@@ -68,6 +68,6 @@ See the documentation at [knot-resolver.readthedocs.io][doc] for more options.
 ### Contacting us
 
 - [GitLab issues](https://gitlab.nic.cz/knot/knot-resolver/issues) (you may authenticate via GitHub)
-- [mailing list](https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-resolver-users)
+- [mailing list](https://lists.nic.cz/postorius/lists/knot-resolver-announce.lists.nic.cz/)
 - [![Join the chat at https://gitter.im/CZ-NIC/knot-resolver](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/CZ-NIC/knot-resolver?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
 

doc/config-debugging.rst

@@ -6,7 +6,7 @@ Debugging options
 In case the resolver crashes, it is often helpful to collect a coredump from
 the crashed process. Configuring the system to collect coredump from crashed
 process is out of the scope of this documentation, but some tips can be found
-`here <https://lists.nic.cz/pipermail/knot-resolver-users/2019/000239.html>`_.
+`here <https://lists.nic.cz/hyperkitty/list/knot-resolver-users@lists.nic.cz/message/GUHW4JSDXZ6SZUAYYQ3U2WWOZEIVVF2S/>`_.
 
 Kresd uses its own mechanism for assertions. They are checks that should always
 pass and indicate some weird or unexpected state if they don't. In such cases,