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

[dependabot]

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

Release notes

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

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.

FailureReason Improvements

Changes to the FailureReason supplied for additional rules

The FailureReason returned in the EmailValidationResult is useful to understand why a specific email address failed validation. In v2.0.0, the FailureReason returned for email addresses that failed one of the additional validation rules added to your EmailValidator (such as disallowIpDomain() or requireValidMXRecord()) now return more specific and useful reasons (such as CONTAINS_IP_DOMAIN or INVALID_MX_RECORD).

... (truncated)

Changelog

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

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 that failure reason.

FailureReason Improvements

Changes to the FailureReason supplied for additional rules

The FailureReason returned in the EmailValidationResult is useful to understand why a specific email address failed validation. In v2.0.0, the FailureReason returned for email addresses that failed one of the additional validation rules added to your EmailValidator (such as disallowIpDomain() or requireValidMXRecord()) now return more specific and useful reasons (such as CONTAINS_IP_DOMAIN or INVALID_MX_RECORD).

... (truncated)

Commits

• 318ff99 [maven-release-plugin] prepare release v2.0.0
• 890e638 Prep docs for v2.0 release
• 340d46e Bump the test-dependencies group with 2 updates (#297)
• 388b3a4 Bump nl.jqno.equalsverifier:equalsverifier from 3.19.2 to 3.19.3 in the test-...
• 84ec8a5 Bump the test-dependencies group with 2 updates (#295)
• d847e61 Rename allowGmailDots to allowNonstandardDots
• 4f3f061 Add allowGmailDots to EmailValidator
• 2c3a98b Finish all valid email descriptions
• bd55641 Improve valid email descriptions
• cf52107 Bump the test-dependencies group with 2 updates (#294)
• 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)