#16166: EmailField? does not comply with SMTP standard
----------------------------------------+-------------------------------
Reporter: qqq1one@… | Owner: nobody
Type: Bug | Status: new
Milestone: | Component: Uncategorized
Version: 1.3 | Severity: Normal
Keywords: EmailField SMTP compliance | Triage Stage: Unreviewed
Has patch: 0 | Easy pickings: 0
----------------------------------------+-------------------------------
Email addresses in the literal form (where the square brackets are
included):
user@[123.123.123.123]
are indicated as invalid by EmailField.
But the literal form is valid as per section 4.1.3 of the SMTP standard:
Sometimes a host is not known to the domain name system and
communication (and, in particular, communication to report and repair
the error) is blocked. To bypass this barrier a special literal form
of the address is allowed as an alternative to a domain name. For
IPv4 addresses, this form uses four small decimal integers separated
by dots and enclosed by brackets such as [123.255.37.2], which
indicates an (IPv4) Internet Address in sequence-of-octets form.
Reference: [http://tools.ietf.org/html/rfc2821#section-4.1.3]
Also referred to in [http://tools.ietf.org/html/rfc1123#page-57]:
5.2.17 Domain Literals: RFC-822 Section 6.2.3
A mailer MUST be able to accept and parse an Internet domain
literal whose content ("dtext"; see RFC-822) is a dotted-
decimal host address. This satisfies the requirement of
Section 2.1 for the case of mail.
An SMTP MUST accept and recognize a domain literal for any of
its own IP addresses.
--
Ticket URL: <https://code.djangoproject.com/ticket/16166>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
