Bump com.sanctionco.jmail:jmail from 1.6.3 to 2.0.2

[dependabot]

Bumps com.sanctionco.jmail:jmail from 1.6.3 to 2.0.2.

Release notes

Sourced from com.sanctionco.jmail:jmail's releases.

v2.0.2

• Fix bug where address containing a display name that starts with a dot . character would be incorrectly invalidated. (Thanks @​utalmighty for reporting!)

v2.0.1

• Fix bug where using the rule requireTopLevelDomain() would incorrectly invalidate addresses that use IP domains (since those inherently have a TLD). (Thanks @​ahegyes for reporting!)
• Fix bug where addresses starting with an at (@) character and ending with either a dot . or a colon : character threw a StringIndexOutOfBoundsException instead of correctly invalidating the address. (Thanks @​alexc-scopely for reporting!)
• Add new ValidationRule disallowSingleCharacterTopLevelDomains() to consider email addresses with TLDs that are only a single character (such as test.c) as invalid. (Thanks @​alexc-scopely for suggesting!)

v2.0.0

Breaking Changes

• By default, Email#normalized now lowercases the email address and removes any extraneous quotes in the local-part of the address. To revert this behavior so that it behaves the same as v1, use the following:

  myEmailObject.normalized(
    NormalizationOptions.builder()
      .keepQuotes()
      .adjustCase(CaseOption.NO_CHANGE)
      .build());
  

• The jmail.normalize.strip.quotes JVM system property no longer does anything. Quotes are stripped by default now. If you need to disable quote stripping, use NormalizationOptionsBuilder#keepQuotes().

• Removed Email#normalized(boolean) method which allowed for a normalized email with stripped quotes. Quotes are stripped by default now. If you need to disable quote stripping, use NormalizationOptionsBuilder#keepQuotes().

• FailureReason was switched from an enum to a class in order to support custom failure reasons, so it is no longer possible to use it in a switch statement.

• Email addresses that fail validation due to additional rules added to the EmailValidator (such as disallowIpDomain() or requireValidMXRecord()) no longer return a generic FailureReason.FAILED_CUSTOM_VALIDATION in the EmailValidationResult. Instead, it returns a more specific FailureReason depending on the rule.

• FailureReason.MISSING_TOP_LEVEL_DOMAIN was changed to FailureReason.MISSING_FINAL_DOMAIN_PART. MISSING_TOP_LEVEL_DOMAIN was previously used for email addresses that failed validation because they ended the email address with a comment. This FailureReason was potentially misleading, for example if you enabled requireTopLevelDomain() on your EmailValidator. Note that the MISSING_TOP_LEVEL_DOMAIN failure reason is now used properly: if you use the rule requireTopLevelDomain(), any address that is missing the TLD will give that failure reason.

... (truncated)

Changelog

Sourced from com.sanctionco.jmail:jmail's changelog.

2.0.2

• Fix bug where address containing a display name that starts with a dot . character would be incorrectly invalidated. (Thanks @​utalmighty for reporting!)

---

2.0.1

• Fix bug where using the rule requireTopLevelDomain() would incorrectly invalidate addresses that use IP domains (since those inherently have a TLD). (Thanks @​ahegyes for reporting!)
• Fix bug where addresses starting with an at (@) character and ending with either a dot . or a colon : character threw a StringIndexOutOfBoundsException instead of correctly invalidating the address. (Thanks @​alexc-scopely for reporting!)
• Add new ValidationRule disallowSingleCharacterTopLevelDomains() to consider email addresses with TLDs that are only a single character (such as test.c) as invalid. (Thanks @​alexc-scopely for suggesting!)

---

2.0.0

Breaking Changes

• By default, Email#normalized now lowercases the email address and removes any extraneous quotes in the local-part of the address. To revert this behavior so that it behaves the same as v1, use the following:

  myEmailObject.normalized(
    NormalizationOptions.builder()
      .keepQuotes()
      .adjustCase(CaseOption.NO_CHANGE)
      .build());
  

• The jmail.normalize.strip.quotes JVM system property no longer does anything. Quotes are stripped by default now. If you need to disable quote stripping, use NormalizationOptionsBuilder#keepQuotes().

• Removed Email#normalized(boolean) method which allowed for a normalized email with stripped quotes. Quotes are stripped by default now. If you need to disable quote stripping, use NormalizationOptionsBuilder#keepQuotes().

• FailureReason was switched from an enum to a class in order to support custom failure reasons, so it is no longer possible to use it in a switch statement.

• Email addresses that fail validation due to additional rules added to the EmailValidator (such as disallowIpDomain() or requireValidMXRecord()) no longer return a generic FailureReason.FAILED_CUSTOM_VALIDATION in the EmailValidationResult. Instead, it returns a more specific FailureReason depending on the rule.

• FailureReason.MISSING_TOP_LEVEL_DOMAIN was changed to FailureReason.MISSING_FINAL_DOMAIN_PART. MISSING_TOP_LEVEL_DOMAIN was previously used for email addresses that failed validation because they ended the email address with a comment. This FailureReason was potentially misleading, for example if you enabled requireTopLevelDomain() on your EmailValidator. Note that the MISSING_TOP_LEVEL_DOMAIN failure reason is now used properly: if you use the rule requireTopLevelDomain(), any address that is missing the TLD will give

... (truncated)

Commits

• ca06256 [maven-release-plugin] prepare release v2.0.2
• 95fca1f fix: allow display-name to start with a dot
• 4ef2e26 Reduce toString calls
• bc6de08 Bump the test-dependencies group with 3 updates (#309)
• ac910d7 Bump com.puppycrawl.tools:checkstyle from 10.25.0 to 10.25.1 in the test-depe...
• 7fa3aec Bump org.sonatype.central:central-publishing-maven-plugin from 0.7.0 to 0.8.0...
• e4dabc3 Use new publishing plugin
• 42cb913 Bump the test-dependencies group with 2 updates (#306)
• 35eefa9 Update version number to 2.0.1
• d0aa749 [maven-release-plugin] prepare for next development iteration
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)