Slashdot Mirror
Where Do Dummy Email Addresses Go?
ajain writes "Maybe a year and a half back or so, I started using someone@somewhere.com as a dummy email id in online blogs, guestboks, forums, and sundry pages. But then I started wondering what if someone actually tried to email me on that email address. I was sure that it would bounce because I assumed that there wouldn't be an actual email address like that. In any case, just for fun, I decided to google on someone@somewhere.com. And lo behold, there are some 4090 results! I have written a small article at my blog and a reader says NoOne@NoWhere.com is another contender. Do you use some common dummy email IDs too, to get around the privacy problem online? Isn't there a potential for malicious misuse of someone's email ID in this way?"
If you go to example.com (or .org, .net) it'll tell you that it was set up as a dummy domain in some RFC for the express purpose of being used as an example: "so then you point your browser to example.com" that wouldn't be abusable. So go right ahead and use example.[com|org|net].
In the same line of thought I'm sending the SPAM at the best SPAM processing place:
abuse@microsoft.com
So that all the sites that send crap will think about it two times.
the From: header can be easily forged and these privacy.net guys are just adding to the misuse of net traffic by replying.
spam should go to one of 2 places... an authority who can fine the sender, or /dev/null (preferably the mail server will reject the spam before even collecting it, such as grey listing does)
That is so uncool. I used to work for an ISP and people like you slowed response time for real issues tremendously when we had to dig through tons of crap to find the real issues.
Two roads diverged in a wood, and I - I took the one the bus load of girls just went down.
Maybe an address at networksolutions.com or netsol.com would be more appropriate, after all they want to be the destination for traffic to nonexistent domain names with their sitefinder crap.
Is that really illegal if there is no fraud involved?
Provided that you don't use a real e-mail address, just who is harmed?
First, I didn't mean the .foo part. I meant the foo.com part. And yes, I was wrong. Shouldn't assume NetSol is right when it says a 3 letter domain is invalid. My bad.
I've used john@doe.com for the longest time
works for me :)
No encryption can withstand the power of the Lucky Guess.