Email forwarding provider questions are a go / no-go list: exclusive MX, Header From intact or rewritten, envelope SRS, HOLD versus catch-all, store window, send-as and how you copy SMTP, leftover-MX stance, and what they will not promise. MailerZ answers: SRS envelope only, headers intact, HOLD on Free, fourteen- or ninety-day store, dashboard SMTP on paid, no inboxing percentage, no SOC 2. If a vendor cannot answer, do not point MX.
Quick answer for email forwarding provider questions
The dangerous vendor rewrites visible From or shrugs at leftover MX.
RFC 5321 and 7208 are how you test their story.
MailerZ: exclusive MX, SRS, intact From, HOLD on Free, dashboard SMTP, honest no-percentage.
Ask for artifacts: history, stored failures.
Ask plan limits in numbers. Free is ten aliases and no send-as here.
Start free only after the answers match the job.
Authoritative mail transport is defined in IETF RFC 5321 — Simple Mail Transfer Protocol. Product path: MailerZ pricing, features, migration planner, Mail Box, and the MailerZ documentation. Solo is $40 per year with send-as, SMTP, and API On. Free keeps those Off. Ask whether you can see the destination SMTP reply after a hop. If the answer is no, you are buying a shrug. Ask whether leftover MX is treated as a hard stop. If the vendor says dual MX is fine, you are buying a coin flip. Ask how many days a failed copy stays visible. MailerZ Free is fourteen days. Paid plans are ninety. Unlimited is one hundred eighty. If they cannot name a number, you will have no evidence when a customer calls on day twenty.
User problem and decision criteria
Decision criteria: identity, exclusivity, unknown policy, store, SMTP, support artifacts.
If you need IMAP, you are in the wrong aisle.
If you need lists, you want an ESP.
If you need a suite, you want a host.
Agencies should use this list on every vendor, including MailerZ.
No badge shopping.
No dual MX “just to try.”
Price pages go stale—check live.
Technical mail flow
Questions → written answers → rehearsal domain → exclusive MX → probe → then production.
Self-send is not the probe.
Leftover MX is a hard stop in the answers.
Step-by-step setup / decision path
- Write the job: inbound only or also send-as.
- Ask the From/SRS question.
- Ask exclusive MX.
- Ask HOLD/FORWARD defaults.
- Ask store length.
- Ask SMTP copy path and caps.
- Ask what they will not promise.
- Rehearse, then cut.
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
Did not ask about From rewrite.
Dual MX trial.
Believed an inboxing %.
Assumed IMAP.
Assumed unlimited on Free.
No leftover-MX question.
Secrets from a blog port.
Self-send QA.
Catch-all default surprise.
No store clock.
SOC 2 assumed.
Cut production first.
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, ten aliases, one seat, fourteen-day store, send-as disabled, SMTP and API disabled. Solo forty dollars a year, twenty-five aliases, ninety-day store, 2,500 outgoing, 20 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
A bad From rewrite is a brand cost.
A good rehearsal is cheap.
Inboxing promises are refund cost.
Agencies: this questionnaire is a deliverable.
Unlimited marketing is usually a limit in a footer.
Store clocks are evidence cost if short.
No fake SLA.
Dashboard SMTP beats a guessed port outage.
Operational depth
Keep the answers in the client folder.
Compare MailerZ features and pricing pages to the answers. Trust the live pages.
If a vendor is cute about leftover MX, they will cost you an incident.
If they rewrite From, DMARC pain is on you.
If they have no history, you will debug with folklore.
Security page for enterprise questionnaire. Do not invent controls.
Rehearse on Free.
Serial cuts if many domains.
Form SMTP is a separate ask.
Offboard ask: how do we leave.
Probe Message-IDs.
Re-read pricing the day you buy.
Field notes for email forwarding provider questions
Write the answers before anyone gets registrar access. A verbal “they’re fine” is how From-rewriters and leftover-MX shrugs become production. Keep the sheet in the client folder. Compare live pages the day you buy. Blogs go stale. This article will not scrape competitor prices.
Ask whether Header From is rewritten. If yes, walk. DMARC and humans both suffer. MailerZ rewrites envelope MAIL FROM with SRS only. From, Subject, Date, Message-ID, body, and MIME stay. Read a received original in the rehearsal. Trust headers, not a sales call.
Ask whether MX must be exclusive. If they recommend a backup vendor MX, walk. Two owners split senders. MailerZ treats leftover MX as a hard stop. Demoting priority is not exclusivity. Two public resolvers are the test, not a panel checkmark.
Ask what happens to unknown local-parts. HOLD, reject, or FORWARD. Free on MailerZ holds. FORWARD as a default is a junk strategy. You want the answer in writing. “We catch everything” is not a feature if your destination is Gmail.
Ask store length and what artifacts exist. Hops, SMTP codes, held copies. Fourteen days Free, ninety paid on MailerZ. If they have no history, you will debug with folklore. Ask how you leave: export, revoke, MX delete. Offboard is a question, not a later surprise.
Ask how send-as is configured. Dashboard copy or a blog port. MailerZ: copy host, port, TLS or STARTTLS from the app. Free cannot send-as. Caps exist. If they imply unlimited outbound on a forwarding plan, read the footer. Lists need an ESP.
Ask what they will not promise. Inboxing percentages, SOC 2, ISO, HIPAA, SLAs. MailerZ will not promise those. Security is the questionnaire. Walk from folder guarantees on a forwarder. Filters live at Gmail and Outlook.
Ask whether they are IMAP. If you need a store, you want a host. Forwarding around Gmail is a different job. Dual-publishing a host and a forwarder is leftover MX. See Workspace comparison if the real alternative is a suite.
Rehearse on one domain. Exclusive MX. Third-mailbox probe both ways if you send. Self-send is not the rehearsal. Message-IDs in the notes. Then cut production.
Agencies should run this list on MailerZ too. Qualification is not loyalty. If a future MailerZ change broke a promise, the written answers are how you notice. Trust features and pricing over memory.
Form SMTP is a separate ask. From must be receivable. Rate limits. Secrets in env. Staging sinks. If they cannot describe that loop, your website will send as a dead letter.
Leftover-MX attitude is the tell. Cute answers cost incidents. You want “delete the old set, then probe.” You do not want “keep Google at priority 20 for safety.”
If they cannot explain envelope versus Header From, they will not explain a 550. Hire someone who can read IETF RFC 5321 — Simple Mail Transfer Protocol or pick a vendor whose docs already do.
Price from the live page the morning you sign. Unlimited marketing is usually a limit in a footnote. Free MailerZ is ten aliases and no send-as. Write the numbers you were told next to the URL you checked.
Do not cut on a product launch day if the answers are incomplete. Incomplete answers are a no-go, not a weekend of hope.
Worked scenarios for provider questions
Vendor A rewrites Header From so “SPF passes.” You walk. Recipients see the wrong person. DMARC alignment on the real sender dies. MailerZ will not do this. The question was the first one. You did not need a price comparison.
Vendor B says keep Google MX at 20 for safety. You walk. That is leftover MX as a product recommendation. Exclusive or you do not point production.
Vendor C has no hop history. A customer incident will be folklore. You either accept that or you pick a vendor with stored codes. MailerZ stores hops in the window. Fourteen or ninety days. Ask the clock.
Vendor D implies unlimited send on a forwarding plan. Footer says a cap. Lists need an ESP. You write the number next to the URL you checked that morning. You do not paste a 2023 blog.
Vendor E claims 99% inboxing. You walk. Nobody outside Gmail owns that folder. MailerZ will not print a percentage. Security reviewers should hear the same no.
You ask MailerZ the same list. Features and pricing and security match: SRS envelope, intact From, HOLD on Free, no send-as on Free, dashboard SMTP on paid, no badges. Qualification is not loyalty. Rehearse anyway.
Form SMTP question skipped. Site sends as a host you do not receive. Replies die. Two-direction probe would have caught it. Add the question: From receivable? Rate limit? Env secrets? Staging sink?
Offboard question skipped. You cannot leave without a ticket novel. Ask export, revoke, MX delete, store clock. Write it. Future you during a breakup will not be kind if this is missing.
IMAP assumed. Users expected folders on the domain. Wrong aisle. Host or keep Gmail. Dual-publish is leftover MX. The question “are you a mailbox” should be early.
Rehearsal skipped because the CEO wanted it live Monday. Incomplete answers. You delay. Incomplete is a no-go. Hope is not a cutover plan.
Agency uses the list on two vendors the same week. Written answers. One From-rewriter eliminated. One leftover-MX shrug eliminated. The remaining vendor gets a rehearsal domain. That is the questionnaire earning money.
Someone cannot explain envelope versus Header From. They cannot explain a 550. You pick a vendor whose docs already speak RFC 5321 or you hire help. Cute marketing is not a runbook.
Price changed between proposal and sign. You re-check the live page. You update the sheet. You do not pretend the old number is a contract if it was never a quote from them.
Leftover-MX attitude was cute, you bought anyway. Incident Friday. Postmortem class leftover MX. The questionnaire had the tell. You ignored it. Next time you walk. That is the scenario you write on the wall.
Practice and anti-patterns for provider questions
Anti-pattern: verbal they’re fine. Write answers before registrar access. From-rewriters and leftover-MX shrugs become production otherwise.
Anti-pattern: Header From rewrite to pass SPF. Walk. Read a received original. Envelope SRS plus intact From is the pair you want.
Anti-pattern: backup vendor MX at 20. Walk. Exclusive or no production cut.
Anti-pattern: no hop history. Incidents become folklore. Ask the store clock. Fourteen or ninety on MailerZ.
Anti-pattern: unlimited send implied. Read the footer. Lists need an ESP. Write the number next to the URL you checked that morning.
Anti-pattern: inboxing percentage. Walk. Filters live at Gmail and Outlook. MailerZ will not print a rate.
Anti-pattern: skipped form SMTP question. Dead Reply-To. From receivable, rate limit, env, staging sink.
Anti-pattern: skipped offboard. Ticket novel at breakup. Ask export, revoke, MX delete, store clock.
Anti-pattern: IMAP assumed. Wrong aisle. Host or keep Gmail. Dual-publish is leftover MX.
Anti-pattern: cut Monday because the CEO wanted it despite incomplete answers. Incomplete is a no-go.
Anti-pattern: cute leftover-MX attitude you ignored. Incident Friday. Next time you walk. Write that on the wall.
Anti-pattern: stale prices in the proposal. Re-check the live page at sign. Quote MailerZ from /pricing. Do not scrape 2023 blogs.
Practice: run the list on MailerZ too. Features, pricing, security. Qualification is not loyalty. Rehearse on one domain. Third mailbox. Both directions if you send.
Practice: agencies use the list to eliminate From-rewriters and leftover-MX shrugs the same week. Remaining vendor gets a rehearsal.
Practice: if they cannot explain envelope versus Header From, they cannot explain a 550. Pick docs that already speak RFC 5321 or hire help.
Practice: keep the answer sheet in the client folder. Compare live pages the day you buy. Blogs go stale. This article will not scrape competitor numbers.
Operator closeout for forwarding-provider questions
Write answers before anyone gets registrar access. Verbal they are fine is how From-rewriters and leftover-MX shrugs become production. Keep the sheet in the client folder. Re-read live pages the morning you sign. Blogs go stale. This article will not scrape competitor prices. MailerZ numbers live on /pricing.
If they rewrite Header From, walk. If they recommend a second vendor MX for safety, walk. If they sell an inboxing percentage, walk. If they cannot explain envelope versus Header From, they cannot explain a 550. You want SRS on the envelope and intact From. MailerZ does that. Open a received original in rehearsal. Trust headers.
Unknown local-parts: HOLD, reject, or FORWARD. Get it in writing. We catch everything is not a feature if the destination is Gmail. MailerZ Free holds. FORWARD is a paid choice with junk cost. Store clocks: ask the number. Fourteen or ninety here. No history means folklore incidents.
Send-as: dashboard copy or a blog port. MailerZ copies host, port, TLS or STARTTLS from the app. Free cannot send-as. Caps exist. Unlimited in a headline is usually a footnote. Lists need an ESP. Form SMTP is a separate ask: receivable From, rate limit, env, staging sink. Skip it and replies die.
Ask how you leave: export, revoke, MX delete, store clock. Offboard is a question, not a breakup novel. Ask whether they are IMAP. If you need a store, buy a host. Dual-publish is leftover MX. See /compare/google-workspace if the real alternative is a suite.
What they will not promise matters. MailerZ will not promise SOC 2, ISO, HIPAA, SLAs, or inboxing rates. /security is the questionnaire. Honesty is the enterprise-friendly move. Cute leftover-MX attitude is the tell. You want delete the old set, then probe. You do not want keep Google at 20.
Run the same list on MailerZ. Qualification is not loyalty. Features and pricing should match: exclusive MX, HOLD on Free, dashboard SMTP on paid, no badges. Rehearse on one domain. Third mailbox. Both directions if you send. Self-send is not the rehearsal. Incomplete answers are a no-go even if the CEO wants Monday.
Agencies eliminate From-rewriters and leftover-MX shrugs in the same week, then rehearse the remainder. Someone who cannot speak RFC 5321 is not your incident partner. Keep Message-IDs in the notes. Then cut production.
Price changes between proposal and sign. Re-check. Update the sheet. Do not treat a scraped 2023 number as a contract. Free MailerZ is ten aliases and no send-as. Write the numbers you were told next to the URL you opened.
If you ignored a cute leftover-MX answer and bought anyway, the Friday incident is on that tell. Next time walk. Write it on the wall. Point MX only after written answers and a rehearsal. Folklore is how domains split.
Handoff memo for the next operator
Vendor evaluations die in email threads. Distill the questions you asked, the answers you received, and the answers you never got into one memo. The next operator should see why you picked MailerZ or why you kept a mailbox host for a regulated workflow. "It felt fine" is not a reason a successor can defend.
Include the proof artifacts: a send-as screenshot, an SPF lookup, a rejection if you tested a From rewrite host, and the plan limits you accepted. Future procurement will ask the same questions. Answering twice from memory is how numbers drift.
Name the stakeholders who signed off: founder, counsel if any, and the person who pays. If counsel never saw the move, write that gap. Silence is not approval.
Finish with the review date. Forwarding that worked in 2026 can fail when a bank tightens From checks or when a plan limit bites. A memo without a review date is a eulogy for the decision, not a living control.
Acceptance criteria before you call it done
A vendor move is done when every question in this article has a written answer, when send-as and inbound proofs exist, and when the people who pay and the people who get sued have seen those proofs. A successful test from your laptop is not the same as an accepted move.
Confirm plan limits against real volume, not a guess. Confirm catch-all policy against real typo risk. Confirm From handling against a bank or vendor that already rejected rewritten mail if you tested a rewrite host. Guessing here is how you repeat the last migration.
Set the review date in the same calendar you use for domain renewal. If the move has no review, it will rot. MailerZ and every other host change quietly. Your questions should come back on a schedule.
FAQ
- What is the safest way to handle email forwarding provider questions?
- Ask whether they rewrite Header From, whether MX must be exclusive, what happens to unknown local-parts, how long hops are stored, how send-as is configured, and whether they publish an inboxing rate. Walk if they rewrite From or sell a folder guarantee.
- 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
- Ask From, MX, HOLD, store, SMTP, non-promises.
- Walk from From-rewriters and folder guarantees.
- Exclusive MX.
- Rehearse first.
- Quote live limits.
- No IMAP assumption.
- Leftover MX is a hard stop.
- Keep answers written.
Conclusion
Ask the questions. Write the answers. Then point MX. Folklore is how domains split.
Start free on MailerZ if the answers you want are intact From, exclusive MX, HOLD, and honest limits.