Subj : Re: [wiki.synchro.net] page added: howto:freq
To   : Digital Man
From : Gamgee
Date : Sun Mar 09 2025 09:20:25

  Re: Re: [wiki.synchro.net] page added: howto:freq
  By: Digital Man to Dan Clough on Sat Mar 08 2025 08:21 pm

 >  > ; Global Keys:
 >  > ; Dirs:       Comma-separated list of BBS directories to allow FREQing
 >  > from. ; SecureDirs: As with Dirs, but only if it is a secure session.
 >  > ; MaxFiles:   The max files that can be FREQed in a single request.
 >  > ;
 >  > ; Magic words...
 >  > ; Each section name is a magic word.  Magic sections support the
 >  > following: ; Dir: REQUIRED.  The file directory to search for the file.
 >  > ; Secure: Boolean... if true, only available on secure sessions.
 >  > ; Match: A wildcard to identify the file.  The most recently uploaded
 >  > match ;        to this will be returned.
 >
 >  > Dirs=uploads
 >  > ;SecureDirs=
 >  > MaxFiles=10
 >
 >  > [ALLFILES]
 >  > Dir=uploads
 >  > Secure=No
 >  > Match=pal*.zip
 >
 >  > The "uploads" name is the Internal Code of that file area, which does
 >  > exist

 > There's no internal code prefix for the file library in which "uploads"
 > exists?

 >  > and contains files that match "pal*.zip".

 > Maybe try a simpler test, just give an exact filename first?

Another quick followup to this...  Again there is no prefix for the file library, and I did use an exact filename, with no change.

I also tried using the OS-level directory path instead of the Internal Code, and that didn't work.

Below is a log snip of what I see in sbbs.log when the FREQ comes in.  The entries before and after this snip are just the session start/stop messages, no other useful information is seen.  I also snipped the timestamp at the beginning of each line for readability:

srvc 0013 BINKP Receiving file: /sbbs/temp/00870073.req (0.0KB)                                                 srvc 0013 BINKP Received file: /sbbs/temp/00870073.req (0.0KB)                                                 srvc 0013 BINKP Deleted file: /sbbs/temp/00870073.req                                                         srvc 0013 BINKP Receiving file: /sbbs/temp/nfx4kkji.req (0.0KB)                                                 srvc 0013 BINKP Received file: /sbbs/temp/nfx4kkji.req (0.0KB)                                                 srvc 0013 BINKP Deleted file: /sbbs/temp/nfx4kkji.req
It is interesting that there are *TWO* .req messages sent with each try, not sure why that is.  I did try another experiment though - I FREQ'd a file from a non-SBBS system, and it also sent two .req's to that system, but I got back the file I requested, and two netmail replies with the file information.

What I notice about the log info above is that there is no "recognition" by BinkIT that there is a request being made.  No error message like "file not found" or anything else.  Just what you see above.  It's like the FREQ function is not enabled in BinkIT or something.

Hopefully this gives some clues about what might be happening.  Also, just for completeness, on the requesting system I have tried sending to "freq@<address>" and to "sysop@<address>" with no difference (probably doesn't matter who it's addressed to).  Also have used "FR: ALLFILES" and "FR:ALLFILES" on the subject line, with no difference.

Thanks for any help you can provide.

---
 þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.