Everyone knows what an email address is, right? (Quiz)
-
Now i just need a registrar that allows emoji...
wrote last edited by [email protected]Any should. Any unicode is converted to alphabetical anyways, through "xn--" + a punycode conversion. Which is actually fairly important for places that don't use the Latin alphabet.
See http://xn-bdk.gay/, which is the same as http://ツ.gay/
(Someone set this up on 196 a while ago, they said they were using Namecheap)
-
You shouldn’t be validating emails yourself anyway. Use a library or check for only the
@and then send an email confirmation.wrote last edited by [email protected]Use a library
Please, no. If someone wrote email address "validation" complex enough to warrant a library, then their code is almost certainly wrong.
or check for only the @ and then send an email confirmation.
Yes. Do that.
If your boss demands a more detailed check at input time, then make it display warnings, not errors, and continue to the confirmation sending step if the user chooses to ignore the warning.
-
This post did not contain any content.
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 "[email protected]", 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.
-
This post did not contain any content.
12/21. It was highly entertaining though.
-
Any should. Any unicode is converted to alphabetical anyways, through "xn--" + a punycode conversion. Which is actually fairly important for places that don't use the Latin alphabet.
See http://xn-bdk.gay/, which is the same as http://ツ.gay/
(Someone set this up on 196 a while ago, they said they were using Namecheap)
oh jesus, rabbit hole accepted, thanks!
-
I don't validate emails, I test them.
That's your email? OK, what did we send it? if we couldn't send to it or the user can't read it there's no reason to accept it.
OK, maybe I do some light validation first, but I don't trust the email address just because it's email-address-shaped.
wrote last edited by [email protected]I don’t validate emails, I test them.
Hooray! You get a gold star.
OK, maybe I do some light validation first,
I hope your "validation" does nothing more than show a warning that the user is allowed to ignore.
I have seen too many systems built by people who think they know what's valid or not before and after the
@sign*, and they are almost always dead wrong. In the worst cases, such systems accept an unusual-looking address and claim to send the expected verification message, but never actually send it. Of course, these systems won't work for some people, and since none of their online docs or support staff know why, those people will be locked out of using the system and funneled into bottomless pit of misery if they try. Please don't build broken garbage like this.*Fun fact: Not so terribly long ago, even the
@sign didn't have to be present. Some email addresses were bang paths. I'm not sure if any of these are still in use, but it wouldn't shock me to learn that they are. -
Let us recite the email validator’s oath:
If it has something before the
@, something between the@and the., and something after the., it’s valid enough.The ultimate validation is to see if it gets sent.
-
And is it really valid if my email provider doesn't accept it? If it's not universally accepted or standard, then it doesn't matter if it's technically valid.
If your email provider doesn’t accept [email protected] is it then invalid?
-
I scored 16/21 on https://e-mail.wtf/ and all I got was this lousy text to share on social media.
This was fun!
Edit: people, upvote the OP, not me
Don't tell me what to do!
-
This post did not contain any content.
nice. though valid but obsolete is not a thing... if it's obsolete it's invalid.
-
Even if it's a completely valid address and the domain exists, they still might've fat fingered the username part. Going to extreme lengths to validate email addresses is pointless, you still have to send an email to it anyway.
I seem to have annoyed an admin of an instance enough for them to subscribe my signup email to hundreds of dating profiles (presumably using a service that offers to harass someone for you)
Many of them aren't good at validating email
One in ten has one email arrive, asking me to click a link to confirm
9 in ten have 5 emails before I notice them:
- Please click a link to confirm
- You received a wink
- You received a wink
- You received 3 chat requests
- You received a link
So it's important to not send emails beyond the validate one to unvalidated addresses, to perfect your service annoying or harassing this parties
Also, use a disposable address for signing up to Lemmy
-
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 "[email protected]", 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.
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.
-
I can't even view it...I get a TLS error
My phone blocked the site, citing "harmful content"
-
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 "[email protected]", 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.
Same as I have a .party domain. So I made a place holder (looking at you progressive) email [email protected]
-
This post did not contain any content.
I scored 16/21 on https://e-mail.wtf/ and all I got was this lousy text to share on social media.
I feel pretty good about that
-
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 "[email protected]", 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.
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
-
This post did not contain any content.
And after that, I now can't wait for the next pull request with a regular expression on email validation to come through.
-
This post did not contain any content.
I vaguely remember a panel where a guy went through various cases like these.
One of the things that stood out is that not every email provides implements the same specs, so one provider might allow you to set up a "valid" email address that might not be able to communicate with other providers as they consider it "invalid".
-
I gave up when I got like 5 wrong. I've ran mail servers for decades, most of the invalid "valids" would get rejected by any mailservers I've administered.
Just because it's not something you'd use anymore doesn't mean it isn't valid.
WEP is still a valid form of wireless encryption, but no one would use it anymore (and so would be obsolete). It's still a part of the 802.11 standard.
-
Let us recite the email validator’s oath:
If it has something before the
@, something between the@and the., and something after the., it’s valid enough.Fails for when there is no TLD. Just send an email and validate a response eg from a link.
