Why Forwarding Beats a Full Mailbox for Most People

You bought a domain. You want professional email β€” [email protected] instead of [email protected]. The instinctive next step is to buy a Google Workspace or Microsoft 365 mailbox at $6–12 per user per month. For most freelancers, side projects, and pre-launch businesses, that is overkill.

Email forwarding gives you the professional address without a separate mailbox. Mail to [email protected] arrives in your existing personal Gmail. You reply through Gmail, and Gmail can be configured to send the reply as the custom address.

Total cost: $0–$1/month, depending on the forwarding provider. Total setup time: 15–30 minutes if your DNS is already accessible.

The Two Halves of Forwarding

Email forwarding has two directions, and they need to be configured separately:

  1. Inbound: Mail sent to [email protected] arrives at your personal inbox. This is what people usually mean by "forwarding."
  2. Outbound (Send-As): When you reply, the recipient sees [email protected] in the From line, not your personal Gmail address.

Most guides cover only the first half. Forgetting the second half is what makes forwarding feel half-broken β€” your replies have a personal address even though incoming mail looks professional.

Step 1: Pick a Forwarding Provider

Common options in 2026:

  • Cloudflare Email Routing: Free if your domain is on Cloudflare DNS. Solid, no nonsense. Best default option.
  • ImprovMX: Free tier covers up to 25 aliases. Reliable.
  • Forward Email: Open-source-friendly. Free tier with reasonable limits.
  • Your registrar's built-in forwarding: Some registrars include basic forwarding free. Quality varies.

For most users, Cloudflare Email Routing is the cleanest choice if your DNS is already there. Set up takes about 5 minutes.

Step 2: Configure the MX Records

To receive email at your domain, your domain's DNS must have MX records pointing to your forwarder's mail servers. Each provider gives you the specific values to use. The general pattern:

  • MX record, host: @ (or your domain name)
  • Priority: typically 10 (or as the provider specifies)
  • Value: the provider's mail server hostname

Most forwarders require 2–3 MX records for redundancy. Add all of them.

Important: you can only have ONE set of MX records on a domain. If you previously set up MX for Google Workspace or another mail provider and now switch to a forwarder, remove the old MX records β€” overlapping configurations cause unpredictable delivery.

Step 3: Configure the SPF Record

SPF (Sender Policy Framework) is a TXT record that tells receiving mail servers which servers are authorized to send mail "from" your domain. Without a proper SPF record, forwarded mail is more likely to be marked as spam.

Add a TXT record like:

  • Host: @
  • Value: v=spf1 include:<your-provider> ~all

The exact "include" value depends on your forwarder β€” providers publish the correct string in their setup docs. ~all means "soft fail" (suspicious mail accepted but flagged). Use that until you are confident, then graduate to -all ("hard fail").

Step 4: Configure DKIM (If Your Forwarder Supports It)

DKIM (DomainKeys Identified Mail) is a cryptographic signature on outgoing mail that proves the mail was authorized by your domain. Most modern forwarders generate DKIM keys for you β€” you copy the provided TXT record into your DNS.

The pattern:

  • Host: <selector>._domainkey (selector is provider-specified, typically cf2024-1 or improvmx)
  • Value: v=DKIM1; k=rsa; p=<long public key>

DKIM is optional in some forwarder setups but strongly recommended. Without it, outbound replies may be marked as spam by Gmail and Outlook.

DMARC ties SPF and DKIM together and tells receivers what to do when mail fails authentication. A starter DMARC record:

p=none means "monitor only, do not block." This is the safe starting point. After a few weeks of clean reports, you can ramp to p=quarantine and eventually p=reject for full protection against domain spoofing.

Step 6: Set Up Send-As in Gmail

Now incoming mail works. Time to fix the reply direction.

  1. In Gmail, go to Settings β†’ Accounts and Import β†’ Send mail as.
  2. Click "Add another email address."
  3. Enter [email protected] and your name.
  4. Gmail asks for SMTP credentials. You need an SMTP relay that can send "as" your domain. Options: your forwarder's SMTP relay (some include it), an SMTP service like SendGrid or Postmark (free tiers available), or Google Workspace itself (defeats the cost-saving purpose).
  5. Enter the SMTP server, port, username, password from your relay provider.
  6. Gmail sends a verification code to the new address β€” which arrives via your forwarding setup. Enter the code.

From now on, when composing in Gmail, you can choose [email protected] in the From dropdown. Replies to forwarded mail automatically use the custom address.

Common Setup Mistakes

  • Using both Google Workspace MX and forwarding MX records. Mail will go to the lower-priority server randomly. Pick one.
  • Forgetting to verify the Send-As address. Without verification, Gmail will not let you send from it.
  • Skipping SPF. Mail technically works but lands in spam. Add SPF before users start emailing you.
  • Adding multiple SPF records. RFC says only one. If you have multiple senders (forwarder + transactional service), combine them into one SPF record with multiple include: directives.

The Verification Checklist

Before relying on the setup:

  1. Send a test email from an external address (a friend's Gmail) to [email protected]. Verify it arrives.
  2. Reply from your Gmail using Send-As. Verify the recipient sees the custom address as the sender.
  3. Check that the reply did not land in spam β€” if it did, your SPF/DKIM setup needs adjustment.
  4. Use a tool like mail-tester.com to score the deliverability of an outbound message. Aim for 8/10 or higher.

When to Graduate to a Real Mailbox

  • You are sending more than 50 emails/day from the custom address β€” forwarding is meant for low-volume use.
  • You need calendar, contacts, or shared inbox features.
  • You are hiring and need separate mailboxes for team members.
  • Compliance or legal requirements demand audit trails on a controlled mail server.

Otherwise, forwarding is a perfectly professional setup that quietly serves millions of small businesses, freelancers, and side projects.