Valid-looking emails bounce because verification checks syntax and mailbox existence, not the receiving server's mood at send time. Greylisting delays unknown senders. Mailboxes fill up. Reputation filters block your IP or domain. The address is real, but the message still gets deferred, rejected, or silently dropped.
What's the difference between a verified email and a deliverable one?
A verified email means the address exists and can technically receive mail. A deliverable email means your specific message reached the inbox this time. Verification is a snapshot of the mailbox. Deliverability depends on the receiving server, your sending reputation, and timing. The two overlap, but they are not the same thing.
Our verification engine confirms two things: the domain publishes valid MX records, and the mailbox responds at the SMTP level. That tells you the address is worth sending to. It cannot promise the next message lands. A server that accepted a probe on Monday can defer, throttle, or block a real send on Tuesday. Nothing about the address changed. The conditions around it did.
Greylisting: the bounce that isn't really a bounce
Greylisting is a spam-control trick. The receiving server sees an unfamiliar sender and returns a temporary 4xx error on the first delivery attempt. Legitimate mail servers read that as 'try again shortly' and retry after a short delay. Most spam bots do not bother. The retry usually succeeds within a few minutes to an hour, and the recipient never notices the pause.
The problem shows up when your sending tool treats that first 4xx as a hard failure and marks the address bad. It was never bad. It was greylisted. If you send through a platform that does not retry, or you export a bounce list too early, you throw away perfectly good contacts. Check whether the code starts with 4 (temporary) or 5 (permanent) before you delete anything.
Full mailboxes and other temporary failures
A mailbox over quota returns 'mailbox full' and rejects new mail until the owner clears space. The address is valid. The person exists. They just stopped reading. This is common with abandoned accounts, former employees who kept a personal forwarder, and free inboxes that quietly hit their storage cap years ago.
Other soft failures look similar. A busy server may time out or refuse the connection under load. A provider protecting its users may throttle you and ask you to slow down. None of these mean the address is dead. They mean 'not right now.' Treat them as a pause, not a verdict.
Temporary failures share one pattern: the server tells you to try again later. Here is how the common ones look and what to do with each.
| What you see | Bounce type | What it usually means | Action |
|---|---|---|---|
| 4xx greylisting | Soft, temporary | Server delaying an unknown sender | Let your platform retry; do not delete |
| Mailbox full | Soft, temporary | Recipient over storage quota | Retry later; suppress after repeat failures |
| Timed out or refused | Soft, temporary | Server busy or throttling | Retry with backoff |
| 550 no such user | Hard, permanent | Address does not exist | Remove immediately |
| 550 blocked or policy | Hard, reputation | Your IP or domain is filtered | Fix reputation, not the list |
Reputation blocks: when the server rejects you, not the address
Some 5xx rejections have nothing to do with the recipient. The receiving server checks your sending IP and domain against blocklists, authentication records, and its own history with you. If your reputation is poor, it rejects the message before it even looks at the mailbox. Every address in that batch bounces, even the real ones.
This is why a clean list can still bounce hard. The block is on your side. Common triggers: sending from a cold IP with no warm-up, missing SPF, DKIM, or DMARC records, a sudden spike in volume, or a past spam-trap hit that got your domain listed. Fix the sending setup and the same addresses start delivering again.
The fix is rarely the list. Pull your domain's authentication records and confirm SPF, DKIM, and DMARC all pass. Check your sending IP against the major blocklists. Slow your volume and let a new IP warm up over a couple of weeks. Reputation recovers, but it recovers on the receiving server's timeline, not yours.
Check your list right now, free
10 checks a day with no signup. 100 a day with just your email.
How do you tell a real bounce from a temporary one?
Read the bounce code. Codes starting with 4 are temporary (soft) failures: greylisting, full mailboxes, throttling. Retry those. Codes starting with 5 are permanent (hard) failures. Some mean the address is dead, but 5xx policy or blocklist messages point at your sending reputation, not the recipient. The wording after the number tells you which.
Keep the full bounce message, not just a pass or fail flag. 'Mailbox full' and 'user unknown' are both rejections, but only one means remove the contact. Group your bounces by reason before you act. Deleting soft bounces shrinks your list for no reason and can hide a reputation problem you actually need to fix.
A quick rule of thumb: if the same address bounces soft two or three times across separate sends, then start treating it as suppressible. One soft bounce is noise. A pattern is a decision. Hard bounces need no waiting. One clean 5xx 'user unknown' is enough to pull the address for good.
Steps to cut avoidable bounces
- Verify the list first so you remove dead addresses and disposable domains before they count against you.
- Authenticate your domain with SPF, DKIM, and DMARC so receiving servers trust your mail.
- Warm up new IPs and domains gradually instead of sending at full volume on day one.
- Segment by bounce reason and retry soft bounces instead of deleting them.
- Suppress an address only after repeated hard bounces or several failed retries.
- Watch your bounce rate and keep it under 2% to protect your sender reputation.
Where verification still earns its place
Verification will not stop a greylist delay or a reputation block. It was never meant to. What it does is remove the bounces you can control: addresses that do not exist, typos, duplicates, and disposable domains. Clear those out and the bounces that remain become signal. You can trace them to sending setup or recipient conditions instead of guessing at a messy list.
There is a bigger payoff too. A clean list protects the sender reputation that decides whether your borderline sends make it through. Fewer invalid hits means fewer hard bounces, which means mailbox providers trust your next campaign a little more. Verification and deliverability are not rivals. The first feeds the second.
Run your list through the Free Email Verifier before a send. It flags invalid syntax, duplicates, and disposable domains right in the browser without touching your daily quota, then runs MX and SMTP-level checks on the rest. You start from a clean base, so when something still bounces, you already know the address was not the problem.