Forwarding your own domain emails to inboxy

If you have your own domain, you can set up a forwarding rule to send emails from addresses like support@yourdomain.com straight into inboxy. Here's how.

The setup (one time)

1. Mint an inboxy address for this purpose.

   • Go to Account → Addresses → New address.
   • Give it a memorable label like "yourdomain-support" so you remember what it's for.
   • Copy the full address (e.g. quiet-otter-47@inboxy.net).

2. Add a forwarding rule to your domain's mail server.

   • Log into your registrar or DNS / mail provider (GoDaddy, Namecheap, Mailgun, PostMark, etc.).
   • Find the mail forwarding or alias settings (exact location varies by provider).
   • Create a forward rule:
     • From: support@yourdomain.com (or whatever address you want)
     • To: quiet-otter-47@inboxy.net
   • Save the rule. It typically takes a few minutes to activate.

3. Test it.

   • Send yourself a test email to support@yourdomain.com from another address.
   • Wait a minute and check your inboxy inbox — it should show up.

Common setups

Provider	Instructions
GoDaddy	Email settings → Forwarding. Enter the target inboxy address.
Namecheap	Mail Settings → Forwarding Address. Add your inboxy alias.
Google Workspace	User accounts → Edit user → User information → Forwarding. Point to inboxy.
Mailgun / PostMark	Create a route / forwarding rule pointing to the inboxy address.
Your own mail server (Postfix, Exim, etc.)	Edit your virtual alias table or .forward file. Add: support: quiet-otter-47@inboxy.net

Exact steps vary — if you're stuck on your provider's UI, their support docs usually cover it in 2-3 minutes.

Multiple addresses into inboxy

If you want to forward several addresses from your domain into the same inboxy address:

support@yourdomain.com    →  quiet-otter-47@inboxy.net
hello@yourdomain.com      →  quiet-otter-47@inboxy.net
contact@yourdomain.com    →  quiet-otter-47@inboxy.net

All three will land in inboxy under one address. The From: and Subject: fields stay the same, so you can tell who originally sent to what.

Or mint separate inboxy addresses and label them differently:

support@yourdomain.com    →  busy-squirrel-23@inboxy.net (label: "support")
hello@yourdomain.com      →  bright-owl-91@inboxy.net (label: "hello")

This way you can filter or label them independently. That's useful if you want to watch support@ closely and batch hello@ into the weekly digest. (Custom local-parts like support@yourdomain.com → business-support@inboxy.net are available on paid plans; the Early Adopter plan uses randomly-generated friendly names.)

Replying from your domain

Once email lands in inboxy from your domain address, you can reply directly via the web UI, MCP client, or API — but the From: will show the inboxy address, not your domain.

If you need to reply as support@yourdomain.com, you'll need to use your domain's own mail interface to send directly (not through inboxy). inboxy is great for receiving and organizing, but sending from your domain's address is separate.

(This is by design — inboxy's sending quota is per account, not per domain, so we can't safely let you send as arbitrary @yourdomain.com addresses.)

Benefits of this setup

• One inbox for everything. Business emails, newsletters, and personal mail all in one place.
• Privacy by default. Your domain emails get the same privacy-first treatment as disposable addresses — no tracking, no third-party access.
• Easy hand-off. If you want to stop using the domain or pass it to someone else, just change the forwarding rule.
• Spam containment. If support@yourdomain.com attracts spam, retire the inboxy address it forwards to — the domain address stays active, but the spam stops reaching you.

Stuck?

If the forwarding rule isn't working after 10 minutes, check:

1. The rule was saved. Some providers need you to click a "Save" or "Confirm" button after entering the rule.
2. No typos in the inboxy address. Copy and paste, don't type it by hand.
3. Your domain's mail service is active. If you're on a free tier, some forwarding features may not be included.

If it's still stuck, email support@inboxy.net with:

• Your domain name (don't worry, this is public)
• The inboxy address you're forwarding to
• Your mail provider's name

We can help troubleshoot from there.