PE> What an interesting life.  I almost replied telling you everything was in
PE> order (basically I didn't believe you, and I had checked and another point
PE> [besides me] also received the message from Dave), and I was going to ask
PE> you to send me 0000ffe4.sa0 that I sent you, so that I could have a look fo
PE> myself.  I checked my logs, and I didn't send you a 0000fffe4.sa0.  I didn'
PE> send you a file for Saturday.  I haven't sent you a file for Saturday since
PE> 30 Sep 95.  The reason for this is most likely because your zmodem sent a
PE> skip command shortly after 30 Sep 95 (probably because you ran out of disk
PE> space), and that's the way Binkley works.  So every week, since late '95, I
PE> have been appending to that file, and you have not been getting it. I have
PE> now manually added that file (and another in the same boat).

FM> Can you explain the above to me? Things like "skip command" 

The zmodem file transfer protocol allows multiple files to be sent.  The
sender says "here's a file, what position do you want to start sending
from", and the receiver can reply "0", or "5000",
or "skip this file".

FM> and "Binkley works like that" 

On receipt of the skip command, rather than say "oh, they obviously
don't want their mail, I'll delete the file", it instead says OK, I've
already attempted to send it, so delete it from the .HLO file.  But don't
delete the actual file.  That way, data isn't lost, it just isn't sent.

FM> and why does it persist forever.

No-one ever writes to the .HLO file again.  The archiver utilities assume
that because an archive exists, it's already in the .HLO file, and can be
appended to.  Obviously once you know the problem, solutions exist.

BFN.  Paul.
@EOT:

---