Only mail servers should send bounce email. They know the information needed to send the bounce message. For example, the From address should not receive bounce messages; the SMTP return address should get these. For most email, the from address and the return address. But think about mailing lists where the email is resent to all the members and the return address is changed to mailing list manager.

More importantly, most of the email you are receiving for unused addresses is spam. Spammers will generate mailboxes for domains even when they haven't harvested the address. The bounce messages won't do any good because spammmers forge return and from addresses. The bounces will be going to someone innocent or invalid address. Even if they went to the spammers, the spammers will likely ignore them and not remove the bad addresses from their lists.

The only case where bounces might be useful is if you acquired an old domain, or there used to be separate mailboxes. Then people might be legitimately using old addresses. I would suggest seeing if your ISP can do mail delivery for just the addresses that you use and bounce all the others at their server.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.