TZUTC: -0800   
   MSGID: 56782.sync_sys@1:103/705 2b9a48c0   
   PID: Synchronet 3.20a-Linux master/989524a94 Nov 11 202 GCC 12.2.0   
   TID: SBBSecho 3.21-Linux master/3e62ad3aa Nov 12 2024 16:24 GCC 12.2.0   
   BBSID: VERT   
   CHRS: ASCII 1   
   https://gitlab.synchro.net/main/sbbs/-/issues/821#note_5996   
      
   I would try just the classic shell before giving up. It comes standard with   
   every sbbs setup and even if the sysop does mangle their own shell, classic   
   should be available, at least. I'm not saying try every possible combination   
   just if the code for the classic shell exists and it's accessible then do it.    
      
   Sure, it's a sysop induced error but it affects the users.   
   --- SBBSecho 3.21-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 90/1 103/705 105/81 106/201 124/5016 128/187 153/757 7715   
   SEEN-BY: 154/10 30 203/0 218/700 221/0 226/30 227/114 229/110 114   
   SEEN-BY: 229/206 317 400 426 428 470 550 700 705 240/1120 5832 266/512   
   SEEN-BY: 280/464 5003 5006 282/1038 291/111 292/8125 301/1 320/219   
   SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124   
   SEEN-BY: 467/888 633/280 712/848 770/1 5020/400 8912 5054/30 5075/35   
   PATH: 103/705 280/464 460/58 229/426