TZUTC: -0800   
   MSGID: 54179.syncprog@1:103/705 2dd0c21a   
   PID: Synchronet 3.21b-Linux master/177a369d2 Jan 04 2026 GCC 12.2.0   
   TID: SBBSecho 3.34-Linux master/c12e79a08 Jan 16 2026 GCC 12.2.0   
   BBSID: VERT   
   CHRS: ASCII 1   
   FORMAT: flowed   
   https://gitlab.synchro.net/main/sbbs/-/commit/df722f1000bf100344e0c3a6   
   Modified Files:   
   	src/sbbs3/fixsmb.c   
   Log Message:   
   Don't report "corrupt message header ID" errors when scanning *.shd file   
      
   ... for non-hyper-allocated message bases.   
      
   Invalid header blocks following the last valid header block of a message   
   is an expected case for a self-packing (e.g. mail) message base where   
   a new shorter header takes the place of an older longer one that used more   
   blocks.   
      
   The very first header block should always be valid and there shouldn't be any   
   invalid block 'gaps' in a hyper-allocated message base.   
   --- SBBSecho 3.34-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 10/0 1 102/401 103/705 105/81 106/201 124/5016 128/187 129/14   
   SEEN-BY: 153/7715 154/110 214/22 218/0 1 215 700 810 226/30 227/114   
   SEEN-BY: 229/110 134 206 317 400 426 428 470 700 705 266/512 280/464   
   SEEN-BY: 291/111 301/1 320/219 322/757 342/200 396/45 460/58 633/280   
   SEEN-BY: 712/848 902/26 5075/35   
   PATH: 103/705 218/700 229/426