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:I have Domain and Name empty
Address 21:1/100
Domain fsxnet
Name Paul Hayton
Direct YesI have Direct No
Uplink for Message Groups fsxNetUplink is empty. If you're not a hub yourself, you don't need this.
Route To 21:1/100Route To is Disabled
Address 21:ALLDomain and Name are empty
Domain fsxnet
Name
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\.
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
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
Any tips where to focus in on?
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
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
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).
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.
Sysop: | Angel Ripoll |
---|---|
Location: | Madrid, Spain |
Users: | 13 |
Nodes: | 8 (0 / 8) |
Uptime: | 76:34:51 |
Calls: | 386 |
Files: | 15,077 |
Messages: | 64,827 |