Re:Complexities of e-mail validation logic
by willcipriano on Monday May 24, 2021 @11:33AM
(#27265548)
I just have a entire domain for the purposes of spam. Anything sent to there ends up in my bulk folder. I use [email protected] so I can tell who sells my email or gets hacked. Never noticed someone trying to send a email to any addresses I haven't previously used.
[ Parent
| on HN ]
> Never noticed someone trying to send a email to any addresses I haven't previously used.
At least a few years ago, I noticed a lot of spam to <random first name>@<my domain> -- i.e., completely made-up addresses that I had never used. Since messages sent to those addresses were guaranteed to be spam, I started treating them as free training data for the spam filter.
I don't know if this still happens, though, because I haven't looked.
This is currently happening to my email domain. Gets rejected as it doesn't have a valid hash (recipient name), but the logfiles are full of <3 letters>@mydomain.com and <english_word>@mydomain.com rejections.
Yeah, this is an age-old issue -- in the early 00s, my mom got a domain and used the email <first_initial>@<domain>.com. She gave up battling the deluge of spam after about a year. We looked through the logs, and saw that her next choice of handle was also getting tons of spam, too, because it was also short.
I do the same thing. I use [email protected]. The addresses are temporary if I want them to be and I can automatically lock the senders to a list that is either automatically learned after x days or manually curated. I've seen some 'marketing' mail get filtered but no hacks yet.
I’ve got [email protected] email for my domain and I’ve never created such an account, much less given it out. Without some uniqueness in the username, I’m not sure you can tell a company sold or lost your data.