Contact List Sending Count Issue

which version you are running on? Seems like server/MySQL might have restarted in between. But Mumara won't send above 100%. It will fix the numbers automatically once the campaign is actually 100% finished. It was a case in one of the older editions but fixed in recent updates.
 
In the application, the sending numbers are increasing but no incoming on the PMTA side. We have the issue after the upgrade to the new version.
We do not have an issue with the spam, complaints, hard bounced, suppressed, inactive, unconfirmed.

Also, we are not starting the MySQL.
 
Still, the question is confusing. Are you having issue with starting MySQL or the sending stats counters? If you can provide me your Mumara and pmta details via ticket, I can look into it. What is the batch size set in application settings and how many threads you are using. If you have set a large batch size, remember it will make your server take a bite more than it can chew.
 
I have looked into your case and here is the story

Let me first explain you the Mumara behavior

In order to make the functionality fast, we have introduced a batch system that actually bypasses all queries to the database for a batch sent. e.g. if you have the batch size set to 100, it means Mumara will prepare a packet of 100 emails and do all MySQL operations upfront before sending the batch, i.e. it will also make a 100 increment for that campaign under sent and then push the emails to the MTA. Before starting the batch, Mumara verifies if the connection is successful or not. If it's not successful, Mumara doesn't increment anything and set the sending node as system-paused and then use the next sending node "if selected" for the same batch. If all sending nodes used for the campaign are failed, the campaign gets system-paused and then the settings applied to recheck the connectivity and resume broadcast (as set in application settings under campaigns tab). While sending a batch to MTA, if the MTA rejects any email in between for some reason, Mumara considers connection has been broken with MTA server and stops the batch right away thinking the SMTP has been failed instead of wasting the remaining emails in the batch. However, it has already incremented the batch size value into the sent counters but hasn't sent the incremented emails for the incremented counter. But when you go to broadcast stats and click on logs tab, it shows you 100% realtime and correct numbers. Also if you manually pause and resume the campaign it should also fix the counters. Moreover, when the campaign is auto resumed and then finishes, it auto fix the counters as well.


Now, what happened in your case???

While sending certain emails, Mumara got a failed response from your MTA as mentioned below

2020-08-10 10:59:13 SMTP -> get_lines(): $str is "550 5.7.1 recipient is in suppression list "sup1": in "RCPT TO:" "

So it seems like you have suppression list set at your MTA side or your MTA is blocking delivery to certain recipients either set by you or your MTA. And Mumara is considering it a connection failure and setting up your sending nodes as system-paused as soon as the response is received. And when it retries after every 30 minutes to self-establish the connection with the system-paused sending nodes, it gets a green signal and activates the sending nodes itself and resumes the system=paused campaign. But when it again starts sending, the same thing happens and everything gets system-paused again. But the increments keep happening and you see a bigger number in the stats that are coming from the counters tables but not an actual count. You can always see the actual count under the logs tab.


Resolution:

1- For now remove suppression list from the MTA side
OR
2- Synchronize your MTA suppression list with Mumara suppression list so Mumara skips the emails

Note: We are going to handle this exception in v5.1.06.3 that shouldn't set the sending nodes as system-paused and keep sending ahead
 
You must log in or register to reply here.
Back
Top