[self-follow-up] I have the list administration password. Thanks, Dave!
I proceeded with some list-administrative activity.
1. I populated or updated the descriptions of the three lists.
https://lists.gnu.org/mailman/listinfo/groff
https://lists.gnu.org/mailman/listinfo/bug-groff
https://lists.gnu.org/mailman/listinfo/groff-commit
2. I added myself as a list administrator. Werner was (and remains)
also an admin of all three lists, and Dave of bug-groff.
3. I set up an explicit Reply-To: header for the bug-groff and
groff-commit lists to direct follow-ups to this list.
4. I changed the moderation options of the bug-groff and groff-commit
lists. (Mailman calls these "Privacy options...", not very
intuitively.)
All "moderated" members' posts to the lists are now rejected with a
message--or should be. There are no unmoderated members. An
experimental commit to the Git repository, and a similar update to a
Savannah ticket, revealed that some hidden logic does what we want
for Git commits but not Savannah ticket updates. But that's fixed
now, too.[1]
5. I removed a bunch of email addresses of "non-members" (I think that
means non-subscribed email addresses) from static filters variously
automatically accepting or in a very small number of cases,
rejecting posts. Many of the addresses, I did not recognize--I'd
guess that some go back many years. These lists no longer seemed
relevant since now, _everybody_ (except Savannah robots) is
moderated.
For years, our documentation and project homepage have touted the
bug-groff and groff-commit lists as "read-only". Now, at last, perhaps
that's true in practice and not merely intention.
Let me know of any questions or concerns.
Regards,
Branden
[1] I think I've got the bug-groff problem solved with a crude and
obvious hack via the admin web interface.
signature.asc
Description: PGP signature
