Proactive Validation for Email Addresses

aimementoring / blueprint

This project defines some standards for all AIME platforms.

5 stars 0 forks source link

Proactive Validation for Email Addresses #26

Open mischacolley opened 5 years ago

mischacolley commented 5 years ago

I've been importing missing emails into MailChimp the last two days and found a number of really common email syntax errors. Wondering if we could build a nice improvement into our email validation to help catch them .... definitely a nice to have but I think it would be the type of thing that is a really nice touch for users. I'd prefer to do this over making them type their email again for instance.

.con
.cm
.co // Not sure iof this is ever valid ? I think all .co have something after as well? i.e. .co.uk or - .co.nz
,com
I've even seen ;com

Thoughts?

mischacolley commented 5 years ago

@davidpaley considering you've been working on validation this could be a good one to consider with #34

davidpaley commented 5 years ago

This one is complicated because actually an email could finish with .cm. It could be an error but it could be a valid email too. You can't validate to not allow email with different finish than .com, that would be incorrect.

Different is the case for ,com or ;com that would not pass our current validation because it can't be a valid email. All the other cases you mentioned are valid and could be valid email address.

https://www.textmagic.com/free-tools/email-validation-tool