smtp4dev
github.com
- Free plan
- Windows
- macOS
- Linux
- Web
- API
- Self-hosted
What smtp4dev is
smtp4dev is a free fake SMTP server for development and testing, allowing teams to inspect email without delivering messages to real customers. It accepts SMTP mail and provides IMAP and POP3 access for retrieving or deleting test messages. The interface includes SMTP session logs, multipart MIME inspection, HTML rendering, validation, compatibility reports, and a viewport switcher for mobile email views. A terminal UI provides the full functionality. Developers can configure multiple mailboxes and routing rules, compose or reply to messages, and relay mail with optional automatic rules. TLS/SSL supports implicit and STARTTLS modes, with generated self-signed certificates and optional authentication. An OpenAPI/Swagger API supports automated tests and external applications, while documented integrations include REST use, SignalR notifications, Testcontainers examples, and direct .NET server use. Deployment options include winget, Docker/OCI images, a .NET global tool, and GitHub releases. Docker-published ports can expose captured email externally, so localhost binding is recommended when outside access is unnecessary.
Who it suits
smtp4dev is aimed at advanced email development, production-like testing, development teams, and CI/CD pipelines. It supports Windows, Linux, macOS, self-hosted deployments, web access, APIs, and containers.
Good to know, and what to watch
- Prevents test email reaching real customers
- Supports SMTP, IMAP, and POP3
- Includes MIME inspection and HTML rendering
- Offers OpenAPI/Swagger automation
- Provides TLS/SSL and optional authentication
- Docker ports may expose captured emails
- Windows winget requires Windows 10 1809 or newer
- Self-hosted configuration is required
The verdict
smtp4dev gives development teams a broad local email-testing environment with protocol access, inspection tools, security settings, and automation APIs. Teams deploying containers should pay close attention to port binding so captured messages are not exposed externally.
What the maker publishes
- API
- The project provides an OpenAPI/Swagger API. source
- API and automation
- An API is available for automated tests and external applications, with endpoints for messages, sessions, mailboxes, and server status and configuration. source
- Client integration
- Applications can connect by SMTP using the host and port where smtp4dev runs; the documentation gives localhost and port 25 as defaults. source
- Configuration
- Settings can be changed in the UI, appsettings.json, environment variables, or command-line arguments. source
- Deployment
- Installation options include winget, Docker/OCI images, a .NET global tool, and GitHub release downloads. source
- Docker security
- The maintainer warns that Docker-published ports may be accessible outside the host and recommends binding to 127.0.0.1 when external access is not needed. source
- Email protocols
- It supports SMTP and provides IMAP and POP3 access to retrieve and delete messages. source
- License
- The GitHub repository identifies the project license as BSD-3-Clause. source
- Mail handling
- Users can configure multiple mailboxes and routing rules, compose or reply to messages, and relay messages with optional automatic rules. source
- Mail protocols
- It supports SMTP, IMAP, and POP3 for receiving, retrieving, and deleting test messages. source
- Message inspection
- Features include SMTP session logs, multipart MIME inspection, HTML rendering, validation, and compatibility reports. source
- Platforms
- The project offers Windows and Linux binaries and containers, plus a .NET SDK tool for platforms where the SDK is available; its README also names Mac OS X. source
- Platforms and distribution
- The project offers Windows and Linux binaries and containers, and a .NET SDK tool for platforms where the SDK is available; its README also names Windows, Linux, and Mac OS X. source
- Purpose
- smtp4dev is a fake SMTP server for development and testing, letting developers test email without sending it to real customers. source
- Security configuration
- The Docker security guide warns that published ports may expose captured emails externally and recommends binding ports to localhost unless outside access is needed. source
- Security features
- It supports TLS/SSL with implicit and STARTTLS modes, automatically generated self-signed certificates, and optional authentication. source
- SMTP debugging
- The product provides SMTP session logging and supports scripting expressions for error simulation. source
- Testing integrations
- The testing guide covers programmatic use with the REST API, SignalR email notifications, Testcontainers examples for multiple programming languages, and direct use of the SMTP server component in .NET. source
- Testing tools
- The interface includes a viewport size switcher for simulating mobile email views and a terminal UI with full functionality. source
- Who it is for
- The README describes it for advanced email development and testing, production-like testing, development teams, and CI/CD pipelines. source
- Windows requirement
- The winget instructions specify Windows 10 version 1809 (build 17763) or newer. source
Checked against the maker's pages on 8 Oct 2026.