All Your Inboxes
All your addresses, one inbox — reply from your domain
Like a lot of people here, I run several small products, each on its own domain. Every one of them needs an info@ or support@ that a real customer can write to — and every option for that was bad in its own way: - A mail hosting seat per domain adds up fast when you have five domains and three customers. - Free forwarding tools treat email as developer infrastructure: DNS lessons, another dashboard, and when you reply, it comes from your personal Gmail — which looks amateur and often lands in spam. What I actually wanted was simple: mail sent to any address I own should land in the inbox I already check, and when I hit Reply, the answer should leave from my business address, in the same thread. That product didn't exist in the shape I wanted, so I built it: https://allyourinboxes.com Some things I learned the hard way while building it: 1. Gmail rejects "+" addresses as forwarding targets with a generic "invalid address" error. Nothing in any documentation says this. We rebuilt our whole address scheme around dots because of it. 2. Gmail also silently rate-limits adding forwarding addresses from sessions/IPs it distrusts — same generic error, no matter what you type. The fix is embarrassing: wait a few hours and try once, cleanly. 3. Cloudflare's Email Routing verification endpoint is now behind bot protection, so "we'll auto-click the verification for you" died as a feature. Even a headless browser gets stuck in the challenge loop. We redesigned the flow around one honest human tap instead. 4. If a domain has no MX records at all, mail doesn't bounce — it just evaporates. Our setup now writes the MX records itself and refuses to touch domains that already have a mail provider. Everything we hit is documented in the product's guides, because I never want a customer to debug what I had to debug. The product is live. One inbox is free forever (no card), and I answer support myself — through the product, since our own support@ runs on it. I'd genuinely love feedback from people who juggle multiple domains: what would make you switch, and what would stop you?
4 Comments
I think you might be mixing us up with an accessibility scanner — there's no a11y angle here. But your scan-vs-remediation framing actually maps well onto what we do with email deliverability, so it's a good question in disguise:
We do "scan" (check SPF/DKIM/DMARC on your domains, flag what's broken), but you're right that a report alone is close to worthless — most owners don't want to know their DNS is wrong, they want mail to arrive. So remediation IS the product: we write the missing records ourselves where we can, and keep monitoring so a silently-broken route gets caught before a customer email evaporates.
Too early for me to have real agency data (we're launching this week), but the agency case you describe — running checks across many client domains and selling the fixes — is exactly where the multi-organization plans point. If you run client domains, I'd genuinely love to hear what a "sellable" report would need to contain.
Happy to. You can reach me at support email on website — it runs on the product itself, so replies come back from that address. Drop me a line with a couple of times that work for you and I'll pick one.