5.1-Setup Bounce Accounts


Unlike most of the contemporary applications having complex and somewhat limited structure for bounce processing, MUMARA has developed utility based bounce processor, keeping client’s convenience in mind. You can create more than one bounce accounts for bounce processing and can use one of these existing bounce accounts while scheduling the email campaign. The following section discusses how to setup the bounce account using “Setup Bounce Account” Page under “Bounce” in the left side navigational menu. 

Figure#5.1.1: Setup Bounce Accounts

Setup Bounce Accounts

The following table defines all the fields and the information to be placed in each field, in order to setup a new bounced email account.
Following Table Consists of

  • Text Fields
  • Dropdown Selections
  • Radio Buttons

Mandatory Fields are marked with asterisks

Table#5.1.1: Setting up Account for Bounce Processing

Bounce Name

As you can create more than one bounce account, you are required to provide a unique name of each account while it up. The bounce name will be used to identify the account within the application and has nothing to do with the recipients/ subscribers.

Bounce Host

Fill in this field with the path to your mail server or you may say the server where the email account for the bounce collection is hosted. This path is required to establish the connection between the application utility and server, and further helps processing the bounces automatically using the “Cron”.

The host or path to your email server or bounce email server generally looks like, or the main IP address of the mail server holding the email account for the bounced emails.  Make sure that the path you have provided is accurate.

Bounce Port

The above mentioned bounce host and this field with the following couple of fields are required to configure the bounce email setting using IMAP or POP access protocols.

Provide appropriate port, if you have configured other than the default ports for IMAP or POP3 respectively. Default port for IMAP 143 and 110 for POP3 (Without SSL or Non-Encrypted).

Bounce Username

Provide the username of the bounce email account. The username of bounced email mostly appears as [email protected]. This is also known as Bounce To email address. Make sure you already have configured the email account with the server you have mentioned in the bounce host field. 

Bounce Password

To establish the verifiable connection with the above mentioned bounce account to process the bounced emails, provide the password associated with the Bounce To email account.

Bounce Folder

The folder to which you want to send the bounced emails. In most of the cases, this folder is INBOX, except for the rare cases. Like sometimes the user may have created a separate folder for bounces. By default it is set to be the INBOX, if you keep this field empty. 

Validate Certificates

Security certificates are the part of verifying the identity of device or person, if connecting to the mail server is using self-signed certificate, select “Yes”, in the other case select “No” to proceed. Keeping this at “No” will not validate the security certificate.


Transport layer security or TLS is security protocol like the SLL that encrypts the file to deliver the mail securely. If the connection to your mail server/bounce server is using TLS to provide communication security, select “Yes” from the dropdown. Otherwise keep this option at “No”.


If the SSL is required to connect to the bounce/mail server, select “Yes” from the dropdown to continue, otherwise keep it to “No” and proceed.

Delete Emails

If you select “Yes” from the dropdown, the application will automatically delete the bounces from the INBOX (Or from the folder selected for bounce collection), each time after processing the bounces.

In case of “Yes” you need to make sure that the particular email account or folder is only used for bounce processing and no other email exists in the INBOX or in the particular folder. If the particular folder/ account isn’t meant to collect the bounced emails only, then go for the option “No” and proceed. Select “No” and manually delete the bounced emails.

Date Processing

You are offered with the two options to choose one of them, both post office protocol (POP3) and internet access messaging protocol (IMAP) are the protocols used to access remote server emails.

Both IMAP and POP are different in working mechanism and scope, like the POP3 is somewhat secure as it allows downloading of the emails from the server or checking of the emails using one computer/ device. While the IMAP allows using multiple devices, computers for the same process, therefore select accordingly.

If you don’t want to go advance to process the bounce using PowerMTA, setting up a new bounce account using configuration of POP or IMAP completes here. Press “Reset” to reconfigure the account, or press “Submit” to save this account.

There is this third button called “Test Email Login”, once clicked, application will establish a connection to the server to verify the login information mentioned above. If the connection to the server established, application will login to the email using the bounce username and password provided above, and after it founds the account information valid, it will return with a success message. An error message will be displayed otherwise. 

Figure#5.1.2: Saving the Details and Testing the Bounce Account

Saving Bounce Details

PowerMTA Bounce Processing

The above mentioned information is required for setting up basic bounce processing account. After you provide all required information, you can finish setting up the basic account here or can check “Use PMTA Bounce Processing”option to process the bounces using PowerMTA.
You need to first setup the basic bounce account fields discussed in the earlier table to configure IMAP or POP3. Both POP and IMAP process the bounces by accessing the bounce to email account. Even with the basic bounce account, the bounced emails can automatically be processed using cron, and further can be deleted by selecting the option “Delete Emails” as “Yes”.
Processing of the bounced emails is an important part of fixing the delivery issues, and the VMTA based PowerMTA offers advance level of bounce categorization, processing and valued options for troubleshooting. Ticking the checkbox with the option “Use PMTA Bounce Processing” will open up couple of more fields. Setting up these advance fields will enable to process the bounces directly from PowerMTA logs.
Unlike the normal bounce processing which only provides some basic value, the PowerMTA bounce processing option of MUMARA has this capability to go beyond, in order to collect accurate percentage/ number of bounced emails, advance value for bounce categorization and reasons to further troubleshoot the underlying issues.
Bounce processing using IMAP or POP requires accessing the bounce email account to read the bounced message and to process the bounces, while with PowerMTA feature, the application connects to the PowerMTA and process the emails marked as bounced within PowerMTA logs, that obviously utilizes less resources.

Figure#5.1.3: PowerMTA Bounce Processing

PowerMTA Bounce Processing

Extension- Table#5.1.1: Setting up details for PowerMTA Bounce Processing 

PowerMTA Server

Choose the PowerMTA server from the dropdown. A complete process of Integrating PowerMTA server with MUMARA is discussed under "Add PowerMTA Server". The dropdown carries the list of all PowerMTA servers which you have integrated using "Add PowerMTA Server" section under "Integration" in the main menu. 

Empty Inbox

Select “Yes” if you want the application to delete the bounced email automatically, each time after processing the bounces, the system will empty the inbox. Select “No” if you want to manage the inbox manually.

a)      Recommendation

It is recommended to select “Yes” from the dropdown which appears next to “Empty Inbox” field. Although in case of PowerMTA the application processes the bounces from the logs and does not enters the bounce to email account for bounce processing. But bounce to email address keeps on receiving these bounced emails, therefore it is recommended to select the auto delete option to keep on performing both the tasks side by side, a) processing the bounce from logs and b)auto deleting the bounced emails from the bounce to email account.