Email Object:FAQ - Revision history

Admin at 23:26, 27 December 2019

2019-12-27T23:26:22Z

← Older revision		Revision as of 23:26, 27 December 2019
Line 2:		Line 2:
	{{CustomTOC}}		{{CustomTOC}}
	==How do I automate the installation of the Email Object?==		==How do I automate the installation of the Email Object?==
	Melissa Data has provided a set of scripts to download the DQ Suite and its misc Email files every month. Download the scripts and insert your custom download links within the configuration params file and then set the scripts to run as a scheduled task. The Windows batch scripts are provided on the DQ Suite DVD, the monthly download in the extras-scripts directory and also here: ~~http~~://www.~~melissadata~~.com/~~Updaters~~.zip. UNIX shell scripts will be available soon.		Melissa Data has provided a set of scripts to download the DQ Suite and its misc Email files every month. Download the scripts and insert your custom download links within the configuration params file and then set the scripts to run as a scheduled task. The Windows batch scripts are provided on the DQ Suite DVD, the monthly download in the extras-scripts directory and also here: https://www.melissa.com/scriptcode/updaters.zip. UNIX shell scripts will be available soon.

Admin at 22:35, 11 March 2016

2016-03-11T22:35:22Z

← Older revision		Revision as of 22:35, 11 March 2016
Line 2:		Line 2:
	{{CustomTOC}}		{{CustomTOC}}
	==How do I automate the installation of the Email Object?==		==How do I automate the installation of the Email Object?==
	~~How do I automate~~ and ~~script~~ the ~~installation of~~ the ~~DQT~~ Suite and ~~Email Object?~~		Melissa Data has provided a set of scripts to download the DQ Suite and its misc Email files every month. Download the scripts and insert your custom download links within the configuration params file and then set the scripts to run as a scheduled task. The Windows batch scripts are provided on the DQ Suite DVD, the monthly download in the extras-scripts directory and also here: http://www.melissadata.com/Updaters.zip. UNIX shell scripts will be available soon.

	~~;Answer:~~
	:Melissa Data has provided a set of scripts to download the DQ Suite and its misc Email files every month. Download the scripts and insert your custom download links within the configuration params file and then set the scripts to run as a scheduled task. The Windows batch scripts are provided on the DQ Suite DVD, the monthly download in the extras-scripts directory and also here: http://www.melissadata.com/Updaters.zip. UNIX shell scripts will be available soon.


	==What are bitwise operations and why do I need to know them for Email Object?==		==What are bitwise operations and why do I need to know them for Email Object?==
	~~;Answer:~~		A Bitwise operation uses a multi-bit type, commonly an integer, and operates at the level of its individual bits. More specifically, we are going to use bit masking when dealing with the Email Object ChangeCode property. Lets first discuss why we are using bitwise operations.
	:A Bitwise operation uses a multi-bit type, commonly an integer, and operates at the level of its individual bits. More specifically, we are going to use bit masking when dealing with the Email Object ChangeCode property. Lets first discuss why we are using bitwise operations.

			The Email Object ChangeCode indicates how the email address has been changed during verification. Currently, there are four possible changes: Syntax, Top Level Domain (TLD), Domain Spelling, and Domain Updated. Any combination of these changes can occur in an email address at once. Just based on these 4 possible changes, we have 15 different combinations of changes in an email address. If we add a 5th possible change, that number jumps to 31. To handle these possible changes combinations while accounting for future additions, we decided to use bitwise operations.

	:The ~~Email Object~~ ChangeCode ~~indicates how~~ the ~~email address has been changed during verification~~. ~~Currently~~, ~~there are four possible changes: Syntax, Top Level Domain (~~TLD), Domain Spelling, and Domain ~~Updated. Any combination of these changes can occur in an email address at once. Just based on these 4 possible changes, we have 15 different combinations of changes in an email address~~. If ~~we add~~ a ~~5th possible~~ change, that ~~number jumps~~ to 31. ~~To handle these possible changes combinations while accounting for future additions~~, we ~~decided to use bitwise operations~~.		The ChangeCode property simply returns an integer. However, the actual information provided is at the bit level. The first bit corresponds to a syntax change, the 2nd bit to a TLD change, the 3rd to Domain Spelling, and 4th to Domain Update. If a specific change has occurred, we set that bit to 1, otherwise we leave it as 0. So, if the Domain Spelling and the syntax has changed, the ChangeCode becomes 0101 and we get the decimal equivalent of 5.

			Now, to actually extract the information from the change code, we make use of bit masking. Bit masking isolates a specific bit so we can see if it is set or not. We do this by performing a logical AND operation on the change code and the bit mask for the bit we want to isolate. The bit mask is simply the integer equivalent of the change code in the Email Object guide, 1 for syntax, 2 for TLD, 4 for domain spelling, and 8 for domain update. Lets take a look at a bit masking example with a ChangeCode of 5(0101) and the bit mask for domain spelling, 4 (0100).

	:The ChangeCode property simply returns an integer. However, the actual information provided is at the bit level. The first bit corresponds to a syntax change, the 2nd bit to a TLD change, the 3rd to Domain Spelling, and 4th to Domain Update. If a specific change has occurred, we set that bit to 1, otherwise we leave it as 0. So, if the Domain Spelling and the syntax has changed, the ChangeCode becomes 0101 and we get the decimal equivalent of 5.


	:Now, to actually extract the information from the change code, we make use of bit masking. Bit masking isolates a specific bit so we can see if it is set or not. We do this by performing a logical AND operation on the change code and the bit mask for the bit we want to isolate. The bit mask is simply the integer equivalent of the change code in the Email Object guide, 1 for syntax, 2 for TLD, 4 for domain spelling, and 8 for domain update. Lets take a look at a bit masking example with a ChangeCode of 5(0101) and the bit mask for domain spelling, 4 (0100).
	~~<blockquote>~~
	<pre>0101		<pre>0101
	AND 0100		AND 0100
	= 0100</pre>		= 0100</pre>
	~~</blockquote>~~
	:As you can see, the bit mask isolates just the 3rd bit. Since the 3rd bit of the result is 1, we know that the 3rd bit of the original change code was also 1, and the domain spelling changed. In order to extract all the changes from the ChangeCode, we must perform the bit masking operation on all the possible changes. So, your code would look something like this.		As you can see, the bit mask isolates just the 3rd bit. Since the 3rd bit of the result is 1, we know that the 3rd bit of the original change code was also 1, and the domain spelling changed. In order to extract all the changes from the ChangeCode, we must perform the bit masking operation on all the possible changes. So, your code would look something like this.
	~~<blockquote>~~
	<pre>if(ChangeCode = 0)		<pre>if(ChangeCode = 0)
	print "No Changes"		print "No Changes"
Line 41:		Line 34:
	if(ChangeCode AND 8 = 8)		if(ChangeCode AND 8 = 8)
	print "Domain Updated"</pre>		print "Domain Updated"</pre>
	~~</blockquote>~~
	:Note: The above was just pseudo code. It will not work as is. Bitwise operations are much more complex than what has been presented here. Please do more research on your own if you are interested.		Note: The above was just pseudo code. It will not work as is. Bitwise operations are much more complex than what has been presented here. Please do more research on your own if you are interested.


	==What is MXLookup?==		==What is MXLookup?==
	~~;Answer:~~		The Email Object has an option to use MXLookup to determine whether a domain is valid or invalid. MXLookup can determine whether the actual mail server is accepting email messages or not. An internet connection is required to use MXLookup.
	:The Email Object has an option to use MXLookup to determine whether a domain is valid or invalid. MXLookup can determine whether the actual mail server is accepting email messages or not. An internet connection is required to use MXLookup.


	==Can I add/remove my own list of valid/invalid Email Domains?==		==Can I add/remove my own list of valid/invalid Email Domains?==
	~~;Answer:~~		Yes, the Email Object can be setup to check against your own list of valid/invalid email addresses. To do this, edit your mdEmailConfig.ini located in the data files directory of the object. To forcefully overwrite the list of valid domains, add them below [valid domains]. To forcefully overwrite the list of invalid domains, add them below [invalid domains].
	:Yes, the Email Object can be setup to check against your own list of valid/invalid email addresses. To do this, edit your mdEmailConfig.ini located in the data files directory of the object. To forcefully overwrite the list of valid domains, add them below [valid domains]. To forcefully overwrite the list of invalid domains, add them below [invalid domains].


	==What data files are needed by the Email Object?==		==What data files are needed by the Email Object?==
	~~;Answer:~~		The Email Object has only 3 required data file:
	:The Email Object has only 3 required data file:

	::mdDomain.dat		:mdDomain.dat
	::mdEmail.ini		:mdEmail.ini
	::mdEmailConfig.ini		:mdEmailConfig.ini


	==How can I further customize the Email Object?==		==How can I further customize the Email Object?==
	~~;Answer:~~		Under the Email Data Files folder, edit the mdEmailConfig.ini file. Here you will see a set of different rules that you can set in order to customize the way Email Object works. The mdEmailConfig.ini file allows you to:
	:Under the Email Data Files folder, edit the mdEmailConfig.ini file. Here you will see a set of different rules that you can set in order to customize the way Email Object works. The mdEmailConfig.ini file allows you to:

	::Add/Remove domain mispelling rules		:Add/Remove domain mispelling rules
	::Add/Remove updated domains		:Add/Remove updated domains
	::Add/Remove valid domains		:Add/Remove valid domains
	::Add/Remove invalid domains		:Add/Remove invalid domains
	::Add/Remove valid mailboxes		:Add/Remove valid mailboxes
	::Add/Remove mobile domains		:Add/Remove mobile domains

	:Instructions on how to edit the mdEmailConfig.ini file are provided within the comments of the file.		Instructions on how to edit the mdEmailConfig.ini file are provided within the comments of the file.


	[[Category:FAQ]]		[[Category:FAQ]]
	[[Category:Email Object]]		[[Category:Email Object]]

Admin at 22:33, 11 March 2016

2016-03-11T22:33:37Z

← Older revision		Revision as of 22:33, 11 March 2016
Line 1:		Line 1:
	~~__FORCETOC__~~		[[Email Object\|← Email Object]]
			{{CustomTOC}}
	==How do I automate the installation of the Email Object?==		==How do I automate the installation of the Email Object?==
	How do I automate and script the installation of the DQT Suite and Email Object?		How do I automate and script the installation of the DQT Suite and Email Object?

Admin: Admin moved page FAQ:Email Object to Email Object:FAQ without leaving a redirect

2014-06-12T21:15:17Z

Admin moved page FAQ:Email Object to Email Object:FAQ without leaving a redirect

← Older revision	Revision as of 21:15, 12 June 2014
(No difference)

Admin at 19:11, 2 August 2012

2012-08-02T19:11:33Z

← Older revision		Revision as of 19:11, 2 August 2012
Line 78:		Line 78:

	[[Category:FAQ]]		[[Category:FAQ]]
	~~[[Category:API]]~~
	[[Category:Email Object]]		[[Category:Email Object]]

Admin at 01:02, 2 August 2012

2012-08-02T01:02:48Z

← Older revision		Revision as of 01:02, 2 August 2012
Line 28:		Line 28:
	<pre>if(ChangeCode = 0)		<pre>if(ChangeCode = 0)
	print "No Changes"		print "No Changes"

	if(ChangeCode AND 1 = 1)		if(ChangeCode AND 1 = 1)
	print "Syntax Changed"		print "Syntax Changed"

	if(ChangeCode AND 2 = 2)		if(ChangeCode AND 2 = 2)
	print "TLD Changed"		print "TLD Changed"

	if(ChangeCode AND 4 = 4)		if(ChangeCode AND 4 = 4)
	print "Domain Spelling Changed"		print "Domain Spelling Changed"

	if(ChangeCode AND 8 = 8)		if(ChangeCode AND 8 = 8)
	print "Domain Updated"</pre>		print "Domain Updated"</pre>

Admin: Created page with "FORCETOC ==How do I automate the installation of the Email Object?== How do I automate and script the installation of the DQT Suite and Email Object? ;Answer: :Melissa Da..."

2012-08-02T01:01:55Z

Created page with "__FORCETOC__ ==How do I automate the installation of the Email Object?== How do I automate and script the installation of the DQT Suite and Email Object? ;Answer: :Melissa Da..."

New page

__FORCETOC__
==How do I automate the installation of the Email Object?==
How do I automate and script the installation of the DQT Suite and Email Object?

;Answer:
:Melissa Data has provided a set of scripts to download the DQ Suite and its misc Email files every month. Download the scripts and insert your custom download links within the configuration params file and then set the scripts to run as a scheduled task. The Windows batch scripts are provided on the DQ Suite DVD, the monthly download in the extras-scripts directory and also here: http://www.melissadata.com/Updaters.zip. UNIX shell scripts will be available soon.

==What are bitwise operations and why do I need to know them for Email Object?==
;Answer:
:A Bitwise operation uses a multi-bit type, commonly an integer, and operates at the level of its individual bits. More specifically, we are going to use bit masking when dealing with the Email Object ChangeCode property. Lets first discuss why we are using bitwise operations.

:The Email Object ChangeCode indicates how the email address has been changed during verification. Currently, there are four possible changes: Syntax, Top Level Domain (TLD), Domain Spelling, and Domain Updated. Any combination of these changes can occur in an email address at once. Just based on these 4 possible changes, we have 15 different combinations of changes in an email address. If we add a 5th possible change, that number jumps to 31. To handle these possible changes combinations while accounting for future additions, we decided to use bitwise operations.

:The ChangeCode property simply returns an integer. However, the actual information provided is at the bit level. The first bit corresponds to a syntax change, the 2nd bit to a TLD change, the 3rd to Domain Spelling, and 4th to Domain Update. If a specific change has occurred, we set that bit to 1, otherwise we leave it as 0. So, if the Domain Spelling and the syntax has changed, the ChangeCode becomes 0101 and we get the decimal equivalent of 5.

:Now, to actually extract the information from the change code, we make use of bit masking. Bit masking isolates a specific bit so we can see if it is set or not. We do this by performing a logical AND operation on the change code and the bit mask for the bit we want to isolate. The bit mask is simply the integer equivalent of the change code in the Email Object guide, 1 for syntax, 2 for TLD, 4 for domain spelling, and 8 for domain update. Lets take a look at a bit masking example with a ChangeCode of 5(0101) and the bit mask for domain spelling, 4 (0100).
<blockquote>
<pre>0101
AND 0100
= 0100</pre>
</blockquote>
:As you can see, the bit mask isolates just the 3rd bit. Since the 3rd bit of the result is 1, we know that the 3rd bit of the original change code was also 1, and the domain spelling changed. In order to extract all the changes from the ChangeCode, we must perform the bit masking operation on all the possible changes. So, your code would look something like this.
<blockquote>
<pre>if(ChangeCode = 0)
print "No Changes"
if(ChangeCode AND 1 = 1)
print "Syntax Changed"
if(ChangeCode AND 2 = 2)
print "TLD Changed"
if(ChangeCode AND 4 = 4)
print "Domain Spelling Changed"
if(ChangeCode AND 8 = 8)
print "Domain Updated"</pre>
</blockquote>
:Note: The above was just pseudo code. It will not work as is. Bitwise operations are much more complex than what has been presented here. Please do more research on your own if you are interested.

==What is MXLookup?==
;Answer:
:The Email Object has an option to use MXLookup to determine whether a domain is valid or invalid. MXLookup can determine whether the actual mail server is accepting email messages or not. An internet connection is required to use MXLookup.

==Can I add/remove my own list of valid/invalid Email Domains?==
;Answer:
:Yes, the Email Object can be setup to check against your own list of valid/invalid email addresses. To do this, edit your mdEmailConfig.ini located in the data files directory of the object. To forcefully overwrite the list of valid domains, add them below [valid domains]. To forcefully overwrite the list of invalid domains, add them below [invalid domains].

==What data files are needed by the Email Object?==
;Answer:
:The Email Object has only 3 required data file:

::mdDomain.dat
::mdEmail.ini
::mdEmailConfig.ini

==How can I further customize the Email Object?==
;Answer:
:Under the Email Data Files folder, edit the mdEmailConfig.ini file. Here you will see a set of different rules that you can set in order to customize the way Email Object works. The mdEmailConfig.ini file allows you to:

::Add/Remove domain mispelling rules
::Add/Remove updated domains
::Add/Remove valid domains
::Add/Remove invalid domains
::Add/Remove valid mailboxes
::Add/Remove mobile domains

:Instructions on how to edit the mdEmailConfig.ini file are provided within the comments of the file.

[[Category:FAQ]]
[[Category:API]]
[[Category:Email Object]]