TZUTC: -0800   
   MSGID: 55532.sync@1:103/705 2db02d0b   
   REPLY: 55531.sync@1:103/705 2db02055   
   PID: Synchronet 3.21a-Linux master/114c3dfde Dec 19 2025 GCC 12.2.0   
   TID: SBBSecho 3.33-Linux master/93cefd0e8 Dec 20 2025 GCC 12.2.0   
   COLS: 80   
   BBSID: VERT   
   CHRS: CP437 2   
   FORMAT: flowed   
   NOTE: FSEditor.js v1.105   
     Re: Re: File Request question   
     By: Gamgee to Digital Man on Mon Dec 22 2025 08:57 pm   
      
    > -=> Digital Man wrote to Gamgee <=-   
    >   
    >  DM>   Re: Re: File Request question   
    >  DM>   By: Gamgee to Digital Man on Mon Dec 22 2025 10:40 am   
    >   
    >  > Thank you also for the new writeup posted on the Wiki for this.  I   
    >  > tested that this morning, to my system from a "test point" that I have.   
    >  > It worked properly, but it did result in the file being sent twice,   
    >  > because there ended up being (2) File Requests (.req) sent, for reasons   
    >  > unknown.  The requesting system is also running SBBS, if that matters.   
    >  > The second file received just over-wrote the first one, in the   
    >  > "inbound" directory, so no real harm done, but seems off a little.   
    >  > Here's a log snippet of the transaction, from the system that received   
    >  > the two requests:   
    >   
    >  DM> The sbbsecho.log messages concerning the file request would likely be   
    >  DM> more helpful.   
    >   
    > Okay, here is the snippet from the orignating system (the point) from   
    > that log.  It shows only the one file request (00870073.req) being   
    > generated and sent.  Not sure where that other .req file came from in   
    > the original (binkit) log that I posted.  Also, in case it mattered,   
    > that line complaining about missing 'areas.bbs', I created an empty one   
    > and repeated the test with the same results.   
      
   The "Could not open Area File" error doesn't matter. And the correct way to   
   suppress that error would be to set echocfg->Paths and Filenames->Area File to   
   a blank string.   
      
    > Also, the timestamp   
    > difference between these logs is because the sending system is on UTC   
    > time.   
    >   
    > 2025-12-22 15:16:16 Could not open Area File (../data/areas.bbs): No such   
    > file or directory   
    > 2025-12-22 15:16:16 Created NetMail (1.msg) from Preem Palver (1:135/115.7)   
    > to sysop (1:135/115), attr: 0981 (PRIVATE, KILLSENT, LOCAL, FREQ), subject:   
    > ALLFILES   
    > 2025-12-22 15:16:16 BSO file request from Preem Palver (1:135/115.7) to   
    > sysop (1:135/115): ALLFILES   
    > 2025-12-22 15:16:16 File (../fido/outbound/00870073.req, 0.0KB) for   
    > 1:135/115 added to BSO/FLO file: ../fido/outbound/00870073.dlo   
    > 2025-12-22 15:16:16 SBBSecho (PID 46223) exiting with error level 0,   
    > NetMail(0 imported, 1 exported, 0 packed)   
    >   
    > Any clues appreciated, thanks!   
      
   Not really any yet. So you only see the second .req filename mentioned in logs   
   on the receiving system?   
   --    
                                               digital man (rob)   
      
   Rush quote #76:   
   His reserve a quiet defense, riding out the day's events, the river..Tom Sawyer   
   Norco, CA WX: 63.3øF, 73.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrs   
   --- SBBSecho 3.33-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