Subject: Host-routed netmail to points
@MSGID: <628E5AD1.64191.dove.sync@realitycheckbbs.org>
@TZ: c1e0
Hi, DM et. al,
I have a question about host-routed netmail to points. I've been banging my head on this for some time and am running into issues.
I'm an RC in fidonet and route netmail for my region. netmail from downlinks passes through OK to destination nodes, but if a downlink sends mail for a point, it appears to sit on my system and is not routed to the bossnode. I found a couple errors in my log where SBBS was trying to send to the point and failing.
How can I set sbbsecho to crashmail the boss node when point mail arrives?
So it looks like the destination point node must not be configured in sbbsecho.ini while the boss node must be configured in sbbsecho.ini for thi
Re: Host-routed netmail to points
By: Digital Man to poindexter FORTRAN on Wed May 25 2022 10:12 am
So it looks like the destination point node must not be configured in sbbsecho.ini while the boss node must be configured in sbbsecho.ini for thi
Would setting a rule for 1:ALL setting the status to CRASH meet that criteria?
What I'd like to do is go ahead and crash anyone directly, and as
expected, crashmail point netmail to the bossnode.
The logic in SBBSecho is currently that the bossnode must be configured. Perhaps that could be changed to just strip the point number always andcalI
The logic in SBBSecho is currently that the bossnode must becalI
configured. Perhaps that could be changed to just strip the point
number always and
I have 1:229/426 configured in sbbsecho and tried sending mail to a point off of Nick's system. I saw this in my log:
5/25 10:45:07p BINKOUT Connecting to 1:229/426.3@fidonet at p3.f426.n229.z1.binkd.net:24554 5/25 10:45:07p BINKOUT Connection to p3.f426.n229.z1.binkd.net:24554 failed (Error: No such host is known. ).
So, it looks like sbbsecho is treating a 4d address literally and trying to
send directly to a point.
Subject: Host-routed netmail to points
@MSGID: <628F17AD.64200.dove.sync@realitycheckbbs.org>
@REPLY: <628E9CC1.47335.sync@vert.synchro.net>
@TZ: c1e0
Re: Host-routed netmail to points
By: Digital Man to Kurt Weiske on Wed May 25 2022 02:16 pm
The logic in SBBSecho is currently that the bossnode must be configured. Perhaps that could be changed to just strip the point number always andcalI
I have 1:229/426 configured in sbbsecho and tried sending mail to a point off of Nick's system. I saw this in my log:
5/25 10:45:07p BINKOUT Connecting to 1:229/426.3@fidonet at p3.f426.n229.z1.binkd.net:24554
5/25 10:45:07p BINKOUT Connection to p3.f426.n229.z1.binkd.net:24554 failed (Error: No such host is known. ).
So, it looks like sbbsecho is treating a 4d address literally and trying to send directly to a point.
What I think it should be doing is evaluating the zone:net/node portion of pointmail and sending the mail according to the boss node's configuration or a wildcard configuration that applies.
Wilfred van Velzen wrote to poindexter FORTRAN <=-
Sometimes that works! For instance I have 2 points which are directly connectable because they have a binkp service running 24/7. And at what address they are connectable is also public information because it's published in the Z2PNT list.
If 1:229/426 is configured in sbbsecho.ini and 1:229/426.3 is *not* configured in sbbsecho.ini, then you should see in your sbbsecho.log file a line similar to this one, when processing a packet for 1:229/426.3:
Routing packet (x) to boss-node 1:229/426
5/25 10:45:07p BINKOUT Connecting to 1:229/426.3@fidonet at
p3.f426.n229.z1.binkd.net:24554
5/25 10:45:07p BINKOUT Connection to p3.f426.n229.z1.binkd.net:24554
failed (Error: No such host is known. ).
Subject: Host-routed netmail to points
@MSGID: <628FE7FE.64204.dove.sync@realitycheckbbs.org>
@REPLY: <628FA08D.47339.sync@vert.synchro.net>
@TZ: c1e0
Re: Host-routed netmail to points
By: Digital Man to poindexter FORTRAN on Thu May 26 2022 08:45 am
If 1:229/426 is configured in sbbsecho.ini and 1:229/426.3 is *not* configured in sbbsecho.ini, then you should see in your sbbsecho.log file a line similar to this one, when processing a packet for 1:229/426.3:
Routing packet (x) to boss-node 1:229/426
Therein lies the problem. 229/426 is defined -- Nick is my uplink. .3 is not defined. What I'm seeing is below.
5/25 10:45:07p BINKOUT Connecting to 1:229/426.3@fidonet at
p3.f426.n229.z1.binkd.net:24554
5/25 10:45:07p BINKOUT Connection to p3.f426.n229.z1.binkd.net:24554
failed (Error: No such host is known. ).
Digital Man wrote to poindexter FORTRAN <=-
The sbbsecho.log file is the relevant log to be looking at in this
case. --
Sysop: | Retros |
---|---|
Location: | Toronto, Canada |
Users: | 23 |
Nodes: | 8 (0 / 8) |
Uptime: | 142:52:47 |
Calls: | 1,087 |
Files: | 6 |
Messages: | 29,843 |