// FIELD NOTES · QA & SMTP
Temporary email for developers and QA
A disposable inbox is the fastest way to watch a real verification email arrive while you are building a signup flow. It is also the wrong tool for automated tests. This page explains the difference, so you do not build a pipeline on something that will disappear in twenty minutes.
Why developers use a disposable inbox
- Your real mailbox stays clean: no test accounts, no verification spam, no unread counters.
- No setup: the address exists before you finish reading this sentence.
- You see the real message a real provider would send, including headers, links and attachments.
- Nothing to tear down afterwards: the inbox expires on its own.
What 20 Minute Mail gives you in a test
- A real address on a real domain, so third-party services accept it.
- Live delivery over a browser connection — no refresh needed.
- HTML rendered in a sandboxed frame, which is also useful to check how your template behaves.
- Attachments listed separately and downloadable.
.emldownload of the whole message, for inspecting raw MIME.- Mail rules by sender, subject or recipient, when you need to reject or route test traffic.
What it deliberately does not do
- You cannot create an address programmatically.
- You cannot poll messages from a script or assert on them in CI.
- You cannot send or reply from the address.
- The session lasts twenty minutes by default and cannot be extended indefinitely.
- Some providers block disposable domains outright, which is a property of their risk scoring, not a bug here.
The right tool for each job
| Job | Use | Why |
|---|---|---|
| Explore a signup form by hand | 20 Minute Mail | Zero setup, live inbox, real domain |
| Assert on email in CI | Local sink: Mailpit, MailHog, smtp4dev | Programmatic, deterministic, no expiry |
| Test a third-party service | Disposable inbox | You cannot point their servers at your local sink |
| Automated inbox API | Mailinator, Mail.tm | Documented APIs and paid tiers |
Using a disposable address where a local sink belongs is the most common mistake in this category: tests become flaky, run against a shared domain, and fail when the session expires.
A simple signup-flow test
-
1 · Open the inbox first
Copy the address from the top bar before submitting the form. Opening it afterwards still works, but starting with it avoids missing a fast message.
-
2 · Submit the form
Use the temporary address in your staging form. Watch the inbox: the message appears without a refresh.
-
3 · Inspect the message
Open the raw
.emlto check headers, links and the MIME structure. Test the verification link in a private window. -
4 · Clean up by doing nothing
When the session ends, the address and its messages are deleted. If you need the address for a second pass, save the recovery code before closing the page.
FAQ
Can I read the inbox from a script?
No public API. Use a local SMTP sink for automation and keep a disposable inbox for manual checks.
Do attachments work?
Yes, they are listed and downloadable, and the whole message can be
saved as an .eml file.
How long do I have?
Twenty minutes, extendable by another twenty. Enough for a manual verification flow, not for a long suite.
Can I use it in CI?
Not reliably: no API, no programmatic creation, and an expiry timer.