The Problem
If you've ever tried to use a disposable email service on Instagram,
TikTok, or Netflix — you know the pain. They get rejected instantly
because platforms maintain blacklists of known fake domains.
I kept hitting this wall while testing registration flows for my
own projects. So I built the solution myself.
The Idea
Instead of fake domains, use real, active Microsoft accounts
as a temporary inbox pool. Assign them to users on demand, let
them receive the verification code, then reclaim the address.
Simple concept. Surprisingly tricky to execute at scale.
Tech Stack
- Backend: Python / Flask
- Database: MySQL (PyMySQL)
- Email access: Microsoft Graph API (OAuth2 + refresh tokens)
- Auth: bcrypt + session-based for web, API key for REST
- Payments: NowPayments (crypto)
- Rate limiting: flask-limiter
The Hard Part — Microsoft Graph API
Getting inbox access via Graph API is straightforward for a single
account. The challenge is doing it for hundreds of accounts without:
- Hitting rate limits
- Token expiry causing missed emails
- Accounts getting flagged for unusual activity
My solution: a warmup step on every new assignment that makes a
lightweight Graph API call to "activate" the session before the
user sends their verification request. This reduced missed emails
significantly.
The API
Every account gets an API key. Developers can automate the whole flow:
Business Model
Pay-as-you-go credits. No subscription. Refund if no email arrives.
This model works well here because users don't need temp emails every day — a subscription would feel like a tax on infrequent use.
What I Learned
The moat isn't the code — it's the operational side (maintaining a healthy account pool)
API-first opens a second market: developers who need this at scale pay more per unit than casual users
Refund policy removes the biggest objection ("what if it doesn't work?")
Try It
🔗 nodemail.store
📄 API Docs
Happy to answer questions about the Graph API integration, the account pool management, or anything else in the comments.