Also as the registrant of one of those new fancy TLDs, much like the owner of this website (email.wtf), their own email addresses will fail those stupid email validation checks that only believe in example@example.[com|net|org]

Shitty websites will fail "example@email.wtf", guaranteed - despite it being 100% valid AND potentially live.

Source - I have a ".family" domain for my email server. Totally functional, but some shitty websites refuse to believe it.

[–] locuester@lemmy.zip 4 points 2 days ago (1 children)

Yeah I have a .engineering for my biz. I also registered mycompanyengineering.com to get through places that won’t take the new TLDs.

Usually banks.

[–] Appoxo@lemmy.dbzer0.com 1 points 2 days ago

Seems like a weird choice as the primary TLD.
I'd switch it just to reduce the annoying typing hassle and to avoid misspelling.

It's already unusual if I say "My email is givenName@LastName.eu"
And that trips so many persons.
First: I have my own domain
Second: It's not gmail, apple or a local provider
Third: The TLD isnt .de or .com but .eu

[–] JackFrostNCola@aussie.zone 2 points 2 days ago

I have plenty of website reject even my fairly vanilla [email]+XYZ@ address add–ons

[–] notarobot@lemmy.zip 1 points 2 days ago (3 children)

I'm not sure I blame the sites. The spec is so complex that it's not even possible to know which regex to use

[–] bignose@programming.dev 1 points 1 day ago* (last edited 1 day ago) (1 children)

The spec is so complex that it’s not even possible to know which regex to use

Yes. Almost like a regex is not the correct tool to use, and instead they should use a well-tested library function to validate email addresses.

[–] notarobot@lemmy.zip 1 points 1 day ago* (last edited 1 day ago)

Exactly! But its not obvios. So most of those shitty websites don't even know they have a problem.

Then there are also people ignoring it on purpose. I once read a reddit comment saying 'well of your address looks like "John wick 🐶❤️"@2001:0db8:85a3:0000:0000:8a2e:0370:7334 I don't event want your email in my DB because oit will break something

[–] axEl7fB5@lemmy.cafe 2 points 2 days ago (1 children)

const emailRegExp = /^[\w.!#$%&'*+/=?^`{|}~-]+@[a-z\d-]+(?:\.[a-z\d-]+)*$/i;

per the HTML specification. From https://developer.mozilla.org/en-US/docs/Learn_web_development/Extensions/Forms/Form_validation#validating_forms_without_a_built-in_api

[–] notarobot@lemmy.zip 2 points 2 days ago (1 children)

That's one very random place to find that. There are a lot of different one and there is no way we all just agree to use that one.

Look art his site that shows a more complete and (in theory) official website. While also explaining that there is no regex that is perfect

https://emailregex.com/

(Compete regex for the lazy)

(?:\[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-]\*\[a-z0-9])?\\.)+\[a-z0-9]\(?:\[a-z0-9-]\*\[a-z0-9])?|\\\[(?:(?:25\[0-5]|2\[0-4]\[0-9]|\[01]?\[0-9]\[0-9]?)\\.){3}(?:25\[0-5]|2\[0-4]\[0-9]|\[01]?\[0-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])+)\\])

[–] axEl7fB5@lemmy.cafe 2 points 2 days ago (1 children)

MDN isn't a very random place?

[–] notarobot@lemmy.zip 1 points 1 day ago

No. But it's on the form validation topic.

[–] ulterno@programming.dev 0 points 1 day ago

I have a feeling, the ones codapine is stating, didn't even care to half-read the spec and just went with what they knew from experience.
Maybe they didn't even know there was a spec.
Maybe they asked ChatGPT for the regex.

[–] BlushedPotatoPlayers@sopuli.xyz 2 points 2 days ago

I have a spam collecting address @freemail.hu , the domain is live and working since 96, sometimes it's not accepted, because it's not Gmail I guess

[–] aeiou_ckr@lemmy.world 2 points 2 days ago

Same as I have a .party domain. So I made a place holder (looking at you progressive) email ___+haslazydevs@gmail.com