Compare the full loop
Do not evaluate forwarding with inbound tests alone. Reply from the alias and inspect the recipient-visible From address.
Forwarding plus a reply path—or forwarding alone?
A practical comparison for teams deciding whether inbound routing is enough or authenticated send-as and recovery matter.
Plain-English verdict
Cloudflare is compelling for basic inbound routing inside its DNS ecosystem. MailerZ is designed for a fuller alias workflow: receive, send as, inspect and recover.
Choose MailerZ when you need
Authenticated SMTP from your alias
Delivery history and a retry-oriented workflow
Explicit unknown-recipient handling
A product focused on custom-domain email operations
CapabilityMailerZCloudflare Email Routing
Custom-domain receivingAlias forwarding to existing inboxesInbound routing to verified destinations
Outbound identityAuthenticated SMTP send-asNo general-purpose outbound SMTP
Unknown recipientsHold or forward, by planRouting-rule behavior
Message recoveryDelivery history and retry workflowActivity visibility; feature set differs
Mailbox storageNo hosted inbox; destination stores mailNo hosted mailbox
Tradeoffs to understand
No platform is the right fit for everyone.
MailerZ does not host an IMAP mailbox; forwarded mail lives at your destination provider.
Cloudflare Email Routing may be simpler if you already use Cloudflare and only need inbound forwarding.
Both products depend on correct DNS and downstream inbox behavior.
Check current terms
Features, limits and pricing change. Confirm Cloudflare’s current documentation before a production decision.
Check current vendor docs
Confirm Cloudflare Email Routing on its own site.
Plans and limits change. Recheck the first-party page before a purchase or MX cutover.
Test before migrating
Start free Prove one address before changing every MX record.
Use a low-risk domain or planned cutover window, verify both directions, then expand.