Bounced Email Guide

When sending email, you will occasionally receive a notification in DailyStory that your message bounced.

What is a bounced email

A bounced email is a notification from the recipient's email system informing the sender that the message has not been delivered (or another delivery problem occurred). The original message is said to have "bounced".

What causes email to bounce

There can be numerous causes that lead to an email server preventing delivery of your message:

Types of bounces

There are two distinct types of bounces that can occur.

Recommended

If you receive a high bounce rate on an email send DailyStory will throttle delivery of additional messages.

Soft Bounce

A temporary issue related to the recipient's email server preventing delivery.

Soft bounces usually resolve themselves. DailyStory will continue checking the status of a soft bounced email for up to 12 hours.

Hard Bounce

A permanent issue related to the recipient's email server.

Recommended

To check your SPAM score (a numerical rating 0-10), you can use a free site like https://www.mail-tester.com/ to understand if your emails are at risk.

How to prevent bounced emails

There are several steps you can take to prevent emails from bouncing. And we recommend reading our detailed blog post for avoiding the junk folder and preventing bounced emails.

Use clean and verified data

It's important that you keep your email lists clean and up-to-date.

Avoid common content SPAM triggers

There are number of known SPAM triggers that you can avoid.

Avoid common SPAM words and phrases

See our article Keyword blocklists: What they do and whether you should use them to access and download common SPAM keywords to avoid.

Recommended

An acceptable bounce rate is between 2-5%. Anything over 5% suggests a problem you need to address and resolve. DailyStory report dashboards give you bounce % rates for individual emails and emails within a timeframe you can set.

Bounce code descriptions

CodeDescription
421service not available, closing transmission channel
450Requested mail action not taken: mailbox unavailable (e.g., mailbox busy)
451Requested action aborted: error in processing
452Requested action not taken: insufficient system storage
500The server could not recognize the command due to a syntax error.
501A syntax error was encountered in command arguments.
502This command is not implemented.
503The server has encountered a bad sequence of commands.
504A command parameter is not implemented.
550User’s mailbox address is invalid
551The recipient is not local to the server.
552The action was aborted due to exceeded storage allocation.
553The command was aborted because the mailbox name is invalid.
554The transaction failed for some unstated reason.
602Internal error code that messages bounced after attempts over 8 hours.

Bounce and retry handling

DailyStory includes advanced logic for bounce/retry logic to automatically reset emails if a non-hard bounce error occurs.

For example, email recipients that return a bounce status due to:

If a recipient is sent an email and a soft bounce is returned, the 'do not contact until' date is automatically set to a random date between four and seven days in the future. This is done to prevent sending multiple emails to an inbox that is not accepting them and potentially damaging the senders reputation.

Recommended

These and other codes - at DailyStory's discretion - will instead change the contacts do not contact until a date to a future date between 15-30 days out. This ensures the contact can cool down for a period of time prior to being eligible for a future email campaign.