MailerZ vs ForwardMX: features, sending and recovery compared

Quick answer for mailerz vs forwardmx

Features: MailerZ is receive, reply, send-as on paid plans, stored hops, DNS diagnostics. It is not IMAP or POP, not an open relay. ForwardMX’s feature list is theirs — including optional mailboxes as a separate offer on their current wording. Do not treat optional mailboxes as MailerZ. We do not host the store.

Sending: MailerZ paid plans include authenticated SMTP within monthly and hourly caps (disabled/2,500/5,000/12,000/20,000 outgoing; 20/40/60/60 per hour). Free cannot send. Unauthorized From is 550. ForwardMX lists SMTP on current pricing — quote the page for counts and terms. Neither should be your campaign platform.

Recovery: MailerZ stores delivery history and failed hops for 14 days on Free and 90 on paid. That is hop evidence, not an archive and not an inbox-placement SLA. Verify ForwardMX logging and retention on their site. Do not invent matching windows.

Price shape: MailerZ Free for proof; Solo $40/year; then monthly or annual Starter, Business, Agency. ForwardMX Personal has been listed around $30/year for one domain with a large forwarder count — re-read https://forwardmx.net/pricing/. Taxes and definitions differ. Alias counting rules differ.

Fan-out: ForwardMX currently describes multiple recipients per alias (their overview has said up to 20). MailerZ routes to destinations you configure. Fan-out multiplies privacy exposure and downstream filters. Do not assume more recipients means better operations.

Transport is still ForwardMX — product documentation. MailerZ vs ForwardMX. MailerZ features. MailerZ pricing.

The real decision

Buyers see “100 aliases” versus “25 aliases” and ignore domains, seats, retention, and send-as. Solo is 25 aliases on five domains with 90-day store and 20 send-as/hour. Starter is 50 aliases, 8 domains, 5 seats. Count the objects you have.

Recovery is the silent object. If you cannot show a destination SMTP line, you will republish MX for a Gmail 5xx. MailerZ is built so that line exists. Ask ForwardMX how you get the same artifact.

Specialist support versus a plan ladder is a real fork. Some teams want a human on a small forwarder. Some want Agency numbers in writing. Neither fork allows leftover MX.

Optional mailboxes on a forwarder vendor are a store decision. If you buy a mailbox there, you left the “keep Gmail” story. Be honest.

When this path is enough

• You can name fan-out versus hop history as the fork.
• You will quote ForwardMX live, not a blog from last year.
• You accept MailerZ send-as caps if you choose MailerZ.
• You will publish one MX set.

When this is the wrong ticket

• You need IMAP as the primary store without reading who hosts it.
• You need bulk send.
• You want both MX sets.
• You want a placement SLA.

Technical mail flow

Exclusive MX decides who accepts. Envelope SRS on MailerZ. Header From intact. Destination is still Gmail or Outlook unless you bought someone else’s mailbox.

Sending is AUTH to that vendor’s SMTP. Wrong host after a move is 550. Dashboard values only for MailerZ.

Recovery is reading the hop you published. Empty MailerZ history is leftover MX or no arrival. Do not blame ForwardMX for a MailerZ leftover, or the reverse.

SPF should include the hop that sends. Two includes for two forwarders is permerror theater.

Catch-all: MailerZ paid FORWARD optional; Free HOLD. Quote ForwardMX catch-all live.

Step-by-step decision path

1. List aliases, fan-out, and whether you need hop rows That list is the comparison.
2. Open /alternative/forwardmx and ForwardMX pricing Same hour.
3. Size MailerZ plan against printed names Solo 15, Starter 50, Business 200, Agency 500.
4. If switching, recreate names before MX HOLD will show gaps.
5. Publish exclusive MX Delete the other forwarder’s hosts.
6. Probe inbound from another mailbox Copy history or their equivalent.
7. Test SMTP on the winner’s live caps MailerZ Free skip.
8. Keep the loser login until probes pass Not their MX.

Worked examples

One domain, eighty printed aliases, no need for hop history: they quoted ForwardMX Personal live and stayed. Honest.

Five domains, five humans, need destination 5xx lines: they chose MailerZ Starter. Fan-out of twenty was not the job.

Dual MX “A/B test.” Split mail. They picked one hop and tested.

SMTP left on ForwardMX after MailerZ inbound. Outbound confused everyone. One host.

Expected MailerZ to match a 100-alias Personal pack on Solo. They sized Starter or dropped museum names.

Failure modes and proof

MailerZ workflow and product boundary

Secuno LLC operates MailerZ. Site: mailerz.net. App: mail.mailerz.net. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME are never rewritten. Not IMAP. Not an open relay.

What MailerZ does

• Accept MX for verified domains.
• Rewrite envelope MAIL FROM with SRS on the forward.
• Leave Header From and MIME intact.
• Hold unknowns on Free. Optional paid FORWARD.
• Paid SMTP from approved identities. Dashboard SPF, DKIM, and DMARC instructions.
• 550 for unauthorized From. Not an open relay.

What MailerZ does not do

• Guarantee Gmail Primary or any inbox placement rate.
• Host IMAP, Calendar, or a Workspace suite.
• Send-as on Free.
• SOC 2, ISO 27001, HIPAA, review counts, or an uptime SLA. Controls: Security and Trust Center.

Plans: MailerZ pricing. Free $0, 1 domain, 10 aliases, 1 seat, 14-day store, send-as Off, SMTP Off, API Off. Solo $40/year, 5 domains, 25 aliases, 90-day, 2,500 outgoing, 20/hour, send-as On, SMTP On, API On. Starter $8 or $80, 8/50/5, 5,000, 40/hour. Business $19 or $190, 25/200/25, 12,000, 60/hour. Agency $39 or $390, 100/500/50, 20,000, 60/hour. Unlimited is $99/month or $990/year. Annual Starter, Business, and Agency include two months free versus monthly. Solo is yearly only. Recovery and hop copies live in Mail Box. Field maps: MailerZ documentation.

Cost, alternatives, and trade-offs

Field notes

Canonical table: /alternative/forwardmx. Sources there include ForwardMX pricing, overview, and service terms.

Re-quote Personal price and alias counts. Do not treat this article as a price list.

MailerZ Agency 20,000 outgoing / 60 per hour is still not bulk.

Spam filtering claims on a forwarder are not a placement SLA.

Authentication features still require you to publish SPF/DKIM/DMARC correctly.

Secuno LLC operates MailerZ. We do not operate ForwardMX.

No SOC 2 claim. /security for controls.

Self-send is invalid on both.

Treat mailerz vs forwardmx as a ticket with artifacts, not a vibe. Ask for public MX from two resolvers, a received copy, and MailerZ history before anyone edits TXT.

Write a one-paragraph policy for MailerZ vs ForwardMX: Features, Sending and Recovery Compared: inbound versus outbound, what you will not do (dual MX, From rewrite, second SPF), and who owns DNS.

Self-send is invalid for mailerz vs forwardmx. Gmail can short-circuit. Use another mailbox and a unique subject.

Leftover MX masquerades as mailerz vs forwardmx. Empty history means the hop never ran. Delete aspmx, Microsoft, and registrar MX. Wait TTL.

Free HOLD and missing aliases look like outages. History shows the hold. Create the named local-part. Catch-all FORWARD is paid and optional — not a debugger.

Paid send-as is a different hop. Free cannot send. Unauthorized From is 550 / 550 5.7.1. DNS will not authorize a From the product has not approved.

MailerZ vs ForwardMX: Features, Sending and Recovery Compared does not include an inbox placement SLA, review counts, or Primary. Say that early.

Proof packet for mailerz vs forwardmx: two-resolver MX, inbound copy with Header From, Authentication-Results, outbound copy if they send, plan name, SMTP line if anything refused.

Retention is 14 days on Free and 90 on paid. Export headers while they live. The destination inbox is the archive.

Agencies should not blend clients in one mailerz vs forwardmx thread. Agency limits are 100 domains, 500 aliases, 50 seats, 20,000 outgoing, 60/hour — still not an SLA.

No SMTP passwords in the mailerz vs forwardmx ticket. No invented SOC 2. Controls live on the Security and Trust Center.

If two products share MX, stop adding records. Exclusive MX is a hard stop. mailerz vs forwardmx cannot be correct on a split path.

If Header From is rewritten, stop tuning SPF for mailerz vs forwardmx. Change the hop. MailerZ will not offer a From-replace control.

If the customer wants Calendar, sell a suite. If they want a hop, sell a hop. MailerZ vs ForwardMX: Features, Sending and Recovery Compared is not Exchange.

Hourly and monthly send-as ceilings (disabled/2,500/5,000/12,000/20,000 outgoing; 20/40/60/60 per hour) produce refuses that look like mailerz vs forwardmx. Read counters.

Null MX plus a real MX is a lie. Remove the lone-dot refuse if you intend to receive.

After any change for mailerz vs forwardmx, wait TTL, probe from another mailbox, and store the new received source next to the MX screenshot.

Write mailerz vs forwardmx in the subject and the layer in the first sentence: leftover MX, HOLD, destination 550, or TTL. Honest first sentences shrink tickets.

Monthly for mailerz vs forwardmx: leftover MX lookup, one external inbound probe, send-as counters if paid. Five minutes. The outage you avoid is a Friday dual-MX restore.

When two vendors disagree about mailerz vs forwardmx, believe two resolvers, one received copy, and one history row. Registrar dots lie. Composer UIs lie.

Teach the next hire the MailerZ split before they touch mailerz vs forwardmx: envelope may change, Header From must not, Free cannot send, unknowns HOLD, leftover MX is a hard stop.

If mailerz vs forwardmx appears in an RFP, answer with published caps and hop evidence. Decline inbox-rate clauses and fake certifications.

Do not bundle unrelated edits with mailerz vs forwardmx. Rotating SMTP while republishing MX while enabling FORWARD is how you lose the ability to name the failure.

Field story 1 for mailerz vs forwardmx: One domain, eighty printed aliases, no need for hop history: they quoted ForwardMX Personal live and stayed. Honest. Keep it in the runbook.

Field story 2 for mailerz vs forwardmx: Five domains, five humans, need destination 5xx lines: they chose MailerZ Starter. Fan-out of twenty was not the job. Keep it in the runbook.

Field story 3 for mailerz vs forwardmx: Dual MX “A/B test.” Split mail. They picked one hop and tested. Keep it in the runbook.

Field story 4 for mailerz vs forwardmx: SMTP left on ForwardMX after MailerZ inbound. Outbound confused everyone. One host. Keep it in the runbook.

Field story 5 for mailerz vs forwardmx: Expected MailerZ to match a 100-alias Personal pack on Solo. They sized Starter or dropped museum names. Keep it in the runbook.

For mailerz vs forwardmx, “Split mail” usually means Both MX. Isolate with Delete one. One change at a time.

For mailerz vs forwardmx, “No hop line” usually means Chose a vendor without stored dest SMTP. Isolate with Ask before cutover. One change at a time.

For mailerz vs forwardmx, “Outbound 550” usually means Free MailerZ or old host. Isolate with Paid; swap host. One change at a time.

For mailerz vs forwardmx, “Alias overflow” usually means Wrong plan. Isolate with Count printed names. One change at a time.

For mailerz vs forwardmx, “Fan-out privacy mess” usually means Twenty recipients on one public address. Isolate with Narrow destinations. One change at a time.

For mailerz vs forwardmx, “Invented SLA” usually means RFP leftover. Isolate with Refuse. One change at a time.

Setup step “List aliases, fan-out, and whether you need hop rows” for mailerz vs forwardmx: That list is the comparison. Skip it and MailerZ vs ForwardMX: Features, Sending and Recovery Compared becomes next week’s ticket.

Setup step “Open /alternative/forwardmx and ForwardMX pricing” for mailerz vs forwardmx: Same hour. Skip it and MailerZ vs ForwardMX: Features, Sending and Recovery Compared becomes next week’s ticket.

Setup step “Size MailerZ plan against printed names” for mailerz vs forwardmx: Solo 15, Starter 50, Business 200, Agency 500. Skip it and MailerZ vs ForwardMX: Features, Sending and Recovery Compared becomes next week’s ticket.

Setup step “If switching, recreate names before MX” for mailerz vs forwardmx: HOLD will show gaps. Skip it and MailerZ vs ForwardMX: Features, Sending and Recovery Compared becomes next week’s ticket.

Setup step “Publish exclusive MX” for mailerz vs forwardmx: Delete the other forwarder’s hosts. Skip it and MailerZ vs ForwardMX: Features, Sending and Recovery Compared becomes next week’s ticket.

Setup step “Probe inbound from another mailbox” for mailerz vs forwardmx: Copy history or their equivalent. Skip it and MailerZ vs ForwardMX: Features, Sending and Recovery Compared becomes next week’s ticket.

Setup step “Test SMTP on the winner’s live caps” for mailerz vs forwardmx: MailerZ Free skip. Skip it and MailerZ vs ForwardMX: Features, Sending and Recovery Compared becomes next week’s ticket.

Setup step “Keep the loser login until probes pass” for mailerz vs forwardmx: Not their MX. Skip it and MailerZ vs ForwardMX: Features, Sending and Recovery Compared becomes next week’s ticket.

Trade-off on mailerz vs forwardmx: MailerZ ladder + history gets HOLD, seats, 14/90 store and gives up Smaller alias packs on low plans. Write that on the quote.

Trade-off on mailerz vs forwardmx: ForwardMX annual alias pack gets Many names on one domain and gives up Confirm logs and seats live. Write that on the quote.

Trade-off on mailerz vs forwardmx: Both MX gets Fake A/B and gives up Split inbound. Write that on the quote.

Trade-off on mailerz vs forwardmx: Buy their optional mailbox gets A store and gives up You left “keep Gmail”. Write that on the quote.

Features, sending, and recovery as three separate scorecards

Features are not a single column. Catch-all, spam filtering, authentication wizards, and fan-out are ForwardMX’s public emphasis — quote them live. Named aliases, HOLD, seats, and a Free-to-Agency ladder are MailerZ’s. Ticking every marketing noun onto one score is how you buy fan-out and then ask where the destination 5xx line went.

Sending is AUTH, From policy, and caps. MailerZ publishes monthly and hourly numbers and refuses unauthorized From with 550. Free cannot send. ForwardMX lists SMTP on pricing — read the current count and acceptable use. If either number is below last month’s human send, do not migrate outbound onto that hop. Keep the old SMTP until you size correctly, then swap one host.

Recovery is an artifact. MailerZ stores hop history and failed destination SMTP for 14 days on Free and 90 on paid. Ask ForwardMX what row you can screenshot when Gmail says 550 after a 250. If the answer is “check the destination,” you did not buy recovery. You bought a hop without a witness.

Alias packs tempt one-domain shops. A hundred names on Personal can beat Solo’s twenty-five on price. Count printed names and domains. Five domains with twelve names each is sixty aliases and five domains — Starter or Business on MailerZ, not a one-domain pack. Wrong object.

Fan-out to many humans looks like collaboration. It is also a privacy and filter multiplier. Each extra destination can drop or leak. Prefer a shared mailbox destination or a small alias map over twenty recipients on hello@ unless you have a written reason.

Optional mailboxes on ForwardMX change the class. If you buy a mailbox there, you are no longer comparing two hops in front of Gmail. You are buying a store. MailerZ will not meet you there. Be explicit on the quote.

Annual versus monthly is cash, not architecture. Solo is yearly only at $40. ForwardMX Personal has been annual. Starter monthly exists if you need to leave in thirty days. Do not let billing cadence hide leftover MX.

After the buy, delete the other MX. Features do not layer. Recovery does not layer. Sending does not layer. One owner per conversation.

Write the three scores on the quote before anyone publishes TXT. Features: named HOLD versus fan-out and alias packs. Sending: MailerZ disabled/2,500/5,000/12,000/20,000 and 20/40/60/60 versus ForwardMX’s live SMTP line. Recovery: 14-day or 90-day hop store versus whatever log they document today. If a stakeholder cannot pick a winner on those three lines, they are shopping logos. Pause the MX change.

Agencies must not average clients. A one-domain shop that loves a Personal alias pack is not a five-domain team that needs seats and hop rows. MailerZ Business is 25 domains, 200 aliases, 25 seats, 12,000 outgoing, 60 per hour. Quote ForwardMX’s current multi-domain story separately. Blended advice produces leftover MX on the client who was not in the room.

FAQ

Key takeaways

• Both are forwarders. Quote ForwardMX live.
• MailerZ: HOLD, history, seats, modest SMTP.
• ForwardMX: alias packs and fan-out on their current card.
• Recovery means hop artifacts, not an SLA.
• One MX owner.
• Free MailerZ cannot send.
• Optional mailboxes are a store.
• Size aliases to the printed list.

Conclusion and next action

Put alias count, fan-out, hop history, and send caps on one sticky note. The product that matches three of four wins. The fourth is a compromise you write down.

Then publish one MX set. Features do not stack across leftover records.

Prove inbound. If you cannot see a hop row and that was the reason you left, you bought the wrong recovery story.

Review quarterly, or sooner if DNS hosts or dashboard instructions change. Author: MailerZ editorial, Secuno LLC.