Where did you get that “RFC standard” regex?
It doesn’t allow domain names with one component RFC5321
Neither does it allow spaces in quoted string, as per RFC5322
This, 👋@✉️.gg, is already a working email address in most clients and if RFC6532 ever gets accepted, it would be officially recognized as such.
My point isn’t to make your regex bad, just that it doesn’t validate or invalidate an email properly. Nothing stops me from giving you and invalid but syntactically correct email after all.
You have to send an email anyways to verify, so the most you can check is the presence of one @ symbol.
Where did you get that “RFC standard” regex? It doesn’t allow domain names with one component RFC5321
Neither does it allow spaces in quoted string, as per RFC5322
This, 👋@✉️.gg, is already a working email address in most clients and if RFC6532 ever gets accepted, it would be officially recognized as such.
My point isn’t to make your regex bad, just that it doesn’t validate or invalidate an email properly. Nothing stops me from giving you and invalid but syntactically correct email after all.
You have to send an email anyways to verify, so the most you can check is the presence of one @ symbol.