Public | Automated Build

Last pushed: 7 months ago
Short Description
With HTACCESS secured Mailhog, e.g. to run Mailhog with public access.
Full Description

Secure Mailhog Docker Image

What and Why

This secured Mailhog-Image is created by me for a university-project. I had running this Image on a public server, so I had to secure the frontend.
You only will be able to access the Mailhog with the HTACCESS-Credentials you set on run.

This instance will run with a in-memory-database, so if you stop the container it could happen, that all information are lost.


docker run -td -e 'MH_USER=myuser' -e 'MH_PWD=mypw' -p 25:1025 -p 8025:8025 aeimer/mailhog-secure

The default credentials are mhog => mhog123, change them with the environment-variables MH_USER and MH_PWD.


I currently updated this image to use mailhog/mailhog as the base image, so I can activate automated rebuilds.

Docker Pull Command
Source Repository