Hi poindexter,

On 2022-05-25 23:01:17, you wrote to Digital Man:

 DM>> The logic in SBBSecho is currently that the bossnode must be
 DM>> configured. Perhaps that could be changed to just strip the point
 DM>> number always and
 pF> calI

 pF> I have 1:229/426 configured in sbbsecho and tried sending mail to a point
 pF> off of Nick's system. I saw this in my log:

 pF>  5/25  10:45:07p  BINKOUT Connecting to 1:229/426.3@fidonet at
 pF> p3.f426.n229.z1.binkd.net:24554 5/25  10:45:07p  BINKOUT Connection to
 pF> p3.f426.n229.z1.binkd.net:24554 failed (Error: No such host is known. ).

 pF> So, it looks like sbbsecho is treating a 4d address literally and trying to
 pF> send directly to a point.

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.

So if DM is going to change anything in the routing logic, I think that possible situation should also be taken into account...


Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815