BL>   You could have written #1EOT just then... write "SE*N-BY" and see
BL> what happens. One of your messages was decimated by that. The correct
BL> approach is to assume that the user may type anything anywhere, and
BL> that includes all the various kludges used in Fido.

If QWK2PKT doesn't strip 0x01, it is a deficiency that can be
fixed by the software, and if it was being used as a BBS door,
that's exactly what would happen.  YOU are responsible for the
messages you are generating, so you either have to change
software or take care not to hit Alt-1 yourself.

BL> If we assume that an Origin line exists...
PE> You aren't even allowed to assume that.
FM> That is certainly a valid possible reading of that spec. I bet
FM> most people *don't* read it that way, but it only takes one.
FM> :-)

BL>   So what happens with the missing Origin line? What catastrophe
BL> follows that is worse than not having the Origin line?

BL>   With Paul's missing EOT we can *lose* the Origin and Tear lines in 
BL> FTS compliant messages as I've shown, 

Poor old Bob.  No such thing happens.  

BL> and maybe half the message as
BL> well, depending on how EOT is processed.

As the generator of SOT/EOT, that's entirely your problem.  The
same as if you try to be really clever by going 
echo "hello" >temp.pkt
and then laughing at how I didn't get the real packet.  Real
clever, Bob.  Or writing your entire message as ^aSECRET: xyz,
because I don't run with "view kludges" on.  Real clever, Bob.
BFN.  Paul.
@EOT:

---