Xref: utzoo comp.mail.sendmail:2800 comp.mail.headers:644 comp.mail.misc:4983 comp.mail.uucp:5989 Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!ncar!gatech!wrdis01!mips!twg.com!david From: david@twg.com (David S. Herron) Newsgroups: comp.mail.sendmail,comp.mail.headers,comp.mail.misc,comp.mail.uucp Subject: Re: Use of Errors-To: Message-ID: <8711@gollum.twg.com> Date: 5 Mar 91 19:49:50 GMT References: <88419@sgi.sgi.com> <1991Mar2.212126.3567@cs.utk.edu> Followup-To: comp.mail.sendmail Organization: The Wollongong Group, Palo Alto, CA Lines: 32 In article mib@wookumz.ai.mit.edu (Michael I Bushnell) writes: >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 Aack! Aack! No! No! Like the gent said.. errors are supposed to be returned to the ****envelope**** From: address. If you're doing SMTP then that's the address in MAIL FROM:<>. If that address is empty then the error should be dropped on the floor. The RFC doesn't, as I recall, specify where to send errors if the envelope return address has been lost. However that usually only happens when the message is delivered and not a moment before... David -- <- David Herron, an MMDF & WIN/MHS guy, <- Formerly: David Herron -- NonResident E-Mail Hack <- <- "MS-DOS? Where we're going we don't need MS-DOS." --Back To The Future