TZUTC: -0600
MSGID: 55528.sync@1:103/705 2daf859a
REPLY: 55517.sync@1:103/705 2dae8d19
PID: Synchronet 3.21a-Linux master/21980aee6 Dec 05 2025 GCC 14.2.0
TID: SBBSecho 3.33-Linux master/93cefd0e8 Dec 20 2025 GCC 12.2.0
BBSID: PALANTIR
CHRS: CP437 2
FORMAT: flowed
-=> Digital Man wrote to RickV <=-
DM> Re: File Request question
DM> By: RickV to Mindsurfer on Sun Dec 21 2025 06:34 am
> Thank you. I was really looking to find out how you send a netmail for a
> file request. It's been a long time since I've done that.
DM> To send a FidoNet file request netmail from Synchronet, the user needs
DM> to either be a sysop or have the 'F' exemption and then include
DM> "FR:" as the subject of the netmail message they're sending.
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:
Dec 22 09:16:25 palantir synchronet: srvc 0013 BINKP JSBinkP/4 inbound
connection from 198.74.54.171:55602
Dec 22 09:16:25 palantir synchronet: srvc 0013 BINKP Will encrypt session.
Dec 22 09:16:25 palantir synchronet: srvc 0013 BINKP Peer version:
BinkIT/2.42,JSBinkP/4,sbbs3.21a/Linux
Dec 22 09:16:25 palantir synchronet: srvc 0013 BINKP Remote addresses:
1:135/115.7@fidonet
Dec 22 09:16:25 palantir synchronet: srvc 0013 BINKP Inbound session for:
1:135/115.7@fidonet
Dec 22 09:16:25 palantir synchronet: srvc 0013 BINKP CRAM-MD5 password match
for 1:135/115.7@fidonet
Dec 22 09:16:25 palantir synchronet: srvc 0013 BINKP Receiving file:
/sbbs/temp/00870073.req (0.0KB)
Dec 22 09:16:25 palantir synchronet: srvc 0013 BINKP Received file:
/sbbs/temp/00870073.req (0.0KB)
Dec 22 09:16:25 palantir synchronet: srvc 0013 BINKP Deleted file:
/sbbs/temp/00870073.req
Dec 22 09:16:25 palantir synchronet: srvc 0013 BINKP Sending file:
/files/main/uploads/pal2512.zip (1431.5KB)
Dec 22 09:16:25 palantir synchronet: srvc 0013 BINKP Receiving file:
/sbbs/temp/neqzr8wk.req (0.0KB)
Dec 22 09:16:25 palantir synchronet: srvc 0013 BINKP Received file:
/sbbs/temp/neqzr8wk.req (0.0KB)
Dec 22 09:16:25 palantir synchronet: srvc 0013 BINKP Deleted file:
/sbbs/temp/neqzr8wk.req
Dec 22 09:16:25 palantir synchronet: srvc 0013 BINKP We got an M_EOB, but there
are still 1 files pending M_GOT
Dec 22 09:16:27 palantir synchronet: srvc 0013 BINKP Sent file:
/files/main/uploads/pal2512.zip (1431.5KB)
Dec 22 09:16:27 palantir synchronet: srvc 0013 BINKP Sending file:
/files/main/uploads/pal2512.zip (1431.5KB)
Dec 22 09:16:30 palantir synchronet: srvc 0013 BINKP Sent file:
/files/main/uploads/pal2512.zip (1431.5KB)
Dec 22 09:16:32 palantir synchronet: srvc 0013 BINKP [198.74.54.171] JavaScript
service thread terminated (0 clients remain, 0 total, 616 served)
Maybe there's something there that would indicate what caused the
duplicate request messages, but not likely to my eye. The first .req is
the hex conversion of the receiving systems FTN address (1:135/115), and
the second .req appears to be a random-generated name from the
requesting system.
Thanks for any info you may be able to provide on this!
... I was on a roll till I slipped on the butter.
--- MultiMail/Linux v0.52
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 129/14 153/757 7715
SEEN-BY: 154/10 30 110 203/0 218/700 221/0 226/30 227/114 229/110
SEEN-BY: 229/112 134 206 317 400 426 428 470 700 705 240/1120 5832
SEEN-BY: 263/1 266/512 280/464 5003 5006 291/111 292/8125 301/1 310/31
SEEN-BY: 320/219 322/757 341/66 234 342/200 396/45 423/120 460/58
SEEN-BY: 460/256 1124 633/280 712/848 770/1 902/26 5020/400 8912 5054/30
SEEN-BY: 5075/35
PATH: 103/705 280/464 460/58 229/426
|
