"compare": ["receiver.email", "mailpit"]
Receiver.email vs Mailpit
Mailpit is a free, MIT-licensed SMTP server and web UI you run yourself, as a single binary or a Docker image: your app sends to it and nothing is delivered. It adds HTML compatibility, link and spam checks, a REST API and a webhook for new mail. Receiver.email is hosted, with real addresses that any sender on the internet can reach, and one long-poll call returns the email with its code and links extracted.
For local development, and CI jobs where you control the app's SMTP settings, choose Mailpit. When the email has to reach a real address (a deployed staging environment, a third-party sender such as an auth provider, or an AI agent signing up on another site), choose Receiver.email.
MailHog is the older SMTP catcher Mailpit was inspired by. Its latest release is still 1.0.1, and Mailpit's README describes it as no longer maintained, so the Mailpit column below is the one to read for both.
Pick Mailpit if
You develop locally or run CI where the app sends through SMTP settings you control, want it free and offline, check HTML, links and spam scores, or mail must never leave your network.
Pick Receiver.email if
The email comes from a sender that delivers to real addresses, tests run against a deployed environment, an agent signs up on sites you don’t control, or you want waits and extracted codes without hosting anything.
Last checked November 2026.
Feature by feature.
| Feature | Receiver.email | Mailpit |
|---|---|---|
| How mail arrives | Public catch-all: any-prefix-<project>@receiver.email, from any sender | An SMTP server you run (port 1025 by default); your app sends to it and nothing is delivered |
| Who can send to it | Anyone on the internet: the addresses are real | Whatever is configured to use its SMTP server |
| Addresses | Unlimited per project, no setup per address | Any: it captures whatever address your app sends to |
| Free option | Free plan: 100 emails/month, 1 project | Free, open source (MIT) |
| Entry paid plan | Starter: $29/month, 10,000 emails/month | None: you host and maintain it |
| Self-hosted | No, cloud only | Yes: a single binary or a Docker image |
| Works offline | No | Yes |
| Retention | 7 days (Free), 30 (Starter), 90 (Pro), up to 365 (Enterprise) | The newest 500 messages by default, optionally by age |
| Wait for an email in a test | waitFor() long-poll, default 30 s, any length | No wait endpoint; poll the REST API, or use the webhook or WebSocket |
| Verification code extraction | waitForOtp(): 4, 6 or 8 digits, or 6 to 8 letters and digits | No |
| Link extraction | Yes | A link checker tests the links in a message |
| Webhooks | Signed email.received | One URL per instance, 1 request/s by default |
| HTML compatibility check | No | Yes |
| Spam scores | No | SpamAssassin or Rspamd |
| SMTP capture and POP3 | No | Yes |
| Simulated SMTP errors | No | Chaos feature |
| Send or relay mail | No. Receive-only (a test email to your own address) | Relays or forwards captured mail through an external SMTP server |
| Client libraries | TypeScript, Python | None official; a REST API |
| MCP server for AI agents | Yes: hosted (mcp.receiver.email, API key) or local (npx) | n/c |
| Command-line client | Yes | n/c |
Last checked November 2026. Competitor details come from each vendor's own pricing and documentation pages, listed below. Plans change, so confirm on their site before you buy. n/c means we could not confirm it from those pages, not that it's missing. Spotted something out of date? Email [email protected].
When to choose Mailpit
- Local development: see every email your app sends, offline and free.
- CI where the app under test runs in the same job and you control its SMTP settings, with no external service or API key.
- You check HTML compatibility, links and spam scores before release.
- You want to test how your app copes with SMTP errors, using Mailpit’s chaos feature.
- Mail must never leave your network.
When to choose Receiver.email
- The email comes from a service that delivers to real addresses, not through your SMTP server: an auth provider’s default sender, a payment processor.
- Tests run against a deployed staging or preview environment you don’t want to reconfigure.
- An AI agent signs up on sites you don’t control.
- You want waits and extracted codes and links, without hosting anything.
- Several CI runners and teammates share one place to read test mail, kept 7 to 365 days by plan.
Moving from Mailpit
There is nothing to run. Instead of pointing the app's SMTP settings at Mailpit, let it send through its real provider to an address you mint with inboxes.create(), then wait by recipient from that address's createdAt where you used to poll Mailpit's API. Coming from MailHog, the same applies: its list, read and delete calls become one wait.
One thing does not carry over: Receiver.email only receives mail sent to its own addresses. If you rely on Mailpit to stop a local app emailing real people, keep it for that.
| Mailpit | Receiver.email |
|---|---|
| SMTP host and port in app config (port 1025) | Your app’s real email provider, sending to a receiver.email address |
| Any address the app sends to | inboxes.create({ prefix }) → prefix-xxxxxx-<project>@receiver.email |
| Polling the REST API, or the new-message webhook | emails.waitFor({ recipient, since, timeout }), or a signed webhook |
| Reading the code out of the body | emails.waitForOtp(...).code |
| Web UI on port 8025 | The dashboard’s live inbox |
| Deleting messages between runs | Nothing to delete: wait from since, and mail expires with your plan’s retention |
import { ReceiverClient } from "@receiverdotemail/sdk";
const receiver = new ReceiverClient(); // reads RECEIVER_API_KEY
const inbox = await receiver.inboxes.create({ prefix: "signup" });
await app.signUp(inbox.address); // [email protected]
// Long-polls until a matching email lands (throws on timeout)
const otp = await receiver.emails.waitForOtp({
recipient: inbox.address,
since: inbox.createdAt,
timeout: 60,
});
otp.code; // "847291"
// Or wait for the email itself and use its extracted links
const email = await receiver.emails.waitFor({ recipient: inbox.address, since: inbox.createdAt });
email.links; // ["https://app.example.com/verify?token=..."]from receiverdotemail import ReceiverClient
async with ReceiverClient() as receiver: # reads RECEIVER_API_KEY
inbox = await receiver.inboxes.create(prefix="signup")
await app.sign_up(inbox.address)
# Long-polls until a matching email lands (raises on timeout)
otp = await receiver.emails.wait_for_otp(
recipient=inbox.address,
since=inbox.created_at,
timeout=60,
)
otp.code # "847291"Full walkthrough in the Quick Start. Plans and limits are on the pricing page.
Try it on one test
Free tier: 100 emails a month, one project, unlimited addresses. No credit card required.