BL> PQWK to add SOT/EOT and eliminate problems with kludge lines in
BL> the text, but it didn't. Now it does. Or does it?

PE> Try to keep up, Bob. We resolved that ages ago. It had diddly
PE> squat to do with SOT/EOT, it had to do with PQWK scanning the
PE> message body to get an address, instead of using the address it
PE> was given on the command line. Frank discovered the bug, and I
PE> fixed it, and verified it by getting him to send me a message
PE> with an origin line, and then I informed the rest of you, and
PE> that was the end of my involvement for months. BFN. Paul.

BL>   Then what was all the discussion with Bill about the extra Origin
BL> line 

That was just discourteous.  It wasn't actually causing any 
software problems for me.

BL> and with Rod about the extra MSGID line?

That was a bug in PQWK250.  As explained over many messages which
you could have read if you had wanted to know.  If you've still
got a copy of PQWK250, try it out for yourself, and do a hex dump
of the generated PKT and look in the header part.  DON'T send me
the resulting packet.  BFN.  Paul.
@EOT:

---