Public | Automated Build

Last pushed: 2 years ago
Short Description
Do not Use - In Development
Full Description

mailman container


This is in development and not ready for production!

This aims to be a dockerfile for a working self contained mailman installation complete
with web management interface and postfix, ready to be interfaced with other systems
via SMTP link.

This is intended for a mailman instance running for an entire domain. All mails entering the system
via smtp will be considered to belong to a mailinglist and will be handed down to mailman.


  • postfix that will only relay mails to the outside via a relay host and forward all incoming mails to mailman if it matches any of the configured domains
  • mailman with the storage directory exposed as a docker volume
  • lighttpd to server the management interface
  • ssh server (contained in phusion/baseimage), this is not recommended but can be disabled.

Design considerations

This image was created using phusion/baseimage. Due to the inherent complexity of mailman and my lack of enthusiasm to clearly separate all three components in different images
all three were configured in the same image. Including a postfix installation seems to be the easiest way to make this plug and play.

You should never expose the HTTP or SMTP service directly to the internet, they have been designed to be used behind a reverse proxy and a properly configured mailserver.

The idea is that you run all mailinglists on one (or several) domains and set these up when you first create the docker image.

How to use

This is not yet ready for real use, this image is still in development!

see script for an example on how to create a container.

Docker Pull Command
Source Repository