Global Email V3:FAQ

← Global Email Web Service

Required Fields

Mandatory:

• CustomerID - "Your License Key"
• Email - "Email to validate"

Optional:

• RecordID = "Internal Reference"
• TransmissionReference = "Internal Reference"
• Options = "Options to set"

Mailbox Validation

Why should client use email validation?

To reduce bounce rates (rejection) and avoid being labeled a spammer from mail servers. Once you are blacklisted, your email deliverability campaigns will suffer a lot and you have trouble sending out emails in the future (most mail servers subscribe to some list of spammer). Integrators should consult with us to in order to understand what they need to look out for to avoid a bad campaign and why certain emails should be flagged/inspected. Even if you avoid Spamtraps, sending out too many invalid emails will cause the mail server to flag you as a potential spammer (which is why mailbox validation is important).

What is the difference between mailbox and normal email validation?

Currently, our email object only performs normal email validation which is essentially just a simple spell check, mail server and domain check. Our Global Email Web Service does both mailbox and normal email validation. Mailbox validation means that the mailbox in the mail server is actually active and exists.

What is mailbox validation?

Mailbox validation is more comprehensive beyond than a MX Domain check. Mailbox validation actually asks the mail server to see if that mailbox account is active and if it exists. Otherwise we will only check to see if the mail server is active and if the mail server exists.

Why does an email have no mailbox validation?

Mailbox validation will only occur if the ES01 result code is returned and if options are set.

What does mailbox validation do?

It performs what is known as an SMPT check in the industry. Our service avoids being labeled as spammers for performing this check through proprietary technology. Your emailing reputation will be safe since we are the ones doing the mailbox checks for them. Of course, your emailing reputation will depend on our results when you start your email campaign on your end.

Verify Mailbox Option

What are the differences between the different modes (OFF, MIXED, FAST, REALTIME)?

Verify Mailbox Options

Unicode

All emails that are unicoded are detected and will return a ES23 result code as well

Validation: Mailbox Vs. Domain

What is the difference between mailbox validation and domain validation?

Mailbox validation confirms that the email account is valid (e.g. "email@gmail.com") while domain validation only verifies that the domain (e.g. "gmail.com") is valid.

What speeds can I expect from this webservice?

The speed of the service depends on the mode (OFF, MIXED, FAST, REALTIME), protocol (SOAP, REST, JSON, XML) and the number of threads.

Verify Mailbox: OFF

• You can expect 119,000 - 171,360 validations per hour single threaded.
• You can expect 206,000 - 248,000 validations per hour with 5 threads.

Verify Mailbox: MIXED

• You can expect 80,000 - 84,000 validations per hour single threaded.
• You can expect 131,000 - 135,000 validations per hour with 5 threads.

Verify Mailbox: FAST

• You can expect 144,000 - 153,000 validations per hour single threaded.
• You can expect 191,000 - 217,000 validations per hour with 5 threads.

Verify Mailbox: REALTIME

• You can expect 15,000 - 16,000 validations per hour single threaded.
• You can expect 45,000 - 79,000 validations per hour with 5 threads.

'Good' Email

What is a good email?

A good email consists of valid characters for the mailbox name, an '@' symbol, and a valid domain name. If mailbox validation option is set, a good email consist of valid characters, valid domain name, and active/existing mailbox account on that mail server.