[Django] #33967: Make EmailValidator accept internationalized local part
Django
-------------------------------------+-------------------------------------
Reporter: j-bernard | Owner: nobody
Type: New | Status: new
feature |
Component: Core | Version: 4.0
(Mail) | Keywords: IDNA EAI
Severity: Normal | EmailValidator RFC
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
This ticket is the first of a list of tickets aiming at bringing Email
Address Internationalization (EAI) compliance to Django by supporting
International Domain Name (IDN) with regards to the latest standard (IDNA
2008) and fixing some processing on internationalized domains or email
addresses.
The whole EAI compliance was cut into small chunks to make it clearer and
allow independent discussions on specific elements.
I know there was a lot of discussion on the EmailValidator but curiously,
hardly anyone seemed to refer to the actual email address standards.
Many of the previous tickets were closed as they would only prevent some
buggy email addresses to be used but this one aims at making the email
validator more internationally inclusive by accepting valid email
addresses that are currently being rejected.
The current EmailValidator does not accept internationalized local-part in
email addresses.
To fix this issue, the local part regex has to be rewritten in a way that
allows Unicode characters as specified in
[https://datatracker.ietf.org/doc/html/rfc6531#section-3.3 RFC6531
section-3.3].
--
Ticket URL: <https://code.djangoproject.com/ticket/33967>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-------------------------------------+-------------------------------------
Reporter: j-bernard | Owner: nobody
Component: Core (Mail) | Version: 4.0
Severity: Normal | Resolution: wontfix
Keywords: IDNA EAI | Triage Stage:
EmailValidator RFC | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* status: new => closed
* resolution: => wontfix
Comment:
Thanks for this ticket, however adding a new dependency is always
controversial and it isn't a light decision so a strong consensus on the
mailing list is required. Please first start a discussion on the
DevelopersMailingList, where you'll reach a wider audience and see what
other think, and
[https://docs.djangoproject.com/en/stable/internals/contributing/bugs-and-
features/#requesting-features follow the guidelines with regards to
requesting features].
Personally, I don't think it's worth complexity. My initial response would
be similar to the Python's, i.e. ''"If you need the IDNA 2008 standard
from RFC 5891 and RFC 5895, use a third-party validator"''.
--
Ticket URL: <https://code.djangoproject.com/ticket/33967#comment:1>
Django
-------------------------------------+-------------------------------------
Reporter: j-bernard | Owner: nobody
Type: New feature | Status: closed
Component: Core (Mail) | Version: 4.0
Severity: Normal | Resolution: wontfix
Keywords: IDNA EAI | Triage Stage:
EmailValidator RFC | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* cc: Florian Apolloner (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/33967#comment:2>
Django
-------------------------------------+-------------------------------------
Reporter: j-bernard | Owner: nobody
Type: New feature | Status: closed
Severity: Normal | Resolution: duplicate
Keywords: IDNA EAI | Triage Stage:
EmailValidator RFC | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => duplicate
* component: Core (Mail) => Core (Other)
Comment:
As far as I'm aware, this is a duplicate of #27029. Please leave comments
there .
--
Ticket URL: <https://code.djangoproject.com/ticket/33967#comment:3>