Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!decwrl!sdd.hp.com!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!ux1.cso.uiuc.edu!maverick.ksu.ksu.edu!deimos.cis.ksu.edu!mccall!tp From: tp@mccall.com Newsgroups: comp.mail.uucp Subject: Re: Imminent death of UUCP Zone predicted Message-ID: <3194.26aad7aa@mccall.com> Date: 23 Jul 90 10:55:38 GMT References: <100@raysnec.UUCP> <269B82AE.415E@intercon.com> <707@logicon.com> <1990Jul16.200955.29906@chinet.chi.il.us> <712@logicon.com> <721@logicon.com> Organization: The McCall Pattern Co., Manhattan, KS, USA Lines: 26 In article <721@logicon.com>, Makey@Logicon.COM (Jeff Makey) writes: > where "bozo-site" is the UUCP name of such a site. I am not one of > these sites, but when I ship such mail out via UUCP with > > From: snoopy!fully.qualified.domain!user > > I can sleep well knowing that I am immune from such lunacy. While I > currently do this for all UUCP traffic, I am beginning to be convinced > that I should only do this if bozo-site is the next UUCP hop. Not immune, but well protected. I think you should certainly not do this for people running smart mailers. You must for people with half-wit mailers (cf. AT&T). You don't need to (and therefore shouldn't) for dumb mailers, since they ignore the headers anyway. Your definition of a bozo-site in this context is a site that knows about From: lines just well enough to destroy them, but doesn't understand RFC822. It is ridiculous that vendors are shipping such systems. I don't think we should break the whole net on their account. I'd just do the rewrites you are doing for those sites only, and not for sites that are either smart enough to cope with RFC822 or dumb enough to leave the headers alone. -- Terry Poot The McCall Pattern Company (uucp: ...!rutgers!ksuvax1!mccall!tp) 615 McCall Road (800)255-2762, in KS (913)776-4041 Manhattan, KS 66502, USA