Xref: utzoo comp.mail.sendmail:2786 comp.mail.headers:640 comp.mail.misc:4965 comp.mail.uucp:5961
Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!lll-winken!elroy.jpl.nasa.gov!sdd.hp.com!think.com!mintaka!mintaka.lcs.mit.edu!mib
From: mib@wookumz.ai.mit.edu (Michael I Bushnell)
Newsgroups: comp.mail.sendmail,comp.mail.headers,comp.mail.misc,comp.mail.uucp
Subject: Re: Use of Errors-To:
Message-ID: <MIB.91Mar4160611@wookumz.ai.mit.edu>
Date: 5 Mar 91 00:06:11 GMT
References: <88419@sgi.sgi.com> <1991Mar2.212126.3567@cs.utk.edu>
Sender: daemon@mintaka.lcs.mit.edu (Lucifer Maleficius)
Organization: Free Software Foundation, Cambridge, MA
Lines: 13
In-Reply-To: moore@chili.cs.utk.edu's message of 2 Mar 91 21:21:26 GMT

In article <1991Mar2.212126.3567@cs.utk.edu> moore@chili.cs.utk.edu (Keith Moore) 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).  So just because sendmail recognizes the Errors-to: header
   and does something useful with it does not relieve it of its
   obligation to report errors to the envelope From: address.

Ack! No!  The errors go to the Sender:, and if that field isn't there,
to the From:.

	-mib