Your email platform shows 98% delivered. But do you actually know what that means?
Most email marketers have been there; you hit send, the numbers look good, and you move on. But “delivered” is one of the most misunderstood metrics in email marketing, and it means something very specific that is worth understanding properly.
Before we dive in, there is one important distinction to make: email delivery and email deliverability are not the same thing. You will see these terms used interchangeably all the time. They are two different concepts, and confusing them leads to real strategic mistakes.
In this article, we are focusing on email delivery; what it means, how to measure it, and how to know if your emails are actually being delivered. Deliverability, which is about whether your email lands in the inbox or the spam folder, is a separate topic we will cover in another article.
Let’s start from the beginning.
What Does “Delivered” Actually Mean?
When your ESP reports an email as “delivered,” it means one specific thing: the receiving mail server accepted your message. That’s it.
Think of it like sending a letter. Delivery is confirmed the moment the post office at the destination accepts the envelope. What happens after that — whether it ends up on the right desk, gets opened, or sits in a pile unread — is a different story.
When you send an email, your sending server communicates with the recipient’s mail server using a protocol called SMTP (Simple Mail Transfer Protocol). If the receiving server accepts the message, it sends back a confirmation. That is what gets counted as “delivered” in your ESP dashboard.
If the receiving server doesn’t accept the message, you get a bounce. And that bounce tells you delivery failed.
Email delivery is a binary outcome:
| ✅ Server accepted the message = delivered |
| ❌ Server rejected the message = not delivered (bounce) |
No grey area. No guessing. That is what makes delivery different from deliverability — delivery always has a definitive answer.
What does a successful SMTP response look like?
When a receiving mail server accepts your email, it responds with a 250 status code. This is the SMTP signal for “message accepted.” Here are a few real world examples:
| ✅ 250 2.0.0 OK: Gmail’s standard acceptance response |
| ✅ 250 2.0.0 OK id=xxxx: Microsoft/Outlook acceptance response |
| ✅ 250 OK: A basic acceptance response common across many mail servers |
You won’t see these in your ESP dashboard directly, your ESP translates that 250 ok response into a “delivered” status in your reporting. But if you ever dig into your email logs or work with a deliverability tool, these are the signals confirming your email made it to the other side.
What is a Bounce and What is it Telling You?
When a receiving mail server rejects your email, it sends back an error message. This is called a bounce. Unlike a successful delivery, a bounce is the receiving server’s way of saying “this message was not accepted and here is why.”
Bounces fall into two categories: hard bounces and soft bounces.
Hard Bounces
A hard bounce is a permanent delivery failure typically denoted with a 5.x.x response from the recipient mail server. Retrying won’t change the outcome. The most common reasons are:
- The email address doesn’t exist
- The domain doesn’t exist
- The receiving server has permanently blocked your sending address
Hard bounces should be removed from your list straight away. Continuing to send to them signals to ISPs that your list hygiene is poor and that can start affecting your deliverability over time.
Soft Bounces
A soft bounce is a temporary failure, denoted with a 4.x.x response from the accepting mail server. The receiving server recognised the address as valid but couldn’t accept the message at that moment. Your ESP will typically retry delivery automatically for a predetermined period of time (ex: 24 – 72 hours). Common reasons include:
- The recipient’s mailbox is full
- The receiving server is temporarily unavailable
- The message size exceeded the server’s limit
If a soft bounce keeps happening over multiple retry attempts, most ESPs will eventually treat it as a hard bounce.
Common bounce codes and what they mean
Behind every bounce is an SMTP error code. Here are some of the most common ones you will come across:
| Bounce Code | Type | Description |
| 550 5.1.1 | Hard | User does not exist. The address is mistyped, outdated, or was never valid. |
| 421 | Soft | Service temporarily unavailable. Could be maintenance, high traffic, or a temporary outage. ESP will retry. |
| 452 | Soft | Insufficient storage. The recipient’s mailbox is full. ESP will retry, but may become a hard bounce. |
| 550 5.7.1 | Hard | Blocked due to DMARC policy. Message failed DMARC authentication (SPF or DKIM alignment failed), often due to misconfiguration. |
How Do You Know if an Email Was Delivered?
Now that we know what delivery means technically, the practical question is: where do you actually find this information?
Unlike deliverability, delivery has a clear answer. Here are the main places to look.
Your ESP Dashboard
The first place to check is your ESP dashboard. Whether you are using Mailchimp, Klaviyo, HubSpot, Salesforce Marketing Cloud, or any other platform, your campaign reporting will show you a delivery rate for every send. Most ESPs also let you drill down into bounce details; which addresses bounced, what type of bounce, and in many cases the actual bounce code from the receiving server.
Email Logs
If you have access to your sending infrastructure, email logs are the most detailed source of delivery information. Every SMTP transaction is recorded including the server response for each message. This is where you will find the raw 250 confirmation codes and bounce messages we covered earlier. Useful when you need to investigate a specific issue or confirm delivery of an individual email.
Delivery Status Notifications (DSN)
Some mail systems support Delivery Status Notifications, an automatic message sent back to the sender confirming the email was delivered to the recipient’s server. Not universally supported, but can be a useful confirmation mechanism particularly in B2B or enterprise environments.
What about a single specific email?
If you need to confirm delivery of one individual email, a transactional message, a contract, an important customer communication, check your email logs for that message and look for the 250 ok responses. If you got a bounce instead, the logs will tell you exactly why.
How to Track Your Delivery Rate
Knowing your delivery rate after a single send is useful. Tracking it consistently over time is what actually keeps you out of trouble.
How to calculate your delivery rate
The formula is simple:
| (Emails Sent – Bounces) ÷ Emails Sent × 100 = Delivery Rate % |
If you sent 10,000 emails and 200 bounced, your delivery rate is 98%. Most ESPs calculate this automatically, but knowing the formula helps you understand what you are looking at and catch inconsistencies in how different platforms report the number.
Delivery rate and bounce rate are two sides of the same coin. A 2% bounce rate means a 98% delivery rate. Some platforms show one, some show both. Worth knowing either way.
Watch the trend, not just the number
A single campaign’s delivery rate tells you something. The trend across multiple campaigns tells you a lot more.
What you want to see is consistency. A stable delivery rate is a healthy sign. A slow decline over several campaigns is worth investigating, it could be list quality, authentication issues, or sender reputation starting to slip. A sudden drop on one specific campaign needs immediate attention, it could point to a problematic segment, a technical issue, or a block from a major ISP.
Set up alerts for bounce spikes
Most modern ESPs let you configure automated alerts for bounce rates. If you haven’t set these up, it’s worth doing. Finding out about a bounce problem after a campaign has fully deployed is too late, the damage is already done.
A good rule of thumb is to get alerted if your hard bounce rate exceeds 2% on any single send, or if you notice an unusual volume of a specific bounce code, especially authentication related ones like the DMARC failures we covered earlier.
So, Do You Know if Your Emails Are Being Delivered?
Email delivery is easy to overlook until something goes wrong. The good news is that it has clear, measurable signals. You don’t need to guess. A 250 response means your email was accepted. A bounce code tells you exactly why it wasn’t.
A few things worth keeping in mind:
- Delivery and deliverability are not the same thing. Delivery is whether the receiving server accepts your message. Deliverability is where it ended up. Don’t mix them up.
- Bounces are your most important delivery signal. Know the difference between hard and soft, act on them quickly, and pay attention to the codes when something looks off.
- Track your delivery rate over time. Trends are more useful than individual snapshots.
- Set up alerts. Don’t wait until after a campaign to find out something went wrong.
Ultimately, understanding email delivery means recognizing the clear, binary nature of the SMTP handshake: a 250 ok response confirms acceptance by the receiving server, and a bounce code signals a definitive failure, providing the exact reason. By consistently monitoring your ESP reports, tracking your delivery rate trends, promptly addressing hard bounces, and utilizing automated alerts, you move past simply trusting a percentage and gain control over the foundational step of all email marketing while ensuring your message successfully reaches the destination’s front door.
