How to Resend to Bounced or Unsubscribed Emails Using Enquire MAP

This safeguard is put into place to protect the Company Email Send reputation and should be managed very carefully. Re-sending to bounced or unsubscribed emails can damage the Community's sending reputation through Enquire MAP as well as damage the domain's public sending reputation.

We also suggest being very careful when deleting unsubscribed contacts. Should these contacts get back into Enquire MAP for any reason, we will not have any record of the bounced/ unsubscribed and sending to them again will also negatively affect Company sending reputation.

How do I bulk unsubscribe a list of contacts?

The user will have to decide on whether they are going to create a Segment or a List of contacts to bulk unsubscribe. A list can be Dynamic or Static. For more information, contact Enquire MAP Support.

Navigate to Contacts > Contact Lists to create a list of contacts from the Contacts menu in Enquire MAP. The User can make a new list of people or use a current set of people.
Select the contacts to bulk unsubscribe then add them to the list to save it.
Navigate to Contacts >All Contacts.
Click the All Contacts drop down to select the list or segment.
Click the CONTACT EXPORTS button after the list or segment is selected and used to filter the All Contacts table.
Download the Excel file that is received via email (or click CONTACT EXPORTS again to see a list of all your recent exports to download).
In the Excel file change NO to YES in Unsubscribed column.
Navigate to Contacts > Import Contacts to upload the edited file.
Update the map column data for “Unsubscribed”.
Use email as a Lookup column:
Click the START IMPORT button. Ini checking the Contact Lists, this list of contacts will appear as Unsubscribed.

Why is it recommended to bulk unsubscribe contacts instead of deleting them?

Enquire MAP fully manages the bounced and unsubscribed contacts and technically, ensures that the emails are not sent to those contacts that have unsubscribed. If opted to delete contacts that have been unsubscribed, Enquire MAP loses all collected data on the contact to include the unsubscribed state. It is possible to re-upload and inadvertently miss the unsubscribed state. If sending emails to prospects that have asked to be unsubscribed, this can negatively affect the Company sending reputation and, depending on the country bylaws, could result in large monetary fines.

List of Bounce Codes

Temporary Failures - “If at first you don’t succeed…”

A 400-style message is usually returned when some sort of transient error is encountered during the message transaction. These types of responses are usually not a cause for alarm as most of these will iron themselves out given a little time.

421 - Messages are temporarily deferred because of recipient server policy reasons. Usually because of too many messages or connections in too short a timeframe. Examples:

421 4.7.0 [GL01] Message from (X.X.X.X) temporarily deferred
421 4.7.1 : (DYN:T1)http://postmaster.info.aol.com/errors/421dynt1.html (throttled)
421 4.7.0 [GL01] Message from (X.X.X.X) temporarily deferred - 4.16.50. Please refer to http://postmaster.yahoo.com/errors/postmaster-21.html

What to do with this response: We’ll continue to retry deferred messages for up to 72 hours for a response like this, but you may consider temporarily easing off the throttle when sending messages to a domain that is returning this code, just so you don’t further delay your messages currently being tried.

450 - Messages that failed because the user’s mailbox was unavailable, perhaps because it was locked or was not routable at the time. Examples:

450 4.2.1 The user you are trying to contact is receiving mail too quickly. Please resend your message at a later time. If the user is able to receive mail at that time, your message will be delivered.
450 too frequent connects from 198.37.147.135, please try again later. (throttled)

What to do with this response: We’ll continue to retry deferred messages for up to 72 hours for a response like this. Generally this is based on a large influx of messages that you send, or if you’ve sent at a rate that the recipient server deems worthy of slowing down.

451 - Messages that simply failed, usually due to a far-end server error. This is unlikely anything you’ve done, remember we’ll keep retrying for 72 hours, so just keep an eye on it. Examples:

451 mta1012.mail.gq1.yahoo.com Resources temporarily unavailable. Please try again later [#4.16.1].
451 Temporary local problem - please try later

What to do with this response: We’ll continue to retry deferred messages for up to 72 hours for a response like this. Just keep your eyes peeled to see if the response to our retry attempts change.

452 - Messages that have been deferred due to insufficient system storage. Not your fault, they’ll probably accept the mail later on once there’s more space. Examples:

452 Too many recipients received this hour (throttled)
4.3.1 Insufficient system storage (throttled)
452 4.2.2 Over Quota

Hard Failures - “Return to Sender…”

A Hard or Immediate failure is anything that gets 500-style message as the result of trying to hand off a message. This typically indicates that some sort of permanent error occurred, this can range from systemic errors on the far-end server that just flat out prevents mail from coming in, all the way to policy-related blocks pertaining to content or other such factors. The examples below will give a taste of some of the myriad reasons a 500-style NDR(non-delivery response) can get returned for.

550 - The user’s mailbox was unavailable. Usually because it could not be found, or because of incoming policy reasons. Examples:

550 5.1.1 The email account that you tried to reach does not exist. Please try double-checking the recipient’s email address for typos or unnecessary spaces.
550 Requested action not taken: mailbox unavailable
550 5.1.1 \<address@aol.com>: Recipient address rejected: aol.com

What to do with this response: It’s probably a good idea to take addresses that throw this response off of your main list, as it’s likely a bogus address or one that was mistyped.

551 - The intended mailbox does not exist on this recipient server. This response will sometimes include a forward address to try if the server knows where the intended mailbox is. Examples:

551 not our customer
551 user does not exist

What to do with this response: Don’t bother re-sending, the recipient server does not recognize the recipient address as being one of it’s own. Keep any eye on the human readable portion of the response, as it may include a forwarding address.

552- The intended mailbox has exceeded its storage limits. Examples:

552 5.2.2 This message is larger than the current system limit or the recipient’s mailbox is full. Create a shorter message body or remove attachments and try sending it again.

What to do with this response: It’s at your discretion if you want to try re-sending, but there’s a pretty good chance that it’s a defunct address. We don’t resend messages with this error code, so refer to the human readable portion for more guidance.

553 - The message was refused because the mailbox name is either malformed or does not exist. Examples: None

What to do with this response: Don’t retry sending to this address, it’s fairly likely that it’s a bogus or mistyped address.

554 - Messages that failed. This response is a ‘default’ of sorts, but can be attributed to anything from planetary alignment, tides of the moon or gypsy curses. Generally a very vague NDR, but refer to the human-readable portion of the message for further instruction. Examples: None

What to do with this response:Use the human readable portion of the message for further guidance, if you’re not sure what to do, just consider the address “bad” unless the recipient contacts you.

Other

SendGrid will also display a code when the recipient server has responded with a literally blank reason code. Rather than leave you to ponder what a blank field might mean, the below message is displayed instead, letting you know that far end was not able to respond intelligently to our request.

Delayed Bounce - Unable to Parse Server Reason

What to do with this response: Your best bet is to contact the mail administrator for the intended recipient’s mail domain to see if they have any more info on what may have happened.

Blocks, Bounces, and Drops

Block - A block is when the email server you are sending to refuses your email. There can be lots of reasons for this: they might decide you are spam, that you violate an internal policy they have, or the user you are sending to may no longer exist on the mail server.

Bounce - A bounce is an email that will be sent back to you because of some error; bounces can be categorized as hard-bounces or soft-bounces. Soft-bounces are 4xx error level and are often temporary. A soft-bounce will reach the recipients email server, and then be sent back due to a full destination inbox, a server error, or an email address that no longer exists. Hard-bounces are 5xx error level and are permanent failures; hard bounces will be sent back because of an invalid address.

Drop - A drop is if it has already bounced, or if it is invalid. These occur to help protect sender reputation.

Please reach out to the dedicated Enquire Account Manager or Enquire MAP Support team for further assistance.