>> what FTS file is that? there is not one that lays out the *.MSG
>> file format specifically as the FTSC is not concerned with local
>> storage issues.

ac> On the contrary, FTS-0001 documents the *.MSG format explictly,
ac> including the required null termination of the user text.

ml> on the contrary... FTS-0001 defines "a stored message"
that is also of the 
ml> same format as packed messages in a FTN type 2 style PKT. 

It isn't.  E.g. the subject field is filled out to 72 characters or
whatever, not truncated down to the minimum.

ml> no mention is 
ml> made that this is *.MSG format. indeed, that section starts out...

Of all the ambigous things in the FTSC specs, this is not one worth a mention.

ml> Perfectly valid FidoNet systems may be implemented whose stored messages
ml> differ greatly from this format.
ml> =============================

ml> i stand, once again, by my statement above... -=B-)

Then you will fall down again.  You said that FTS-1 didn't document the
*.MSG.  It does.  You gave a reason that it wasn't concerned with local
storage methods.  It shouldn't be.  But it did anyway.

ml> yes, i do also agree, that what is detailed in FTS-0001.015 section B is 
ml> the same basic format of a *.MSG message but it is not specifically defined 
ml> as "the *.MSG spec" >

And it doesn't explicitly say it isn't written in English either. Looks
remarkably like Mark-Lewis-make-it-up-as-you-go-along-language if you take
a close look.  BFN.  Paul.
@EOT:

---