Xref: utzoo comp.mail.sendmail:2803 comp.mail.headers:645 comp.mail.misc:4992 comp.mail.uucp:6005
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!cmcl2!phri!roy
From: roy@phri.nyu.edu (Roy Smith)
Newsgroups: comp.mail.sendmail,comp.mail.headers,comp.mail.misc,comp.mail.uucp
Subject: Re: Use of Errors-To:
Message-ID: <1991Mar6.172315.1112@phri.nyu.edu>
Date: 6 Mar 91 17:23:15 GMT
References: <88419@sgi.sgi.com> <1991Mar2.212126.3567@cs.utk.edu>
Sender: news@phri.nyu.edu (News System)
Organization: Public Health Research Institute, New York City
Lines: 20

moore@cs.utk.edu writes:
> Errors-to: is not officially sanctioned by the RFCs, which dictate that
> errors should be reported to the *envelope* From: address (which is
> supposed to be copied to the Return-path: header during final delivery).

	The problem is that Errors-to: is a very useful thing to have, or
at least it's useful to have the same functionality.  If I send something
to a mailing list, I certainly don't want to see dozens of error messages
pouring back into my box about delivery errors to people I've never heard
of just because they happen to be on the mailing list.

	What is the "right way" to set up the headers on mail resent from a
mail reflector so that replies go back to the originator (and/or the whole
mailing list) but that error messages get sent to the mailing list
maintainer?
--
Roy Smith, Public Health Research Institute
455 First Avenue, New York, NY 10016
roy@alanine.phri.nyu.edu -OR- {att,cmcl2,rutgers,hombre}!phri!roy
"Arcane?  Did you say arcane?  It wouldn't be Unix if it wasn't arcane!"