clu@malihh.hanse.de (Carsten Lutz) (04/12/91)
Hi !
Could anyone please mail me a source of the UUCP-e-Protocol ? ( And only
that please, I don't need anything about g and f stuff ! )
I would like to implement it and don't know exactly how it works yet.
I think there are 20 bytes sent for every file with the following contents:
1234\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0
^^^^ ^
| filled with chr(0)'s
Length in ascii-notation.
then the file is sent. The only errorchecking is testing the length of
the received file. If it is not Ok the connection is closed and the file
erased.
But how do the cicos know wich one is to send and wich one to receive a
file ? And is there any init-sequence ?
Greetings,
Carsten
--
+ Carsten Lutz, Rellingen, FRG / clu@malihh.hanse.de +
+ Voice : +49 4101 207871 Fax: +49 4101 27757 Traily : +49 4101 22306 +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ ...This is usually because the networks transfer the mail by emulating +
+ punched cards ! - Donnalyn Frey +csg@pyramid.pyramid.com (Carl S. Gutekunst) (04/19/91)
In article <3760704@malihh.hanse.de> clu@malihh.hanse.de (Carsten Lutz) writes: >Could anyone please mail me a source of the UUCP-e-Protocol ? The "real" source belongs to AT&T. You cannot get a copy without a System V source license. It sounds like you are pretty close to reverse engineering it, though. It's a very simple protocol. Just watch the packets on a scope; you'll figure it out very quickly. If you already have source for 'f' (which is public domain), you can follow the same model. <csg>
andys@ulysses.att.com (Andy Sherman) (04/24/91)
In article <3760704@malihh.hanse.de> clu@malihh.hanse.de (Carsten Lutz) writes: >Hi ! > >Could anyone please mail me a source of the UUCP-e-Protocol ? ( And only >that please, I don't need anything about g and f stuff ! ) > >I would like to implement it and don't know exactly how it works yet. >I think there are 20 bytes sent for every file with the following contents: I hope you mean a protocol description and not source code. Otherwise you are most likely asking somebody to violate a license agreement. I believe that 'e' protocol was an enhancement that was part of HoneyDanBer UUCP (now known as the System V Basic Networking Utilities). This is not public domain stuff. Andy Sherman/AT&T Bell Laboratories/Murray Hill, NJ AUDIBLE: (908) 582-5928 READABLE: andys@ulysses.att.com or att!ulysses!andys What? Me speak for AT&T? You must be joking!