SMTP Authentication Works but Mail Still Does Not Arrive

Quick answer for smtp auth works mail not delivered

SMTP AUTH is a session. MAIL FROM / Header From is an authorization. MailerZ accepts credentials and still returns 550 5.7.1 when the identity is unhosted or unauthorized.

Inbound confirmations for Gmail Send mail as travel a different path. Leftover MX drops those confirms. AUTH in Outlook looks fine. The identity never verifies.

Destination 550 after we accepted the message is their refuse. History will show it. AUTH remains green. The mailbox owner must read that text.

Hourly caps refuse after a burst. AUTH still works. Counters explain the 550. Solo is 5/hour. Do not call that a DNS outage.

Authoritative mail transport is still IETF RFC 5321 — Simple Mail Transfer Protocol. troubleshooting. delivery recovery. tools.

The real decision

Helpdesks reset passwords when the password already worked. That wastes MFA time and misses the From.

Decision: did we accept the DATA? If no, read our 550. If yes, read the destination’s. If there is no outbound history, you never submitted to us.

php mail and “sendmail” bypass AUTH entirely. The customer says SMTP works because a leftover test succeeded last month.

A suite SMTP will AUTH to Outlook and still not use MailerZ. Name the host in the client.

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

Client connects, AUTHs, presents From. We check plan and identity. Then we relay. Failures after AUTH are the usual mystery.

Gmail confirmation inbound still needs exclusive MX. Mixed MX makes AUTH look done and confirm never arrive.

Self-send from the same Gmail can look delivered without our hop. Invalid.

DKIM signs only after we accept. Unpublished DKIM is a later layer, not an AUTH bug.

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

Outlook AUTH green, From was the personal Microsoft account. 550 5.7.1. Switching From to hello@ on a paid plan delivered.

WordPress SMTP test passed. Production used php mail. Customers never saw MailerZ signatures. Host field was ignored by the plugin’s fallback.

Gmail Send mail as AUTH saved. Confirm never arrived. aspmx leftover. After delete, confirm landed, send-as completed.

Starter hit 10/hour during a launch email. AUTH fine. Later messages 550. They queued.

Destination 550 mailbox full on the accountant. AUTH and our accept were fine. They freed the mailbox.

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, webmail, or Calendar.
• 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, 3 aliases, 1 seat, 14-day store, send-as disabled, SMTP and API disabled. Solo $40/year, 3 domains, 15 aliases, 90-day, 1,000 outgoing, 5/hour. Starter $8 or $80, 5/50/5, 2,000, 10/hour. Business $19 or $190, 25/200/25, 4,000, 15/hour. Agency $39 or $390, 100/500/50, 8,000, 25/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

Log the AUTH user and the From separately. They are allowed to differ only when the product says so — here they must match an approved identity.

Related: /send-reply, /docs, /troubleshooting, /delivery-recovery.

Do not paste passwords into the AUTH-works ticket.

If the client host is wrong, AUTH may succeed against someone else entirely. Screenshot the host.

Search demand for smtp auth works mail not delivered 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. SMTP Authentication Works but Mail Still Does Not Arrive is a workflow, not a checkbox.

Write a one-paragraph policy the team can reuse for smtp auth works mail not delivered. 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 smtp auth works mail not delivered are Friday edits without a probe.

Self-send remains invalid for smtp auth works mail not delivered. 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, smtp auth works mail not delivered 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 smtp auth works mail not delivered.

Paid send-as is a different hop from inbound smtp auth works mail not delivered. 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. SMTP Authentication Works but Mail Still Does Not Arrive 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 smtp auth works mail not delivered: 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. smtp auth works mail not delivered arguments without artifacts become myths. The destination inbox is the archive, not the hop store.

Agencies should not blend clients in one smtp auth works mail not delivered thread. One domain, one matrix, one MX screenshot. Agency plan limits are 100 domains, 500 aliases, 50 seats, 8,000 outgoing, 25/hour — still not unlimited, still not an SLA.

Security hygiene: no SMTP passwords in the smtp auth works mail not delivered 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 smtp auth works mail not delivered 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. SMTP Authentication Works but Mail Still Does Not Arrive 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. smtp auth works mail not delivered cannot be correct on a split path.

If Header From is already rewritten, stop tuning SPF for smtp auth works mail not delivered. 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 smtp auth works mail not delivered. Workspace and Microsoft 365 are different architectures with their own filters and their own 550s.

Hourly and monthly send-as ceilings (disabled/1,000/2,000/4,000/8,000 outgoing; 5/10/15/25 per hour by plan) produce refuses that look like smtp auth works mail not delivered 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 smtp auth works mail not delivered 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. SMTP Authentication Works but Mail Still Does Not Arrive is done when proof exists, not when the panel is green.

Field story 1 for smtp auth works mail not delivered: Outlook AUTH green, From was the personal Microsoft account. 550 5.7.1. Switching From to hello@ on a paid plan delivered. Keep that story in the runbook so the next person does not reopen SMTP Authentication Works but Mail Still Does Not Arrive from zero.

Field story 2 for smtp auth works mail not delivered: WordPress SMTP test passed. Production used php mail. Customers never saw MailerZ signatures. Host field was ignored by the plugin’s fallback. Keep that story in the runbook so the next person does not reopen SMTP Authentication Works but Mail Still Does Not Arrive from zero.

Field story 3 for smtp auth works mail not delivered: Gmail Send mail as AUTH saved. Confirm never arrived. aspmx leftover. After delete, confirm landed, send-as completed. Keep that story in the runbook so the next person does not reopen SMTP Authentication Works but Mail Still Does Not Arrive from zero.

Field story 4 for smtp auth works mail not delivered: Starter hit 10/hour during a launch email. AUTH fine. Later messages 550. They queued. Keep that story in the runbook so the next person does not reopen SMTP Authentication Works but Mail Still Does Not Arrive from zero.

Field story 5 for smtp auth works mail not delivered: Destination 550 mailbox full on the accountant. AUTH and our accept were fine. They freed the mailbox. Keep that story in the runbook so the next person does not reopen SMTP Authentication Works but Mail Still Does Not Arrive from zero.

For smtp auth works mail not delivered, 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 smtp auth works mail not delivered, symptom “Unknowns missing” usually means Free HOLD. Isolate it with History hold. Do not stack a second change until that proof exists.

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

For smtp auth works mail not delivered, 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 smtp auth works mail not delivered, 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 smtp auth works mail not delivered, 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 smtp auth works mail not delivered, symptom “Self-send clean” usually means Short-circuit. Isolate it with Other mailbox. Do not stack a second change until that proof exists.

For smtp auth works mail not delivered, 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 smtp auth works mail not delivered: Screenshot current MX, SPF, DKIM, NS. Skip it and SMTP Authentication Works but Mail Still Does Not Arrive turns into a second ticket next week. Do the step, store the artifact, then continue.

Setup step “Verify the domain.” for smtp auth works mail not delivered: TXT as the dashboard states. Skip it and SMTP Authentication Works but Mail Still Does Not Arrive turns into a second ticket next week. Do the step, store the artifact, then continue.

Setup step “Create named aliases first.” for smtp auth works mail not delivered: Do not cut MX onto empty maps. Skip it and SMTP Authentication Works but Mail Still Does Not Arrive turns into a second ticket next week. Do the step, store the artifact, then continue.

Setup step “Publish one MX set.” for smtp auth works mail not delivered: Delete Google, Microsoft, registrar leftovers. Skip it and SMTP Authentication Works but Mail Still Does Not Arrive turns into a second ticket next week. Do the step, store the artifact, then continue.

Setup step “Prove from another mailbox.” for smtp auth works mail not delivered: Unique subject. Header From intact. Skip it and SMTP Authentication Works but Mail Still Does Not Arrive turns into a second ticket next week. Do the step, store the artifact, then continue.

Setup step “Only then send-as if paid.” for smtp auth works mail not delivered: Dashboard SPF/DKIM. Outbound probe. Skip it and SMTP Authentication Works but Mail Still Does Not Arrive turns into a second ticket next week. Do the step, store the artifact, then continue.

Setup step “Store the proof packet.” for smtp auth works mail not delivered: MX, hop, headers, plan name. Skip it and SMTP Authentication Works but Mail Still Does Not Arrive turns into a second ticket next week. Do the step, store the artifact, then continue.

Trade-off on smtp auth works mail not delivered: 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 smtp auth works mail not delivered: 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 smtp auth works mail not delivered: 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 smtp auth works mail not delivered: 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.

SMTP Authentication Works but Mail Still Does Not Arrive is enough when You can staff exclusive MX and named aliases. If that condition is false, stop implementing smtp auth works mail not delivered and reopen the decision.

SMTP Authentication Works but Mail Still Does Not Arrive is enough when You will keep Header From intact. If that condition is false, stop implementing smtp auth works mail not delivered and reopen the decision.

SMTP Authentication Works but Mail Still Does Not Arrive is enough when You can probe from another mailbox. If that condition is false, stop implementing smtp auth works mail not delivered and reopen the decision.

SMTP Authentication Works but Mail Still Does Not Arrive is the wrong ticket when History is empty and leftovers remain. Name the correct system instead of forcing smtp auth works mail not delivered to cover it.

SMTP Authentication Works but Mail Still Does Not Arrive is the wrong ticket when You want an inbox placement SLA. Name the correct system instead of forcing smtp auth works mail not delivered to cover it.

SMTP Authentication Works but Mail Still Does Not Arrive is the wrong ticket when You plan to rewrite visible From. Name the correct system instead of forcing smtp auth works mail not delivered to cover it.

Write smtp auth works mail not delivered 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. SMTP Authentication Works but Mail Still Does Not Arrive stays short when the first sentence is honest.

Keep a standing calendar note for smtp auth works mail not delivered: 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 smtp auth works mail not delivered, 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 smtp auth works mail not delivered: 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 smtp auth works mail not delivered 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. SMTP Authentication Works but Mail Still Does Not Arrive is not a place to invent enterprise theater.

Export while the 14- or 90-day window still has the smtp auth works mail not delivered 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 smtp auth works mail not delivered. 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. SMTP Authentication Works but Mail Still Does Not Arrive 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

If AUTH works and mail does not arrive, you finished the easy step. Read the next SMTP sentence.

Next action: open history for the submission after AUTH and classify 550, cap, leftover confirm, or destination refuse.

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