Issue with deffered emails with Sendgrid Web Api

[bancomail]

Hello,
we successfully deliver our email campaign with Sendgrid, but we've noticed a mismatch in bounce reporting on MW.

As you probably know, Sendgrid retries to send deferred emails several times. Any failed attempt including the first, is marked as deferred. The process stops when SendGrid receive the last responce which can be 'delivered' or 'blocked'.

As far as we can see, Mailwizz receives the notification that email was deferred and marks contact as bounced in the compaign reports. Problem is that if an initially deffered email is successfully delivered after a few attempts (like in screenshot) , Mailwizz doesn't update the status of that contact and so the campaign still reports the contact as deferred and hence bounced. This distorts the true statistics of the compaign.

In processSendgrid function of DswhController.php (/apps/frontend/controllers/DswhController.php), we noticed that Mailwizz only handles this four types of notification:

1) dropped
2) deferred
3) bounce
4) spamreport

There is no processing of other types of notifications such as: Delivered or Processed.

How we can handle this issue?

Thanks in advance.

 

[twisted1919]

@bancomail - We don't look for Delivered / Processed events because it would hammer most of the servers with notifications we don't need eitherway.
Your point does make sense, but the only way to work around this is to simply don't take deferred into consideration anymore since we will anyway have a final notification if the email is for real non-deliverable.

 

[frm.mwz]

don't take deferred into consideration anymore since we will anyway have a final notification if the email is for real non-deliverable

+1

PS: Maybe @AHK 's extension can then help to resend?

 

[twisted1919]

Maybe @AHK 's extension can then help to resend?

It doesn't matter because the sending is anyway retried by sendgrid.

 

[frm.mwz]

It doesn't matter because the sending is anyway retried by sendgrid.

So if the final notification is for some non-deliverable (not bounced), e.g. GiveUp after many retires or so, then AHK's extension could be used to resend with another DS, which would seem like a great option, would that work?

 

[twisted1919]

So if the final notification is for some non-deliverable (not bounced), e.g. GiveUp after many retires or so, then AHK's extension could be used to resend with another DS, which would seem like a great option, would that work?

Yeah, but why bother using a 3rd-party when mailwizz itself will retry sending by its own from the upcoming version ?