Hi All,

After much reading I was able to add FSXNet ontop of Fidonet. My issue is that when I try to send netmail to another node BinkD is ignoring the message. I can
send netmail to my hub just fine. All netmail goes to outbound.015 and my hub creates files with the hex 00020064 and sends just fine, but if I try to send netmail to a different node through the hub it set the hex for that node such as 00010065 and puts it in the outbound.015 folder but just ignores it. I have tweaked the settings around several different ways such as Direct to YesLocal Address (AKA) set the hubs address in the route to... The binkd.conf has this in it
domain fidonet /sbbs/fido/outbound 1
domain fido alias-for fidonet
domain fidonet.org alias-for fidonet
address 1:19/25@fidonet
domain fsxnet /sbbs/fido/outbound 15
domain fsxnet.nz alias-for fsxnet
address 21:2/160@fsxnet
sysname "DarkAges BBS"
location "Wayne, OK"
sysop "Randy Henderson"
nodeinfo 115200,TCP,BINKP
---SNIP
node 21:2/100@fsxnet -md error404bbs.ddns.net:24555 MYPASS

My sbbsecho.ini

[node:21:2/100@fsxnet]
Name = Todd Zieman
Comment = My Hub
Archive = ZIP
PacketType = 2+
AreaFix = true
AreaFixPwd = MYPASS
SessionPwd = MYPASS
Passive = false
Direct = true
Notify = false
Status = Crash
LocalAddress = 21:2/160
BinkpHost = error404bbs.ddns.net
BinkpPort = 24555
BinkpPoll = true
BinkpPlainAuthOnly = false
BinkpAllowPlainAuth = false
BinkpAllowPlainText = true
BinkpTLS = false

[node:21:ALL]
Name =
Comment =
Archive = None
PacketType = 2+
PacketPwd =
AreaFix = false
AreaFixPwd =
SessionPwd =
TicFilePwd =
Inbox =
Outbox =
Passive = false
Direct = false
Notify = false
Keys =
Status = Normal
Route = 21:2/100
GroupHub =
BinkpHost =
BinkpPort = 24554
BinkpPoll = false
BinkpPlainAuthOnly = false
BinkpAllowPlainAuth = false
BinkpAllowPlainText = true
BinkpTLS = false
BinkpSourceAddress =

Thanks,
Gargoyle

---
þ Synchronet þ DarkAges BBS | darkagesbbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: SBBSECHO
By: Gargoyle to ALL on Tue Jan 28 2020 04:50 pm

Hi All,

After much reading I was able to add FSXNet ontop of Fidonet. My issue is that when I try to send netmail to another node BinkD is ignoring the message. I can send netmail to my hub just fine. All netmail goes to outbound.015 and my hub creates files with the hex 00020064 and sends just fine, but if I try to send a netmail to a different node through the hub it set the hex for that node such as 00010065 and puts it in the outbound.015 folder but just ignores it. I have tweaked the settings around several different ways such as Direct to YesLocal Address (AKA) set the hubs

address

in the route to... The binkd.conf has this in it
domain fidonet /sbbs/fido/outbound 1

When you say "my hub" and "the hub", are you referring to another system or your own?

To be clear, you can join multiple FTN networks (e.g. FidoNet and FSXnet) without running multiple mailers or tossers on your system.

digital man

Synchronet/BBS Terminology Definition #69:
SSL = Secure Sockets Layer (precursor to TLS)
Norco, CA WX: 71.6øF, 35.0% humidity, 9 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.10-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

I didn't mean to interchange those words, the hub I send to is what I was referring to in both instances. I am only running 1 mailer and 1 tosser. SO that why I have 2 entries in the binkd.conf

domain fidonet /sbbs/fido/outbound 1
domain fsxnet /sbbs/fido/outbound 15

I figured out the mail for fido goes in the outbound and mail for FSXNet goes in outbound.015 and binkd finds it in both places.

The netmail sends if I send it to my uplink (Host node) but if I send netmail to another system it puts it in the outbound.015 folder and ignores it......

My uplink 21:2/100 if I send netmail works
If I send netmail to 21:1/101 and it just sits there

I have 21:ALL in my echo config I tried setting route = Blank and route=21:2/100 thinking if I specifically told it to route through my uplink it
would make its way to it's final destination

I did notice that when I send netmail it names the file the hex code for the node I am sending to. I do have the current nodelist in the configuration as well. I assume it had to be there to find the systems I was sending netmail to.

Hope that clears it up somewhat.

Gargoyle

---
þ Synchronet þ DarkAges BBS | darkagesbbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: SBBSECHO
By: Gargoyle to Digital Man on Tue Jan 28 2020 10:12 pm

I didn't mean to interchange those words, the hub I send to is what I was referring to in both instances. I am only running 1 mailer and 1 tosser.

I guess it was this statement of yours that confused me:

"my hub creates files with the hex 00020064 and sends just fine" - if you're not running "my hub" how would know what files are created on the hub?

SO
that why I have 2 entries in the binkd.conf

domain fidonet /sbbs/fido/outbound 1
domain fsxnet /sbbs/fido/outbound 15

I figured out the mail for fido goes in the outbound and mail for FSXNet goes in outbound.015 and binkd finds it in both places.

The netmail sends if I send it to my uplink (Host node) but if I send netmail to another system it puts it in the outbound.015 folder and ignores it......

My uplink 21:2/100 if I send netmail works
If I send netmail to 21:1/101 and it just sits there

I have 21:ALL in my echo config I tried setting route = Blank and route=21:2/100 thinking if I specifically told it to route through my

uplink

it would make its way to it's final destination

Yes, routing through your hub would be the normal setup.

I did notice that when I send netmail it names the file the hex code for

the

node I am sending to. I do have the current nodelist in the configuration

as

well. I assume it had to be there to find the systems I was sending netmail to.

Hope that clears it up somewhat.

Perhaps this reference will help diagnose things more clearly for you: http://wiki.synchro.net/ref:fidonet_files

My guess is that your netmail is either on-hold for the node you've sent it to (and not being routed through your hub) or your binkd configuration doesn't know how to deliver the mail to that node (e.g. doesn't know how to find the nodelist and look-up the relevant IP address or hostname). Routing your netmail through your hub will resolve that issue.

digital man

This Is Spinal Tap quote #12:
Nigel Tufnel: Well, I don't know - wh-wh-... what're the hours?
Norco, CA WX: 63.7øF, 33.0% humidity, 6 mph NNE wind, 0.00 inches rain/24hrs --- SBBSecho 3.10-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Thanks for the suggestions.

Not on hold, set to crash - I agree it is not being routed through the hub BinkD doesn't have a path to send directly to that node, it should be routed through the hub
It can find the nodelist and it is up-to-date
I agree it needs to route through the hub - That's where I am stuck

Went through the fido_files document again, I had gone through it a couple of times before, still nothing glaring to me that I am missing

If I send netmail to the hub it works fine, netmail through the hub to another system within the network gets stuck, sbbsecho names files via hex (as what I understand it) for the entry in sbbsecho for the hub (00020064) it sends those files with that hex name, if I add any other netmail system (00010065) it uses a different hex and packs it up, just won't send.
In the linked nodes section 21:ALL is .015 which is how I figured out in binkd domain fsxnet /sbbs/fido/outbound 15 because all the mail for fsxnet goes in that outbound folder
So mail to 21:2/1000 is 00020064, it goes without a hitch. Mail to 21:1/101 hex
00010065 get dropped off in the .015 folder but the 00010065 never sends. So I 100% agree binkd doesn't know what to do with it I assumed that is where the 21:ALL comes in. All to zone 21 goes to the hub, or so I would think.

It is killing me that it is whipping me :-)

I more logs to post to see if it helps.

Here is an example of the netmail that gets stuck

2020-01-29 20:07:05 Created NetMail (1.msg) from Randy Henderson (21:2/160) to Paul Hayton (21:1/101), attr: 0183, subject: Netmail Test
2020-01-29 20:07:05 Packing NetMail (1.msg) from Randy Henderson (21:2/160) to Paul Hayton (21:1/101), attr: 0183, subject: Netmail Test
2020-01-29 20:07:05 Node (21:1/101) successfully locked via: /sbbs/fido/outbound.015/00010065.bsy
2020-01-29 20:07:05 Adding NetMail (1.msg) to new packet for 21:1/101: /sbbs/fido/outbound.015/00010065.cut
2020-01-29 20:07:05 Deleting /sbbs/netmail/1.msg (from line 5272)
2020-01-29 20:07:05 Touching outgoing semfile: ../data/binkout.now
2020-01-29 20:07:05 Deleting /sbbs/fido/outbound.015/00010065.bsy (from line 3020)
2020-01-29 20:07:05 Deleting /sbbs/ctrl/sbbsecho.bsy (from line 3026) 2020-01-29 20:07:05 SBBSecho (PID 28510) exiting with error level 0, NetMail(0 imported, 1 exported, 1 packed)

Here is an example of netmail that goes out just fine

2020-01-29 20:36:33 Created NetMail (1.msg) from Randy Henderson (21:2/160) to AREAFIX (21:2/100), attr: 0183, subject: ***
2020-01-29 20:36:33 Packing NetMail (1.msg) from Randy Henderson (21:2/160) to AREAFIX (21:2/100), attr: 0183, subject: ***
2020-01-29 20:36:33 Node (21:2/100) successfully locked via: /sbbs/fido/outbound.015/00020064.bsy
2020-01-29 20:36:33 Adding NetMail (1.msg) to new packet for 21:2/100: /sbbs/fido/outbound.015/00020064.cut
2020-01-29 20:36:33 Deleting /sbbs/netmail/1.msg (from line 5272)
2020-01-29 20:36:33 Touching outgoing semfile: ../data/binkout.now
2020-01-29 20:36:33 Deleting /sbbs/fido/outbound.015/00020064.bsy (from line 3020)
2020-01-29 20:36:33 Deleting /sbbs/ctrl/sbbsecho.bsy (from line 3026) 2020-01-29 20:36:33 SBBSecho (PID 28792) exiting with error level 0, NetMail(0 imported, 1 exported, 1 packed)

So both netmail messages go to /sbbs/fido/outbound.015
[root@bbs sbbs]# ls /sbbs/fido/outbound.015
00010065.cut 00020064.cut

Then the mailer kicks in

[root@bbs sbbs]# tail -25 /var/log/binkd.log
+ 29 Jan 20:37:30 [28800] call to 21:2/100@fsxnet
29 Jan 20:37:30 [28800] trying 71.74.66.9:24555...
29 Jan 20:37:30 [28800] connected
+ 29 Jan 20:37:30 [28800] outgoing session with cpe-71-74-66-9.insight.res.rr.com [71.74.66.9] (24555)
- 29 Jan 20:37:31 [28800] OPT CRAM-MD5-e21a04ebcddd1c5c825a1ecc89b66936
+ 29 Jan 20:37:31 [28800] Remote requests MD mode
- 29 Jan 20:37:31 [28800] SYS fsxNet [Net2] Tholian
- 29 Jan 20:37:31 [28800] ZYZ Todd Zieman - Solaris
- 29 Jan 20:37:31 [28800] TIME Wed, 29 Jan 2020 21:37:32 -0500
- 29 Jan 20:37:31 [28800] VER Mystic/1.12A43 binkp/1.0
- 29 Jan 20:37:31 [28800] BUILD 2019/03/03 01:36:15 Windows/64
+ 29 Jan 20:37:31 [28800] addr: 21:2/100@fsxnet
+ 29 Jan 20:37:31 [28800] pwd protected session (MD5)
+ 29 Jan 20:37:31 [28800] sending /sbbs/fido/outbound.015/00020064.cut as c65fd334.pkt (426)
- 29 Jan 20:37:31 [28800] QSIZE 1 files 17,629 bytes
- 29 Jan 20:37:31 [28800] receiving 0000ffc4.we2 (17629 byte(s), off 0)
+ 29 Jan 20:37:31 [28800] sent: /sbbs/fido/outbound.015/00020064.cut (426, 426.00 CPS, 21:2/100@fsxnet)
+ 29 Jan 20:37:31 [28800] 0000ffc4.we2 -> /sbbs/fido/inbound/0000ffc4.we2
29 Jan 20:37:31 [28800] got *.we?, delayed creating /sbbs/data/fidoin.now
29 Jan 20:37:31 [28800] got *.WE?, delayed creating /sbbs/data/fidoin.now
+ 29 Jan 20:37:31 [28800] rcvd: 0000ffc4.we2 (17629, 17629.00 CPS, 21:2/100@fsxnet)
+ 29 Jan 20:37:32 [28800] done (to 21:2/100@fsxnet, OK, S/R: 1/1 (426/17629 bytes))
29 Jan 20:37:32 [28800] Creating /sbbs/data/fidoin.now
29 Jan 20:37:32 [28800] session closed, quitting...
29 Jan 20:37:32 [28182] rc(28800)=0

The log indicates it only sent the one netmail message, the netmail to Paul i.e. 00010065.cut was not sent

[root@bbs sbbs]# ls /sbbs/fido/outbound.015
00010065.cut 00020064.try

Thanks,

Gargoyle
DakrkAges BBS Wayne, OK
darkagesbbs.com

---
þ Synchronet þ DarkAges BBS | darkagesbbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: SBBSECHO
By: Gargoyle to Digital Man on Wed Jan 29 2020 08:53 pm

Thanks for the suggestions.

Not on hold, set to crash - I agree it is not being routed through the hub BinkD doesn't have a path to send directly to that node, it should be

routed

through the hub
It can find the nodelist and it is up-to-date
I agree it needs to route through the hub - That's where I am stuck

If you're routing the netmail, you don't really need a nodelist then. I haven't used in a nodelist in 25 years.

Went through the fido_files document again, I had gone through it a couple of times before, still nothing glaring to me that I am missing

If I send netmail to the hub it works fine, netmail through the hub to another system within the network gets stuck, sbbsecho names files via hex (as what I understand it) for the entry in sbbsecho for the hub (00020064) it sends those files with that hex name, if I add any other netmail system (00010065) it uses a different hex and packs it up, just won't send.

Then the netmail isn't being routed.

In the linked nodes section 21:ALL is .015 which is how I figured out in binkd domain fsxnet /sbbs/fido/outbound 15 because all the mail for fsxnet goes in that outbound folder
So mail to 21:2/1000 is 00020064, it goes without a hitch. Mail to 21:1/101 hex 00010065 get dropped off in the .015 folder but the 00010065 never sends.

Apparently you don't have the 21:ALL node configuration set to route to 21:2/1000 (or was that a typo and it should be /100?). Double-check your configuratoin.

So I 100% agree binkd doesn't know what to do with it I assumed that
is where the 21:ALL comes in. All to zone 21 goes to the hub, or so I would think.

Only if you have it configured that way in sbbsecho.ini.

It is killing me that it is whipping me :-)

I more logs to post to see if it helps.

Here is an example of the netmail that gets stuck

2020-01-29 20:07:05 Created NetMail (1.msg) from Randy Henderson (21:2/160) to Paul Hayton (21:1/101), attr: 0183, subject: Netmail Test
2020-01-29 20:07:05 Packing NetMail (1.msg) from Randy Henderson (21:2/160) to Paul Hayton (21:1/101), attr: 0183, subject: Netmail Test

Yup, no routing happening.

digital man

Synchronet/BBS Terminology Definition #44:
KD = King Drafus (Allen Christiansen)
Norco, CA WX: 61.2øF, 23.0% humidity, 3 mph SSE wind, 0.00 inches rain/24hrs --- SBBSecho 3.10-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Good to know that the nodelist is not needed, I was going to write a script to unpack/extract and replace the nodelist weekly, one less thing to worry about.

"Apparently you don't have the 21:ALL node configuration set to route to 21:2/1000 (or was that a typo and it should be /100?). Double-check your configuration." Yes typo in the message not the configuration

[node:21:ALL@fsxnet]
Name =
Comment =
Archive = None
PacketType = 2+
PacketPwd =
AreaFix = false
AreaFixPwd =
SessionPwd =
TicFilePwd =
Inbox =
Outbox =
Passive = false
Direct = false
Notify = false
Keys =
Status = Normal
Route = 21:2/100
LocalAddress = 21:2/160
GroupHub =
BinkpHost = error404bbs.ddns.net
BinkpPort = 24555
BinkpPoll = false
BinkpPlainAuthOnly = false
BinkpAllowPlainAuth = false
BinkpAllowPlainText = true
BinkpTLS = false
BinkpSourceAddress =

I will start specifically researching "netmail not being routed" I was going to
try a different mailer, but it seems the choices are limited to BinkD with Linux, I found an old copy or Irex but I think it will cause more issues than trying to solve the routing problem.

Gargoyle
DakrkAges BBS Wayne, OK
darkagesbbs.com

---
þ Synchronet þ DarkAges BBS | darkagesbbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Good to know that the nodelist is not needed, I was going to write
a script to unpack/extract and replace the nodelist weekly, one
less thing to worry about.

There is the nodelist handler that works with binkit when nodelists are received. Not strictly needed but good to have if you ever want to send a netmail directly to a node not in your config.

I will start specifically researching "netmail not being routed" I
was going to try a different mailer, but it seems the choices are
limited to BinkD with Linux, I found an old copy or Irex but I
think it will cause more issues than trying to solve the routing
problem.

I'm not to sure about your routeing issue but as far as mailers go you'll
find binkit is just as good and fast as binkd/efficient as binkd.

The binkit mailer also supports file requests from your node if you
configure that. Binkd can do that to but you need an external srif
utility and you need to keep the index's upto date, no need for that with binkit.

Ttyl :-),
Al

---
* MagickaBBS * The Rusty MailBox - Penticton, BC Canada
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: SBBSECHO
By: Gargoyle to Digital Man on Thu Jan 30 2020 09:51 am

Good to know that the nodelist is not needed, I was going to write a script to unpack/extract and replace the nodelist weekly, one less thing to worry about.

"Apparently you don't have the 21:ALL node configuration set to route to 21:2/1000 (or was that a typo and it should be /100?). Double-check your configuration." Yes typo in the message not the configuration

[node:21:ALL@fsxnet]
Name =
Comment =
Archive = None
PacketType = 2+
PacketPwd =
AreaFix = false
AreaFixPwd =
SessionPwd =
TicFilePwd =
Inbox =
Outbox =
Passive = false
Direct = false
Notify = false
Keys =
Status = Normal
Route = 21:2/100

Okay, so that means that newly-exported netmail destined for a 21:* address which does not otherwise have a [node:*] section in your sbbsecho.ini (in other words, it's not a "linked node" in EchoCfg) will be routed to 21:2/100, assuming the NetMail is not flagged with either "crash" or "hold" status. A routed NetMail message will appear in your sbbsecho.log file with a "Routing NetMail" log message.

If you're sending a NetMail message to an address which *is* a "linked node", then that message is not going to be routed unless you have that specific node configured to route somewhere else in EchoCfg/sbbsecho.ini.

I will start specifically researching "netmail not being routed" I was

going

to try a different mailer, but it seems the choices are limited to BinkD with Linux, I found an old copy or Irex but I think it will cause more issues than trying to solve the routing problem.

The problem you're having has nothing to do with BinkD. BinkD should work fine once you have SBBSecho configured properly.

You do have other options for mailers however, if you care to experiment in the future:
http://wiki.synchro.net/module:binkit


digital man

Synchronet "Real Fact" #72:
Synchronet CIOXTRN (created by Deuce) is a 32-bit replacement for DOORWAY. Norco, CA WX: 72.3øF, 19.0% humidity, 0 mph SSW wind, 0.00 inches rain/24hrs --- SBBSecho 3.10-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

There is the nodelist handler that works with binkit when nodelists
are received. Not strictly needed but good to have if you ever want
to send a netmail directly to a node not in your config.

I meant to say tickit, not binkit.. :)

If you get nodelists with tics tickit (tic file tosser) will grab your
nodelist for binkit to use. There is also and online nodelist browser
that you can use on the BBS to browse and search the nodelist.

Ttyl :-),
Al

---
* MagickaBBS * The Rusty MailBox - Penticton, BC Canada
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Thanks

Gargoyle
DakrkAges BBS Wayne, OK
darkagesbbs.com

---
þ Synchronet þ DarkAges BBS | darkagesbbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: SBBSECHO
By: Digital Man to Gargoyle on Thu Jan 30 2020 12:11 pm

Okay, so that means that newly-exported netmail destined for a 21:* address which does not otherwise have a [node:*] section in your sbbsecho.ini (in other words, it's not a "linked node" in EchoCfg) will

be

routed to 21:2/100, assuming the NetMail is not flagged with either "crash" or "hold" status. A routed NetMail message will appear in your sbbsecho.log file with a "Routing NetMail" log message.

Right I do not have a linked node for 21:1/101 in sbbsedcho.ini file, I do have 21:ALL in there, I made an assumption since FidoNet setup docs reccomend putting in 1:ALL etc... that I needed something similar in anoither network. I did have 21:2/100 set to crash but that is my uplink so I think that is okay. I will look at the logs again.

The problem you're having has nothing to do with BinkD. BinkD should work fine once you have SBBSecho configured properly.

Good to know, that narrows my search.
Gargoyle
DakrkAges BBS Wayne, OK
darkagesbbs.com

---
þ Synchronet þ DarkAges BBS | darkagesbbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: SBBSECHO
By: Digital Man to Gargoyle on Thu Jan 30 2020 12:11 pm

If you're sending a NetMail message to an address which *is* a "linked node", then that message is not going to be routed unless you have that specific node configured to route somewhere else in EchoCfg/sbbsecho.ini.

Would you consider changing this logic? (I tripped up on it too.)

I also thought, that netmail would be routed, unless "Direct" was true. Since you do have a direct configuration in echocfg, could you make it so that netmail will find the closes *:*/ALL to send netmail to unless Direct is true.

This would then enable you to have a configuration for a node that you may have a direct relationship with, but you can still route mail appropriately.

(This will help me with a problem I have with an uplink - I have an echocfg definition for a node - but when I netmail, for somereason after a successful poll, the mail is not transferred. The node does receive my netmail when routing it - but I have to remove the config in echocfg to have it routed.) ...deon


... Real Programmers do List Processing in FORTRAN.

---
þ Synchronet þ Alterant | an SBBS in Docker on Pi!
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Also is it normal with 2 networks two pick the originating address once you put
in who it addressed to?

Select Originating Address:
1: 1:19/25
2: 21:2/160

Gargoyle
DakrkAges BBS Wayne, OK
darkagesbbs.com

---
þ Synchronet þ DarkAges BBS | darkagesbbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: SBBSECHO
By: Alter Ego to Digital Man on Fri Jan 31 2020 09:28 am

Re: SBBSECHO
By: Digital Man to Gargoyle on Thu Jan 30 2020 12:11 pm

If you're sending a NetMail message to an address which *is* a "linked node", then that message is not going to be routed unless you have

that

specific node configured to route somewhere else in EchoCfg/sbbsecho.ini.

Would you consider changing this logic? (I tripped up on it too.)

In what way? SBBSecho does a closest-match search through all configured linked-nodes. You would prefer it a furthest-match search?

I also thought, that netmail would be routed, unless "Direct" was true.

The best-match linked-node status must be "normal" (not Hold or Crash) and the NetMail message itself must not have the CRASH or HOLD attribute flag set the netmail to be routed.

Since you do have a direct configuration in echocfg, could you make it so that netmail will find the closes *:*/ALL to send netmail to unless Direct is true.

This would then enable you to have a configuration for a node that you may have a direct relationship with, but you can still route mail

appropriately.

(This will help me with a problem I have with an uplink - I have an echocfg definition for a node - but when I netmail, for somereason after a successful poll, the mail is not transferred. The node does receive my netmail when routing it - but I have to remove the config in echocfg to

have

it routed.) ...deon

So you want echomail and netmail to take different routes to that linked node? If you want all mail to be routed to that linke node, just remove its linked-node configuration or set it's "Route to" configuration to the other hop you want it go through (and set Direct = No).

Or maybe I don't understand your request. :-)

digital man

Synchronet "Real Fact" #27:
Rob Swindell (digital man) was born approximately 4 hours before the Unix epoch.
Norco, CA WX: 72.1øF, 17.0% humidity, 5 mph SE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.10-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: SBBSECHO
By: Gargoyle to Digital Man on Thu Jan 30 2020 05:13 pm

Also is it normal with 2 networks two pick the originating address once you put in who it addressed to?

Select Originating Address:
1: 1:19/25
2: 21:2/160

That's normal when you have SCFG->Networks->FidoNet->Choose NetMail Source Address set to "Yes".

digital man

Synchronet/BBS Terminology Definition #41:
IP = Internet Protocol
Norco, CA WX: 72.1øF, 17.0% humidity, 5 mph SE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.10-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: SBBSECHO
By: Digital Man to Alter Ego on Thu Jan 30 2020 04:14 pm

The best-match linked-node status must be "normal" (not Hold or Crash)

and

the NetMail message itself must not have the CRASH or HOLD attribute flag set the netmail to be routed.

I didnt think it was working this way - but let do some testing and if it is not working the way I though, I'll give examples of configs and logs...

So you want echomail and netmail to take different routes to that linked node? If you want all mail to be routed to that linke node, just remove

Probably yes.

Echomail shouldnt be routed right? (I think I did see that sbbsecho route an echomail export to an uplink instead of the address in the export list - I know the uplink MBSE would have discarded it as being addressed "not to me").

So I would be expecting:
* Echomail be packaged up according to the export list of areas.bbs and not address to a routed uplink.
* Netmail is package to an uplink, unless it is marked as direct. (I think crash also triggers a direct connection? - although I think I recall this behaving differently on different BBS systems in the past...)

Is this right?

But as I say, let me play this out properly and I'll come back with logs if it is not working as I would expect...
...deon


... Today's extravagance becomes tomorrow's necessity.

---
þ Synchronet þ Alterant | an SBBS in Docker on Pi!
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: SBBSECHO
By: Alter Ego to Digital Man on Fri Jan 31 2020 12:20 pm

Re: SBBSECHO
By: Digital Man to Alter Ego on Thu Jan 30 2020 04:14 pm

The best-match linked-node status must be "normal" (not Hold or Crash) and the NetMail message itself must not have the CRASH or HOLD attribute flag set the netmail to be routed.

I didnt think it was working this way - but let do some testing and if it

is

not working the way I though, I'll give examples of configs and logs...

So you want echomail and netmail to take different routes to that linked node? If you want all mail to be routed to that linke node,

just

remove

Probably yes.

Echomail shouldnt be routed right?

Not normally, though it's technically possible.

(I think I did see that sbbsecho route an
echomail export to an uplink instead of the address in the export list - I know the uplink MBSE would have discarded it as being addressed "not to me").

So I would be expecting:
* Echomail be packaged up according to the export list of areas.bbs and not address to a routed uplink.

If one of the linked-nodes for a area is configured to route, the echomail packets (or bundles) will be routed.

* Netmail is package to an uplink, unless it is marked as direct. (I think crash also triggers a direct connection? - although I think I recall this behaving differently on different BBS systems in the past...)

The first "it" in your sentence above, that refers to the NetMail message or the uplink? It's possible both mesages and links to "marked as direct". Currently, the direct setting for a linked node is not checked in SBBSecho when deciding to route netmail messages for that node (or not).


digital man

This Is Spinal Tap quote #38:
Artie Fufkin: I'm not asking, I'm telling with this. Kick my ass.
Norco, CA WX: 65.5øF, 30.0% humidity, 6 mph NNE wind, 0.00 inches rain/24hrs --- SBBSecho 3.10-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Gargoyle wrote to Digital Man <=-

"Apparently you don't have the 21:ALL node configuration set to
route to 21:2/1000 (or was that a typo and it should be /100?). Double-check your configuration." Yes typo in the message not the configuration

[node:21:ALL@fsxnet]
Name =
Comment =
Archive = None
PacketType = 2+

<SNIP>

Try removing the "@fsxnet" part of that node definition. That's
how mine is and it works fine.



... Behind every great man is an amazed mother-in-law!
--- MultiMail/Linux v0.52
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: SBBSECHO
By: Gamgee to Gargoyle on Thu Jan 30 2020 20:48:00

[node:21:ALL@fsxnet]
Name =
Comment =
Archive = None
PacketType = 2+

<SNIP>

Try removing the "@fsxnet" part of that node definition. That's
how mine is and it works fine.

all of my sbbsecho entries have the @domain part and i also have the domains configured along with the nodelists for them...

my "ALL" default routing entries are listed first (in numerical order because $OCD)...

i also note that none of my "Route = " lines have the @domain... just the FTN address...


)\/(ark

---
þ Synchronet þ The SouthEast Star Mail HUB - SESTAR
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Terms :-)
My Hub = The system my mail is routed to, my uplink, the one that sends mail to
me when messages are posted in different echo's and the one I send mail from networked echo's to that are posted on my BBS

<SNIP>

Try removing the "@fsxnet" part of that node definition. That's
how mine is and it works fine.

You are right it did not have to be there, the regular mail still sent, and netmail to my hub's address sent, but mail to 21:1/101 still did not send

That's normal when you have SCFG->Networks->FidoNet->Choose NetMail Source Address set to "Yes".

Cool, I did figure that out after the posting, I guess I was turning things off
and on trying to figure out the magic switch to fix my issue. When I saw it, I thought duh, I turned that on.

Not normally, though it's technically possible.

So in FidoNet if I want to send nemtail to someone@1:203/2 and my SBBSECHO has 1:11/11 as my hub that I send everything (According to the above settings) it should take my netmail someone@1:203/2 pass it to my hub 1:11/11 then it goes on its journey to eventually makes its way to whom it was addressed to.
In my mind, that is how it works

It's been a long time since FrontDoor 202 days and I know some of my explanations have been confusing, so I am going to restate my issue in case I have mislead anyone.

I still struggle with the hex stuff, I understand the concept.... my hub's hex is 00020064 and any netmail sent to my hub has the name
00020064.cut and it is put in the outbound.015 folder (.015 hex number for zone
21) so it makes sense to me, and it works. However when the netmail to
another node in the network 21:1/101 has a hex of 00010065 it makes the netmail
message 00010065.cut and puts it in the outbound.015 folder it is ignored.
I would think anything in the outbound.015 folder should be routed to my hub. As an experiment, I took the 00010065.cut file and renamed it and it went out in milliseconds.

In addition, any message posted in the FSXNet Echo's goes to my hub just fine.

I do understand that if I had 21:ALL set to crash it would try to send direct, or on hold, it would be ignored as well.
Obviously, BinkD sees the 00010065.cut file and ignores it.

SBBSECHO.INI > Linked Nodes (Things that have no value were left out to save space)
[node:21:ALL]
Archive = None
PacketType = 2+
AreaFix = false
Passive = false
Direct = false
Notify = false
Status = Normal

That's why at first I blamed BinkD, then read the SBBSEcho.ini instructions until I got a headache. I wondered if scfg > networks > FidoNet Echomail and NetMail might have an incorrect setting
Under System addresses I have my main which is FidoNet and a AKA as FSXNet node
number. I have tried adding and removing it, no change

I appreciate everyone's help and patience.

Gargoyle
DakrkAges BBS Wayne, OK
darkagesbbs.com

---
þ Synchronet þ DarkAges BBS | darkagesbbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: SBBSECHO
By: Gargoyle to Gamgee on Fri Jan 31 2020 09:02:56


Gamgee> Try removing the "@fsxnet" part of that node definition. That's
Gamgee> how mine is and it works fine.

Gargoyle> You are right it did not have to be there, the regular mail
Gargoyle> still sent, and netmail to my hub's address sent, but mail
Gargoyle> to 21:1/101 still did not send

remember, packed mail in the BSO is not unpacked and repacked when routing changes... you have to rename the ?ut file by hand or use some external 3rd party BSO tool for that... so that original netmail you're trying to test with will stay in place until you do that or delete it and write another one to test with...


)\/(ark

---
þ Synchronet þ The SouthEast Star Mail HUB - SESTAR
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: SBBSECHO
By: Gargoyle to Gamgee on Fri Jan 31 2020 09:02 am

Not normally, though it's technically possible.

So in FidoNet if I want to send nemtail to someone@1:203/2 and my SBBSECHO has 1:11/11 as my hub that I send everything (According to the above settings) it should take my netmail someone@1:203/2 pass it to my hub 1:11/11 then it goes on its journey to eventually makes its way to whom it was addressed to.
In my mind, that is how it works

Correct, assuming that's how you have your system (SBBSecho) configured.

It's been a long time since FrontDoor 202 days and I know some of my explanations have been confusing, so I am going to restate my issue in case I have mislead anyone.

So FrontDoor is an arc/attach-style mailer which handles routing. BinkD is a BSO/FLO-style mailer which does *not* handle routing. For BSO, the echomail program (e.g. SBBSEcho) has to handle the routing.

I still struggle with the hex stuff, I understand the concept.... my hub's hex is 00020064 and any netmail sent to my hub has the name
00020064.cut and it is put in the outbound.015 folder (.015 hex number for zone 21) so it makes sense to me, and it works. However when the netmail to another node in the network 21:1/101 has a hex of 00010065 it makes the netmail message 00010065.cut and puts it in the outbound.015 folder it is ignored.
I would think anything in the outbound.015 folder should be routed to my hub.

No. The mailer (BinkD) does not handle routing. The mail files must be named for your hub for BinkD to deliver it to to your hub.

As an experiment, I took the 00010065.cut file and renamed it and it
went out in milliseconds.

In addition, any message posted in the FSXNet Echo's goes to my hub just fine.

I do understand that if I had 21:ALL set to crash it would try to send direct, or on hold, it would be ignored as well.
Obviously, BinkD sees the 00010065.cut file and ignores it.

SBBSECHO.INI > Linked Nodes (Things that have no value were left out to

save

space)
[node:21:ALL]
Archive = None
PacketType = 2+
AreaFix = false
Passive = false
Direct = false
Notify = false
Status = Normal

So you're not routing your 21:* netmail?

That's why at first I blamed BinkD, then read the SBBSEcho.ini instructions until I got a headache. I wondered if scfg > networks > FidoNet Echomail

and

NetMail might have an incorrect setting
Under System addresses I have my main which is FidoNet and a AKA as FSXNet node number. I have tried adding and removing it, no change

No, that's not it.


digital man

Synchronet "Real Fact" #73:
SyncTERM (created by Deuce) contains portions of Synchronet and SEXYZ code. Norco, CA WX: 75.0øF, 21.0% humidity, 2 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.10-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Is this

i also note that none of my "Route = " lines have the @domain... just the FTN address...

Suppose to say have or do not have?

Gargoyle
DakrkAges BBS Wayne, OK
darkagesbbs.com

---
þ Synchronet þ DarkAges BBS | darkagesbbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Rampage> remember, packed mail in the BSO is not unpacked and repacked when routing changes... you have to rename
Rampage> the ?ut file by hand or use some external 3rd party BSO tool for that... so that original netmail you're trying to test
Rampage> with will stay in place until you do that or delete it and write another one to test with...

I have just been deleting it and writing another one, I am getting pretty quick
at it.

Gargoyle
DarkAges BBS Wayne, OK
darkagesbbs.com

---
þ Synchronet þ DarkAges BBS | darkagesbbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Deon

Let me know if you get that working, sounds like a similar problem of mine.

Gargoyle
DarkAges BBS Wayne, OK
darkagesbbs.com

---
þ Synchronet þ DarkAges BBS | darkagesbbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: SBBSECHO
By: Digital Man to Gargoyle on Fri Jan 31 2020 11:12 am

So FrontDoor is an arc/attach-style mailer which handles routing. BinkD

is

a BSO/FLO-style mailer which does *not* handle routing. For BSO, the echomail program (e.g. SBBSEcho) has to handle the routing.

Thanks for that, helps me wrap my head around it.

No. The mailer (BinkD) does not handle routing. The mail files must be named for your hub for BinkD to deliver it to to your hub.

SO, it is not a matter of Binkd ignoring it, since it is only the mailer, SBBSECHO is not configured right so it is not packing it correctly.

So you're not routing your 21:* netmail?

If you mean setting
Route = 21:2/100
Which is the hub, I have had it in and out on differnet occasionas trying various setups.

No, that's not it.

Cool, another rabbit I don't have to chase.

Just for fun I tried to send a FidoNet NetMail (Just never tried it other than Seal Echo or Allfix) anyway it has the same issue. So I can stop looking at the differences between the two.
Gargoyle
=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=_~
DarkAges BBS | Wayne, Oklahoma | Synchronet 3.17
Telnet: darkagesbbs.com | WWW: dakrgesbbs.com
FidoNet | Dove-Net | FSXNet | Doors BBSLink

---
þ Synchronet þ DarkAges BBS | darkagesbbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: SBBSECHO
By: Gargoyle to Gamgee on Fri Jan 31 2020 09:02:56


Gargoyle> I still struggle with the hex stuff, I understand the concept....

are you on linux? if so, the following command will be helpful ;)

printf "%04x%04x" 3634 12

"%04x" means to zero pad the result to four places and convert the decimal numbers to hex...

the above will return the hex for my main system... just change the two numbers to the net and node of the destination system...


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

Re: Re: SBBSECHO
By: Gargoyle to Rampage on Fri Jan 31 2020 16:06:49


Gargoyle> Is this

i also note that none of my "Route = " lines have the @domain... just the FTN address...

Gargoyle> Suppose to say have or do not have?

none of my route lines have the @domain... only the node entries...

[...]
[node:1:116/ALL@fidonet]
Name =
Comment = Fidonet 1:116 Systems via 1:116/116
Archive = None
PacketType = 2+
PacketPwd =
AreaFix = false
AreaFixPwd =
SessionPwd =
TicFilePwd =
Inbox =
Outbox =
Passive = false
Direct = false
Notify = false
Keys =
Status = Normal

Route = 1:116/116

GroupHub =
BinkpHost =
BinkpPort = 24554
BinkpPoll = false
BinkpPlainAuthOnly = false
BinkpAllowPlainAuth = false
BinkpAllowPlainText = true
BinkpTLS = false
BinkpSourceAddress =
[...]
[node:1:135/ALL@fidonet]
Name =
Comment = Fidonet 1:135 Systems via 1:135/300
Archive = None
PacketType = 2+
PacketPwd =
AreaFix = false
AreaFixPwd =
SessionPwd =
TicFilePwd =
Inbox =
Outbox =
Passive = false
Direct = false
Notify = false
Keys =
Status = Normal

Route = 1:135/300

GroupHub =
BinkpHost =
BinkpPort = 24554
BinkpPoll = false
BinkpPlainAuthOnly = false
BinkpAllowPlainAuth = false
BinkpAllowPlainText = true
BinkpTLS = false
BinkpSourceAddress =
[node:1:153/ALL@fidonet]
Name =
Comment = Fidonet 1:153 Systems via 1:153/7715
Archive = None
PacketType = 2+
PacketPwd =
AreaFix = false
AreaFixPwd =
SessionPwd =
TicFilePwd =
Inbox =
Outbox =
Passive = false
Direct = false
Notify = false
Keys =
Status = Normal

Route = 1:153/7715

GroupHub =
BinkpHost =
BinkpPort = 24554
BinkpPoll = false
BinkpPlainAuthOnly = false
BinkpAllowPlainAuth = false
BinkpAllowPlainText = true
BinkpTLS = false
BinkpSourceAddress =
[...]


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

Re: Re: SBBSECHO
By: Gargoyle to Digital Man on Fri Jan 31 2020 05:24 pm

Re: Re: SBBSECHO
By: Digital Man to Gargoyle on Fri Jan 31 2020 11:12 am

So FrontDoor is an arc/attach-style mailer which handles routing.

BinkD

is a BSO/FLO-style mailer which does *not* handle routing. For BSO,

the

echomail program (e.g. SBBSEcho) has to handle the routing.

Thanks for that, helps me wrap my head around it.

No. The mailer (BinkD) does not handle routing. The mail files must be named for your hub for BinkD to deliver it to to your hub.

SO, it is not a matter of Binkd ignoring it, since it is only the mailer, SBBSECHO is not configured right so it is not packing it correctly.

Correct.

So you're not routing your 21:* netmail?

If you mean setting
Route = 21:2/100
Which is the hub, I have had it in and out on differnet occasionas trying various setups.

You need it in there if you want to route netmail that's been addressed to 21:* nodes.

digital man

Synchronet "Real Fact" #3:
Synchronet version 2 was written in C and 8086 assembly programming languages. Norco, CA WX: 77.4øF, 19.0% humidity, 2 mph ESE wind, 0.00 inches rain/24hrs --- SBBSecho 3.10-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Rampage wrote to Gamgee <=-

[node:21:ALL@fsxnet]
Name =
Comment =
Archive = None
PacketType = 2+

<SNIP>

Try removing the "@fsxnet" part of that node definition. That's
how mine is and it works fine.

all of my sbbsecho entries have the @domain part and i also have
the domains configured along with the nodelists for them...

It seems redundant and unnecessary to include that. I also have
the domains/nodelists configured, as such:

[domain:fsxnet]
Zones = 21
DNSSuffix =
OutboundRoot = /sbbs/fido/outbound
NodeList = /sbbs/fido/nodelist/FSXNET.361

So, doesn't the system already know that "[node:21:ALL]" means
FSXNet? It states right there that FSXNet is zone 21.

my "ALL" default routing entries are listed first (in numerical
order because $OCD)...

;-)

i also note that none of my "Route = " lines have the @domain...
just the FTN address...

Same here.


... She kept saying I didn't listen to her, or something like that.
--- MultiMail/Linux v0.52
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

[root@bbs sbbs]# printf "%04x%04x" 2 100
00020064

Worked great

Gargoyle
=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=_~
DarkAges BBS | Wayne, Oklahoma | Synchronet 3.17
Telnet: darkagesbbs.com | WWW: dakrgesbbs.com
FidoNet | Dove-Net | FSXNet | Doors BBSLink

---
þ Synchronet þ DarkAges BBS | darkagesbbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: SBBSECHO
By: Gargoyle to Alter Ego on Fri Jan 31 2020 04:13 pm

Let me know if you get that working, sounds like a similar problem of mine.

To get it working, just add the specific routes you need for each defined entry you have in sbbsecho.ini.

EG:
I am 21:2/116, I have

21:ALL go to 21:2/100

If I had an entry for 21:1/111, I would add 21:2/100 as a "Route To" for that node as well, if I wanted stuff to be routed through my normal hub (and not go direct).

I think we've worked out sbbsecho will route everything addressed in the "Route to" (which in my experience is not functional, since it will route any packet - including those with echomail) to that destination (and some destinations dont know how to route packets unless it is just a netmail packet).

But in the normal scenario (based on the example above), I would probably never export echomail for 21:1/111, so having that route to is OK.

(I have to toggle that for an uplink in fido, where polling it direct is not receiving mail - echomail and netmail, so I have to send a routed netmail for the sysop to receive my message - and to do that I temporarily add that route to for that to happen.)
...deon


... For a man of fortitude, there are no walls, only avenues.

---
þ Synchronet þ Alterant | an SBBS in Docker on Pi!
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: SBBSECHO
By: Gamgee to Rampage on Fri Jan 31 2020 18:36:00


Rampage>> all of my sbbsecho entries have the @domain part and i also
Rampage>> have the domains configured along with the nodelists for
Rampage>> them...

Gamgee> It seems redundant and unnecessary to include that. I also
Gamgee> have the domains/nodelists configured, as such:

Gamgee> [domain:fsxnet]
Gamgee> Zones = 21
Gamgee> DNSSuffix =
Gamgee> OutboundRoot = /sbbs/fido/outbound
Gamgee> NodeList = /sbbs/fido/nodelist/FSXNET.361

Gamgee> So, doesn't the system already know that "[node:21:ALL]"
Gamgee> means FSXNet? It states right there that FSXNet is zone 21.


what does it do in the following situations?


[domain:survnet]
Zones = 9
DNSSuffix =
OutboundRoot = /sbbs/ftn/out/survnet
NodeList = /sbbs/ftn/nodelist/survnet.txt
[domain:virnet]
Zones = 9
DNSSuffix =
OutboundRoot = /sbbs/ftn/out/virnet
NodeList = /sbbs/ftn/nodelist/virnet.txt
[domain:winsnet]
Zones = 9
DNSSuffix =
OutboundRoot = /sbbs/ftn/out/winsnet
NodeList = /sbbs/ftn/nodelist/winsnet.txt


[domain:araknet]
Zones = 10
DNSSuffix =
OutboundRoot = /sbbs/ftn/out/araknet
NodeList = /sbbs/ftn/nodelist/araknet.txt
[domain:league10]
Zones = 10
DNSSuffix =
OutboundRoot = /sbbs/ftn/out/league10
NodeList = /sbbs/ftn/nodelist/league10.txt


[domain:fsxnet]
Zones = 21
DNSSuffix = fsxnet.nz
OutboundRoot = /sbbs/ftn/out/fsxnet
NodeList = /sbbs/ftn/nodelist/fsxnet.txt
[domain:usenet]
Zones = 21
DNSSuffix =
OutboundRoot = /sbbs/ftn/out/usenet
NodeList = /sbbs/ftn/nodelist/usenet.txt
[domain:zone21]
Zones = 21
DNSSuffix =
OutboundRoot = /sbbs/ftn/out/zone21
NodeList = /sbbs/ftn/nodelist/zone21.txt


[domain:gamenet]
Zones = 32
DNSSuffix =
OutboundRoot = /sbbs/ftn/out/gamenet
NodeList = /sbbs/ftn/nodelist/gamenet.txt
[domain:htmlnet]
Zones = 32
DNSSuffix =
OutboundRoot = /sbbs/ftn/out/htmlnet
NodeList = /sbbs/ftn/nodelist/htmlnet.txt


[domain:sfnet]
Zones = 42
DNSSuffix =
OutboundRoot = /sbbs/ftn/out/sfnet
NodeList = /sbbs/ftn/nodelist/sfnet.txt
[domain:unionnet]
Zones = 42
DNSSuffix =
OutboundRoot = /sbbs/ftn/out/unionnet
NodeList = /sbbs/ftn/nodelist/unionnet.txt


[domain:anet]
Zones = 92
DNSSuffix =
OutboundRoot = /sbbs/ftn/out/anet
NodeList = /sbbs/ftn/nodelist/anet.txt
[domain:zenet]
Zones = 92
DNSSuffix =
OutboundRoot = /sbbs/ftn/out/zenet
NodeList = /sbbs/ftn/nodelist/zenet.txt


yes, those are real zones and domains harvested from my mailer logs ;)

in each of these cases, the domain is a must if you're in multiple FTNs that use the same zone for different FTN domains... sbbsecho is quite capable of handling this with one small caveat...

that caveat is what i call 4.5D (as opposed to 5D) because it still uses the hex zone number on the end of the OutboundRoot instead of only using it for additional zones in the same net... BinkIt has no problem with this because it and sbbsecho use the same code (i think) but binkd needs to be lied to and told that the base zone for all domains is 1 instead of the actual base zone... JustaNet is an example of this...

[domain:justanet]
Zones = 510,539
DNSSuffix =
OutboundRoot = /sbbs/ftn/out/justanet
NodeList = /sbbs/ftn/nodelist/justanet.txt

sbbsecho maintains

/sbbs/ftn/out/justanet.1fe
/sbbs/ftn/out/justanet.21b

instead of

/sbbs/ftn/out/justanet
/sbbs/ftn/out/justanet.21b

like a true 5D tosser would... i'm not saying that this is wrong but it isn't how i read the BSO description for this situation... if it were like this, then how come fidonet with its zones 1-6 (yes, i still keep all 6 in reserve) doesn't use /sbbs/ftn/out/fidonet.001 for its base outbound root? ;)

NOTE: sharp eyes will note that yes, i'm using different OutboundRoot directories for each domain instead of using only one OutboundRoot for all and relying on the hex zone extension... this is how i understand full 5D to be done but the other (current) way is "ok", too...

for example, i find this easier to deal with when i'm manually hunting something in the outbound than when all directories are outbound.xxx... not to mention that thing about mixing traffic for multiple domains using the same zone(s)


/sbbs/ftn/out/fidonet
/sbbs/ftn/out/fidonet.002
/sbbs/ftn/out/fidonet.003
/sbbs/ftn/out/fidonet.004
/sbbs/ftn/out/fidonet.005
/sbbs/ftn/out/fidonet.006
/sbbs/ftn/out/fmlynet.008
/sbbs/ftn/out/survnet.009
/sbbs/ftn/out/virnet.009
/sbbs/ftn/out/winsnet.009
/sbbs/ftn/out/araknet.00a
/sbbs/ftn/out/league10.00a
/sbbs/ftn/out/wwivftn.00b
/sbbs/ftn/out/zyxelnet.010
/sbbs/ftn/out/nazznet.013
/sbbs/ftn/out/fsxnet.015
/sbbs/ftn/out/survnet.015
/sbbs/ftn/out/usenet.015
/sbbs/ftn/out/zone21.015


my understanding is that 5D outbound would look like this... i find it even easier to follow/understand... for one thing, it is immediately apparent which domains use more than one zone which helps narrow the directory in which to look for certain traffic...

/sbbs/ftn/out/advnet
/sbbs/ftn/out/agoranet
/sbbs/ftn/out/amiganet
/sbbs/ftn/out/anet
/sbbs/ftn/out/araknet
/sbbs/ftn/out/battlnet
/sbbs/ftn/out/beerme
/sbbs/ftn/out/billnet
/sbbs/ftn/out/choicfdn
/sbbs/ftn/out/cnet
/sbbs/ftn/out/combatnt
/sbbs/ftn/out/cscnet
/sbbs/ftn/out/cybernet
/sbbs/ftn/out/dbnet
/sbbs/ftn/out/dixie
/sbbs/ftn/out/dorenet
/sbbs/ftn/out/dovenet
/sbbs/ftn/out/dsdsnet
/sbbs/ftn/out/ezynet
/sbbs/ftn/out/fidode
/sbbs/ftn/out/fidonet
/sbbs/ftn/out/fidonet.002
/sbbs/ftn/out/fidonet.003
/sbbs/ftn/out/fidonet.004
/sbbs/ftn/out/fidonet.005
/sbbs/ftn/out/fidonet.006
/sbbs/ftn/out/fmlynet
/sbbs/ftn/out/fsxnet
/sbbs/ftn/out/gamenet
/sbbs/ftn/out/gamesnet
/sbbs/ftn/out/gatornet
/sbbs/ftn/out/gmsnet
/sbbs/ftn/out/gtpower
/sbbs/ftn/out/happynet
/sbbs/ftn/out/htmlnet
/sbbs/ftn/out/ilink
/sbbs/ftn/out/justanet
/sbbs/ftn/out/justanet.21b
/sbbs/ftn/out/league10
/sbbs/ftn/out/linuxnet
/sbbs/ftn/out/micronet
/sbbs/ftn/out/nazznet
/sbbs/ftn/out/pasnet
/sbbs/ftn/out/pinet
/sbbs/ftn/out/potsnet
/sbbs/ftn/out/quartz
/sbbs/ftn/out/rdwxnet
/sbbs/ftn/out/retronet
/sbbs/ftn/out/rmininet
/sbbs/ftn/out/scinet
/sbbs/ftn/out/sfnet
/sbbs/ftn/out/spooknet
/sbbs/ftn/out/sportnet
/sbbs/ftn/out/stn
/sbbs/ftn/out/survnet
/sbbs/ftn/out/tqmradio
/sbbs/ftn/out/tqwnet
/sbbs/ftn/out/unionnet
/sbbs/ftn/out/usenet
/sbbs/ftn/out/virnet
/sbbs/ftn/out/vkradio
/sbbs/ftn/out/vqnet
/sbbs/ftn/out/whisper
/sbbs/ftn/out/winsnet
/sbbs/ftn/out/wwivftn
/sbbs/ftn/out/xnet
/sbbs/ftn/out/zenet
/sbbs/ftn/out/zeronet
/sbbs/ftn/out/zone21
/sbbs/ftn/out/zyxelnet



)\/(ark

---
þ Synchronet þ The SouthEast Star Mail HUB - SESTAR
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: SBBSECHO
By: Gargoyle to mark lewis on Fri Jan 31 2020 19:36:16

[root@bbs sbbs]# printf "%04x%04x" 2 100
00020064

Worked great

:)

i have numerous scripts that use that form... one looks for mail sitting around in the outbound and lists it along with the binkd "next attempt" and "last attempt results" information if binkd is being used...

like this section that converts the hex back into decimal and stores it in the ftnaddress variable... blank lines added to avoid wordwrap hell...


if [[ -f ${thisfile} ]]; then

# is it a file or a directory?

idx=$(strindex "$thisfile" .pnt)

if (( idx == -1 )); then

nopathfname=${thisfile##*/}

noextfname=${nopathfname%.*}

ftnaddress="$(printf "%d:%d/%d" 0x"$pathext" 0x"${noextfname:0:4}" 0x"${noextfname:4}")"

# get the flo file type; f - normal, c - crash, h - hold, d - direct, i - immediate

floext=${nopathfname#*.}

else

pntdir=$(basename "$(dirname "$thisfile")")

noextpntdir=${pntdir%.*}

nopathfname=${thisfile##*/}

noextfname=${nopathfname%.*}

ftnaddress="$(printf "%d:%d/%d.%d" 0x"$pathext" 0x"${noextpntdir:0:4}" 0x"${noextpntdir:4}" 0x"${noextfname:0:8}")"

# get the flo file type; f - normal, c - crash, h - hold, d - direct, i - immediate

floext=${nopathfname#*.}

fi


example output:

3 destinations in fidonet zone 1
d 1:14/6@fidonet (000e0006) : 1 file : 05:50
Next Delivery Attempt: 2020-02-01 08:00:53 -0500
Last Delivery Status: connection closed by foreign host

d 1:123/130@fidonet (007b0082) : netmail : 6 days 07:56:25
Next Delivery Attempt: 2020-02-01 08:00:19 -0500
Last Delivery Status: Connection timed out

d 1:123/755@fidonet (007b02f3) : 265 files : 1 day 17:24:32
Next Delivery Attempt: 2020-02-01 08:04:41 -0500
Last Delivery Status: Connection timed out



)\/(ark

---
þ Synchronet þ The SouthEast Star Mail HUB - SESTAR
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: SBBSECHO
By: Rampage to Gamgee on Sat Feb 01 2020 07:47:42


Rampage> yes, those are real zones and domains harvested from my mailer
Rampage> logs ;)

i just wanted to say that while writing that long message and doing more research, i found five more FTN networks in my mailer logs ;)

zoonet zone 31 (01f)
devnet zone 256 (100)
wennet zone 316 (13c)
musicnet zone 440 (1b8)
weirdnet zone 944 (3b0)


)\/(ark

---
þ Synchronet þ The SouthEast Star Mail HUB - SESTAR
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: SBBSECHO
By: Alter Ego to Gargoyle on Sat Feb 01 2020 04:32 pm

To get it working, just add the specific routes you need for each defined entry you have in sbbsecho.ini.
21:ALL go to 21:2/100

Issue: When sending netmail to anyone other then 21:2/100 it does not go
Just to be sure I deleted all linked nodes and started over to make sure I didn't have anything quirky going on.

So my uplink hub settings in SBBSECHO.INI
[node:21:2/100@fsxnet]
More stuff below
<<SNIP>>

Only with that entry and no others like 21:ALL
Netmail just sits there
I added

[node:21:ALL]
More stuff below
<<SNIP>>

Netmail just sits there I would think it would try to poll 21:?/??? whomever I addressed the netmail to - I dont have any sessions setup with these nodes but I assume I could send a netmail
Then I added a Route to to match my uplink

[node:21:ALL]
Route = 21:2/100
More stuff below
<<SNIP>>

Netmail to 21:1/101 just sits there

If I had an entry for 21:1/111, I would add 21:2/100 as a "Route To" for that node as well, if I wanted stuff to be routed through my normal hub (and not go direct).

Then I tried

[node:21:1/101@fsxnet]
More stuff below
<<SNIP>>

Netmail just sits there
Then I added a route to for that node

[node:21:1/101@fsxnet]
Route = 21:2/100
More stuff below
<<SNIP>>

In reading the responses I don't think most people feel like the @domain is an issue so to be sure I added the @fsxnet after the 21:ALL and still netmail sat there

Other than adding a nodelist I had not really changed anything here'

[domain:fsxnet]
Zones = 21
DNSSuffix = fsxnet.nz
NodeList = /sbbs/nodelist/FSXNET.024

I wondered if maybe I couldn't reach fsxnet.nz

[root@bbs sbbs]# ping fsxnet.nz
PING fsxnet.nz (185.199.111.153) 56(84) bytes of data.
64 bytes from 185.199.111.153 (185.199.111.153): icmp_seq=1 ttl=54 time=0.922 ms
64 bytes from 185.199.111.153 (185.199.111.153): icmp_seq=2 ttl=54 time=0.703 ms
^C
-+- fsxnet.nz ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 0.703/0.812/0.922/0.113 ms
[root@bbs sbbs]#

So I can reach that domain

I have logs set to debugging - However between sbbsecho log and binkd log I am not sure what is going on - What is happening between ssbsecho and binkd?

Sbbsecho says it processes the netmail
2020-02-01 09:12:16 Created NetMail (1.msg) from Randy Henderson (21:2/160) to Paul Hayton (21:1/101), attr: 0183, subject: Test
2020-02-01 09:12:16 Packing NetMail (1.msg) from Randy Henderson (21:2/160) to Paul Hayton (21:1/101), attr: 0183, subject: Test
2020-02-01 09:12:16 Node (21:1/101) successfully locked via: /sbbs/fido/outbound.015/00010065.bsy
2020-02-01 09:12:16 Adding NetMail (1.msg) to new packet for 21:1/101: /sbbs/fido/outbound.015/00010065.cut
2020-02-01 09:12:16 Deleting /sbbs/netmail/1.msg (from line 5272)
2020-02-01 09:12:16 Touching outgoing semfile: ../data/binkout.now
2020-02-01 09:12:16 Writing 3 areas to /sbbs/data/badareas.lst
2020-02-01 09:12:16 Deleting /sbbs/fido/outbound.015/00010065.bsy (from line 3020)
2020-02-01 09:12:16 Deleting /sbbs/ctrl/sbbsecho.bsy (from line 3026) 2020-02-01 09:12:16 SBBSecho (PID 19712) exiting with error level 0, NetMail(0 imported, 1 exported, 1 packed)

On the next poll the message is not sent

+ 01 Feb 09:13:05 [19723] Remote requests MD mode
- 01 Feb 09:13:05 [19723] SYS fsxNet [Net2] Tholian
- 01 Feb 09:13:05 [19723] ZYZ Todd Zieman - Solaris
- 01 Feb 09:13:05 [19723] TIME Sat, 01 Feb 2020 10:13:06 -0500
- 01 Feb 09:13:05 [19723] VER Mystic/1.12A43 binkp/1.0
- 01 Feb 09:13:05 [19723] BUILD 2019/03/03 01:36:15 Windows/64
+ 01 Feb 09:13:05 [19723] addr: 21:2/100@fsxnet
+ 01 Feb 09:13:05 [19723] pwd protected session (MD5)
- 01 Feb 09:13:05 [19723] QSIZE 1 files 1,192 bytes
- 01 Feb 09:13:06 [19723] receiving 0000ffc4.sa1 (1192 byte(s), off 0)
+ 01 Feb 09:13:06 [19723] 0000ffc4.sa1 -> /sbbs/fido/inbound/0000ffc4.sa1
01 Feb 09:13:06 [19723] got *.sa?, delayed creating /sbbs/data/fidoin.now
01 Feb 09:13:06 [19723] got *.SA?, delayed creating /sbbs/data/fidoin.now
+ 01 Feb 09:13:06 [19723] rcvd: 0000ffc4.sa1 (1192, 1192.00 CPS, 21:2/100@fsxnet)
+ 01 Feb 09:13:06 [19723] done (to 21:2/100@fsxnet, OK, S/R: 0/1 (0/1192 bytes))
01 Feb 09:13:06 [19723] Creating /sbbs/data/fidoin.now
01 Feb 09:13:06 [19723] session closed, quitting...


Crazy right? At least it is driving me crazy.

Gargoyle
=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~
DarkAges BBS | Wayne, Oklahoma | Synchronet 3.17
Telnet: darkagesbbs.com | WWW: dakrgesbbs.com
FidoNet | Dove-Net | FSXNet | Doors BBSLink

... Chuck Norris can get 8 hours of sleep in 2 hours.

---
þ Synchronet þ DarkAges BBS | darkagesbbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Rampage wrote to Gamgee <=-

Rampage>> all of my sbbsecho entries have the @domain part and i
also
Rampage>> have the domains configured along with the nodelists
for
Rampage>> them...

Gamgee> It seems redundant and unnecessary to include that. I
also
Gamgee> have the domains/nodelists configured, as such:

Gamgee> [domain:fsxnet]
Gamgee> Zones = 21
Gamgee> DNSSuffix =
Gamgee> OutboundRoot = /sbbs/fido/outbound
Gamgee> NodeList = /sbbs/fido/nodelist/FSXNET.361

Gamgee> So, doesn't the system already know that "[node:21:ALL]"
Gamgee> means FSXNet? It states right there that FSXNet is zone
21.

what does it do in the following situations?

[domain:survnet]
Zones = 9
DNSSuffix =
OutboundRoot = /sbbs/ftn/out/survnet
NodeList = /sbbs/ftn/nodelist/survnet.txt
[domain:virnet]
Zones = 9
DNSSuffix =
OutboundRoot = /sbbs/ftn/out/virnet
NodeList = /sbbs/ftn/nodelist/virnet.txt
[domain:winsnet]
Zones = 9
DNSSuffix =
OutboundRoot = /sbbs/ftn/out/winsnet
NodeList = /sbbs/ftn/nodelist/winsnet.txt

<SNIP>

Hmmmm, Okay, I thought networks were supposed to pick/use a unique
zone number. Didn't realize this situation existed, and in *THAT*
case it makes sense to add the domain name to a routing label.

I suspect there are very few systems (other than STAR hubs like
yourself) that would need such a thing. :-)

I also snipped the 4.5D/5D stuff you wrote, but that's good info
and handy for large systems with lots of downlinks. Thanks!



... AAcckk!! II''mm iinn hhaallff dduupplleexx
--- MultiMail/Linux v0.52
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: SBBSECHO
By: Gamgee to Rampage on Sat Feb 01 2020 08:19:00

Hmmmm, Okay, I thought networks were supposed to pick/use a unique
zone number. Didn't realize this situation existed, and in *THAT*
case it makes sense to add the domain name to a routing label.

FTN domains (aka 5D) were created specifically to handle multiple FTNs using the same zone numbers... it was a lot worse back in the day but duplicate zones is also one of the reasons why the various FTN lists were created and maintained... of course, they also provided a convienient list of othernets for operators to look through when looking for additional networks for their systems...

I suspect there are very few systems (other than STAR hubs like
yourself) that would need such a thing. :-)

leaf nodes would need to use the domains if they are in FTNs that share the same zone... if you're in only one FTN or only a few that don't share a zone, you can get by without using the domains...

in my case, i wanted to ""move up to"" using full 5D just because ;) plus it also allows me to find defects and solutions for them to enhance the capability...

I also snipped the 4.5D/5D stuff you wrote, but that's good info
and handy for large systems with lots of downlinks. Thanks!

i posted it specifically to provide the info for others to have and study... you're quite welcome to it :)


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

Re: SBBSECHO
By: Gargoyle to Alter Ego on Sat Feb 01 2020 09:22 am

Re: SBBSECHO
By: Alter Ego to Gargoyle on Sat Feb 01 2020 04:32 pm

To get it working, just add the specific routes you need for each defined entry you have in sbbsecho.ini.
21:ALL go to 21:2/100

Issue: When sending netmail to anyone other then 21:2/100 it does not go Just to be sure I deleted all linked nodes and started over to make sure I didn't have anything quirky going on.

So my uplink hub settings in SBBSECHO.INI
[node:21:2/100@fsxnet]
More stuff below
<<SNIP>>

Only with that entry and no others like 21:ALL
Netmail just sits there

Netmail destined for what address?

I added

[node:21:ALL]
More stuff below
<<SNIP>>

No "Route = " line?

Netmail just sits there I would think it would try to poll 21:?/???

whomever

Only if the mail was created with a Crash attribute. And only if your mailer (BinkD) can know how to connect to that 21:?/??? node.

I addressed the netmail to - I dont have any sessions setup with these

nodes

but I assume I could send a netmail

You can if BinkD has access to a current nodelist and the destination node in that nodelist has a valid IP address or hostname which with BinkD can use to connect to that node.

Then I added a Route to to match my uplink

[node:21:ALL]
Route = 21:2/100

Okay, but then that's too late for any netmail messages already exported by SBBSecho. You'd have to send a neew netmail message to 21:?/??? and have it exported by SBBSecho for it then be routed to 21:2/100.

Netmail to 21:1/101 just sits there

If that NetMail was sent *before* you added the "Route" entry, then that makes complete sense.

If I had an entry for 21:1/111, I would add 21:2/100 as a "Route To" for that node as well, if I wanted stuff to be routed through my

normal

hub (and not go direct).

Then I tried

[node:21:1/101@fsxnet]
More stuff below
<<SNIP>>

That's not going to help.

Netmail just sits there

For the same reasons outlined above.

Then I added a route to for that node

[node:21:1/101@fsxnet]
Route = 21:2/100

Again, if you added this route *after* you exported the netmail, it's too late.

I have logs set to debugging - However between sbbsecho log and binkd log I am not sure what is going on - What is happening between ssbsecho and

binkd?

Crazy right? At least it is driving me crazy.

You seem to keep removing the Route configuration from EchoCfg/sbbsecho.ini before sending/exporting netmail and then expecting that when you add the Route configuration back-in, that the previously exported netmail will then get routed to your hub. It will not.

digital man

Synchronet "Real Fact" #40:
Synchronet has been ported to FreeBSD, NetBSD, OpenBSD, Solaris, QNX, and MacOS.
Norco, CA WX: 83.8øF, 19.0% humidity, 0 mph SSW wind, 0.00 inches rain/24hrs --- SBBSecho 3.10-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Ok, got it fixed, it was not sbbsecho but binkd not looking in the correct folder,

FYI all the docs say domain fidonet /sbbs/fido/outbound 1 and 1 Zone so if your
do FsxNet you would think it would be domain fsxnet /sbbs/fido/outbound 21 and I couls send my uplink netmail but in the end it has to be domain fsxnet /sbbs/fido/outbound 1

I had this gut feeling it was binkd ignoring something...3 days, so happy!!

Gargoyle
=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~
DarkAges BBS | Wayne, Oklahoma | Synchronet 3.17
Telnet: darkagesbbs.com | WWW: dakrgesbbs.com
FidoNet | Dove-Net | FSXNet | Doors BBSLink

---
þ Synchronet þ DarkAges BBS | darkagesbbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: SBBSECHO
By: Gargoyle to Alter Ego on Sat Feb 01 2020 09:22 am

Crazy right? At least it is driving me crazy.

I'll have a play tonight and get you are working example - I'm in hub 2 as well, and I'll set up definition to 1/101, but have it route via 2/100...

Stay tuned :)
...deon


... Any club that would accept me as a member, I wouldn't want to join.

---
þ Synchronet þ Alterant | an SBBS in Docker on Pi!
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Thanks deon but I got it working when I added Sp00kNet and couldn't send the host Netmail. When sbbsecho set the folder to outbound.2bc and I couldn't get the settings to work for the domain I tried...

domain spooknet /sbbs/fido/outbound 700 ( I read set to set the zone after the outbound)

no luck I tried domain spooknet /sbbs/fido/outbound 2bc the hex code for 700 and got a BinkD error so I found the BinkD authors docs...

http://wiki.synchro.net/howto:binkd says
bP Your binkd path (Mine is /usr/bbs/sbbs/fido)
fZ your Fidonet Zone (1 for north america)
domain fidonet bP/outbound fZ
So.... for me that means
domain fidonet /sbbs/fido/outbound 1

When I setup FSXNet using the same logic of fZ (In my mind fZ = NetZone) So...... I set up
domain fsxnet /sbbs/fido/outbound 21
Makes sense to me - Then I could not send netmail to anyone but my uplink

Still working on that problem I setup Sp00kNet and tried
domain spooknet /sbbs/fido/outbound 700
Could not send netmail to even my uplink

SBBSEcho packed it up fine in outbound.2bc
I tried custom outgoing paths and thought GRRRRRRRRRRR

I went back to BinkD documentation from the author http://binkd.grumbler.org/binkdfaq.txt.en and found this

One must configure not the zone of your own address for 'domain'
keyword as one might think but the zone that should not be appended to the outbound name (i.e. the outbound subdirectory extensions are not processed
for the zone denoted in the 'domain' line).

the last part is a conflict from the synchro wiki

They gave this example

domain fidonet c:\\ftn\\outbound\\fidonet 2
domain omeganet c:\\ftn\\outbound\\fidonet 2
address 2:5070/222@fidonet 11:58/6@omeganet

It is obligatory to configure all your addresses with domains. The
outbound directory and the path should be the same everywhere (4D tosser considers all addresses to belong to one domain).

So I gave it a shot and tried this (At the top of BinkD.conf)

domain fidonet /sbbs/fido/outbound 1
domain fsxnet /sbbs/fido/outbound 1
domain spooknet /sbbs/fido/outbound 1
address 1:19/25@fidonet 21:2/160@fsxnet 700:100/39@spooknet

Like magic it started working, I can send netmail to 21:1/101 I can send netmail to my Sp00kNet hub

I hope someone else having this issue can find this long message and it helps them

Gargoyle
=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~
DarkAges BBS | Wayne, Oklahoma | Synchronet 3.17
Telnet: darkagesbbs.com | WWW: dakrgesbbs.com
FidoNet | Dove-Net | FSXNet | Doors BBSLink

---
þ Synchronet þ DarkAges BBS | darkagesbbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On 02-01-20 09:08, Rampage wrote to Gamgee <=-

i just wanted to say that while writing that long message and doing
more research, i found five more FTN networks in my mailer logs ;)

zoonet zone 31 (01f)
devnet zone 256 (100)
wennet zone 316 (13c)
musicnet zone 440 (1b8)
weirdnet zone 944 (3b0)

I'm responsible for devnet and musicnet. They were QWK only networks, and I offered myself as a gateway to FTN. The zone numbers were chosen to suit the nets

256 is the number of vaues a byte can have (8 bits).

440(Hz) is the frequency of A above middle C in music, and a common standard frequency for tuning.


... Talk is cheap -- supply exceeds demand!
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

On 02-01-20 23:00, Gargoyle wrote to Alter Ego <=-

So I gave it a shot and tried this (At the top of BinkD.conf)

domain fidonet /sbbs/fido/outbound 1
domain fsxnet /sbbs/fido/outbound 1
domain spooknet /sbbs/fido/outbound 1
address 1:19/25@fidonet 21:2/160@fsxnet 700:100/39@spooknet

Like magic it started working, I can send netmail to 21:1/101 I can
send netmail to my Sp00kNet hub

I hope someone else having this issue can find this long message and it helps them

Yeah I worked that one out early on, and have helped a few out through it. Between the behaviour of binkd and watching other 5D aware tossers and mailers in action (e.g. Mystic), I worked it out. :)


... "There is a very fine line between 'hobby' and 'mental illness.'"
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

Re: SBBSECHO
By: Gargoyle to Alter Ego on Sat Feb 01 2020 23:00:40


Gargoyle> So I gave it a shot and tried this (At the top of BinkD.conf)

Gargoyle> domain fidonet /sbbs/fido/outbound 1
Gargoyle> domain fsxnet /sbbs/fido/outbound 1
Gargoyle> domain spooknet /sbbs/fido/outbound 1
Gargoyle> address 1:19/25@fidonet 21:2/160@fsxnet 700:100/39@spooknet

this is exactly what i was speaking of in my long message where i wrote about me calling how sbbsecho handles BSO "4.5D"... it appends the hex zone number even with different outbounds for each domain... in binkd you have to lie to it by telling it to use zone 1 as you did above...


)\/(ark

---
þ Synchronet þ The SouthEast Star Mail HUB - SESTAR
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

mark lewis wrote to Gamgee <=-

FTN domains (aka 5D) were created specifically to handle multiple FTNs using the same zone numbers... it was a lot worse back in the day but duplicate zones

I don't remember duplicate zone numbers, seemed to recall FTSC or someone keeping a canonical list of node numbers. My othernet started off with zone
9, and we renumbered once we discovered the list (and that someone else was using zone 9)



... Powered By Celeron (Tualatin). Engineered for the future.
--- MultiMail/XT v0.52
þ Synchronet þ realitycheckBBS -- http://realitycheckBBS.org
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: SBBSECHO
By: poindexter FORTRAN to mark lewis on Sun Feb 02 2020 07:48:00

FTN domains (aka 5D) were created specifically to handle multiple
FTNs using the same zone numbers... it was a lot worse back in
the day but duplicate zones

I don't remember duplicate zone numbers, seemed to recall FTSC or
someone keeping a canonical list of node numbers.

that was done by a 3rd party who was interested in making a list to make it easier to locate other FTNs... kinda like the echolist used in fidonet and some few other FTNs...

My othernet started off with zone 9, and we renumbered once we
discovered the list (and that someone else was using zone 9)

i remember that change... it really wasn't necessary but it did make it easier for systems using only 4D capable tossers and mailers to be in both/all FTN domains that shared the same zone number... especially since the duplicate zone numbers would share the same outbound BSO directory... full 5D uses different outbound BSO directories for each domain ;)

4D BSO for FTN zones 1-6 and 9 eg:

/sbbs/ftn/out
/sbbs/ftn/out.002
/sbbs/ftn/out.003
/sbbs/ftn/out.004
/sbbs/ftn/out.005
/sbbs/ftn/out.006
/sbbs/ftn/out.009

5D BSO for FTN zones 1-6 and two zone 9s eg:

/sbbs/ftn/out/fidonet
/sbbs/ftn/out/fidonet.002
/sbbs/ftn/out/fidonet.003
/sbbs/ftn/out/fidonet.004
/sbbs/ftn/out/fidonet.005
/sbbs/ftn/out/fidonet.006
/sbbs/ftn/out/foobar
/sbbs/ftn/out/rocknet

the base part of those last dirs could be anything you want... the above are, again, just examples...

currently, in the case of sbbsecho and binkit, 5D is done like this...

/sbbs/ftn/out/fidonet
/sbbs/ftn/out/fidonet.002
/sbbs/ftn/out/fidonet.003
/sbbs/ftn/out/fidonet.004
/sbbs/ftn/out/fidonet.005
/sbbs/ftn/out/fidonet.006
/sbbs/ftn/out/foobar.009
/sbbs/ftn/out/rocknet.009



)\/(ark

---
þ Synchronet þ The SouthEast Star Mail HUB - SESTAR
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Lol, just goofy to me.

Gargoyle
=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~=-~
DarkAges BBS | Wayne, Oklahoma | Synchronet 3.17
Telnet: darkagesbbs.com | WWW: dakrgesbbs.com
FidoNet | Dove-Net | FSXNet | Doors BBSLink

---
þ Synchronet þ DarkAges BBS | darkagesbbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: SBBSECHO
By: Gargoyle to Rampage on Sun Feb 02 2020 07:09 pm

Lol, just goofy to me.

What's goofy to you? You didn't quote anything.

Nightfox

---
þ Synchronet þ Digital Distortion: digitaldistortionbbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: SBBSECHO
By: Nightfox to Gargoyle on Sun Feb 02 2020 17:23:33

Lol, just goofy to me.

What's goofy to you? You didn't quote anything.

the thread reader works quite well... i was able to easily find the message he was replying to ;)


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

Re: SBBSECHO
By: Gargoyle to Rampage on Sun Feb 02 2020 19:09:21


Gargoyle> Lol, just goofy to me.

in a way it is but it also makes sense depending on the implementation of the 5D BSO... at least we can lie to binkd and tell it all domains are based on zone 1 and it'll work properly with the hex extensions on BSO outbounds using different directory names for each domain... there's still some love needed in that area but for now, it works...


)\/(ark

---
þ Synchronet þ The SouthEast Star Mail HUB - SESTAR
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: SBBSECHO
By: mark lewis to Nightfox on Sun Feb 02 2020 09:05 pm

What's goofy to you? You didn't quote anything.

the thread reader works quite well... i was able to easily find the message he was replying to ;)

Which thread reader?

Nightfox

---
þ Synchronet þ Digital Distortion: digitaldistortionbbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On 02-02-20 17:39, Rampage wrote to poindexter FORTRAN <=-

5D BSO for FTN zones 1-6 and two zone 9s eg:

/sbbs/ftn/out/fidonet
/sbbs/ftn/out/fidonet.002
/sbbs/ftn/out/fidonet.003
/sbbs/ftn/out/fidonet.004
/sbbs/ftn/out/fidonet.005
/sbbs/ftn/out/fidonet.006
/sbbs/ftn/out/foobar
/sbbs/ftn/out/rocknet

the base part of those last dirs could be anything you want... the
above are, again, just examples...

currently, in the case of sbbsecho and binkit, 5D is done like this...

/sbbs/ftn/out/fidonet
/sbbs/ftn/out/fidonet.002
/sbbs/ftn/out/fidonet.003
/sbbs/ftn/out/fidonet.004
/sbbs/ftn/out/fidonet.005
/sbbs/ftn/out/fidonet.006
/sbbs/ftn/out/foobar.009
/sbbs/ftn/out/rocknet.009

For the record, Mystic also uses the second layout (i.e. identical behaviour to
SBBSEcho/BinkIT). I don't know what other 5D aware tossers are out there (I only know SBBSEcho and mutil in this category), so I have no other examples of 5D BSO structure and behaviour.

As a mailer, BinkD will do whatever you tell it to. It can use either BSO layout, depending on configuration, but it's really the tosser that seems to control this. I had to make BinkD match SBBSEcho (which was trivial).


... Jargon is used as a means of succeeding by, not simplifying.
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

On 02-02-20 21:05, mark lewis wrote to Nightfox <=-

Re: SBBSECHO
By: Nightfox to Gargoyle on Sun Feb 02 2020 17:23:33

Lol, just goofy to me.

What's goofy to you? You didn't quote anything.

the thread reader works quite well... i was able to easily find the message he was replying to ;)

We're not all readong online.


... Hell is kept warm with profane burners.
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

On 02-02-20 20:58, Rampage wrote to Gargoyle <=-

Re: SBBSECHO
By: Gargoyle to Rampage on Sun Feb 02 2020 19:09:21

Gargoyle> Lol, just goofy to me.

in a way it is but it also makes sense depending on the implementation
of the 5D BSO... at least we can lie to binkd and tell it all domains
are based on zone 1 and it'll work properly with the hex extensions on
BSO outbounds using different directory names for each domain...
there's still some love needed in that area but for now, it works...

I do the same thing, except my default zone is Z3. :)


... An Elephant; A Mouse built to government specifications.
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

Re: SBBSECHO
By: Nightfox to mark lewis on Sun Feb 02 2020 21:12:40

What's goofy to you? You didn't quote anything.

the thread reader works quite well... i was able to easily find the

message he was replying to ;)

Which thread reader?

the '*' when reading messages with the default sbbs code...


)\/(ark

---
þ Synchronet þ The SouthEast Star Mail HUB - SESTAR
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: SBBSECHO
By: Rampage to Nightfox on Mon Feb 03 2020 06:44 am

the thread reader works quite well... i was able to easily find
the message he was replying to ;)

Which thread reader?

the '*' when reading messages with the default sbbs code...

Ah, I see.. I use my own message reader and haven't used the stock Synchronet reader in a while. I'll have to check that out.

Nightfox

---
þ Synchronet þ Digital Distortion: digitaldistortionbbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Tony,

440(Hz) is the frequency of A above middle C in music, and a common standard
frequency for tuning.

Boy, I haven't heard that term in awhile!!

Reminds me of 2 music shirts I saw at the Florida All State Chorus in
1977 in Orlando. A friend of mine in choir were the only 2 from south
Florida to make the festival.

The shirts had musical symbols, and what to do with them.

1) I'm a Fermata. Hold Me.
2) I'm an Accent. Attack Me.

Guess they're looking for nothing but treble, and are rather bass in
their discussions...one has to make note of that. <G>

Daryl

* OLX 1.53 * Before drawing boards, where did they go back to??
--- SBBSecho 3.10-Win32
* Origin: The Thunderbolt BBS - tbolt.synchro.net (1:19/33)

On 02-04-20 22:55, Daryl Stout wrote to TONY LANGDON <=-

Tony,

440(Hz) is the frequency of A above middle C in music, and a common

tandard

frequency for tuning.

Boy, I haven't heard that term in awhile!!

:)

1) I'm a Fermata. Hold Me.
2) I'm an Accent. Attack Me.

Clever. :)

Guess they're looking for nothing but treble, and are rather bass in their discussions...one has to make note of that. <G>

Oh dear. :D


... Potted meat: all the other stuff too vile for hot dogs.
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)