Yeah, see @hauleth’s answer. But as with emails there’s a huge difference between validating a postal by format (which is a sanity check at best) and actually validating a postal for being a correct (and existing) postal.
LostKobrakai
Schultzer
Concerning
EmailValidator, indeed, the regular expression used is the one used by browsers to validate
Email validation has been done before in the community, I would take a look at Pow.Ecto.Schema.Changeset — Pow v1.0.39 for a spec compliant unicode email validation.
1
achedeuzot
hauleth
Seems that this is still not fully valid, as this do not allow [::1] as a domain part. Additionally it will allow .foo. as a domain, which is incorrect.
2
achedeuzot
Hi folks !
I’ve published v0.2.0 with your feedbacks.
- I’ve improved the URLValidator by better documenting what is and what isn’t supported.
- I’ve added all countries for the PostalCodeValidator (still no full database but a first sanity check of the format). The formats come from http://i18napis.appspot.com/, recommended by the (now deprecated) unicode postal code database.
- I’ve added better documentation to EmailValidator and an
opt-inapproach to which checks you want to apply. I also addedpow’s package email validator and fixed some of the shortcomings found by @hauleth. - I’ve added the
validate_manyhelper as it’s indeed common to validate multiple fields with the same options.
As usual, happy to have your feedbacks, issues and pull requests 
Cheers 
3
danschultzer
Pow Core Team
Good catch, thanks! Didn’t validate the domain properly.
I didn’t add IP addresses as it’s strongly discouraged with RFC 3696:
The domain name can also be replaced by an IP address in
square brackets, but that form is strongly discouraged except for
testing and troubleshooting purposes.
@achedeuzot you may want to take a look at the changes in Improve email validation · Issue #560 · pow-auth/pow · GitHub as I didn’t validate the domain properly. Each DNS label should be validated. There are also some additional validation that I didn’t include such as checking for reserved domains (like example.com, these domains can’t receive e-mail).
2
achedeuzot
Thanks for the link to the pow issue link. I’ll update the validator check to better reflect your updates. It looks far better than mine which only addressed a few specific issues.
0
achedeuzot
Hi everyone !
Just to let you know I’ve released a new version with your feedbacks and an improvement:
- The
EmailValidatorhas been updated to the latest:powlogic for better handling all emails use-cases, thanks @danschultzer ! - I’ve added a
PhoneNumberValidatorthat useslibphonenumberunder the hood - Some dependency updates & compatibility with Elixir 1.11
As usual, if you have feedback, suggestions etc. don’t hesitate. Cheers 
1