Email validator does not accept numeric TLD

[progval@…]

The email validator does not accepte numeric TLDs, while they are valid.

An example : ​https://www.42registry.org/

[Ramiro Morales]

​https://www.42registry.org/ isn't a valid email addres at all. And adding a test to validate the 'something@42registry.org' address shows that our email validator doesn't reject it (tested with 1,3., 1.3.1, 1.3.X and trunk)

[anonymous]

I meant that 42registry.org provides domain name registration for .42 domains. So progval@progval.42 is valid.

[Aymeric Augustin]

I don't want to start a policy debate, but I have to point out that .42 only works for people who're using Global Anycast's DNS — in other words, it doesn't work for something like 99.999% of Internet users (take or give one 9).

The home page of Global Anycast (only available in French) says that the next steps to help the project are "contribute to create a working proof of concept" and "help define protocol v1". This indicates that the projects is stil far from mainstream.

Given that this regex is subject to endless debates — see #17405, #17386, #17100, #16310, and that's just from the first of the eleven pages of results for "email validator" — I'm reluctant to accept this ticket.

[Gabriel Hurley]

After some discussion between PaulM and myself, given that there are no globally approved TLDs that are only numbers, and given that you can write your own validator if you so desire, and given the difficulty with that regex in general (as already pointed out) I'm gonna make a call on this not being a good candidate for inclusion in Django core at this time since that's three core devs all against it.

If you feel this decision is incorrect/inappropriate, please take it to the Django Dev mailing list and make your case to the community. Thanks for pointing this out, though!