Sign UP to My-Addr Project
My-Addr Project contact form (email verification service)
Server time: Thu 12:43 GMT
support:
Information
User menu
service secured by https
 
Lastest news:
09 Oct 2017
Bulk processing was very slow today (because of problem with dc), fixed.
25 Sep 2017
Some files was delayed after verification, fixed.
12 Sep 2017
Perfomance issue was fixed.
08 Sep 2017
Service is overloaded because of issue with DC, we working on it.
15 Aug 2017
Increased processing speed for "little" files.
02 Jul 2017
Improved processing for private domains that hosted by office365.
13 Jun 2017
We regenerated reports for files that was finished 1-2 days ago but with empty reports.
09 Jun 2017
Fixed bug with file canceling when file already taken by parser.
30 May 2017
Speed up of emails re-verification.
19 May 2017
Fixes for yahoo verification.
23 Apr 2017
Bulk processing: "pause" button was added.
04 Apr 2017
New SSL certificate for email-verify.my-addr.com and api.my-addr.com was not recognazed by some browsers, fixed.
21 Mar 2017
Major speed up and decreasing number of "unknown" results. "Bulk processing" queue continue to contains lots of files, it will take some time until files will be finished.
19 Feb 2017
Improved handling for some domains that will a little decrease % of unknown results.
04 Feb 2017
Fixes for "Get file info with API" documentation.
09 Jan 2017
00:30 GMT we rebooted claster and service was not accessible.
28 Dec 2016
Today, strating from 7:00 GTM until 9:30 GMT service was not accessible because of routing problem in data center. It is reason why some emails was marked with sub-status "dead_server" and status "fail". Pls make us know if you need to re-verify file for free.
26 Nov 2016
Our domain was not accessible for part of customers because of DNS issue, fixed.
25 Nov 2016
Bulk processing: speed increased to 15%.
23 Nov 2016
Fixes for AOL.com processing.
19 Nov 2016
Today Email verification working slower than usually, but it will work much more faster on Sunday.
16 Nov 2016
Added ability to get balance through API.
25 Oct 2016
We know that our service is heavy loaded and working on speed up it.
11 Oct 2016
Processing for emails that related to domains mail.ru/bk.ru/inbox.ru/list.ru/mail.ua restored but it is very slow.
30 Sep 2016
Now CSV parser will work even for files with extended data where "space" before or after email address.
13 Aug 2016
Important upgrade for descrease number of emails marked with "smtp_protocol" sub-status.
08 Aug 2016
Improved API for one-by-one verification, now you can also get "sub-status".
06 Aug 2016
Design of upload form is changed, not it must be compatible with biggest number of browsers.
26 Jul 2016
Fixed issue with slow parsing after yesterday's changes.
26 Jul 2016
Improved handling for some domains that will a little decrease % of unknown results.
14 Jul 2016
We changed DNS servers for better performance, pls make us know if something will going wrong.

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".
example of email verification
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:
"user1@email.com","ok"
"user2@email.com","fail"
"user3@email.com","unknown"
"user4@email.com","ok"
Status "ok" will be if three conditions will be true:
  • email service answer us that ready to receive letter
  • no antispam tricks in use
  • email service do not answering that any email is valid
Status "fail" will be if five conditions will be true:
  • email service answer us that will not receive letter to this email
  • server is down
  • smpt server working incorrect
  • no antispam tricks in use
  • email syntax is incorrect
Status "unknown" will be if two conditions will be true:
  • looking like antispam tricks in use
  • email service answering "valid" for any email
We do not take money for "unknown" emails.

 

Understanding of "valid" report

This report - it's all emails from "all" report where status is "ok". Row structure is "email@email.com", looking like:
"user1@email.com"
"user4@email.com"
 

Understanding of "detail" report

This newest type of report, created for advanced customers. Row structure is "email@email.com","substatus", looking like:
"user1@email.com","ok"
"user2@email.com","p_unknown_email"
"user3@email.com","t_attempt_rejected"
"user4@email.com","dead_server"
There are 13 sub-statuses, prefix "t_" or "p_" can be added to sub-status, so sub-statues in report can be with/without prefix.
List and description of sub-statuses:
  • "ok" - all is ok, server saying that ready to receive letter to this address and no tricks detected
  • "error" - server saying that delivery fail, but no information about email existing
  • "smtp_error" - smtp answer of server is invalid, destination server report us about some internal error
  • "smtp_protocol" - destination server allow us to connect, but smtp session was closed before email was verified
  • "unknown_email" - server saying that delivery fail and email not exist
  • "attempt_rejected" - delivery fail, reason similar to "rejected"
  • "relay_error" - delivery fail because relaying problem happens
  • "antispam_system" - some antispam technology blocking verification progress
  • "email_disabled" - email account is suspended/disabled/limited and can't receive emails
  • "domain_error" - email server for whole domain is not installed or incorrect, so all emails not deliverable
  • "ok_for_all" - email server saying that ready to accept letter to any email
  • "dead_server" - email server 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.
example of smtp that hard to verify
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.

Verify email list in two easy steps!

Copyright © 2007-2017 Email-Verify.My-Addr.com
Non-free services of My-Addr Project.
All rights reserved