Configuration

By default, Mailpit listens on port 8025 for the web UI and port 1025 for SMTP.

Mailpit runtime flags & environment variables

Configuration options for the web UI & API, including HTTPS

Configuring SMTP (including STARTTLS or SSL/TLS)

Enable the POP3 server (with or without TLS)

Integrate Mailpit with SpamAssassin to test “spamminess” of messages

Creating a self-signed HTTPS/TLS certificate for HTTP/API, SMTP, and POP3

Creating password files for HTTP/API, SMTP, and POP3

Automatically auto-forward all messages to another email address

Configure message relaying (release) in Mailpit

Monitor Mailpit performance and statistics with Prometheus

How to configure nginx, Apache, or IIS to proxy to Mailpit

Use Mailpit’s Chaos feature to artificially trigger SMTP errors to test application resilience

Tuning Mailpit’s compression levels, RAM & CPU usage

Mailpit stores messages in either a permanent or temporary SQLite database

Common issues and limitations when running Mailpit

Various privacy & security policies enforced by Mailpit

Configuring Mailpit to listen on Unix domain sockets instead of network interfaces