Configure Newsletter2Go as Email Engine to automatically process all bounces
Bounced emails from outdated customer email addresses is a huge problem, especially for those shop owners using purchased email lists. Even if you send email only to those customers who have signed up to receive them, you can expect some bounced emails when inboxes are full, email addresses are changed, or servers are temporarily down.
Bounced emails that are not properly handled might result in an increased spam rating, so it is important to handle the inevitable email bounces that will come your way, and there’s no better way to do it than with the MailBeez BounceHive Bounce Handling module!
The fully integrated BounceHive Bounce Handling from MailBeez allows you to automatically handle hard bounces, soft bounces and transient bounces:
Hard Bounces: Hard bounces result when email addresses are completely unknown, obsolete, or incorrect and will never be delivered to the recipient. Hard-Bounced email addresses are immediately blocked by MailBeez so that no further emails will be sent to these addresses.
Soft Bounces: Soft bounces result when email addresses have full mailboxes, their domain is temporarily down, or they’re currently not able to receive email for whatever reason. Soft-Bounces will cause MailBeez to wait the configured number of days before trying the send again.
After a configured number of soft-bounces, the next soft-bounce will be converted into a hard bounce and no further emails will be sent to that address.
Transient Bounces: A transient bounce occurs when a particular message can not yet be delivered, but the server is still trying. MailBeez will not do anything with these Bounces as they are informative in nature.
The bounces are stored using the customers’ email and the customers’ id. Both must match to block a sending, so when a customer has changed the email address to a valid email, the bounce-block for the old email will not affect the new sendings. Very cool!
CRE Loaded 6.x
Found errors? Think you can improve this documentation? edit this page