Subj : Host-routed netmail to points
To   : poindexter FORTRAN
From : Digital Man
Date : Thu May 26 2022 08:45:17

  Re: Host-routed netmail to points
  By: poindexter FORTRAN to Digital Man on Wed May 25 2022 11:01 pm

 > 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
 >
 > DM> The logic in SBBSecho is currently that the bossnode must be configured.
 > DM> Perhaps that could be changed to just strip the point number always and
 > calI
 >
 > 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.

According to the logic I pasted here and explained:

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
-- 
                                            digital man (rob)

Sling Blade quote #16:
Karl Childers (to Doyle, re: lawn mower blade): I aim to kill you with it. Mmm.
Norco, CA WX: 60.7øF, 92.0% humidity, 2 mph SE wind, 0.00 inches rain/24hrs
---
 þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

.