On Oct 10, 9:35 am, James Bennett <ubernost...@gmail.com> wrote: > So what I'd like to propose is that EmailField essentially check that > the value contains an '@', and a '.' somewhere after it. This will > cover most addresses that are likely to be in actual use, and various > confirmation processes can be used to rule out any invalid addresses > which happen to slip through that.
Good idea - every real project I've had where this became an issue had to switch to some sort of actual mail-based validation system (confirmation, live MX connection, etc.). Adding doc links about email validation tools would be better because it'd establish that this is something which deserves some thought if you rely on email addresses. Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
