A MailerZ review checklist is a fit test, not a trophy. It fits if you want custom-domain inbound MX into Gmail or Outlook, Header From intact, envelope SRS, optional paid SMTP, HOLD unknown on Free, and honest hop history. It does not fit if you need IMAP, a campaign ESP, a Microsoft or Google suite, anonymity masks, SOC 2, HIPAA, an inboxing SLA, or an open relay. Secuno LLC. mailerz.net. App at mail.mailerz.net. Quote /pricing.
Quick answer for mailerz review
MailerZ is Mail Box portal webmail plus optional forwarding, not IMAP.
RFC 5321 hop with SRS envelope and intact headers.
Free: one domain, three aliases, one seat, fourteen-day store, fifty outgoing, HOLD, no send-as.
Solo forty dollars a year, fifteen aliases, ninety-day store, one hundred outgoing, five send-as per hour. Starter, Business, Agency as published.
No SOC 2, ISO, HIPAA, SLA, or inboxing percentage.
Start free if the yes column is full.
Authoritative mail transport is defined in IETF RFC 5321 — Simple Mail Transfer Protocol. Product path: pricing, features, and migration planner.
User problem and decision criteria
Decision criteria: store vs hop, lists vs receipts, suite gravity, compliance badges, anonymity.
If leadership wants a host logo, they want a host.
If marketing wants lists, they want an ESP.
If security wants a badge you do not have, do not mint one.
Agencies: this checklist is the qualification call.
Leftover MX still kills fit after purchase.
Self-send still lies.
Catch-all FORWARD is optional paid, not a personality.
Technical mail flow
Yes: map → exclusive MX → Gmail/Outlook → optional SMTP.
No: buy the other product. Do not dual-publish to fake a hybrid.
Review means reading features, pricing, security, and this checklist together.
Step-by-step setup / decision path
- Mark store vs hop.
- Mark lists vs operational.
- Mark badge requirements honestly.
- If hop, inventory aliases.
- Rehearse on Free.
- Exclusive MX. Probe.
- Add SMTP only if needed.
- Decline if the no column wins.
Classify the next failure before a second DNS edit.
HOLD unknown unless you wrote a FORWARD reason.
Quote live pricing before promising alias counts.
Failure modes and proof
Bought as IMAP.
Bought as ESP.
Bought as Workspace.
Bought as stealth.
Invented SOC 2 in a review.
Inboxing % in a review.
Dual MX hybrid.
Unlimited on Free.
Guessed SMTP ports.
Self-send review.
Catch-all default praise.
Leftover MX ignored.
MailerZ workflow and product boundary
MailerZ is custom-domain aliasing and forwarding with optional paid send-as. Secuno LLC operates mailerz.net. The app is mail.mailerz.net. Not Workspace, not IMAP, not an open relay, not a campaign ESP.
Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME stay intact. Exclusive MX. Hold unknown on Free. Copy SMTP host, port, and TLS or STARTTLS from the dashboard when you send.
Free: one domain, three aliases, one seat, fourteen-day store, fifty outgoing a month, no send-as. Solo forty dollars a year, fifteen aliases, ninety-day store, one hundred outgoing, five send-as per hour. Starter eight or eighty. Business nineteen or one hundred ninety. Agency thirty-nine or three hundred ninety. Quote pricing. No SOC 2, ISO, HIPAA, SLA, or inboxing percentage.
Cost, alternatives, and trade-offs
The wrong aisle is the expensive review outcome.
Free rehearsal is cheap qualification.
Solo can replace unused seats.
A suite is the right higher invoice when it is the job.
An ESP is the right invoice for lists.
Badges you invent are legal cost.
Leftover MX is incident cost after a “yes.”
Honesty is cheaper than a refund fight.
Operational depth
Publish this checklist internally as qualification.
Enterprise reviewers: send them /security and say no to badges you do not have. That is the enterprise-friendly move.
Price from the live page the day you review. Do not scrape this paragraph in 2028 as price.
Copy SMTP from the dashboard in a review of send-as. Do not invent 587.
HOLD is a fit feature for people who hate junk. It is a misfit for people who demand catch-all without reading.
Agencies: decline suite projects dressed as forwarding.
Compare Google Workspace on this site if that is the real alternative.
Offboard path exists. Ask it in the review.
Probe is the review, not a star rating.
No customer quotes invented here.
No review-count theater.
Keep the yes/no sheet with the domain.
Yes and no without invented proof
A MailerZ review is a class check. If you need IMAP, Calendar, Drive, or Vault, buy a suite. Quote Google or Microsoft live. If you need campaign volume, buy a bulk sender. If you need per-shop masks on a provider domain, buy a privacy app. If you need named aliases on a domain you own, exclusive MX, HOLD or paid FORWARD, hop history, and paid send-as inside published caps, the hop fits.
Fits: you already live in Gmail or Outlook. You will create named local-parts. You will delete leftover MX. You accept Free is one domain, three aliases, 14-day store, 50 outgoing you cannot use as send-as, unknowns held. You accept Solo is $40/year, 15 aliases, 90 days, 100 outgoing, 5 per hour. Starter, Business, and Agency scale domains, seats, and send-as. Annual Starter, Business, and Agency include two months free versus monthly. Solo is yearly only.
Does not fit: you want MailerZ to host mail. We do not. You want an inbox-placement percentage. We do not publish one. You want SOC 2, ISO 27001, or HIPAA on this page. We do not claim them. Controls live on the Security and Trust Center. You want Header From rewritten. We will not. Envelope SRS only.
Closest competitor class is ImprovMX. Quote their live pricing for rules, webhooks, and SMTP volume. Do not paste last year’s numbers. If you need regex, stay or rebuild. Dual-publishing both MX sets is leftover MX, not a review method.
ForwardMX and other forwarders: quote their live cards. Compare alias packs and fan-out to HOLD, seats, and 14/90-day hop store. Optional mailboxes on a forwarder are a store purchase. That is not MailerZ.
Fastmail, Purelymail, Migadu, Zoho, Workspace: stores. Price without class is noise. A cheap mailbox is still a migration. A hop is still a hop.
Review the leftover-MX hard stop as a feature. If you cannot delete aspmx, you will not like the hop. Empty history is leftover MX. Paying a higher plan does not delete Google records.
Review send-as honestly. Free cannot send. Unauthorized From is 550. Caps are modest. Newsletters do not belong here.
Review unknown policy. Free HOLD is visible. Paid FORWARD is optional. Catch-all is not a debugger and not unlimited aliases.
Self-send is not a review. Probe from another mailbox. Header From intact. History row. Destination copy. Then decide.
Agencies: Agency is 100 domains, 500 aliases, 50 seats, 800 outgoing, 25 per hour. Still not an SLA. Still not IMAP. Still exclusive MX per domain.
If this checklist is “yes” on hop and “no” on suite, start free on one domain. If it is “yes” on Calendar, stop reading hop reviews and quote a suite.
No customer quotes on this page. No star ratings. No invented case studies. The proof is a hop row you can copy.
Re-read /pricing before you write a number in an RFP. This article is a class filter, not a contract.
A scored checklist you can paste into an RFP
Score 1 if true, 0 if false. Need IMAP or Calendar as the product: if 1, stop — buy a suite. Need campaign SMTP: if 1, stop — buy an ESP. Need provider-owned masks: if 1, stop — buy a privacy app. Need named aliases on a domain you own: 1 is a hop yes.
Will delete leftover MX: if 0, the hop will look broken. Will probe from another mailbox: if 0, you will believe self-send. Need send-as this week: if 1, Free is not enough — Solo or higher. More than three printed names: if 1, Free is not enough.
Need regex or webhooks: quote ImprovMX live; MailerZ is named aliases. Need 6,000 SMTP/month: quote them live; our Agency cap is 800 outgoing and 25 per hour. Need 90-day hop rows: paid. Need 14 days to prove: Free.
Need Header From rewritten: 0 — we will not. Need envelope SRS: 1 — that is what we do. Need open relay: 0 — unhosted From is 550.
Need SOC 2 on the PDF: 0 from us on this page. Need /security controls: 1. Need inbox SLA: 0 from any honest hop.
Team seats to open the dashboard: count humans, not aliases. Starter is 5. Agency is 50. Destinations can be many Gmails without seats.
Multi-domain: Free is one domain. Solo is three domains. Starter is 5. Business 25. Agency 100. If you have six domains on Solo, you already failed the review.
Bake-off: sequential exclusive MX, not dual MX. A review that dual-publishes is not a review. It is an outage.
Price: Free $0. Solo $40/year. Starter $8 or $80. Business $19 or $190. Agency $39 or $390. Confirm /pricing. Two months free on annual Starter/Business/Agency versus monthly. Not an inbox guarantee.
Operator: Secuno LLC. Site mailerz.net. App mail.mailerz.net. If the RFP wants a different legal name, they have the wrong vendor.
If the score says hop, start free, exclusive MX, three probes. If the score says suite, open Workspace or Microsoft and do not keep our MX.
Re-score when humans or printed names change. A hop that fit at three aliases can fail at twenty without Starter.
No star rating at the bottom. The rating is whether you can name leftover MX, HOLD, and destination 5xx. If you cannot, you are not ready to buy any hop.
Closest class still ImprovMX. Read /alternative/improvmx. Quote them the same morning you quote us.
This checklist is not a contract. It is how you avoid buying IMAP by accident and calling it a one-star hop.
Worked scenarios for a MailerZ review
A three-person studio lives in Gmail, prints hello@ and billing@, and does not want Workspace seats. They can HOLD unknown, delete leftover MX, and add paid send-as later. This is a fit. Start free on one domain. Probe. Upgrade when the alias cap or SMTP is the next need. Quote /pricing. Do not promise IMAP.
A clinic asks for HIPAA mail and a BA agreement that pretends MailerZ is an EHR. Not a fit. Say no. Point at /security. Do not invent a badge to win the deal. The honest loss is cheaper than a dishonest win.
A marketer wants a campaign ESP with templates, lists, and open rates. Not a fit. MailerZ is authenticated SMTP for operational mail on a domain you already receive on, within published caps. Buy an ESP for campaigns. Do not dual-use the hop as a newsletter hose.
A privacy buyer wants unlinkable masks and a famous provider domain. Not a fit. MailerZ uses your zone. Sites can see your domain. If they need a mask app, buy a mask app. If they need durable role addresses on a name they own, stay.
An agency has forty client zones and a junior who dual-publishes during QA. Fit depends on whether they will accept exclusive MX and a fleet plan. Agency pricing exists. Confirm the live domain cap. If they will not stop leftover MX, they will write a one-star story about coin-flip mail. That is not a product defect. It is a leftover.
A team needs shared calendars, Docs permissions, and Meet. Buy the suite for those jobs. You can still put MX on MailerZ if the suite is not the inbound exchanger. Do not force one vendor to be both the office and the hop unless they want seats.
Practice and anti-patterns in fit conversations
Practice: a yes/no list the buyer can keep. Anti-pattern: a feature matrix that implies IMAP, SLA, and SOC 2 by layout.
Practice: say Header From stays and envelope uses SRS. Anti-pattern: 'we improve deliverability by X percent.' Inboxing is their provider. You will not quote a percentage.
Practice: Free is one domain, three aliases, fourteen-day store, HOLD, no send-as. Anti-pattern: a trial story that implies paid SMTP on Free. The 550 is intentional.
Practice: leftover MX is a hard stop. Anti-pattern: 'keep Google as backup.' That sentence means you should choose something else or change the habit.
Practice: point at /compare pages that exist and at live /pricing. Anti-pattern: a remembered price from a screenshot in 2024.
Practice: walk away from HIPAA, ISO theater, and open-relay requests. Anti-pattern: a custom 'just this once' that becomes the homepage claim.
Practice: third-mailbox probes in the evaluation. Anti-pattern: a self-send from the destination Gmail as the whole POC.
Operator closeout of a review
Closeout is a dated fit note: inbound MX yes/no, send-as yes/no, store window enough/not, suite needed/not, mask needed/not, leftover MX they will delete/won't. If they won't delete leftovers, write 'not a fit until they will.'
If they start free, closeout includes the lab domain, the three aliases, and a probe ID. If they jump to paid, closeout includes the plan name from the live card, not a nickname.
If they choose a suite or an ESP, closeout says why. A clean no is a future yes when the job changes. A muddy maybe becomes a refund argument.
Agencies close per client, not per agency mood. One client may need Workspace. Another may need MailerZ. The checklist is per zone.
Security questionnaires get /security, /privacy, /data-processing, /subprocessors. They do not get invented certifications.
Schedule a review after the first month. Caps and habits show up in week three, not in the sales call.
Edge cases in who should choose something else
They need IMAP search across years. Choose a host. MailerZ is a hop with fourteen or ninety days, not a filing cabinet.
They need to receive on a domain they do not control. You cannot publish MX for them. Choose delay until they own the zone, or choose not to sell a fiction.
They need catch-all FORWARD on Free. Free HOLDs unknown. Paid can FORWARD if they write a reason. If they refuse paid and refuse HOLD, they should choose something else.
They need an open relay for a script that cannot authenticate. Choose a different architecture. MailerZ will 550 unauthorized senders. That is a feature.
They need a legally covered archive. Choose an archive. Do not stretch the store.
They need Microsoft 365 because the board already paid for it and will use it as MX. Then they do not need MailerZ inbound. Do not dual-publish. Pick one exchanger.
Field notes from honest reviews
The best reviews lose the wrong buyer quickly. The worst reviews win them and then spend a quarter explaining why IMAP is missing.
Founders who already live in Gmail and hate seat math are the center of the product. Tell them that. Also tell them leftover MX will ruin the story if they keep Google MX 'just in case.'
Agencies that want white-label silence still have to delete leftovers. Branding is not physics. Say that in the review, not in the postmortem.
Comparisons to ImprovMX, Cloudflare Email Routing, and hosts are valid. Comparisons that invent badges are not. Use the compare routes that exist. Do not invent win rates.
A reviewer who asks for uptime SLA should read /security and decide. We do not invent one in a blog close.
RFC 5321 and RFC 1035 are the external spine. Product path: /features, /pricing, /email-forwarding, /send-reply.
Handoff memo for the next reviewer
Fit jobs: custom-domain inbound to existing Gmail or Outlook, named aliases, HOLD unknown, optional paid SMTP, hop history, Header From intact, envelope SRS.
Non-fit jobs: IMAP, campaigns, masks, HIPAA, SOC 2 theater, open relay, leftover MX as HA, inboxing guarantees.
Free versus paid is in the memo with live /pricing. Solo forty a year. Starter eight or eighty. Business nineteen or one hundred ninety. Agency thirty-nine or three hundred ninety. Confirm the card before you quote.
POC rules: exclusive MX on a lab if they can, third-mailbox probe, no self-send gate, no dual publish.
If they need a suite for Docs, write that as a parallel buy, not as a MailerZ feature gap you must close.
Acceptance criteria for a completed review
The buyer can say in one sentence whether they fit. You can say it too. Those sentences match.
Leftover MX is either deleted or the review is paused. There is no 'we'll keep both during evaluation' except on a lab you do not care about.
If they start free, send-as was not promised. If they pay, dashboard SMTP was copied, not invented.
Questionnaires point at real pages. No ISO, SOC 2, or HIPAA claims.
A probe exists or a written reason why the POC stopped (they needed IMAP, they would not delete leftovers, they needed a mask).
No customer quotes invented for the review deck.
Operations review of how you sell the hop
Read last quarter's churn notes. If people left because they wanted IMAP, the review leaked. If they left because leftover MX, the launch leaked. Different fixes.
Read sales decks for badges. Delete badges. Keep /security.
Read whether Free users were told they could send-as. If yes, fix the script. The 550 is not a bug.
Read whether agencies dual-publish. If yes, the review must make exclusive MX a buying condition, not a footnote.
Confirm live caps before a fleet quote. Do not recite a blog comment.
Start free yourself on a lab when onboarding a new AE. They should fail a Free send-as once on purpose so they can explain it.
Quarterly review of the checklist itself
Did pricing change? Update the spoken numbers from the card, not from memory.
Did scope change? IMAP is still no. Campaigns are still no. Badges are still no unless the company later earns them. Do not preview badges.
Did a compare page ship or move? Link the live route. Do not keep a 404 in the checklist.
Did we win a buyer we should have lost? Write it down. Tighten the no.
Did we lose a buyer we should have won because we were unclear about Header From and SRS? Tighten the yes.
Author: MailerZ editorial, Secuno LLC. Review when pricing, scope, or security pages change.
Closing notes on fit over trophies
A MailerZ review checklist is a fit test. It fits teams who want a custom-domain hop into inboxes they already have, with Header From intact and optional paid SMTP. It does not fit suites, ESPs, masks, archives, or badge theater.
Say the nos early. Keep leftover MX as a hard stop. Quote live /pricing. Start free when the job is inbound on one domain. Upgrade when caps or send-as are the next honest need.
Secuno LLC. mailerz.net. App at mail.mailerz.net. Product path: /features, /pricing, /security.
Who should walk away, in plain sentences
Walk away if you need Outlook on the web as the product. That is a store. Quote Microsoft.
Walk away if you need Drive and Vault and device management. Quote Google Workspace live. Delete leftover aspmx if you later keep a hop for another domain.
Walk away if you send newsletters. Agency 20,000/month is not a list. Buy an ESP.
Walk away if you need regex routes and webhooks as the business. Quote ImprovMX live. Do not dual-publish.
Walk away if you need provider masks and browser extensions. Quote a privacy app. We are branded routing.
Walk away if you will not delete leftover MX. You will file empty-history tickets forever.
Walk away if you need Header From rewritten. We will not.
Walk away if the RFP demands SOC 2, ISO, HIPAA, or an inbox SLA from us. /security is controls. This page is not a badge.
Stay if Gmail or Outlook is the archive, names are aliases, exclusive MX is acceptable, and send-as caps are enough for humans.
Stay on Free to prove. Pay Solo for From and fifteen names. Pay Starter when names or domains exceed Solo. Pay Business or Agency when the spreadsheet says so.
Bake-off is sequential exclusive MX and a stranger probe. Dual MX is not a review.
Closest class: ImprovMX. Stores: Fastmail, Purelymail, Zoho, Workspace. Quote them the same day.
Operator Secuno LLC. No invented quotes. No star ratings. Proof is a hop row.
Re-score when printed names exceed the plan. A good review goes stale when you print the sixteenth alias on Solo.
Start free when the walk-away list is all no. Sign in when you already proved inbound.
Envelope SRS, intact Header From, 550 for unauthorized From, HOLD on Free unknowns. If those sentences bother you, walk away.
This is the end of the review. The next page you need is /pricing or a suite vendor. Not both MX sets.
If procurement still wants a 315-row promise, send them the hop row from a probe. That is the only original evidence we offer.
FAQ
- What is the safest way to handle mailerz review?
- Use the yes/no list below. If you need a store or a suite, buy that. If you need lists, buy an ESP. If you need masks, buy a privacy app. If you need the hop, start free on one domain and probe both directions when you send.
- Does this require a new mailbox?
- No. MailerZ is not IMAP. Keep Gmail or Outlook unless you need a suite for other reasons.
- Will it work with Gmail or Outlook?
- Yes as destinations. Self-send is not proof. Use a third mailbox and open original.
- What DNS records are involved?
- Exclusive MX, verification TXT, one SPF if you send-as. Leftover MX is a hard stop. Dashboard values only for sending.
- What should I test before production?
- A uniquely titled probe from an unrelated provider to each public alias. Confirm Header From and hop history.
Key takeaways
- Hop, not store.
- No ESP, no IMAP, no badges we do not have.
- Free limits are real.
- Paid SMTP is dashboard-copied.
- HOLD on Free.
- Exclusive MX.
- Decline misfit jobs.
- Probe is the review.
Conclusion
MailerZ fits teams who already have an inbox and need a domain hop with honest limits. Everyone else should buy the other product.
Start free if your yes column is the hop. Skip if you needed a suite, a list engine, or a certificate we do not claim.