uucico is eating my outgoing mail!

[David Herron -- One of the vertebrae]

It's a failure in the protocol -- probably flow control causing packets
to be dropped.

At some moderately high level of the UUCP protocol it's sending commands
back and forth, like the "S" command is to send a file across.  The
C command is something else.  (Sorry, I don't know what).

One side is doing a read(2) which is failing.  er.. I'd have to check in
the source, but I believe the "FAIL" means that the read returned <= 0
meaning an actual failure.  For instance, the line might have dropped.
Either that or it simply timed out.

Well, I just glanced into the source and unfortunately the answer didn't
leap out at me.  However ... The only place I could find that message being 
printed is, as I say, at the level above the line protocol.  It is waiting
to read a message from the remote side.  The FAIL message is caused when
the read() doesn't return the correct number of characters -- like I said
above, <= 0 characters.

-- 
<- David Herron; an MMDF guy                              <david at ms.uky.edu>
<- ska: David le casse\*'      {rutgers,uunet}!ukma!david, david at UKMA.BITNET
<- 
<- New official address:  attmail!sparsdev!dsh at attunix.att.com