-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2020.example.com is a valid fqdn #68
Comments
Thanks, @Spone, good catch. I was operating on the RFC-952 spec which disallows hostnames beginning with non-alpha characters. This was definitely changed in the last 35 years (for example, RFC-1123), and I should have caught that. I do know that hostnames can consist of only numbers, but primary domains cannot be only numeric. This example should be valid in all modes. I'll use your example above in the spec and get it fixed. I'll expect to have that done later today. |
* issue-68-numeric-subdomain-fails-validation: Fix regexp for numeric subdomains (fixes #68) [specs] Add tests for numeric subdomains
* develop: Bump version to `2.2.1` Add `rubocop-rake` to dev dependencies Enforce domain character limit Allow mailbox-only addresses in `:rfc` mode Fix regexp for numeric subdomains (fixes #68) [specs] Add tests for numeric subdomains
Fixed in Thanks, @Spone, for reporting! |
Thanks a lot, I managed to catch the issue by running the validation on a production database export, so thank you anonymous user who has a uncommon email :) |
I think primary domains can be only numeric. For example, the strict mode is marking emails like |
This is true, |
Yes! Thanks for catching this. @delphaber, can you please add this as a separate issue? Specifically something like "valid numeric domains are considered invalid strict mode." I see the failing test in your PR. Thanks! Yeah, that will help make sure that we don't break it again, but I need to get in there and fix the validation RegEx. I hope to get to that in the next couple days. |
Specifically, for my own reference, RFC 1123 states:
|
will do! |
Currently in
strict
mode:but
2020.example.com
is indeed a valid FQDN, right?The text was updated successfully, but these errors were encountered: