BL> BTW, how do you know where to add your EOT? Read the
BL> Tear line, do you? If that's the case, what's it doing
BL> that the Tear line doesn't do? Your EOT logic is loony.

FM> Actually, that's a very good point. If an automated
FM> process can determine where to place a SOT/EOT pair,
FM> then by trivial proof a SOT/EOT pair ain't necessary.

You've had a brain fart. That doesnt apply to what is CREATING the message,
say taking what an external editor hands it as user text, bracketing that
with the SOT/EOT pair, and THEN doing whatever it chooses to with control
info outside the block of user text its not concerned with.

Its just as true if its got an internal editor too.
@EOT:

---