News for hackers. Stuff that matters.
Re:Death to the 'noreply' mailbox by stock_toaster on Thursday August 11, 2011 @12:54AM (#2871456)
I think for things where feedback is warranted, sure. But for automated email sending, alerts, notifications, things which may have very high bounce rates, using a real mailbox is basically spamming yourself or your support team.

I tend to use 'automated@' or 'a.robot@' though, to reflect that it was sent on behave of a process.

Re:Death to the 'noreply' mailbox by nodata on Thursday August 11, 2011 @12:59AM (#2871467)
But you won't know whether feedback is warranted. You don't get to decide - the user does.

As an example, yesterday I got an e-mail where a template variable hadn't been expanded. noreply means they don't get to find out. It's worth my time replying to an e-mail. It's not worth finding a contact form and filling it out.

Re:Death to the 'noreply' mailbox by capnrefsmmat on Thursday August 11, 2011 @12:58AM (#2871462)
Your reply-to address doesn't have to be the same as the envelope-from on the message, so intentional replies can go to a different address than SMTP bounces. You don't have to spam yourself.