Reading an SMTP response without guessing means pasting the line, naming the hop, and acting on the class. A red Outlook toast is not 5.7.1. A green Gmail word is not 250. MailerZ history can show the conversation it spoke. It cannot translate a screenshot of an icon into a fix.
Quick answer for read smtp response
IETF RFC 5321 — Simple Mail Transfer Protocol defines reply classes. 2xx succeeded at this conversation. 4xx is temporary; retry. 5xx is permanent; stop. Enhanced status codes add a family (5.1.1 unknown recipient, 5.7.1 policy or auth, 4.2.2 mailbox full). The human text is still part of the evidence. Product path: troubleshooting and delivery recovery.
Name the hop. Sender to MailerZ is one conversation. MailerZ to Gmail is another. A 250 on the first and a 550 on the second is not a contradiction. Competitor posts on the ImprovMX blog (nofollow) often quote codes without hops. Quote them live. Dual-publishing their MX beside MailerZ still makes some replies belong to them.
Confirm MailerZ pricing when the line is 550 5.7.1 on send-as and you are on Free. Free receives. Solo is $40 per year. Starter is $8 or $80. Business is $19 or $190. Agency is $39 or $390. No plan turns a toast into a line. No plan is an inbox SLA.
Google’s people-first guidance is about pages; see creating helpful, reliable, people-first content. An SMTP article that only says “check spam” is guessing.
The user problem and the decision criteria
The ticket says mail failed. The evidence is an icon. The decision is whether you have a 4xx, a 5xx, a 250 plus empty inbox, or empty history. Those four jobs do not share a fix. Guessing 5.7.1 because Outlook was red is how you rotate passwords on an inbound leftover-MX outage.
| Question | If yes | If no |
|---|---|---|
| Can you paste the full history line? | Classify it. Then act. | You do not have a response yet. |
| Is history empty? | Leftover MX or missing offer. Not a 550. | Read the class on the line you have. |
| Is it 4xx? | Wait or fix the temp cause. Leave open. | If 5xx, fix then new probe. |
| Is it 250 and the inbox empty? | Folder or HOLD. Not a bounce. | If 250 and present, you are done with SMTP class. |
| Is the proof a client toast? | Open logs. Toasts compress the truth. | Good. Still name the hop. |
Technical mail flow
Each SMTP command can receive a reply. The line you care about for “did this hop take the message” is usually the 250 after DATA—or the 4xx/5xx that replaced it. Forwarding adds a second conversation. You must say which DATA you are quoting.
IETF RFC 7208 — Sender Policy Framework (SPF) and IETF RFC 7489 — Domain-based Message Authentication, Reporting, and Conformance (DMARC) results live in headers after accept. They are not SMTP reply codes. Mixing dmarc=fail into a 550 ticket is how you republish SPF during leftover MX.
Unhosted or unauthorized outbound SMTP is 550 5.7.1 from MailerZ. That line is precise. It is not “Gmail blocked us.” It is “this identity may not use this relay.” Paid plan, matching From, valid credentials. Different article from inbound 550 5.1.1 unknown recipient.
Self-send can skip public MX and invent a local success with no history line. Ban it as the only evidence. Probe from another provider. Unique subject. Paste history.
Step-by-step setup and decision path
Copy the full line
Code, enhanced status, text. Do not paraphrase into “it bounced.”
Name the hop and the envelope recipient
Inbound versus forward. hello@ versus sales@. Header To can lie.
Classify 2 / 4 / 5
Accept, retry, stop. Do not close 4xx as delivered. Do not loop 5xx.
If history is empty, leave codes
Two-resolver MX. Create the printed alias. Foreign probe. Docs.
If 250 and empty inbox, leave codes
Search folders and HOLD. Then recovery. Do not rotate SMTP.
Fix one cause, then new unique probe
Same message-id after a resend is a lie. New subject. New id.
Failure modes and proof
| What you see | Likely line | Next |
|---|---|---|
| Outlook red toast | Unknown until you copy history | Do not rotate passwords yet |
| 550 5.1.1 | Unknown recipient at that hop | Create the envelope name or stop catch-all folklore |
| 550 5.7.1 outbound | Unauthorized send-as | Plan, identity, credentials |
| 450 / 451 / 452 | Temporary | Wait, then re-read. Leave ticket open |
| 250 then nowhere | Accept, then store | Folder and HOLD, not bounce |
| No line | Hop never happened | Leftover MX or sender cache |
Proof is the pasted line plus hop name. Agencies collect this per destination. Client Gmail 250 and Client Outlook 5.7.1 are two tickets even if the founder sent one blast of tests.
MailerZ workflow and product boundary
MailerZ is inbound MX plus authenticated SMTP. Envelope SRS only. Header From never rewritten. History is the reply log for hops MailerZ spoke. It is not IMAP, not Workspace, not an open relay. Unhosted SMTP is 550 / 550 5.7.1.
HOLD stores unknown local-parts on Free. That may look like a missing bounce to the original sender if MailerZ accepted then held. Read policy. Free is one domain, ten aliases, 14-day store, send-as disabled, SMTP and API disabled. Solo is $40 per year: 5 domains, 25 aliases, 90-day store, 2,500 outgoing, five outgoing per hour, unknowns forwarded. Starter is $8 or $80. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm pricing. Limits are not an inbox SLA. No SOC 2 claim lives here.
Features describe routing. They do not decode a toast. Paid plans do not change RFC 5321 classes.
Cost, alternatives, and trade-offs
| Choice | What you get | What you give up |
|---|---|---|
| Pasted line plus hop | A real next action | The comfort of an icon |
| Guess 5.7.1 from a toast | Password theater | The leftover MX you never listed |
| Cron retry on 5xx | Noise and duplicates | A clean failure |
| Buy a suite to “see errors” | A store. Quote live | The Gmail archive you already have |
Time is a line item. One pasted history row costs less than another day of guessing. Leftover MX costs more than Solo. A Free-plan send-as 5.7.1 still costs more than the upgrade if send-as is the job.
The four parts of a reply
The three-digit code is the class. Receivers and senders must honor it. You can argue with the text. You cannot argue with a 5xx by retrying forever.
The enhanced status (x.y.z) is a finer family. 5.1.x is addressing. 5.7.x is policy and security. 4.2.x is mailbox state. If two vendors use the same 550 with different x.y.z, they are different jobs.
The text is the server’s dialect. “User unknown,” “Relay not permitted,” “Try again later” are not interchangeable. Copy them. Do not translate into “spam.”
The hop is who spoke. MailerZ inbound refuse, MailerZ outbound to Gmail, or leftover Google MX the sender still hits. Empty MailerZ history plus a bounce from ASPMX is a leftover-MX ticket with a perfectly readable line—from the wrong product.
Codes operators mix up
421 versus 450: both temporary, different flavors (service not available versus mailbox action). Leave both open. Do not call them delivered.
452 versus 552: storage. One may be temporary, one often permanent. Read the class digit first. Then the text.
551 versus 550 5.1.1: forwarding or user-not-local versus unknown. Do not create a catch-all FORWARD to hide a 5.1.1. HOLD on Free is the quieter unknown path.
554 can be policy or a generic permanent refuse. The text matters more than folklore that 554 means blacklist. Prove it.
Multiline replies start with a hyphen then a space on the last line. Copy all lines. Truncating to the first 550 loses the enhanced code.
What to paste on the ticket
Message-id, UTC window, envelope recipient, full history line, public MX from two resolvers, whether the probe was a self-send. Do not paste passwords. Do not paste a full customer invoice.
If those facts are missing, the ticket will bounce back as a request for the same screenshots. “It failed” is not a fact. The line is the fact.
After a 5xx fix, send a new unique probe. After a 4xx, wait and re-read the same id if the sender retried, or note the new id if they resent. Mixing ids is how you “fix” the wrong envelope.
If a second operator needs the same order without a call, send this page plus what delivered means and leftover MX. Line first. Hop second. Class third. DNS last unless history is empty. That order prevents rotating SMTP because Outlook was red.
Paid plans do not change how to read a line. Solo, Starter, Business, and Agency still use 2xx/4xx/5xx. The upgrade changes send-as and limits. It does not make a toast into history.
Legal hold is not the 14-day Free store. Two-factor on the destination Gmail is still required after the line looks clean. Registrar saves can republish leftover MX and change which product speaks the next 250. Re-query.
Night operators close on a guessed 5.7.1. Leave the ticket open with the pasted line or a written “no line, history empty.” Morning you will know whether to delete ASPMX or create sales@.
IPv6 versus IPv4 can produce different replies if one family is firewalled. History shows the family that connected. Do not guess “blacklist” because a dual-stack checker failed AAAA while IPv4 250’d.
TLS required versus opportunistic STARTTLS can 5xx with a policy text. That is not leftover MX. Fix TLS or the destination requirement. Do not call a TLS refuse a folder problem.
Open a held body for break-glass recovery and expect an audit row. That is a control, not a SOC 2 badge. Do not send zone or SMTP passwords to support. The artifacts that close a read smtp response ticket are a pasted line, a hop name, and one change that matches the class.
Pipelining and CHUNKING do not change how you read the final reply. They change batching. If a middlebox breaks the pipeline, you may see a disconnect with no clean 250 or 5xx. Capture the last bytes you got. Do not invent 5.7.1 to fill the gap.
DSN bounces after SRS return to MailerZ with a far-side line inside. That inner line is the destination’s reply, wrapped. Read both wrappers. The outer 250 to the original sender’s bounce-handler is not the inner 550 from Gmail. Name which paragraph you are quoting.
Plus-addressing can 5.1.1 at a destination that does not accept plus tags after MailerZ already 250’d inbound. Two hops, two lines. Create a plain alias the destination will take. Do not tell the original sender their inbound 250 means Gmail stored hello+stripe@.
Subdomains produce replies for the name that was offered. A 550 on pay.example.com is not a 550 on example.com. Query MX on the printed hostname before you “fix” the apex line you already like.
Shared screenshots hide multiline replies. Ask for the raw history export. If the reporter only has a phone crop of “550,” bounce the ticket. Three digits without text is how 5.1.1 and 5.7.1 get swapped and the wrong secret gets rotated.
Corporate gateways after Gmail can add a later refuse you will never see in MailerZ history. Your line stays 250 to Gmail. The gateway’s 5xx is a destination you do not operate. Say that. Do not republish SPF to please a journal.
Registrar included forwarding speaks its own dialect of 550. If leftovers remain, the sender’s bounce may quote the registrar, not MailerZ. That is useful. It proves which product they hit. Delete that MX. Do not debug the registrar’s wording as if it were yours.
Night CTA still belongs after a line you can paste. If you only receive, start free. If the line is 5.7.1 on send-as, Solo is the first paid rung. Do not buy Agency to decode a toast. Capacity is not a parser.
Field notes for reading an SMTP reply
The first digit is the job
A full SMTP response is a three-digit code plus text, sometimes plus an enhanced status like 5.7.1. The first digit decides the job. 2xx is success. 4xx is temporary. 5xx is permanent. Guessing from a red badge in a plugin is how you cut MX for a greylist and loop a 550. Read the line. Copy it into the ticket with a UTC timestamp and a Message-ID. Do not paste the SMTP password next to it.
Accepted, forwarded, and delivered are hop words, not synonyms for Primary. A 250 at MailerZ means this layer took the envelope. A 250 at the destination means the dest store accepted. A spam folder is still delivered. Empty history means hop one never ran — leftover MX or a missing alias — not a mysterious 550.
Enhanced codes refine, they do not replace the class
5.7.1 is authorization or policy. 4.2.1 is often greylist or congestion. 5.1.1 is often no such user. Still start with 4 versus 5. Then read the text the dest actually sent. Do not map every 550 to “spam.” Mailbox full can be 452 or 552 depending on the dest. AUTH failure is hop zero and may not have a dest class at all.
Inbound versus outbound are different tickets. Destination 421 after MailerZ accepted is dest deferral. Outbound 550 5.7.1 on send-as is plan or From. Free has no send-as. Catch-all does not mint a From.
What you may not infer
You may not infer inbox placement from a 250. You may not infer leftover MX from a 421. You may not infer a Gmail folder from a MailerZ history row. Search all mail. Query public MX. Then talk. Self-send from the same Gmail hides the public path and is not a response you can show a customer.
MailerZ is inbound MX plus authenticated SMTP from Secuno LLC. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME are never rewritten. Not Google Workspace, not IMAP or POP, not an open relay. Unauthorized send is SMTP 550 / 550 5.7.1. Leftover MX is a hard stop. Self-send from Gmail to the same Gmail account can hide routing errors. Not SOC 2, not ISO 27001, not HIPAA. MailerZ Free is one domain, ten aliases, one seat, a 14-day store, send-as disabled, SMTP and API disabled, and unrouted mail held or rejected only. Solo is $40 per year only. Starter is $8 monthly or $80 yearly. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm numbers on the pricing page. Limits are not an inbox-placement promise.
Worked story
Support swore mail failed. The plugin showed a red badge. History showed destination 250. The copy was in Promotions. They searched all mail. The response was honest. The folder was not a status.
A second ticket treated 421 as leftover MX and added Google hosts. Preference favored Google. MailerZ went quiet. They deleted Google, waited, and the third attempt 250’d. The 421 was temporary. The leftover was the outage.
Close criteria
Copy the numeric code and enhanced status. Classify 2 / 4 / 5. Decide inbound versus outbound. If 4xx, wait or retry inside the store window. If 5xx, fix the cause. If empty history, check leftover MX and the named alias first. New unique subject after a fix. Related: 421 article, 450 versus 451 versus 452, accepted versus forwarded versus delivered, delivery recovery. Start free, prove inbound, upgrade when From must travel.
Operator packet for an SMTP reply ticket
Paste the line, not the feeling
Numeric code, enhanced status, dest text, UTC time, Message-ID, inbound or outbound, unique subject. No password. A red badge is not a line. Empty history is not a 550. Classify 2 / 4 / 5 before anyone touches MX.
Actions that match the class
2xx plus missing Primary: search all mail. 4xx: wait or backoff, do not dual MX. 5xx: fix From, dest, or plan. AUTH fail: fix the trio. Leftover MX: delete leftovers. New unique subject after a fix. Fourteen-day Free window, ninety on paid. Caps and windows are not inbox SLAs.
Who owns the next hop
MailerZ 250 then dest 421 is dest deferral. MailerZ 550 5.7.1 is authorization. Leftover Google 250 and empty MailerZ history is leftover MX. Do not mix those sentences in Slack. Related 421 and 450 articles exist. Start free, prove inbound, upgrade when From must travel.
Done
Line copied. Class named. Action matches class. Probe with a new subject. MX only changes if leftovers exist. Not a folder war. Not a DKIM first guess.
Definition of done
A full SMTP response is evidence. A badge is not. Copy the line. Classify 2, 4, or 5. Search dest including spam on a 250. Wait on 4xx. Fix the cause on 5xx. Empty history is leftover MX or a missing alias. Self-send is not a line you can show a customer. Fourteen-day Free store, ninety on paid. Confirm pricing. Start free, prove inbound, upgrade when From must travel.
Agencies isolate inbound versus outbound tickets so a dest 421 does not become a leftover-MX change on the wrong zone. New unique subject after every fix. Do not paste passwords next to the code. Delivery recovery is hops this layer saw, not Primary, not Vault.
Proof you can keep
A reply you can show a customer
Subject, UTC, code, enhanced status, dest text, Message-ID, inbound or outbound, public MX listing, history empty or not. That packet settles arguments. “It failed” does not. If the code is 250 and they still cannot find the copy, you walk them through all mail and spam. If the code is 421, you say temporary and you do not add leftover MX. If history is empty, you show leftover Google hosts. MailerZ editorial at Secuno LLC will not invent an inbox SLA to make the packet prettier.
Agencies keep this packet per zone. Client A’s 250 does not explain client B’s empty history. Isolate outbound tickets from inbound tickets. New unique subject after every change. Fourteen or ninety days bound what this hop still holds. Confirm pricing. Start free. Upgrade when From must travel.
FAQ
What is the safest way to handle read smtp response?
Copy the full line from MailerZ history: reply code, enhanced status, text, and which hop spoke. Classify 2xx, 4xx, 5xx before you change DNS. Empty history is not a code. Do not guess from a Gmail or Outlook toast.
Does this require a new mailbox?
No. Reading a reply is evidence work. Gmail or Outlook can stay the store. MailerZ is not IMAP. Buy hosting only if you need folders on the domain instead of Gmail.
Will it work with Gmail or Outlook?
Both hide the SMTP line behind a toast. Open original or the sending logs. MailerZ history is the hop you operate. Free has no send-as. A 550 5.7.1 on outbound is authorization, not leftover MX.
What DNS records are involved?
Exclusive MX so the hop you are reading is yours. Leftover MX means some replies came from Google or Microsoft. SPF and DMARC are not SMTP reply codes. They appear later in Authentication-Results.
What should I test before production?
A uniquely titled third-mailbox probe, two-resolver MX, a pasted history line you can read out loud, and a new probe after any 5xx fix. Do not loop a cron at a 550. Do not close a 4xx as delivered.
Key takeaways
- Read smtp response: paste the full line, name the hop, honor the class.
- 2xx accept. 4xx retry. 5xx stop. Enhanced codes refine; they do not replace the class.
- A toast is not a line. Empty history is leftover MX or a missed offer.
- 250 plus empty inbox is a folder or HOLD ticket, not a bounce.
- 550 5.7.1 outbound is authorization. 550 5.1.1 is unknown recipient.
- New unique probe after a 5xx fix. Do not loop a cron.
- Free receives. Solo $40/yr starts send-as. Confirm /pricing.
- Envelope SRS only. Not IMAP, not an inbox SLA, not SOC 2.
Conclusion and next action
If mail failed, stop guessing from icons. Copy the SMTP line. Name the hop. Classify 2, 4, or 5. MailerZ can show the conversation it spoke. It cannot invent a log for leftover Google MX or turn a toast into 5.7.1. Start free on one domain and paste a real history row before you change a second setting.
Ready to quote the line
Start free with one domain and history you can paste.
Inbound on Free. Solo when send-as is the job. Sign in if the domain is already there.
Review quarterly, or sooner if MailerZ history labels or destination toast copy change. Author: MailerZ editorial, Secuno LLC.