We are pleased to announce the release of the long awaited Global Email V4 Service worldwide. This announcement is Europe-specific and is part of our ongoing effort to provide all our customers around the world with access to the same new and improved version of Global Email.
Compared to V3, the new Global Email V4 brings new and improved algorithms to improve accuracy with Accept All* emails (indicated by Melissa result code ES07) and various other types of domain that are considered problematic in the field of email verification. In addition, we added new fields to V4’s results, as well as a new request option.
*Accept All: We were able to verify that the MX server is active, but we were unable to verify the mailbox due to the way the recipient setup their MX server.
How to Access Global Email V4
V4 is available now (v4.0.0.10). In order to begin using it, please change the request URL as following:
- V3: https://globalemail.melissadata.net/v3/WEB/GlobalEmail/doGlobalEmail…
- V4: https://globalemail.melissadata.net/v4/WEB/GlobalEmail/doGlobalEmail…
Importance Notice about Backwards Compatibility V3 & V4:
It is important to note that Version 4 no longer uses the ES02 result code. Instead, invalid emails will be indicated only by the existing EE## result codes. If your code uses only ES02 to find invalid emails, V4 will break compatibility.
For example: EE04,ES02,ES22 would be shortened to EE04,ES22
If you already use only the EE## codes when checking our results, no action is needed. Otherwise, please make the necessary changes to properly interpret EE## codes and to account for the removal of the ES02 result code.
Improvements
- Accuracy has improved by up to 75% for Accept All Emails
- General speed and performance improvements
Additions
- New field “MXServer”
- New field “DeliverabilityConfidenceScore”
- New field “PrivacyFlag”
- New request option WhoIsLookup
- Various new fields related to this – see the example at the end of this document
Accept All Emails
Version 3 could only identify Accept All domains, as they are set up in a way that does not allow us to verify the mailbox due to restrictions set by the MX Server. Even with a valid Accept All email, trying to send an email to such an address was a gamble. Several large email providers have most or all of their emails come back as Accept All, such as Yahoo, AOL, and Verizon.
By leveraging new techniques and methods, Version 4 will provide more accurate and informative results – meaning more valid and invalid results – for up to 75% of Accept All emails. This means that users will be able to keep or discard more emails with more confidence.
Examples of popular domains that will generate more accurate results:
- Aol.com
- Hotmail.com
- Yahoo.com
- Verizon.com
- “.edu” domains
New Request Option
WhoIsLookup
This option is enabled by default at no extra cost. To disable WhoIs Lookup, add the follow option to the REST request:
Version 4 comes with WhoIs integration. This new option appends information about the domain from WhoIs, such as when the domain was created or registered and contact information for the company that owns the domain.
If you do not need Whois information and would like to optimize for faster validation speeds, simply disable by setting WhoIsLookup:OFF.
New Result Fields
DeliverabilityConfidenceScore
Deliverability Confidence Score is a feature that determines the probability of your email making it into the mailbox of the recipient. This score is especially useful for marketing campaigns in which high volume of emails are being sent out in a short amount of time.
The deliverability confidence score can greatly simplify how you interpret our results. As shown in the following table, you can simply partition the 0-100 range into three parts, and use emails based on a simple numerical scale.
Recommendation:
| Deliverability Score | Recommendation |
| 0 to 30 | Do not send. |
| 31 to 60 | Email delivery not guaranteed. |
| 61 to 100 | Send mail. There is a high chance of email delivery success. |
MXServer
Note: this field is only available with Premium mode.
The MX server (Mail eXchange server) is the server that handles receiving emails for a given domain. This field is somewhat specialized. Users can use this field as part of a more granular valid-invalid verdict on an email, or to better identify and avoid problematic emails from problematic email providers.
PrivacyFlag
This flag indicates if an email may be located in a country that might be affected by any additional privacy regulations, such as GDPR. This flag is intended to help your organization to ensure compliance when emailing to privacy sensitive emails.
Possible values are “Y” or “N” (“yes” or “no”).
Domain fields related to WhoIsLookup
Other than the existing DomainName, any field that starts with the word Domain is returned from WhoIsLookup – DomainAgeEstimated, etc.
Please see our wiki for descriptions of each WhoIs-related field:
http://wiki.melissadata.com/index.php?title=Global_Email%3AResponse
V4 Response Example:
New fields handled by Melissa are in bold red. All new fields in bold blue are returned by WhoIsLookup.
{
"Version": "4.0.0.10",
"TransmissionReference": "",
"TransmissionResults": " ",
"TotalRecords": "1",
"Records": Array[1][
{
"RecordID": "1",
"Results": "ES01,ES21",
"DeliverabilityConfidenceScore": "85",
"EmailAddress": "[redacted]@yahoo.com",
"MailboxName": "[redacted]",
"DomainName": "yahoo",
"TopLevelDomain": "com",
"TopLevelDomainName": "Commercial",
"DateChecked": "7/13/2020 10:45:12 PM",
"DomainAgeEstimated": "9308",
"DomainExpirationDate": "2023-01-19T05:00:00",
"DomainCreatedDate": "1995-01-18T08:00:00",
"DomainUpdatedDate": "2019-12-18T13:45:43",
"DomainEmail": "domain-admin@oath.com",
"DomainOrganization": "Oath Inc.",
"DomainAddress1": "22000 AOL Way",
"DomainLocality": "Dulles",
"DomainAdministrativeArea": "VA",
"DomainPostalCode": "20166",
"DomainCountry": "UNITED STATES",
"DomainCountryCode": "US",
"DomainAvailability": "UNAVAILABLE",
"DomainPrivateProxy": " ",
"PrivacyFlag": "N",
"MXServer": "mta5.am0.yahoodns.net"
}
]
}
|
If you have any questions regarding this update, please contact us at Melissa Tech Support.