Top
New to MailBeez? Start learning the basics
Advanced Module - Version 4.32 updated 28. Feb. 2024

BounceHive Bounce Handling


Get this Module as part of following plans:

Start Up

S M L

Business

S M L

Enterprise

S M L

 

Configure Newsletter2Go as Email Engine to automatically process all bounces

Requirements

  • A separate email account set up specifically for bounce handling & configured as an IMAP mailbox in your email client
  • Use of MailBeez own built in Email Engine – SMTP (PHPMailer)
  • Your server must allow you to connect to IMAP servers – Check with your hosting company, especially if you plan to use GMail, as some have blocked the GMail-specific port

Get Your Bounced Emails Under Control

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!

Handle All Types of Bounces

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!  
 


Compatibility
This module is compatible with following shop systems

Gambio GX2/GX3/GX4

Modified-Shop 1.x/2.x/3.x

ZenCart 1.3.x/1.5.x

osCommerce 2.x

MailBeez.io API V2


Changelog

v4.3.1

15.01.2024

    • PHP8.2 refactoring

v4.3.1

21.03.2023

    • PHP8 refactoring

v4.3.0

14.10.2022

    • PHP8 refactoring

v4.2

10.05.2021

    • Gambio 4.2+ compatibility

v4.1

12.01.2021

    • Gambio 4.2+ compatibility

v4.0.1

24.07.2020

    • unable to install on new systems

v4.0.0

21.04.2020

    • PHP7.4 refactoring
    • Support for 4.0 Core Framework

v3.91

21.01.2019

    • more robust message-id extraction

v3.9

24.09.2018

    • PHP7.2 refactoring

v3.5

14.09.2018

    • PHP7 compatibility
    • support for additional bounce email format

v3.34

11.07.2018

    • correct documentation link

v3.33

01.11.2017

    • refactoring

v3.32

04.10.2017

    • logic for removable tag

v3.31

17.08.2016

    • fixed a bug connected to renaming of setting PHPMailer to SMTP

v3.3

30.06.2016

    • PHP7 refactoring
    • fixed a bug connected to renaming of setting PHPMailer to SMTP

v3.2.1

20.04.2016

    • fixed a bug connected to renaming of setting PHPMailer to SMTP

v3.2

18.08.2015

    • PHP5.6 compatibility

v3.1

15.07.2015

    • support for Newsletter2Go bounce handling

v3.01

28.04.2015

    • Gambio preintegration support

v3.0

03.11.2014

    • MailBeez 3.0 ready

Found errors? Think you can improve this documentation?   edit this page