Black Friday is 8 days away. When a big send stalls, the answer is usually sitting in your bounce report. A code that starts with 4 means “slow down”. A code that starts with 5 means “stop”. Reading the difference this week tells you exactly what to fix before the biggest send of your year.
Most senders look at one number after a campaign: the bounce rate. During sale week that number hides the real story. Two campaigns can show the same bounce rate, and one has a dirty list while the other is being slowed down by a mailbox provider. They need opposite fixes, and the codes tell you which one you have.
The two families of bounce codes
Every rejected email comes back with a three-digit SMTP reply code, often followed by a longer “enhanced” code such as 5.1.1 or 4.7.0. The first digit matters most.
- 5xx = permanent. In its guide to handling bounced emails, Spamhaus explains that the reply code for all hard bounces begins with 5, and that no retry will occur.
- 4xx = temporary. Spamhaus describes these as temporary failures where a retry will occur. The receiving server is saying “not now”, not “never”.
A hard bounce is a decision. A soft bounce is a conversation that is still going.
What the middle digit tells you
The enhanced code narrows things down. RFC 3463, the internet standard that defines these codes, groups them by subject. These are the ones you will see most in a bulk campaign:
- 5.1.x (addressing status): something is wrong with the address itself.
5.1.1means, in the standard’s words, “the mailbox specified in the address does not exist.” - 5.7.x (security or policy status): the receiver refused the message because of who sent it or how, not because of the address.
5.7.1is “delivery not authorized, message refused.” - 4.2.x (mailbox status, temporary):
4.2.2is a full mailbox, which the standard says should be treated as a transient failure. - 4.7.x (temporary policy refusal): in sale week this usually means you are sending faster than the receiver will accept from you right now.
Each family points to a different owner on your team. 5.1.x is a list problem. 5.7.x is usually a setup or reputation problem. 4.7.x is a sending-speed problem.
What to do with each type of bounce
Hard bounces on the address (5.1.x)
Suppress them straight away and never mail them again. Spamhaus is clear: after a hard bounce, don’t send to that contact again. On Black Friday, one stale import can push your hard-bounce rate up within minutes, and mailbox providers notice. Clear them after every send, not once a month.
Policy blocks (5.7.x)
Don’t just delete these addresses. A 5.7.x is often about you, not them. Check that SPF, DKIM and DMARC pass for the exact domain in your From line, look at recent complaint levels, and compare which mailbox providers are refusing. If one provider is blocking and the others are fine, the problem is your reputation with that provider. Spamhaus also notes that some hard blocks with 554 codes will often disappear over roughly 24 to 72 hours, which is one more reason to fix the cause rather than purge the list. Our guide on why bulk emails go to spam and how to fix it walks through the usual causes.
Deferrals (4.7.x and other 4xx codes)
These matter most in sale week. A deferral means the receiver is willing to talk but wants you to go slower. Your sending system retries automatically, and Spamhaus points out that addresses hit by a temporary failure should not necessarily be removed from a list. What you should change is your pace:
- lower the hourly sending speed for the provider that is deferring;
- split the campaign into waves instead of one blast;
- send to your most engaged subscribers first.
Mailbox full (4.2.x)
Let the retries run. If the same address keeps soft-bouncing across several campaigns, treat it as inactive and move it into a re-engagement or suppression segment.
Why bounces rise in sale week
Bounces climb every holiday season, and not only because of your list. One large email platform’s holiday help article lists the reasons: overall sending volume goes up, people mark emails as spam instead of clicking unsubscribe, and spammers take advantage of the holidays from Black Friday through the New Year. It also notes that heavy volume can make Hotmail hard-bounce contacts with a 5.7.1 code when it shouldn’t.
That last point is a useful warning. In sale week, a spike of 5.7.x bounces from one provider is not proof that those addresses are dead. Pause, slow down and look at the pattern before you delete anyone.
Send to clean lists and engaged contacts, and don’t start mailing new lists during the holidays.
That is the same article’s advice for the season, and it is worth repeating. If you are still planning which segment gets which email, our Black Friday email calendar lays it out day by day.
A 15-minute bounce check for this week
Run this on your next campaign, before the big day:
- Export the bounce report and group it by the first digit: 4xx and 5xx.
- Inside the 5xx group, split 5.1.x (address) from 5.7.x (policy).
- Group everything by receiving domain: Gmail, Yahoo, Outlook and your largest business domains.
- Suppress every 5.1.x address before the next send.
- If 5.7.x bounces are concentrated on one provider, check authentication and complaints for that provider before you send to it again.
- If 4.7.x deferrals cluster on one provider, lower your hourly speed for that provider and send in smaller waves.
- Write down today’s numbers. On Black Friday, compare against them every hour instead of guessing.
For a broader checklist, see how to improve email deliverability for bulk campaigns.
In SMTPProvider, delivery and bounce reports sit alongside campaign scheduling with sending speed and pause/resume, so you can slow a campaign down the moment deferrals climb instead of letting it run. The promotional API documentation shows how campaigns, sending speed and reports fit together, and our support team is a real person on chat and phone if you get stuck.
The short version
A 5xx is a “no”. A 4xx is a “not yet”. Remove dead addresses fast, fix the cause of policy blocks, and answer deferrals by slowing down rather than sending harder. Read your codes this week so Black Friday holds no surprises.
See how our API and reports handle bounces and sending speed in the SMTPProvider promotional API documentation.