MSGID: 1:154/110@fidonet.org 67e14272   
   REPLY: 53851.sync@1:103/705 2c4735bd   
   TID: SBBSecho 3.24-Win32 master/740dfa696 Mar 21 2025 MSC 1942   
   BBSID: FILECABI   
   CHRS: CP850 2   
   TZUTC: -0500   
   CHRS: CP437 2   
   Hello RickV!   
      
   Thursday July 02 1970 01:16, I wrote to Digital Man:   
      
    RV>   Re: Bad packets   
    RV>   By: Digital Man to Richard Vonzel on Sun Mar 23 2025 15:59:12   
      
    DM>> Yes, sbbsecho.log (assuming you're using SBBSecho). Also, usually   
    DM>> the *reason* for the bad-packet determination is in the filename,   
    DM>> when echocfg->Global   
    RV>  Settings->> Incoming Bad Packets is set to "Rename *.reason.bad" (the   
    RV>  Settings->> default),   
      
    RV> Thank you, that helps.   
      
    RV> RickV   
    RV> ---   
    RV>  þ Synchronet þ The File Cabinet BBS   
      
   I have that setup that way for a bad packet, when a packet comes in it's still   
   call just *.bad, not that reason.bad. I'm not sure why it's bad anyways, it a   
   netmail from a hub.   
      
   RickV   
      
   === GoldED+/W64-MSVC 1.1.5-b20240306   
    # Origin: The File Cabinet BBS (filecabi.casacam.net:1025) (1:154/110)   
   --- SBBSecho 3.24-Win32   
    * Origin: The File Cabinet BBS (filecabi.casacam.net:1025) (1:154/110)   
   SEEN-BY: 105/81 106/201 128/187 153/7715 154/110 218/700 226/30 227/114   
   SEEN-BY: 229/110 114 206 317 400 426 428 470 550 700 705 266/512 291/111   
   SEEN-BY: 320/219 322/757 342/200 396/45 460/58 633/280 712/848 902/26   
   SEEN-BY: 5075/35   
   PATH: 154/110 229/426