Accepted vs forwarded vs delivered: email statuses explained

Quick answer for email delivery statuses accepted forwarded delivered

Read MailerZ history as accepted and forwarded hops this layer saw. Read the destination including spam as delivered-or-classified. That is email delivery statuses accepted forwarded delivered.

Guide: empty history is hop one. Setup: exclusive MX, named alias, unique subject. Best practice: do not collapse three words into “it bounced.”

Delivery recovery stores hops this layer saw. Leftover misses are not there.

Send-as 550 is hop five, not inbound delivered.

MailerZ Free is one domain, three 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 MailerZ pricing. Limits are not an inbox-placement promise.

Google’s own Send mail as steps live in Google Gmail Help — Send mail from a different address. Workspace as a product is described on Google Workspace — product overview. Transport still follows IETF RFC 5321 — Simple Mail Transfer Protocol.

email delivery statuses accepted forwarded delivered guide: the real decision

Called spam a failed forward.

Recreated aliases because history was empty — leftover MX.

Mixed form 550 into inbound status.

Criteria: unique subject, history row, dest search, named hop.

Technical mail flow for email delivery statuses accepted forwarded delivered

Lookup, accept, map, second SMTP, dest reply or classify.

Two dests can mix 250 and 5xx.

Header From stays. SRS may rewrite the envelope.

Hold is not accepted-to-dest. It is policy.

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, not webmail, 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.

email delivery statuses accepted forwarded delivered setup

Write a unique subject. Then look up MX. Then read history. Then search the dest.

1. Exclusive MX. Two views.
2. Named alias exists.
3. Send unique subject from another mailbox.
4. Read accepted / forwarded in history.
5. Search dest including spam.
6. If empty history, leftover or unnamed — not a dest reject.
7. If 5xx from dest, fix store quota or policy.
8. New subject after any fix.

Failure modes and proof

Self-send.

No unique subject.

Spam called bounce.

Empty history called Gmail reject.

550 send-as mixed in.

MailerZ workflow and product boundary

Related: delivery recovery, troubleshooting, docs, features.

14/90 day store is hops, not Vault.

Related pages: delivery recovery, troubleshooting, docs, and features.

email delivery statuses accepted forwarded delivered best practice

Observability is included in the hop. It is not an inbox SLA. Confirm /pricing.

Competitor blogs — nofollow.

MailerZ Free is one domain, three 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 MailerZ pricing. Limits are not an inbox-placement promise.

Field notes you can reuse

Deferral vs permanent is the companion.

Rejection diagnosis is hop naming.

Agencies: two dests need two dest searches.

SOC 2 is still no.

Do not invent “delivered to Primary.”

Hold unknowns separately.

RFC 5321 250 is accept, not happiness.

Quarterly leftover review.

Deeper field notes for email delivery statuses accepted forwarded delivered

250 is a hop, not a mood

Email delivery statuses accepted forwarded delivered collapse in tickets as “it bounced.” SMTP 250 at MailerZ means this layer accepted. Forwarded means we attempted the dest session. The dest may 250 and file spam. That is delivered-to-the-store, not delivered-to-Primary. We do not promise Primary. We do not sell an inbox SLA. Confirm /pricing.

Empty history means hop one never ran or the alias was unnamed/held. Asking recovery to fetch a leftover miss is asking for a log that does not exist. Collect timestamp, unique subject, public MX. Do not mail passwords.

Two dests and mixed status

One dest 250, one dest 5xx. History can look mixed. Probe both stores. Fix quota. New subject. Do not delete the alias because one dest was full. Hold is not forwarded. It is policy on unknowns.

Outbound 550 is not inbound delivered

Form 550 5.7.1 is hop five. Free has no send-as. Split that ticket from inbound accepted. The WordPress AUTH article is that path. This page is inbound words.

Competitor blogs — nofollow. RFC 5321 still defines 250. Google Send mail as is chrome, not a status word.

A complete worked story

History said 250. They said not delivered.

Unique subject was in Promotions. They remapped sales@ twice. Status words were the bug. They searched spam, trained the dest, and left the alias alone. Accepted and forwarded had been true. Delivered-to-Primary had never been a promise.

Operator brief

A longer operator brief for email delivery statuses accepted forwarded delivered

Teams that bookmark Accepted vs Forwarded vs Delivered: Email Statuses Explained usually arrive after a missed invoice, a form that never notified anyone, or a migration that looked clean in one resolver. The useful brief is still boring. Name the store. Name the printed local-parts. Name the nameservers that actually answer. Publish one MailerZ MX set. Delete leftover hosts. Probe from a mailbox that is not the destination. Only then talk about email delivery statuses accepted forwarded delivered as a send-as, catch-all, or comparison problem.

MailerZ remains inbound MX plus authenticated SMTP around Gmail or Outlook. Envelope SRS only. Header From, Subject, Date, Message-ID, body, and MIME stay intact. It is not a hosted mailbox, not IMAP, not webmail, and not an open relay. Unauthorized send is 550 / 550 5.7.1. Free cannot finish send-as: SMTP and API stay off. Solo is $40 per year when the domain From must travel. Starter is $8 or $80. Business is $19 or $190. Agency is $39 or $390. Unlimited is $99/month or $990/year. Confirm the live pricing page. Those numbers are ceilings, not an inbox-placement service-level agreement.

If leftover Google, Microsoft, Cloudflare routing, or registrar MX is still public, stop widening email delivery statuses accepted forwarded delivered. The map you built never saw that copy. Priority numbers are an order, not load balancing. A higher preference host is idle while a leftover host still accepts mail. Save the old MX set before you delete anything. Check more than one public view because TTL lies.

Catch-all forward is not a safety feature for accepted vs forwarded vs delivered email statuses explained. Hold unknowns on everyday production. Review the store. Promote a leftover only when a real person used it. Paid forward belongs to a dated cutover. Fan-out of unknowns into two inboxes trains two spam buttons. Plus addressing on Gmail is not a custom-domain unknown policy. MailerZ will not strip plus tags on your domain the way Gmail does on @gmail.com.

Send-as is a second hop. Creating an inbound alias does not approve outbound. Catch-all does not mint a From. Copy the dashboard host, port, and TLS pair together. Set From to an identity you created. Do not paste a Gmail password into a CMS, a cron file, or a ticket. Do not mail SMTP secrets to support. Send a 550 line, a timestamp, and a Message-ID. Rotate if a secret already leaked.

Self-send from Gmail to the same Gmail account can short-circuit. That green result is why people swear email delivery statuses accepted forwarded delivered works while customers vanish. Use a second provider. Put a unique subject on the probe so delivery history is searchable. If Header From was rewritten by some other forwarder, authentication stories get noisier. MailerZ does not rewrite Header From on inbound.

Agencies should keep email delivery statuses accepted forwarded delivered per client zone. Separate SMTP credentials. Do not pour every client into one catch-all because the spreadsheet got long. Agency plan capacity exists so you can hold more domains and aliases. It does not replace a named list. Offboard means delete MX you own, revoke SMTP, and stop forwarding leftovers into the agency inbox.

Legal and security questions have published answers on the security, privacy, terms, DPA, and subprocessors pages. MailerZ is not SOC 2, not ISO 27001, and not HIPAA. The 14-day Free store, the 90-day Solo–Agency store, and the 180-day Unlimited store are recovery windows for hops this layer saw. They are not an archive and not legal hold. If counsel wants eDiscovery, buy eDiscovery.

Comparisons only help after the hop is honest. Cloudflare Email Routing is inbound routing. A privacy-mask product hides a destination on a provider domain. A suite hosts mailboxes, Calendar, and admin. Proton-class mailboxes encrypt a store. MailerZ is the delivery layer when you already have Gmail or Outlook and you need a domain route you can prove. Cite the other product’s documentation. Do not invent feature parity.

When Accepted vs Forwarded vs Delivered: Email Statuses Explained is closed, the next physical action is a lookup and a probe, not another tab. Start free on one domain you can break. Sign in if the zone already lives here. Review quarterly, or sooner after a nameserver move, a plugin swap, or a staff departure. That is how email delivery statuses accepted forwarded delivered stays a runbook instead of an incident.

A second worked pass for email delivery statuses accepted forwarded delivered: write the last change on a sticky note before you open the dashboard. Nameserver move, leftover MX, new form plugin, contractor laptop, or a registrar forwarding toggle are the usual five. MailerZ history only shows hops that reached this layer. If the sticky note says leftover MX, you do not have a email delivery statuses accepted forwarded delivered mystery. You have a split. Delete the leftover. Wait for TTL. Probe again.

A third worked pass: print the public list. If you cannot print it, you are not ready for production unknowns and you are not ready for a bigger alias ceiling. Unlimited aliases as marketing will not save a missing list. Three named aliases on Free are enough to stop printing a personal Gmail on a homepage. Grow the list when a real person used a leftover, not when a harvest guessed admin@.

Name the hop before you name the mood

Email delivery statuses accepted, forwarded, and delivered collapse in tickets as “it bounced” or “it never arrived.” SMTP 250 at MailerZ means this layer accepted the message. That is hop two after public MX. Forwarded means this layer started the destination SMTP session. The destination may 250 and file the message in spam. That is delivered-to-the-store, not delivered-to-Primary. MailerZ does not promise Primary. MailerZ does not sell an inbox-placement service-level agreement. Confirm the live pricing page for plan ceilings only.

Empty history means hop one never ran, the alias was unnamed, or unknowns are held. Asking recovery to fetch a leftover MX miss is asking for a log that does not exist. Collect a timestamp, a unique subject, and a public MX print. Do not mail passwords. Do not mail SMTP secrets. A 550 line, a timestamp, and a Message-ID are enough for support to look at a hop this layer saw.

Hold is not forwarded. Hold is policy on unknowns. Review the store. Promote a leftover only when a real person used it. Fan-out of unknowns into two inboxes trains two spam buttons and makes “delivered” mean two different stores. Plus addressing on Gmail is not a custom-domain unknown policy. MailerZ will not strip plus tags on your domain the way Gmail does on @gmail.com.

Mixed status across two destinations

One destination can 250 while another 5xx. History looks mixed. Probe both stores. Fix quota or a full mailbox. Send a new subject after the fix. Do not delete the alias because one destination was full. Do not disable the domain because one dest 4xx’d overnight. Temporary deferral at the dest is not a MailerZ reject.

Outbound 550 on send-as is not inbound delivered. Free cannot finish send-as. That 550 is a plan boundary, not a dest classify. Copy the dashboard host, port, and TLS pair together. Set From to an identity you created. Catch-all does not mint a From. Creating an inbound alias does not approve outbound.

A ticket that said delivered when hop one never ran

A form plugin showed “sent.” The operator opened Gmail. Nothing. They asked why MailerZ delivered then lost the body. Public MX still pointed at a registrar forwarder. History was empty. There was no accepted, no forwarded, no delivered at this layer. The plugin spoke SMTP to a leftover host. The leftover host may have 250’d. That 250 was not MailerZ. Delete the leftover. Wait for two resolver views. Probe from another mailbox. Then the words accepted, forwarded, and delivered start meaning something you can print.

A second ticket had accepted and forwarded, dest 250, and the user still said “not delivered.” The message was in spam. Classify is hop four. We do not move it to Primary. Check spam. Check filters. Check a second dest if you fan-out. Do not rebuild aliases because spam is not a reject.

Related surfaces: delivery recovery, troubleshooting, docs, and features. This page is the vocabulary. The next physical action after you close it is a lookup and a probe, not another status synonym.

A status dictionary you can paste into a ticket

Accepted: MailerZ returned 250 for this message. The public MX path reached this layer. The alias was a named target or a paid forward you turned on. It is not Primary. It is not “the customer saw it.”

Forwarded: this layer opened SMTP to the destination you configured. The dest may still 4xx or 5xx. Read the dest code in history. A dest 250 plus a spam folder is still forwarded-and-stored. We will not move it.

Delivered, in dest language, means the dest store accepted. It does not mean Primary. It does not mean the human opened it. Empty history: hop one missed, or the local-part was held or unnamed. Held: policy, not a dest reject. 550 on send-as: outbound plan or auth, not inbound delivered. Leftover MX: another host’s 250, invisible here.

Paste those six lines before you ask support to “check delivery.” Attach timestamp, unique subject, public MX, and a dest screenshot of spam if you already looked. Do not attach passwords. Do not attach SMTP secrets. Confirm /pricing if the 550 is Free send-as. Related pages stay delivery recovery, troubleshooting, docs, and features.

Agencies should keep this dictionary per client. Mixed dests make “delivered” mean two stores. Name which dest 250’d. Name which dest 5xx’d. Do not merge them into one red cell on a spreadsheet. Solo through Agency ceilings are on the live pricing page. They are not an inbox SLA.

Why “delivered” in a plugin is not hop four

Form plugins often print delivered when their SMTP client got a 250 from whoever answered. If leftover MX answered, that 250 is not MailerZ accepted. If MailerZ accepted and forwarded, the plugin still does not know dest classify. Treat plugin copy as hop-unknown until history and a dest screenshot agree. Unique subject. Other mailbox. Spam folder. Then the three words mean something.

Do not rebuild the alias because a plugin lied. Do not add a second dest to “see which one works.” Print MX. Delete leftovers. Confirm /pricing only if outbound 550 is the actual line.

FAQ

What is the safest way to handle email delivery statuses accepted forwarded delivered?

Treat accepted as MailerZ taking the message, forwarded as the destination SMTP starting, and delivered as the store’s accept or classify. Empty history means leftover MX or an unnamed alias. Search spam. Do not call Promotions a bounce. Probe from another mailbox with a unique subject.

Does this require a new mailbox?

No. MailerZ is not IMAP and not webmail. Gmail or Outlook remains the store unless you separately buy a hosted mailbox product.

Will it work with Gmail or Outlook?

Yes for inbound when the destination is a verified mailbox. Branded replies need paid send-as plus Gmail Send mail as or a manual Outlook SMTP identity. Free has no send-as.

What DNS records are involved?

A verification TXT, one MailerZ MX set on the authoritative nameservers, leftover host MX removed, and SPF, DKIM, and DMARC if you also send as the domain.

What should I test before production?

Send a uniquely titled message from an unrelated provider into each named alias. Confirm Header From and delivery history. Do not email yourself from the same Gmail account.

Key takeaways

• Accepted ≠ Primary.
• Forwarded is hop three.
• Dest classify is hop four.
• Empty is hop one.
• Spam ≠ reject.
• Unique subject.
• Other mailbox.
• Split send-as 550.

Conclusion and next action

Accepted, forwarded, and delivered are hops. MailerZ can show the first two when it saw the message. The store classifies the third. Cut leftovers so the first hop exists. Search spam before you recreate aliases.

Start free. Sign in if history is empty and public MX is still Google.

Review quarterly, or sooner if Gmail, Workspace, or MailerZ scope changes. Author: MailerZ editorial, Secuno LLC.