-3
I’m having a somewhat unusual (or common I don’t know) problem. I have an e-mail registration field. The user adds an email, the system checks if the email already exists in the database, if not he registers, if yes, he does not register.
It turns out that if the user differentiates a letter from the email to uppercase the system interprets the email differently. For example, there is an email in the BD: "[email protected]", if a user tries to register the email "[email protected]" the system allows.
What can I do to disable this uppercase/lowercase check? Or is it not necessary? the system has to do this check anyway.
Considerations you should do: If I send the email to
X
will be the same as I send tox
? If yes, you must treat to consider them equivalent. Another is: it will matter to the user to registerX
and store in the bankx
?– Woss
Have you read RFC to know which parts make a difference? Depending on the Marcos@ server and milestones may actually be different accounts. at (@) the normal rules apply to Domain name. on the left, the implementation is allowed to do as it sees fit.
– Bacco
But that wouldn’t be half wrong, because, like, if I’m a public person who gets a lot of emails at the [email protected]. If the guy types the email on his cell phone he already leaves the first letter capitalized, so [email protected], so the emails that were for me are addressed to another, I think there is no e-mail server that allows it to know.
– Vitor Leite
It is better to develop in certainty than in speculation... quantity of bugs certainly decreases.
– Woss