Not sure if this would work or not...but used Al's...a sample CFG file &
one I found on another website. Please feel free to tell me what needs to be changed/added.

# Number @ end is the root zone
domain fsxnet d:\fe\outbound\fsx_out 21
domain wwivftn d:\fe\outbound\wwiv_out 11
domain scinet d:\fe\outbound\sci_out 77
domain spooknet d:\fe\outbound\spook_out 700
domain micronet d:\fe\outbound\micro_out 618
domain fidonet d:\fe\outbound\fido_out 1
domain vkradio d:\fe\outbound\vk_out 432
domain amiganet d:\fe\outbound\amiga_out 39

# Our Addresses
address 21:1/147@fsxnet
address 11:1/223@wwivftn
address 77:1/129@scinet
address 700:100/70@spooknet
address 618:300/32@micronet
address 1:340/1000@fidonet
address 432:1/145@vkradio
address 39:905/103@amiganet

sysname "ACME BBS"
location "Albany, Oregon"
sysop "Phoobar"

nodeinfo 115200,CM,IBN
try 10
hold 600
send-if-pwd

log d:\binkd\binkd.log
loglevel 4
conlog 4
percents
printq
backresolv

inbound d:\fe\inbound\fsx_in
inbound d:\fe\inbound\wwiv_in
inbound d:\fe\inbound\sci_in
inbound d:\fe\inbound\spook_in
inbound d:\fe\inbound\micro_in
inbound d:\fe\inbound\fido_in
inbound d:\fe\inbound\vk_in
inbound d:\fe\inbound\amiga_in
temp-inbound d:\fe\tinbound\fsx_in_temp
temp-inbound d:\fe\tinbound\wwiv_in_temp
temp-inbound d:\fe\tinbound\sci_in_temp
temp-inbound d:\fe\tinbound\spook_in_temp
temp-inbound d:\fe\tinbound\micro_in_temp
temp-inbound d:\fe\tinbound\fido_in_temp
temp-inbound d:\fe\tinbound\vk_in_temp
temp-inbound d:\fe\tinbound\amiga_in_temp

minfree 2048
minfree-nonsecure 2048

kill-dup-partial-files
kill-old-partial-files 86400

prescan

# HUBS
node 21:2/100@fsxnet -md ipv4.error404bbs.ddns.net:24555 ******** c
node 11:1/100@wwivftn -md ipv4.bbs.weather-station.org:24555 ******** c
node 77:1/100@scinet -md ipv4.bbs.diskshop.ca ******** c
node 700:100/70@spooknet -md ipv4.echo.phatstar.org ******** c
node 618:300/32@micronet -md ipv4.realitycheckbbs.org ******** c
node 3:770/1@fidonet -md ipv4.agency.bbs.nz ******** c
node 432:1/100@vkradio -md ipv4.bridge.vkradio.com ******** c
node 39:905/0@amiganet -md ipv4.bbs.diskshop.ca ******** c


# our listening port (default=24554)
# use a different port for basic added security-ish (e.g. avoid generic scans) # iport 54554

pid-file d:\binkd\binkd.pid

# touch a watch file when files are received to kick of toss
flag d:\fe\inbound\toss!.now *.su? *.mo? *.tu? *.we? *.th? *.fr? *.sa? *.pkt *.tic

# nuke old .bsy/.csy files after 12 hours
kill-old-bsy 12h

ACME BBS-Member of fsxNet/WWIVNet/SciNet/AmigaNet/VKRadio/FidoNet/MicroNet.

--- Mystic BBS v1.12 A46 2020/04/21 (Windows/32)
* Origin: ACME BBS-W.Coyote & D.Brown are our best users. (1:340/1000)

Hello Don,

Not sure if this would work or not...but used Al's...a sample CFG file
& one I found on another website. Please feel free to tell me what
needs to be changed/added.

# Number @ end is the root zone
domain fsxnet d:\fe\outbound\fsx_out 21
domain wwivftn d:\fe\outbound\wwiv_out 11
domain scinet d:\fe\outbound\sci_out 77
domain spooknet d:\fe\outbound\spook_out 700
domain micronet d:\fe\outbound\micro_out 618
domain fidonet d:\fe\outbound\fido_out 1
domain vkradio d:\fe\outbound\vk_out 432
domain amiganet d:\fe\outbound\amiga_out 39

My tosser is not 5D so I have my zone listed as 1 for all my domain lines and they all point to a single outbound, something like this..

domain fidonet d:\\fe\\outbound 1
domain fsxnet d:\\fe\\outbound 1

Also, I think you'll need to escape those paths in the OS/2 or windows version like so.

d:\\fe\\outbound

inbound d:\fe\inbound\fsx_in
inbound d:\fe\inbound\wwiv_in

I also just have one inbound..

inbound d:\\fe\\inbound
inbound-nonsecure d:\\fe\\inbound\\insecure
inbound-temp d:\\fe\\inbound\temp


Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hello Don,

inbound-temp d:\\fe\\inbound\temp

That should be..

temp-inbound d:\\fe\\inbound\\temp

or what ever the directory you use actually is.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Re: Worked on this earlier after work this evening...
By: Don Lowery to All on Sat May 02 2020 10:06 pm

Not sure if this would work or not...but used Al's...a sample CFG file & one I found on another website. Please feel free to tell me what needs to be changed/added.
# Number @ end is the root zone
domain fsxnet d:\fe\outbound\fsx_out 21
domain wwivftn d:\fe\outbound\wwiv_out 11

...

inbound d:\fe\inbound\fsx_in
inbound d:\fe\inbound\wwiv_in

So your domain statements are a little different to mine. I guess it might depend on how your tosser is configured, and if it is tossing packets into those locations.

Mine is setup with 1 inbound and 1 outbound, and the number at the end of the domain statements is not the zone name for the network, but the zone of the root outbound directory.

IE: I have
domain private /fido/mailer/out 10
domain fsxnet /fido/mailer/out 10
...
inbound /fido/mailer/in

(1 inbound definition, and multiple domain definitions for each network, but all end in 10, since it is my "default" zone.)

Thus, my toss (hpt) is configured to look for inbound in /fido/mailer/in, and the outbound is configured as /fido/mailer/out.

I have 8 networks configured and mail flows well ;)
...ëîåã

... If you can't learn to do it well, learn to enjoy doing it badly.
--- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)

02 May 20 22:06, you wrote to All:

Not sure if this would work or not...but used Al's...a sample CFG file
& one I found on another website. Please feel free to tell me what
needs to be changed/added.

inbound d:\fe\inbound\fsx_in
inbound d:\fe\inbound\wwiv_in
inbound d:\fe\inbound\sci_in

[...]

temp-inbound d:\fe\tinbound\fsx_in_temp
temp-inbound d:\fe\tinbound\wwiv_in_temp
temp-inbound d:\fe\tinbound\sci_in_temp

[...]

This won't work. There is only one inbound, one temp-inbound and one inbound-nonsecure. It's possible to define an ibox for a node though.


* Origin: kakistocracy (2:280/464.47)

Re: Worked on this earlier after work this evening...
By: Don Lowery to All on Sat May 02 2020 22:06:24

# Number @ end is the root zone
domain fsxnet d:\fe\outbound\fsx_out 21
domain wwivftn d:\fe\outbound\wwiv_out 11
domain scinet d:\fe\outbound\sci_out 77
domain spooknet d:\fe\outbound\spook_out 700
domain micronet d:\fe\outbound\micro_out 618
domain fidonet d:\fe\outbound\fido_out 1
domain vkradio d:\fe\outbound\vk_out 432
domain amiganet d:\fe\outbound\amiga_out 39

the above is for full 5D BSO... if your tosser is not also full 5D, it will not work properly...

if your tosser is only 4D BSO, then all the above paths need to be the same with the zones as you have specified... most FTN mail tossers are only 4D capable...

if your tosser uses the other form of 5D BSO, then the paths can be like you have them but the zones all have to be 1 so the directories get the hex extension added to them...


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

On 05-03-20 08:12, mark lewis wrote to Don Lowery <=-

Re: Worked on this earlier after work this evening...
By: Don Lowery to All on Sat May 02 2020 22:06:24

# Number @ end is the root zone
domain fsxnet d:\fe\outbound\fsx_out 21
domain wwivftn d:\fe\outbound\wwiv_out 11
domain scinet d:\fe\outbound\sci_out 77
domain spooknet d:\fe\outbound\spook_out 700
domain micronet d:\fe\outbound\micro_out 618
domain fidonet d:\fe\outbound\fido_out 1
domain vkradio d:\fe\outbound\vk_out 432
domain amiganet d:\fe\outbound\amiga_out 39

the above is for full 5D BSO... if your tosser is not also full 5D, it will not work properly...

I'm yet to see a tosser that works with the above config.

if your tosser is only 4D BSO, then all the above paths need to be the same with the zones as you have specified... most FTN mail tossers are only 4D capable...

Actually, every 4D setup I've used has used the same zone default zone number as well for each domain, as well as the same outbound root, so in the above example, every domain would have something like:

domain fidonet d:\fe\outbound 1
domain wwivftn d:\fe\outbound 1
domain scinet d:\fe\outbound 1

etc.

if your tosser uses the other form of 5D BSO, then the paths can be
like you have them but the zones all have to be 1 so the directories
get the hex extension added to them...

This is for BSO format that both SBBSecho and Mystic (mutil) use.


... A visit to a strange place will bring fresh work.
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

Tony wrote (2020-05-04):

# Number @ end is the root zone
domain fsxnet d:\fe\outbound\fsx_out 21
domain wwivftn d:\fe\outbound\wwiv_out 11
domain scinet d:\fe\outbound\sci_out 77
domain spooknet d:\fe\outbound\spook_out 700
domain micronet d:\fe\outbound\micro_out 618
domain fidonet d:\fe\outbound\fido_out 1
domain vkradio d:\fe\outbound\vk_out 432
domain amiganet d:\fe\outbound\amiga_out 39

the above is for full 5D BSO... if your tosser is not also full 5D,
it will not work properly...

I'm yet to see a tosser that works with the above config.

Squish, Crashmail II, Fastecho and others do support 5D, but not the binkd-style that omits the zone number for the default zone (in this configuration). Of course no tosser supports that, because according to the standard there is only one global default zone.

ASO and fileboxes work fine.

---
* Origin: (2:280/464.47)

Re: Re: Worked on this earlier after work this evening...
By: Tony Langdon to mark lewis on Mon May 04 2020 08:47:00

the above is for full 5D BSO... if your tosser is not also full
5D, it will not work properly...

I'm yet to see a tosser that works with the above config.

me either, really...

if your tosser is only 4D BSO, then all the above paths need to

be the same with the zones as you have specified... most FTN mail
tossers are only 4D capable...

Actually, every 4D setup I've used has used the same zone default
zone number as well for each domain, as well as the same outbound
root, so in the above example, every domain would have something
like:

domain fidonet d:\fe\outbound 1
domain wwivftn d:\fe\outbound 1
domain scinet d:\fe\outbound 1

yes but then you cannot be in two FTNs that used the same zone and there are several of those out there...

if your tosser uses the other form of 5D BSO, then the paths can be
like you have them but the zones all have to be 1 so the directories
get the hex extension added to them...

This is for BSO format that both SBBSecho and Mystic (mutil) use.

if i'm reading this correctly, then yes... see here for the (almost) current domain setup my binkd is using to work with sbbsecho...

https://paste.linux-help.org/view/07b043b2

i need to move it to a git repo, though... then i can more easily work with updates to it but there's only been one update, a dns lookup entry for one net, since i put it up...


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

Re: Worked on this earlier after work this evening...
By: Oli to Tony Langdon on Mon May 04 2020 09:59:22

Squish, Crashmail II, Fastecho and others do support 5D, but not the binkd-style that omits the zone number for the default zone (in this configuration). Of course no tosser supports that, because according
to the standard there is only one global default zone.

here we go again... which standard? the one you tried to point to the last time was written after the time you think/thought it was written... you never responded to my post pointing that out...

then there's the fact that the standard could be wrong or simply out of date... the FTSC documents current practise so if the practise changes, then the standard will also change...


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

mark wrote (2020-05-04):

Re: Worked on this earlier after work this evening...
By: Oli to Tony Langdon on Mon May 04 2020 09:59:22

Squish, Crashmail II, Fastecho and others do support 5D, but not
the binkd-style that omits the zone number for the default zone
(in this configuration). Of course no tosser supports that,
because according to the standard there is only one global default
zone.

here we go again... which standard? the one you tried to point to the
last time was written after the time you think/thought it was written... you never responded to my post pointing that out...

then there's the fact that the standard could be wrong or simply out of date... the FTSC documents current practise so if the practise changes, then the standard will also change...

If you are unable to read the documents at ftsc.org, I will not waste my time anymore.

You are a member of the FTSC since when?

---
* Origin: (2:280/464.47)

Re: Worked on this earlier after work this evening...
By: Oli to mark lewis on Mon May 04 2020 13:34:55

If you are unable to read the documents at ftsc.org, I will not waste my

time anymore.

good... maybe also stop spewing incorrect information?

i've read the documents and know what they say... i can also easily look at the dates on them which you apparently cannot do... the fact is that what you are pointing to as a standard was written *after* the tools under discussion... that means there was no standard for those tools to adhere to... plus the fact that documented standards change and it is quite easy for a tool that once was standards complient to no longer be standards complient... especially if it is not updated any more...

You are a member of the FTSC since when?

longer than you've been around ;)


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

mark wrote (2020-05-04):

Re: Worked on this earlier after work this evening...
By: Oli to mark lewis on Mon May 04 2020 13:34:55

If you are unable to read the documents at ftsc.org, I will not
waste my time anymore.

good... maybe also stop spewing incorrect information?

bla bla ...

i've read the documents and know what they say... i can also easily look at the dates on them which you apparently cannot do... the fact is that what you are pointing to as a standard was written *after* the tools
under discussion... that means there was no standard for those tools to adhere to... plus the fact that documented standards change and it is quite easy for a tool that once was standards complient to no longer be standards complient... especially if it is not updated any more...

You can try to spin it again and again. I already quoted the BinkleyTerm documentation from 1990. But I do it again for you:

"Note that outbound areas for domains other than your own will ALWAYS have a zone extension."

You are a member of the FTSC since when?

longer than you've been around ;)

You didn't learn much.

Since I started using it in 1993 the 5D BSO format hasn't changed. Only binkd invented it's own thing.

If this is all wrong, please update the FTS document.

---
* Origin: (2:280/464.47)

On 05-04-20 09:59, Oli wrote to Tony Langdon <=-

I'm yet to see a tosser that works with the above config.

Squish, Crashmail II, Fastecho and others do support 5D, but not the binkd-style that omits the zone number for the default zone (in this configuration). Of course no tosser supports that, because according to the standard there is only one global default zone.

Yeah all the working setups I've seen include the hex suffix for all 5D outbound zones except the main AKA's default.

ASO and fileboxes work fine.

I've never used ASO, but it does look like a better setup.


... And, best of all, Fido people are the best of all!
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

Re: Worked on this earlier after work this evening...
By: Oli to mark lewis on Mon May 04 2020 14:16:40

i've read the documents and know what they say... i can also easily
look at the dates on them which you apparently cannot do... the fact
is that what you are pointing to as a standard was written *after*
the tools under discussion... that means there was no standard for
those tools to adhere to... plus the fact that documented standards
change and it is quite easy for a tool that once was standards
complient to no longer be standards complient... especially if it is
not updated any more...

You can try to spin it again and again.

no spin... not even trying or wanting to...

I already quoted the BinkleyTerm documentation from 1990. But I do
it again for you:

"Note that outbound areas for domains other than your own will
ALWAYS have a zone extension."

1. the binkleyterm documentation is *NOT* the standards document...

2. if i am a member of zones 1 (fidonet) and 42 (fubarnet), then going
by the above single line taken out of context, the domain for z42
(fubarnet) is my domain as well as the one for zone 1 (fidonet)...
thus the outbound for z42 (fubnarnet) would *NOT* have the extension
(.02a) added...

thanks for playing!


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

domain amiganet d:\fe\outbound\amiga_out 39

My tosser is not 5D so I have my zone listed as 1 for all my domain
lines and they all point to a single outbound, something like this.. domain fidonet d:\\fe\\outbound 1
domain fsxnet d:\\fe\\outbound 1

That was my 1st question when I started putting this together.

Also, I think you'll need to escape those paths in the OS/2 or windows version like so.
d:\\fe\\outbound

Have seen this happen just a time or two before while working with Mystic. Am going to get it changed out.

inbound d:\fe\inbound\wwiv_in

I also just have one inbound..
inbound d:\\fe\\inbound
inbound-nonsecure d:\\fe\\inbound\\insecure
inbound-temp d:\\fe\\inbound\temp

This was something else I was wondering about. As Picard says...will make it so.

Again...thank you so much for the help/suggestions. Everything helps!

ACME BBS-Member of fsxNet/WWIVNet/SciNet/AmigaNet/VKRadio/FidoNet/MicroNet.

--- Mystic BBS v1.12 A46 2020/04/21 (Windows/32)
* Origin: ACME BBS-W.Coyote & D.Brown are our best users. (1:340/1000)

inbound-temp d:\\fe\\inbound\temp

That should be..
temp-inbound d:\\fe\\inbound\\temp

I caught that one & made a note on the printed copy I made.

ACME BBS-Member of fsxNet/WWIVNet/SciNet/AmigaNet/VKRadio/FidoNet/MicroNet.

--- Mystic BBS v1.12 A46 2020/04/21 (Windows/32)
* Origin: ACME BBS-W.Coyote & D.Brown are our best users. (1:340/1000)

domain wwivftn d:\fe\outbound\wwiv_out 11
inbound d:\fe\inbound\fsx_in
inbound d:\fe\inbound\wwiv_in

So your domain statements are a little different to mine. I guess it
might depend on how your tosser is configured, and if it is tossing packets into those locations.

Was putting this together in Windows 10 to use in OS/2-ArcaOS with at 2 different cfg's from different open to put this together. That's why it may look so strange.

Al mentioned that I needed just 1 location for many of these...rather than seperate locations.

Mine is setup with 1 inbound and 1 outbound, and the number at the end
of the domain statements is not the zone name for the network, but the zone of the root outbound directory.
domain private /fido/mailer/out 10
domain fsxnet /fido/mailer/out 10
inbound /fido/mailer/in
(1 inbound definition, and multiple domain definitions for each network, but all end in 10, since it is my "default" zone.)

That was another misunderstanding I had that yourself & Al mentioned.

Thus, my toss (hpt) is configured to look for inbound in
/fido/mailer/in, and the outbound is configured as /fido/mailer/out.
I have 8 networks configured and mail flows well ;)

Have the same amount of networks.

Thank you for all your help. When it's explained...it makes sense.

ACME BBS-Member of fsxNet/WWIVNet/SciNet/AmigaNet/VKRadio/FidoNet/MicroNet.

--- Mystic BBS v1.12 A46 2020/04/21 (Windows/32)
* Origin: ACME BBS-W.Coyote & D.Brown are our best users. (1:340/1000)

inbound d:\fe\inbound\sci_in
temp-inbound d:\fe\tinbound\fsx_in_temp
temp-inbound d:\fe\tinbound\wwiv_in_temp

This won't work. There is only one inbound, one temp-inbound and one inbound-nonsecure. It's possible to define an ibox for a node though.

This was something which was nagging me as I was putting this together. With about 3 different sources I was using...attempted to do the best one.

Thank you again for the help! Knowing there is help out there really helps
when there's stuff I don't know.

ACME BBS-Member of fsxNet/WWIVNet/SciNet/AmigaNet/VKRadio/FidoNet/MicroNet.

--- Mystic BBS v1.12 A46 2020/04/21 (Windows/32)
* Origin: ACME BBS-W.Coyote & D.Brown are our best users. (1:340/1000)

domain amiganet d:\fe\outbound\amiga_out 39

the above is for full 5D BSO... if your tosser is not also full 5D, it will not
work properly...
if your tosser is only 4D BSO, then all the above paths need to be the same with the zones as you have specified... most FTN mail tossers are only 4D capable...

My tosser is FastEcho/2 1.60...so don't expect it to be 5D. Al/Oli & others have mentioned this so am going to make the changes...especially that much of my software is roughly about 20 years old because OS/2-ArcaOS is the OS I'm using as a host.

if your tosser uses the other form of 5D BSO, then the paths can be like you have them but the zones all have to be 1 so the directories get the hex extension added to them...

Will be making the changes. When I do...will repost what I have done. Hopefully...it will help out anyone else who is trying to do what I am.

Thank you for your help! Am so relieved there is help out there without
making someone feel bad without the knowledge/experince all of you have.

ACME BBS-Member of fsxNet/WWIVNet/SciNet/AmigaNet/VKRadio/FidoNet/MicroNet.

--- Mystic BBS v1.12 A46 2020/04/21 (Windows/32)
* Origin: ACME BBS-W.Coyote & D.Brown are our best users. (1:340/1000)

the above is for full 5D BSO... if your tosser is not also full 5D, will not work properly...

I'm yet to see a tosser that works with the above config.

Understand what you were talking about in fsxNet. Was a little confused on
what you were talking about without an example. Seeing it as a visual learner...I understand now.

Actually, every 4D setup I've used has used the same zone default zone number as well for each domain, as well as the same outbound root, so in the above example, every domain would have something like:
domain fidonet d:\fe\outbound 1
domain wwivftn d:\fe\outbound 1
domain scinet d:\fe\outbound 1

I'm feeling pretty good about getting this going with having seen it put together.

Thank you for all your help!

ACME BBS-Member of fsxNet/WWIVNet/SciNet/AmigaNet/VKRadio/FidoNet/MicroNet.

--- Mystic BBS v1.12 A46 2020/04/21 (Windows/32)
* Origin: ACME BBS-W.Coyote & D.Brown are our best users. (1:340/1000)

You can try to spin it again and again. I already quoted the BinkleyTerm

docum

tation from 1990. But I do it again for you:

"Note that outbound areas for domains other than your own will ALWAYS have a zo
e extension."

[...snip...]

Since I started using it in 1993 the 5D BSO format hasn't changed. Only

binkd

vented it's own thing.

I have both BT and binkd installed on the same machine here. Both of them
use the same format for my outbounds, by default. I do not have to specify
the zone extension for each zone's outbound in either config file, and shouldn't unless I want to break something.

I can tell you that binkd is using the same format that BinkleyTerm is
using... the zone extension, in HEX.

Mike


* SLMR 2.1a * This just in: Research causes cancer in rats!
--- SBBSecho 3.11-Linux
* Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)

On 05-04-20 06:52, mark lewis wrote to Tony Langdon <=-

Re: Re: Worked on this earlier after work this evening...
By: Tony Langdon to mark lewis on Mon May 04 2020 08:47:00

the above is for full 5D BSO... if your tosser is not also full
5D, it will not work properly...

I'm yet to see a tosser that works with the above config.

me either, really...

if your tosser is only 4D BSO, then all the above paths need to

be the same with the zones as you have specified... most FTN mail
tossers are only 4D capable...

Actually, every 4D setup I've used has used the same zone default
zone number as well for each domain, as well as the same outbound
root, so in the above example, every domain would have something
like:

domain fidonet d:\fe\outbound 1
domain wwivftn d:\fe\outbound 1
domain scinet d:\fe\outbound 1

yes but then you cannot be in two FTNs that used the same zone and
there are several of those out there...

Well that's the problem 5D is supposed to solve, but not all implementations can do that yet. For example, SBBSecho uses a domain to zone mapping that appears to be 1-1, which I'm not sure could handle 2 domains with the same zone.

if your tosser uses the other form of 5D BSO, then the paths can be
like you have them but the zones all have to be 1 so the directories
get the hex extension added to them...

This is for BSO format that both SBBSecho and Mystic (mutil) use.

if i'm reading this correctly, then yes... see here for the (almost) current domain setup my binkd is using to work with sbbsecho...

https://paste.linux-help.org/view/07b043b2

Yep that's what I'm talking about. :)

i need to move it to a git repo, though... then i can more easily work with updates to it but there's only been one update, a dns lookup entry for one net, since i put it up...

So all of those nets are active?


... Relax. It's only ones and zeroes.
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

On 05-04-20 11:40, Don Lowery wrote to Tony Langdon <=-

the above is for full 5D BSO... if your tosser is not also full 5D, will not work properly...

I'm yet to see a tosser that works with the above config.

Understand what you were talking about in fsxNet. Was a little confused
on what you were talking about without an example. Seeing it as a
visual learner...I understand now.

Cool. Examples can help. :)

I'm feeling pretty good about getting this going with having seen it
put together.

Thank you for all your help!

You're welcome! :)


... This is abuse, arguments are down the hall.
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

Re: Re: Worked on this earlier after work this evening...
By: Tony Langdon to mark lewis on Tue May 05 2020 18:01:00

domain fidonet d:\fe\outbound 1
domain wwivftn d:\fe\outbound 1
domain scinet d:\fe\outbound 1

yes but then you cannot be in two FTNs that used the same zone and
there are several of those out there...

Well that's the problem 5D is supposed to solve, but not all implementations can do that yet. For example, SBBSecho uses a
domain to zone mapping that appears to be 1-1, which I'm not sure
could handle 2 domains with the same zone.

exactly... unless you use the format i linked to earlier (link quoted below)...

if your tosser uses the other form of 5D BSO, then the paths can be
like you have them but the zones all have to be 1 so the directories
get the hex extension added to them...

This is for BSO format that both SBBSecho and Mystic (mutil) use.

if i'm reading this correctly, then yes... see here for the (almost) current domain setup my binkd is using to work with sbbsecho...

https://paste.linux-help.org/view/07b043b2

Yep that's what I'm talking about. :)

yes, it is part of my work on trying to see what is necessary for sbbsecho to be fully 5D complient... there are some problems due to some 4D assumptions but they are easily worked around... i just need to find more time to dig deeper into the code and see what fixes are needed...

i need to move it to a git repo, though... then i can more easily
work with updates to it but there's only been one update, a dns
lookup entry for one net, since i put it up...

So all of those nets are active?

i don't know... the list is gleaned from my mailers' logs by scanning for the FTN addresses and domains presented by other mailers when we connect... that data is then run through a series of linux tools to trim it down and create a raw list... that raw list is then manually tweaked into the final result currently being used by my binkd... that raw list is also used to create the proper 5D domain directories in my base BSO directory... i've also added the gathered domains and zones to my tosser's configuration using its defined ini format so BinkIt.js should also be using them when i use BinkIt.js as my mailer...


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

On 05-05-20 08:32, mark lewis wrote to Tony Langdon <=-

Re: Re: Worked on this earlier after work this evening...
By: Tony Langdon to mark lewis on Tue May 05 2020 18:01:00

domain fidonet d:\fe\outbound 1
domain wwivftn d:\fe\outbound 1
domain scinet d:\fe\outbound 1

yes but then you cannot be in two FTNs that used the same zone and
there are several of those out there...

Well that's the problem 5D is supposed to solve, but not all implementations can do that yet. For example, SBBSecho uses a
domain to zone mapping that appears to be 1-1, which I'm not sure
could handle 2 domains with the same zone.

exactly... unless you use the format i linked to earlier (link quoted below)...

Umm, how does that help when a tosser has a 1-1 zone-domain mapping? The issue
here is in the tosser being able to infer the right zone from what is effectively a 4D addressing scheme internally. I'm specifically thinking of SBBSecho here. the ftndomains.ini file describes zone to domains mappings, but
in a true 5D environment, anything's possible, and a truly 5D aware tosser shouldn't assume any relationships between zones and domains, other than being explicitly told the zones for each domain.

if your tosser uses the other form of 5D BSO, then the paths can be
like you have them but the zones all have to be 1 so the directories
get the hex extension added to them...

This is for BSO format that both SBBSecho and Mystic (mutil) use.

if i'm reading this correctly, then yes... see here for the (almost)

current domain setup my binkd is using to work with sbbsecho...

https://paste.linux-help.org/view/07b043b2

Yep that's what I'm talking about. :)

yes, it is part of my work on trying to see what is necessary for
sbbsecho to be fully 5D complient... there are some problems due to
some 4D assumptions but they are easily worked around... i just need to find more time to dig deeper into the code and see what fixes are needed...

The question here is what do you see SBBSecho needs? To me, it looks like SBBSecho is actually 4D internally, and a simple translation table is used to map zones to domains, but there's an obvious flaw - if two domains have the same zone, how does SBBSecho know what is what? Anyway, my binkd config is a smaller version of that - using the domains I am connected to, and a default zone of 3, rather than 1.

i need to move it to a git repo, though... then i can more easily
work with updates to it but there's only been one update, a dns
lookup entry for one net, since i put it up...

So all of those nets are active?

i don't know... the list is gleaned from my mailers' logs by scanning
for the FTN addresses and domains presented by other mailers when we connect... that data is then run through a series of linux tools to

Reason I'm asking is there's some not in NuSkooler's Google sheet, so looks like someone will need to update the sheet. :)

trim it down and create a raw list... that raw list is then manually tweaked into the final result currently being used by my binkd... that
raw list is also used to create the proper 5D domain directories in my base BSO directory... i've also added the gathered domains and zones to
my tosser's configuration using its defined ini format so BinkIt.js
should also be using them when i use BinkIt.js as my mailer...

Well, you won't get all the domains I'm connected to anymore, I now have so many AKAs that I have to use hide-aka and present-aka judiciously to make sure my links work! :)

)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

... Look closely at the most embarrassing details and amplify them
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

Dumas wrote (2020-05-04):

You can try to spin it again and again. I already quoted the
BinkleyTerm docum tation from 1990. But I do it again for you:

"Note that outbound areas for domains other than your own will ALWAYS
have a zo e extension."

[...snip...]

Since I started using it in 1993 the 5D BSO format hasn't changed. Only
binkd vented it's own thing.

I have both BT and binkd installed on the same machine here. Both of

them

use the same format for my outbounds, by default. I do not have to specify the zone extension for each zone's outbound in either config
file, and shouldn't unless I want to break something.

I can tell you that binkd is using the same format that BinkleyTerm is using... the zone extension, in HEX.

how do your outbound directories look like? what's the outbound config in binkd.cfg?

---
* Origin: (2:280/464.47)