Re:Have I been pwned? Check if your email has been compromis...
by baby on Wednesday December 04, 2013 @09:06PM
(#6852183)
This seems way too difficult to manage.
I wish there was a Gmail like application that anyone could set up easily on its server and that would allow for : quick email generation.
You need to sign up to something ? Generate a quick mail that redirects automatically to your main inbox and that you can give away when signing up.
If you see that spam is arriving on this email, remove it.
Re:Have I been pwned? Check if your email has been compromis...
by im3w1l on Wednesday December 04, 2013 @11:12PM
(#6852645)
[email protected]
Goes to the inbox of user baby
Re:Have I been pwned? Check if your email has been compromis...
by baby on Thursday December 05, 2013 @01:50PM
(#6856285)
I already know this trick and don't use it because :
* it's easy to get the real email address from it.
* most sign up form don't accept the "+" sign.
Re:Have I been pwned? Check if your email has been compromis...
by eli on Wednesday December 04, 2013 @05:30PM
(#6850888)
That seems like a lot of overhead to manage. Also, you're going to have a bad day if a spam bot decides to spam thousands of <common_user_name>@yourdomain.com. Maybe that's fallen out of practice, but I've seen it happen before.
Re:Have I been pwned? Check if your email has been compromis...
by Aldo_MX on Wednesday December 04, 2013 @05:56PM
(#6851096)
Not really, in this year I had changed only 1 filter, the initial setup may be cumbersome, but the end result is worth the effort.
And about the spam to random addresses, in 8 years the most extreme problem I had faced is spam to censored addresses like [email protected] (thanks google code).
Re:Have I been pwned? Check if your email has been compromis...
by spindritf on Wednesday December 04, 2013 @05:41PM
(#6850975)
It's a tried and true spamming tradition and it's going strong. I see plenty of entries like
Envelope-to: <[email protected]>
in my reject log. Addresses that were never used anywhere. Some things just refuse to die.
I follow the following pattern with websites:
If the website is important (ex. government), I use <sitename><4_numbers>@<private_domain>. My filtering rules are extremely strict, and every mail that doesn't come from the expected website gets automatically flagged as spam and deleted. If their DB leaks, I just change the 4 numbers.
If I know the website and it's not an startup, I use <sitename>@<public_domain>, ex. [email protected]. My filtering rules only flag the messages as "maybe spam" when the sender is not in my contacts. If their DB leaks, I change the filter from "maybe spam" to "spam".
If it's a website I don't know, or a startup, I use <full_domain>@<publc_domain>, ex. [email protected]. I don't filter them, but if I start getting spam, I just simply set the email as an alias to my wormhole (an account I never check that flags anything it receives as spam).
If it's a spam blog, or a website that forces me to create an account by no apparent reason, I just use the wormhole address.