Good morning, all!

I think this might be related to the "best match" line from what I was reading from a few posts, but wanted to ask for some clarification on netmail/echomail routing. I'm able to communicate directly to my hub with no issues, however, it seems like I'm running into an issue trying to send to another address in the fsxNet network. Instead of routing through the hub, it's trying to send the mail direct to their address.

Here's how I have the two linked nodes configured:

Address 21:1/100
Domain fsxnet
Name Paul Hayton
Comment fsxNet coordinator
Archive Type ZIP
Packet Type 2+
Packet Password
Session Password xxxxxxxxxxxxxx
TIC File Password
AreaFix Support Yes
AreaFix Password xxxxxxxxxxxxxx
EchoList Keys
Status Normal
Direct Yes
Passive No
Send Notify List No
Uplink for Message Groups fsxNet
Local Address (AKA) Best Match
Route To 21:1/100
Inbox Directory
Outbox Directory
BinkP Settings...

---------------------------------------------------

Address 21:ALL
Domain fsxnet
Name
Comment everyone in zone 21
Archive Type None
Packet Type 2+
Packet Password
Session Password
TIC File Password
AreaFix Support No
AreaFix Password
EchoList Keys
Status Normal
Direct No
Passive No
Send Notify List No
Uplink for Message Groups
Local Address (AKA) Best Match
Route To 21:1/100


The domain in echocfg looks like this:

Name fsxnet
Zones 21
DNS Suffix fsxnet.nz
Outbound Root ../fido/outbound
NodeList


When sending outside my hub's address, (in this case 21:2/116) this is what I'm seeing in the log:

7/18 10:30:54a BINKOUT Attempting callout for 21:2/116@fsxnet, file: C:\sbbs\fido\outbound.015\00020074.cut
7/18 10:30:54a BINKOUT JSBinkP/4 callout to 21:2/116@fsxnet started
7/18 10:30:54a BINKOUT connecting to 21:2/116@fsxnet at undefined
7/18 10:30:54a BINKOUT Connecting to 21:2/116@fsxnet at f116.n2.z21.fsxnet.nz:24554
7/18 10:31:05a BINKOUT Connection to f116.n2.z21.fsxnet.nz:24554 failed (Error: Unable to connect).
7/18 10:31:05a BINKOUT Unlocking C:\sbbs\fido\outbound.015\00020074.bsy.
7/18 10:31:05a BINKOUT No flow files to be processed.
7/18 10:31:05a BINKOUT Done checking in C:\sbbs\fido\outbound.015\.


Any tips where to focus in on?

Thanks again for any help!
--rob
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On Thu, 18 Jul 2024 07:55:00 -0700
"smooth0401" (VERT) <VERT!smooth0401@endofthelinebbs.com> wrote:

Good morning, all!

I think this might be related to the "best match" line from what I
was reading from a few posts, but wanted to ask for some
clarification on netmail/echomail routing. I'm able to communicate
directly to my hub with no issues, however, it seems like I'm running
into an issue trying to send to another address in the fsxNet
network. Instead of routing through the hub, it's trying to send the
mail direct to their address.

Let's compare. Keep in mind I use binkd and not binkit.

Here's how I have the two linked nodes configured:

Address 21:1/100
Domain fsxnet
Name Paul Hayton

I have Domain and Name empty

Direct Yes

I have Direct No

Uplink for Message Groups fsxNet

Uplink is empty. If you're not a hub yourself, you don't need this.

Route To 21:1/100

Route To is Disabled

Address 21:ALL
Domain fsxnet
Name

Domain and Name are empty

Otherwise the same.

When sending outside my hub's address, (in this case 21:2/116) this
is what I'm seeing in the log:

7/18 10:30:54a BINKOUT Attempting callout for 21:2/116@fsxnet,
file: C:\sbbs\fido\outbound.015\00020074.cut
7/18 10:30:54a BINKOUT JSBinkP/4 callout to 21:2/116@fsxnet
started 7/18 10:30:54a BINKOUT connecting to 21:2/116@fsxnet at
undefined 7/18 10:30:54a BINKOUT Connecting to 21:2/116@fsxnet at f116.n2.z21.fsxnet.nz:24554
7/18 10:31:05a BINKOUT Connection to f116.n2.z21.fsxnet.nz:24554
failed (Error: Unable to connect).
7/18 10:31:05a BINKOUT Unlocking
C:\sbbs\fido\outbound.015\00020074.bsy. 7/18 10:31:05a BINKOUT No
flow files to be processed. 7/18 10:31:05a BINKOUT Done checking in C:\sbbs\fido\outbound.015\.

Not sure if matching my settings will fix your issue but worth a try.
--
End Of The Line BBS - Plano, TX
telnet endofthelinebbs.com 23
---
þ Synchronet þ End Of The Line BBS - endofthelinebbs.com
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: routing outside of hub for fsxnet (and fido)
By: smooth0401 to ALL on Thu Jul 18 2024 07:55 am

Good morning, all!

I think this might be related to the "best match" line from what I was reading from a few posts, but wanted to ask for some clarification on netmail/echomail routing. I'm able to communicate directly to my hub with no issues, however, it seems like I'm running into an issue trying to send to another address in the fsxNet network. Instead of routing through the hub, it's trying to send the mail direct to their address.

Here's how I have the two linked nodes configured:

Address 21:1/100
Domain fsxnet
Name Paul Hayton
Comment fsxNet coordinator
Archive Type ZIP
Packet Type 2+
Packet Password
Session Password xxxxxxxxxxxxxx
TIC File Password
AreaFix Support Yes
AreaFix Password xxxxxxxxxxxxxx
EchoList Keys
Status Normal
Direct Yes
Passive No
Send Notify List No
Uplink for Message Groups fsxNet
Local Address (AKA) Best Match
Route To 21:1/100

You've defined a circular route there ^^^. This routing should disabled.

Address 21:ALL
Domain fsxnet
Name
Comment everyone in zone 21
Archive Type None
Packet Type 2+
Packet Password
Session Password
TIC File Password
AreaFix Support No
AreaFix Password
EchoList Keys
Status Normal
Direct No
Passive No
Send Notify List No
Uplink for Message Groups
Local Address (AKA) Best Match
Route To 21:1/100

The domain in echocfg looks like this:

Name fsxnet
Zones 21
DNS Suffix fsxnet.nz
Outbound Root ../fido/outbound
NodeList

When sending outside my hub's address, (in this case 21:2/116) this is what

Sending what exactly? Crash/direct netmail is normally sent direct. Did you send crash or direct netmail?

Any tips where to focus in on?

The sbbsecho.log file should contain additional clues.
--
digital man (rob)

Rush quote #83:
Bruised and sullen stormclouds have the light of day obscured
Norco, CA WX: 80.7øF, 59.0% humidity, 2 mph SSW wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Ah, what's interesting is Synchro actually reverted the Route to on the 21:1/100 linked node record, so I guess we're covered there.

I just hit "E" and then "N" to send a netmail... I figured since it was in Zone 21 and the config for 21:All was set to Direct:No that it'd route that message through the "Route to: 21:1/100" but it doesn't sound like that logic is sound. I know Synchro doesn't use nodelists, but I did see under domains where I could import one... would that help in this case?

Here's a snippit from the sbbsecho.log:

2024-07-18 10:10:23 Created NetMail (1.msg) from Rob Olsen (21:1/234) to deon (21:2/116), attr: 0183, subject: fsxnet filebases with synchronet
2024-07-18 10:10:23 Packing NetMail (1.msg) from Rob Olsen (21:1/234) to deon (21:2/116), attr: 0183, subject: fsxnet filebases with synchronet
2024-07-18 10:10:23 SBBSecho (PID 5000) exiting with error level 0, NetMail(0 imported, 1 exported, 1 packed)

Also wanted to thank nelgin for their reply as well!

--rob
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: routing outside of hub for fsxnet (and fido)
By: smooth0401 to Digital Man on Thu Jul 18 2024 12:02 pm

Ah, what's interesting is Synchro actually reverted the Route to on the 21:1/100 linked node record, so I guess we're covered there.

echocfg likely did that for you.

I just hit "E" and then "N" to send a netmail... I figured since it was in Zone 21 and the config for 21:All was set to Direct:No that it'd route that message through the "Route to: 21:1/100" but it doesn't sound like that logic is sound. I know Synchro doesn't use nodelists, but I did see under domains where I could import one... would that help in this case?

No, a nodelist wouldn't make any difference.

Here's a snippit from the sbbsecho.log:

2024-07-18 10:10:23 Created NetMail (1.msg) from Rob Olsen (21:1/234) to deon (21:2/116), attr: 0183, subject: fsxnet filebases with synchronet

I can see from that netmail attr value that the crash attribute is set.

the latest & greatest versions of SBBSecho actually give you the human-readable interpretation of those attribute flags (e.g. "crash"), but yes, crash mail is not routed. So change your configuration in SCFG->Networks->FidoNet, if you want routed mail to be the default.
--
digital man (rob)

Sling Blade quote #17:
Charles Bushman: A shovel just makes too goddamned much racket.
Norco, CA WX: 89.0øF, 49.0% humidity, 6 mph WSW wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Hola Smooth0401!

18 Jul 24 07:55, smooth0401 dijo a ALL:

Good morning, all!

I think this might be related to the "best match" line from what I was reading from a few posts, but wanted to ask for some clarification on netmail/echomail routing. I'm able to communicate directly to my hub with no issues, however, it seems like I'm running into an issue trying to send to another address in the fsxNet network. Instead of routing through the hub, it's trying to send the mail direct to their address.

I have two fsxnet nodes. One in the node that acts as a hub (21:1/191) and the other in the BBS with synchronet (21:1/192). 192 routes everything through 191, which is responsible for routing it to the main fsxnet nodes. 21:1/100

NOTE: I'm sure the configuration can be improved :) Any help is welcome

Here's how I have the two linked nodes configured:

Address 21:1/100
Domain fsxnet
Name Paul Hayton
Comment fsxNet coordinator
Archive Type ZIP
Packet Type 2+
Packet Password
Session Password xxxxxxxxxxxxxx
TIC File Password
AreaFix Support Yes
AreaFix Password xxxxxxxxxxxxxx
EchoList Keys
Status Normal
Direct Yes
Passive No
Send Notify List No
Uplink for Message Groups fsxNet
Local Address (AKA) Best Match
Route To 21:1/100
Inbox Directory
Outbox Directory
BinkP Settings...

---------------------------------------------------

mine:

[node:21:1/191]
Name = Zruspas's HUB FSXNET
Comment =
Archive = None
PacketType = 2+
PacketPwd = xxx
AreaFix = true
AreaFixPwd = xxx
SessionPwd = xxx
TicFilePwd = xxx
Inbox =
Outbox =
Passive = false
Direct = false
Notify = false
Keys =
Status = Crash
LocalAddress = 21:1/192
GroupHub = FSXNET
BinkpHost = bbs.zruspas.org
BinkpPort = 24554
BinkpPoll = true
BinkpPlainAuthOnly = false
BinkpAllowPlainAuth = true
BinkpAllowPlainText = true
BinkpTLS = false
BinkpSourceAddress =

Address 21:ALL
Domain fsxnet
Name
Comment everyone in zone 21
Archive Type None
Packet Type 2+
Packet Password
Session Password
TIC File Password
AreaFix Support No
AreaFix Password
EchoList Keys
Status Normal
Direct No
Passive No
Send Notify List No
Uplink for Message Groups
Local Address (AKA) Best Match
Route To 21:1/100

mine:

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

I hope it helps you

Un saludo,
Angel Ripoll
aripoll @ zruspas.org

--- GoldED+/LNX 1.1.5-b20240209 + HPT 1.9 + Binkd 1.1 en Debian
* Origin: Synchronet - bbs.zruspas.org - Zruspa's BBS - (2:341/66)

Re: routing outside of hub for fsxnet (and fido)
By: smooth0401 to ALL on Thu Jul 18 2024 07:55 am

Howdy,

7/18 10:30:54a BINKOUT connecting to 21:2/116@fsxnet at undefined
7/18 10:30:54a BINKOUT Connecting to 21:2/116@fsxnet at f116.n2.z21.fsxnet.nz:24554
7/18 10:31:05a BINKOUT Connection to f116.n2.z21.fsxnet.nz:24554 failed (Error: Unable to connect).

Oddly, f116.n2.z21.fsxnet.nz should resolve even though you havent explicitely defined it. Not sure why it shows as undefined.


...ëîåï

---
þ Synchronet þ AnsiTEX bringing back videotex but with ANSI
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: routing outside of hub for fsxnet (and fido)
By: deon to smooth0401 on Fri Jul 19 2024 08:07 am

Re: routing outside of hub for fsxnet (and fido)
By: smooth0401 to ALL on Thu Jul 18 2024 07:55 am

Howdy,

7/18 10:30:54a BINKOUT connecting to 21:2/116@fsxnet at undefined
7/18 10:30:54a BINKOUT Connecting to 21:2/116@fsxnet at f116.n2.z21.fsxnet.nz:24554
7/18 10:31:05a BINKOUT Connection to f116.n2.z21.fsxnet.nz:24554 failed (Error: Unable to connect).

Oddly, f116.n2.z21.fsxnet.nz should resolve even though you havent explicitely defined it. Not sure why it shows as undefined.

Sorry, hit send too quickly. I realised as I was typing this, it might be that my systems were offline yesterday due to a power failure, so that might be why...


...ëîåï

---
þ Synchronet þ AnsiTEX bringing back videotex but with ANSI
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Thanks for everyone's replies! I'll look through logs, check the crash attribute, and try you again deon.
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)