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.Are statistics available somewhere?
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.I will need to provide proof to Amazon AWS that all emails have been validated.
I don’t believe I apply any specific ordering so presumably in order by user ID ascending, but I don’t know.In what order are the accounts validated? I see there is a significant difference in results between validation services.
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.If its possible to implement bulk/batch API checks instead of single checks then that would make it much easier to use.
@DragonByte Tech please look into this.I've had to have this addon removed from multiple sites, as it caused the xf_job table to grow to over 250GB
RTFCL (Read The Fabulous Change Log)@DragonByte Tech please look into this.
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...
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?@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.
full
does not appear in their API docs.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...
We use essential cookies to make this site work, and optional cookies to enhance your experience.