Post

This feature of those services is the bane of my life. I think the threshold is like 30 days and I don't often think that far ahead.

1. I viewed source and saw TypeScript, which is awesome 2. That's the most uncivilized attack on someone's self esteem I've seen in days. I love it

If I may, you should make clear it's about the syntax and not necessarily a proper mailbox. I tripped on the first one considering the domain as invalid as it's intended for documentation use and not an actual service

Quotes & brackets tripped me up. I had no idea. For emails in public facing apps, not local apps or networks (how else would like @[@] work??), my validation rule is basically does it have an @, at least one letter after @, at least one dot and one letter at the end. And !bad chars like : or ,.

It wouldn’t, and a lot of the examples that are valid wouldn’t work in practice. The spec is very broad, the world has changed a lot since it was written.

Totally agree. I've been doing this a couple of decades. I remember the wild west of email and see how much it's changed for the better. Unfortunately, very few of the suggested regexes and validation libraries have...not.

Yes, I was tempted to put a disclaimer at the end stating that this is all valid/invalid _according to the spec_ and has no bearing on the reality of what your email provider or any given website will accept.

To be fair, as far as RFC 5322 goes, if you bring your "quotes" or [square brackets] you can do whatever tf you want. It is a surprisingly relaxed spec.