I'm locked out of my 6 year old Chipotle account because they now say my email address is invalid when I login. Here is me asking for their help:

A few years back I bought a .family domain for my wife and I to have emails at ourlastname.family That lasted a week because almost every online service wouldn’t accept it. Now we have a .org

I hate it.

My first email address was @k.ro (a free email provider many many years ago) and many websites thought a valid second-level domain name cannot be just one letter

Same. There are a lot of sites that just outright refuse to accept my email address that I’ve had for years, because it’s not a .com TLD.

It's easier to Google "email regex [language]" and copy the first result from stack overflow.

@spider-man.net?

The only correct regex for email is: .+@.+

So long as the address has a local part, the at sign, and a hostname, it's a valid email address.

Whether it goes somewhere is the tricky part.

You should be able to double quote the local part and use the space. "like this"@email.net. Good luck getting that through a validator though.

Actually, one of our customers found out the hard way that there is harm in sending emails to invalid addresses. Too many kickbacks and cloud services think you're a bot. Prevented the customer from being able to send emails for 24 hours.

This is the result of them "requiring" an email for customers but entering a fake one if they didn't want to provide their email, and then trying to send out an email to everyone.

Our software has an option to disable that requirement but they didn't want to use it because they wanted their staff to remember to ask for an email address. It was not a great setup but they only had themselves to blame.

The best of validation is just to confirm that the email contains a @ and a . and if it does send it an email with a confirmation link.

Email standard sucks anyway. By the official standard, [email protected] and [email protected] should be treated as separate users...

.+@.+\..+

And that one isn't even a weird edge case! It's a domain with a sub domain, if they can't even cover that case then it's an extra shitty RegEx

Like my work email which is "[email protected]"

Let's see your regex pattern that covers every possible valid email address and rejects all invalid then. It's not remotely as easy as you're making it out to be.

Not saying this isn't a shitty pattern, but you can't make a claim like that.

Which would still be technically wrong. There does not need to be a dot.

Even that would be technically incorrect. I believe you could put an A record on a TLD if you wanted. In theory, my email could be me@example.

Another hole to poke in the single dot regex: I could put in fake@com. with a dot trailing after the TLD, which would satisfy "dot after @" but is not an address to my knowledge.

I've had issues with this in using govt emails too. DOD accounts all have multiple dots based on branch and dept. It broke so many systems and emails never went through.

The easiest and most correct check: any character, then @, then any other character.

Beautiful

That regex makes me nauseous

As the owner of a .info domain, I know this pain all too well.

They meant that they are intentionally trying NOT to help the customer, hopefully they just give up at some point. (That's why they are redirecting to bots and not to an actual human.)

Most IVR systems block that option because fuck you that's why.

There should be an '@,' followed by a domain ([email protected]).

What is your email address?

...and Hail.

Not without the support of an email address.

Technically you don't need a period for a valid address. "a@a" is a valid email address.

Yeah, I’ve noticed that a lot of sites are starting to disallow aliasing with email addresses. So annoying.

laughs in aliased Gmail addresses.

.+@[^\.]+\..+

I think you intended a different RFC?

Has anyone followed standards properly? There are weird workarounds in Linux's TCP implementation because they had to do the same non-standard workarounds as BSD which was added since there are too many buggy TCP implementations out there that will break if the RFC is followed to the letter...

It even has ascii-art svgbob would like!

You can use symbols like [ ] . { } ~ = | $ in the local-part (bit before the @) of email addresses. They're all perfectly valid but a lot of email validators reject them. You can even use spaces as long as it's using quotation marks, like

"hello world"@example.com

A lot of validators try to do too much. Just strip spaces from the start and end, look for an @ and a ., and send an email to it to validate it. You don't really care if the email address looks valid; you just care whether it can actually receive email, so that's what you should be testing for.

interesting if you're interested in the topic

The first rule of tautology club is the first rule of tautology club.

Yeah that video is great. My favourite part is the Russian post address thing.

He has a lot of interesting and funny talks like that.

The problem is their website also implemented an invalid email check when I try to login which is what got me to this point

Here is an alternative Piped link(s):

properly followed by most mail providers

Piped is a privacy-respecting open-source alternative frontend to YouTube.

I'm open-source; check me out at GitHub.

Nah, it's just a old school chat bot following a predefined flow chart.

yes but that would be an AI still

That is AI...

According to my kid, everything is spicy.

creepy

IMO the biggest issue is separating the customer from support people too much, and likely separating the support people from the actual business too much. They throw up that stupid bot in between customers and contacting support because they don't want support people answering the same questions a million times, yet in doing so they just make the customer experience worse. And the bot does a bad job helping people with basic stuff, and a worse job of letting people get actual help from a person when the bot realizes it can't do what the user needs.

The people on Twitter told me to use the website contact form because they don't have any actual connection to the company. I'm guessing they're outsourced and can regurgitate from an FAQ, but they have no ability to escalate to someone with any power.

I’m assuming by “dot” you meant @

In fact both are optional. With FQDN-Adressing a user without domain defaults to localhost, with Bang-Adressing there is no @ because the last system is left for interpretation of the last receiver and if he consideres it a user, so be it.

Then I might get the added benefit that someone from Chipotle's web dev team finds us dunking on them.

Same. Nowadays I just use a catch-all email address. [email protected]. Allows me to name, shame, and block the company that leaks my email address.

The bot may transfer it to an operator if you ask it right.

Or it may not, cause usually in such cases it's made clear initially that you are writing to a bot, and the purpose of that bot is to give the human a summary of what you want, to make it quicker (for them, not for you).

For me BK doesn't allow to add my card (even their web interface does, FFS, so I know it's not my bank or something). But at least I can see the order status (useful when playing board games somewhere near a BK, to not wait there and not to skip things said and dice rolled).

you hear about google deleting a lot of old accounts? imagine how many of those were used purely to make accounts on other sites.

It's obvious that these people don't work full time with a family

restaurant

Lol

Just put the I'd into YT.