#31960: Document that Django email validator does not enforce valid emails
-------------------------------+--------------------------------------
Reporter: James Pic | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 3.1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Description changed by James Pic:
Old description:
> Currently, Django makes it seem that using an EmailField / EmailValidator
> will protect projects from getting invalid emails in their database, for
> example: emails starting with a dot like ".f...@bar.com" will be invalid
> as expected.
>
> But in reality, Django doesn't actually care :
> https://code.djangoproject.com/ticket/31959#ticket
>
> This makes the following documentation statement inaccurate:
>
> > "EmailField: A CharField that checks that the value is a valid email
> address using EmailValidator."
>
> Source :
> https://docs.djangoproject.com/en/3.1/ref/models/fields/#emailfield
>
> It would be only fair to users to document that the EmailValidator will
> let invalid emails through, which will be the cause of SMTPError, and
> that people who don't want invalid emails in their EmailField must
> override and fix Django's default behaviour.
New description:
Currently, Django makes it seem that using an EmailField / EmailValidator
will protect projects from getting invalid emails in their database, for
example: emails starting with a dot like ".f...@bar.com" will be invalid as
expected.
But in reality, users must not count on Django for that:
- https://code.djangoproject.com/ticket/31959
- https://code.djangoproject.com/ticket/25452
This makes the following documentation statement inaccurate:
> "EmailField: A CharField that checks that the value is a valid email
address using EmailValidator."
Source :
https://docs.djangoproject.com/en/3.1/ref/models/fields/#emailfield
It would be only fair to users to document that the EmailValidator will
let invalid emails through, which will be the cause of SMTPError, and that
people who don't want invalid emails in their EmailField must override and
fix Django's default behaviour.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/31960#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.e61435f3105145b0f792b5c072f64fc0%40djangoproject.com.
