docker-mailserver is inspired by the renowned ISPMail guide. This project lets you run your own email services, giving you independence from large providers. It is a secure, customizable, and feature-rich solution for managing your email infrastructure.

Container images are built on Alpine Linux or vendor base images and are kept lightweight.

Changelog Upgrade Guide

• Secure email protocols: POP3, IMAP, and SMTP with user authentication
• Web-based management interface for account, domain, and alias administration
• Intuitive webmail interface
• Fetchmail integration to retrieve emails from external providers
• DKIM message signing for email authenticity
• Server-side mail filtering with configurable rules via a web frontend
• Spam filter training by simply moving emails to or from the junk folder
• Real-time spam prevention using RBLs (Real-Time Blackhole Lists)
• Selective greylisting for likely spam
• Support for catch-all email addresses
• Support for send-only accounts restricted from receiving emails
• Restriction of sender addresses for enhanced security
• Configurable address extensions using the '-' delimiter
• Quota management with notifications when quotas are exceeded
• Enforced TLS for secure communication
• Full-text search (FTS) support for efficient message searching
• Continuous self-monitoring via Docker healthcheck
• Developed with a strong focus on quality assurance

1. Run git clone git@github.com:jeboehm/docker-mailserver.git
2. Copy the file .env.dist to .env and change the variables in it according to your needs. The variables are described in the docs.
3. Run bin/production.sh pull to download the images.
4. Run bin/production.sh up -d to start the services.
5. After a few seconds, you can access the services listed in the section Ports overview.
6. Create your first email address and an admin user by running bin/production.sh run --rm web setup.sh. The wizard will ask you a few questions to set everything up.
7. Now you can log in to the management interface with your new account credentials.

Kubernetes installation is a first-class citizen. You can use the kustomization.yaml file to deploy the mailserver to your Kubernetes cluster.

Important: Installing on Kubernetes requires an existing MySQL-compatible database (for example, MySQL or Percona XtraDB). The provided kustomization does not provision a database. Configure the database connection in your .env and supply credentials as Kubernetes Secrets before applying the manifests. See the Kustomize External Database and HTTPS Ingress Example and the documentation Use another MySQL instance for details.

1. Run git clone git@github.com:jeboehm/docker-mailserver.git
2. Copy the file .env.dist to .env and change the variables in it according to your needs. The variables are described in the docs.
3. Run kubectl create namespace mail
4. Run bin/create-tls-certs.sh
5. Run kubectl create -n mail secret tls tls-certs --cert=config/tls/tls.crt --key=config/tls/tls.key
6. Run kubectl apply -n mail -k .

• Upgrade Guide
• Environment Variables
• Features
• Service Architecture
• Roundcube Configuration
• TLS Configuration
• External MySQL
• Relayhost Configuration
• PHP Sessions
• Installation:
  • Kustomize External Database and HTTPS Ingress Example
  • Compose Traefik Reverse Proxy Example
• Developer Guide

• Issues
• mailserver-admin
• fetchmailmgr