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:
I also reached out to them on Twitter but they directed me to this form. I followed up with them on Twitter with what happened in this screenshot but they are now ignoring me.
Somebody made a shitty regex.
Probably, from what I can see the address in question isn't really that exotic. but an email regex that validates 100% correctly is near impossible. And then you still don't know if the email address actually exists.
I'd just take the user at their word and send an email with an activation link to the address that was supplied. If the address is invalid, the mail won't get delivered. No harm done.
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.
Email standard sucks anyway. By the official standard, User@email.com and user@email.com should be treated as separate users...
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.
.+@.+\..+
That's what it looks like to me too
I could probably write a RegEx for email format validation that's accurate, but why would I when there are ones already written and readily available that covers all possible legit variations on the standard? I never understood why people insist on writing their own (crap) RegEx for something with as many possible variations they can miss like email...
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
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.
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 "my.name@umbrellacompany.company.com"
Smells like bad regex
Exactly. After the @ they should just confirm there's at least one period. The rest is pretty much up in the air.
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.
Beautiful
That regex makes me nauseous
That is 100% a bot, and whoever made the bot just stuck in a custom regex to match “user@sld.tld” instead of using a standardized domain validation lib that actually handles cases like yours correctly.
Edit: the bots are redirecting you to bots are redirecting you to bots. This is not a bug. This is by design.
This is not a bug. This is by design.
I'd say it's a bug in the design as it clearly fails to work with a completely fine email.
It might even be worse than that, imagine if they let one of those learning algorithms handle their customer service.
That all loads of companies that do. In this case it would be better because it would actually understand what constitutes an email rather than running some standard script with no comprehension of what it's doing.
The difference between AI and automated script responses is AI is actually thinking at some level.
But using a standardized library would be 3PP and require a lot of paperwork for some reaosn.
The best way to validate an email address is to sent it an email validation link.
Anything outside of that is a waste of effort.
Modern customer service is about willfully designed layers of broken system engineered specifically to frustrate the majority of people that can't regulate their emotions. It's always a series of about "12 doors" you have to cross through that are exceedingly difficult to pass through. They are designed to sap your energy with the hope that you eventually reach a boiling point, hang up, get distracted, go on with your day and never follow up out of fear of starting the same process again.
Chipotle is telling you they don’t want your money
I would sure like the free stuff they promised me after my past purchases
Clearly AI.
Nah, it's just a old school chat bot following a predefined flow chart. And in this flowchart someone implemented an improper email check.
It's pretty much the same as if there was just a website with an email field which then complains about a non valid email which in fact is very valid. And this is pretty common, the official email definition isn't even properly followed by most mail providers (long video but pretty funny and interesting if you're interested in the topic).
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.
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...
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.
Look, I get it, but first, what's your email address?
I'm not falling for that again
Not without the support of an email address.
If that's their standard, you can probably just edit the html to make the login button active and then sign-in.
It depends if they have backend validation on their API as well that has the same rules
This is why you never attempt to validate an email address beyond requiring an @ followed by a period, and send a verification email
Which is blatant incompetence considering there is a very straightforward RFC covering domain names.
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!
Pepper is making you salty
Pepper is spicey
According to my kid, everything is spicy.
Have you tried giving them your email address?
My Ameriprise account has its own email address because the fuckers don't believe any email starting with email@ is a real email. I've called them a million times and got them to file a bug, which they did, and then closed as won't fix.
Ⓕ
Sorry for your loss..
Why are you keeping track of the age of your Chipotle account?
Because those points add up, playa.
Gotta count down the days 'til it's legal.
creepy
enshitification of everything intensifies
Not enshittification. Just the usual shitty customer service experience.
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.
And to an EDU account, what a madman.
Reply, that you'd be happy to provide your e-mail. but first, you must verify them, my having them provide an e-mail.
sorry to answer your post ill need an email address
Ok but this is the last time!
No, dots are NOT necessary. Actually you do not even need to supply a domain or a top level domain because mails then default to the default system which is usually localhost.
But even for routed mail there doesn't need to be a dot.
There is still valid Bang-Adressing for UUCP routed emails:
!bigsite!foovax!barbox!me
This is a valid email which basically means "send my email to bigsite, from there to foovax, then to barbox, to the user me."
And if you are in a playful mood - mix FQDN and BANG addressing...
A couple of years ago I made Hotmail crash by sending a mail to googlemail.de!hotmail.com!googlemail.com!hotmail.de!googlemail.ca!hotmail.ca!googlemail.fr!hotmail.fr!... [repeated it for 32kByte] ...!myuseraccount - their server literally crashed completely all over the world for like 15 minutes. I am so proud of myself but then it was their fault for not complying to RfC822.
I'm assuming by "dot" you meant @
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.
Burritos are easy to meal prep. Make your own shit and stop paying these clowns.
Could we please stop with this nonsense that "hey just make your own blahblah".
Yeah, when I have literally 10 minutes between meetings to stuff something into my mouth, I'll sure start to prep my meal. And on weekends? Fuck that too, I just want to lay on my couch doing nothing. But certainly not my meal.
It's obvious that these people don't work full time with a family
Get the bot to tell you it's connecting you to someone like you did, then give it a fake email address to get past that point.
Honestly I mostly just posted this to be funny but this is good advice
In this case, the fake email address could be sacbuntchris(at)lemmy.world to be used with that idiot bot.
Then I might get the added benefit that someone from Chipotle's web dev team finds us dunking on them.
I signed up to an insurance company here in Japan with first.last+something@domain.com and they later changed their rules and I couldn't sign in at all. They told me to open a new account. I didn't want to pay them once let alone twice. Never doing business with them again.
Yeah I tried to use + in some signups recently but it just gets cut
Same. Nowadays I just use a catch-all email address. Companyname@domain.tld. Allows me to name, shame, and block the company that leaks my email address.
And that's why I want to talk to a person.
No one wants to pay a person. And your business is worth losing. Because their bot fixes 90 percent of their problems. Not justifying. Just mocking their shitty approach.
Pepper, can you transfer me to Tortilla?
This is so dumb but so funny
And if tortilla can’t help then I want to talk to GUACAMOLE!
Alot of email verifications, very recently, are now having trouble with verifications in the domain name especially if it has a second period like yours.
Nah, this has been going on for years.
I literally can not make an account in their app. No idea why. It’s trash just keeps saying something went wrong
Are you rooted and/or ad blocking at the system and/or network level? It's probably that.
Whenever I have the random "Something went wrong" in an app that doesn't resolve in a day or 2 it's almost always because it has root detection or it's using an API call on a URL that gets filtered somewhere along the line in my adblocking system.
BK app is all fucked whenever I try to redeem coupons unless I disable AdAway
Chipotle being a shit company? I'm shocked!
I have enough 7-11 points to buy out several franchise locations, but I can't use them.
I made the account with Facebook, then later deleted Facebook. Since I don't have a Facebook to log in to the app to redeem points, I can't redeem them at all.
I contacted corporate about this, and they say there's nothing I can do.
The fun part is that my still valid email was connected to the now defunct Facebook, so I can't use my email either. Not even to make a new account.
Same deal with my phone number.
So if I ever want a free shitty taquito, I basically need an entirely new Identity.
A lot of oauth2 implementations don't really seem to have a mechanism to change providers or switch to email alone. It's going to be fun when one of the big providers like Facebook or Google decide they don't want to do oauth2 any more and a bunch of their users are suddenly locked out of millions of third party websites.
Wow. Chipotle are honestly kind of awesome for helping you out like this. It sucks that more companies won't protect their customers from themselves like this.
And this is one of the many reasons that these days I create a @duck.com email address for each website.
My password manager (Bitwarden) happily generates for me both the mail and the password… now instead of having to look up for the unique password for each website I need to look for both the unique password and unique email 🤷
Furthermore if they are incompetent enough to make shitty regexp they are for sure incompetent to keep their db safe from hacking/leaking… and I am fine with a duck.com address being locked, less so with my actual email address
I personally use simplelogin aliasing service for that and just save the mail in my password manager keepass.
Incompetent verification is definitely a problem, like they applied the most simplistic concept of 'what's a valid email address'. I had a problem like this with a website that needed an address, trying to sign up for a phone at my new house. My address went like '123123 State Road 533' The name of the road was State Road 533, that is, as in Highway 533. However, the address interpreter read it as a road called State Rd and ignored the 533, and told me the address wasn't found.
Its quite common on email domains.
I have a .email gTLD and I am frequently told its not a valid domain. Its getting better but apparently many forms only consider .com, .org, .edu etc valid.
Chipotle account? how does buying fast food involve an account? And for six years? for what?
It's a restaurant where they have a loyalty program and give you a good amount of free stuff.
restaurant
Lol
I used to have an email address “myfirstname@i.am”. I thought it was really cool… until I kept having issues logging into sites that didn’t understand how email worked. I now use “companyimgivingmyemailto@myname.com”, and I just confuse humans who think I work at their company, and that I don’t understand how email works…
I do that too, but had to add another variable. I use a priority-level or yearly rotating trigger word to pick out messages from spam. Keeps more of the riffraff out and easy to ban old temp addresses.
[Trigger].[Company name] @ domain.com
Chipotle needs to watch this video:
I tried to start that video, but I got "Failed with error code 1003, see logs for more info". (I don't think I have have access to any logs, so I guess that part isn't for me.) Maybe Chipotle wasn't able to watch it either, and so that's why their system is broken.
Just put the I'd into YT.
Chipotle’s customer service sucks ass even after you get a person. Good food though.
why would u eat at chipotle in the first place
Don't use edu emails on anything you don't want to loose access too
Same thing here with my Taco Bell app. Can't use it because my email became not a valid email address.
Stand with me against this injustice. I'll be the Baja to your Blast
Dave's not here.
Far out, man.
When you insist on implementing your own email address validation...
I have my own domain that uses a specific 2-letter ccTLD - it's a short domain variation of my surname (think "goo.gl" for Google). I've been using it for years, for my email.
Over those years, I have discovered an astonishing number of fuckheaded organisations whose systems insist I should have an email address with a "traditional" TLD at the end.
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
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.
I hate it.
The only useful email validation is "can I get an MX from that" and "does it understand what I'm saying in that SMTP". Anything else is someone that have too much free time.
It's easier to Google "email regex [language]" and copy the first result from stack overflow.
I've encountered this because my domain has a hyphen in it. Very irritating.
@spider-man.net?
I'm not aware of any correct email validations. I'm still looking for something accepting a space in the localpart.
Also a surprising number of sites mess with the casing of the localpart. Don't do that - many mailservers do accept arbitrary case, but not all. MyName@example.com and myname@example.com are two different mail addresses, which may point to the same mailbox if you are lucky.
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.
https://www.netmeister.org/blog/email.html