Sourced from email-validator's releases.
v2.1.1 (February 26, 2024)
- Fixed typo 'marking' instead of 'marketing' in case-insensitive mailbox name list.
- When DNS-based deliverability checks fail, in some cases exceptions are now thrown with
raise ... fromfor better nested exception tracking.- Fixed tests to work when no local resolver can be configured.
- This project is now licensed under the Unlicense (instead of CC0).
- Minor improvements to tests.
- Minor improvements to code style.
Sourced from email-validator's changelog.
2.1.1 (February 26, 2024)
- Fixed typo 'marking' instead of 'marketing' in case-insensitive mailbox name list.
- When DNS-based deliverability checks fail, in some cases exceptions are now thrown with
raise ... fromfor better nested exception tracking.- Fixed tests to work when no local resolver can be configured.
- This project is now licensed under the Unlicense (instead of CC0).
- Minor improvements to tests.
- Minor improvements to code style.
2.1.0 (October 22, 2023)
- Python 3.8+ is now required (support for Python 3.7 was dropped).
- The old
ValidatedEmailobject, which in the previous version was superseded bynormalized, will now raise a deprecation warning if used. See https://stackoverflow.com/q/879173 for strategies to suppress the DeprecationWarning.- A
__version__module attribute is added.- The email address argument to validate_email is now marked as positional-only to better reflect the documented usage using the new Python 3.8 feature.
2.0.0 (April 15, 2023)
This is a major update to the library, but since email address specs haven't changed there should be no significant changes to which email addresses are considered valid or invalid with default options. There are new options for accepting unusual email addresses that were previously always rejected, some changes to how DNS errors are handled, many changes in error message text, and major internal improvements including the addition of type annotations. Python 3.7+ is now required. Details follow:
- Python 2.x and 3.x versions through 3.6, and dnspython 1.x, are no longer supported. Python 3.7+ with dnspython 2.x are now required.
- The dnspython package is no longer required if DNS checks are not used, although it will install automatically.
- NoNameservers and NXDOMAIN DNS errors are now handled differently: NoNameservers no longer fails validation, and NXDOMAIN now skips checking for an A/AAAA fallback and goes straight to failing validation.
- Some syntax error messages have changed because they are now checked explicitly rather than as a part of other checks.
- The quoted-string local part syntax (e.g. multiple @-signs, spaces, etc. if surrounded by quotes) and domain-literal addresses (e.g. @[192.XXX...] or @[IPv6:...]) are now parsed but not considered valid by default. Better error messages are now given for these addresses since it can be confusing for a technically valid address to be rejected, and new allow_quoted_local and allow_domain_literal options are added to allow these addresses if you really need them.
- Some other error messages have changed to not repeat the email address in the error message.
- The
ValidatedEmailobject has been renamed tonormalizedto be clearer about its importance, but access via- Some mailbox names like
postmasterare now normalized to lowercase per RFC 2142.- The library has been reorganized internally into smaller modules.
- The tests have been reorganized and expanded. Deliverability tests now mostly use captured DNS responses so they can be run off-line.
- The main tool now reads options to validate_email from environment variables.
- Type annotations have been added to the exported methods and the ValidatedEmail class and some internal methods.
- The old dict-like pattern for the return value of validate_email is deprecated.
Versions 2.0.0.post1 and 2.0.0.post2 corrected some packaging issues. 2.0.0.post2 also added a check for an invalid combination of arguments.
Version 1.3.1 (January 21, 2023)
- The new SPF 'v=spf1 -all' (reject-all) deliverability check is removed in most cases. It now is performed only for domains that do not have MX records but do have an A/AAAA fallback record.
Version 1.3.0 (September 18, 2022)
- Deliverability checks now check for 'v=spf1 -all' SPF records as a way to reject more bad domains.
- Special use domain names now raise EmailSyntaxError instead of EmailUndeliverableError since they are performed even if check_deliverability is off.
- New module-level attributes are added to override the default values of the keyword arguments and the special-use domains list.
... (truncated)