Re:800M Email Addresses Leaked Online by Email Verification ...
by css on Thursday March 07, 2019 @07:28PM
(#19334041)
Been using a wildcard for one of my email domains for years (facebook@..., linkedin@... etc) and never once have I had issues with spam. Everything for services I dont care about goes through SpamAssassin on the mail server and items that pass get dumped to Gmail, where only "ham" messages will get forwarded through to my real inbox.
[ Parent
| on HN ]
Re:800M Email Addresses Leaked Online by Email Verification ...
by johnnyfaehell on Thursday March 07, 2019 @07:33PM
(#19334071)
I think they were using their catch-all for non-transactional/newsletter emails. I have a catch-all for websites and then another that I give to people to email me on. This lets me see emails sent to me by a person easily while having separate email addresses for each site.
Re:800M Email Addresses Leaked Online by Email Verification ...
by usrusr on Friday March 08, 2019 @05:13AM
(#19336393)
Do you have catchall directly on the second level domain (@mydomain.com) or do you only catchall a specific subdomain (@mail.mydomain.com)? I'd expect a very big difference in the volume of blue sky spam between those two. If GP sbov has the catchall directly on mydomain.com, then restricting the value space to *.r will make a meaningful difference.
Having the "validating substring" in front of the @ will actually make it easier when you have to use the email address in vocal communication: many humans are unaccustomed to encountering more than one dot after the at.