---

Give out x7k2p9qzrm@yourdomain.com instead of your real address. Whatever gets sent to it is parsed, cleaned up, and delivered to Discord. Torch it when you're done.

Two moving parts

A core that generates addresses, tracks who owns them, parses incoming mail, and doesn't care where any of it came from or where it's going. Two things plug into it:

• Where mail comes from. Cloudflare (Email Routing + D1), your own server (SMTP + SQLite), or mail.tm (no domain, no server).
• Where mail goes. Discord.

Pick one from each list.

Setup guides

• Cloudflare Workers: no server to run, just a Cloudflare account and a domain.
• Self-hosted: your own machine, your own domain, your own uptime.
• mail.tm: no domain or server at all. Read the caveat in that guide first, mail.tm's domain is a known temp-mail domain and some signup forms block it.
• Discord setup: same steps regardless of which of the above you picked. Commands (/new /list /extend /torch) are documented there.

One hosting guide, plus the Discord guide.

How it works

1. /new generates a random address and stores who owns it.
2. You hand it out.
3. Mail arrives. The receiver looks up the owner. Missing, expired, or torched: dropped, no bounce, nothing logged.
4. Valid: the mail gets parsed (HTML to readable text, links intact, attachments forwarded) and sent to Discord.

Daily cleanup clears expired/torched addresses and stale rate-limit rows, on every path.

Delivery is always a DM, even if the bot's in a server and you ran /new in a channel there. Nothing posts anywhere public.

Architecture

src/core/             Address CRUD, rate limiting, dispatch, MIME parsing.
                       Doesn't import from adapters/ or storage/.
src/core/storage.ts    SqlExecutor: the run/first/all interface core runs
                       SQL against. D1 and SQLite are both SQLite dialect,
                       so core/db.ts and core/ratelimit.ts are shared
                       between them word for word.
src/storage/           d1.ts and sqlite.ts, the two SqlExecutor drivers.
src/adapters/          Delivery adapters. discord/ ships built in.
src/worker.ts          Cloudflare entrypoint.
src/node/               Self-hosted entrypoint (SMTP server, HTTP server
                         for the Discord webhook, cleanup schedule).
src/receivers/mailtm/  mail.tm entrypoint (API client, poller instead of
                         SMTP, its own cleanup that deletes the mail.tm
                         account before dropping the row).

Extending it

Delivery adapter. Implement MailAdapter in src/core/types.ts: a name, and a deliver(owner, mail) that returns { success, error? } and never throws. Register it in buildAdapters().

Storage or receiving backend. Implement SqlExecutor in src/core/storage.ts. Call handleInboundEmail({ to, from, raw }, db, dispatcher) from core/email.ts for each piece of mail. raw takes a Buffer, ReadableStream, or string, whatever postal-mime accepts.

Limits

• 5 active addresses per owner, 10 day expiry. Both configurable.
• DM bodies cap at 1500 characters inline, longer gets attached as message.txt.
• Inbound HTML caps at 256KB before parsing (parsing cost scales quadratically with input, and addresses are reachable by anyone who learns one).
• Attachments forward individually up to 25MB combined per email. Over budget gets dropped with a note, not the whole batch.

License

MIT. See LICENSE.