Everyone knows what an email address is, right? (Quiz)
-
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.
-
I didn't understand this one. How do you have a no dot domain? Like you need to distinguish from example.com or example.wtf
Edit: do you mean if you own
.googleyou can have youremail@googleaddress?wrote last edited by [email protected]In response to your edit.
Yes, or countries could use their cctld, e.g. email@us or noreply@uk.
Or any tld owner could do the same with theirs, of course.
-
I didn't understand this one. How do you have a no dot domain? Like you need to distinguish from example.com or example.wtf
Edit: do you mean if you own
.googleyou can have youremail@googleaddress?you could also send mails within your local network, the hostname just has to resolve and have a mail service running
-
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.
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 [email protected]"
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.deor.combut.eu -
This post did not contain any content.
13/21, seems like I am not significantly different from random guessing
-
13/21, seems like I am not significantly different from random guessing
Got the same, I can't believe how many weird comments and extra random things can get added into an email address.
-
nice. though valid but obsolete is not a thing... if it's obsolete it's invalid.
Agreed! (because then I would get 3 more points on the test)
-
Fails for when there is no TLD. Just send an email and validate a response eg from a link.
No. The number of users who have a real email with no TLD is far less than the number of users who will accidentally type an email with no TLD if you don’t validate on the front end.
I’m here to help 99.9% of users sign up correctly, not to be completely spec-compliant for the 0.1% who think they’re special.
-
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.
Hooray, you have better security than Apple, who won't let me use my own email because some idiot in Australia used it first.
-
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'm not sure I blame the sites. The spec is so complex that it's not even possible to know which regex to use
