We aim to release Mailman 3.0 on Thursday, April 16, 2015.
This page is where we are collecting the feature list and other artifacts for Mailman 3.0, which will be a major upgrade for the project. Many things that people have been wanting for years will be addressed, most notably a unified user database, true virtual domain support, and backing the Mailman data in a real database layer. From a development perspective, we will be adopting a very strict test-driven development model, utilizing modern Python technology and coding styles. The focus will be on providing core Mailman functionality through a REST API, architecturally separate components loosing communicating for better system administration and development lifecycles, while continuing the tradition of providing a turnkey solution with all the necessary parts, making it even easier to download, install, and go.
Contributors are welcome and encouraged! Discussions will happen on the mailman-developers mailing list. Anyone can check out and use the current development source branches. The TODO list below is not a commitment of features (unless marked with a Done ).
Development and status
Mailman 3 is essentially five projects:
Mailman 3.0 is most suitable to new installations of Mailman. We do not guarantee that it will work well for migrations and upgrades of Mailman 2.x; we believe that will work, but encourage you to make backups and test your migrations first. It is not yet at full feature parity with Mailman 2.x, but we're working on that for 3.1.
To Do List
- Update installation HOWTO(s)
- Write release notes and announcement
- Test new installs of 3.0 suite
subscription moderation (see bug 1058449)
Post HOWTO, release notes & announcement
TODOs for the next point release of 3.x:
- Mailman Suite:
Internationalization - there must be a way for the community to contribute translations and for us to integrate them into releases (bug 1414154)
Migration scripts for current Mailman 2 installations (bug 965532)
- Test migration from 2 to 3
Mailman 2 & 3 co-existing
- Make it easier to install with Docker
- Subscription policy: dealing with permission to unsubscribe
- Implementation of django-browserid + custom audience checking
- Add user settings page (Likely to be completed as part of stylistica's summer of code work; may need temporary fix sooner)
Add ability to remove moderators/owners from a list (see bug 1062889)
non-member disposition [Put list of non-members in list settings with allow/deny, etc] (see bug 1414149)
Pull list of supported languages for a domain from Mailman core via API (see bug 1414298)
- if a nonmember replies via the web interface, subscribe them as nondelivery member
Currently the best path for installing the entire Mailman 3 suite at once is Mailman Bundler:
If you're installing on Ubuntu, see DEV/Mailman 3.0/Mailman 3.0 Suite Install on Ubuntu for the commands to install the prerequisites.
We do eventually hope to have appropriate packages for some popular distros, so if you prefer packages only, please be patient!
If you want to try Mailman 3 suite out in Docker, you might want to see DEV/Mailman 3.0/Mailman 3.0 Suite Dockerfile. I am still looking for someone to help provide nice instructions on how to use this, including connecting port 8000 inside the container to a port on the outside so that the tutorial can end with "and now go to http://localhost:8000/mailman3 to check out the web interface!"