Earlier quoted context omitted.
Not sure why this is downvoted. I can imagine non-nefarious reasons to collect these lists.
Why do people downvote stuff that simply triggers them? This is useful info
Tell HN: After 10 years of experiments, custom username emails receive no spam
351–359 of 359 posts
Re: Tell HN: After 10 years of experiments, custom username emails receive no spam
#352Earlier quoted context omitted.
I agree, but the dot should be escaped because it matches any character, so "@domain\.com$" should just works for.
Or use [.] so it's super clear on the a-human-is-reading-it parse.
Re: Tell HN: After 10 years of experiments, custom username emails receive no spam
#353Earlier quoted context omitted.
Yes. I've written code that does this for parsing leaked email lists before as part of a normalizing step.
I imagine the challenge is knowing what parsing rules apply to which domains. Gmail supports the + thing, but that's non-standard. Is that something you tried to handle in a general way?
Re: Tell HN: After 10 years of experiments, custom username emails receive no spam
#354Earlier quoted context omitted.
Frameworks usually have some sort of email parser. Email parsing is non trivial. But I agree matching .*?@domain.com$ would probably work fine.
Definitely use a real email address parser if it’s available, easy and/or you’re dealing with unknown email addresses. But absent any strange circumstances there’s also nothing wrong with basic string manipulation if it’s done properly (e.g. split on @ and test for an exact string match, case insensitive). As personal preference, I’d choose that over regexp.
Re: Tell HN: After 10 years of experiments, custom username emails receive no spam
#355Earlier quoted context omitted.
Definitely use a real email address parser if it’s available, easy and/or you’re dealing with unknown email addresses. But absent any strange circumstances there’s also nothing wrong with basic string manipulation if it’s done properly (e.g. split on @ and test for an exact string match, case insensitive). As personal preference, I’d choose that over regexp.
Hackers deliberately create strange circumstances, it's the primary way to find exploits. Any code that relies on a lack of strange circumstances is a time-bomb.
1. Split on @
2. Get last string from array
3. Convert to lowercase
4. Perform exact string compare against target domain
It's possible that there's some window for obscure unicode hijinks, but I'd posit that a regexp parser or a "proper" email parsing library is just as at-risk. Possibly more so as those would be significantly more complicated and involve significantly more code.Re: Tell HN: After 10 years of experiments, custom username emails receive no spam
#356I've had obvious aliases at a number of compromised databases and so far none of those generate any spam. In fact, recently I received an email from some white hat that my address was part of a site that has been hacked twice and the site-owners have not reported it, so the white hat was sending out email blasts to tell people. I've never been spammed to that address.
Where I've seen one alias spread when it somehow ended up on some political list. A non-political blogger's newsletter address has spread from here to kingdom come and I suspect that the blogger had someone else managing the sending of that newsletter who decided to borrow the list, and the people he gave it to decided to do some more sharing.
[1] https://krebsonsecurity.com/2022/08/the-security-pros-and-co...
Re: Tell HN: After 10 years of experiments, custom username emails receive no spam
#357Earlier quoted context omitted.
Slightly easier* than running a domain, i've had luck with myemail+CompanyX@gmail.com when signing up to CompanyX. Gmail handles the '+' transparently (in the same way as it ignores '.') and delivers the email to myemail@gmail.com. It is fun to receive a survey about "an anonymous company you have used in the past"... sent to myemail+uber@gmail.com. *yet less reliable, '+' in email addresses isn't always accepted, an…
How did they expect you to respond to a survey about an anonymous company?
Re: Tell HN: After 10 years of experiments, custom username emails receive no spam
#358Is the fear of "people selling your email to spammers" a modern myth, or are spam filters that good? Email databases for sale are not always for spam or malware. They are often used for tracking and cross marketing calculations. Placing a companies name in the address will signal a canary and they may likely filter your contact out of their database or at least flag it and treat it differently. I've been using email…
I was offered a few employee discounts by front line associate because of using an email address with a company name. I declined but found it awkward to explain the details.
Re: Tell HN: After 10 years of experiments, custom username emails receive no spam
#359Buying a house. Lender immediately sold my email and phone number and I’ve been getting about a dozen aggressive sales messages a day. But hey, maybe it’s just a few bad apples.
Phone, physical mail, e-mail too. Buying a house probably netted me more spam than anything I've ever signed up for online.