Multi-Domain SMTP Sending Without Running Your Own Mail Cluster

Quick answer for multi domain smtp sending

A cluster gives you unlimited ways to become an open relay. Caps are a feature.

Each domain still needs exclusive inbound MX if you also receive. SMTP does not replace MX.

ESP versus MailerZ: volume and marketing features versus operational send-as. Read 2,500/5,000/12,000/20,000 outgoing.

Free cannot participate. Stop workshopping postfix because you are on Free.

Authoritative mail transport is still IETF RFC 5321 — Simple Mail Transfer Protocol. features. migration planner. delivery recovery.

The real decision

Developers enjoy running mailers. Founders enjoy sleeping.

Decision: operational mail versus campaigns. Campaigns leave.

One SPF include pile across ten domains copied badly causes permerror on all ten.

A suite send connector per tenant is an MSP 365 motion, not this hop.

When this path is enough

• You can staff exclusive MX and named aliases.
• You will keep Header From intact.
• You can probe from another mailbox.

When this is the wrong ticket

• History is empty and leftovers remain.
• You want an inbox placement SLA.
• You plan to rewrite visible From.

Technical mail flow

App or Outlook AUTH → From must be an identity on that domain → sign → dest.

Wrong domain From 550 even if AUTH is a seat that can see the account.

Rotate secrets per 216. Do not run a cluster just to rotate.

Inbound leftovers still drop replies people think are “SMTP issues.”

Step-by-step decision path

1. Inventory leftovers. Screenshot current MX, SPF, DKIM, NS.
2. Verify the domain. TXT as the dashboard states.
3. Create named aliases first. Do not cut MX onto empty maps.
4. Publish one MX set. Delete Google, Microsoft, registrar leftovers.
5. Prove from another mailbox. Unique subject. Header From intact.
6. Only then send-as if paid. Dashboard SPF/DKIM. Outbound probe.
7. Store the proof packet. MX, hop, headers, plan name.

Worked examples

Agency postfix got listed. They moved operational mail to MailerZ and campaigns to an ESP.

Ten domains, one copied SPF with twelve includes. Permerror city. Diet per zone.

They sent campaign blasts on Agency 20,000/month. Wrong product. ESP.

Identity for client A used on client B From. 550. Correct.

VPS mailer had no hop store. Debugging was SSH folklore. History was the upgrade.

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: pricing. Free $0, 1 domain, 10 aliases, 1 seat, 14-day store, send-as disabled, SMTP and API disabled. Solo $40/year, 5 domains, 25 aliases, 90-day, 2,500 outgoing, 20/hour. 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.

Cost, alternatives, and trade-offs

Field notes

Related: /features, /migration-planner, /delivery-recovery, /pricing.

Do not publish the SMTP password in Ansible git.

Watch 60/hour if many domains share a burst.

No inbox SLA for any domain.

Search demand for multi domain smtp sending usually arrives as a screenshot, not a sentence. Ask for the received copy, the public MX set, and the plan name before you change a record. Multi-Domain SMTP Sending Without Running Your Own Mail Cluster is a workflow, not a checkbox.

Write a one-paragraph policy the team can reuse for multi domain smtp sending. Name the hop (inbound versus outbound), the proof artifact, and the thing you will not do (dual MX, From rewrite, second SPF record). Put the paragraph in the ticket template.

Change control matters more than a clever record. One person owns DNS for this domain. Adding an include, a selector, or a backup MX requires a ticket. Most regressions in multi domain smtp sending are Friday edits without a probe.

Self-send remains invalid for multi domain smtp sending. Gmail can short-circuit. Outlook can look local. Use a mailbox on another provider and a unique subject. If the customer refuses, the ticket stays open.

Leftover MX masquerades as every authentication and spam incident. If history is empty, multi domain smtp sending is the wrong title until two resolvers agree on one product. Delete aspmx, Microsoft, and registrar MX. Wait TTL.

Free HOLD and missing aliases masquerade as outages. History shows the hold. Create the named local-part or accept that unknowns stay. Catch-all FORWARD is paid, optional, and a spam trade-off — not a debugger for multi domain smtp sending.

Paid send-as is a different hop from inbound multi domain smtp sending. Free cannot send. Unauthorized From is 550 / 550 5.7.1. Publishing prettier DNS will not authorize a From the product has not approved.

Destination filters still win after a clean hop. Multi-Domain SMTP Sending Without Running Your Own Mail Cluster does not include an inbox placement SLA, review counts, or a Primary guarantee. Say that once, early, so the customer stops buying a story you cannot ship.

Proof packet for multi domain smtp sending: public MX from two resolvers, inbound received copy with Header From, Authentication-Results, outbound received copy if they send, plan name, and the SMTP line if anything refused. That packet ends folklore.

Retention is 14 days on Free and 90 on paid. Export headers while they live. multi domain smtp sending arguments without artifacts become myths. The destination inbox is the archive, not the hop store.

Agencies should not blend clients in one multi domain smtp sending thread. One domain, one matrix, one MX screenshot. Agency plan limits are 100 domains, 500 aliases, 50 seats, 20,000 outgoing, 60/hour — still not unlimited, still not an SLA.

Security hygiene: no SMTP passwords in the multi domain smtp sending ticket, no message bodies in chat, no invented SOC 2. Controls live on the Security and Trust Center. Secrets rotate if they leaked.

Related operations stay on real routes: forwarding, send-as, troubleshooting, tools, delivery recovery, docs, pricing. Do not invent a pillar. If multi domain smtp sending is actually leftover MX, say leftover MX.

Refresh cadence is at least quarterly, sooner after a domain transfer, panel change, ESP trial, or dashboard host change. Multi-Domain SMTP Sending Without Running Your Own Mail Cluster goes stale when the zone changes and the runbook does not.

If two products still share MX after you explained the coin flip, stop adding records. Exclusive MX is a hard stop. multi domain smtp sending cannot be correct on a split path.

If Header From is already rewritten, stop tuning SPF for multi domain smtp sending. Change the hop. MailerZ will not offer a From-replace control. Honest identity is the product.

If the customer wants a suite, sell the suite as Calendar and a hosted mailbox, not as a magic fix for multi domain smtp sending. Workspace and Microsoft 365 are different architectures with their own filters and their own 550s.

Hourly and monthly send-as ceilings (disabled/2,500/5,000/12,000/20,000 outgoing; 20/40/60/60 per hour by plan) produce refuses that look like multi domain smtp sending outages. Read counters before you republish DKIM.

Null MX plus a real MX is another lie. Remove the lone-dot refuse if you intend to receive. Empty inbound plus a pretty multi domain smtp sending essay is still a refuse-all.

After you change anything, wait TTL, probe from another mailbox, and store the new received source next to the MX screenshot. Multi-Domain SMTP Sending Without Running Your Own Mail Cluster is done when proof exists, not when the panel is green.

Field story 1 for multi domain smtp sending: Agency postfix got listed. They moved operational mail to MailerZ and campaigns to an ESP. Keep that story in the runbook so the next person does not reopen Multi-Domain SMTP Sending Without Running Your Own Mail Cluster from zero.

Field story 2 for multi domain smtp sending: Ten domains, one copied SPF with twelve includes. Permerror city. Diet per zone. Keep that story in the runbook so the next person does not reopen Multi-Domain SMTP Sending Without Running Your Own Mail Cluster from zero.

Field story 3 for multi domain smtp sending: They sent campaign blasts on Agency 20,000/month. Wrong product. ESP. Keep that story in the runbook so the next person does not reopen Multi-Domain SMTP Sending Without Running Your Own Mail Cluster from zero.

Field story 4 for multi domain smtp sending: Identity for client A used on client B From. 550. Correct. Keep that story in the runbook so the next person does not reopen Multi-Domain SMTP Sending Without Running Your Own Mail Cluster from zero.

Field story 5 for multi domain smtp sending: VPS mailer had no hop store. Debugging was SSH folklore. History was the upgrade. Keep that story in the runbook so the next person does not reopen Multi-Domain SMTP Sending Without Running Your Own Mail Cluster from zero.

For multi domain smtp sending, symptom “Empty history” usually means Leftover or cached MX. Isolate it with Two resolvers. Do not stack a second change until that proof exists.

For multi domain smtp sending, symptom “Unknowns missing” usually means Free HOLD. Isolate it with History hold. Do not stack a second change until that proof exists.

For multi domain smtp sending, symptom “Header From rewritten” usually means Wrong hop. Isolate it with Received From. Do not stack a second change until that proof exists.

For multi domain smtp sending, symptom “SMTP 550 send-as” usually means Free or unauthorized From. Isolate it with History line. Do not stack a second change until that proof exists.

For multi domain smtp sending, symptom “spf=fail hop two” usually means Naive envelope. Isolate it with Return-Path. Do not stack a second change until that proof exists.

For multi domain smtp sending, symptom “Still spam after clean hop” usually means Destination filters. Isolate it with Not an SLA. Do not stack a second change until that proof exists.

For multi domain smtp sending, symptom “Self-send clean” usually means Short-circuit. Isolate it with Other mailbox. Do not stack a second change until that proof exists.

For multi domain smtp sending, symptom “Wrong DNS panel” usually means NS ≠ registrar UI. Isolate it with NS lookup. Do not stack a second change until that proof exists.

Setup step “Inventory leftovers.” for multi domain smtp sending: Screenshot current MX, SPF, DKIM, NS. Skip it and Multi-Domain SMTP Sending Without Running Your Own Mail Cluster turns into a second ticket next week. Do the step, store the artifact, then continue.

Setup step “Verify the domain.” for multi domain smtp sending: TXT as the dashboard states. Skip it and Multi-Domain SMTP Sending Without Running Your Own Mail Cluster turns into a second ticket next week. Do the step, store the artifact, then continue.

Setup step “Create named aliases first.” for multi domain smtp sending: Do not cut MX onto empty maps. Skip it and Multi-Domain SMTP Sending Without Running Your Own Mail Cluster turns into a second ticket next week. Do the step, store the artifact, then continue.

Setup step “Publish one MX set.” for multi domain smtp sending: Delete Google, Microsoft, registrar leftovers. Skip it and Multi-Domain SMTP Sending Without Running Your Own Mail Cluster turns into a second ticket next week. Do the step, store the artifact, then continue.

Setup step “Prove from another mailbox.” for multi domain smtp sending: Unique subject. Header From intact. Skip it and Multi-Domain SMTP Sending Without Running Your Own Mail Cluster turns into a second ticket next week. Do the step, store the artifact, then continue.

Setup step “Only then send-as if paid.” for multi domain smtp sending: Dashboard SPF/DKIM. Outbound probe. Skip it and Multi-Domain SMTP Sending Without Running Your Own Mail Cluster turns into a second ticket next week. Do the step, store the artifact, then continue.

Setup step “Store the proof packet.” for multi domain smtp sending: MX, hop, headers, plan name. Skip it and Multi-Domain SMTP Sending Without Running Your Own Mail Cluster turns into a second ticket next week. Do the step, store the artifact, then continue.

Trade-off on multi domain smtp sending: choosing Exclusive MX + named aliases gets you Debuggable path and gives up You must delete leftovers. Write that exchange on the quote so nobody pretends it is free.

Trade-off on multi domain smtp sending: choosing Dual MX backup gets you Feels safe and gives up Coin-flip misses. Write that exchange on the quote so nobody pretends it is free.

Trade-off on multi domain smtp sending: choosing From rewrite gets you Cosmetic SPF and gives up Trust and DKIM. Write that exchange on the quote so nobody pretends it is free.

Trade-off on multi domain smtp sending: choosing Suite seats gets you Hosted mailbox and gives up Per-user price. Write that exchange on the quote so nobody pretends it is free.

Multi-Domain SMTP Sending Without Running Your Own Mail Cluster is enough when You can staff exclusive MX and named aliases. If that condition is false, stop implementing multi domain smtp sending and reopen the decision.

Multi-Domain SMTP Sending Without Running Your Own Mail Cluster is enough when You will keep Header From intact. If that condition is false, stop implementing multi domain smtp sending and reopen the decision.

Multi-Domain SMTP Sending Without Running Your Own Mail Cluster is enough when You can probe from another mailbox. If that condition is false, stop implementing multi domain smtp sending and reopen the decision.

Multi-Domain SMTP Sending Without Running Your Own Mail Cluster is the wrong ticket when History is empty and leftovers remain. Name the correct system instead of forcing multi domain smtp sending to cover it.

Multi-Domain SMTP Sending Without Running Your Own Mail Cluster is the wrong ticket when You want an inbox placement SLA. Name the correct system instead of forcing multi domain smtp sending to cover it.

Multi-Domain SMTP Sending Without Running Your Own Mail Cluster is the wrong ticket when You plan to rewrite visible From. Name the correct system instead of forcing multi domain smtp sending to cover it.

Write multi domain smtp sending in the subject line of the ticket and the layer in the first sentence. If the layer is leftover MX, say leftover MX. If the layer is HOLD, say HOLD. If the layer is a destination 550, paste the text. Multi-Domain SMTP Sending Without Running Your Own Mail Cluster stays short when the first sentence is honest.

Keep a standing calendar note for multi domain smtp sending: monthly external probe, leftover MX lookup, and a glance at send-as counters if you are paid. Five minutes. The outage you avoid is the Friday dual-MX restore.

When two vendors disagree about multi domain smtp sending, believe artifacts: two resolvers, one received copy, one history row. Do not believe the prettier admin center. Registrar dots lie. Composer UIs lie. Self-send lies.

Teach the next hire the MailerZ split before they touch multi domain smtp sending: envelope may change, Header From must not, Free cannot send, unknowns HOLD, leftover MX is a hard stop, no inbox SLA, no SOC 2 sticker. That speech prevents a class of tickets.

If multi domain smtp sending appears in an RFP, answer with published caps and hop evidence. Decline inbox-rate clauses. Decline fake certifications. Point at pricing and the Security and Trust Center. Multi-Domain SMTP Sending Without Running Your Own Mail Cluster is not a place to invent enterprise theater.

Export while the 14- or 90-day window still has the multi domain smtp sending hop. Future-you will not remember the SMTP sentence. The destination mailbox remains the archive. We will not grow the store because a blog asked.

Do not bundle unrelated edits with multi domain smtp sending. Rotating SMTP while republishing MX while enabling FORWARD is how you lose the ability to name the failure. One change, one probe, one stored copy.

If you need a suite, buy a suite for Calendar and a hosted mailbox. If you need a hop, buy a hop. Multi-Domain SMTP Sending Without Running Your Own Mail Cluster does not become Exchange because a quote stacked seats next to aliases.

FAQ

Key takeaways

• Exclusive MX is a hard stop.
• Header From stays the original sender.
• SRS is envelope-only.
• Free holds unknowns and cannot send-as.
• 550 means read the text.
• Self-send lies.
• No inbox SLA.
• 14- or 90-day store is not an archive.
• MailerZ is not IMAP.
• No SOC 2, ISO, or HIPAA claims.

Conclusion and next action

You do not need a cluster to send as ten domains at operational volume.

Next action: count monthly sends, pick a plan, publish per-domain DKIM, probe each From.

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