13 ms·
Totally disagree with the conclusion. This is Netflix's issue for not validating the email account. Not sure if Uber has changed this since then, but back in th
by hn_throwaway_99 9y ago
Totally disagree with the conclusion. This is Netflix's issue for not validating the email account. Not sure if Uber has changed this since then, but back in the day I used to get the full ride details and receipts from someone else who mistyped their email.
If you are sending private transactional emails you need to verify accounts first.
- ctz 9y agoPayPal and eBay also don't validate email, not even before attaching a bank account or making a purchase.
- sabujp 9y agoi found out that ebay.in does not, iirc they do for US accounts or am i wrong?
- jamesfisher 9y agoI think these are orthogonal issues. The dots do matter, but Netflix should also validate email addresses. However, I don't think it's as critical. Lack of email validation means I receive someone else's ride details (I agree, annoying), but dots-don't-matter means I might accidentally pay for that person's rides.
- lrdd 9y agoBut if just the email validation problem were addressed - you wouldn't accidentally pay for someone's rides. Their account would never be created as they don't have access to the email they provided. Just dealing with email validation solves both problems.
- ESRogs 9y agoIf Google fixed dots-don't-matter, couldn't someone still sign up for Netflix with jameshfisher+netflix@gmail.com? If Netflix checks for + address duplicates, then that's not an issue. But you could still have the situation where someone signs up for, let's say, Hulu with your standard jameshfisher@gmail.com account. And then you could still end up paying if you forget whether you ever signed up for Hulu or not (maybe you were about to sign up and didn't, maybe you planned to in the future). Email validation seems like the most important defense against this kind of thing. Dots mattering seems secondary.
- Pxtl 9y agoA similar problem exists for weird services like Amazon that allow multiple accounts for the same email address (unless they finally fixed that stupid idea?).
- mcpherrinm 9y agoMultiple accounts with the same email haven't been available for many, many years. I'm not sure exactly when registration for these was disabled, but it was 10+ years ago. Possibly 15-20 years ago. I think it was a valid design decision at the time, before accounts on websites were widespread and a family might only have a single email address from their ISP. The rise of free webmail accounts from Hotmail etc changed that, of course. And now we have a shared understanding of how accounts on websites should work. Neither of those were true in 1994.
- Pxtl 9y agoGood to know. I had accidentally created multiple accounts for myself around '05 or so and was really surprised by it. Iirc back then they also required separate accounts per-country, but I could be wrong about that.
- stordoff 9y agoThey still do AFAICT (I had to sign up for a Japanese account relatively recently).
- AnssiH 9y agoAmazon Japan and Amazon China are the only ones that have separate accounts from the rest of the Amazon sites.
- uiri 9y agoI don't think they require separate accounts per-country, but my only experience is with .com and .ca. They might do the accounts on a per-realm basis (North America, Far East, Europe, etc.) rather than strictly per-country.
- bo1024 9y agoThey're both issues, I agree there, but I think Netflix's screwup is larger here. Lack of validation means that Netflix is emailing someone asking them to pay for something, who may be totally different than the person getting that thing.
- codetrotter 9y agoThinking about this a bit more, I believe that there is another problem with how account creation is done. In general we do it in two steps: 1. User detail and password 2. E-mail confirmation Instead, if we did 1. User details but NOT password 2. E-mail confirmation and subsequently entering the password on the page that was sent via e-mail. Actually, I think the most optimal would be 1. Enter e-mail address only 2. E-mail confirmation and entering all details This would simultaneously protect the person that initated account creation and the owner of the e-mail address from one-another.
- batuhanw 9y agoSecond solution seems pretty optimal for security but not sure if users up for that.
- DougWebb 9y agoTypically when I implement user self-registration for my portal-website clients, I use a variation of your third option: 1. Enter email address and some out-of-band information that only an existing-account-holder should know. Eg: a web portal for a utility company could ask for the account number and amount due from a recent bill. 2. Send confirmation email with a code/link. 3. After user enters a valid code, continue registration by gathering additional user details, password, and (usually) recovery Q&A. The user account is not created until step 3; if they provide a fake email, it's as if the registration attempt never occurred. Absolutely no access is granted until after the final step. The extra details in step #1 only works for website registration of a user that has a pre-existing relationship with the company, of course. For a new account, email address is all you should request at that point.
- stephen_g 9y agoI wish requiring validation was still the norm. I get that services and sites want to reduce “friction” and get people using it right away, but anybody like me with fairly generic gmail address knows, many people don’t know their own email address. I must have hundreds of active accounts linked to that email that I didn’t sign up for (although I’m sure a lot of them can’t be logged into anymore and the people can’t recover their passwords). That account became unusable, I got my own domain account a decade or so ago to replace it but still look in there occasionally. Please though, anybody implementing signups - if you are going to let people sign up without validating email addresses, put a “I didn’t sign up for this account” link in every email you send.
- nabla9 9y agoDot's don't matter if the relevant RFC says they don't matter and I think this is the case. Google follows the standard, Netflix does not.
- B1FF_PSUVM 9y agoThe other way around. It's Google who decided to do it that way.
- cestith 9y agoWhich the RFCs for email do allow. The local part is the local part, under local control, and should not be assumed about by remote systems.
- B1FF_PSUVM 9y agoRegular people, upon looking at an email address, might think that - alert@example.com - A.Lert@example.com - Al.Ert@example.com etc. were different. Requiring them to know or check what's the "local control" policy at each site may be a stretch. Principle of least surprise, etc.
- nybble41 9y agoThese are all different e-mail addresses; that part should not be surprising, and Netflix is absolutely doing the right thing by considering them different. (The same goes for "+labels": a "+" is a perfectly valid character in the local part of an e-mail address and the meaning of the "+" is entirely up to the mail host, so e.g. rejecting e-mails with a "+" or stripping out the "+" and following characters would violate the RFCs.) No, Netflix's errors lie in (a) sending e-mail for any purpose other than account validation to an unvalidated e-mail address, and (b) including a pre-authenticated link in the e-mail that bypasses the normal account access controls. Pre-authenticated links are poor security practice in general; e-mail is notoriously insecure, and simply being able to read an e-mail sent to the address on file does not imply that the reader should have access to the account. As for "dots don't matter", it can be argued that Google made some scams a bit easier by routing e-mails to non-canonical e-mail addresses to users who don't realize they even have such addresses; my own recommendation would have been to block registration of e-mails differing only in the number or placement of dots, but bounce any incoming mail where the "To:" field doesn't match the canonical form chosen at account creation time. However, since doing away with the "dots don't matter" policy would not significantly impact the more general issue of e-mail address aliasing, I do not believe that Google's policies are to blame for this particular security gap.
- emn13 9y agodots-don't-matter isn't sufficient to fix this issue - any other canonicalization issues would surfacea as the same problem. That might include casing, unicode issues, the `+irrelevantsuffix` stuff, and probably more, including perhaps any kind of aliases in the hostname. The idea that you can tell whether two accounts are the same is questionable; netflix should not be relying on it. Furthermore, the hack is possibly much less serious (but nonetheless conceivable) even without any canonicalization issues whatsoever. Apparently, a user can trick netflix into sending email to arbitrary email addresses. Sure, this is likely not to be an issue if the recipient doesn't have netflix in the first place - but if you try 1000 times (which spammers and phishers are wont to do) - you may well happen to hit a person that'll pay nonetheless - perhaps they forgot which email they used for netflix in the first place, or perhaps they share an email account, or perhaps the real owner is dead/on vacation/otherwise unavailable and somebody else is tending the account and thus more gullible than usual. Netflix should never ask for money from random strangers without making 100% clear what the context of that request is. (If indeed this article is accurate, because I wouldn't rule out the chance that the author made some oversight earlier).
- tehlike 9y agoI assume lots of emails get validated like this by people who doesn't know what they are doing. Sad, really...
- AndrewSnow 9y agoAbsolutely. I don’t blame people who don’t interact with email for not reading the relevant RFCs, but not verifying control and expecting local part uniqueness to mean uniqueness of users is obviously busted to anyone who has worked with email. This is Netflix failing to understand part of their product surface. Both the dot behavior and the even more common ‘+’ feature are perfectly spec compliant.
- uiri 9y agoIt really bothers me the number of web services which reject email addresses containing '+' in the local part. If you're going to try to "validate" an email address, read the goddamn RFCs.
- siimtalvik 9y agoOne of the two reasons i changed my recipient_delimiter parameter to '.' The other would be that spammers know that anything after a + is usually optional and strip it. Can't do that when the delimiter is a '.'
- wyclif 9y agoI do the same thing, for the same reason. I haven't A/B tested both options or anything, but I know I've gotten spam where they stripped the "+" parameter.
- __david__ 9y agoI also did that, but I made '_' work, too. Part of me wants to add 'x' as an alternative just for further obfuscation.
- hawktheslayer 9y agoI like the idea of adding +spam@gmail.com, but it would be really easy for this to be invalidated by just stripping this from your email before selling it in a mailing list.
- 9y ago
- mholt 9y agoWhat great timing -- I've been fighting Uber on this very issue as of last night: https://twitter.com/mholt6/status/982414407941611520 https://twitter.com/mholt6/status/982414407941611520
- slartibardfast0 9y agocompletely agree, I've a rather common name with a corresponding gmail, it's absolutely shocking how little validation major Airlines do around emails!
- chatmasta 9y agoYep. Bug is the ability for users to charge a credit card before verifying email. Or did the victim in this blogpost also verify their email at some point? Netflix could be forgiven for thinking that updating payment details via email = verifying email. But if the victim had to respond to two emails, the first of which is a “verify email for your new account,” the phishing would be less believable. Ultimately, the viability of a phishing scheme depends on the plausibility of receiving an email from a source. In this case, Netflix does send emails about updating your card details when a subscription charge fails, so plausibility of receiving the email from Netflix is high. Another symptom that this is a bug with Netflix is that they granted the ability for one user to trigger a crafted email to another user.
- zaidf 9y agoThe standard email verification patterns rely on the user clicking a link. I am not sure how that would have helped here. Making users retype the email (instead of merely click on a link) might be better for exposing scams but requires more work on the user’s part.
- chatmasta 9y agoUltimately the bug relies on how believable the emails from Netflix are. If I got an email from Netflix asking me to update card details, I wouldn’t be surprised because maybe my card expired. But if I got an email asking to verify my new account, I would be very surprised. I didn’t sign up for a new Netflix account. If after that, I got an email to update my card details, I would be alarmed because of the recent unexpected signup email.
- zuminator 9y agoYes, I've received emails of the form, "You recently signed up on our website for Fooflix, please confirm by clicking here. If you did not recently sign up, please disregard this email. Anyway, now that this is a known problem, both Netflix and Gmail should take reasonable steps to mitigate.
- 9y ago
- csydas 9y agoWhy can't it be both sides' issue? I have a fairly uncommon first and last name, but I still get emails from the few folk who share my name combination, and I too have gotten sensitive information that I shouldn't have. I cannot imagine the strangeness that must occur for folks with more common name combinations, and the idea that e.mail@gmail.com is the same as email@gmail.com just seems wrong to me. As far as I know, all other email services and providers treat such accounts as unique, and it's a strange situation with very limited benefit to the end user. While I have made use of "the dots don't matter", it's always been as a way of circumventing account restrictions. The casual convenience of "dots not mattering" seems like it's overshadowed by the difficulty this can cause (as evidenced with the article and my own experience)
- djur 9y agoPermitting separate "sarah.jones" and "sarahjones" accounts would be pretty bad, too. Too easy to impersonate people. "Dots matter but are not included in uniqueness checks" is probably the safest approach.
- shkkmo 9y agoWhile you CAN strip periods in the local part of the email and convert them to lower case before checking uniqueness, you do this as the risk of improperly disallowing valid and distinct addresses. A better solution is to check for similar address and provide a prompt "do you already have an account with this address:" rather than completely blocking registration with that address. However, you should definitely not do these things to the address that you save for the purposes of sending email because then you risk improperly sending emails to the wrong person. In general, validating the format of an email address is both extremely hard and pointless (since only a small portion of mis-entries will results in an invalid email address). Pretty much the only way to validate an email address effectively is to verify it by sending an email to it and expecting the user to click an email.
- djur 9y agoTo be clear, I'm talking about what email providers could do to reduce the risk of confusion, not what email senders should do to validate emails. I agree that the only way to validate an email address is to send a confirmation.
- axoltl 9y agoIf you have a bug in a system, do you fix it at the source, or do you fix it at all the leaves? Netflix might be wrong here, but fixing it at Netflix doesn't make the problem go away. Fix the problem once (GMail) and never ever have to deal with it again.
- chatmasta 9y agoBut you can’t put the cat back in the bag. People have used the system to sign up for multiple emails at multiple sites, expecting them to go to the same inbox. I suppose you could solve the problem by grandfathering all existing aliases and whitelisting delivery of only those that received at least one email before the policy change. And also continuing to forbid registration of any aliases.
- jwilk 9y agoI'm (naively?) hoping that Google doesn't know which aliases received at least one email.
- chatmasta 9y agoOf course they know. They delivered the emails to the aliases, which are permanently in the To: field of the metadata. As long as you can see the email “to” address in the gmail web interface, so can Google.
- yemkay 9y agoThe verification email too is a phishing attempt, as it gets delivered to wrong person. All it takes is just a click.
- nybble41 9y agoThe verification e-mail is going to say something like "Please verify this e-mail address for your new Netflix account", which is going to look very suspicious to anyone who didn't just sign up for an account. As phishing attempts go, this is not likely to be very effective. It's not nearly as bad as skipping right to the part where they ask for updated payment information (with a pre-authenticated link!)—someone who has a Netflix account, and perhaps a credit card which recently expired, has no reason to suspect such a request, and most likely would not notice that the e-mail address the notice was sent to does not match the one they used when setting up their own account.
- tech2 9y agoI had a similar issue with Sony/PSN recently. Someone had registered their account and even though I received a validation email I didn't click the link. I then got a welcome-to email a few days later. PSN's emails don't have a "This is the wrong email" link like some services do, and the US support page link geo redirects to a UK 404 page. I had to go googling for an email address to complain to in order to remedy this.
- dfee 9y agoI see a lot of claims that email addresses should be verified prior to a transactional email being delivered - that that’s the “norm” or stupidly obvious way. But when there is a real consequence on a conversion funnel for requiring email address verification (say ecommerce), I imagine the obvious business decision is to do the exact opposite.
- typicalbender 9y agoIt's about risk management. In this case they decided to take on the risk of account information leaking by not verifying the address instead of the risk to account conversions. The former shows more care toward their users and the latter shows more care to their bottom line. You can argue which is the right decision all day long but ultimately is a question of risk tolerance.
- mulmen 9y agoWhat's the point of a conversion funnel that creates exactly one conversion and then a huge amount of customer grief when they can never use the account again? If the email address matters then validate it, if it doesn't need to be validated then don't ask for it.
- dfee 9y agoI don’t understand what you mean by a “CF that creates exactly one conversion”. Anyways, your response isn’t relevant in that I’m not suggesting an email address should (not) be verified. Rather, we’re discussing whether verifying identity needs to come before or after (or alongside) the transactional email - e.g. a receipt of purchase. At the same time, validation and verification are not the same thing - and sometimes it’s not necessary to perform address/identity verification.
- berkut 9y agoThis has happened to me with quite a few websites (netflix, nytimes, dropbox, and many smaller more localised websites for small businesses / services): people somehow seem to have registered and/or added payment details with an email address they don't own.
- rdsubhas 9y agoWhat you say can be applicable for subscription billing. But there are hundreds of other sites and apps where you can "checkout" stuff without needing to register, which is also a welcome/better feature. And yes, they do notify when a transaction failed. You cannot ask a whole ecosystem to change because of a feature/flaw on a central vendor. Where will you start? Force people to create accounts and verify emails when buying a one-off train ticket or ordering a pizza? What if people/market don't want this registration/activation crap for doing small utility stuff? For a payment, I have to authenticate with my payment provider, not to my email vendor. And payment providers do have delayed reconciliation issues that are sometimes notified back. And where would you stop? Validate each and every piece of info the user provides? Send a SMS verification code to the phone for same utility bill? The conclusion is correct: Fix the vendor. I asked for a specific email address when I signed up. Similarly I should get emails only for "dots" that I have specifically opted in to. Deny receiving the email, show me a warning, don't allow it until I opt in. Anything else is just asking for trouble.
- Sir_Substance 9y ago>This is Netflix's issue for not validating the email account. Eeeh, I just re-read RFC 2822. It explicitly states that the local-part of an address may contain any number of dots as long as they are separated by (if I'm reading this correctly) at least one character, and do not start with a dot. There's nothing in there that states you should treat dotted and undotted variants of an address as the same address. So, google isn't violating the specification, but they are extending it in an unexpected way. Google could extend it further by implementing a "giraffes don't matter" policy where any instances of the word "giraffe" are recursively snipped out, so that "test@example.com" is the same as "tegirgiraffeaffest@example.com", but if they did it would be a bit rich for them to expect the rest of the world to adapt code to that decision. It might be reasonable for google to expect others to handle this "dots dont matter" policy if it was some kind of defacto standard, but AFAIK it's not. I would argue that this form of attack is uniquely enabled by the gmail devs making a decision to add additional behavior to an otherwise well-understood spec, and that it's not netflixes problem to solve that. To be frank, netflix can't solve it. Asking netflix to change their code will only solve it for netflix, gmail users will still be "at risk" from, you know, potentially literally every other domain on the internet. So I would say that this is a risk that gmail users need to be aware of and mitigate themselves, perhaps by taking such drastic steps as reading their bills before paying them.
- LoSboccacc 9y agoThe spec say that the server can alias valid addresses as much as they like and the sender should not assume any form of aliasing. Netflix second guessing the aliasing pattern is the bug
- fjsolwmv 9y agoThere is no bug in Gmail. The bug is that the vendor is sending unclear email contents.
- notatoad 9y agoI agree, the responsiblity for this flaw ultimately lies with netflix. And if laying blame is a helpful thing to do, the blame lies with netflix. But at the same time, in a purely practical sense the mockup at the end of the article showing an explicit warning about email being sent to a non-canonical address is clearly excellent and should be implemented.
- josteink 9y ago> the responsiblity for this flaw ultimately lies with netflix Indeed. You should always validate emails for accounts. The amount of accounts I “have” and can’t cancel because of sites not doing any email-ownership validation is quite annoying. > in a purely practical sense the mockup at the end of the article showing an explicit warning about email being sent to a non-canonical address is clearly excellent and should be implemented. Gmail is doing something very nonstandard here and it’s absolutely their responsibility to inform users why they are getting emails on addresses (most?) users would never know about nor use. I’d even say that having this feature on with infinite whitelisting by default is a security issue which should be resolved. Preferably by only allowing explicitly whitelisted entries created by (the few) power users using this feature.
- vit05 9y agoI have the same problem with Netflix, Uber and other sites. They simply do not check the email. It's an absurd. And the biggest problem is that the person who mistakenly uses my email asks a hundred times to reset MY password. Gmail and these sites need to take this issue more seriously.
- what_ever 9y agoAbsolutely. Netflix is using ID created by some other service as their ID without verifying with the other service if the ID in question belongs to the user who is claiming it's theirs. There needs to be a 2nd factor to confirm whether an ID belongs to someone - password/confirmation/code/pin which Netflix doesn't use here at all.
- tbabb 9y agoNot only that, but apparently he was able to change Eve's account details without having to enter a password. If instead Netflix had prompted him before allowing him to change the credit card, it would not have worked, because he wouldn't have known Eve's password and Eve wouldn't have known his. All around very bad security design on Netflix's part.
- kbsletten 9y agoHe said in the post that he was able to reset the password because the account was linked to "his" email.
- theclaw 9y agoBut if you have to reset the password to update the credit card details, then surely the scam won't work because the scammer would no longer be able to use the account. For this scam to work the "Update your credit card" mail must contain a credential that allows you to update the scammer's card without changing or being challenged for their password. That doesn't seem great.
- giomasce 9y agoFully agree. All authentication operations should always be completely explicit and clearly display the identity you are authenticating to. An email link implicitly logging you in looks like completely unacceptable. The email to recover your password can be excepted, because it is clearly an authentication-related thing and maintain the invariant that at most one person is actually able to log in.
- rickycook 9y agoyou still have session cookies, because AFAIK netflix doesn’t log out all your devices when you reset your password (though i think there’s an option for that?) so you can still set the password and email back if you have the session cookie maybe?
- 9y ago
- brongondwana 9y agoTotally... different services provide different ways to have multiple addresseses. The article already mentions one (plus addressing), but there are also others (like FastMail's subdomain addressing)[1]. And many people have catchall or misspelling addresses on their own domain. That said, I dislike Gmail's "the dots don't matter" since it really screws up calendar invitation handling, because calendars don't handle aliases well. [1] https://www.fastmail.com/help/receive/addressing.html https://www.fastmail.com/help/receive/addressing.html
- pryce 9y agoAbsolutely - his proposed solution - disabling the dots-dont-matter feature and retiring them does nothing to stop this exact same attack vector instead employing the '+' feature that he admires and wishes to retain. The attack goes like this: * Hammer the Netflix signup form until you find a gmail.com address which is “already registered”. Let’s say you find the victim jameshfisher. * Eve creates a Netflix account with address jameshfisher+netflix * Sign up for free trial with a throwaway card number. * After Netflix applies the “active card check”, Eve cancels the card. * Wait for Netflix to bill the cancelled card. Then Netflix emails jameshfisher+netflix, going to jameshfisher's inbox, asking for a valid card. * Hope Jim reads the email to jameshfisher+netflix, assumes it’s for his Netflix account backed by jameshfisher, then (follows a link in the email and) enters his card 1234. * Eve changes the email for the Netflix account to eve@gmail.com, kicking Jim’s access to this account. * Use Netflix free forever with Jim’s card 1234! Either they're both security liabilities, and they should both be removed, or the problem lies elsewhere.
- kevin_thibedeau 9y agoMoreover some broken email validators reject plus addresses. It's nice to be able to fall back on special dot combos when you want to keep track of sites selling your email to spammers.
- jdhawk 9y agoSpammers already know the dot rules. Its fairly easy to identify a Domain Group (ymail/yahoo) or (google/gmail/somewhere.edu) and then strip and reapply certain rules based on what that Mail Provider allows.
- adarshaj 9y agoThat's true in theory. In practice however, I've had success with figuring out a service that leaked my dotted address (I used a dot because the service didn't validate email with plus). I think this is often the case too because, spammers don't really bother validating emails by postprocessing etc. and just sell the emails in bulk in shady markets
- emmelaich 9y agoYep, but it's still a misfeature. I set up a firstname.lastname account for someone. On other services (e.g. iTunes) they've used that combo with and without dots. It's a nightmare trying to help them with password resets. They're not an internet-savvy individual.
- fjsolwmv 9y agoGmail can't cure stupid.
- pishpash 9y agoThese companies are stupid and not worthy of respect. Not only Netflix, but Apple and even some banks don't (or didn't) verify email before sending private information.
- efficax 9y agoEh, but consider online shopping carts. I go to some ecommerce site, enter in my email to buy something. If I have to verify the email first, conversion rates will plummet. Instead, (and this is what we do at my company), we attempt to validate that the email is a real one with MX lookups and even SMTP checks. But otherwise, you just have to trust the shopper.
- jv22222 9y agoStill... I get so many other people's email because of this dot's don't matter feature it's very frustrating! For example I'm regularly cc'd on a list of a South African film production company. I often get invites to parties from a group of students in Georgia. And, someone seems to use a dot alternative of my name to buy sex toys! And that is just a few! I used to send back the emails saying "Hey you go the wrong person" until I realized it has no effect on these types of group emails.
- fjsolwmv 9y agoNot because dots don't matter. That's unrelated. It's because people don't know or lie about their own email address.
- orblivion 9y agoAnd if they do require a verify, they should make it obvious that it was user initiated just then. Otherwise it could be the same scam: Eve creates an account. James gets the email. "Hmm that's funny. Okay I'll verify again".
- sytelus 9y agoEmIl address is an identity. The core philosophical issue here is that an identity provider assigns you bucket of identities without your knowledge. Now others who do have knowledge of your assigned identities can take advantage to impersonate you. The idea that it can be resolved by email verification does not hold well because in several circumstances it might not be possible (for example, you need to create your account at the PoS). It’s a bug indeed if you think of email address as identity. It’s unrealistic expectation that all non-technical users should be aware about this feature as well as that all login system must use email verification. The solution is simple: email provider should let user create additional identities with their knowledge. That is by default dot feature is not enabled but user should be able to go in and create alternative identities that they want explicitly.
- zouhair 9y agoAgree, this said the "dot don't matter" is also an awful thing. I'd rather have gmail create a real alias system instead of this hack. That's the thing that is good with Yahoo.mail, it has real alias system.
- fjsolwmv 9y agoWhy is it awful?
- s0rce 9y agoI get these types of things nearly daily since everyone mistakenly assumes they have my gmail account, single first initial and common last name. Many services don't require you to confirm e-mails, this is the problem. My apple ID account was created by someone else and they set the security questions and if you "forget" all the answers you cannot reset them online! Only services I've seen that handled this properly are gmail and snapchat which send a verification e-mail to the entered address (for gmail its the secondary) and there is a link that you can click indicating your e-mail should not be associated with this account.
- devmunchies 9y agoalthough this is Netflix's fault, gmail should have an account feature to toggle "dots don't matter" on and off.
- ykumards 9y agoThat was exactly my reaction after reading the first few paragraphs. “How did Eve circumvent the email verification step?” Netflix should totally fix this, even my local public library asks for email verification after signing up.
- jpcosta 9y agoI really wish this was the norm! I have a very common name and signed up for gmail address right at the start. I now receive tons of spam because there are people who sign up to the weirdest things with my gmail handle.