Bruno Wolff III [mailto:[EMAIL PROTECTED]] wrote:
> There isn't any point in doing this for double bounces. Double bounces are
> caused when both the recipient and sender addresses are munged. No automated
> response to a double bounce is going to be useful. At our site I estimate
> 80-90% of the double bounces are from spam. The others are caused by our
> users sending out email (to bogus addresses) with bogus return addresses
> (typically typos).
>
> If you aren't going to look through the messages and try to figure out if
> one of your users has something set up wrong and let them know about it,
> it should be pretty safe to delete double bounces. Though you might want
> to look at ones that don't have any received headers indicating they came
> from outside your network, since those are not likely to be spam.
[snip]
I just didn't want to end up ignoring any message sent by a real user to the
postmaster address. Since they would have a real return path, they would get a
reply. In talking about the postmater address, RFC 822 says: "Mail sent to that
address is to be routed to a person responsible for the site's mail system or
to a person with responsibility for general site operation." I didn't want to
violate that.
But setting something up sounds like too much work for too little gain, so I'll
just /dev/null all the postmaster e-mails.
- David Harris
Principal Engineer, DRH Internet Services
