What is email forwarding? A technical guide for custom domains

Quick answer for what is email forwarding

Email forwarding is a second SMTP transaction after your MX accepts the first. Create a named alias, publish one MailerZ MX set, delete leftover hosts, and probe from another mailbox. That is what is email forwarding in production.

Best practice: hold unknowns, do not rewrite Header From, do not self-send, do not promise inbox placement.

Setup is verify, map, cut leftover MX, probe. Send-as is a different hop.

Self-hosted Postfix is the same idea with your pager. A suite is a different idea.

MailerZ Free is one domain, three aliases, one seat, a 14-day store, send-as disabled, SMTP and API disabled, and unrouted mail held or rejected only. Solo is $40 per year only. Starter is $8 monthly or $80 yearly. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm numbers on MailerZ pricing. Limits are not an inbox-placement promise.

Google’s own Send mail as steps live in Google Gmail Help — Send mail from a different address. Workspace as a product is described on Google Workspace — product overview. Transport still follows IETF RFC 5321 — Simple Mail Transfer Protocol.

what is email forwarding guide: the real decision

Registrar UIs call Header-From rewrites “forwarding.” That product breaks authentication stories.

Gmail’s auto-forward between Gmail accounts is not custom-domain forwarding.

Buyers want a mailbox and buy a hop, or want a hop and buy a suite.

Criteria: second SMTP, intact Header From, named map, leftover MX gone.

Technical mail flow for what is email forwarding

Lookup, accept, map, second session, destination classify. RFC 5321 envelope, RFC 5322 header.

SRS on the envelope is normal. Header rewrite is a different product.

If leftover MX accepts first, this flow is a diagram, not a log.

Reply is not forwarding.

MailerZ is inbound MX plus authenticated SMTP from Secuno LLC. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME are never rewritten. Not Google Workspace, not IMAP, not webmail, not an open relay. Unauthorized send is SMTP 550 / 550 5.7.1. Leftover MX is a hard stop. Self-send from Gmail to the same Gmail account can hide routing errors. Not SOC 2, not ISO 27001, not HIPAA.

what is email forwarding setup

Define the hop, then publish it.

1. Name the destination mailbox.
2. Verify the domain.
3. Create printed aliases.
4. Publish one MX set. Delete leftovers.
5. Probe from another provider.
6. Leave catch-all off.
7. Add send-as only if a From must travel.
8. Read features and delivery recovery so you know what logs exist.

Failure modes and proof

Registrar rewrite called forwarding.

Gmail filter called forwarding.

Leftover MX.

Catch-all hose.

Inbox-rate promise.

MailerZ workflow and product boundary

MailerZ is inbound MX plus optional SMTP. Envelope SRS only. Related: email forwarding, features, delivery recovery, email routing lab.

Not SOC 2, not ISO, not HIPAA. Store windows are recovery.

Related pages: email forwarding, features, delivery recovery, and email routing lab.

what is email forwarding best practice

Free explains the word on one domain. Paid explains send. A VPS explains the pager. A suite explains Calendar. Confirm pricing.

Wrong aisle costs more than Agency.

MailerZ Free is one domain, three aliases, one seat, a 14-day store, send-as disabled, SMTP and API disabled, and unrouted mail held or rejected only. Solo is $40 per year only. Starter is $8 monthly or $80 yearly. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm numbers on MailerZ pricing. Limits are not an inbox-placement promise.

Field notes you can reuse

Cite RFC 5321 when someone says forwarding is fake email.

Hold unknowns.

Do not fan-out catch-all.

Agencies: per-zone hops.

Measure reliability without fake uptime claims.

Collect Message-ID before support.

Quarterly MX review.

This guide is the definition. The setup guide is the cutover.

Deeper field notes for what is email forwarding

A definition you can defend

Email forwarding for a custom domain is this: a message is addressed to a recipient on your domain; an MX host you control accepts it; that host sends a new SMTP transaction to a destination mailbox you already have. The destination is usually Gmail or Outlook. The original Header From should survive. The envelope sender may be rewritten with SRS so the second hop’s SPF story is honest. That is what is email forwarding when the words are not marketing.

It is not IMAP. It is not a mailbox. It is not a privacy mask on someone else’s domain. It is not Google Workspace. It is not an open relay. A forwarder that accepts mail for domains it does not verify is a relay. MailerZ verifies the domain and rejects unauthorized send with 550 / 550 5.7.1.

Forward versus alias versus redirect versus catch-all

People use these words as synonyms. They are not. An alias is a named local-part you created. Forwarding is the hop that alias uses. A redirect in some registrar UIs rewrites Header From and breaks authentication stories. Catch-all is a policy for local-parts you did not name. MailerZ does not rewrite Header From. If a cheap host rewrote it, your “forwarding” is a different product.

Auto-forward inside Gmail from one Gmail to another is also not custom-domain forwarding. That path never published your MX. It is a Gmail filter. Useful, unrelated.

Why the envelope and the header disagree

RFC 5321 is the envelope. RFC 5322 is the header. Forwarding must change the envelope to a mailbox the next hop will accept. It should not need to change the header the human reads. SRS is the usual envelope rewrite. Teams that rewrite Header From to “prove” the hop create the via line and the spam button. MailerZ’s boundary is envelope SRS only.

If you need the original envelope preserved for a legal reason, you are asking for a journal or a BCC archive, not forwarding. Buy that product. Do not stretch SRS into legal hold.

Where forwarding fails in practice

Leftover MX. Self-send tests. Catch-all into a spam-trained inbox. A destination that rejects the second hop. A rewrite of Header From by a registrar toy. A TTL that still serves the old host in one city. None of those are “Gmail hates forwarding.” They are hop errors. Delivery history on the destination and a public MX lookup are the first two artifacts.

Delayed or missing mail after a nameserver move is usually split brain: some resolvers see MailerZ, some still see Google. Wait, or lower TTL before the cut. Do not add a second MX “for backup” unless you understand that the better-preference leftover will steal production.

What a forwarding service must show you

The MX hosts to publish. The leftover warning. Named alias list. Hold versus forward versus reject for unknowns. A store window for hops it saw. SMTP credentials if you pay to send. A 550 you can read. MailerZ publishes those. Inbox-placement percentages are not on that list. A forwarding service cannot promise 100 percent inbox placement.

Self-hosted threads often argue Postfix on a VPS. That is a different job: you become the MX operator. Fine if you want the pager. MailerZ is the operator when you do not.

A complete worked story

A registrar that rewrote From

A shop enabled “email forwarding” in a registrar panel. Customers arrived. Header From became the shop’s own domain. Gmail showed via. Replies went to a noreply they did not monitor. They moved MX to MailerZ, created hello@, and probed. Header From was the customer again. Same word, different product. The technical guide exists so that shop can ask “do you rewrite Header From?” before they buy the next panel.

Operator brief

A longer operator brief for what is email forwarding

Teams that bookmark What Is Email Forwarding? A Technical Guide for Custom Domains usually arrive after a missed invoice, a form that never notified anyone, or a migration that looked clean in one resolver. The useful brief is still boring. Name the store. Name the printed local-parts. Name the nameservers that actually answer. Publish one MailerZ MX set. Delete leftover hosts. Probe from a mailbox that is not the destination. Only then talk about what is email forwarding as a send-as, catch-all, or comparison problem.

MailerZ remains inbound MX plus authenticated SMTP around Gmail or Outlook. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME stay intact. It is not a hosted mailbox, not IMAP, not webmail, and not an open relay. Unauthorized send is 550 / 550 5.7.1. Free cannot finish send-as: SMTP and API stay off. Solo is $40 per year when the domain From must travel. Starter is $8 or $80. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm the live pricing page. Those numbers are ceilings, not an inbox-placement service-level agreement.

If leftover Google, Microsoft, Cloudflare routing, or registrar MX is still public, stop widening what is email forwarding. The map you built never saw that copy. Priority numbers are an order, not load balancing. A higher preference host is idle while a leftover host still accepts mail. Save the old MX set before you delete anything. Check more than one public view because TTL lies.

Catch-all forward is not a safety feature for what is email forwarding a technical guide for custom domains. Hold unknowns on everyday production. Review the store. Promote a leftover only when a real person used it. Paid forward belongs to a dated cutover. Fan-out of unknowns into two inboxes trains two spam buttons. Plus addressing on Gmail is not a custom-domain unknown policy. MailerZ will not strip plus tags on your domain the way Gmail does on @gmail.com.

Send-as is a second hop. Creating an inbound alias does not approve outbound. Catch-all does not mint a From. Copy the dashboard host, port, and TLS pair together. Set From to an identity you created. Do not paste a Gmail password into a CMS, a cron file, or a ticket. Do not mail SMTP secrets to support. Send a 550 line, a timestamp, and a Message-ID. Rotate if a secret already leaked.

Self-send from Gmail to the same Gmail account can short-circuit. That green result is why people swear what is email forwarding works while customers vanish. Use a second provider. Put a unique subject on the probe so delivery history is searchable. If Header From was rewritten by some other forwarder, authentication stories get noisier. MailerZ does not rewrite Header From on inbound.

Agencies should keep what is email forwarding per client zone. Separate SMTP credentials. Do not pour every client into one catch-all because the spreadsheet got long. Agency plan capacity exists so you can hold more domains and aliases. It does not replace a named list. Offboard means delete MX you own, revoke SMTP, and stop forwarding leftovers into the agency inbox.

Legal and security questions have published answers on the security, privacy, terms, DPA, and subprocessors pages. MailerZ is not SOC 2, not ISO 27001, and not HIPAA. The 14-day Free store, the 90-day Solo–Agency store, and the 180-day Unlimited store are recovery windows for hops this layer saw. They are not an archive and not legal hold. If counsel wants eDiscovery, buy eDiscovery.

Comparisons only help after the hop is honest. Cloudflare Email Routing is inbound routing. A privacy-mask product hides a destination on a provider domain. A suite hosts mailboxes, Calendar, and admin. Proton-class mailboxes encrypt a store. MailerZ is the delivery layer when you already have Gmail or Outlook and you need a domain route you can prove. Cite the other product’s documentation. Do not invent feature parity.

When What Is Email Forwarding? A Technical Guide for Custom Domains is closed, the next physical action is a lookup and a probe, not another tab. Start free on one domain you can break. Sign in if the zone already lives here. Review quarterly, or sooner after a nameserver move, a plugin swap, or a staff departure. That is how what is email forwarding stays a runbook instead of an incident.

A second worked pass for what is email forwarding: write the last change on a sticky note before you open the dashboard. Nameserver move, leftover MX, new form plugin, contractor laptop, or a registrar forwarding toggle are the usual five. MailerZ history only shows hops that reached this layer. If the sticky note says leftover MX, you do not have a what is email forwarding mystery. You have a split. Delete the leftover. Wait for TTL. Probe again.

A third worked pass: print the public list. If you cannot print it, you are not ready for production unknowns and you are not ready for a bigger alias ceiling. Unlimited aliases as marketing will not save a missing list. Three named aliases on Free are enough to stop printing a personal Gmail on a homepage. Grow the list when a real person used a leftover, not when a harvest guessed admin@.

More working detail

Why people keep calling forwarding “not real email”

Suite vendors and some self-hosters treat a hop without IMAP as fake. RFC 5321 does not require the accepting MX to store the message forever. It requires a responsible next hop or a bounce. Forwarding is a responsible next hop. The store is Gmail. The identity the public writes is still your domain. That is real enough for invoices, forms, and support — which is what most small teams meant by email.

The critique is fair when someone promised a hosted archive, legal hold, or shared admin search and delivered a hop. That is a sales lie, not a protocol failure. MailerZ does not promise those. The 14-day and 90-day windows are hops this layer saw. If you need Vault, buy Vault.

Another critique: forwarding can fail SPF at the destination if the envelope is not rewritten and the original sender’s SPF does not include the forwarder — which it never will. SRS exists so the envelope matches the hop that actually talks to Gmail. That is why envelope rewrite is normal and header rewrite is not. Teams that skip SRS and then blame “forwarding” are blaming the missing envelope fix.

A third critique: each extra hop is a chance to defer. True. So is every suite. Measure with unique probes and history, not with a status page you invented. MailerZ will not publish a fake uptime badge to win this argument.

Read the features page for what the hop includes. Read delivery recovery for what the store is. Read the routing lab to see MX the way a sender sees it. Those three pages are the rest of the definition in product form.

One more working distinction

Forwarding versus BCC archive versus journal

Some compliance teams ask a forwarder to keep a perfect second copy of every conversation in both directions. That is journaling or a BCC archive on the mailbox product. Inbound forwarding copies messages that were addressed to your domain. It does not automatically copy replies that leave Gmail as a personal address. If you need both directions in a store you control, you are back in suite or archive territory. Say that in the first meeting. What is email forwarding stays a receive hop — and optional thin send — not a journal.

Marketing automation that “forwards” leads into a CRM is also not this hop. That is an API or a mailbox parse. If the CRM must see hello@ mail, either give it the Gmail or give it a second destination on the alias. Two destinations are a copy. Name who owns the CRM copy so humans do not double-reply.

When a developer says the app “just forwards,” ask whether it accepted MX. If the app only called an API after a webhook, you are not in this guide. You are in SMTP-for-forms or inbound parse. Different aisle, different 550.

FAQ

What is the safest way to handle what is email forwarding?

It is a second SMTP transaction after your MX accepts mail for a named alias. Header From should stay intact. Envelope SRS is normal. It is not a mailbox. Prove it with a public MX lookup and a probe from another mailbox.

Does this require a new mailbox?

No. MailerZ is not IMAP and not webmail. Gmail or Outlook remains the store unless you separately buy a hosted mailbox product.

Will it work with Gmail or Outlook?

Yes for inbound when the destination is a verified mailbox. Branded replies need paid send-as plus Gmail Send mail as or a manual Outlook SMTP identity. Free has no send-as.

What DNS records are involved?

A verification TXT, one MailerZ MX set on the authoritative nameservers, leftover host MX removed, and SPF, DKIM, and DMARC if you also send as the domain.

What should I test before production?

Send a uniquely titled message from an unrelated provider into each named alias. Confirm Header From and delivery history. Do not email yourself from the same Gmail account.

Key takeaways

• Second SMTP hop.
• Header From stays.
• Envelope may SRS.
• Not IMAP.
• Named aliases.
• Hold unknowns.
• No leftover MX.
• No inbox SLA.

Conclusion and next action

Email forwarding is an MX accept plus a second SMTP send to a mailbox you already have. MailerZ is that hop for custom domains around Gmail or Outlook.

Start free. Sign in if you already pay for a hop that still rewrites Header From.

Review quarterly, or sooner if Gmail, Workspace, or MailerZ scope changes. Author: MailerZ editorial, Secuno LLC.