Skip to content
nofeb

Solutions / QA of email flows

Throwaway inboxes for testing email flows

For qa and platform teams testing sign-up and notification mail

Every product with sign-up has email in its critical path, and most test suites skip it because checking a mailbox is slow and flaky.

The problem

Parallel tests need their own addresses, a fast way to wait for mail, and structured access to the codes and links inside it.

How it runs on nofeb

  1. Create an inbox per test with a short time to live; it deletes itself.
  2. Trigger the flow, then call wait_for_email with a subject or sender filter.
  3. Assert on the extracted codes and links, or on the raw message byte-exact.
  4. Mail between inboxes on the platform is delivered internally, so a test can also play both sides.
  5. A harness that already reads mail over IMAP or POP3 points at nofeb instead of a test mail server: the username is the inbox address and the password an app password created for it.
  6. A test dashboard can follow every inbox in the run over the WebSocket stream, filtered to message.* events.
  7. After a long run, search across the run's inboxes for the message that went missing, by subject, sender or the words in it.

Where nofeb stops

  • nofeb receives real mail on real addresses; it is not a capture-everything sandbox for mail your staging systems send to arbitrary recipients. Use a sending sandbox for that.

Status of everything this relies on

CapabilityWhat it doesStatus
Disposable inboxes with a time to live Give an inbox a lifetime in seconds; it and its mail are removed when it expires, and an event says so. Shipped
Unlimited inboxes Create as many inboxes as the work needs, with a generated or chosen address and an idempotent client reference. Shipped
Wait for an email Long-poll an inbox for up to a minute until a message matching sender, subject or has-a-code arrives. Shipped
One-time code and link extraction Verification codes and classified links are pulled out of every message and returned as fields. Shipped
Delivery between inboxes Mail between inboxes on the platform is delivered internally, for agent-to-agent workflows and test environments. Shipped
Byte-exact raw messages Download any stored message exactly as it was received. Shipped
Idempotent sends Retry a send with the same Idempotency-Key and it is sent once. Shipped
IMAP and POP3 IMAP4rev2 (with IMAP4rev1 compatibility, IDLE, CONDSTORE and QRESYNC) and POP3 on every inbox, over TLS only, signed in with the inbox address and an API key or a revocable per-inbox app password. Shipped
Realtime stream A WebSocket stream of the same events as webhooks and the feed, in order, resumable from a cursor with no gap and no duplicates, and filtered by inbox, pod or event type within the credential's own reach. Shipped
Search that understands Full-text and semantic search over subjects, addresses, the new text of each message, attachment names and attachment text, across every inbox a key can see. Filter by inbox, pod, folder, thread, sender, recipient, date, attachments, keywords, authentication failures and metadata; results carry highlighted snippets and can be grouped by thread. Shipped