The best Cloudflare Email Routing alternative when you need send-as is a delivery layer that owns MX and authenticated SMTP on the same operator. Routing can receive. It does not become a domain From because the calendar flipped. Keep Gmail or Outlook as the store. Cut to one MX set. Prove inbound. Pay for send-as. Do not run Cloudflare MX beside MailerZ MX.
Quick answer for cloudflare email routing alternative send as
Stay on Cloudflare Email Routing if inbound-only is still the job and you are happy in that DNS. Read their current limits in Cloudflare — Email Routing documentation. That documentation is the source for their product, not this page. Cloudflare routing does not become MailerZ leftover-MX handling, stored failed hops, or authenticated send-as because a comparison post mentioned it.
Move when replies must show the domain. MailerZ is a focused forwarding plus SMTP layer around the inbox you already use. Point MX at MailerZ. Recreate named aliases. Delete leftover routing hosts. Prove inbound from another mailbox. Then create a paid SMTP credential and attach Gmail Send mail as or a manual Outlook identity. Google’s client clicks live in Google Gmail Help — Send mail from a different address.
Free cannot finish send-as. 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/month or $990/year. Confirm numbers on MailerZ pricing. Limits are not an inbox-placement promise.
Transport follows IETF RFC 5321 — Simple Mail Transfer Protocol. MailerZ may rewrite only the envelope return path with Sender Rewriting Scheme. Header From, Subject, Date, Message-ID, body, and MIME are never rewritten. Unauthorized send gets SMTP 550. MailerZ is not an open relay, not IMAP, and not Workspace. Product surfaces live on MailerZ features.
Cutover is an MX swap, not an IMAP export. Use the migration planner if you want a rollback note before you delete routing records. The homepage job is still receive, reply, and send as your domain — MailerZ.
The user problem and the decision criteria
The usual trigger is a reply. Customers write to hello@yourdomain.com. Routing drops the copy in Gmail. The founder hits reply. Recipients see @gmail.com, or a via line, or a thread that looks broken. Someone then adds a random SMTP vendor next to Cloudflare MX. Two logs. No leftover-MX stop. That patchwork is why people search for a Cloudflare Email Routing alternative when they need send-as.
The opposite trigger is also valid. Routing still fits if you only need inbound, you live in Cloudflare DNS, and you will not print a domain From this quarter. Buying send-as you will not use is not an alternative. It is an unused credential.
A third trigger is evidence. A message vanished. Routing gave you less of a hop story than you wanted. MailerZ stores required content and metadata and records destination responses. That is not a reason to invent an uptime SLA. It is a reason to want history when you also want SMTP.
| Question | If yes | If no |
|---|---|---|
| Must recipients see the domain on replies? | You need authenticated SMTP. Routing inbound is not enough. | Stay on routing if inbound-only still fits. |
| Do you already trust Gmail or Outlook as the store? | A delivery layer can attach send-as. | You are shopping for hosting, not a routing alternative. |
| Can you publish one MX set and delete leftover routing MX? | Cutover is possible. | Do not start. Split MX loses mail. |
| Do you need leftover-MX diagnostics and stored failed hops? | MailerZ is in scope for that class of evidence. | Do not invent those features on routing. |
| Is sending personal or operational, not bulk? | Paid MailerZ SMTP is in scope. | Use a campaign platform either way. |
This alternative fits when the domain is an identity, the inbox already exists, and send-as is a real acceptance test. It fails when you need Cloudflare routing’s place in a DNS workflow you will not leave, when you need a hosted mailbox suite, or when you want a promise that Gmail will file mail in Primary.
Technical mail flow
Routing and MailerZ can share a domain name. They cannot share MX. A sending server looks up MX, offers MAIL FROM, names RCPT TO, and transfers content. IETF RFC 5321 — Simple Mail Transfer Protocol is the transport standard. SPF, DKIM, and DMARC authorize sending; they do not file a Gmail tab. See IETF RFC 7208 — Sender Policy Framework (SPF), IETF RFC 6376 — DomainKeys Identified Mail (DKIM), and IETF RFC 7489 — Domain-based Message Authentication, Reporting, and Conformance (DMARC).
What routing was doing
Cloudflare Email Routing accepts mail for addresses you configured and forwards into a destination mailbox. That is inbound routing. Their docs define current behavior and limits. This article does not replace those docs and does not claim their feature list. If you only needed that hop, you did not have a send-as problem yet.
What MailerZ does after the cut
MailerZ MX answers. The edge checks verification and the alias. The message is stored, then forwarded to Gmail or Outlook. Header From stays the original sender. The envelope may use SRS. Delivery history records the destination response. Unknown recipients are held on Free. Paid catch-all forward is optional.
The send-as hop routing did not finish
Paid MailerZ SMTP authenticates a client, checks the From, applies plan limits, and submits. Gmail Send mail as or Outlook manual SMTP attaches that credential. Incoming mail stays at the destination mailbox. Free has no send-as. Unauthorized or unhosted recipients get 550.
Recovery storage is 14 days on Free and 90 days on paid plans. That is hop evidence, not a second archive. Legal hold stays in Gmail or Outlook.
Step-by-step setup and decision path
Do this in order. Enabling SMTP while Cloudflare MX still answers is how verification mail vanishes.
Confirm send-as is the real job
If inbound-only still fits, stay on routing. If recipients must see the domain, continue.
Export the rule list
Write every local-part and destination you currently route. You will recreate them as named aliases. Catch-all on routing is not automatically catch-all on MailerZ. Free holds unknown. Paid catch-all forward is a watched policy.
Add and verify the domain on MailerZ
Root domain, not
https://. Publish the verification TXT. Do not cut MX until verify passes.Create the aliases
Map them to the same Gmail or Outlook destinations. Complete destination verification if asked. Free allows ten aliases. Solo allows twenty-five.
Publish MailerZ MX and delete leftover routing MX
One set. Query from two resolvers. Keep a rollback note in the migration planner until the external probe works.
Prove inbound from a different mailbox
Unique subject, unrelated provider, each alias. Confirm Header From and delivery history. Open spam and junk. Do not use Gmail self-send as the only test.
Upgrade only for send-as
Solo at $40 per year is the usual next step. Create the SMTP credential. Do not paste your Google password. Attach Gmail Send mail as or Outlook manual SMTP.
Send to a second external inbox
Check visible From, return hop, and outbound history. Far-side placement is still their filter.
| Record | Job | Failure if wrong |
|---|---|---|
| Verification TXT | Prove you control the zone | Receiving and sending stay disabled |
| MailerZ MX | Inbound after the cut | Mail stays on routing or bounces |
| Leftover routing MX removal | Stop split delivery | Some senders never reach MailerZ |
| SPF / DKIM / DMARC | Authorize paid send-as | Receivers treat outbound as unauthenticated |
Failure modes and proof
Most “the alternative is worse than routing” reports are leftover Cloudflare MX, Free asked to send-as, or a rule you forgot to recreate.
| What you see | Likely cause | Proof to collect |
|---|---|---|
| Some senders still hit routing | Leftover Cloudflare MX or cache. | Public MX from two resolvers. |
| A local-part that worked yesterday is gone | Alias not recreated. Free ceiling is ten. | Rule list versus alias list. Plan name. |
| Catch-all noise or missing typos | Unknown policy differs. Free holds. Paid forward is optional. | Held-mail view. Catch-all setting. |
| Cannot send as the domain | Still on Free, or SMTP not attached. | Plan name. From selector. Outbound history. |
| Google cannot verify Send mail as | Inbound not live or leftover MX stole the message. | Delivery history, Gmail Spam, public MX. |
| Self-send never appears | Gmail short-circuited. | Probe from another provider. |
| 550 on send | Unauthorized From or unhosted domain. | Exact SMTP response. Approved identities. |
| Two vendors, two stories | You added SMTP without cutting MX. | One MX set. One outbound credential. |
Proof is a sanitized destination screenshot or header block plus the MailerZ event. Do not send SMTP passwords to support. If you need DNS reads, use troubleshooting and DNS diagnostics. Those tools are DNS-only.
Do not treat Cloudflare’s inbound success last month as proof that send-as will work this month on a leftover hybrid. Cut MX. Then attach SMTP. The year on the calendar does not merge those hops.
MailerZ workflow and product boundary
MailerZ is a custom-domain email delivery layer operated by Secuno LLC. Point MX at MailerZ. Mail for a hosted, verified domain can land in Gmail or Outlook. Paid plans add authenticated SMTP. The live site is mailerz.net. The app is mail.mailerz.net.
What MailerZ does as a send-as alternative
- Accept inbound mail for verified domains and named aliases.
- Preserve Header From on the forward.
- Hold unknown recipients on Free; optional paid catch-all forward.
- Store messages 14 days on Free or 90 days on paid plans.
- Send through authenticated SMTP from approved identities on paid plans.
- Record delivery history for inbound and outbound hops.
- Surface leftover MX as diagnostics, not as a guaranteed health score.
What MailerZ does not do
- Replace Cloudflare Email Routing’s docs or live limits.
- Replace Gmail or Outlook with IMAP or webmail.
- Rewrite header From, Subject, Date, Message-ID, body, or MIME.
- Offer send-as on Free.
- Promise inbox placement, uptime SLAs, or review counts.
- Claim SOC 2, ISO 27001, or HIPAA. Controls live on Security and Trust Center.
- Act as an open relay. Unauthorized send gets 550 / 550 5.7.1.
- Send newsletters or purchased lists.
Free is one domain. Solo is five domains. Starter, Business, and Agency raise domain, alias, seat, and send ceilings. A dashboard seat is not a Cloudflare routing rule and not a mailbox.
Cost, alternatives, and trade-offs
Routing inbound is often $0 in Cloudflare’s current packaging — confirm on their site. MailerZ Free is $0 inbound proof with no send-as. Solo is $40 per year when the From must travel. Starter, Business, and Agency raise ceilings. Registrar and Gmail consumer stores are separate.
| Approach | You get | You give up |
|---|---|---|
| Cloudflare Email Routing only | Inbound routing in that DNS. | MailerZ history, leftover-MX stop, paid send-as on this product. |
| Routing + random SMTP | Possible From identity. | Two vendors, two logs, leftover MX risk. |
| MailerZ Free after cutover | Inbound you can prove. Three aliases. Unknown held. | No send-as. 14-day store. |
| MailerZ Solo or higher | Same layer for MX and paid SMTP. | You operate DNS. Published send limits. Not a suite. |
| Google Workspace | Hosted mailbox and suite. | Per-user cost. Different job than routing-plus-SMTP. |
ImprovMX is the closest commercial forwarding class; compare live plans. Two months free on annual Starter, Business, and Agency is arithmetic against monthly, not a coupon stacked on Solo. Campaign mail still does not belong on this identity.
Time is part of cost. An afternoon on leftover routing MX costs more than Solo for many founders. Finish the cut. Then create one SMTP credential. Two half-configured hops — routing MX plus a random SMTP vendor — is the expensive week you were trying to leave.
Shared role addresses do not need a second Cloudflare zone per name. Recreate hello@ and billing@ as named aliases. If the printed list is longer than ten, that is Solo or a shorter public list, not a reason to keep leftover routing MX “for the extras.”
Vacation responders stay on Gmail. A vacation responder on Free still leaves as the Gmail identity unless you also paid for send-as and told Gmail which From to use. Routing did not finish that hop. MailerZ Free does not finish it either. Pay when the auto-reply must say the domain.
Operator brief
A longer operator brief for cloudflare email routing alternative send as
Teams that bookmark Best Cloudflare Email Routing Alternative When You Need Send-As 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 cloudflare email routing alternative send as 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/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 cloudflare email routing alternative send as. 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 best cloudflare email routing alternative when you need send as. 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 cloudflare email routing alternative send as 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 cloudflare email routing alternative send as 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 Best Cloudflare Email Routing Alternative When You Need Send-As 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 cloudflare email routing alternative send as stays a runbook instead of an incident.
A second worked pass for cloudflare email routing alternative send as: 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 cloudflare email routing alternative send as 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. Ten 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@.
FAQ
What is the safest way to handle cloudflare email routing alternative send as?
List every current routing rule, add and verify the domain on MailerZ, recreate named aliases, publish one MailerZ MX set, delete leftover Cloudflare routing MX, and prove inbound from a different mailbox. Then add paid send-as. Do not run both MX sets.
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. Cloudflare Email Routing also did not host a mailbox. Send-as is an SMTP identity, not a new inbox.
Will it work with Gmail or Outlook?
Yes for inbound when the destination is a verified mailbox. Gmail uses Send mail as on a paid plan. Outlook uses a manual SMTP identity. Incoming mail stays at the destination mailbox. Interface labels vary by Outlook version.
What DNS records are involved?
A verification TXT, one MailerZ MX set, leftover Cloudflare or host MX removal, and the SPF, DKIM, and DMARC values shown in the dashboard if you also send as the domain. Routing MX beside MailerZ MX splits mail.
What should I test before production?
Send a uniquely titled message from an unrelated provider into each recreated alias. Confirm Header From and delivery history. Then send outward through paid SMTP to a second external inbox. Self-send from Gmail to the same Gmail account can hide routing errors.
Key takeaways
- A Cloudflare Email Routing alternative when you need send-as is MX plus paid SMTP, not routing with a second vendor taped on.
- Stay on routing if inbound-only still fits. Read their docs for their limits.
- Keep Gmail or Outlook as the store. MailerZ is not IMAP.
- Free proves inbound after the cut. Free has no send-as.
- Solo is $40 per year when the From must travel.
- One MX set. Leftover routing MX is a hard stop.
- Header From stays original on inbound. Envelope SRS is the allowed rewrite.
- Recreate every named alias. Do not assume catch-all policy matches.
- MailerZ is not SOC 2 and not a bulk sender.
Conclusion and next action
If you came here for the best Cloudflare Email Routing alternative when you need send-as, write the job first. Inbound-only can stay on routing. Domain From needs authenticated SMTP on one MX set you can prove. List the rules. Verify MailerZ. Cut leftover hosts. Probe from another mailbox. Pay Solo or another published plan only when the From identity has to travel.
MailerZ fits that split with delivery history and a recovery window you can see. It does not fit hosted mailboxes for every user, certified compliance reports, or campaign-scale sending. It does not replace Cloudflare’s own documentation. Start on Free after the cut if receiving is the first proof. Move to Solo when replies must show the domain.
Next action: copy your routing list, add one domain, recreate the aliases, and send a uniquely titled message from a mailbox that is not the destination. Use the migration planner if routing MX is still live. The register path is one domain, not a DNS religion.
Need send-as? Cut MX first
Start free with one domain and prove the hop.
Inbound on Free after a clean MX cut. Paid send-as when the From identity has to travel. Sign in if the domain is already there.
Review quarterly, or sooner if Cloudflare Email Routing, MailerZ send-as limits, or Gmail Send mail as changes. Author: MailerZ editorial, Secuno LLC.