Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!umich!samsung!psuvax1!psuvm!HMCVAX!NED From: NED@HMCVAX.CLAREMONT.EDU (Ned Freed, Postmaster) Newsgroups: bit.listserv.pmdf-l Subject: RE: errors-to field Message-ID: Date: 4 Feb 90 01:01:00 GMT Sender: PMDF Distribution List Reply-To: PMDF Distribution List Lines: 23 Approved: NETNEWS@PSUVM Gateway Errors-to: postmast@YMIR.BITNET X-PS-Qualifiers: /DOOF X-Envelope-to: PMDF-L@IRLEARN.BITNET X-VMS-To: IN%"DMPM@DUKEMC.BITNET" X-VMS-Cc: IPMDF X-To: DMPM@DUKEMC, INFO-PMDF@YMIR I have little to add to Terry's analysis of Errors-to: fields; he covered it very well. Errors-to: was a proposed extension to RFC822 (came out on the header-people mailing list originally, I think). It never has made it to RFC status. I think one RFC mentions it, but only in passing. The new Internet Standards RFC talks about how to encode envelope information into headers. This is not precisely the same thing, but it is close, and I think as a result Errors-to: is sort of dead as far as standardization is concerned. PMDF is capable of generating Errors-to: lines. Some mailers do respect them, so it is a good idea to make them available. PMDF does not respect Errors-to: lines. It uses envelope-from addresses instead. I've thought of changing PMDF to use Errors-to: (at least in the message bouncer) but I've never gotten around to it. It is actually sort of tricky to do, and would require an additional entry point in mm_ that accepts preparsed headers for inclusion in messages (this would be a good idea in any case, so I'll probably implement it sometime). If anyone thinks Errors-to: support in PMDF is a pressing concern, please let me know. Ned