The server has probably been repurposed for other mailing lists. What you are seeing could just a side effect of leaving the list up in read-only mode.
Part of the FOSS philosophy goes beyond just software, and into data integrity. While the operators of the list may have decided to move on, and disabled it for futher communication, they probably chose to leave it up as a historical record. Why not let people continue to access the list in read only mode? If someone were to take an interest in any conversations that once took place there, they could subscribe and access any archives that were created. Don't confuse the act of disabling NEW messages with the act of removing OLD messages. On Mon, Sep 2, 2019 at 5:39 AM Rich Shepard <[email protected]> wrote: > On Sun, 1 Sep 2019, wes wrote: > > > Most likely answer is that the operator did not actually delete the > > mailing list from Mailman. Possibly simply disabled incoming delivery, > > which effectively disables the list while maintaining the message archive > > and subscriber list, etc. > > Wes, > > Okay. I didn't know one could do this with Mailman and don't understand why > one would do so rather than just shutting down the server (in the case of > the single mail list). A few years ago I tried hosting a couple of mail > lists for volunteer groups but the potentail users found it too difficult > to > subscribe and use so I dropped the lists and de-activated Mailman. > > Regards, > > Rich > > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
