TZUTC: -0800   
   MSGID: 57442.sync_sys@1:103/705 2c31339e   
   PID: Synchronet 3.20e-Linux master/7c30785d2 Mar 05 2025 GCC 12.2.0   
   TID: SBBSecho 3.23-Linux master/2adf8468d Mar 06 2025 GCC 12.2.0   
   BBSID: VERT   
   CHRS: ASCII 1   
   https://gitlab.synchro.net/main/sbbs/-/issues/885#note_6733   
      
   I would not attempt to manipulate incoming messages at all.   
      
   Edited to elaborate: each part of the incoming message packet has special   
   meaning. The "SERVER" is the "from_user" field in the beginning of the next   
   packet. Simply inserting a CR-LF in front of "SERVER" does not fix the   
   problem, because the remaining packet string would need to be processed by the   
   client separately from the proceeding packet. Besides, it's incomplete since   
   the two meshed packets exceed the legal length of one packet anyway.   
      
   For the record, the Mystic clients see the same faulty startup message too.   
      
   TL;DR: The server needs to fix what it's sending out.   
   --- SBBSecho 3.23-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 10/0 1 102/401 103/1 13 17 705 105/81 106/201 124/5016 128/187   
   SEEN-BY: 153/7715 154/110 214/22 218/0 1 215 601 700 720 840 860 880   
   SEEN-BY: 226/30 227/114 229/110 114 206 317 400 426 428 470 550 700   
   SEEN-BY: 229/705 266/512 280/464 291/111 301/1 320/219 322/757 342/200   
   SEEN-BY: 396/45 460/58 633/280 712/848 902/26 5075/35   
   PATH: 103/705 218/700 229/426