News for hackers. Stuff that matters.
Re:Data allegedly stolen from 560M Ticketmaster users by cush on Friday May 31, 2024 @12:39PM (#40537245)
How else would it work? It’s incredibly convenient. The option to create a new email is presented on signup forms, or you can open Hide My Email settings and generate one. I have hundreds of emails this way
Re:Data allegedly stolen from 560M Ticketmaster users by mariusor on Friday May 31, 2024 @01:15PM (#40537750)
> How else would it work?

Like grandparent said: by having a catch-all email address on a domain. Then emails that are being sent to invalid email accounts on that domain end up in that mailbox.

Re:Data allegedly stolen from 560M Ticketmaster users by cush on Saturday June 01, 2024 @12:23AM (#40542855)
I’m not sure that idea was thought through. An infinite number of addresses that all point to the same inbox is effectively the same as having one address
Re:Data allegedly stolen from 560M Ticketmaster users by mariusor on Saturday June 01, 2024 @04:00AM (#40543777)
The point of having multiple addresses delivering to the same mailbox is to be able to use per service custom emails. The grand-grand parent wanted a ticketmaster specific email, so if they sell their data, or it gets leaked, they know from the email address it was from ticketmaster, or another service.

Another commenter in the thread presented how their company "normalizes" gmail addresses by removing "." character and "+..." suffixes, so users don't abuse their system by creating multiple accounts with what is basically the same email. Having a catch-all mailbox allows people to circumvent this "security" measure.

I'm imagining that you actually want to have separate emails pointing to separate mailboxes, and for that case indeed, your solution is better, but for the life of me I can't imagine why anyone would prefer having to check multiple emails, instead of a single one. :D

Re:Data allegedly stolen from 560M Ticketmaster users by cush on Saturday June 01, 2024 @04:40PM (#40548908)
Yeah I get it, just disagree that it circumvents anything. If emails actually worked this way then leaking the domain would be effectively the same as leaking an email is today. The + scheme doesn’t work because of the aforementioned normalization, and this domain thing wouldn’t work for the exact same reason - whoever had the leaked email could just send an email to <anything-they-want>@<yourdomain> and it’s all the same