Next step towards 1.0.0 #63
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: karolyi/py3-validate-email#63
Loading…
Reference in a new issue
No description provided.
Delete branch "master"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Comments welcome!
BTW, I will add more unittests for
smtp_check
to this PR soon, but you're still welcome to comment on what's already here.@ -14,3 +21,4 @@
we talk to seemingly accepts the email address.
## Everything gets rejected:
Is this really the case with MS servers? So far I've seen outlook servers (if you meant those) rejecting the invalid emails properly.
"dynamic range" is called an IP pool
... servers for many email domains (depending on their configuration) will reject connections ...
if not check_dns and not check_smtp:
is preferred, as it's more pythonic :)This can look like
(autopep8 make these changes)
There was a couple comments I made, but aside from those, I'm very satisfied with what you did here.
You did a nice documentation job there, clever job done with the tests. Let's iron out the changes I mentioned here and the dependency questions, and then I think we're ready for the major release.
@ -14,3 +21,4 @@
we talk to seemingly accepts the email address.
## Everything gets rejected:
I have tested various domains where the MX is .mail.protection.outlook.com; some of them reject invalid emails properly and some don't. If you want I can send you some examples in private email, you can find my email address [here[(https://wiki.fsfe.org/Supporters/reinhard).
This was a great contribution, thank you!
I'll change the idna dependency and make a 1.0.0 release soon.