All Your InboxesStart free

Replying to customers from your own address

You write a reply to the notification; the customer receives it from info@yourdomain.com — allyourinboxes appears nowhere. This page explains how replying works, whose replies are accepted, and what the “reply wasn't sent” warnings mean.

1 · The shortest path: Reply to the notification

  1. Open the notification you received and press Reply in your mail app — Gmail, Outlook, your phone, doesn't matter.
  2. Write your answer and send it. The system picks it up and delivers it to the customer FROM THE INBOX'S OWN ADDRESS.
  3. The customer sees a normal email thread: their mail plus your answer from your address. No trace of the system in between.

2 · From the panel: New email

  1. Starting a fresh email rather than replying? Open the inbox in the panel and press New email.
  2. Enter the recipient, subject, and message → send. The mail again goes out from the inbox's own address.
  3. You can even start a new email from inside Gmail without opening the panel — using the s.xxx address: /docs/send-from-gmail.

Whose replies are accepted? (Security)

  1. The system only accepts replies coming FROM YOUR NOTIFICATION ADDRESS — your sign-up email (changeable in Settings).
  2. The reply must also pass SPF/DKIM authentication; if you send from a normal provider like Gmail or Outlook, that happens by itself.
  3. These two checks stop anyone who merely knows your address from emailing your customers in your name.
  4. Every mail's received/notified/replied/rejected trail, with reasons, is on the Activity page.

What does the “reply wasn't sent” warning mean?

  1. If your reply can't be delivered for any reason, it doesn't vanish silently — a “wasn't sent” warning lands at your notification address and tells you why.
  2. Most common cause: you replied from a different account than your notification address. Resend from the right one.
  3. Second most common: SPF/DKIM authentication failed — usually seen with custom setups sending from their own server. Moving your notification address to a provider like Gmail/Outlook ends the problem.
  4. If you got the warning, the customer received nothing; fix the cause and send again.

Where people get stuck

I replied, but the customer sees some “allyourinboxes” address

The inbox's sending side isn't connected yet. Cloudflare inboxes come with sending ready; for IMAP inboxes connect SMTP on the Advanced screen (/docs/connect-hosting-imap), and for Outlook use Connect Microsoft (/docs/outlook-forwarding).

I'm not sure whether my reply went out

The rule is simple: no warning means it went out. If you want to see it anyway, the Activity page shows every mail's trail — your reply appears as a “replied” entry.

I want a teammate to be able to reply too

Replies are only accepted from the account's notification address. For team use, point the notification address at a shared mailbox (e.g. the team's Gmail) — you change it in Settings with a 6-digit code, and the code is sent to the NEW address.

One step further for busy inboxes: AI auto-reply (Pro) answers real incoming mail using your instructions — /docs/ai-auto-reply. Plans: /pricing

All your email. One place.

Connect any inbox. Send from the right address automatically. Free plan forever, paid from $6.99/mo, and it never touches how your mailboxes are set up.

Try it free