BL> There was a Meddage-ID, but I don't know the format so I just tried
BL> abcdefghijklmon... etc, and stuck your address on the back.

Are you an engineer by any chance?

PE>> I then went and hunted around, and found a directory that
PE>> looked like it had your D. files in it. Both files were 29
PE>> bytes long, and consisted of a cunbatch, and when I
PE>> decompressed it, I found just a single line saying "#!rnews" or
PE>> similar, no message at all.

BL> Weird... they were 500-byte (or so) messages when they left this
BL> end, consisting of two messages compressed. If you only get the first 
BL> line (#! rnews 0004) it must have something to do with my crlf treatment. 
BL> How come you strip it before you uncompress it? Weird. This is what I 
BL> actually sent... (before compression)

BL> #! rnews 009
BL> Path: scorpio!Ubobl
BL> From: Ubobl{at}scorpio.rosebay.matra.com.au
BL> Newsgroups: dial.test
BL> Subject: Test 005
BL> Message-ID: " if you don't have one already.

BL> This is my log, showing that it went up, seeing I'm a silly old
BL> twit who can't be trusted... 

BL> 20:16:52 sending "scorpio/0006.DAT" to
"X.Ubobl0006" (53 bytes)
BL> 20:16:52 sent 0006.DAT (53 bytes, 0 cps)
BL> 20:16:52 sending "scorpio/0006.XQT" to
"D.Ubobl0006" (645 bytes)
BL> 20:16:52 sent 0006.XQT (645 bytes, 1935 cps)

Hmmmm.  I would have called you a filthy liar had you not posted this.
Unfortunately my stupid uucp program doesn't tell me how many bytes the
file you send me was (it does tell me how many I sent you though!), so I
can't verify that my end unless I start delving into the source code.

BL> SO... to strip all but the first line of the message, your program
BL> must first have unpacked it, removed the cunbatch, stripped it, and then
BL> compressed it again. I wopnder why it did that.

:-)  Actually, that is a possibility.  Actually, it even puts it in
another location with a different filename, so anything is possible.

Can you uuencode one of your files that you are planning on sending me, and
post it to me here (like Friday daytime whilst I've still got a system you
can talk to!), so that I can see what you're really sending.

I bet what you've done is put a null ('\0') after that rnews line.

BL> On the other hand, I think it is more likely that you are a silly
BL> young twit who can't be trusted...

That possibility is still valid.  BFN.  Paul.
@EOT:

---