Yeevu Inbox
Mailboxes that land, migrate, and warm up.
Provision mailboxes on a private cluster, copy your existing mail across with folders intact, then warm the new senders inside a closed conversation mesh until providers trust them.
What it does
Three machines, one dashboard.
Each one runs independently. Together they close the gap between “new domain” and “trusted sender”.
Mailboxes on a private cluster.
Add a domain, we queue the DNS plan. DKIM is rotated in place, SPF kept if permissive, MX swung — without flattening the records you already trust. Every change is auditable in dns_actions.
- Cloudflare DNS API — zone-scoped token only
- State: verifying → dns_applied → provisioned
- Yeevu Private Email cluster, SMTPS port 465
Idempotent IMAP → IMAP.
Folders, flags, and the original INTERNALDATE stay put. The poller dedupes by Message-ID, reports progress back, and retries the fragile bits. Run it again — same result.
- Mode 1: onboard to our cluster (recurring sync)
- Mode 2: provider-to-provider (one-time job)
- ~300 messages/min per worker
Real threads. Real replies.
A closed conversation mesh — opened, replied to, starred. The gradient that providers actually score, not synthetic ping-pong. Senders ramp on a schedule that looks like a person.
- Cron: send 5 min · rescue 15 min
- Connect via OAuth (Gmail / Outlook) or IMAP
- 14 – 28 day ramp to inbox placement
The journey
From handshake to first warm send.
Four phases. Clean handoffs. No manual DNS juggling.
- 01< 30 sec
Hand us a domain.
Paste it into /domains/new. We confirm it’s unowned in our cluster, ready the workspace, and queue the DNS plan.
- 02< 2 min
We reconcile DNS, not steamroll it.
DKIM rotated in place. SPF kept if permissive. MX flipped. DMARC left alone. The diff is auditable in
dns_actions. - 03Hours, not days
Mail copies behind the scenes.
The poller does the heavy carry — folders, flags, headers, Message-ID dedupe. You watch a number go up. We retry the 503s.
- 0414 – 28 days
The senders enter the mesh.
A few conversations a day, replied to, marked important — ramping on a schedule that looks like a person. Providers score the gradient.
The contract
Plain English. No asterisks.
Six things we commit to — and keep.
You keep your DNS.
No nameserver delegation needed. The Cloudflare API token is scoped to Zone:DNS:Edit on the zones you authorise — nothing more.
Your credentials, sealed.
Source IMAP credentials are AES-256-GCM at rest. The poller decrypts in memory. Nothing is written to logs.
Migrations are idempotent.
Re-run a job and you get the same mailbox. No duplicates, no missing folders, no read-state anomalies.
Warm-up is a real conversation.
Threads have topics, replies, follow-ups, and silences. Providers score the gradient, not the volume.
You can leave with your mailboxes.
The migrator runs the other way too. We’ll move you off our cluster onto whoever you choose, with the same fidelity.
One worker. One bill.
Procurement, migration, warm-up: the same Cloudflare Worker, the same dashboard, the same invoice. No SaaS nesting dolls.
Ready to ship a sender that lands?
Set up a domain, migrate your mail, and start warming — all from one place.