How to force bounce/complaints re-processing with another delivery reports source?

agentlink

Beginner
Jan 10, 2020
4
0
1
Hi.

First of all, this issue is pretty hot, because we already emailed about 50k of our subscribers and got 1.5k bounces/complaints that are not processed yet. Now, we want to send another campaign, but we face a risk that our reputation will drop, as the bounced email addresses will be emailed as well (remember that they were not processed and set as bounced) resulting in ESPs potentially blocking us.

Secondly, I should explain why the bounces were not processed. We set-up our initial campaign with Amazon SES as the sending node and activated delivery processing coming with it. However, the delivery reports from Amazon were not processed due to a bug in Mumara, which was eventually fixed. Anytime a delivery report from Amazon is not processed, it sends a fallback copy to a specified bounce email address. So that what it did with the 1.5k bounces/complaints.

Finally, what we want is to have those 1.5k bounces to be processed before we send a new campaign. We have the bounce email set-up in Mumara. However, Mumara will not process those bounces. Probably, it recognizes that campaign was sent with another set-up for bounce processing. We already tried some hacks with the database changing the value of smtp_ids and current_smtp columns in the campaign_schedules table with smtp_id column in the campaign_schedule_logs table. It didn't help. There was a thread here, where Mumara team recommended to the value of is_bounced column to 0 in the campaign_schedule_logs table. However, it is 0 already for all contacts there.

Could you please help with this? What do we need to do to force Mumara to process bounces for a campaign (btw it is on pause if it makes a difference) from a bounce email address rather than Amazon?

Thank you.
 

wasif

Administrator
Staff member
Apr 9, 2019
98
7
8
If you have a CSV file of all those bounced email addresses, you can simply use the Mumara Bulk Update tool under "Contacts" menu where you can upload the CSV file and set all email addresses as bounced.
 

wasif

Administrator
Staff member
Apr 9, 2019
98
7
8
And regarding the other question, if the broadcast is paused, it doesn't make any effect on bounce processing. That's a separate process!
 

agentlink

Beginner
Jan 10, 2020
4
0
1
If you have a CSV file of all those bounced email addresses, you can simply use the Mumara Bulk Update tool under "Contacts" menu where you can upload the CSV file and set all email addresses as bounced.
Unfortunately, we do not have a CSV file. All bounces and complaints from Amazon were sent to our bounce email address. They have different reasons and it will take lot of time to manually compile a CSV file from all those 1.5k emails. Taking into account that the cause was in the application's bug, we hope that you will provide some automated solution not involving a lot of manual work.
 

wasif

Administrator
Staff member
Apr 9, 2019
98
7
8
Mumara doesn't go beyond two days for bounce processing via POP/IMAP. Here is what we can do for now, we can include an option under application settings so you can choose the duration from when to process the bounces.
 

agentlink

Beginner
Jan 10, 2020
4
0
1
That would be just perfect!
Could you please make sure that FBL processing also works with that setting?
Thank you.
 

wasif

Administrator
Staff member
Apr 9, 2019
98
7
8
Yes it will reflect at all places running on Pop/Imap methods!
 

agentlink

Beginner
Jan 10, 2020
4
0
1
There is version 5.0.52 released. We updated, but cannot find the setting you mentioned. Was it implemented?
 

wasif

Administrator
Staff member
Apr 9, 2019
98
7
8
No it wasn't yet implemented. I still see it pipelined. Hopefully in next update!