Opened 2 years ago
Closed 2 years ago
#33967 closed New feature (duplicate)
Make EmailValidator accept internationalized local part
| Reported by: | j-bernard | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (Other) | Version: | 4.0 |
| Severity: | Normal | Keywords: | IDNA EAI EmailValidator RFC |
| Cc: | Florian Apolloner | Triage Stage: | Unreviewed |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
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 RFC6531 section-3.3.
Change History (2)
comment:2 by , 2 years ago
| Cc: | added |
|---|
comment:3 by , 2 years ago
| Component: | Core (Mail) → Core (Other) |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
As far as I'm aware, this is a duplicate of #27029. Please leave comments there .