13 Jun 2017We regenerated reports for files that was finished 1-2 days ago but with empty reports.

Online email address verification results guide

Introduction

This short guide will help to understand our customers how to get maximum information from our email verification reports.
Bulk email verifier's result it's three CSV reports: "all","valid","detail".Attention: not all text editors of Windows displaying file correct, pls use WordPad editor instead of default Notepad.
If all emails in report going in one row, or more than one email address per row - it's wrong editor and not issue of our service.

Understanding of "all" report

This type of report consist of email address and status. It's row structure is "email@email.com","status", this is file of example.
In text editor it will looking like this:

"domain_error" - email server or dns for whole domain is not installed or incorrect, so all emails are not deliverable

"ok_for_all" - email server saying that ready to accept letter to any email

"dead_server" - email server is dead, no connection to it

"syntax_error" - syntax error in email address

"unknown" - email delivery fail but no information about reasons

Prefix "t_" mean "temporary", "p_" mean "permanent". Prefix very useful because giving additional information about situation:
"p_email_disabled" - it means that server say that email is permanently disabled
"t_attempt_rejected" - it can happens when server just overloaded, and temporary reject verification
"p_error" - no information about email existing, but no chance to deliver email in future too
"t_error" - no information about email existing, but there is some chance that email is alive.Sub-statuses with prefixes very powerful weapon for email results understanding and choosing email list for mailing.

Interesting facts for deeper understanding

There is only one method to be 100% sure that email address is really exist - send email letter.
There are no software or online tools in the world that can verify any email address 100% correct.
Why? Because it's theoretically impossible in case of some email services.
See example of unverifiable email service on scheme.
There is only one email verification method, it's called "SMTP verification", and it's based on data analysis in connection1.
So how "SMTP verification" can know that destination emails server will send bounce in second connection?
There are lots email servers that not compatible with smtp standards, so biggest part of software and online verification tools
giving fake results for it. Our service become one of the best verifiers because our verification based not only on standards,
it's based on large amount of experience.