BL>   SHIT! It's either my PKT2QWK or BlueWave! Your packet is alright.

BL>   SHIT! SHIT! It's my PKT2QWK! It doesn't like "SEEN-BY." A bug has 
BL> taken control of my mail... where's the Baygon?

Oh dear, if only we had used SOT/EOT, eh?

BL>   I think your FTS-0501 is a great idea. It's about time someone put
BL> it all together, but I would make a few extra changes:

The document describes a CURRENT protocol, it does not attempt
to create a new one.

BL> 1.  Remove the length restrictions on the To, From, Sbj strings.

That is not existing protocol.

BL> 2.  Restrict the length of the message text (12-30Kb).

That is not existing protocol either, there are mailprocessors
that do a lot more than this, and should do too.  Not to 
mention it is completely bizaare that you want to make the
"subject" go from 72 characters to infinity, but reduce the
message text down to just 12k.

BL> 3.  Define characters allowed in message text (all but control codes).

True, this one should be defined, one way or the other, whether
control characters are allowed.

BL>   Also, you forgot to define FREQ, either in Sbj string or as separate
BL> file.

I did define FREQ, in the subject string.  The "separate file"
is not a PKT, but a .REQ file.  I am only documenting the former.

BL>   There are comments I have on the language and layout, but that will
BL> take more time. I'll post a revised document tomorrow for comment.

I look forward to it!  I am interested in seeing how it can be
better structured.  BFN.  Paul.
@EOT:

---