| ▲ | overlordalex 7 hours ago | ||||||||||||||||||||||||||||
The way that this is done these days (and likely what the author did/does) is that you use a custom domain to receive mail; you provide an email like service@custom.com, and that way when service@ starts receiving spam you know exactly where it comes from | |||||||||||||||||||||||||||||
| ▲ | ValentineC 7 hours ago | parent | next [-] | ||||||||||||||||||||||||||||
^ I've been doing this with catchalls since before Google Apps for Domain was even a thing. Sometimes customer support staff bring up "oh, do you work at <company> too"? I just tell them that I created an email address just for their company, in case they spam me. | |||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||
| ▲ | aaomidi 7 hours ago | parent | prev | next [-] | ||||||||||||||||||||||||||||
Take it a step further and do uuid@ | |||||||||||||||||||||||||||||
| ▲ | fragmede 7 hours ago | parent | prev [-] | ||||||||||||||||||||||||||||
yes, but service is too guessable, so append a randomly generated nonce as well, eg service_rjfh34@example.com. It doesn't need to be cryptographically random, just non trivially guessable to prove the service is leaking email addresses. | |||||||||||||||||||||||||||||