Search results

@twisted1919 Obviously, It is possible some anti-spam filters or recipient servers might employ spam filters or software to verify that an email, is in fact, safe for a human to open. So based on your confirmation, currently, mailwizz does not inherently decipher between legitimate and...

@twisted1919 why not implement Event Webhook because it will include the most amount of information on those engagement events. Here is an example of how reports those open events to the webhook: { "email": "example@test.com", "timestamp": 1513299569, "smtp-id"...

@twisted1919 Alternatively why not implement Event Webhook because it will include the most amount of information on those engagement events. Here is an example of how reports those open events to the webhook: { "email": "example@test.com", "timestamp": 1513299569, "smtp-id"...

@twisted1919 So, the conclusion from your response is that the mailwizz Geo IP detection metric feature is 100% inaccurate. What about the mailwizz mail open rate metric feature? accurate? if not, have you correctly implemented open rate solution like...

Hello, @twisted1919 We are using Maximind database to locate Geo of email opener following mailwizz kb document listed above, Unfortunately, discovered after running several testing that the GEO location indicated on the customer front end side (i.e.when clicking Geo open subtab under...

@twisted1919 Mailwizz is showing version 1.9.31 , is this the latest version? if so how one can verify quickly?