Re: Re: File Request question
By: Gamgee to Digital Man on Wed Dec 24 2025 07:47 am

DM, this is my second reply to you on this... Just thought of another thing that might be relevant - I did this same FREQ test from my main BBS to several other FidoNet systems, and got the same results (two .req files sent, and the requested file sent back twice from their system. The SBBS build is newer on the "test point" system - master/3fa76bald ; and the main/real BBS is 21980aee6. Both on Linux. Just wanted you to have this info.

Did you confirm the that FREQ file si actually sent twice? If it was, it would appear in the BinkP-related log output on both systems. Was that observed?
--
digital man (rob)

Synchronet "Real Fact" #16:
Synchronet first supported FidoNet networking (with SBBSFIDO) in 1992
Norco, CA WX: 57.9øF, 95.0% humidity, 0 mph NE wind, 1.25 inches rain/24hrs
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Digital Man wrote to Gamgee <=-

Re: Re: File Request question
By: Gamgee to Digital Man on Wed Dec 24 2025 07:47 am

DM, this is my second reply to you on this... Just thought of another thing that might be relevant - I did this same FREQ test from my main BBS to several other FidoNet systems, and got the same results (two .req files sent, and the requested file sent back twice from their system. The SBBS build is newer on the "test point" system - master/3fa76bald ; and the main/real BBS is 21980aee6. Both on Linux. Just wanted you to have this info.

Did you confirm the that FREQ file si actually sent twice? If it was,
it would appear in the BinkP-related log output on both systems. Was
that observed?

Yes, the BinkP logs (syslog) show it on both sides as being
sent/received twice.



... Gone crazy, be back later, please leave message.
--- MultiMail/Linux v0.52
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL

Re: Re: File Request question
By: Deuce to Gamgee on Wed Dec 24 2025 05:03 pm

It sounds like the REQ file is being included in a file reference flow file (*.*lo). It should not be, see FTS-5005 for details.

Thanks, fixed now.
--
digital man (rob)

Synchronet/BBS Terminology Definition #79:
SSJS = Server-side JavaScript
Norco, CA WX: 64.0øF, 63.0% humidity, 4 mph WSW wind, 0.49 inches rain/24hrs ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Re: File Request question
By: Gamgee to Digital Man on Wed Dec 24 2025 07:47 am

DM, this is my second reply to you on this... Just thought of another thing that might be relevant - I did this same FREQ test from my main BBS to several other FidoNet systems, and got the same results (two .req files sent, and the requested file sent back twice from their system. The SBBS build is newer on the "test point" system - master/3fa76bald ; and the main/real BBS is 21980aee6. Both on Linux. Just wanted you to have this info.

Thanks, should be fixed now, based on Deuce's analysis and feedback.
--
digital man (rob)

Breaking Bad quote #30:
Damn, chick's got an ass like an onion - makes me want to cry. - Hank Schrader Norco, CA WX: 64.0øF, 63.0% humidity, 4 mph WSW wind, 0.49 inches rain/24hrs ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

The simplest way to do a FREQ is:
echo filenameiwant.foo >> /sbbs/ftn/outbound/0e32000c.req

That's not super difficult, but not as easy as "FR:filename" in the
subject line of a netmail, IMHO.

Indeed! ;)

---
þ SLMR 2.1a þ "Wanna give Honest Abe another term in the Oval Office?"
þ Synchronet þ CAPCITY2 * Capitol City Online

Digital Man wrote to Gamgee <=-

Re: Re: File Request question
By: Gamgee to Digital Man on Wed Dec 24 2025 07:47 am

DM, this is my second reply to you on this... Just thought of another thing that might be relevant - I did this same FREQ test from my main BBS to several other FidoNet systems, and got the same results (two .req files sent, and the requested file sent back twice from their system. The SBBS build is newer on the "test point" system - master/3fa76bald ; and the main/real BBS is 21980aee6. Both on Linux. Just wanted you to have this info.

Thanks, should be fixed now, based on Deuce's analysis and feedback.

Thank you. I'm out of town for the week but will upgrade over the
weekend and test. Appreciate it! Also appreciate you, Deuce. :-)




... Gone crazy, be back later, please leave message.
--- MultiMail/Linux v0.52
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL

Re: Re: File Request question
By: Gamgee to Deuce on Wed Dec 24 2025 02:21 pm

Reading the wiki, the oddball way it's describing there, it's important to note that the .req file is not being created in the outbound dir.

I believe you, but don't know why that's important here.

Because wuth the REQ file in the outbound dir, it will get sent twice. ;)

The simplest way to do a FREQ is:
echo filenameiwant.foo >> /sbbs/ftn/outbound/0e32000c.req

That's not super difficult, but not as easy as "FR:filename" in the
subject line of a netmail, IMHO.

Ah, I had thought you were doing the manual method, not the Synchronet method using SBBSEcho.

If you then want to force a callout:
touch /sbbs/ftn/outbound/0e32000c.dlo
(Or run binkit -l 1:3634/12)

But wouldn't that just create an empty (0 byte) .dlo file which would
not be pointing at the .req file? Normally a .?lo file is a text
listing of the actual filename/pkt/.?ut to be sent. In this case the
.dlo file wouldn't have that info.

Yes, the empty .flo file is a "flow file" that causes a callout as soon as possible.

Packet files (.?ut) also do no show up in .?lo files since they trigger a callout on their own.

REQ files are special in that they're transferred during connections but *do not* trigger a callout, so to trigger a callout rather than just wait for the next time you connect, you need to create a file that does trigger a callout. That's what a zero-length .dlo file does.
---
þ Synchronet þ The future of BBSing

Re: Re: File Request question
By: Gamgee to Digital Man on Thu Dec 25 2025 07:43 pm

Also appreciate you, Deuce. :-)

No problem, I really do appreciate you reporting the issue and following up with details. That behaviour makes finding and fixing problems like this easy for us.
---
þ Synchronet þ The future of BBSing

Deuce wrote to Gamgee <=-

Re: Re: File Request question
By: Gamgee to Deuce on Wed Dec 24 2025 02:21 pm

Reading the wiki, the oddball way it's describing there, it's important to note that the .req file is not being created in the outbound dir.

I believe you, but don't know why that's important here.

Because wuth the REQ file in the outbound dir, it will get sent twice.
;)

The simplest way to do a FREQ is:
echo filenameiwant.foo >> /sbbs/ftn/outbound/0e32000c.req

That's not super difficult, but not as easy as "FR:filename" in the
subject line of a netmail, IMHO.

Ah, I had thought you were doing the manual method, not the Synchronet method using SBBSEcho.

If you then want to force a callout:
touch /sbbs/ftn/outbound/0e32000c.dlo
(Or run binkit -l 1:3634/12)

But wouldn't that just create an empty (0 byte) .dlo file which would
not be pointing at the .req file? Normally a .?lo file is a text
listing of the actual filename/pkt/.?ut to be sent. In this case the
.dlo file wouldn't have that info.

Yes, the empty .flo file is a "flow file" that causes a callout as soon
as possible.

Packet files (.?ut) also do no show up in .?lo files since they trigger
a callout on their own.

REQ files are special in that they're transferred during connections
but *do not* trigger a callout, so to trigger a callout rather than
just wait for the next time you connect, you need to create a file that does trigger a callout. That's what a zero-length .dlo file does.

Ahhhhh man, that's perfect. GREAT explanation for something I thought I understood (and mostly did), but that clears up a few things for me on
how that all works. Thank you again and greatly appreciated!




... Gone crazy, be back later, please leave message.
--- MultiMail/Linux v0.52
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL

Deuce wrote to Gamgee <=-

Re: Re: File Request question
By: Gamgee to Digital Man on Thu Dec 25 2025 07:43 pm

Also appreciate you, Deuce. :-)

No problem, I really do appreciate you reporting the issue and
following up with details. That behaviour makes finding and fixing problems like this easy for us.

Thank you very much, and glad to help when I can. You guys are more appreciated than you know. :-)

Seriously, thanks.




... Gone crazy, be back later, please leave message.
--- MultiMail/Linux v0.52
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL

Re: Re: File Request question
By: Deuce to Gamgee on Fri Dec 26 2025 07:19:29

Re: Re: File Request question
By: Gamgee to Deuce on Wed Dec 24 2025 02:21 pm

That's not super difficult, but not as easy as "FR:filename" in the subject line of a netmail, IMHO.

Hi.

In the subject line, the filename is a DOS file type, but when it's sent, in my case, it removes the extension and I never receive anything, apart from an error message from the destination BBS.

I send a netmail with FR:AP251227.ZIP, but when I check the log, it appears without the extension and I receive an error message.

Here's the log:

2025-12-27 17:30:02 Created NetMail (1.msg) from Tanausu Martin (21:3/219) to Andrew Leary (21:4/105), attr: 0981 (PRIVATE, KILLSENT, LOCAL, FREQ), subject: AP251227.
2025-12-27 17:30:02 OST file request from Tanausu Martin (21:3/219) to Andrew Leary (21:4/105): AP251227.
2025-12-27 17:30:02 File (../fido/outbound.015/00040069.req, 0.0KB) for 21:4/105 added to BSO/FLO file: ../fido/outbound.015/00040069.flo
2025-12-27 17:30:02 SBBSecho (PID 5176) exiting with error level 0, NetMail(0 imported, 1 exported, 0 packed)
2025-12-27 17:30:22 Importing /sbbs/fido/nonsecure/570D59FB.PKT (type 2e, 0.7KB) from 21:4/105 to 21:3/219
2025-12-27 17:30:22 mbcico FREQ processor (21:4/105) To: Sysop (21:3/219) Attr: 0081 (PRIVATE, KILLSENT) Imported
2025-12-27 17:30:23 SBBSecho (PID 5651) exiting with error level 0, Packets(1 imported, 0 sent), NetMail(1 imported, 0 exported, 0 packed)

---
þ Synchronet þ Citrick BBS

Re: Re: File Request question
By: Tanausu M. to Deuce on Sat Dec 27 2025 06:37 pm

I send a netmail with FR:AP251227.ZIP, but when I check the log, it appears without the extension and I receive an error message.

Here's the log:

2025-12-27 17:30:02 Created NetMail (1.msg) from Tanausu Martin (21:3/219) to Andrew Leary (21:4/105), attr: 0981 (PRIVATE, KILLSENT, LOCAL, FREQ), subject: AP251227.

This is more a Digital Man issue, but I do note that the prefix ("FR:") is the same length as the part truncated from the end ("ZIP").

Not sure if that's related or not.
---
þ Synchronet þ The future of BBSing

I send a netmail with FR:AP251227.ZIP, but when I check the log, it appears without the extension and I receive an error message.

Here's the log:

2025-12-27 17:30:02 Created NetMail (1.msg) from Tanausu Martin (21:3/219) to Andrew Leary (21:4/105), attr: 0981 (PRIVATE, KILLSENT, LOCAL, FREQ), subject: AP251227.

This is more a Digital Man issue, but I do note that the prefix ("FR:")
is the same length as the part truncated from the end ("ZIP").

Not sure if that's related or not.

Yes, it seems so. With the latest patch you released, it no longer sends duplicates.

--- MultiMail/FreeBSD v0.52
þ Synchronet þ Citrick BBS

Re: Re: File Request question
By: Deuce to Tanausu M. on Mon Dec 29 2025 04:20 am

Re: Re: File Request question
By: Tanausu M. to Deuce on Sat Dec 27 2025 06:37 pm

I send a netmail with FR:AP251227.ZIP, but when I check the log, it appears without the extension and I receive an error message.

Here's the log:

2025-12-27 17:30:02 Created NetMail (1.msg) from Tanausu Martin (21:3/219) to Andrew Leary (21:4/105), attr: 0981 (PRIVATE, KILLSENT, LOCAL, FREQ), subject: AP251227.

This is more a Digital Man issue, but I do note that the prefix ("FR:") is the same length as the part truncated from the end ("ZIP").

Not sure if that's related or not.

I wasn't able to reproduce this (see the extension is included in the filename from the file request subject line):

12/29/25 03:53:36 Created NetMail (2.msg) from Rob Swindell (1:103/705) to wx6yyz (1:103/13), attr: 0983 (PRIVATE, CRASH, KILLSENT, LOCAL, FREQ), subject: FILENAME.EXT
12/29/25 03:53:36 BSO file request from Rob Swindell (1:103/705) to wx6yyz (1:103/13): FILENAME.EXT
--
digital man (rob)

Rush quote #21:
You can surrender without a prayer, but never really pray without surrender Norco, CA WX: 57.8øF, 29.0% humidity, 3 mph ESE wind, 0.00 inches rain/24hrs ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Re: File Request question
By: Digital Man to Deuce on Mon Dec 29 2025 03:55 am

I wasn't able to reproduce this (see the extension is included in the filename from the file request subject line):

I assume it's not doing some archive weirdness...
---
þ Synchronet þ The future of BBSing

Re: Re: File Request question
By: Digital Man to Deuce on Mon Dec 29 2025 03:55:18

I wasn't able to reproduce this (see the extension is included in the filename from the file request subject line):

12/29/25 03:53:36 Created NetMail (2.msg) from Rob Swindell (1:103/705) to wx6yyz (1:103/13), attr: 0983 (PRIVATE, CRASH, KILLSENT, LOCAL, FREQ), subject: FILENAME.EXT
12/29/25 03:53:36 BSO file request from Rob Swindell (1:103/705) to wx6yyz (1:103/13): FILENAME.EXT
--
digital man (rob)

Hello. I've also provided little to no information. I'm currently using what I believe is one of the latest versions of dailybuild_linux_x64, but with FreeBSD 15. I don't know if the master branch would change anything regarding that minor bug.
Currently, I can't switch the server to another Linux system. It's something beyond my control.

What I've done is create a script, and it seems to avoid that bug. Does anyone know where the bug is? I'll have to compile the master branch to see if it disappears and saves me all this trouble.

Sorry for filling up the message with all of the following.

events.log

2025-12-29 18:24:27 BINKOUT Call attempt to 1:229/700@fidonet, file: /sbbs/fido/outbound.001/00e502bc.clo
2025-12-29 18:24:27 BINKOUT JSBinkP/4 call to 1:229/700@fidonet initiated 2025-12-29 18:24:29 BINKOUT Connecting to 1:229/700@fidonet on mysticrealms.ddns.net:24554
2025-12-29 18:24:30 BINKOUT Authentication successful: not secure
2025-12-29 18:24:30 BINKOUT Sending file: /sbbs/fido/outbound.001/00e502bc.req (0.0KB)
2025-12-29 18:24:30 BINKOUT File sent: /sbbs/fido/outbound.001/00e502bc.req (0.0KB)
2025-12-29 18:24:30 BINKOUT We received an M_EOB, but there is still an M_GOT file pending.
2025-12-29 18:24:30 BINKOUT File deleted: /sbbs/fido/outbound.001/00e502bc.clo 2025-12-29 18:24:30 BINKOUT File deleted: /sbbs/fido/outbound.001/00e502bc.req 2025-12-29 18:24:31 BINKOUT Timed event: '?binkit' returned 0



sbbsecho.log

2025-12-29 18:24:22 NetMail (1.msg) created from Tanausu Martin (2:341/207) to Jeff Earle (1:229/700), attr: 0983 (PRIVATE, CRASH, KILLSENT, LOCAL, FREQ), subject: FR:AP251228.ZIP
2025-12-29 18:24:22 OST file request from Tanausu Martin (2:341/207) to Jeff Earle (1:229/700): FR:AP251228.ZIP
2025-12-29 18:24:22 BSO/FLO file shrunk for 1:229/700: ../fido/outbound.001/00e502bc.clo
2025-12-29 18:24:22 SBBSecho (PID 95438) ending with error level 0, NetMail (0 imported, 1 exported, 0 packaged)

Debug:
=== Only variables/properties ===
from = Tanausu Martin
from_net_type = 2
from_net_addr = 2:341/207
a = Jeff Earle
to_net_type = 2
to_net_addr = 1:229/700
subject = FR:AP251228.ZIP
attr = 1
auxattr = 8193
netattr = 73
-----Header Properties-----
from (string) = Tanausu Martin
from_net_type (number) = 2
from_net_addr (string) = 2:341/207
a (string) = Jeff Earle
to_net_type(number) = 2
to_net_addr (string) = 1:229/700
subject(string) = FR:AP251228.ZIP
attribute(number) = 1
auxiliary_attribute(number) = 8193
netattr (number) = 73
-----end of header-----

var new_hdr =
{
from: name_of_from,
from_network_type: hdr.to_network_type,
from_network_address: aka,
to: subject_name,
from_network_type: hdr.to_network_type,
from_network_address: subject.address,
subject: parts.subject,
attribute: hdr.attribute,
attribute: hdr.attribute,
attribute: hdr.attribute,
netattr: hdr.netattr
};

// Check if the message is a file request
// If so, set the flag and let sbbs do the rest
if (new_hdr.subject != null && new_hdr.subject.substring(0, 3) === "FR:")
{
new_hdr.netattr |= NETMSG_LOCAL | NETMSG_KILLSENT | NETMSG_CRASH;
new_hdr.auxattr |= MSG_FILEREQUEST;
}

getproperties(new_hdr)
dump_header_props(new_hdr);

if(!msgbase.save_msg(new_hdr, parts.body))
{
print("Error sending message\n");
continue;
}

//Mark the original as deleted
hdr.attr |= MSG_DELETE;

if(!msgbase.put_msg_header(true, msg_nodelete[a], hdr))
print("Error updating header for offset " + msg_nodelete[a]);

---
þ Synchronet þ Citrick BBS

Re: Re: File Request question
By: Tanausu M. to Digital Man on Mon Dec 29 2025 06:53 pm

What I've done is create a script, and it seems to avoid that bug. Does anyone know where the bug is? I'll have to compile the master branch to see if it disappears and saves me all this trouble.

Sorry for filling up the message with all of the following.

sbbsecho.log

2025-12-29 18:24:22 NetMail (1.msg) created from Tanausu Martin (2:341/207) to Jeff Earle (1:229/700), attr: 0983 (PRIVATE, CRASH, KILLSENT, LOCAL, FREQ), subject: FR:AP251228.ZIP

The "FR:" isn't supposed to actually be part of the subject stored in the message header. If you include the "FR:" prefix in a netmail subject that you enter from within Synchronet (the terminal server), it'll strip the "FR:" prefix and add the FREQ attribute. This message you're showing has both the FREQ attribute *and* the "FR:" prefix in the subject. That's not correct.
--
digital man (rob)

Rush quote #25:
Throw off those chains of reason and your prison disappears
Norco, CA WX: 67.0øF, 21.0% humidity, 15 mph NE wind, 0.00 inches rain/24hrs ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Re: File Request question
By: Tanausu M. to Digital Man on Mon Dec 29 2025 06:53 pm

Hello. I've also provided little to no information. I'm currently using what I believe is one of the latest versions of dailybuild_linux_x64, but with FreeBSD 15. I don't know if the master branch would change anything regarding that minor bug.
Currently, I can't switch the server to another Linux system. It's something beyond my control.

Can you at least run a FreeBSD build instead of a Linux one?
---
þ Synchronet þ The future of BBSing

Re: Re: File Request question
By: Digital Man to Tanausu M. on Mon Dec 29 2025 13:33:54

Re: Re: File Request question
By: Tanausu M. to Digital Man on Mon Dec 29 2025 06:53 pm

What I've done is create a script, and it seems to avoid that bug. Does anyone know where the bug is? I'll have to compile the master branch to see if it disappears and saves me all this trouble.

Sorry for filling up the message with all of the following.

sbbsecho.log

2025-12-29 18:24:22 NetMail (1.msg) created from Tanausu Martin (2:341/207) to Jeff Earle (1:229/700), attr: 0983 (PRIVATE, CRASH, KILLSENT, LOCAL, FREQ), subject: FR:AP251228.ZIP

The "FR:" isn't supposed to actually be part of the subject stored in the message header. If you include the "FR:" prefix in a netmail subject that you enter from within Synchronet (the terminal server), it'll strip the "FR:" prefix and add the FREQ attribute. This message you're showing has both the FREQ attribute *and* the "FR:" prefix in the subject. That's not correct.

Sorry for the inconvenience, I've already fixed part of that error, a couple more, and now I'm receiving files in the nonsecure folder.

/sbbs/fido/nonsecure $ ls
agoranet.zip

---
þ Synchronet þ Citrick BBS

Re: Re: File Request question
By: Deuce to Tanausu M. on Tue Dec 30 2025 03:31:43

Re: Re: File Request question
By: Tanausu M. to Digital Man on Mon Dec 29 2025 06:53 pm

Hello. I've also provided little to no information. I'm currently using what I believe is one of the latest versions of dailybuild_linux_x64, but with FreeBSD 15. I don't know if the master branch would change anything regarding that minor bug.
Currently, I can't switch the server to another Linux system. It's something beyond my control.

Can you at least run a FreeBSD build instead of a Linux one?

Hi. The version I had was compiled from the dailybuild_linux-x64 branch. I switched to the master branch, but the error persisted. I was finally able to fix it with the JavaScript script.

---
þ Synchronet þ Citrick BBS