How to reply from a custom domain email address in Gmail — without Google Workspace

The problem: receiving is solved, replying is not

Getting email at a custom domain into Gmail is straightforward. Services like Cloudflare Email Routing, ImprovMX, and similar tools handle inbound forwarding for free. You point your MX records, set a forwarding rule, and mail sent to support@yourdomain.com shows up in your Gmail inbox.

Replying is the problem. When you hit reply in Gmail, it defaults to your Gmail address — not your custom domain address. Your customer, who wrote to support@yourdomain.com, receives a reply from yourname@gmail.com.

That gap is what this guide addresses: how to actually reply from a custom domain address in Gmail, and what each approach costs as you add more addresses.

Option 1: Gmail's built-in Send As feature

Gmail has a built-in feature called Send As that lets you add custom sender addresses. Under Settings → Accounts → Send mail as, you can add an address like support@yourdomain.com and configure it to send through an SMTP server you control.

For the SMTP server, you have a few options: your domain registrar may include one with hosting, or you can use a transactional email provider like Brevo (formerly Sendinblue) or Mailjet, which have free tiers. Once configured, Gmail lets you choose which sender address to use when composing or replying.

This works. For one or two addresses and a single domain, it is often all you need.

• Free to set up with most domain registrars or free-tier SMTP providers
• You choose the sender address manually when composing or replying
• Requires a separate SMTP credential for each custom domain address
• Works in Gmail, but sender selection is manual — one dropdown, every time

Where Send As breaks down

The manual selection step is where Send As starts to feel fragile. When you reply to a message, Gmail does not automatically know which of your configured addresses the customer originally wrote to. You have to remember and pick it yourself.

With two addresses, that is manageable. With support@, billing@, sales@, and hello@ across two or three domains, it becomes a daily error risk. Replying from the wrong address to a customer — from support@ when they wrote to billing@, or from your Gmail address when they expect a domain reply — is an easy, professional-looking mistake.

Each address also needs its own SMTP setup. Adding a new customer-facing address means configuring another credential, another verification flow, and another entry in Gmail's settings.

Option 2: Google Workspace

Google Workspace solves the problem completely by giving each domain address its own full mailbox. You log in to that mailbox, compose and reply from it, and everything works as expected — because the address is a proper Gmail account.

The tradeoff is cost. Google Workspace starts at around $6 per user per month. If your 'user' is actually a role address like support@ or billing@, you are paying a per-person price for what is functionally a routing decision.

For larger teams with real people behind each address, Workspace is the obvious choice. For small teams or solo operators managing several customer-facing addresses, the per-seat model means paying separately for every visible identity even if the same person handles them all.

Option 3: A relay layer with automatic sender matching

A third approach sits between the two. Instead of configuring one SMTP credential per address (as in Send As) or buying a full mailbox per address (as in Workspace), a relay layer sits between your domain addresses and your Gmail inbox.

The inbound side works the same as basic forwarding: Cloudflare Email Routing receives mail at your domain addresses and forwards it to your Gmail inbox. The difference is in what happens to the routing context — specifically, which address the customer originally wrote to.

A relay layer preserves that context. When you reply via a single configured SMTP account, the relay reads the original recipient address from the conversation, and sends your reply back out from the correct domain address — automatically, without you selecting anything.

OhRelay works this way. You configure one SMTP account in Gmail once. After that, every reply goes out from whatever domain address received the original message. Support@ customers get replies from support@. Billing@ gets billing@. You never touch the sender dropdown.

• One SMTP credential configured in Gmail, regardless of how many addresses you manage
• Sender address is matched automatically based on which address received the email
• Adding a new domain address does not require another SMTP setup
• Sent copies land in your Gmail sent folder — mail stays in your own account

Which approach fits your situation

Gmail Send As is the right starting point if you have one domain and one or two addresses. The manual sender selection is a small inconvenience that is easy to live with at that scale.

Google Workspace makes sense when each address genuinely corresponds to a different person who needs their own inbox, search history, and mail management. The per-seat cost is justified by the per-person workload.

A relay approach like OhRelay fits when your address count is growing faster than your team. More domains, more role addresses, more client-facing identities — but still a small number of real people handling the work. In that shape, a routing layer that handles sender matching automatically removes a daily source of friction and error without requiring a mailbox purchase for each new address.

A note on Cloudflare Email Routing

Cloudflare Email Routing is the inbound side of this setup for most people who end up here. It is free, reliable, and works well for forwarding mail from custom domain addresses into Gmail. But it does not solve the reply problem — it only handles incoming mail.

If you are already using Cloudflare Email Routing and looking for how to reply correctly, the options above are the practical paths. Send As covers simple cases. A relay layer covers the multi-address case without adding per-address cost.