TZUTC: -0700   
   MSGID: 55014.sync@1:103/705 2d4ba26b   
   REPLY: 51952.dove-syncdisc@12:1/2 2d4ad50a   
   PID: Synchronet 3.21a-Linux master/2287878bd Sep 27 2025 GCC 12.2.0   
   TID: SBBSecho 3.30-Linux master/88b423313 Sep 29 2025 GCC 12.2.0   
   COLS: 80   
   BBSID: VERT   
   CHRS: CP437 2   
   FORMAT: flowed   
   NOTE: FSEditor.js v1.105   
     Re: sbbsecho and bad packets   
     By: deon to Digital Man on Tue Oct 07 2025 07:49 pm   
      
    >   Re: sbbsecho and bad packets   
    >   By: Digital Man to deon on Mon Oct 06 2025 11:30 pm   
    >   
    > Howdy,   
    >   
    >  > Indeed, yes, but the DateTime field definition for the packed message is   
    >  > "inherited" from the Stored Message definition - it's not redefined.   
    >   
    > I'm not seeing what you are seeing - but ok.   
      
   FSP-1042 (still in draft stage) has the packed message header more clearly   
   defined:   
   ,-------------------------------------------------------------   
                    | Name         | Type | Length     | Description                
   |                 +--------------+------+------------+----------   
   ---------------+                 | dateTime     | nStr | Exactly 19 | Date and   
   time of message |                 | toUserName   | nStr | 0-35       | User   
   the message is to   |                 | fromUserName | nStr | 0-35       |   
   User the message is from |                 | subject      | nStr | 0-71         
   | Message subject          |                 | text         | nStr |   
   0-Infinity | Message body             |                 `-------   
   ------+------+------------+--------------------------'   
      
      
   The nStr type is defined (in FSP-1024) as:   
   nStr:   
           NUL-terminated string.  A sequence of zero or more non-NUL   
           characters followed by a single NUL character.  If a length is   
           specified, does NOT include the terminating NUL.  If an nStr   
           with a length of 19 is stored, it will take 20 bytes of   
           storage because of the terminating NUL.   
      
    > I'll tell this node that they need to have their software fixed to not send   
    > DateTimes as a 20 byte field, but a null terminated string - I think the   
    > source is hpt, so lets see if they agree...   
      
   I think you have that backwards, the DateTime must be a null terminated   
   string: exactly 19 characters followed by a NUL.   
   --    
                                               digital man (rob)   
      
   Sling Blade quote #7:   
   Karl: I don't reckon the Good Lord would send anybody like you to Hades.   
   Norco, CA WX: 59.4øF, 88.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrs   
   --- SBBSecho 3.30-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 10/0 1 102/401 103/1 17 705 105/81 106/201 124/5016 128/187   
   SEEN-BY: 129/14 153/7715 154/110 218/0 1 215 601 610 700 840 860 880   
   SEEN-BY: 226/30 227/114 229/110 206 317 400 426 428 470 700 705 266/512   
   SEEN-BY: 280/464 291/111 301/1 320/219 322/757 342/200 396/45 460/58   
   SEEN-BY: 633/280 712/848 902/26 5075/35   
   PATH: 103/705 218/700 229/426