Xref: utzoo comp.unix.xenix.sco:2670 biz.sco.general:126 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!chinacat!chip From: chip@chinacat.unicom.com (Chip Rosenthal) Newsgroups: comp.unix.xenix.sco,biz.sco.general Subject: Re: SCO TCP/IP Keywords: tcp/ip Message-ID: <1991May31.172535.23002@chinacat.unicom.com> Date: 31 May 91 17:25:35 GMT References: <22@pegasus.UUCP> <1991May30.224320.4758@tygra.Michigan.COM> Organization: Unicom Systems Development, Inc. Lines: 28 In article <1991May30.224320.4758@tygra.Michigan.COM> jp@tygra.Michigan.COM (John Palmer) writes: >I tried to get hold of SCO regarding failure of their TCP/IP to >adhere to accepted standards by providing support for UUCP connections. To which standards are you referring, pray tell? SVID? POSIX? FIPS? Maybe you are making this up as you go along, and don't really know what the fuck you are talking about. >Last Friday, a tech support guy called me and suggested using SMTP. >Sorry, but some of the sites I talk to require UUCP over TCP/IP - Then tell them to get their SMTP fixed. SMTP is a recommended part of the TCP/IP protocol suite. uucp isn't even granted elective status. >It seems to me that they'd have to make a EFFORT to EXCLUDE >UUCP support instead of INCLUDE it. I mean, if they have a UNIX >source code license, they already have the support in there. How can one boy have room for so many feet in a single mouth? >Thats why we'll be dropping our SCO Reseller Contract soon and will >be sticking with Interactive. Good. I hope that means we won't be seeing you around this group anymore. -- Chip Rosenthal | Don't play that Unicom Systems Development 512-482-8260 | loud, Mr. Collins.