Global Email V3:FAQ - Revision history

Admin at 19:07, 10 January 2020

2020-01-10T19:07:33Z

← Older revision		Revision as of 19:07, 10 January 2020
Line 35:		Line 35:

	;What are the verify result codes?		;What are the verify result codes?
	ES20, ES21, ES22, ES23, ES24 will tell you the level of validation ~~the email was verified to~~.		ES20, ES21, ES22, ES23, ES24 will tell you the level of validation used.

	;What are the error result codes?		;What are the error result codes?

Admin at 23:47, 23 May 2019

2019-05-23T23:47:14Z

← Older revision		Revision as of 23:47, 23 May 2019
Line 115:		Line 115:

	==What speeds can I expect from this web service?==		==What speeds can I expect from this web service?==
	The speed of the service depends on the mode (Express, Premium), protocol (~~SOAP,~~ REST, JSON, XML) and the number of threads/Machine spec.		The speed of the service depends on the mode (Express, Premium), protocol (REST, JSON, XML) and the number of threads/Machine spec.
	Sometimes increasing the number of threads will slow down your process due to machine constraints.		Sometimes increasing the number of threads will slow down your process due to machine constraints.

	;Verify Mailbox<nowiki>:</nowiki> Express		;Verify Mailbox<nowiki>:</nowiki> Express
	*You can expect 144,000 - 153,000 validations per hour single threaded.		[[File:WS_GlobalEmailV3_Speed-Express.png]]
	*You can expect 191,000 - 217,000 validations per hour with 5 threads.

	[[File:~~WS_GlobalEmail_Throughput~~-~~FAST~~.png~~\|800px~~]]

	;Verify Mailbox<nowiki>:</nowiki> Premium		;Verify Mailbox<nowiki>:</nowiki> Premium
	*You can expect 15,000 - 16,000 validations per hour single threaded.		[[File:WS_GlobalEmailV3_Speed-Premium.png]]
	*You can expect 45,000 - 79,000 validations per hour with 5 threads.

	[[File:~~WS_GlobalEmail_Throughput~~-~~REALTIME~~.png~~\|800px~~]]


	[[Category:FAQ]]		[[Category:FAQ]]
	[[Category:Global Email V3]]		[[Category:Global Email V3]]

Admin: Admin moved page Global Email:FAQ to Global Email V3:FAQ without leaving a redirect

2019-05-23T17:23:30Z

Admin moved page Global Email:FAQ to Global Email V3:FAQ without leaving a redirect

← Older revision	Revision as of 17:23, 23 May 2019
(No difference)

Admin at 17:23, 23 May 2019

2019-05-23T17:23:19Z

← Older revision		Revision as of 17:23, 23 May 2019
Line 1:		Line 1:
	[[Global Email\|← Global Email]]		[[Global Email V3\|← Global Email V3]]
	__FORCETOC__		__FORCETOC__
	==What Features does it have?==		==What Features does it have?==
	*[[Global Email:Introduction#Summary\|Functions and Capabilities]]		*[[Global Email V3:Introduction#Summary\|Functions and Capabilities]]

	==Available as==		==Available as==
Line 129:		Line 129:

	[[File:WS_GlobalEmail_Throughput-REALTIME.png\|800px]]		[[File:WS_GlobalEmail_Throughput-REALTIME.png\|800px]]




	[[Category:FAQ]]		[[Category:FAQ]]
	[[Category:Global Email]]		[[Category:Global Email V3]]

Admin at 18:13, 4 November 2016

2016-11-04T18:13:40Z

← Older revision		Revision as of 18:13, 4 November 2016
Line 81:		Line 81:
	==TimeToWait Option==		==TimeToWait Option==
	;What exactly does this do? What number should I be using?		;What exactly does this do? What number should I be using?
	TimeToWait is our newest option designed to give you more control over the process flow. It’s up to you and your team to decide if this option is necessary for you to use. The minimum value for this option is '''5 seconds''', while the maximum value is '''45 seconds'''. The Default value is set to '''25 seconds'''. Setting TimeToWait to a lower number will give you faster, but less accurate results. On the ~~higher~~ hand, setting this value to a higher number will give you slower, but more accurate results. It’s up to you and your team to decide what you value more for each project – accuracy or speed. We recommend running a small test batch with a large variety of your emails at different TimeToWait settings. Every ‘ideal number’ will be different; and may change dependent on your email batch. The best way to find your ‘ideal number’ is to get a good spread across your email data base, and test that sample selection at different TimeToWait settings until you find the number that gives you the most accurate results in an acceptable time.		TimeToWait is our newest option designed to give you more control over the process flow. It’s up to you and your team to decide if this option is necessary for you to use. The minimum value for this option is '''5 seconds''', while the maximum value is '''45 seconds'''. The Default value is set to '''25 seconds'''. Setting TimeToWait to a lower number will give you faster, but less accurate results. On the other hand, setting this value to a higher number will give you slower, but more accurate results. It’s up to you and your team to decide what you value more for each project – accuracy or speed. We recommend running a small test batch with a large variety of your emails at different TimeToWait settings. Every ‘ideal number’ will be different; and may change dependent on your email batch. The best way to find your ‘ideal number’ is to get a good spread across your email data base, and test that sample selection at different TimeToWait settings until you find the number that gives you the most accurate results in an acceptable time.

	For more information, see [[#ES03’s and TimeToWait\|ES03’s and TimeToWait]].		For more information, see [[#ES03’s and TimeToWait\|ES03’s and TimeToWait]].

Admin at 23:05, 3 November 2016

2016-11-03T23:05:20Z

@@ Line 78: / Line 78: @@
 ;What are the differences between the different modes (Express, Premium)?
 [[Global Email:Request#Options|Verify Mailbox Options]]
 =='Good' Email==

Admin at 22:47, 29 August 2016

2016-08-29T22:47:49Z

← Older revision		Revision as of 22:47, 29 August 2016
Line 1:		Line 1:
	[[Global Email\|← Global Email]]		[[Global Email\|← Global Email]]
	__FORCETOC__		__FORCETOC__

	==What Features does it have?==		==What Features does it have?==
	*[[Global Email:~~Functions and Capabilities~~\|Functions and Capabilities]]		*[[Global Email:Introduction#Summary\|Functions and Capabilities]]

	==Available as==		==Available as==
Line 44:		Line 43:

	;Why should client use email 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 a form of spammers list). 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).		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 a form of spammers list). 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 spam traps, 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 an accept all mail server?		;What is an accept all mail server?
Line 51:		Line 50:
	;When should client use premium or express?		;When should client use premium or express?
	Premium		Premium
	*Should definitely be used for any email marketing campaign or where having the right email in a web form is completely necessary for it to function.		*Should definitely be used for any email marketing campaign or where having the right email in a web form is completely necessary for it to function.

	Express		Express
	*Can be used for simple web forms where it would be nice to have a correct email but it isn't absolutely of ~~upmost~~ importance or if there are no consequences for a bad email in ~~realtime~~. You can validate with premium mode in post batch processing.		*Can be used for simple web forms where it would be nice to have a correct email but it isn't absolutely of utmost importance or if there are no consequences for a bad email in real-time. You can validate with premium mode in post batch processing.

	;What is the difference between mailbox and normal email validation?		;What is the difference between mailbox and normal email validation?
Line 77:		Line 77:
	==Verify Mailbox Option==		==Verify Mailbox Option==
	;What are the differences between the different modes (Express, Premium)?		;What are the differences between the different modes (Express, Premium)?
	[[Global Email ~~Web Service~~:Options\|Verify Mailbox Options]]		[[Global Email:Request#Options\|Verify Mailbox Options]]

	=='Good' Email==		=='Good' Email==
Line 88:		Line 88:

	=='Unknown' Email==		=='Unknown' Email==
	;What is a unknown email?		;What is an unknown email?

	~~Unknown~~ email will return a ES03. With mailbox validation even if it's an unknown email, we want to let you know that it's with high certainty that it's an unknown email and that we did try request to the mail server for a mailbox validation call on this email.		An unknown email will return a ES03. With mailbox validation even if it's an unknown email, we want to let you know that it's with high certainty that it's an unknown email and that we did try request to the mail server for a mailbox validation call on this email.

	Here are some examples of unknown emails, the mail server for some reason during the mail validation call, triggered our ES03 code either by responding with a non standardized response, or the mail server is increasingly aggressive with their protection to the point where IP address block might be implemented against our system if we continue or mail server tells us that we need to send a message to receive a bounce code (actually performing this could cause IP Block) or Grey Listing technology has been detected (we could not proceed). Another possible ~~resason~~, is that the mail server the email resides on is timing out. There are too many to list and some are proprietary in nature. ES03 is meant to convey "at this moment in time, the email's status cannot be determined", email statuses are always in flux and it could change if you were to do another check.		Here are some examples of unknown emails, the mail server for some reason during the mail validation call, triggered our ES03 code either by responding with a non standardized response, or the mail server is increasingly aggressive with their protection to the point where IP address block might be implemented against our system if we continue or mail server tells us that we need to send a message to receive a bounce code (actually performing this could cause IP Block) or Grey Listing technology has been detected (we could not proceed). Another possible reason, is that the mail server the email resides on is timing out. There are too many to list and some are proprietary in nature. ES03 is meant to convey "at this moment in time, the email's status cannot be determined", email statuses are always in flux and it could change if you were to do another check.

	Some mail servers are friendly and some are hostile. We will try to do mailbox validation on all mailboxes. Hostile mail servers have been developing countermeasure technologies to fight detection services like ours. It is a constant warfare for countermeasures and detection technologies. As they constantly develop their technologies...we constantly develop ours. So sometimes, for a certain email, mail server's algorithm at the mailbox validation level did a better job countering our algorithm's moves which results in a ES03.		Some mail servers are friendly and some are hostile. We will try to do mailbox validation on all mailboxes. Hostile mail servers have been developing countermeasure technologies to fight detection services like ours. It is a constant warfare for countermeasures and detection technologies. As they constantly develop their technologies...we constantly develop ours. So sometimes, for a certain email, mail server's algorithm at the mailbox validation level did a better job countering our algorithm's moves which results in a ES03.

Oscar: /* Result Codes */

2015-09-16T00:38:16Z

Result Codes

← Older revision		Revision as of 00:38, 16 September 2015
Line 27:		Line 27:

	;What are the primary result codes?		;What are the primary result codes?
	ES01, ES02, ES03 will tell you the primary status of the email.		ES01, ES02, ES03 will tell you the primary status of the email. Good, Bad, or Unknown respectively.

	;What are the secondary result codes?		;What are the secondary result codes?

Oscar: /* Result Codes */

2015-09-16T00:37:58Z

Result Codes

← Older revision		Revision as of 00:37, 16 September 2015
Line 30:		Line 30:

	;What are the secondary result codes?		;What are the secondary result codes?
	ES04, ES05, ES06, ES07, ES08, ~~ES10, ES11, ES12, ES13, ES23~~ will tell you additional information about the email.		ES04, ES05, ES06, ES07, ES08, ES09 will tell you additional vital information about the email.

	;What are the ~~validation~~ result codes?		;What are the correction result codes?
	ES20, ES21, ES22, ES23 will tell you the level of validation the email was verified to.		ES10, ES11, ES12, ES13 will tell you if anything in the email has been updated or corrected.

			;What are the verify result codes?
			ES20, ES21, ES22, ES23, ES24 will tell you the level of validation the email was verified to.

	;What are the error result codes?		;What are the error result codes?
	EE01, EE02, EE03, EE04 will tell you what was wrong with the email.		EE01, EE02, EE03, EE04 will tell you what was wrong with the email. So you will frequently see ES02, EEXX grouped together

	==Mailbox Validation==		==Mailbox Validation==

Oscar: /* 'Unknown' Email */

2015-09-14T21:31:59Z

'Unknown' Email

← Older revision		Revision as of 21:31, 14 September 2015
Line 89:		Line 89:
	Unknown email will return a ES03. With mailbox validation even if it's an unknown email, we want to let you know that it's with high certainty that it's an unknown email and that we did try request to the mail server for a mailbox validation call on this email.		Unknown email will return a ES03. With mailbox validation even if it's an unknown email, we want to let you know that it's with high certainty that it's an unknown email and that we did try request to the mail server for a mailbox validation call on this email.

	Here are some examples of unknown emails, the mail server for some reason during the mail validation call, triggered our ES03 code either by responding with a non standardized response, or the mail server is increasingly aggressive with their protection to the point where IP address block might be implemented against our system if we continue or mail server tells us that we need to send a message to receive a bounce code (actually performing this could cause IP Block) or Grey Listing technology has been detected (we could not proceed). There are too many to list and some are proprietary in nature.		Here are some examples of unknown emails, the mail server for some reason during the mail validation call, triggered our ES03 code either by responding with a non standardized response, or the mail server is increasingly aggressive with their protection to the point where IP address block might be implemented against our system if we continue or mail server tells us that we need to send a message to receive a bounce code (actually performing this could cause IP Block) or Grey Listing technology has been detected (we could not proceed). Another possible resason, is that the mail server the email resides on is timing out. There are too many to list and some are proprietary in nature. ES03 is meant to convey "at this moment in time, the email's status cannot be determined", email statuses are always in flux and it could change if you were to do another check.

	Some mail servers are friendly and some are hostile. We will try to do mailbox validation on all mailboxes. Hostile mail servers have been developing countermeasure technologies to fight detection services like ours. It is a constant warfare for countermeasures and detection technologies. As they constantly develop their technologies...we constantly develop ours. So sometimes, for a certain email, mail server's algorithm at the mailbox validation level did a better job countering our algorithm's moves which results in a ES03.		Some mail servers are friendly and some are hostile. We will try to do mailbox validation on all mailboxes. Hostile mail servers have been developing countermeasure technologies to fight detection services like ours. It is a constant warfare for countermeasures and detection technologies. As they constantly develop their technologies...we constantly develop ours. So sometimes, for a certain email, mail server's algorithm at the mailbox validation level did a better job countering our algorithm's moves which results in a ES03.