Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!mips!daver!tscs!tct!chip From: chip@tct.uucp (Chip Salzenberg) Newsgroups: comp.mail.misc Subject: Re: Which headers may Sendmail re-write? Message-ID: <27763922.496B@tct.uucp> Date: 24 Dec 90 17:21:38 GMT References: <1990Dec18.155353.5024@mp.cs.niu.edu> <1990Dec19.154652.11573@sceard.Sceard.COM> <25215@ucsd.Edu> Organization: Teltronics/TCT, Sarasota, FL Lines: 28 Brian Kantor describes UCSD's setup. Two items deserve comment: According to brian@ucsd.Edu (Brian Kantor): >Our rmail has been taught to believe that any bangist address in a From: >line arriving via uucp is likely to be wrong, so it substitutes the From_ >path in place of it. It also does that if there is no domain, the >domain is "uucp", or there is no From: line. This policy is justifiable, in my opinion, for the same reason that the behavior of mailx is not. The From: header is an RFC822 invention, and if you generate one, it should conform to RFC822. >If the mail arriving via uucp contains a From: line like host@dom.ain, >rmail does not alter it at all before passing it to sendmail, and when it >leaves via uucp, we choose the greatest common denominator and issue it >as ucsd!dom.ain!host in the outgoing From: line, and as >"From dom.ain!host date remote from ucsd" in the uucp From line. This policy, however, is totally unjustifiable. As RFC822 gains even wider acceptance among the non-Internet community, more and more UUCP-only sites will be registered with the DNS. Why, oh why, must a site registered with the DNS and complying with RFC822 in every way suffer the slings and arrows of outrageous header rewriting, just because they happen to use UUCP as their mail transport? -- Chip Salzenberg at Teltronics/TCT , "Please don't send me any more of yer scandalous email, Mr. Salzenberg..." -- Bruce Becker