A bounce address is the return-path address in your email header that is responsible to receive delivery reports of the failed messages. Without a bounce address, your email isn't fully qualified and technically it's the main sender of the email that authenticates SPF (Sender Policy Framework).
While rendering the email message for delivery, Mumara embeds the bounce address into email headers as per your selection during the scheduling process.
Menu Navigation: Setup - Bounce Addresses
When you navigate to Bounce Address page, you see the following
Fields
Field |
Description |
Bounce Address |
The email address where your want to receive delivery reports of the failed messages (bounced back) |
Host |
The hostname of the server where bounce email is hosted |
Username |
Username of bounce mailbox |
Method |
Connection method of bounce mailbox i.e POP or IMAP |
Port |
Port number to connect |
Error |
It displays an error if Mumara is unable to connect to your bounce mailbox |
Actions |
- Test Connection: It opens a popup and starts testing the selected Bounce Addresses
- Set as Active: Set the bounce address as active
- Set as Inactive: Set the bounce address as Inactive
- Export to CSV: Export the bounce address to a CSV file
- Edit: Edit a bounce address
- Delete: Edit bounce address
|
- Test Connection: Test connection for the selected bounce addresses
Note: If no bounce address is selected then the action will apply on all bounce addresses globally
- Set as Active: Set the selected bounce addresses as active
- Set as Inactive: Set the selected bounce addresses as inactive
- Export to CSV: Export the selected bounce addresses to a CSV file
- Delete: Delete selected bounce addresses
Type into the search box to search across all bounce addresses
Click [+ Add New] button to add a new bounce address.
Fields
Field |
Description |
Bounce Email Address |
Email address where you'll receive bounces |
Process Bounces |
Let Mumara login to your bounce mailbox, read delivery reports and process them accordingly |
Active |
Enable processing of bounced emails |
Method |
POP: POP method downloads the emails from Inbox
IMAP: IMAP synchronizes the mailbox and folders |
Host |
The hostname of the server where bounce email is hosted |
Username |
Username to log in to bounce mailbox |
Password |
The password to login to bounce mailbox |
Port |
Port number of the bounce mailbox server |
Folder |
Folder name to process bounces from. Default: INBOX |
Validate Certificate |
Validate SSL certificate of the bounce mail server |
Mail Encryption |
Encryption of the incoming bounced emails i.e SSL or TLS |
Delete Emails after Processing |
Delete emails from bounce mailbox once they are processed by Mumara |
Verify Connection |
It's a button to validate bounce authentication if Mumara is able to login to your bounce mailbox |
Bounce cron runs every 2 hours by default however you can modify the processing time in Cron Settings. Once the bounce cron executes, it tries to log in to the bounce mailbox with active status using the saved authentication details. Upon a successful connection, it will look for new/unread emails and start reading them to understand the content. A delivery report email contains important information e.g. message-id of the email, bounce code/reason and other informative details for tracking purposes. Mumara matches delivery report of the failed messages within campaign logs and finds which campaign it belongs to and which contact it exactly is, and classifies the contact as soft/hard bounced after finding the matched bounce reason. You are also able to see the bounced emails under the "Bounced" tab in broadcast statistics. Moreover, you can also modify default bounce rules.