PE> Actually, after getting an EOT I only delete lines starting
 PE> "---" and "origin" etc.

 BL> Very wise... but you lost a genuine Origin line.

 PE> No, I only delete them when displaying user-text. The address
 PE> is still gathered from the last origin line.

  Eh? The *last* origin line? How do you know which one is the right 
one? I thought EOT was supposed to identify it? Do you read the first 
one following EOT or the last one following EOT, or the last one?

 BL> What out-of-spec message? Which FTS spec did I break?

 PE> You didn't. You violated the only FSC spec that defines
 PE> SOT/EOT.

 PE> PROPOSALS
 PE> ---------

 PE> Proposals are those publications which have been submitted by
 PE> developers.  You are not obliged to follow any of them.  However,
 PE> in the situation where a developer introduces a new keyword, no
 PE> further proposal may alter the use of that keyword in any way.
 PE> In addition, if you wish to use any such keyword introduced by a
 PE> proposal, you are required to adhere to the proposal to the
 PE> letter.  Non-compliance to these keyword-specifications will
 PE> result in the system being in FTSCD PROPOSAL BREACH.  You are
 PE> not expected to ever be in FTSCD PROPOSAL BREACH, but if you
 PE> are, and you have been alerted to this situation, you are expected
 PE> to fix the situation AS SOON AS POSSIBLE.  Failure to fix the
 PE> situation within 6 months results in you being in FTSCD BREACH,
 PE> without any further leniency period.  All proposals have names
 PE> of FSC-05xx, and are available from the FTSCD Chair.

  Are you saying that #1 EOT may not be typed in a message? I am not
making any proposals. I'm not trying to use your EOT keyword. I'm just
typing #1EOT as part of normal text in a message, using a mailer which
does not add SOT/EOT.

  This is exactly the same as typing AREA: as the first line in a
Netmail message. It's just part of text and you have to assume it can
happen. Your #1EOT can be part of text, like any other keyword. The
difference is that the *other* keywords are not inside the Tearline
and Origin line.

  EOT is flawed, Paul... seriously flawed.

  If I typed "MSGID" is normal text, a msgig-aware reader would read 
the first one outside text and ignore the false one in text. The same
applies to all other control lines at the head of the message, That's 
why they're at the head of the message. Perhaps you don't understand
this. EOT is different... it *inside* the text window.

  Your SOT/EOT spec is flawed. It should specify that the real EOT is
the *last* one.

Regards,
Bob

___ Blue Wave/QWK v2.12
@EOT:

---