Validity of email for user registration

[inezkok]

I think the checking of the validity of emails during user sign up isn't stringent enough, leading to it accepting invalid emails like test@test where test isn't a valid domain since the last portion does contain a period and at least two characters e.g. .com, and random#@123 where the prefix should only contain alphanumeric characters, or underscores, periods, and dashes. Can follow this link for more info.

If not i think a possible enhancemement would be to send an email verification to the given emails containing a verification link, for the user to be successfully registered.

[ChillinRage]

Before I start implementing the backend validation, we might need to ensure both front end and backend follow the same validation logic for consistency.

So @Chen1x , how thorough/lax do you want the email validation to be? My lazy idea is to just use isEmail from import validator js library (one liner), which covers most general formats. Otherwise the most thorough one is to manually recode the entire format based on the wiki.

[Chen1x]

I think using regex should suffice, what do you think? I think importing a package just for email check could be overkill

[ChillinRage]

Okk. I think plain old regex works best too. Just coordinate our regex then.

[ChillinRage]

Actually, since it's just a regex validation, ig it would be easier if one of us just implement it. I can do it if you dm.

[Chen1x]

https://stackoverflow.com/questions/201323/how-can-i-validate-an-email-address-using-a-regular-expression

I think the top solution on the above post is good

(?:[a-z0-9!#$%&'+/=?^_{|}~-]+(?:\.[a-z0-9!#$%&'*+/=?^_{|}~-]+)|"(?:[\x01-\x08\x0b\x0c\x0e-\x1f\x21\x23-\x5b\x5d-\x7f]|\[\x01-\x09\x0b\x0c\x0e-\x7f])")@(?:(?:a-z0-9?.)+a-z0-9?|[(?:(?:(2(5[0-5]|[0-4][0-9])|1[0-9][0-9]|[1-9]?[0-9])).){3}(?:(2(5[0-5]|[0-4][0-9])|1[0-9][0-9]|[1-9]?[0-9])|[a-z0-9-][a-z0-9]:(?:[\x01-\x08\x0b\x0c\x0e-\x1f\x21-\x5a\x53-\x7f]|\[\x01-\x09\x0b\x0c\x0e-\x7f])+)])