[DBTech] DragonByte Mail

[DBTech] DragonByte Mail [Paid] 5.2.0

No permission to buy (€14.95)
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.
 
Last edited:
In what order are the accounts validated? I see there is a significant difference in results between validation services.
 
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.
 
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.
 
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.
 
DragonByte Tech updated [DBTech] DragonByte Mail with a new update entry:

5.1.0 "Gold"

Update highlights​

This version makes a minor change to the "Maintenance" page's admin permission checks, as well as preparing for the upcoming XenForo v2.3.8.

Previous v5.1.0 Beta builds contained an important fix for sites using the "Max mails per hour" setting!

See previous change logs for more information.


Complete Change Log​

Change: Apply the correct admin permission to the "Maintenance" page
Change: Move database query...

Read the rest of this update entry...
 
I'm currently comparing various email validation services results and finding out that some email validation results require rechecks. Specifically:
  • Inbox full (currently invalid)
  • Unknown
This makes perfect sense because if an inbox is full, then the inbox will be valid once the recipient removes some emails. It's worth noting that both these validation results make up a significant percentage of total validation issues.

How is this addon handling these two types of validation results?
 
Small suggestion that would be handy:
 
@DragonByte Tech
"has_inbox_full":=true is registered as a hard bounce. This is incorrect. It is a soft bounce. XenForo correctly handles it as such and your software normally does so as well.
The SES bounce processing functionality that you implemented for me also handles inbox_full as a soft bounce. Such accounts should not be set to invalid, because in most cases these clear up after some time. Setting account status to invalid, means the account will never be validated again, so the situation will not be corrected this way.

Inbox full makes up a significant amount of failures.
I have checked out how the plugins of email validating services handle it and they either mark it as valid (if there are no other issues) or they provide a setting in their WordPress plugins to make an exception.

Please rectify this issue, because it leads to a significant number of valid accounts being set to invalid user status.
 
@DragonByte Tech
"has_inbox_full":=true is registered as a hard bounce. This is incorrect. It is a soft bounce. XenForo correctly handles it as such and your software normally does so as well.
The SES bounce processing functionality that you implemented for me also handles inbox_full as a soft bounce. Such accounts should not be set to invalid, because in most cases these clear up after some time. Setting account status to invalid, means the account will never be validated again, so the situation will not be corrected this way.

Inbox full makes up a significant amount of failures.
I have checked out how the plugins of email validating services handle it and they either mark it as valid (if there are no other issues) or they provide a setting in their WordPress plugins to make an exception.

Please rectify this issue, because it leads to a significant number of valid accounts being set to invalid user status.
Only one validator (Reoon) makes a distinction between inbox full and other validation errors as far as I can tell, is this the validator you're using?

EDIT: I found a few more not so straightforward ways to obtain that information for the following validators:
  • CaptainVerify
  • Emailable
  • Reoon
  • UseBouncer

The other validators not listed do not appear to provide the required information, as the word full does not appear in their API docs.
 
Last edited:
I'm indeed using Reoon on XF and WP. On WP they have settings in the plugin to control how to handle inbox_full.
Emailable also makes the distinction. Check here:
ZeroBounce completely ignores inbox_full and marks such accounts as Valid.
Services like Bouncer do take it into account, but mark the address as Risky, but Valid.

The above services have a major advantage over services that incorrectly label inbox full as a hard_bounce / invalid.
 
DragonByte Tech updated [DBTech] DragonByte Mail with a new update entry:

5.1.1

Update highlights​

This version updates some of the validation APIs to log "Inbox full" as a soft bounce rather than a hard bounce.

Furthermore, this version updates the various log pages to allow search criteria to persist when clicking back into the search form.


Complete Change Log​

Change: CaptainVerify, Emailable, Reoon and UseBouncer can now log "inbox full" as a soft bounce
Change: Criteria are now carried over when clicking the...

Read the rest of this update entry...
 
Back
Top Bottom