Opened 18 years ago
Closed 17 years ago
#3603 closed (wontfix)
Email validation error on ip literal mail routes
Reported by: | Owned by: | Adrian Holovaty | |
---|---|---|---|
Component: | Forms | Version: | 0.95 |
Severity: | Keywords: | ip literal email validator | |
Cc: | Triage Stage: | Design decision needed | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Django doesn't validate IP literal email addresses.
May be a pointless patch, but then again, someone may find it useful.
Attachments (1)
Change History (5)
by , 18 years ago
Attachment: | emailpatch.patch added |
---|
comment:1 by , 18 years ago
Component: | Core framework → django.newforms |
---|---|
Triage Stage: | Unreviewed → Design decision needed |
I think before we go down this route we need to determine just how much of the insanely-complex RFC822 address spec we want to support; it's definitely a diminishing-returns problem...
Also, if this is to be dealt with it needs to be dealt with in newforms, so I'm going to change the component.
comment:2 by , 18 years ago
Erm? Come again?
No offence, but email is KINDA core to alot of applications these days. I've not submitted and tested this patch because I thought it might be nice. It is a bug. Django does not support RFC2822 Addresses. It *should*. That's why RFCs exist. Domain literals, while weird and not really accepted, are a part of industry today, and as such are specified as part of the standard.
e.g. In my case, I am sending email to a network device that does not understand properly (read: it's buggy as hell) the emails it should be receiving.
comment:3 by , 18 years ago
Incidentally, this is nothing to do with "forms" per se.
It's a model that's actually executing this validator.
Email patch