See also
Mailman3 has multiple components. Each doing a different thing. This is a simplified overview.
How To
Create a mailing list
Disable or re-enable a mailing list
Remove a mailing list
Note: unless you know what you're doing, don't actually do this. It most likely does not do what you want. Just disable the list (see above) instead.
Remove a message from the mailing list archives
Delete the whole thread
Delete a single message
Export a listing of all subscribers to a mailing list
Check if an email address is subscribed to any lists
Remove an individual from all mailing lists
Reset a user's password
Rename a mailing list
Import from Google Groups
It is straightforward to migrate a list from Google Groups to Mailman. A list owner in Google should use Google Takeout (see documentation) to export the member list (members.csv) and archives (topics.mbox). File a task requesting a new list and include a link to the Takeout result (if the list contents are private, provide this information to the Mailman admins/SRE team privately).
Create the new list in Mailman like normal, then use the "Mass subscription" form at <​​> to import the existing subscribers.
Copy the mbox to the mailing list server and run:
sudo mailman-web hyperkitty_import -l /path/to/topics.mbox
This might take a while because of the "Synchronizing properties with Mailman" step, that's fine.
Then update the search index:
sudo mailman-web update_index_one_list
All done! Make sure to have the list owner in Google disable the group there, and remind subscribers to update the lists' email address to LISTNAME@​lists.​
Add a list to Gmane
A new list can be added to Gmane very easily if the first message has not already been sent or history is not important. If the history needs to be imported, a ticket should be file in Phabricator with projects 'Wikimedia-Mailing-list' and 'operations' (easy link stating which list needs to imported and to which Gmane group if it exists already.

Docs and links
Site Administrator docs on
Authorized recipients for
Anyone with a signed NDA can be on the mailing list. For a list of signed NDAs for staff/contractors there is T83783, WMF-NDA and ldap/nda (or ldap/wmf).
Migrate servers
See Mailman/Migration for comments made about past migrations (lily to sodium, sodium to fermium, fermium to lists1001).
Upgrading Mailman3
When upgrading Mailman3 packages for a version that includes schema changes, use the following process.
  1. Downtime host in icinga
  2. Disable puppet
  3. Manually stop mailman3 and mailman3-web systemd services
  4. Run apt to install the new packages
  5. Run sudo mailman-wrapper help to apply the mailman3 schema updates (yes, running just the "help" command will apply the schema changes)
  6. Run sudo mailman-wrapper help again to make sure the schema update didn't obviously break anything.
  7. Run sudo mailman-web migrate to apply the mailman3 schema updates
  8. Clear static CSS/JS caches: sudo mailman-web collectstatic --clear --noinput && sudo mailman-web compress
  9. Start mailman3 and mailman3-web systemd services again, keep an eye on errors in the logs
  10. Re-enable puppet and remove icinga downtime if it hasn't expired yet.
Post upgrade:
Verify that the messages the MediaWiki Installer screen-scrapes haven't changed.
Configuration details
The new Mailman3 setup lives on lists1001. Some state is under /var/lib/mailman3/, the global configuration is in /etc/mailman/ via Puppet.
The mail server used is Exim, the web server used is Apache.
We are currently using custom backported packages of the mailman3 suite. A few patches have been cherry-picked from upstream to fix issues we've run into. The packaging Git repositories can be found on apt1001 in legoktm's home directory.
There is currently one change that is hotpatched and not in the package yet.
Mailman setup
Mail server setup
See Mailman/MTA
Web server setup
To get Mailman running with Apache the puppet class role::lists is applied which uses module mailman. Puppet module mailman uses puppet module Apache which sets up Apache and the site config is in the template
lists1001 is backed up to backup1001 using Bacula. All of /var/lib/mailman3 is backed up, which potentially includes on-disk templates and the search index. We do not back up /var/lib/mailman3/web which comes from the package and digests that haven't been sent yet.
The database lives on m5, which is also regularly backed up into Bacula, too.
Tested failure modes
Because mail delivery and transport should be reliable, I have tested what happens in certain failure modes, e.g. when SpamAssassin's spamd daemon is not running.
Spamd not running
Because of the /defer_ok modifiers in the Exim ACLs, Exim will act as if no spam filtering attempts are made when spamd is not running, and will accept the message. The following lines are logged:
spam acl condition: warning - spamd connection to, port 783 failed: Connection refused spam acl condition: all spamd servers failed H=xxx.xxxxxxx.xx [xx.xx.xx.xx]:xxxx I=[]:25 U=exim Warning: ACL "warn" statement skipped: condition test deferred
Mailman not running
If the Mailman queue runner daemons are not running, incoming messages will still get delivered to the Mailman queue by Exim. However, nothing else will happen until the Mailman processes are started.
Spam fighting
See Mailman/Spam fighting
Most emails sent out by Mailman3 can be customized using "templates". You can see the default English templates. You can edit them by visiting​YOURLISTNAME​​. These are translatable on
It may also be useful to read the template documentation (the code parts can be ignored).
See Mailman/Monitoring
Who has access?
The following people have "superuser" access via the web UI for admin access to all lists:
Mailman2 data
Most private Mailman2 data is backed up in bacula in a long-term backup (details). See how to restore a file.
Last edited on 15 September 2021, at 18:57
Content is available under CC BY-SA 3.0 unless otherwise noted.
Privacy policy
Terms of Use
 Home Random Log in  Settings  Donate  About Wikitech  Disclaimers