Answering msg from andrew clarke to rowan crowe,
on Saturday February 04 1995 at 00:14

 JdBP>> {at}MSGID: 2:440/4.0 2f285dfb

 rc>> I notice that none of your messages have a ^aREPLY line,
 rc>> yet you are able to generate ^aMSGID. Why? Is this not
 rc>> breaking the spec by not following it fully?

 ac> He's using the Blue Wave door for Maximus, which generates a MSGID.
 ac> Combine that with an off-line reader and this is what you get (unless by
 ac> some fluke the OLR supports REPLY line generation.)

    Whoops, I didn't look very carefully at the tagline/tearline on his
message.

    I was under the impression that BWAVE (or some form of offline reader)
_did_ support ^aREPLY.

 ac> Whether it's "breaking" FTS-9 can be debated, I suppose,
but I'd much
 ac> rather bang my head on a brick wall.

    I wish my other machine was not dead. It leaves me without a copy of the
FTSC archives. I'll just grab FTS-9 from 3:635/727 now.....done.

    Obviously my memory is not as good as I thought it was. I recalled a
sentence along the lines of "if you are to implement this spec, you
must implement it fully." There is no such sentence.

     This FTS (FidoNet(r) Technical Standard) specifies an optional
     standard for the FidoNet community.  Implementation of the
     protocols defined in this document is not mandatory,  but all
     implementations of these protocols are expected to adhere to this
     standard.  Distribution of this document is unlimited.

    ".... but all implementations of these protocols are expected to
adhere to this standard" - that would be the closest I could get.

Best wishes, Ro.

---