remove references to the mailing list in the manual and replace with forum link, if needed

doc/src/Build_windows.rst

@@ -73,8 +73,9 @@ configuration should set this up automatically, but is untested.
 In case of problems, you are recommended to contact somebody with
 experience in using Cygwin.  If you do come across portability problems
 requiring changes to the LAMMPS source code, or figure out corrections
-yourself, please report them on the lammps-users mailing list, or file
-them as an issue or pull request on the LAMMPS GitHub project.
+yourself, please report them on the
+`LAMMPS forum at MatSci <https://matsci.org/c/lammps/lammps-development/>`_,
+or file them as an issue or pull request on the LAMMPS GitHub project.
 
 .. _msvc:
 
@@ -117,8 +118,8 @@ LAMMPS with MPI enabled.
 .. note::
 
    This is work in progress and you should contact the LAMMPS developers
-   via GitHub, the forum, or the mailing list, if you have questions or
-   LAMMPS specific problems.
+   via GitHub or the `LAMMPS forum at MatSci <https://matsci.org/c/lammps/lammps-development/>`_,
+   if you have questions or LAMMPS specific problems.
 
 .. _cross:
 

doc/src/Errors_bugs.rst

@@ -17,9 +17,8 @@ the steps outlined below:
    if your issue has already been reported and if it is still open.
  * Check the `GitHub Pull Requests page <https://github.com/lammps/lammps/pulls>`_
    to see if there is already a fix for your bug pending.
- * Check the `mailing list archives <https://www.lammps.org/mail.html>`_ or
-   the `LAMMPS forum <https://www.lammps.org/forum.html>`_ to see if the
-   issue has been discussed before.
+ * Check the `LAMMPS forum at MatSci <https://matsci.org/lammps/>`_
+   to see if the issue has been discussed before.
 
 If none of these steps yields any useful information, please file a new
 bug report on the `GitHub Issue page <https://github.com/lammps/lammps/issues>`_.
@@ -38,12 +37,9 @@ generate this restart from a data file or a simple additional input.
 This input deck can be used with tools like a debugger or `valgrind
 <https://valgrind.org>`_ to further :doc:`debug the crash <Errors_debug>`.
 
-You may also send an email to the LAMMPS mailing list at
-"lammps-users at lists.sourceforge.net" describing the problem with the
-same kind of information.  The mailing list can provide a faster response,
-especially if the bug reported is actually expected behavior.  But because
-of the high volume of the mailing list, it can happen that your e-mail
-is overlooked and then forgotten.  Issues on GitHub have to be explicitly
-closed, so that will *guarantee* that at least one LAMMPS developer will
-have looked at it.
+You may also post a message in the `development category of the LAMMPS
+forum at MatSci <https://matsci.org/c/lammps/lammps-development/>`_
+describing the problem with the same kind of information.  The forum can
+provide a faster response, especially if the bug reported is actually
+expected behavior or other LAMMPS users have come across it before.
 

doc/src/Intro_website.rst

@@ -20,7 +20,6 @@ available online are listed below.
 * `Glossary of terms relevant to LAMMPS <https://www.lammps.org/glossary.html>`_
 * `LAMMPS highlights with images <https://www.lammps.org/pictures.html>`_
 * `LAMMPS highlights with movies <https://www.lammps.org/movies.html>`_
-* `Mailing list <https://www.lammps.org/mail.html>`_
 * `LAMMPS forum <https://www.lammps.org/forum.html>`_
 * `Workshops <https://www.lammps.org/workshops.html>`_
 * `Tutorials <https://www.lammps.org/tutorials.html>`_

doc/src/Manual.rst

@@ -14,11 +14,11 @@ LAMMPS is an open-source code, distributed freely under the terms of
 the GNU Public License Version 2 (GPLv2).
 
 The `LAMMPS website <lws_>`_ has a variety of information about the
-code.  It includes links to an on-line version of this manual, a
-`mailing list <https://www.lammps.org/mail.html>`_ and
-`online forum <https://www.lammps.org/forum.html>`_  where users can
-post questions, and a `GitHub site <https://github.com/lammps/lammps>`_
-where all LAMMPS development is coordinated.
+code.  It includes links to an on-line version of this manual, an
+`online forum <https://www.lammps.org/forum.html>`_ where users can post
+questions and discuss LAMMPS, and a `GitHub site
+<https://github.com/lammps/lammps>`_ where all LAMMPS development is
+coordinated.
 
 ----------
 

doc/src/Modify_contribute.rst

@@ -27,11 +27,10 @@ join the `LAMMPS developers on Slack <https://lammps.slack.com>`_.  This
 slack work space is by invitation only.  Thus for access, please send an
 e-mail to ``slack@lammps.org`` explaining what part of LAMMPS you are
 working on.  Only discussions related to LAMMPS development are
-tolerated in that work space, so this is **NOT** for people that look for
-help with compiling, installing, or using LAMMPS.  Please post a message
-to the `lammps-users mailing list <https://www.lammps.org/mail.html>`_
-or the `LAMMPS forum <https://www.lammps.org/forum.html>`_ for those
-purposes.
+tolerated in that work space, so this is **NOT** for people that look
+for help with compiling, installing, or using LAMMPS.  Please post a
+message to the `LAMMPS forum <https://www.lammps.org/forum.html>`_ for
+those purposes.
 
 Packages versus individual files
 --------------------------------

doc/src/group.rst

@@ -294,11 +294,13 @@ group and running further.
 
 .. note::
 
-   All fixes and computes take a group ID as an argument, but they
-   do not all allow for use of a dynamic group.  If you get an error
+   All fixes and computes take a group ID as an argument, but they do
+   not all allow for use of a dynamic group.  If you get an error
    message that this is not allowed, but feel that it should be for the
    fix or compute in question, then please post your reasoning to the
-   LAMMPS mail list and we can change it.
+   `LAMMPS forum at MatSci <https://matsci.org/c/lammps-development/>`_
+   and we can look into changing it.  The same applies if you come
+   across inconsistent behavior when dynamic groups are allowed.
 
 The *static* style removes the setting for a dynamic group, converting
 it to a static group (the default).  The atoms in the static group are