5.3-Setup Bounce Reasons Manually

Setting Up Bounce Reasons

When you send email to a large number of subscribers, errors are likely to occur at some level in bulk email delivery. Bounced is the email which the subscriber’s email client rejects to receive, these are also known as non-delivery reports. There are types and reasons of the bounces, two of the major types are soft and hard bounces.

Permanent delivery error is called “Hard Bounce” and the momentary delivery issue is considered as the “Soft Bounce”. There are reasons why these delivery problems occur, some of these reasons have already been categorized as hard or soft bounce and have become industry standards. Like if the email address does not exist, it constitutes a permanent delivery issue and will be considered as hard bounce, 5.0.0 is the error code for email address does not exist.

It is always recommended to process the bounces effectively in order to better categorize the bounced emails. The recommended practice for the hard bounce is don’t send further emails to them, add them to don’t send email list, remove or move them to a separate list of hard bounces. You can login to your account and can explore the detailed stats of particular campaign in order to view the detailed reasons of the bounced emails.  MUMARA has three levels to establish and categorize the bounced email as hard or soft, as per its error code and reasons.

Once the email is bounced back, system will first check the custom bounce reasons that you have manually set using “Setup Bounce Reasons” page to categorize the type of bounce (Hard or Soft), if it remains unable to match the reason and the code with the list of reasons setup manually, it moves to the second level.

There are set of bounced reasons and their codes saved in MUMARA by default, at second level the system matches the reason of bounced emails with the set of reasons saved in the application as its default behavior to categorize the bounced email. 

Even if it remains unable to match the error code with default reasons and error codes, it will then apply industry standards on that particular bounced emails to stamp the email as hard or soft bounce, as per its error code and the reason.

However, in some of the cases, you may need to setup custom reasons to categorize the bounced emails as hard or soft.

Like in the case of IP blacklisting which in general terms a permanent error and considered as hard bounce. But if you have more than one sending IPs, you can send the next campaign from another IP.

For such cases, you will manually setup the error code and the reason to stamp the particular email as soft bounce, if it occurs. Click “Setup Bounce Reasons” under “Bounce” in the left side navigational menu to setup manual bounce reasons.


Figure#5.3.1: Setting Up Bounce Reasons Manually


Table#5.3.1: Setting Up Bounce Reasons Manually

Bounce Label

Fill in this field with the name which can help to identify the particular bounce reason within the database.

Bounce Code

Setup appropriate error code for the bounce reason (Example, 5.0.0 or 5.1.1)


Bounce Reason

Provide relevant information with regard to the error code, which you have mentioned in the field above. (Like relevant information for 5.1.1 error code is Bad Destination Mail Box Address)

Bounce Type

Select which type of bounce is this? If you select “Hard” system will stamp this reason as “Hard” bounce, and if you select “Soft” application will categorize this reason as “Soft” bounce. Once it receives non-delivery report matching with the reason and the error code mentioned in the above two fields, it will straight away categorize the bounce as “Hard” or “Soft” as per the suggested type.  


Set this as "Active" to immediately start categorizing the particular kind of bounce "Hard" or "Soft" as per the customize bounce reason, you have just created. Inactive status of the bounce reason will have no effect over bounce categorization and processing. 


Complete the relevant information and click “Submit” to save this custom bounce reason. 


Have more questions? Submit a request


Powered by Zendesk