Re:Bank Sends Email to Wrong Gmail User, Sues Google For His...
by mustpax on Thursday September 24, 2009 @01:15PM
(#841621)
I imaging if you owned noreply.com you'd get a hefty amount of private correspondence in as well. I bet there are plenty of services out there that use [email protected] thinking it's the email equivalent of /dev/null for some magical reason.
Re:Bank Sends Email to Wrong Gmail User, Sues Google For His...
by josefresco on Thursday September 24, 2009 @01:27PM
(#841665)
I wrote an article a while back on this topic and whether the owners of test.com, check the email account [email protected].
Didn't get a good answer but I would imagine they could see a lot of very personal information come their way as many geeks I've known use that to test their software.
Re:Bank Sends Email to Wrong Gmail User, Sues Google For His...
by jerf on Thursday September 24, 2009 @02:13PM
(#841772)
Best practice as I understand it is to use emails that have the TLD "invalid", or one of a couple of others that have been explicitly set aside as "never will be issued" by RFCs. They also have the advantage of looking very out-of-place, where @test.com may slip by.
Re:Bank Sends Email to Wrong Gmail User, Sues Google For His...
by psadauskas on Thursday September 24, 2009 @02:40PM
(#841850)
Full list, and what they should be used for, here: http://en.wikipedia.org/wiki/Top-level_domain#Reserved_domai...
For testing, I usually use test{n}@testname.test. I've so far managed to avoid no-reply. If someone tries to reply to one of our message emails, I want to know what problem they're having, and the context to go with it from what message we sent them. "noreply" emails are anti-user-friendly.
A lot of this mail is mailing lists that didn't do double opt-in and hence *@jgc.org got added to the list. But quite a lot is just personal mail.
For a while I used to receive the itineraries for the private jet of a famous entrepreneur because they were meant to be CC:ed to someone at igc.org but came to me instead.