Where Does Mailman Store Lists and Data?
Where Mailman 3 keeps lists, archives, queues, and config under its var directory tree on Linux servers..
Last updated
Mailman 3 organizes everything under a var directory whose location follows the install method. Distro packages use the FHS tree with lists, archives, data, and queues in standard spots. Source installs default to local var trees instead.
The info command prints the resolved paths for your exact setup, which beats guessing across packaging styles. Queues, locks, and logs branch beside the data. Backups need the var tree plus config and database together. Skip any one leg and restores fail halfway.
Where Mailman stores this, by platform
/var/lib/mailman/lists
Holds lists, archives, data, queues, and templates per install layout; source builds use local var trees instead. Run the info command to print your resolved paths. Back up var plus config and database with services stopped.
Frequently asked questions
how do I migrate Mailman to a new server
Copy the lists, archives, and data folders from the var tree with services stopped, plus mailman.cfg and the database. Templates customize per level from site to list. HyperKitty archives need their own export when used.
paths differ from the docs, why
Check which layout the install uses: distro packages follow FHS while source installs default elsewhere. The info command prints every resolved directory. Debian source guides often land in /opt paths instead.
how do I customize list mail templates
Drop template files into the templates tree at site, domain, or list level for headers, footers, and notices. Core picks them up by level automatically. Keep custom templates outside package dirs to survive upgrades.
Notice an outdated path? Let us know.