Heya DM.

I was just testing out SRIF/FREQ with Synchronet's netmail functionality, and I'm noticing an issue again with BSO-specific handling.

When sending a Netmail to anything@ZONE:NET/NODE, using FR: somename for the subject, as documented, sbbsecho packs it up like arcmail style, despite being configured for Binkley BSO style.

The way BinkD, for example, handles file requests is by having a specially named hexnetnode.req file being the contents of what's being requested. When SBBSEcho is configured for BSO, it packs it up just as-if it were a regular netmail. I know this because I'm looking at the *.msg it exports (and isn't deleted due to a prior bug/fix already resolved), and it's got the flags Frq on it, just like attachmail would be done, thus gets packed up, and sent as an .out file, which BinkD will take and import as netmail for whomever it is destined for.

)))[Psi-Jack -//- Decker]

---
þ Synchronet þ Decker's Heaven -//- bbs.deckersheaven.com

Re: FREQing with Synchronet
By: Psi-Jack to Digital Man on Sun Sep 06 2015 02:30 am

Heya DM.

I was just testing out SRIF/FREQ with Synchronet's netmail functionality, and I'm noticing an issue again with BSO-specific handling.

When sending a Netmail to anything@ZONE:NET/NODE, using FR: somename for the subject, as documented, sbbsecho packs it up like arcmail style, despite being configured for Binkley BSO style.

The way BinkD, for example, handles file requests is by having a specially named hexnetnode.req file being the contents of what's being requested. When SBBSEcho is configured for BSO, it packs it up just as-if it were a regular netmail. I know this because I'm looking at the *.msg it exports (and isn't deleted due to a prior bug/fix already resolved), and it's got the flags Frq on it, just like attachmail would be done, thus gets packed up, and sent as an .out file, which BinkD will take and import as netmail for whomever it is destined for.

I'll look into. I've never heard of this .req file before.

digital man

Synchronet "Real Fact" #13:
SBBSecho was originally written by Allen Christiansen (King Drafus) in 1994. Norco, CA WX: 74.0øF, 50.0% humidity, 1 mph SSE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Re: FREQing with Synchronet
By: Digital Man to Psi-Jack on Mon Sep 07 2015 12:00 am

Re: FREQing with Synchronet
By: Psi-Jack to Digital Man on Sun Sep 06 2015 02:30 am

Heya DM.

I was just testing out SRIF/FREQ with Synchronet's netmail
functionality, and I'm noticing an issue again with BSO-specific

handling.

When sending a Netmail to anything@ZONE:NET/NODE, using FR: somename
for the subject, as documented, sbbsecho packs it up like arcmail
style, despite being configured for Binkley BSO style.

The way BinkD, for example, handles file requests is by having a
specially named hexnetnode.req file being the contents of what's being
requested. When SBBSEcho is configured for BSO, it packs it up just
as-if it were a regular netmail. I know this because I'm looking at
the *.msg it exports (and isn't deleted due to a prior bug/fix already
resolved), and it's got the flags Frq on it, just like attachmail
would be done, thus gets packed up, and sent as an .out file, which
BinkD will take and import as netmail for whomever it is destined for.

I'll look into. I've never heard of this .req file before.

Ditto, neither had I, but it's been around apparently since 1995. It's a very simple file, in the format of:

<filename> [!<password>]

One file per line, optional password required, prefixed by an exclaimation
mark for the password. Then the poll file ?lo references that .req file with a ^/path/to/file.req, to delete it upon transmission.

This is for SRIF style file requests, to be specific, which is what IP mailers like BinkP use.

)))[Psi-Jack -//- Decker]

---
þ Synchronet þ Decker's Heaven -//- bbs.deckersheaven.com

Re: FREQing with Synchronet
By: Psi-Jack to Digital Man on Mon Sep 07 2015 12:21 pm

Re: FREQing with Synchronet
By: Digital Man to Psi-Jack on Mon Sep 07 2015 12:00 am

Re: FREQing with Synchronet
By: Psi-Jack to Digital Man on Sun Sep 06 2015 02:30 am

Heya DM.

I was just testing out SRIF/FREQ with Synchronet's netmail
functionality, and I'm noticing an issue again with BSO-specific handling.
When sending a Netmail to anything@ZONE:NET/NODE, using FR: somename
for the subject, as documented, sbbsecho packs it up like arcmail
style, despite being configured for Binkley BSO style.

The way BinkD, for example, handles file requests is by having a
specially named hexnetnode.req file being the contents of what's being
requested. When SBBSEcho is configured for BSO, it packs it up just
as-if it were a regular netmail. I know this because I'm looking at
the *.msg it exports (and isn't deleted due to a prior bug/fix already
resolved), and it's got the flags Frq on it, just like attachmail
would be done, thus gets packed up, and sent as an .out file, which
BinkD will take and import as netmail for whomever it is destined for.

I'll look into. I've never heard of this .req file before.

Ditto, neither had I, but it's been around apparently since 1995. It's a very simple file, in the format of:

<filename> [!<password>]

One file per line, optional password required, prefixed by an exclaimation mark for the password. Then the poll file ?lo references that .req file with a ^/path/to/file.req, to delete it upon transmission.

This is for SRIF style file requests, to be specific, which is what IP mailers like BinkP use.

Try rev 1.263 of SBBSecho (now in CVS). The documentation I found (BT-REF.TXT) doesn't mention the password, so I didn't add that. Let me know how it works for ya.

digital man

Synchronet "Real Fact" #48:
Synchronet program was named 'sbbs' instead of 'sync' to avoid conflict w/Unix. Norco, CA WX: 87.6øF, 45.0% humidity, 10 mph SE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

07 Sep 15 00:00, you wrote to Psi-Jack:

The way BinkD, for example, handles file requests is by having a
specially named hexnetnode.req file being the contents of what's being
requested. When SBBSEcho is configured for BSO, it packs it up just
as-if it were a regular netmail. I know this because I'm looking at the
*.msg it exports (and isn't deleted due to a prior bug/fix already
resolved), and it's got the flags Frq on it, just like attachmail would
be done, thus gets packed up, and sent as an .out file, which BinkD
will take and import as netmail for whomever it is destined for.

I'll look into. I've never heard of this .req file before.

it is the WaZOO FREQ protocol stuff from FTS-0006's YOOHOO and YOOHOO/2U2 protocol methods document... page 6 of FTS-0006.002 gives the file names used and pages 8-9 describe how it works...

FTS-0006 says that it covers the Opus-CBCS system method of netmail handshaking... IIRC, binkleyterm was fashioned after Opus-CBCS by the same author as FTS-0006 so it makes sense that the binkleyterm docs would contain some info about the .req files but maybe not all of it ;)

)\/(ark

... My other computer is an Osborne! ;*)
---
* Origin: (1:3634/12.73)
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net