Actually, I'm now finding that this *did* happen, but there was a cron job to compensate for mailman's instability which was restarting mailman on an hourly basis, which obviously nullifies any attempts to remove it from the init scripts...I've now removed the restarter scripts too.Regards,Erik.On Sat, Jul 13, 2024 at 10:17 AM Erik Huelsmann <ehuels@gmail.com> wrote:The idea was to disable mailman2 after a few weeks. However, this hasn't happened until today. I will switch off list processing on the old mailing lists now that the only thing being sent to them is spam in the first place.Regards,Erik.On Sat, Jul 15, 2023 at 1:08 PM Erik Huelsmann <ehuels@gmail.com> wrote:All,Now that the 50 most active projects have been migrated to Mailman3 (available through https://mailman3.common-lisp.net/), I've disabled the web-ui for Mailman2. This means that the page listing the available mailing lists (https://mailman.common-lisp.net/listinfo) now forwards to mailman3's list management page (https://mailman3.common-lisp.net/postorius). All related entry-points for managing lists also have been disabled (meaning: /admin, /admindb, /create, etc.).The old archives are still available. They're listed at https://mailman.common-lisp.net/pipermail/ (which is where they've always been). I have no intention to remove these archives at this point, although we may want to point users to the fact that mailman3 is where new archives are being accumulated, especially on the thread/date index pages.Regards,
--
--
--