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

[dependabot]

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

Release notes

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

v1.6.3

• Fix bug where email addresses containing control characters in the local-part were incorrectly considered valid. (Thanks @​PascalSchumacher for reporting!)
• Add new methods ifValid(Consumer<Email> action) and ifValidOrElse(Consumer<Email> action, Consumer<FailureReason> failureAction) to the EmailValidationResult object.

v1.6.2

• Fix bug where IPv4 addresses with non-arabic numerals would incorrectly be considered valid. (Thanks @​harrel56 for reporting!)
• Fix bug where IPv4 addresses with extraneous leading zeros would incorrectly be considered valid. (Thanks @​harrel56 for reporting!)
• The requireValidMXRecord() validation rule now correctly fails validation for domains that use a "Null MX" record. (Thanks @​elmolm for contributing! 🎉)

v1.6.1

• Fix bug so that email addresses that end in a dash - character now correctly fail validation with the reason FailureReason.DOMAIN_PART_ENDS_WITH_DASH instead of incorrectly returning FailureReason.ENDS_WITH_DOT. (Thanks @​tbatchlear for reporting!)

v1.6.0

• Add a new rule requireAscii() that considers an email address containing non-ASCII characters to be invalid. (Thanks @​frodeto for suggesting!)
• Add new property isAscii() on Email objects that returns if the email address only contains ASCII characters or not.
• Add option to strip quotes within the local-part of an email address when normalizing the address with the normalize() method. (Thanks @​tdelaney-leadiro for suggesting!)
  • This new option will remove quotes if the email address would still be valid and semantically the same without them.
  • To enable the option, either:
    • Call the normalize method that takes a boolean as the parameter, and use true. Example: email.normalize(true)
    • Set the -Djmail.normalize.strip.quotes=true JVM property at runtime, and continue to use the normalize() method without parameters.

v1.5.1

• Add a new rule requireValidMXRecord(int initialTimeout, int numRetries) that allows for customization of the timeout for DNS lookups. (Thanks @​dotneutron for suggesting!)
• Reduce the default timeout for DNS lookups when adding the requireValidMXRecord() rule to an EmailValidator from potentially taking a maximum of 25 seconds to a maximum of 600 milliseconds.

v1.5.0

• Add new method validate(String email) that returns an EmailValidationResult object, containing the reason for validation failure upon failure. (Thanks @​bobharner for suggesting!)
• Add new ValidationRule requireValidMXRecord() to consider email addresses that have a domain with no MX record in DNS as invalid. (Thanks @​lpellegr for suggesting!)
• Fix bug where an email address that ends with a comment that is missing the closing parentheses were incorrectly considered as valid. For example: [email protected](comment

Changelog

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

1.6.3

• Fix bug where email addresses containing control characters in the local-part were incorrectly considered valid. (Thanks @​PascalSchumacher for reporting!)
• Add new methods ifValid(Consumer<Email> action) and ifValidOrElse(Consumer<Email> action, Consumer<FailureReason> failureAction) to the EmailValidationResult object.

---

1.6.2

• Fix bug where IPv4 addresses with non-arabic numerals would incorrectly be considered valid. (Thanks @​harrel56 for reporting!)
• Fix bug where IPv4 addresses with extraneous leading zeros would incorrectly be considered valid. (Thanks @​harrel56 for reporting!)
• The requireValidMXRecord() validation rule now correctly fails validation for domains that use a "Null MX" record. (Thanks @​elmolm for contributing! 🎉)

---

1.6.1

• Fix bug so that email addresses that end in a dash - character now correctly fail validation with the reason FailureReason.DOMAIN_PART_ENDS_WITH_DASH instead of incorrectly returning FailureReason.ENDS_WITH_DOT. (Thanks @​tbatchlear for reporting!)

---

1.6.0

• Add a new rule requireAscii() that considers an email address containing non-ASCII characters to be invalid. (Thanks @​frodeto for suggesting!)
• Add new property isAscii() on Email objects that returns if the email address only contains ASCII characters or not.
• Add option to strip quotes within the local-part of an email address when normalizing the address with the normalize() method. (Thanks @​tdelaney-leadiro for suggesting!)
  • This new option will remove quotes if the email address would still be valid and semantically the same without them.
  • To enable the option, either:
    • Call the normalize method that takes a boolean as the parameter, and use true. Example: email.normalize(true)
    • Set the -Djmail.normalize.strip.quotes=true JVM property at runtime, and continue to use the normalize() method without parameters.

---

1.5.1

• Add a new rule requireValidMXRecord(int initialTimeout, int numRetries) that allows for customization of the timeout for DNS lookups. (Thanks @​dotneutron for suggesting!)
• Reduce the default timeout for DNS lookups when adding the requireValidMXRecord() rule to an EmailValidator from potentially taking a maximum of 25 seconds to a maximum of 600 milliseconds.

---

1.5.0

• Add new method validate(String email) that returns an EmailValidationResult object, containing the reason for validation failure upon failure. (Thanks @​bobharner for suggesting!)
• Add new ValidationRule requireValidMXRecord() to consider email addresses that have a domain with no MX record in DNS as invalid. (Thanks @​lpellegr for suggesting!)
• Fix bug where an email address that ends with a comment that is missing the closing parentheses were incorrectly considered as valid. For example: [email protected](comment

---

Commits

• 5068087 [maven-release-plugin] prepare release v1.6.3
• cb2635c Add new ifValid and ifValidOrElse methods
• a986bd7 Remove quodana scan in CI
• b179558 Addresses with unquoted control characters should be invalid
• 77a2ee6 Bump JetBrains/qodana-action from 2024.1.4 to 2024.1.5 in the gh-actions grou...
• 7cbe01e Bump JetBrains/qodana-action from 2024.1.3 to 2024.1.4 in the gh-actions grou...
• 0d5df44 Bump JetBrains/qodana-action from 2024.1.2 to 2024.1.3 in the gh-actions grou...
• c5cb447 Bump com.puppycrawl.tools:checkstyle from 10.15.0 to 10.16.0 in the test-depe...
• 1bc5bba Bump JetBrains/qodana-action from 2024.1.1 to 2024.1.2 in the gh-actions grou...
• a1a8947 Bump JetBrains/qodana-action from 2023.3.2 to 2024.1.1 in the gh-actions grou...
• 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)