EmailField? does not comply with SMTP standard
|Reported by:||qqq1one@…||Owned by:||nobody|
|Severity:||Normal||Keywords:||EmailField SMTP compliance|
|Cc:||Triage Stage:||Ready for checkin|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
Email addresses in the literal form (where the square brackets are included):
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 [126.96.36.199], which
indicates an (IPv4) Internet Address in sequence-of-octets form.
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.
Change History (5)
comment:1 Changed 4 years ago by melinath
- Component changed from Uncategorized to Core (Mail)
- Needs documentation unset
- Needs tests set
- Patch needs improvement unset
- Triage Stage changed from Unreviewed to Accepted
- Version changed from 1.3 to SVN