Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!pdn!tscs!tct!chip From: chip@tct.uucp (Chip Salzenberg) Newsgroups: comp.mail.misc Subject: Re: Which headers may Sendmail re-write? Message-ID: <27710D99.140E@tct.uucp> Date: 20 Dec 90 19:14:33 GMT References: <1990Dec14.174541.14252@Think.COM> <276D13B4.6732@tct.uucp> <1990Dec18.182210.12980@Think.COM> Organization: Teltronics/TCT, Sarasota, FL Lines: 21 According to barmar@think.com (Barry Margolin): >UUCP is the name of a protocol *suite* (the transport layer protocols have >names like "UUCP g-protocol"). Yes, RFC822-compliant messages are included >in that suite, but there's no requirement that hosts using the UUCP mail >transfer protocol recognize such addresses. As I noted at length in another message, the "dumb UUCP" sites about which everyone seems so worried won't even notice that the RFC822 headers exist, because dumb UUCP sites *only* care about the envelope. It is a known and acknowledged fact that dumb UUCP sites require bang paths in the envelope. Rewriting the envelope is therefore required. No problem. So what does that have to do with RFC822 headers? Nothing, that's what. Munging addresses in *headers* just because dumb UUCP sites need bang paths in the *envelope* is misdirected at best. -- Chip Salzenberg at Teltronics/TCT , "Please don't send me any more of yer scandalous email, Mr. Salzenberg..." -- Bruce Becker