Hey! @Eikeike While signing up, it stores the email ID as it is provided by the user.
I think we should convert it to lowercase; the same thing happens when we sign up and sign in. Even if there is some capital letter in the email, it still works, even if the email has no capital letter.
One more thing: my email ID is [email protected] and I am signed up with [email protected] I got an email to verify the account.

See Wiki

Technically all other local-parts are case-sensitive, therefore [email protected] and [email protected] specify different mailboxes; however, many organizations treat uppercase and lowercase letters as equivalent. Indeed, RFC 5321 warns that "a host that expects to receive mail SHOULD avoid defining mailboxes where ... the Local-part is case-sensitive".

While it is a common practice to keep the naming convention case-insensitive, the RFC itself says it is case-sensitive and there are a few mail servers around which allow case-sensitive naming. So, IMHO we should keep this case-sensitive only

Good discussion. As much as the spec of email addresses in general say they are case-sensitive, I'd prefer to enhance user experience. I'll take a peek into this issue, or if anyone's willing to take up this issue, that would be great!

A possible solution would be simply to .toLowerCase() the input provided by the user for username and email, before inserting it into the DB. And also, it would need to be normalised again when checking the credentials (in Local Auth Strategy).

@AmruthPillai can i work on this ?? i will do those two things , you have mentioned above ??

hello @AmruthPillai , can I go with this issue

hello @AmruthPillai, is this issue still open??
can i trying to solved this issue

@AmruthPillai I was wondering about the statement you put forward earlier, could you please guide me further taking the quote below as the "beginning" for further conversation. Regards

A possible solution would be simply to .toLowerCase() the input provided by the user for username and email, before inserting it into the DB. And also, it would need to be normalised again when checking the credentials (in Local Auth Strategy).