Global Email:FAQ - Revision history

Admin at 18:14, 8 November 2024

2024-11-08T18:14:01Z

← Older revision		Revision as of 18:14, 8 November 2024
Line 107:		Line 107:

	The email provider tells external verifiers that any email is valid and active, and even accepts all incoming emails as if the mailbox is valid and active, regardless of what may actually be the case. Because of this, sending emails to such addresses is essentially a gamble. We are constantly improving our accuracy with these emails.		The email provider tells external verifiers that any email is valid and active, and even accepts all incoming emails as if the mailbox is valid and active, regardless of what may actually be the case. Because of this, sending emails to such addresses is essentially a gamble. We are constantly improving our accuracy with these emails.

			;How does Melissa verify accept-all emails?

			Our Predictive Accept-All Verification uses a proprietary, innovative method to validate accept-all emails by analysing them for signs of historical activity. This analysis is integrated into our Deliverability Confidence Score, providing a reliable indication of whether an email to an accept-all address is likely to reach its intended recipient.

	;Why does accept-all get its own result code?		;Why does accept-all get its own result code?

Admin at 00:53, 24 February 2022

2022-02-24T00:53:01Z

Admin at 22:25, 23 February 2022

2022-02-23T22:25:24Z

← Older revision		Revision as of 22:25, 23 February 2022
Line 137:		Line 137:

	==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 (REST, JSON, XML) and the number of threads/Machine spec~~.		The Global Email Web Service is split to two major option types: Express, Premium.
	~~Sometimes increasing~~ the ~~number~~ of ~~threads~~ will ~~slow down your process due~~ to ~~machine constraints~~.		These options drastically vary in performance due to the nature of the service. Express will usually return a higher throughput by returning results based on cached data while Premium involves a real time check to an MX Server to validate an email address. There are other factors that will impact performance so the throughputs may vary depending on the use case.

	~~;Verify Mailbox<nowiki>~~:~~</nowiki> Express~~		Factors impacting performance:
	~~[[File:WS_GlobalEmailV4_Speed-Express.png]]~~

	;~~Verify Mailbox<nowiki>~~:</~~nowiki> Premium~~		*VerifyMailBox Options Express vs. Premium
	~~[[File:WS_GlobalEmailV4_Speed~~-Premium~~.png]]~~		**Selecting Express or Premium options will be the greatest factor impacting performance
			**Premium will have slower speeds due to real time validation
			*Number of threads used for sending requests to the service:
			**We recommend 10 threads for processing
			*TimeToWait
			**Default setting is 25 seconds per request. Setting this lower will give you faster performance but may affect accuracy. Setting this higher will do the opposite; slower performance and possible higher accuracy
			*Data Quality
			**The quality of data sent to the service can affect the performance substantially
			**Premium real time checks will wait for a response from an MX server. If there are issues with a domain, TimeToWait may hit its maximum, increasing processing time
			*WhoIsLookup
			**Activating this option will allow domain information lookups which has a small performance impact

			With these variations, you can expect these approximate throughput rates:

			{\| class="alternate01"
			!VerifyMailBox Option!!Throughput (records / hour)
			\|-
			\|Express\|\|150,000 - 250,000
			\|-
			\|Premium\|\|40,000 - 100,000
			\|}


	[[Category:FAQ]]		[[Category:FAQ]]
	[[Category:Global Email V4]]		[[Category:Global Email V4]]

Admin at 16:51, 26 August 2020

2020-08-26T16:51:49Z

← Older revision		Revision as of 16:51, 26 August 2020
Line 1:		Line 1:
	~~[[Global Email~~\|~~← Global Email]]~~		{{GlobalEmailV4Nav
	~~__FORCETOC__~~		\|BasicsCollapse=
			}}

			{{CustomTOC}}

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

Admin at 21:00, 10 August 2020

2020-08-10T21:00:35Z

← Older revision		Revision as of 21:00, 10 August 2020
Line 24:		Line 24:

	==Deliverability Confidence Score==		==Deliverability Confidence Score==
	Deliverability ~~Confidence Score represents the probability, from 0~~ to ~~100%, of your email making it~~ to ~~the recipient’s mailbox. This field can~~ be ~~used as~~ a simple ~~check~~ to ~~determine if you want to send to an email (see the table below)~~.		Deliverability confidence score was added to Global Email V4. It is intended to be a quick and simple way to interpret and use our results. Please see [[Global Email:Deliverability Confidence Score\|Deliverability Confidence Score]] for more information.

	Please note that not all valid emails, i.e. emails that have result code ES01, have a deliverability confidence score of 100. The same myriad factors that are used in determining our result codes are reflected in this new score.

	~~Our recommendations for using~~ Deliverability Confidence Score:

	{\| ~~class="alternate01 sortable"~~
	!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.~~
	\|}


	~~We believe this new field is especially useful~~ for marketing campaigns involving a high volume of emails sent out in a short amount of time. We recommend that emails with lower scores be sent out at a slower rate as they have a higher chance of a missed delivery due to external factors. Continuously sending emails out to emails with low deliverability scores is likely to lead to blacklisting, high bounce rates, and being flagged as spam by email providers.


Line 53:		Line 36:
	Any EE code means the email is in some way invalid. Since we have removed the old result code ES02 from Version 4, invalid emails will only have EE codes and either ES21 or ES22.		Any EE code means the email is in some way invalid. Since we have removed the old result code ES02 from Version 4, invalid emails will only have EE codes and either ES21 or ES22.

	~~Please~~ refer to ~~the full table of result codes here:~~ [[~~Result Code Details#~~Global Email\|~~Global Email~~ Result ~~Code Details~~]].		For more information on our result codes and how to use them, please refer to [[Global Email:Result Codes\|Result Codes (Advanced)]].


Line 117:		Line 100:
	;What is an accept-all email?		;What is an accept-all email?

	Accept-all (indicated by result code ES07) means that the email provider sets up their servers in a way that makes them relatively opaque to external email ~~validators~~. A ~~validator~~ will be able to perform a normal syntax check and determine if the domain is valid and active.		Accept-all (indicated by result code ES07) means that the email provider sets up their servers in a way that makes them relatively opaque to external email verifiers. A verifier will be able to perform a normal syntax check and determine if the domain is valid and active.

			The email provider tells external verifiers that any email is valid and active, and even accepts all incoming emails as if the mailbox is valid and active, regardless of what may actually be the case. Because of this, sending emails to such addresses is essentially a gamble. We are constantly improving our accuracy with these emails.

			;Why does accept-all get its own result code?

			Accept-all emails are generally problematic, but perhaps the most problematic for large email marketing campaigns. Without a way to identify accept-all emails, such a campaign could send a great many emails to accept-all addresses, many of which would bounce or get flagged as spam, thus decreasing ROI.

	~~Since the email provider accepts~~ all ~~incoming emails as if the mailbox is valid and active, regardless of what may actually be the case, sending to such~~ emails ~~is essentially a gamble~~.		Please refer to [[Global Email:Result Codes\|Result Codes (Advanced)]] for more information on how to handle accept-all emails using Global Email.

Admin at 22:52, 23 July 2020

2020-07-23T22:52:27Z

← Older revision		Revision as of 22:52, 23 July 2020
Line 24:		Line 24:

	==Deliverability Confidence Score==		==Deliverability Confidence Score==
	Deliverability Confidence Score ~~is a feature that determines~~ the probability ~~of your email making it into the mailbox of the recipient. It is meant to be used as an aid to help determining the quality of your emails. It is scored~~ from 0-100, ~~where 0 means 0% probability~~ of your email making it ~~into the mailbox and 100% probability means that your email will show up in~~ the mailbox. Please note that while an email may be valid, there are external factors such as mailbox provider’s black listing filters, spam rules and grey-listing technology that determine ultimately if your email is accepted by the recipient. This ~~score is especially useful for marketing campaigns in which high volume off emails are being sent out in a short amount of time. It is recommended that emails with lower scores~~ be ~~sent out at a slower rate~~ as ~~they have a higher chance of~~ a ~~missed delivery due~~ to ~~external factors. Continuously sending emails out~~ to ~~emails with low deliverability scores may lead~~ to ~~blacklisting, high bounce rates, and being auto filtered into spam folder by mail providers~~.		Deliverability Confidence Score represents the probability, from 0 to 100%, of your email making it to the recipient’s mailbox. This field can be used as a simple check to determine if you want to send to an email (see the table below).

	Our recommendations for ~~utilizing Global Email’s deliverability confidence scores.~~		Please note that not all valid emails, i.e. emails that have result code ES01, have a deliverability confidence score of 100. The same myriad factors that are used in determining our result codes are reflected in this new score.

			Our recommendations for using Deliverability Confidence Score:

	{\| class="alternate01 sortable"		{\| class="alternate01 sortable"

Admin at 00:00, 23 July 2020

2020-07-23T00:00:39Z

Show changes

Admin at 22:18, 7 June 2019

2019-06-07T22:18:17Z

← Older revision		Revision as of 22:18, 7 June 2019
Line 134:		Line 134:
	\|0 to 30\|\|Do not send.		\|0 to 30\|\|Do not send.
	\|-		\|-
	\|31 to 60\|\|~~Send cautiously and actively monitor bounce rates~~.		\|31 to 60\|\|Email delivery not guaranteed.
	\|-		\|-
	\|61 to 100\|\|Send mail. There is a high chance of email delivery success.		\|61 to 100\|\|Send mail. There is a high chance of email delivery success.

Admin at 23:45, 23 May 2019

2019-05-23T23:45:53Z

← Older revision		Revision as of 23:45, 23 May 2019
Line 113:		Line 113:
	*Aol and Yahoo mail servers are known to take the longest time to validate.		*Aol and Yahoo mail servers are known to take the longest time to validate.

	~~<!--~~==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 (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_GlobalEmailV4_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_GlobalEmailV4_Speed-Premium.png]]
	*You can expect 45,000 - 79,000 validations per hour with 5 threads.

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

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

2019-05-23T17:50:32Z

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

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

← Older revision		Revision as of 00:53, 24 February 2022
Line 142:		Line 142:
	Factors impacting performance:		Factors impacting performance:

	*VerifyMailBox Options Express vs. Premium		;VerifyMailBox Options Express vs. Premium
	**Selecting Express or Premium options will be the greatest factor impacting performance		:*Selecting Express or Premium options will be the greatest factor impacting performance
	**Premium will have slower speeds due to real time validation		:*Premium will have slower speeds due to real time validation
	*Number of threads used for sending requests to the service:		;Number of threads used for sending requests to the service:
	**We recommend 10 threads for processing		:*We recommend 10 threads for processing
	*TimeToWait		;TimeToWait
	**Default setting is 25 seconds per request. Setting this lower will give you faster performance but may affect accuracy. Setting this higher will do the opposite; slower performance and possible higher accuracy		:*Default setting is 25 seconds per request. Setting this lower will give you faster performance but may affect accuracy. Setting this higher will do the opposite; slower performance and possible higher accuracy
	*Data Quality		;Data Quality
	**The quality of data sent to the service can affect the performance substantially		:*The quality of data sent to the service can affect the performance substantially
	**Premium real time checks will wait for a response from an MX server. If there are issues with a domain, TimeToWait may hit its maximum, increasing processing time		:*Premium real time checks will wait for a response from an MX server. If there are issues with a domain, TimeToWait may hit its maximum, increasing processing time
	*WhoIsLookup		;WhoIsLookup
	**Activating this option will allow domain information lookups which has a small performance impact		:*Activating this option will allow domain information lookups which has a small performance impact

	With these variations, you can expect these approximate throughput rates:		With these variations, you can expect these approximate throughput rates:

	{\| class="alternate01"		:{\| class="alternate01"
	!VerifyMailBox Option!!Throughput (records / hour)		!VerifyMailBox Option!!Throughput (records / hour)
	\|-		\|-