hishamalfoqaha
/
py3-validate-email
forked from karolyi/py3-validate-email
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add changelog for 1.0.0

This commit is contained in:
László Károlyi 2021-03-01 17:37:29 +01:00
parent 1999e1d433
commit b0e89cabd7
Signed by untrusted user: karolyi
GPG Key ID: 2DCAF25E55735BFE
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
CHANGELOG.txt
View File

@ -1,3 +1,12 @@
1.0.0:
- New major release with breaking changes! They are:
- Ambiguous results, and the possibility of more of them:
- The validate_email_or_fail() function will now raise an SMTPTemporaryError() on an ambiguous result. That is, greylisting or no servers providing a definitive negative or positive.
- A server that bails out with a 4xx code at any part of the SMTP conversation, will be marked as ambiguous, just like the way most implementations treat email delivery.
- The validate_email_or_fail() function will now raise an SMTPCommunicationError() on a denied email address but will keep trying other MX hosts for validation. If all other servers are ambiguous, the validation will fail nonetheless.
- Both of the aforementioned exceptions will contain the occurred communication results in their error_messages class variables.
- Props to @reinhard-mueller for coming up with the new proposal and helping in refining the idea.
0.2.16:
- Workaround for a bug in the built-in python 3.8 smtp library: https://github.com/karolyi/py3-validate-email/issues/50
@ -104,4 +113,4 @@
- Handle 'No MX record' exception
0.1.3:
- Added ambigious (4xx) response code handling
- Added ambiguous (4xx) response code handling