Philipp Marek (@pmarek) on GitLab, 2018-11-07.
References: * http://docs.mailman3.org/en/latest/migration.html * http://docs.mailman3.org/en/latest/prodsetup.html#mailman-3-in-docker
Status:
Bad email addresses that cause bounces won't yet remove the receiver address from a mailing list (2018-11-07):
Mailman 3 doesn’t have support for bounce processing yet, but it is on the roadmap.
if I read that correctly. Should we wait a bit for that to be fixed?
Archive the archives ;)
We need to archive the current HTML pages:
URLs to archived messages will break
and setup a new page tree; I don't think loosing all the links is acceptable. Creating redirects from all the old to the new ML posts is quite some effort.
Migration effort
As of now, there isn’t a turnkey solution to migrate all your lists from Mailman 2 to Mailman 3,
I don't know (yet) how many lists there are --
Docker
Debian has mailman3 packages available out-of-the-box (3.2.0-2 in testing/unstable, at least); this means that any security or other updates would get installed[1] automatically. All the hassles with docker volumes etc. could be avoided.
Ad 1: At least, if we'd pin that package to testing or unstable until the next Debian release is out, which would include mailman3 by default.
Philipp Marek (@pmarek) on GitLab, 2018-11-07.
I guess the best way is to keep the archives as they are, and migrate live lists' web pages to https://mailman3.common-lisp.net.
Administrator (@root) on GitLab, 2018-11-07.
We have Docker installed on our server. I've wondered if we want /need to use Docker images for greater flexibility and keeping up with recent Mailman versions, especially due to the limitations that you've just documented (and my personal naive hope that they get fixed at some point). After they get fixed, it's likely to take quite some time before those fixes hit Debian...
Erik Huelsmann (@ehuelsmann) on GitLab, 2018-11-07.
A thought about the number of mailing lists we have and the use of mailman3: maybe we can migrate only a few at first to build up some experience and confidence.
Erik Huelsmann (@ehuelsmann) on GitLab, 2018-11-07.
@pmarek regarding rewrite rules: we're managing an extensive list of rewrite rules and even "rewrite maps" (programs that generate rewrite responses) to make sure we cover renamed resources and keep the links "alive". Preferably, we keep the current links in working order as we have with our current archives (the directories exist, but mailman isn't aware of their existence -- a trick that worked well to keep the links working correctly).
Dave Cooper (@dcooper) on GitLab, 2026-10-01.
The lists have been moved to Mailman 3 by Erik Huelsmann. Closing — thank you, Erik.
Sign in to comment.