Global Email:Build History: Difference between revisions

From Melissa Data Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(10 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[Global Email|← Global Email]]
[[Global Email|← Global Email]]
{{CustomTOC}}
{{CustomTOC}}
Please see the Melissa Product Release Notes for updated Build History moving forward:
*https://releasenotes.melissa.com/cloud-api/global-email/
==Build 4.2.1.4215==
''Released November 2022''
<p class="sectionhead">Minor Release</p>
*Stability improvements and bug fixes.
==Build 4.2.1.4209==
''Released October 2022''
<p class="sectionhead">Minor Release</p>
*Stability improvements and bug fixes.
==Build 4.2.1.4205==
''Released October 2022''
<p class="sectionhead">Minor Release</p>
*Stability improvements and bug fixes.
==Build 4.2.1.4202==
''Released September 2022''
<p class="sectionhead">Major Release</p>
:;New Fields
:*<code>DomainAuthenticationStatus</code>
::Returns security protocols used on the receiving mail server
:*<code>DomainTypeIndicator</code>
::Predicts if email belongs to a personal or business/organization email by analyzing the domain.
:*<code>BreachCount</code> (Available late 2022 or early 2023)
::Returns the known number of breaches that this email account has been involved in.
:;Improvements
:*'''Speeds'''
::We made significant investments in our email validation cloud infrastructure, focusing on stability, reliability and speed improvements.
:*'''MX Level Validation'''
::We have made improvements at the MX server level to identify issues at the domain level more accurately, resulting in quicker validations for invalid mail servers. We leverage additional logic to determine if the provider is having a temporary outage at the domain level.
:*'''Domain Correction'''
::We made significant improvements and reworked our domain correction algorithm with the goal of reducing false corrections. We plan to expand domain corrections to include more popular domains on a periodic basis.
:*'''DeliveryConfidenceScore Accuracy'''
::We’ve implemented new, dynamic logic to improve the accuracy of the delivery confidence scores.
:;Bug Fixes
:*Fixed Issue with inconsistent role address detection
==Build 4.2.1.4199==
''Released September 2022''
<p class="sectionhead">Minor Release</p>
*Stability improvements and bug fixes
==Build 4.2.1.4158==
''Released August 2022''
<p class="sectionhead">Minor Release</p>
*Improvements on speed and stability
==Build 4.0.0.29==
''Released May 2021''
<p class="sectionhead">Minor Release</p>
*Small fixes
**Improved handling of rare types real-time check results
**Improved handling of rare types of email results found in the cache
==Build 4.0.0.26==
''Released February 2021''
<p class="sectionhead">Minor Release</p>
*Small fixes
**Fixed rare bug where result code '''ES24''' appeared erroneously
**Optimized domain-only verification
*Enhanced '''DeliverabilityConfidenceScore''' (first of multiple upcoming improvements)
**Now leveraging more historical data to increase accuracy of DCS
==Build 4.0.0.22==
''Released January 2021''
<p class="sectionhead">Minor Release</p>
*New response field: '''EmailAgeEstimated'''
**Shows the estimated minimum age of an email
*Improved handling emails from problematic domains
==Build 4.0.0.19==
''Released October 2020''
<p class="sectionhead">Minor Release</p>
*Improved handling of some rare results.
==Build 4.0.0.18==
==Build 4.0.0.18==
''Released October 2020''
''Released October 2020''
;Minor Release
<p class="sectionhead">Minor Release</p>
*Improvements and fixes to enhance service for users affected by GDPR and other privacy regulations.
*Improvements and fixes to enhance service for users affected by GDPR and other privacy regulations.


Line 9: Line 102:
==Build 4.0.0.17==
==Build 4.0.0.17==
''Released September 2020''
''Released September 2020''
;Minor Release
<p class="sectionhead">Minor Release</p>
*Changed result codes related to domain-only verification to maintain compatibility.
*Changed result codes related to domain-only verification to maintain compatibility.


Line 15: Line 108:
==Build 4.0.0.15==
==Build 4.0.0.15==
''Released September 2020''
''Released September 2020''
;Minor Release
<p class="sectionhead">Minor Release</p>
*Small changes to response format for domain-only verification.
*Small changes to response format for domain-only verification.


Line 21: Line 114:
==Build 4.0.0.13==
==Build 4.0.0.13==
''Released August 2020''
''Released August 2020''
;Minor Release
<p class="sectionhead">Minor Release</p>
*Increased overall data uplift for domain country information.
*Increased overall data uplift for domain country information.
*Added domain-only mode:  ability to verify domains alone.
*Added domain-only mode:  ability to verify domains alone.
Line 28: Line 121:
==Build 4.0.0.10==
==Build 4.0.0.10==
''Released May 2020''
''Released May 2020''
;Minor Release
<p class="sectionhead">Minor Release</p>
*Changed logic to decrease frequency of ES03 result code.
*Changed logic to decrease frequency of ES03 result code.


Line 34: Line 127:
==Build 4.0.0.8==
==Build 4.0.0.8==
''Released March 2020''
''Released March 2020''
;Major Release
<p class="sectionhead">Minor Release</p>
*MX Server field added.
*MX Server field added.
*Improvements to Accept All emails for specific domains.
*Improvements to Accept All emails for specific domains.


Line 41: Line 134:
==Build 4.0.0.5==
==Build 4.0.0.5==
''Released April 2019''
''Released April 2019''
;Minor Release
<p class="sectionhead">Minor Release</p>
*Privacy Flag field added. If the top level domain is based within Europe, The Privacy Flag Response field will contain a “Y”. Otherwise, the Privacy Flag Response field will contain an “N”
*'''Privacy Flag''' field added. If the top level domain is based within Europe, The Privacy Flag Response field will contain a <code>Y</code>. Otherwise, the Privacy Flag Response field will contain an <code>N</code>
*Result Code ES30 added. TLD that may be sensitive to GDPR. This will indicate that sending to these emails may result in a fine or penalties. Proceed with caution when sending to these emails.
*Result Code '''ES30''' added. TLD that may be sensitive to GDPR. This will indicate that sending to these emails may result in a fine or penalties. Proceed with caution when sending to these emails.





Latest revision as of 00:21, 4 February 2023

← Global Email


Please see the Melissa Product Release Notes for updated Build History moving forward:

Build 4.2.1.4215

Released November 2022

Minor Release

  • Stability improvements and bug fixes.


Build 4.2.1.4209

Released October 2022

Minor Release

  • Stability improvements and bug fixes.


Build 4.2.1.4205

Released October 2022

Minor Release

  • Stability improvements and bug fixes.


Build 4.2.1.4202

Released September 2022

Major Release

New Fields
  • DomainAuthenticationStatus
Returns security protocols used on the receiving mail server
  • DomainTypeIndicator
Predicts if email belongs to a personal or business/organization email by analyzing the domain.
  • BreachCount (Available late 2022 or early 2023)
Returns the known number of breaches that this email account has been involved in.
Improvements
  • Speeds
We made significant investments in our email validation cloud infrastructure, focusing on stability, reliability and speed improvements.
  • MX Level Validation
We have made improvements at the MX server level to identify issues at the domain level more accurately, resulting in quicker validations for invalid mail servers. We leverage additional logic to determine if the provider is having a temporary outage at the domain level.
  • Domain Correction
We made significant improvements and reworked our domain correction algorithm with the goal of reducing false corrections. We plan to expand domain corrections to include more popular domains on a periodic basis.
  • DeliveryConfidenceScore Accuracy
We’ve implemented new, dynamic logic to improve the accuracy of the delivery confidence scores.
Bug Fixes
  • Fixed Issue with inconsistent role address detection


Build 4.2.1.4199

Released September 2022

Minor Release

  • Stability improvements and bug fixes


Build 4.2.1.4158

Released August 2022

Minor Release

  • Improvements on speed and stability


Build 4.0.0.29

Released May 2021

Minor Release

  • Small fixes
    • Improved handling of rare types real-time check results
    • Improved handling of rare types of email results found in the cache


Build 4.0.0.26

Released February 2021

Minor Release

  • Small fixes
    • Fixed rare bug where result code ES24 appeared erroneously
    • Optimized domain-only verification
  • Enhanced DeliverabilityConfidenceScore (first of multiple upcoming improvements)
    • Now leveraging more historical data to increase accuracy of DCS


Build 4.0.0.22

Released January 2021

Minor Release

  • New response field: EmailAgeEstimated
    • Shows the estimated minimum age of an email
  • Improved handling emails from problematic domains


Build 4.0.0.19

Released October 2020

Minor Release

  • Improved handling of some rare results.


Build 4.0.0.18

Released October 2020

Minor Release

  • Improvements and fixes to enhance service for users affected by GDPR and other privacy regulations.


Build 4.0.0.17

Released September 2020

Minor Release

  • Changed result codes related to domain-only verification to maintain compatibility.


Build 4.0.0.15

Released September 2020

Minor Release

  • Small changes to response format for domain-only verification.


Build 4.0.0.13

Released August 2020

Minor Release

  • Increased overall data uplift for domain country information.
  • Added domain-only mode: ability to verify domains alone.


Build 4.0.0.10

Released May 2020

Minor Release

  • Changed logic to decrease frequency of ES03 result code.


Build 4.0.0.8

Released March 2020

Minor Release

  • MX Server field added.
  • Improvements to Accept All emails for specific domains.


Build 4.0.0.5

Released April 2019

Minor Release

  • Privacy Flag field added. If the top level domain is based within Europe, The Privacy Flag Response field will contain a Y. Otherwise, the Privacy Flag Response field will contain an N
  • Result Code ES30 added. TLD that may be sensitive to GDPR. This will indicate that sending to these emails may result in a fine or penalties. Proceed with caution when sending to these emails.


Build 4.0.0.3

Released March 2019

  • Initial Release