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.
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.
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]
Route = 21:3/100
[node:21:3/100@fsxnet]
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.
I guess I'm surprised that crash forces direct, but maybe that's from an inadequate understanding of the event system.
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.
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).
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?
There is a global setting for all Netmail. I just checked... It's in SCFG, Networks, Fidonet. Netmail Defaults to Crash/Direct etc.
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?
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.
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.
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.
| Sysop: | Weed Hopper |
|---|---|
| Location: | Clearwater, FL |
| Users: | 12 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 22:54:54 |
| Calls: | 116 |
| Calls today: | 1 |
| Files: | 50,356 |
| D/L today: |
90 files (17,592K bytes) |
| Messages: | 299,262 |