Mailpit

Overview

Mailpit is a free, open-source local SMTP server and email-testing utility for developers. It suits development and CI/CD workflows that need to inspect and exercise email without sending it to real recipients. Its strongest case is the combination of message inspection, rendering checks, and automation; its default unsecured SMTP setup and finite message retention call for deliberate configuration.

Key features

Inspect messages and catch rendering problems

The web interface presents formatted HTML, highlighted HTML source, text, headers, raw source, and MIME attachments, with thumbnails for image attachments. That breadth is useful when a fault could lie in either the rendered message or its underlying structure. HTML Check applies more than 175 HTML and CSS checks based on compatibility data from caniemail.com; link checks and HTML screenshots add practical ways to catch problems before messages reach customers. Optional SpamAssassin-based checks provide another testing signal, but require SpamAssassin.

Exercise delivery and automate tests

Messages can be tagged, relayed through another SMTP server, automatically forwarded, or made to trigger configurable SMTP errors through the Chaos feature. That makes Mailpit useful not just for viewing output but for checking how an application responds to delivery failures. Its REST API supports accessing, searching, deleting, sending, tagging, and releasing messages, which suits repeatable integration tests. Summary webhooks can send message information to external services; Mailpit has been tested with n8n and offers a Cypress package for integration testing.

Deployment, security, and operating limits

Mailpit runs without additional dependencies as a single binary or multi-architecture Docker image, with static binaries for Windows, Linux, and Mac and Docker images for 386, amd64, and arm64. Its reported ingestion rate is 100–200 emails per second, depending on system and message factors. By default it retains only the most recent 500 messages, while optional POP3 exposes only the latest 100. Those limits are sensible for a test inbox, but longer-running or busier environments may need active message management.

The web UI and API support optional HTTPS and basic authentication; SMTP can use authentication and TLS. However, SMTP defaults to port 1025 without encryption or authentication, so teams should review access and network exposure rather than carry development defaults into an environment where other users can connect. The UI's strict Content-Security-Policy blocks remote content other than images, stylesheets, and fonts, and it sets a no-referrer policy; tracking images remain allowed. Link checking blocks requests to internal networks by default, helping reduce server-side request forgery risk.

Pricing

Mailpit is free and open source. Its single plan costs 0.00 USD per free and includes a static binary or multi-architecture Docker images, with default retention of the most recent 500 emails. There is no paid tier to unlock higher retention or additional capabilities, so this is a strong fit for developers who can work within the default cap or manage messages themselves. The plan's defining trade-off is capacity, not a feature paywall.

Platforms

Mailpit supports Linux, macOS, and Windows, as well as web access, an API, and self-hosted deployment. The binary and Docker options make it suitable for local machines and CI/CD environments; the web interface provides the message-inspection surface.

Who it's for

Mailpit is best for developers who need a local destination for application email, want to inspect message content, or need SMTP behavior in integration tests without contacting real email addresses. It is less suited to teams seeking a managed production delivery service or a long-retention inbox without operating their own setup.

Pros and cons

• Pros: Broad message inspection, including raw content and MIME attachments, helps diagnose both formatting and construction issues.
• Pros: HTML, link, screenshot, and optional spam checks cover several common pre-delivery checks in one utility.
• Pros: REST API, webhooks, and configurable SMTP errors support automated tests and failure scenarios.
• Pros: Free, dependency-free binary and Docker deployment work across local development and CI/CD setups.
• Cons: The default 500-message retention and 100-message POP3 window constrain persistent or high-volume test use.
• Cons: SMTP starts without encryption or authentication, so exposed instances need configuration before broader access.
• Cons: Tracking images are still permitted by the UI's remote-content policy.

Alternatives

For a broader comparison, see Email Testing Software. Choose Twilio Segment instead if you want a freemium web, iOS, and Android platform with a free plan that includes 1,000 visitors per month, 500,000 Reverse ETL records per month, two sources, and 700+ integrations. Choose MailSlurp if you need hosted API and web inbox testing with monthly allowances for received emails, sandbox sends, device renders, and inbox placement tests. Emailens is another freemium web, API, and extension option, with 30 simulated previews per day on its free plan.

GlockApps is an alternative with free spam-test credits, DMARC allowances, uptime monitors, and an IP reputation monitor. SMTP Labs offers a free monthly tier with SMTP, IMAP, POP3, API, and email audit, plus seven-day message retention. Mailgun has a free plan that includes 100 emails per day, email APIs and SMTP relay, a custom sending domain, tracking, analytics, webhooks, and an inbound route. Twilio Email Testing offers a 60-day free trial with three email-testing credits, while its Basic plan starts at 15.00 USD per month with 10 credits. Inbox Monster is a paid alternative with annual creative and SMS suite plans.

Verdict

Choose Mailpit if you want a free, self-hostable tool that lets developers inspect messages and automate email and SMTP tests before they reach real recipients. Its testing breadth is the main reason to choose it; look elsewhere for managed production delivery, or plan additional configuration and message cleanup if the default security and retention settings do not fit your environment.