Reading a bounce message begins with matching the notification to a specific outbound message and recipient. Only after confirming that connection is the reported outcome worth investigating. Treat what the remote server reports as unconfirmed until your own outbound logs back it up. This walkthrough follows one complete delivery status notification (DSN) through that exact process.
Match the report before you act on it
Preserve the raw message source and the diagnostic text before editing or sharing excerpts. Keeping relationships between identifiers, addresses, and timestamps intact is what lets you match the report to an actual send. If you cannot match it, pause any automated action: DSNs can be forged.
This walkthrough uses a synthetic example rather than live production logs. An internal appointment application dispatched a plain-text notification from notices@studio.example to mira@recipient.example. The envelope return address was returns@studio.example. The sender asked that any report return headers only and supplied the envelope identifier Visit-84B. The sending MTA accepted the message and then attempted delivery. No live mail was transferred and no authentication records were queried.
Here is the complete synthetic report as received. Its third MIME part carries the returned original headers, while the original message body is omitted as requested.
Return-Path: <>
Received: from outbound.studio.example (outbound.studio.example [192.0.2.84])
by inbox.studio.example with ESMTP id DSN84B
for <returns@studio.example>; Mon, 14 Sep 2026 09:10:08 +0000
Date: Mon, 14 Sep 2026 09:10:06 +0000
From: Studio Postmaster <postmaster@studio.example>
To: <returns@studio.example>
Message-ID: <dsn-84B@outbound.studio.example>
Subject: Delivery stopped for appointment notice
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
boundary="studio-84B-report"
--studio-84B-report
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Delivery to mira@recipient.example has failed.
The remote server reported that this mailbox does not exist.
No further delivery attempts will be made for this message and recipient.
--studio-84B-report
Content-Type: message/delivery-status
Content-Transfer-Encoding: 7bit
Original-Envelope-Id: Visit-84B
Reporting-MTA: dns; outbound.studio.example
Arrival-Date: Mon, 14 Sep 2026 09:10:01 +0000
Final-Recipient: rfc822; mira@recipient.example
Action: failed
Status: 5.1.1
Remote-MTA: dns; mx.recipient.example
Diagnostic-Code: smtp; 550 5.1.1 Mailbox does not exist
Last-Attempt-Date: Mon, 14 Sep 2026 09:10:04 +0000
--studio-84B-report
Content-Type: text/rfc822-headers
Content-Transfer-Encoding: 7bit
Date: Mon, 14 Sep 2026 09:10:00 +0000
From: Studio Appointments <notices@studio.example>
To: Mira <mira@recipient.example>
Message-ID: <visit-84B@studio.example>
Subject: Your appointment time
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
--studio-84B-report--
What each part of the report tells you
The observations below analyze this synthetic DSN. In a live production incident, the validity of each observation depends on matching evidence from your own server logs.
| Sample field or block | What you can observe | Corroboration or next decision |
|---|---|---|
| Outer headers | The report goes to returns@studio.example and its Return-Path is empty. | That matches the premise and the DSN return-address rules, but it doesn’t prove provenance. |
| Three MIME parts | A human-readable explanation, the delivery-status fields and the returned headers. | The report container fixes this order. The header-only request explains the omitted body; text/rfc822-headers labels that third part. |
Blank line after Arrival-Date | The message-wide fields end and Mira’s outcome begins. | Preserve the recipient-block separation. No other recipient outcome appears. |
Reporting-MTA / Remote-MTA | outbound.studio.example made the reported delivery attempt; mx.recipient.example is the remote system whose response is reported. | Match both hostnames against your outbound logs before deciding which server caused the failure. |
Final-Recipient | This block concerns mira@recipient.example. | Correlate it with the accepted envelope recipient, not only with To. |
Status / Diagnostic-Code | 5.1.1 and 550 5.1.1 Mailbox does not exist agree with each other. | Keep the transport diagnostic intact and get the command stage from logs. |
| Dates | Creation 09:10:00; arrival 09:10:01; last attempt 09:10:04; report 09:10:06; receipt 09:10:08. All Monday, UTC. | The chronology holds together, but it gives you neither a retry history nor a command transcript. |
Returned Message-ID / Original-Envelope-Id | <visit-84B@studio.example> identifies the original content; Visit-84B identifies its submission. | Preserve spelling and case. The outer <dsn-84B@outbound.studio.example> identifies the report, not the message. |
The Status field provides a transport-independent outcome, while Diagnostic-Code preserves the SMTP response in this example.
The Original-Recipient field is absent because the submission parameters did not include an explicit original-recipient attribute. Because the field is optional, don’t backfill it from the To header: that would introduce false data into your bounce records.
What do Status 5.1.1 and Action: failed establish?
The reported failure indicates a missing destination mailbox, which is the meaning of 5.1.1. That’s a lead for investigation, not independent proof that the address is invalid. Even a failure DSN is not an absolute guarantee of nonreceipt. To review the standalone error definition, see the dedicated reference for SMTP 5.1.1, recipient mailbox does not exist.
The header Action: failed indicates the reporting MTA halted delivery attempts for this message and recipient; delayed would mean attempts continue. An MTA can give up on delivery while still reporting a temporary 4.x.x condition that persisted: action and condition answer different questions. Do not rewrite it as 5.x.x. Enhanced codes follow class.subject.detail, and an unfamiliar detail is no reason to guess beyond the class and subject you recognize. See the guide on reading SMTP status codes.
During the SMTP exchange, a 4yz reply permits retries, whereas a 5yz response warns against repeating the identical request. These are SMTP reply rules, not HTTP conventions. A live session reply is distinct from this asynchronous MIME report, which arrives afterwards.
Policy rejections require different checks. Enhanced code 5.7.1 concerns authorization or filtering, and SMTP 550 can include a policy refusal, but neither proves an SPF, DKIM, DMARC, or reputation problem by itself. Never alter DNS or drop contacts based on raw status codes alone.
No authentication verdict appears inside this bounce body. If the bounce has an outer Authentication-Results header, it only reflects the report message that was evaluated, not your original outgoing email. Authentication of the original message needs its own evidence with trusted provenance; without it, the original message’s authentication stays unknown. DMARC failure reports use ARF formatting and include distinctive markers such as report-type=feedback-report, Feedback-Type: auth-failure, and Auth-Failure: dmarc, as illustrated in RFC 9991’s report format. A standard policy DSN is an entirely different report type.
What to check next
Here is what the bounce tells us so far: delivery failed for one recipient because the remote server reported the mailbox doesn’t exist. It does not prove that the address is invalid, or that the bounce is genuine. The next step is matching your outbound logs and asking the responsible operator to corroborate the recipient and the remote response. If identifiers or diagnostics disagree, resolve discrepancies before running automated list suppression.
When server logs corroborate a genuine address error, apply your suppression policy to that specific recipient. Only retry sending once you’ve fixed the problem, like getting an updated email address from the recipient. For a delay notification, inspect the local queue first, because retry parameters are configurable. No internet standard imposes a universal ESP retry limit or list-removal threshold.
Once you correct an issue, monitor subsequent transmissions. As the standard notes, a positive final DATA reply transfers responsibility for delivery; it doesn’t establish inbox placement or that anyone read the message. Do not treat the absence of a new bounce as proof that the recipient received your email.
For step-by-step diagnostic workflows, use the SMTP failure triage guide. When escalating to a remote provider, prepare your ticket using the provider escalation checklist.
Frequently asked questions
Does a 5.1.1 bounce prove the address is invalid?
No. A 5.1.1 code only indicates that the destination mail server reported the mailbox as missing at that moment. You need corroborated sending logs or direct recipient confirmation before treating the address as permanently invalid.
What is the difference between Action: failed and Action: delayed?
Action: failed says the reporting MTA has stopped trying for this message and recipient; delayed would mean it was still trying. A stopped delivery can still carry a persistent transient 4.x.x condition.
Does a 5.7.1 bounce prove an SPF, DKIM or DMARC problem?
No. The 5.7.1 enhanced code signals a generic administrative or security rejection rather than a specific authentication failure. You cannot diagnose DNS records or domain reputation from that code alone without inspecting server logs and diagnostic text.
When does a retry after a bounce make sense?
A retry makes sense only after fixing the underlying condition, such as correcting a typo in the recipient address. For transient delay reports, you should inspect queue state rather than triggering manual resends.
Does an Authentication-Results header on a bounce describe the original message?
No. Any outer Authentication-Results header evaluates the incoming bounce report itself rather than the original outbound message. Authentication of the original message needs its own evidence with trusted provenance; without it, the original message’s authentication stays unknown.


