3 ms·
This is interesting, because cPanel still ships with Mailman 2 as the 2->3 archive conversion still has bugs[0]. 0: https://features.cpanel.net/topic/upgrade-t
by syntheticnature 6y ago
This is interesting, because cPanel still ships with Mailman 2 as the 2->3 archive conversion still has bugs[0].
0: https://features.cpanel.net/topic/upgrade-to-mailman-3-0 https://features.cpanel.net/topic/upgrade-to-mailman-3-0
- kazinator 6y agoIf archive "conversion" is an issue, that sounds like the new archive tool that Mailman 3 comes with is not good at importing mbox files and generating an archive from them? That seems hard to believe. I had no issue with this with Lurker. A few times in the (now fairly distant) past I gone in there and blew off all the generated content (after editing an mbox archive file), then re-generated. Since then I developed an invisible delete button right in the web UI, for removing spam from the web archive. If you know where to click, and what the password is, you can blow off any post. An archiver that can't import your historic mbox files has a showstopper issue for anyone with existing archives, and may present a problem to someone who wants to rebuild a damaged web archive.
- syntheticnature 6y agoLooking at that thread, it's not clear whether the problem is the archives or moving some other configuration aspects; it seems like they think an archive-less move is easier, but given there's no support at all...