I'm really struggling here with routing netmail. I added fsxNet using the
init script (which has some fatal fsxNet issues I'll submit a bug report or change for). After fixing the issues the script created, echomail is working properly with the hub. But no matter what I've tried and what people have suggested, netmail is still trying to route directly. Can someone offer some insight? Logs and config files below.

Thanks,
Andre


What I'm trying:
----------------
netmail
ping@21:2/116
subject/body just have test nonsense in them.
----------------


syslog error where you can see it route directly (21:2/116) instead of
through the hub (21:3/100)
----------------

Feb 6 09:28:51 BBS-Nano synchronet: term Node 1 <Andre> sent NetMail to ping (21:2/116)
Feb 6 09:28:54 BBS-Nano synchronet: evnt DAILY Semaphore signaled for Timed Event: FIDOOUT
Feb 6 09:28:54 BBS-Nano synchronet: evnt FIDOOUT Running native timed event: FIDOOUT
Feb 6 09:28:54 BBS-Nano synchronet: evnt FIDOOUT Timed event: FIDOOUT
returned 0
Feb 6 09:28:59 BBS-Nano synchronet: evnt DAILY Semaphore signaled for Timed Event: BINKOUT
Feb 6 09:28:59 BBS-Nano synchronet: evnt BINKOUT Running timed event:
BINKOUT
Feb 6 09:28:59 BBS-Nano synchronet: evnt BINKOUT BinkIT/2.41 invoked with options:
Feb 6 09:28:59 BBS-Nano synchronet: evnt BINKOUT Attempting callout for 21:2/116@fsxnet, file: /home/bbs/synchronet/fido/outbound.015/00020074.cut
Feb 6 09:28:59 BBS-Nano synchronet: evnt BINKOUT JSBinkP/4 callout to 21:2/116@fsxnet started
Feb 6 09:28:59 BBS-Nano synchronet: evnt BINKOUT Connecting to
21:2/116@fsxnet at f116.n2.z21.fsxnet.nz:24554
Feb 6 09:29:00 BBS-Nano systemd-resolved[560]: Server returned error
NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Feb 6 09:29:00 BBS-Nano systemd-resolved[560]: message repeated 3 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018- 0001, retrying transaction with reduced feature level UDP.]
Feb 6 09:29:00 BBS-Nano synchronet: evnt BINKOUT Connection to f116.n2.z21.fsxnet.nz:24554 failed (Error: Name or service not known).



Relevant parts (I think) of sbbsecho.ini:
----------------
[node:21:ALL]
Name =
Comment = Everyone in zone 21
Archive = None
PacketType = 2+
PacketPwd =
AreaFix = false
AreaFixPwd =
SessionPwd =
TicFilePwd =
Inbox =
Outbox =
Passive = false
Direct = false
Notify = false
Keys =
Status = Crash
Route = 21:3/100
GroupHub =
BinkpHost =
BinkpPort = 24554
BinkpPoll = false
BinkpPlainAuthOnly = false
BinkpAllowPlainAuth = false
BinkpAllowPlainText = true
BinkpTLS = false
BinkpSourceAddress =


[node:21:3/100@fsxnet]
Name = <Deon>
Comment = <his email>
Archive = None
PacketType = 2+
PacketPwd = <redacted>
AreaFix = true
AreaFixPwd = <redacted>
SessionPwd = <redacted>
TicFilePwd = <redacted>
Inbox =
Outbox =
Passive = false
Direct = false
Notify = false
Keys =
Status = Crash
GroupHub = fsxNet
BinkpHost = alterant.leenooks.net
BinkpPort = 24554
BinkpPoll = true
BinkpPlainAuthOnly = false
BinkpAllowPlainAuth = false
BinkpAllowPlainText = true
BinkpTLS = false
BinkpSourceAddress =

---
þ Synchronet þ Radio Mentor BBS - bbs.radiomentor.org
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Routing netmail problem
By: Andre to All on Sat Feb 06 2021 09:43 am

properly with the hub. But no matter what I've tried and what people have suggested, netmail is still trying to route directly. Can someone offer some
insight? Logs and config files below.

You have your netmail set to Crash. Setting netmail to Crash or Direct will send it direct. You want Netmail to route, so set it to Normal. I can't remember if the setting is in EchoCfg or in SCFG, but its there.

Bob Roberts

---
þ Synchronet þ Halls of Valhalla =San=Francisco= hovalbbs.com:2333
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

You have your netmail set to Crash. Setting netmail to Crash or Direct will send it direct. You want Netmail to route, so set it to Normal. I can't remember if the setting is in EchoCfg or in SCFG, but its there.

It's in echocfg. Someone had mentioned that on the Discord server as well. Changed it to Normal for both the hub and the 21:ALL, but hasn't seemed to make a difference.


- Andre

---
þ Synchronet þ Radio Mentor BBS - bbs.radiomentor.org
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

You have your netmail set to Crash. Setting netmail to Crash or Direct will send it direct. You want Netmail to route, so set it to Normal. I can't remember if the setting is in EchoCfg or in SCFG, but its there.

It's in echocfg. Someone had mentioned that on the Discord server as well. Changed it to Normal for both the hub and the 21:ALL, but hasn't seemed to make a difference.

Found it. I had, some time ago, set netmail to default to crash in scfg.

wkitty42 from the Discord server put a lot of effort into helping me troubleshoot, including understanding the outbound extension meanings and whatnot.

I guess I'm surprised that crash forces direct, but maybe that's from an inadequate understanding of the event system.

Thanks,
Andre

---
þ Synchronet þ Radio Mentor BBS - bbs.radiomentor.org
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Routing netmail problem
By: Andre to All on Sat Feb 06 2021 09:43 am

I'm really struggling here with routing netmail. I added fsxNet using the init script (which has some fatal fsxNet issues I'll submit a bug report or change for). After fixing the issues the script created, echomail is working properly with the hub. But no matter what I've tried and what people have suggested, netmail is still trying to route directly. Can someone offer some insight? Logs and config files below.

Thanks,
Andre

What I'm trying:
----------------
netmail
ping@21:2/116
subject/body just have test nonsense in them.
----------------

syslog error where you can see it route directly (21:2/116) instead of through the hub (21:3/100)
----------------

Feb 6 09:28:51 BBS-Nano synchronet: term Node 1 <Andre> sent NetMail to ping (21:2/116)
Feb 6 09:28:54 BBS-Nano synchronet: evnt DAILY Semaphore signaled for Timed Event: FIDOOUT
Feb 6 09:28:54 BBS-Nano synchronet: evnt FIDOOUT Running native timed event: FIDOOUT
Feb 6 09:28:54 BBS-Nano synchronet: evnt FIDOOUT Timed event: FIDOOUT returned 0
Feb 6 09:28:59 BBS-Nano synchronet: evnt DAILY Semaphore signaled for Timed Event: BINKOUT
Feb 6 09:28:59 BBS-Nano synchronet: evnt BINKOUT Running timed event: BINKOUT
Feb 6 09:28:59 BBS-Nano synchronet: evnt BINKOUT BinkIT/2.41 invoked with options:
Feb 6 09:28:59 BBS-Nano synchronet: evnt BINKOUT Attempting callout for 21:2/116@fsxnet, file: /home/bbs/synchronet/fido/outbound.015/00020074.cut Feb 6 09:28:59 BBS-Nano synchronet: evnt BINKOUT JSBinkP/4 callout to 21:2/116@fsxnet started
Feb 6 09:28:59 BBS-Nano synchronet: evnt BINKOUT Connecting to 21:2/116@fsxnet at f116.n2.z21.fsxnet.nz:24554
Feb 6 09:29:00 BBS-Nano systemd-resolved[560]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Feb 6 09:29:00 BBS-Nano systemd-resolved[560]: message repeated 3 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018- 0001, retrying transaction with reduced feature level UDP.]
Feb 6 09:29:00 BBS-Nano synchronet: evnt BINKOUT Connection to f116.n2.z21.fsxnet.nz:24554 failed (Error: Name or service not known).

Routing happens in SBBSecho. So the log you want to be looking at is data/sbbsecho.log.

Relevant parts (I think) of sbbsecho.ini:
----------------
[node:21:ALL]

Route = 21:3/100

That's the important part.

[node:21:3/100@fsxnet]

Are those the only 2 links or do you have *any* others in your sbbsecho.ini for 21:*?

Again, look at the sbbsecho.log for the routing.
--
digital man

Rush quote #27:
Growing up it all seems so one-sided, opinions all provided
Norco, CA WX: 76.7øF, 17.0% humidity, 3 mph ESE wind, 0.00 inches rain/24hrs --- SBBSecho 3.12-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Routing netmail problem
By: Andre to All on Sat Feb 06 2021 09:43:03


Andre> I'm really struggling here with routing netmail.

we took care of this on discord yesterday, right?


)\/(ark

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

Re: Re: Routing netmail problem
By: Andre to Bob Roberts on Sat Feb 06 2021 13:52:18


Andre> wkitty42 from the Discord server put a lot of effort into helping

yup... that's me... this is my other account i use on IRC and my BBS ;)

Andre> me troubleshoot, including understanding the outbound extension
Andre> meanings and whatnot.

i'm glad it helped and that you got it working...


)\/(ark

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

Re: Re: Routing netmail problem
By: Andre to Bob Roberts on Sat Feb 06 2021 01:24 pm

You have your netmail set to Crash. Setting netmail to Crash or Direct will
send it direct. You want Netmail to route, so set it to Normal. I can't
remember if the setting is in EchoCfg or in SCFG, but its there.

It's in echocfg. Someone had mentioned that on the Discord server as well. Changed it to Normal for both the hub and the 21:ALL, but hasn't seemed to make
a difference.

There is a global setting for all Netmail. I just checked... It's in SCFG, Networks, Fidonet. Netmail Defaults to Crash/Direct etc.

Bob Roberts

---
þ Synchronet þ Halls of Valhalla =San=Francisco= hovalbbs.com:2333
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: Routing netmail problem
By: Andre to Bob Roberts on Sat Feb 06 2021 01:52 pm

I guess I'm surprised that crash forces direct, but maybe that's from an inadequate understanding of the event system.

I had the EXACT same problem when I first started with SBBS. I didn't realize Crash would also force Direct. I thought it would just send it right away. But Normal already sends it right away, so Crash sends it Right Away AND sends it Direct. Which I guess is just a hold over from the old days when Fidonet was on Dialup Modems.

If you setup the Nodelist support in EchoCfg under Domains, then your Direct stuff will get delivered. And yes, DM will tell you it doesn't need it because it can lookup the info via DNS, but in my experience that only works with Fido and not well with the Othernets.

I spent some time setting up the TickFix handler for nodelists for all my networks, and now the nodelists update automatically. Except for a couple that don't send TIC files and just dump the nodelist in my inbound. And AmigaNet which compresses with LHA... and TickFix handler can't handle it.

Bob Roberts

---
þ Synchronet þ Halls of Valhalla =San=Francisco= hovalbbs.com:2333
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Bob Roberts wrote to Andre <=-

I spent some time setting up the TickFix handler for nodelists
for all my networks, and now the nodelists update automatically.
Except for a couple that don't send TIC files and just dump the
nodelist in my inbound. And AmigaNet which compresses with
LHA... and TickFix handler can't handle it.

Sounds like LHA is not set up as a valid Archiver in sbbsecho.ini .



... Error - Operator out of memory!
--- MultiMail/Linux v0.52
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Routing netmail problem
By: Andre to All on Sat Feb 06 2021 09:43 am

I'm really struggling here with routing netmail. I added fsxNet using the init script (which has some fatal fsxNet issues I'll submit a bug report or change for).

Did you submit a bug report yet?
--
digital man

This Is Spinal Tap quote #29:
I find lost luggage. I locate mandolin strings in the middle of Austin!
Norco, CA WX: 63.7øF, 30.0% humidity, 5 mph E wind, 0.00 inches rain/24hrs
--- SBBSecho 3.12-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Routing netmail problem
By: Digital Man to Andre on Sun Feb 14 2021 02:04 pm

Re: Routing netmail problem
By: Andre to All on Sat Feb 06 2021 09:43 am

I'm really struggling here with routing netmail. I added fsxNet using the init script (which has some fatal fsxNet issues I'll submit a bug report or change for).

Did you submit a bug report yet?

Still haven't seen that bug report. :-(
--
digital man

Rush quote #2:
If the future's looking dark, we're the ones who have to shine.
Norco, CA WX: 51.6øF, 70.0% humidity, 6 mph NNW wind, 0.00 inches rain/24hrs --- SBBSecho 3.13-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: Routing netmail probl
By: Bob Roberts to Andre on Sun Feb 07 2021 09:11 am

There is a global setting for all Netmail. I just checked... It's in SCFG, Networks, Fidonet. Netmail Defaults to Crash/Direct etc.

Hi Rob,

I just ran in to this issue myself (I am quoting a message from February '21), where this setting seems to be an override, not a default. If one sets netmail to crash in scfg, routing in sbbsecho.ini is ignored.

I was wondering if the intention was for this to override everything or if it should simply be a default except where routing configuration elsewhere is in play?

Thanks.

---
þ Synchronet þ ... The Basement ... Not really open yet.
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: Routing netmail problem
By: Trikester to Digital Man on Sat Jan 08 2022 04:16 pm

Re: Re: Routing netmail probl
By: Bob Roberts to Andre on Sun Feb 07 2021 09:11 am

There is a global setting for all Netmail. I just checked... It's in SCFG, Networks, Fidonet. Netmail Defaults to Crash/Direct etc.

Hi Rob,

I just ran in to this issue myself (I am quoting a message from February '21), where this setting seems to be an override, not a default. If one sets netmail to crash in scfg, routing in sbbsecho.ini is ignored.

I was wondering if the intention was for this to override everything or if it should simply be a default except where routing configuration elsewhere is in play?

I don't really understand the question. "Crash" (for FidoNet) means immediate and direct. So... by definition, not routed.
--
digital man (rob)

Rush quote #5:
Some are born to rule the world, to live their fantasies
Norco, CA WX: 49.4øF, 87.0% humidity, 0 mph SE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.14-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: Routing netmail problem
By: Digital Man to Trikester on Sat Jan 08 2022 10:33 pm

There is a global setting for all Netmail. I just checked... It's in SCFG, Networks, Fidonet. Netmail Defaults to Crash/Direct etc.

Hi Rob,

I just ran in to this issue myself (I am quoting a message from February '21), where this setting seems to be an override, not a default. If one sets netmail to crash in scfg, routing in sbbsecho.ini is ignored.

I was wondering if the intention was for this to override everything or if it should simply be a default except where routing configuration elsewhere is in play?

I don't really understand the question. "Crash" (for FidoNet) means immediate and direct. So... by definition, not routed.

Hmm... I guess I see it as the "Defaults to..." wording in the setting suggests it would be a setting that could be overridden elsewhere. If it's not set elsewhere, netmail would default to crash.

But, since we're able to configure in sbbsecho.ini various settings for nodes, hubs, and turn routing on or off, things that should affect mail delivery, then when netmail is posted to a node affected by those settings that the 'defaults' should no longer apply?

ie: Because of it's overriding nature, it's easier to set up no crash mail except for the nodes you want mail crashed to, than to crash to most nodes but have some that you don't crash to and route elsewhere.

---
þ Synchronet þ ... The Basement ... Not really open yet.
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On 2022 Jan 09 09:15:58, you wrote to Digital Man:

ie: Because of it's overriding nature, it's easier to set up no crash mail except for the nodes you want mail crashed to, than to crash to most nodes but have some that you don't crash to and route elsewhere.

remember that there is a difference between setting a netmail message to crash and the routing statement of crash which is for packets and bundles... netmail with normal status can easily be packed into packets routed with crash status... the reverse, on the other hand, is not a good thing, though...

)\/(ark

"The soul of a small kitten in the body of a mighty dragon. Look on my majesty, ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!"
... Best way to stop a runaway horse: Place a bet on it.
---
* Origin: (1:3634/12.73)

Re: Re: Routing netmail problem
By: Trikester to Digital Man on Sun Jan 09 2022 09:15 am

Re: Re: Routing netmail problem
By: Digital Man to Trikester on Sat Jan 08 2022 10:33 pm

There is a global setting for all Netmail. I just checked... It's in SCFG, Networks, Fidonet. Netmail Defaults to Crash/Direct etc.

Hi Rob,

I just ran in to this issue myself (I am quoting a message from February '21), where this setting seems to be an override, not a default. If one sets netmail to crash in scfg, routing in sbbsecho.ini is ignored.

I was wondering if the intention was for this to override everything or if it should simply be a default except where routing configuration elsewhere is in play?

I don't really understand the question. "Crash" (for FidoNet) means immediate and direct. So... by definition, not routed.

Hmm... I guess I see it as the "Defaults to..." wording in the setting suggests it would be a setting that could be overridden elsewhere. If it's not set elsewhere, netmail would default to crash.

That's correct, and that "elsewhere" is in the subject of the message. https://synchro.net/docs/networking.html#SendingFidoNetNetMail

But if you're setting is for netmail to be sent as crash (in SCFG), then all netmail created within the terminal server will be set to crash.

But, since we're able to configure in sbbsecho.ini various settings for nodes, hubs, and turn routing on or off, things that should affect mail delivery, then when netmail is posted to a node affected by those settings that the 'defaults' should no longer apply?

The terminal server has no knowledge of what nodes you have configured in sbbsecho.ini. And I don't really see the connection either. The SCFG setting you're talking about is impacting how netmail is created by the terminal server (BBS users using the traditional BBS user experience).

ie: Because of it's overriding nature, it's easier to set up no crash mail except for the nodes you want mail crashed to, than to crash to most nodes but have some that you don't crash to and route elsewhere.

If you don't want to crash netmail (created in the terminal server) to all nodes, then don't set that SCFG setting to crash.
--
digital man (rob)

Sling Blade quote #7:
Karl: I don't reckon the Good Lord would send anybody like you to Hades.
Norco, CA WX: 71.1øF, 22.0% humidity, 0 mph SE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.14-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: Routing netmail problem
By: Digital Man to Trikester on Sun Jan 09 2022 01:02 pm

Thanks muchly for the additional info. Between your and Mark's extra information I have a better understanding why that's the way that it is.

I have definitely un-set it in scfg.

---
þ Synchronet þ ... The Basement ... Not really open yet.
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)