TIP: Click on subject to list as thread! ANSI
echo: locsysop
to: Frank Malcolm
from: Paul Edwards
date: 1996-06-11 00:02:52
subject: EOT too far...

PE> BL> I can add a false EOT just as easily

PE> God you're a dork.  You CAN'T add a false EOT.  Log on to Sydney
PE> PCUG and see if you can add an EOT.  Good luck.

FM> I think you would be better served by explaining *why* you can't add a
FM> "false EOT".

You can't enter the character 0x01 on a BBS (or if you can, the
BBS software can and should be changed to prevent it).  OTOH you
can enter a fake tearline etc, since that is normal ASCII.

PE> It is the responsibility of each node to have their software set
PE> up correctly.  Failure to follow the EOT spec is the same as
PE> failing to follow the MSGID spec.  That's your problem.  A PCable
PE> offence, too.  BFN.  Paul.

FM> Is it? Does SOT/EOT have the same status as ^aMSGID & ^aREPLYID? The
FM> latter occur in a FTS document, the former FSC. And while I don't really
FM> understand the difference yet, I thought FSC had some sort of lesser
FM> status?

No, I meant it was the same as in "failure to follow specs" is
"failure to follow specs".  Only the MSGID is PCable in the above.
BFN.  Paul.
@EOT:

---
* Origin: X (3:711/934.9)

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.