MailDev
Node-based local SMTP catcher.
MailDev is a Node-based local SMTP catcher with a web UI. Install it with npm or Docker, point SMTP at port 1025, and read captured mail on port 1080. It can fire a webhook when mail arrives and optionally relay caught messages to a real SMTP host, which is useful in CI.
Judged purely as an API. What the request contract guarantees on retry, how complete the webhook event coverage is, whether suppressions are readable and writable programmatically, and how much the message log retains when something needs debugging in production.
Against high-frequency programmatic sends where a missed delivery is a product failure, MailDev covers webhook coverage, and does not cover idempotency keys, event stream, the suppressions API, batch sending, and SDK breadth. Whether that gap matters depends on how central those are to the build.
- Idempotency keys: No
- Webhooks: Yes
- Event stream: No
- Operating since: Not published
- Suppressions API: No
- Best published rate per 1,000: Tiers not published in comparable form
- Batch sending: No
- SDKs: None
- Deliverability: Not applicable.
Not applicable.
Node-centric local development and CI.
New projects that could start on Mailpit for closer HTML rendering.
- › Installs with a single npm install or docker run
- › SMTP on 1025 with a web UI and REST API on 1080
- › Optional webhook on new mail for CI assertions
- › Relay mode can forward caught mail to a real SMTP host
- › Vue UI renders modern HTML email less faithfully than Mailpit
- › Release cadence is slower than Mailpit
Features at a glance
| API | Yes |
| SMTP | Yes |
| SDKs | None |
| Webhooks | Yes |
| Templates | none |
| React Email | No |
| Batch send | No |
| Scheduled send | No |
| Suppressions | No |
| Multi-tenant | No |
| Inbound parsing | No |
| Event stream | No |
| Idempotency keys | No |
| Dedicated IP | No |