News for hackers. Stuff that matters.
Re:Tell HN: GitHub now blocks aliased email addresses by sigstoat on Friday January 27, 2023 @02:44PM (#34550773)
in my experience that sort of "send some spam to addresses we have no reason to believe exist" behavior takes the form of sending stuff to $commonfirstname@domain not $service@domain

nobody is sending email to alsdkjfadf@domain

Re:Tell HN: GitHub now blocks aliased email addresses by ylk on Friday January 27, 2023 @02:56PM (#34550940)
> nobody is sending email to alsdkjfadf@domain

That’s actually the kind of spam I used to receive on a very short domain with a catch-all.

I guess they loop through short domain names and then try to brute-force the local part.

Re:Tell HN: GitHub now blocks aliased email addresses by mynameisvlad on Friday January 27, 2023 @03:04PM (#34551082)
Interestingly, I have <3letters>.one but I think because it's an uncommon TLD and a seemingly random 3 letters, I haven't had that issue.
Re:Tell HN: GitHub now blocks aliased email addresses by takoid on Friday January 27, 2023 @02:46PM (#34550807)
You are right. But I think using a catch all with a separate username for each service/business is becoming an increasingly common practice so I would imagine it’s only a matter of time before spammers catch on and begin exploiting this.
Re:Tell HN: GitHub now blocks aliased email addresses by scrlk on Friday January 27, 2023 @03:00PM (#34551004)
I use service name + 4 random alphanumeric characters. Seems to strike a reasonable balance between just using the service name vs. completely random characters.
Re:Tell HN: GitHub now blocks aliased email addresses by wkrsz on Friday January 27, 2023 @02:51PM (#34550865)
Then we adapt.