Interpreting HexValidEmail results
HexValidEmail is a multi-level, server-side, bad-address
filter. When an email address passes this filter, however, it isn't
necessarily a good address. The following table summarizes what the
confidence rating does and does not tell you.
| |
Confidence
rating
(highest successful
validation level) |
0
Bad |
1
Syntx |
2
DNS |
3
SMTP |
A*
Cbak |
B*
Auth |
| Address is definitely bad for the
reason specified by the Error property |
Y |
|
|
|
|
|
| Syntax is OK |
|
Y |
Y |
Y |
Y |
Y |
| Domain exists |
|
|
Y |
Y |
Y |
Y |
| Domain has a working mail server |
|
|
|
Y |
Y |
Y |
| Mail server did not reject address |
|
|
|
Y |
Y |
Y |
| Local part (username) is valid on
destination system |
|
|
|
|
Y |
Y |
| Address reaches the recipient
you intend and thus is definitely good |
|
|
|
|
|
Y |
*A and B
Not supplied by HexValidEmail. These are optional tests that require actually
sending email and are something you would need to custom-develop for your
own system.
"Cbak" = "Callback", by which we mean sending
an email that contains an URL or reply address that the recipient can
use to indicate they received it.
"Auth" = Callback with authentication, which means a
sending a callback email that requires the recipient to enter their
password, thus verifying they are the intended recipient.
This
is the only way to determine an email address is definitely good.
|
