Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!think.com!spool.mu.edu!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!axion!uzi-9mm.fulcrum.bt.co.uk!igb
From: igb@fulcrum.bt.co.uk (Ian G Batten)
Newsgroups: comp.mail.uucp
Subject: Re: UUCP Protocols
Keywords: uucp, protocols
Message-ID: <SH?_BT*@uzi-9mm.fulcrum.bt.co.uk>
Date: 23 Apr 91 10:02:10 GMT
References: <1991Apr19.125453.22@cutler.uucp> <1407@ncrnorw.Norway.NCR.NO> <7322@auspex.auspex.com>
Sender: news@fulcrum.bt.co.uk (News with an UZI)
Organization: BT Fulcrum, Birmingham
Lines: 15

In article <7322@auspex.auspex.com> guy@auspex.auspex.com (Guy Harris) writes:
> "x" - some kind of UUCP-on-X.25 implementation that AT&T had; I don't
> know if they ever released it in source form, and I've heard it had lots
> of problems.

It is indeed in the V.3 source distribution.  It's useless in the UK,
and I believe other places, because it marks the end of each
transmission by sending a zero-length data segment.  This is discarded
by PSS in the UK.  Therefore it works fine until the first C-CY
exchange, at which point it hangs.

There is also the ``d'' protocol, for use over datakit, in the V.3
sources.  I've no idea what sort of protocol it is.

ian