TZUTC: -0700   
   MSGID: 53849.sync@1:103/705 2c469a99   
   REPLY: 1:154/110@fidonet.org 67e01181   
   PID: Synchronet 3.20e-Linux terminal-abstraction/b92945bc0 Mar 09 2025 GCC   
   12.2.0   
   TID: SBBSecho 3.24-Linux master/ad9ab307f Mar 18 2025 GCC 12.2.0   
   COLS: 80   
   BBSID: VERT   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.105   
     Re: Bad packets   
     By: Richard Vonzel to All on Sun Mar 23 2025 08:47 am   
      
    > Hello All!   
    >   
    > I'm getting bad packets from one of my hubs. I am sending them areamgr   
    > request using the  %help option, and it returns with the info but is marked   
    > as *.bad. Is there a way to tell why it's going bad? A log maybe?   
      
   Yes, sbbsecho.log (assuming you're using SBBSecho). Also, usually the *reason*   
   for the bad-packet determination is in the filename, when echocfg->Global   
   Settings->Incoming Bad Packets is set to "Rename *.reason.bad" (the default),   
   again, assuming you're using SBBSecho.   
   --    
                                               digital man (rob)   
      
   Sling Blade quote #16:   
   Karl Childers (to Doyle, re: lawn mower blade): I aim to kill you with it. Mmm.   
   Norco, CA WX: 75.5øF, 46.0% humidity, 7 mph WSW wind, 0.00 inches rain/24hrs   
   --- SBBSecho 3.24-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 153/757 7715 154/10   
   SEEN-BY: 154/30 110 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 291/111 292/8125 301/1 310/31 320/219 322/757   
   SEEN-BY: 341/66 234 342/200 396/45 423/120 460/58 256 1124 467/888   
   SEEN-BY: 633/280 712/848 770/1 902/26 5020/400 5054/30 5075/35   
   PATH: 103/705 280/464 460/58 229/426