[44net] Re: Mailman migration

I'm a newcomer to the project and the list, still working on getting some time to actually get my endpoint up and running -- so I don't have a lot of history on this. I think discourse is a great piece of software if you're looking to host a web discussion forum, but that's not always the best way to manage communication, and the feedback so far seems like people prefer email for this particular group. From what I've seen, that makes sense to me. Anything you get from the internet is "cloud based" one way or another. I think the sentiment that people are expressing isn't about where the infrastructure lives, but more about using the walled gardens that are SaaS products. There are legitimate concerns here. A paid service can change the rules at any time. They can, and often do, treat you like a product, selling information about you to other organizations for their benefit, and not really for yours. They can decide to just close their doors, or terminate the product and give you nothing. Not wanting to be subject to this is not unreasonable. I am in multiple groups.io <http://groups.io> lists. I don't love it, but it's not the worst thing ever -- aside from the above concerns that come with any hosted solution of that sort. If I do get any veto influence I would use it on any suggestion of using discord. I abhor discord for all of the above reasons, plus their abominable terms of service which, among other things, bar you from using any other client but theirs. (It's technically feasible, but if they discover it they ban you.) No bridges, no unified clients, nothing. They are the worst and I hate that they've gotten so much traction despite being such a garbage organization. On Thu, Apr 21, 2022 at 8:07 AM Chris Smith via 44net &lt;44net(a)mailman.ampr.org <mailto:44net@mailman.ampr.org>> wrote: Hello All, FYI, we had an issue with the mailing list server last week: The server the mailing list is hosted on experienced an unexpected reboot. The server came back up ok and all the services associated with the mailing list continued to run, so Nagios (the application we use to monitor our systems) did not report any issues. However, the sudden reboot had corrupted several open files associated with the mailing list software (Mailman 2.1) and the 44net mailing list was not passing emails. As the list often goes through quiet periods this was not noticed for several days. Unfortunately the backup period for the server was only set to a few days and by the time the issue was investigated all the available backups were of the corrupted files. As the longer term plan was always to migrate from the older (now unsupported) Mailman 2.1 to the latest Mailman 3.1 the decision was taken to migrate the mailing list to a new server. ARDC already has a Mailman 3 server for some internal mailing lists, so we migrated the 44net list there. I am pleased to report that the archives from the old server were successfully migrated over, so no loss of data there thankfully. The web interface for the new home of 44net can be found here: https://mailman.ardc.net/mailman3/postorius/lists/44net.mailman.ampr.org/ The MX record has been updated to point to the new server, so you should continue to send emails to 44net(a)mailman.ampr.org <mailto:44net@mailman.ampr.org> to post to the list. I want to take this opportunity to thank John - KI5D for hosting the mailing list since we had the last big crash in 2012. The mailman server, with John looking after it has provided excellent service to the community. John is going to continue to help out by acting as admin for the 44net mailing list on it’s new home. Best 73, Chris - G1FEF _______________________________________________ 44net mailing list -- 44net(a)mailman.ampr.org <mailto:44net@mailman.ampr.org> To unsubscribe send an email to 44net-leave(a)mailman.ampr.org <mailto:44net-leave@mailman.ampr.org> _______________________________________________ 44net mailing list -- 44net(a)mailman.ampr.org To unsubscribe send an email to 44net-leave(a)mailman.ampr.org