Attention mark,   
      
    ml> really? type 2[.0] is definitely defined in there...   
      
   Indeed.  However no mention of any other type except type 1 which fts-0001.016   
   declares to be obsolete.   
      
    ml> 1:153/7715 doesn't run sbbs or sbbsecho...   
      
   The reply was to 1:153/757.   
      
    ml> and here we thought you were old-school... the old-school way is   
    ml> forced right-hand margins with CRLF on each line...   
      
   type 1?  A reference would have been nice.  As for CRLF, those are even more   
   excessive than just a single LF.  Old school only requires a single CR but   
   then again that depends on where one gets schooled and of course doesn't apply   
   when speaking fts-0001.016.  As for right-hand margins that requires even more   
   wasted bytes in a packed message.  They certainly aren't required for display   
   if one considers inserting them at the start of each line, which of course is   
   variable depending on the hardware the message(s) get written to.   
      
    ml> sbbsecho's MSGID is not corrupt... it just doesn't match some   
    ml> template that some fidonet folks think it should...   
      
   Reference?  fts-0009.001 claims;   
      
     ^AMSGID: origaddr serialno   
      
   where origaddr constitutes a valid return address for the originating   
   network.  If indeed fts-0001.016 is to be considered the defacto standard for   
   Fidonet messaging then the origaddr would be 1:153/757 in this case.   
      
   End transmission.   
      
   ... Teslacle's Deviant to Fudd's Law:   
       Half of what goes in here must come out there.   
   --- GNU bash, version 4.4.19(1)-release (x86_64-silvermont-linux-gnu)   
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)