Good points, you have eased my mind. It sounds like following the standard is the exception here (^_^) A well placed word to the wise should handle those special cases.
Thanks guys. Cynthia On Nov 10, 3:38 pm, Eli Jones <eli.jo...@gmail.com> wrote: > While the RFC says e-mail is "supposed" to be case sensitive.. you will save > yourself a lot of headaches by doing an insensitive search on email > address... most e-mail providers probably prevent case sensitive e-mail > addresses anyway. > > If some person tries to sign up.. and they happen to be an individual from a > E-mail provider that allows case sensitive e-mails, and there is another > person at this E-mail provider with a different case version of their e-mail > address, AND both of these people sign up for your service... Then, you can > deal with that glitch as a special case (so to speak). > > On Tue, Nov 10, 2009 at 2:02 PM, Cynthia Kurtz <cfku...@cfkurtz.com> wrote: > > > Here is a question about the User functions that others may be able to > > answer. > > > My app (rakontu) creates invitation-only groups (for story sharing). > > Group managers use email addresses to tell the app whom they have > > invited to join the group. When an invited person first visits the > > app, it checks the users.get_current_user().email() against the emails > > the group manager typed in. If it finds a match, the person becomes a > > group member and things go smoothly from there. > > > However, there is a problem with case sensitivity in gmail addresses. > > When a person creates a gmail account, they type in anything they like > > - upper or lower case or whatever. What shows on their gmail page > > (where they read their email) is all in lower case. But what the > > users.get_current_user().email() returns is NOT all lower case. It's > > whatever they typed in when they first created the gmail account. And > > most people have no idea what that was. > > > For example, say I created a gmail account called "JJones". When I log > > in to the gmail account, it says at the top "jjo...@gmail.com". When I > > invite "jjones" to join a Rakontu group, and the person makes their > > first visit, users.get_current_user().email() returns "JJones" and the > > cases don't match and the person can't join. But if I invite "JJones" > > to join, the cases DO match and they can join. > > > The problem is, there is no way for the group manager to know what the > > person's correct email case is, since it is apparently impossible to > > find the original capitalization on the account (I've been all over > > gmail looking). You can even sign in to Google with either case form > > of your gmail account. > > > I *could* do a case-insensitive match on the emails to see if > > users.get_current_user().email() matches the list. Probably it is not > > very likely that two people with similar but different-case emails > > could have been asked to join at the same time. But I don't like > > having to do that especially because email is *supposed* to be case > > sensitive. I'd like to find a better way to resolve this. > > > Any advice? > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
