News for hackers. Stuff that matters.
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.