Email forwarding service: what to look for before you buy

Quick answer for email forwarding service

Before you buy an email forwarding service, ask whether they rewrite Header From, how they treat leftover MX, what happens to unknown recipients, how long they store hops they saw, and what unauthorized send returns. MailerZ: envelope SRS only, leftover MX is a hard stop, Free holds unknowns, 14-day or 90-day store, 550 / 550 5.7.1.

Guide: match the aisle. Setup: trial on a breakable domain with a real leftover cut. Best practice: no inbox-rate contracts.

Workspace is a suite. Proton is a mailbox. Privacy masks hide provider domains. Cite their docs. Do not invent parity.

Solo is $40 per year when send-as matters. Confirm live pricing.

MailerZ Free is one domain, ten 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 monthly or $990 yearly. 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.

email forwarding service guide: the real decision

Buyers shop unlimited aliases and skip hold policy.

They trial without cutting leftover Google and call the service broken.

They need Vault and buy a hop.

Criteria: hop shape, numeric ceilings, reject codes, legal pages that do not invent certifications.

Technical mail flow for email forwarding service

A service you buy still follows lookup, accept, map, resend. If they hide the MX hosts, you cannot run hop one.

If they hide 550, you cannot run send.

If they hide leftover guidance, you will debug ghosts.

If they claim SOC 2 and you cannot find the report, treat the claim as missing. MailerZ does not claim SOC 2.

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 or POP, 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.

email forwarding service setup

Trial the discipline, not the logo.

1. Write the printed names and the destination inbox.
2. Create the domain. Verify.
3. Add one alias. Do not catch-all.
4. Publish MX. Cut leftovers the same hour.
5. Probe from another mailbox.
6. Read history. Read a 550 if you try send on Free.
7. Only then move a production zone.
8. Compare suite or VPS if the aisle was wrong.

Failure modes and proof

Trial with leftover Google still live.

Bought unlimited catch-all.

Mailed SMTP password to support.

Needed Calendar, bought a hop.

Believed an inbox SLA.

MailerZ workflow and product boundary

MailerZ publishes plans on pricing. Features and delivery recovery show the hop. Routing lab practices lookups. Email forwarding is the product page.

Not IMAP or POP. Mail Box is portal webmail. Not an open relay.

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

email forwarding service best practice

Free is a real trial if you cut leftovers. Solo, Starter, Business, Agency are ceilings. Workspace seats are a different invoice. Confirm pricing.

Self-host cost is your time at 3 a.m.

MailerZ Free is one domain, ten 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 monthly or $990 yearly. Confirm numbers on MailerZ pricing. Limits are not an inbox-placement promise.

Field notes you can reuse

Disqualify Header-From rewrites early.

Print numeric ceilings.

Agency capacity is not a missing list.

Legal: security, privacy, terms, DPA, subprocessors. No invented badges.

Reddit self-hosted is research, not a vendor.

Do not compare inbox rates you cannot measure.

Quarterly leftover review after you buy.

The setup guide is the cutover. This page is the purchase.

Deeper field notes for email forwarding service

Buy a hop, not a vibe

An email forwarding service is an MX operator plus a map plus, if you pay, SMTP. Marketing will talk about unlimited aliases, military encryption, and inbox rates. Ask for the MX hosts, leftover-MX guidance, unknown-recipient policy, store window, send-as limits, and what 550 looks like. If those answers are missing, you are buying a vibe. MailerZ publishes them. Confirm live pricing. Free is one domain, ten aliases, no outgoing, no send-as. Paid plans raise ceilings. None of that is an inbox-placement contract.

Questions that disqualify a vendor in one call

Do they rewrite Header From on inbound? If yes, your authentication story gets noisier and Gmail via lines get more common. MailerZ does not rewrite Header From. Do they accept send from any IP after you add a domain? That is an open relay. MailerZ does not. Do they require you to host IMAP? Then they are a mailbox, and you should compare them to Workspace, not to a forwarder.

Do they show leftover MX as a hard stop? If they shrug, you will debug ghosts. Do they hold unknowns or dump catch-all into Primary by default? Dumping is how spam buttons train against your domain. Do they invent SOC 2 on the homepage? MailerZ does not claim SOC 2, ISO 27001, or HIPAA. Legal pages exist. Read those, not a badge that is not there.

What “unlimited” usually hides

Unlimited aliases without a hold policy is a harvest hose. Unlimited domains without per-zone MX discipline is an agency mess. Unlimited send without authentication is a relay. Ask for the numeric ceilings and the reject codes. MailerZ Agency is 100 domains, 500 aliases, 50 seats, 800 outgoing, 25 send-as per hour. Those numbers are enough for a lot of client work and still a list you can print.

Self-hosted versus bought

A Reddit self-hosted thread will tell you to run Postfix. That can work. You then own abuse, backups, TLS, and the 3 a.m. deferral. Buy a forwarding service when you want the operator to be someone else’s pager and you still want Gmail as the store. Do not buy a suite because a thread said forwarding is “hacky.” Forwarding is a normal MX design. Suites are a different aisle.

Price that matches the job

If you only receive three names, Free may be enough. If one From must travel, Solo at $40 per year is the usual step. If you were about to buy Workspace seats so a footer could print support@, compare that invoice to Solo or Starter. If you need Vault, do not cheap out on a forwarder. You need the suite. Honest mismatch saves a quarter.

Proof before you move production MX

Create the domain. Verify. Add one alias. If you can, use a staging name. Publish MX only when you can cut leftovers the same hour. Probe from another mailbox. Read delivery history. Then print the address. A trial that never cuts leftover Google is not a trial of the service. It is a trial of split brain.

Support artifacts worth paying for

A vendor that wants your SMTP password in the ticket is a vendor to leave. Send a timestamp, a Message-ID, and a 550 line. MailerZ’s troubleshooting pages tell you to collect those. Delivery recovery exists for hops this layer stored. That is the product shape to look for before you buy.

A complete worked story

Two quotes, one leftover

An agency compared a cheap registrar forwarder to MailerZ. The cheap one rewrote Header From and offered unlimited catch-all. They trialled MailerZ on a client sandbox, cut leftover Google, and probed. History showed the hop. They priced Agency against the hours they spent on registrar ghosts. They did not buy Workspace for those clients. They also did not buy the cheap rewrite. The buy question was leftover MX and Header From, not a logo.

Operator brief

A longer operator brief for email forwarding service

Teams that bookmark Email Forwarding Service: What to Look for Before You Buy 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 email forwarding service 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 Mail Box portal webmail, not IMAP, not POP, 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 monthly or $990 yearly. 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 email forwarding service. 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 email forwarding service what to look for before you buy. 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 email forwarding service 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 email forwarding service 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 Email Forwarding Service: What to Look for Before You Buy 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 email forwarding service stays a runbook instead of an incident.

A second worked pass for email forwarding service: 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 email forwarding service 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

A one-page RFP you can send any vendor

1. List the MX hosts I must publish and whether leftover hosts are a hard stop. 2. Do you rewrite Header From, Subject, Date, Message-ID, body, or MIME on inbound? 3. What is the default unknown-recipient policy and can I hold? 4. How long do you store hops you accepted? 5. What SMTP 550 text do I get for unauthorized send? 6. What are numeric ceilings for domains, aliases, seats, outgoing, and send-as per hour? 7. Which certifications do you actually hold — not “aligned with”? 8. Where do I read subprocessors? MailerZ answers: leftover MX is a hard stop; envelope SRS only; Free holds unknowns; 14-day Free / 90-day paid store; 550 / 550 5.7.1; ceilings on the pricing page; not SOC 2, not ISO 27001, not HIPAA; legal pages for the rest.

If a vendor cannot answer in writing, you are buying a landing page. If they answer with an inbox percentage, ask how they measured it and whether your domain is in the sample. They will change the subject. Keep the RFP.

Price the implementation, not just the plan. Leftover MX cleanup, alias inventory, and one external probe are the implementation. A service that hides those steps will cost you a weekend after you “bought.” MailerZ’s setup guide is those steps. Read it before you compare logos.

Procurement will ask for a DPA. Point at the published DPA if you use MailerZ. Do not invent a SOC letter to unblock a deal. Enterprise wording that outruns the legal pages is how you lose the next security review.

One more working distinction

Contract language that should stay boring

Prefer “we accept MX for verified domains and forward to destinations you name” over “we secure your communications.” Prefer published send-as hourly ceilings over “fair use.” Prefer a store window in days over “we keep logs.” MailerZ’s boring version is on pricing, features, security, and the legal pages. An email forwarding service that cannot be boring in a contract will get creative in an incident.

Write the store window as 14 days on Free, 90 days on Solo through Agency, and 180 days on Unlimited. Write outgoing as disabled on Free and 2,500 / 5,000 / 12,000 / 20,000 / 100,000 on paid plans. Write aliases as 10 / 25 / 50 / 200 / 500 / uncapped. Confirm MailerZ pricing the day the RFP goes out. A vendor who will not put those numbers next to leftover-MX and Header From policy is still selling a landing page. Ask for the leftover-MX sentence in writing before you compare logos.

A short operating rule

A note on comparing list prices

Compare yearly Solo at $40 to one leftover Workspace seat, not to an ESP’s starter tier. An email forwarding service is not bulk mail. If the quote includes dedicated IPs and list hygiene, you are in the wrong aisle again. Confirm MailerZ numbers on the live pricing page before you paste them into a procurement sheet.

FAQ

What is the safest way to handle email forwarding service?

Buy an operator that publishes MX hosts, leftover-MX guidance, unknown hold, a store window, and 550 on unauthorized send. Do not buy inbox-rate promises. Trial with a real leftover cut and an external probe.

Does this require a new mailbox?

No. MailerZ is Mail Box portal webmail (Inbox, Sent, New email). It is not IMAP or POP. 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

• Buy a hop.
• Ask leftovers.
• Ask hold.
• Ask 550.
• No Header rewrite.
• No inbox SLA.
• Trial with a real cut.
• Wrong aisle is expensive.

Conclusion and next action

Look for leftover-MX discipline, named maps, hold, a store, and honest send limits. MailerZ is built that way. Start free on a domain you can break.

Sign in if you already bought a panel that still rewrites From.

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