@Alexis D'Alba​ It's a bit of a judgement call based on your particular business need, but that said, I wouldn't keep trying more than 3 or 4 times at the most.

The two main things to consider are:

1. Is the bounce being caused by a spam trap / blacklisting that gets de-listed after a day or two. SpamCop automatically de-lists after 24 hours if there aren't any more spam trap hits and most others follow the same pattern. So, let's say you or someone else on the same shared IP hits a spam trap. Your lead's recipient mail server likely has filters in place to monitor those spam trap and blacklist services, and if a sender is on them, they bounce your email. However, after you get de-listed, you can start successfully re-sending email to those leads again without them getting bounced, so it's worth a couple of retries.

2. Multiple emails to a lead who repeatedly bounces your emails is viewed as "spammy" behavior. Email senders develop a sending reputation based on patterns and behaviors. If you continue sending to leads who are bouncing every email all the time, your sending reputation takes a hit, which affects whether you make it past other people's spam filters. So, while it's good to keep retrying in case of a temporary spam trap / blacklisting, you don't want to keep re-sending for too long. Watch your database--sometimes that's only 3 or 4 retries. Sometimes you can get away with retrying more often. It varies a lot so it's hard to put a hard and fast rule on it.

@Mike Reynolds​

Hi.. I was trying to create the directory for maintaining the reasons for hard bounce, but I don't want custom field to populate the details for bounce. Instead, I was thinking to use Email Invalid Cause or Email Suspended Cause fields for the details.

Will it be helpful if I use the above fields or what difference will it make if I use custom field for entering details.

@Ayush Aggarwal​ If you're referring to writing to those fields, that won't be possible. Email Invalid Cause and Email Suspended Cause are system managed fields so you probably won't be able to write to them.

Cool! Can you share an example or screenshot on how the details will be shown in the custom field. Will it be similar to reasons that we get in Email Invalid/Suspended Cause fields with the bounce codes, sub bounce codes. I am trying to understand what difference will it make using a custom field.

The reasons recorded will be whatever the recipient mail servers give for why the emails were bounced. They usually follow a standard "form letter" type of reply, but it's entirely up to the admin of that mail server as to what they use for the code they supply. Most will be a generic "Code xyz Bounced because 123" or some variation on that, but I've seen bounce codes actually say "Go away". Really.

Whatever the bounce reason given, that will be what is entered into the custom field. The real goal of the custom field is just to have a place to record what they're saying for why they're bouncing your emails. It's best to use the custom field just so you can catch the reasons and review them. Plus you may get a laugh out of some of them.

Hi Kiersti,

I recently had a customer who had a 550 error. Is there a way to re-add them to our distribution list? She wants to receive our emails!

Would love any suggestions to help customers whose emails have gotten suspended get back on our lists.

Thanks!

Kathryn

Hi Kathryn,

I'd suggest to maybe just delete the existing entry and create a new one.

Best; Matjaž

How do you add a column to the results report after an email has been sent out that will show the details of why an email has bounced?

Is it safe to mark a user as "No Longer at Firm" in our CRM System if his/her email address got 550 code？

No.