TZUTC: -0800   
   MSGID: 55773.sync@1:103/705 2de4d4db   
   REPLY: 55769.sync@1:103/705 2de44efa   
   PID: Synchronet 3.21b-Win32 master/0bc7b3297 Jan 31 2026 MSC 1944   
   TID: SBBSecho 3.35-Linux master/0bc7b3297 Jan 31 2026 GCC 12.2.0   
   COLS: 80   
   BBSID: VERT   
   CHRS: CP437 2   
   FORMAT: flowed   
   NOTE: FSEditor.js v1.105   
     Re: BinkP errors   
     By: Waveyuk to All on Sat Jan 31 2026 05:00 pm   
      
    > Hey all.   
    >   
    > So, struggling a little with getting fido working on the bbs. I have my fido   
    > node number (2:250/18) and my uplink is 2:250/1. I can see a list of all   
    > Fido message areas in the BBS (all with 0 messages). If I try to send a   
    > message to areafix@2:250/1 putting my password in the subject line and the   
    > message body as %help I get the following on the backend of the bbs:   
    >   
    > BINKOUT We got an M_EOB, but there are still 1 files pending M_GOT   
    > Error 104 (Connection reset by peer) in recv() of first byte of packet   
    > header   
      
   More of the Binkp/BinkIT log output would be helpful.   
      
    > I'm running the BBS on Linux and have opened port 24554 for BinkP.   
      
   That's good, but it sounds like you're maknig an *outbound* connecting to your   
   hub (so in your inbound port 24554 would not be used in that case).   
      
    > Also, and maybe related, I cannot seem to work out how to use Nodelists.   
    > I've Googled and read and using the sbbsecho -n command nothing happens.   
      
   SBBSecho doesn't use nodelists. I don't think the -n option does what you   
   think it does? Run 'sbbsecho -?' for list of options, if you're curious.   
      
   I've been running just fine for over 25 years without a nodelist. You don't   
   technically need one.   
      
    > Clearly I am doing something wrong and after 31 years of being away from the   
    > BBS scene, my brain isn't recalling what I should be doing (although back in   
    > the day I think I used D'Bridge!).   
    >   
    > Any help, guidance or pointing in the right direction really appreciated.   
    > Thanks   
      
   Sure, more log output/context. :-) Usually it's an address/hostname or password   
   issue.   
   --    
                                               digital man (rob)   
      
   This Is Spinal Tap quote #20:   
   Well, I'm sure I'd feel much worse if I weren't under such heavy sedation.   
   Norco, CA WX: 70.6øF, 28.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrs   
   --- SBBSecho 3.35-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 10/0 1 102/401 103/1 17 705 105/81 106/201 124/5016 128/187   
   SEEN-BY: 129/14 153/7715 154/110 218/0 1 215 601 700 840 860 880 226/30   
   SEEN-BY: 227/114 229/110 112 134 206 317 400 426 428 470 700 705 266/512   
   SEEN-BY: 280/464 291/111 301/1 320/219 322/757 342/200 396/45 460/58   
   SEEN-BY: 633/280 712/848 902/26 5075/35   
   PATH: 103/705 218/700 229/426