[DBTech] DragonByte Mail [Paid] 5.1.0b2

[Alpha1]

Are statistics available somewhere? If not then it would be nice to add to admin statistics. i.e.
Accounts: 500k
Validated: 200k
Bounced: 80k
Banned: 30k
Need to be validated: 190k

Or something like that.

 

[DragonByte Tech]

Are statistics available somewhere?

There's no such statistics at this time, and there wouldn't really be a reliable way of fetching them either as the validation log is pruned at regular intervals.

 

[Alpha1]

I will need to provide proof to Amazon AWS that all emails have been validated.

 

[DragonByte Tech]

I will need to provide proof to Amazon AWS that all emails have been validated.

Then your best bet is to export the log from your validation service, as any numerical statistic like that above does not constitute proof of anything.

 

[Alpha1]

In what order are the accounts validated? I see there is a significant difference in results between validation services.

 

[DragonByte Tech]

In what order are the accounts validated? I see there is a significant difference in results between validation services.

I don’t believe I apply any specific ordering so presumably in order by user ID ascending, but I don’t know.

 

[Alpha1]

It seems like its in random order, so that would not explain the difference in results. I'd expect that older accounts or accounts that have not logged in for some time will have a higher percentage of invalid email addresses. But I guess that's not it and it comes down to how the individual provider handles / qualifies the results. I'm beginning to see some differences in that respect.

 

[Alpha1]

BTW: I don't think validating by cron or manually is feasible for userbases larger than a few thousand. The cron runs 6 times per day and validates 25 addresses per run, so 150 per day. Thats 4500 per month. We have hundreds of thousands of accounts. I can do that trough CLI, though that is still quite slow as it uses single checks instead of bulk checking trough API. The API response speed differs quite a lot between providers.

Monthly subscriptions of some providers are much cheaper than prepaid credits. This can safe hundreds of bucks. But these subscriptions often limit the number of validations per day to a certain number of thousands per day. Which means that we would need to run CLI every day for many weeks.

I'm really happy that you've added this functionality. If its possible to implement bulk/batch API checks instead of single checks then that would make it much easier to use.

 

[DragonByte Tech]

If its possible to implement bulk/batch API checks instead of single checks then that would make it much easier to use.

No. Bulk checks don't return results in the normal way, they send you an email when the results are ready, so you would be manually handling thousands of emails.

Furthermore, it doesn't save any credits as it still counts 1 email = 1 lookup.