Help

Each inbox you connect has two independent levels. Level 1 — seeing mail: you forward the mailbox to a private address we give you (looks like f+abc123@allyourinboxes.com). Every message shows up in the app and as a notification at your personal address. No password involved.

Level 2 — replying (optional): you turn on replying for that inbox, and answers you write — by replying to a notification or in the app — go out from the inbox’s own address. The person who wrote to you sees your domain, not ours.

Each level can fail independently, which is why the fixes below are grouped by symptom.

The f+… address is unique per inbox. If you connect two mailboxes, each gets its own — forwarding both to the same one delivers all mail to the wrong project (or nowhere).

Find each inbox’s address on the Inboxes page, under “Forward mail to”. Always copy it from there.

Work through these in order — each one has happened in the wild:

1. Is the forwarding rule actually saved? Check your mail provider’s settings for a rule pointing at your f+… address — the exact one from the Inboxes page, since every inbox has its own.
2. Did your provider ask you to confirm the address? Gmail and others email a confirmation code to the forwarding target — that target is us, so we catch the code and show it on the Inboxes page (and email it to you). Paste it back where the provider asks. Gmail also needs the “Forward a copy” option selected after verifying — that second step is the one everyone misses.
3. Can the domain receive mail at all? If the domain’s DNS was moved (say, to Vercel or Cloudflare when a website was set up) the mail (MX) records may have been left behind — mail then goes nowhere, silently. Adding the inbox again will tell you if MX records are missing, who manages your DNS, and exactly which records to add.
4. Still nothing? Log in to the mailbox’s webmail and check whether your test email even arrived there (look in spam too). If it never arrived, the problem is upstream of forwarding — usually DNS.

Common in the first days: our notification domain is doing everything right technically (SPF, DKIM and DMARC all pass), but mailbox providers also score on history, and history only accumulates.

• Open the notification and mark it Not spam — your own mailbox learns instantly.
• Add notifications@allyourinboxes.com to your contacts — the strongest signal there is.
• Replying to notifications (which is the whole point) builds reputation fastest.

The most deceptive failure we’ve seen: the reply leaves your mail server successfully, then Gmail or Outlook refuses it at the door — not even into spam — because the sending domain has no SPF record. Mailbox providers now require SPF or DKIM on the sending domain, full stop.

Fix: add your mail host’s SPF value as a TXT record wherever the domain’s DNS is managed. Your host publishes it (welcome email, panel, or search their name + “SPF record”). We check for this when you enable replying and warn you if it’s missing.

Also check the reply went where you expect: a reply goes to whoever wrote the original message — if you emailed yourself a test from another account, the reply lands in that account.

MX records are your domain’s public signpost saying “deliver my mail here”. Two facts prevent most confusion:

• They live wherever your domain’s nameservers point — which may not be where you bought the domain, and not where your mailbox is. If your site runs on Vercel or Cloudflare, DNS (and therefore MX) is probably managed there.
• The values come from whoever hosts the mailbox — they’re fixed and published. When we detect missing MX we show a picker with the exact values for the major providers, ready to copy.

Watch for typos: a single missing letter in an MX value (it has happened) breaks delivery. DNS changes can take up to an hour to take effect.

On Google or Microsoft mailboxes, use the one-click connect button — no password, and you can revoke it in your account at any time. We ask only for permission to send; we never request access to read your mail.

Everywhere else, we detect the mailbox’s server from the address automatically, so the only thing you type is the mailbox password. Gmail and Outlook over password require an app password, not your account password — the form warns you when that applies.

• We only ever get a copy of forwarded mail — your mailboxes keep everything and keep working if you leave.
• Replies are only accepted from your own notification address; no one else can send from your domain through us.
• Passwords are encrypted (AES-256-GCM) and never shown again anywhere.
• We never touch your DNS, MX or mailbox settings unless you connect Cloudflare and ask us to.

Email support@allyourinboxes.com with your domain name and what you tried — it comes straight to a human, and DNS puzzles are our bread and butter.