I've run into this issue before, but never figured out a resolution. ããI'm running SBBS 3.19, SBBSecho v3.15-win32. I received a netmail from a point in zone 2. I replied to it, and see a .cut file in what looks like the proper place - %binkdir%\outbox.002\00dd0001.pnt\0000003a.cut. The contents of the .cut file is the netmail reply I wrote. So far, so good.ããIf I poll the boss node, nothing gets transferred. If I poll the point, nothing happens, as expected.ããIs there a setting I've missed in echocfg to properly route any point mail I receive to the boss node?ãã---ã þ Synchronet þ .: realitycheckbbs.org :: scientia potentia est :.ã

Re: routing to pointsã By: poindexter FORTRAN to All on Tue Feb 14 2023 12:43 pmãã > I've run into this issue before, but never figured out a resolution.ã >ã > I'm running SBBS 3.19, SBBSecho v3.15-win32. I received a netmail from aã > point in zone 2. I replied to it, and see a .cut file in what looks like theã > proper place - %binkdir%\outbox.002\00dd0001.pnt\0000003a.cut. The contentsã > of the .cut file is the netmail reply I wrote. So far, so good.ã >ã > If I poll the boss node, nothing gets transferred. If I poll the point,ã > nothing happens, as expected.ã >ã > Is there a setting I've missed in echocfg to properly route any point mail Iã > receive to the boss node?ããHere's the relevant logic in sbbsecho.s pack_netmail():ãã if(nodecfg == NULL && addr.point != 0) {ã fidoaddr_t boss = addr;ã boss.point = 0;ã if((nodecfg = findnodecfg(&cfg, boss, /* exact: */true)) != NULL) {ã addr = boss;ã lprintf(LOG_INFO, "Routing NetMail (%s) to boss-node %s"ã ,getfname(path), smb_faddrtoa(&addr, NULL));ã }ã }ããWhich means that the boss node must be configured in EchoCfg->Linked Nodes for this boss-routing to occur. Is the boss node in question configured in EchoCfg->Linked Nodes?ã-- ã digital man (rob)ããThis Is Spinal Tap quote #39:ãFemale Airport Security Officer: Do you have any artificial plates or limbs?ãNorco, CA WX: 49.0øF, 84.0% humidity, 4 mph ESE wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: routing to pointsã By: Digital Man to poindexter FORTRAN on Tue Feb 14 2023 05:06 pmããDM> Which means that the boss node must be configured in EchoCfg->Linked NodesãDM> for this boss-routing to occur. Is the boss node in question configured in ããNo. I tried configuring the boss node and that didn't work either. I'll see if I can reproduce that.ããIt seems cumbersome to have to configure a boss node on an individual basis. I'd need to receive mail, then create an entry for the boss node. If an end-user receives a netmail and replies, I might not even know to create the entry. It might be nice if, when packing mail for a point, you check to see if there's a points list, and if not, automatically address point-bound mail to the boss, where any default rules could handle routing mail to the boss.ãã---ã þ Synchronet þ .: realitycheckbbs.org :: scientia potentia est :.ã

Re: routing to pointsã By: poindexter FORTRAN to Digital Man on Tue Feb 14 2023 09:41 pmãã > Re: routing to pointsã > By: Digital Man to poindexter FORTRAN on Tue Feb 14 2023 05:06 pmã >ã > DM> Which means that the boss node must be configured in EchoCfg->Linkedã > DM> Nodes for this boss-routing to occur. Is the boss node in questionã > DM> configured inã >ã > No. I tried configuring the boss node and that didn't work either. I'll seeã > if I can reproduce that.ã >ã > It seems cumbersome to have to configure a boss node on an individual basis.ã > I'd need to receive mail, then create an entry for the boss node. If anã > end-user receives a netmail and replies, I might not even know to create theã > entry. It might be nice if, when packing mail for a point, you check to seeã > if there's a points list, and if not, automatically address point-bound mailã > to the boss, where any default rules could handle routing mail to the boss.ããApparently boss-routing feature was added to SBBSecho just for you:ãhttps://gitlab.synchro.net/main/sbbs/-/commit/45ced2a3b39d30cbb8c909e66e063ceeff05e636ããI suppose it may be possible to route to netmail a non-linked node. <shrug> I don't recall the original request/discussion surrounding this change, but the commit message refers to you, specifically.ã-- ã digital man (rob)ããBreaking Bad quote #46:ãIf I ever get anal polyps, at least I know what to name them. - Saul GoodmanãNorco, CA WX: 48.6øF, 26.0% humidity, 0 mph NNW wind, 0.05 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: routing to pointsã By: Digital Man to poindexter FORTRAN on Wed Feb 15 2023 09:58 amããDM> Apparently boss-routing feature was added to SBBSecho just for you:ãDM> https://gitlab.synchro.net/main/sbbs/-/commit/45ced2a3b39d30cbb8c909e66e063ãDM> ceeff05e636 ããLooking at the commit, it looks like it was some time ago, in sbbsecho 3.13. My sbbsecho reports version 3.15?ãã---ã þ Synchronet þ .: realitycheckbbs.org :: scientia potentia est :.ã

Re: routing to pointsã By: Digital Man to poindexter FORTRAN on Wed Feb 15 2023 09:58 amããDM> Apparently boss-routing feature was added to SBBSecho just for you:ãDM> https://gitlab.synchro.net/main/sbbs/-/commit/45ced2a3b39d30cbb8c909e66e063ãDM> ceef f05e636ãããSince I typed my last response, I've upgraded to 3.20, Created an email to a point node and am seeing the following behavior:ãã1. Try to poll the point address - not found (as is expected)ã2. Try to poll the boss (not defined in sbbsecho.cfg) - doesn't transfer point mail.ã3. Try to poll the boss (defined in sbbsecho.cfg) - doesn't transfer point mail.ããIt's be great if there was a way that the logic could automatically boss-route any point mail, regardless of whether or not the boss is defined in sbbsecho.cfg.ãã---ã þ Synchronet þ .: realitycheckbbs.org :: scientia potentia est :.ã

Re: routing to pointsã By: poindexter FORTRAN to Digital Man on Wed Feb 15 2023 06:08 pmãã > Re: routing to pointsã > By: Digital Man to poindexter FORTRAN on Wed Feb 15 2023 09:58 amã >ã > DM> Apparently boss-routing feature was added to SBBSecho just for you: httpã > DM> s://gitlab.synchro.net/main/sbbs/-/commit/45ced2a3b39d30cbb8c909e66e063ã > DM> ceeff05e636ã >ã > Looking at the commit, it looks like it was some time ago, in sbbsecho 3.13.ã > My sbbsecho reports version 3.15?ããYes. I'm not sure of your point.ã-- ã digital man (rob)ããBreaking Bad quote #12:ã[Walt] Looks like Keith Richards with a glass a warm milk! - Hank SchraderãNorco, CA WX: 44.0øF, 45.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: routing to pointsã By: poindexter FORTRAN to Digital Man on Wed Feb 15 2023 07:09 pmãã > Re: routing to pointsã > By: Digital Man to poindexter FORTRAN on Wed Feb 15 2023 09:58 amã >ã > DM> Apparently boss-routing feature was added to SBBSecho just for you: httpã > DM> s://gitlab.synchro.net/main/sbbs/-/commit/45ced2a3b39d30cbb8c909e66e063ã > DM> ceef f05e636ã >ã >ã > Since I typed my last response, I've upgraded to 3.20, Created an email to aã > point node and am seeing the following behavior:ã >ã > 1. Try to poll the point address - not found (as is expected)ã > 2. Try to poll the boss (not defined in sbbsecho.cfg) - doesn't transferã > point mail.ã > 3. Try to poll the boss (defined in sbbsecho.cfg) - doesn't transfer pointã > mail.ããThe point->boss routing happens in SBBSecho, so before you would do any polling.ãã > It's be great if there was a way that the logic could automaticallyã > boss-route any point mail, regardless of whether or not the boss is definedã > in sbbsecho.cfg.ããHm. I'll consider doing that. I'm not sure why it wasn't done that way initially. I understand for echomail why you couldn't/wouldn't, but I suppose NetMail should be possible in that scenario. I'll give it more thought.ã-- ã digital man (rob)ããSynchronet/BBS Terminology Definition #45:ãIP = Internet ProtocolãNorco, CA WX: 44.0øF, 45.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Digital Man wrote to poindexter FORTRAN <=-ãã > It's be great if there was a way that the logic could automaticallyã > boss-route any point mail, regardless of whether or not the boss is definedã > in sbbsecho.cfg.ãã DM> Hm. I'll consider doing that. I'm not sure why it wasn't done that wayã DM> initially. I understand for echomail why you couldn't/wouldn't, but Iã DM> suppose NetMail should be possible in that scenario. I'll give it moreã DM> thought. --ããThanks for looking at this; point mail lingering in my inbound has beenãa thing for some time, and it'd be nice to be able to have default rulesãhandle the mail instead of having to manually re-route it.ããDoes sbbsecho support a point list? I know that zone 2 has one, but Iãdon't understand the reasoning behind being able to crash a point. Iãthought the whole idea was for a system that wasn't up 24/7 (orãavailable at all) would use the boss node as an endpoint on the networkãand reach out to the boss node instead of being reachable.ãããã ã--- MultiMail/Win v0.52ã * Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Digital Man wrote to poindexter FORTRAN <=-ãã > Looking at the commit, it looks like it was some time ago, in sbbsecho 3.13.ã > My sbbsecho reports version 3.15?ãã DM> Yes. I'm not sure of your point.ããThanks again for looking into this.ããI wanted to send you my logs and notes from my experiments with pointãnetmail. If I understand the logic, a point that has a boss node definedãin sbbsecho.ini should have mail host-routed to the boss. I'm runningãsbbsecho 3.20, recently updated from the nightly archives.ããIt appears that point mail isn't being host-routed, which the commit youãreferenced appears to suggest.ããI did the following:ãã1. I defined the boss node, 2:221/1 in sbbsecho.ini. I created a netmail toã2:221/1:58 in SBBS. When I run SBBSECHO, I see the netmail being packed.ããã C:\Users\kweiske>sbbsechoãã SBBSecho v3.20-Win32 (master/aa33f300f) - Synchronet FidoNetã EchoMail Tosserãã Loading configuration files from c:\sbbs\ctrl\ SBBSechoã 3.20-Win32 master/aa33f300f Feb 15 2023 MSC 1929 (PID 5580)ã invoked with options: Configured: 6 archivers, 84 linked-nodes,ã 8 echolists NetMail directory: c:\sbbs\binkit\netmail\ Secureã Inbound directory: c:\sbbs\binkit\inbox\ Non-secure Inboundã directory: c:\sbbs\binkit\inbox\ Outbound (BSO root) directory:ã c:\sbbs\binkit\outbox\ Reading ../data/AREAS.BBS Exportingã Outbound NetMail from c:\sbbs\data\mail toã c:\sbbs\binkit\netmail\*.msg ... NetMail msg #13487 fromã poindexter FORTRAN to 1:103/1 (1:103/1): already sent NetMailã msg #29046 from Kurt Weiske to August Abolins (2:221/1.58):ã Exporting NetMail message #29046 from Kurt Weiske toã August Abolins (2:221/1.58) Created NetMail (4.msg) from Kurtã Weiske (1:218/700) to August Abolins (2:221/1.58), attr: 0183,ã subject: Anotherãã Packing Outbound NetMail from c:\sbbs\binkit\netmail\*.msg ...ã Node (2:221/1.58) successfully locked via:ã ../binkit/outbox.002\00dd0001.pnt\0000003a.bsy Adding NetMailã (4.msg) to new packet for 2:221/1.58:ã ../binkit/outbox.002\00dd0001.pnt\0000003a.cut Deletingã c:\sbbs\binkit\netmail\4.msg (from line 5344)ãã Touching outgoing semfile: ../data/binkout.now Writing 33 areasã to ../data/badareas.lst Deletingã ../binkit/outbox.002\00dd0001.pnt\0000003a.bsy (from line 2963)ã Deleting c:\sbbs\ctrl\sbbsecho.bsy (from line 2969) SBBSechoã (PID 5580) exiting with error level 0, NetMail(0 imported, 1ã exported, 1 packed)ãã2. I try polling the boss node, configured in echocfg:ãã[node:2:221/1] Name = Comment = Archive = ZIP PacketType = 2+ PacketPwdã= AreaFix = false AreaFixPwd = SessionPwd = TicFilePwd = Inbox = Outboxã= Passive = false Direct = false Notify = false Keys = Status = CrashãGroupHub = BinkpHost = BinkpPort = 24554 BinkpPoll = falseãBinkpPlainAuthOnly = false BinkpAllowPlainAuth = falseãBinkpAllowPlainText = true BinkpTLS = false BinkpSourceAddress =ãã C:\Users\kweiske>binkpoll 2:221/1ãã JSexec v3.20a-Win32 master/aa33f300f - Execute Synchronetã JavaScript Module Compiled Feb 15 2023 05:04:19 with MSC 1929ãã Loading configuration files from c:\sbbs\ctrl JavaScript-C 1.8.5ã 2011-03-31 JavaScript: Creating runtime: 8388608 bytesãã Reading script from c:\sbbs\exec\binkit.jsã c:\sbbs\exec\binkit.js compiled in 0.00 seconds BinkIT/2.41ã invoked with options: -l 2:221/1 Attempting poll for nodeã 2:221/1@fidonet JSBinkP/4 callout to 2:221/1@fidonet startedã Connecting to 2:221/1@fidonet at f1.n221.z2.rbb.fidonet.fi:24554ã Peer version: binkd/1.1a-115/OS2 Authentication successful:ã non-secure c:\sbbs\exec\binkit.js executed in 6.84 secondsãã JavaScript: Destroying context JavaScript: Destroying runtimeãã3. I see this in my events log:ãã 2/16 08:36:52a BINKPOLL Attempting callout for 2:221/1.58@fidonet,ã file: C:\sbbs\binkit\outbox.002\00dd0001.pnt\0000003a.cut 2/16ã 08:36:52a BINKPOLL JSBinkP/4 callout to 2:221/1.58@fidonet startedã 2/16 08:36:53a BINKPOLL Connecting to 2:221/1.58@fidonet atã p58.f1.n221.z2.binkd.net:24554 2/16 08:36:53a BINKPOLL Connection toã p58.f1.n221.z2.binkd.net:24554 failed (Error: No such host is known.ã ).ãããã... Change nothing and continue consistentlyã

--- MultiMail/Win v0.52ã * Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Re: routing to pointsã By: Kurt Weiske to Digital Man on Thu Feb 16 2023 06:17 amãã > Does sbbsecho support a point list?ããNo, SBBSecho has no knowledge of nodelists or pointlists.ã-- ã digital man (rob)ããThis Is Spinal Tap quote #39:ãFemale Airport Security Officer: Do you have any artificial plates or limbs?ãNorco, CA WX: 60.9øF, 16.0% humidity, 6 mph N wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Re: routing to pointsã By: Kurt Weiske to Digital Man on Thu Feb 16 2023 09:38 amãã > -=> Digital Man wrote to poindexter FORTRAN <=-ã >ã > > Looking at the commit, it looks like it was some time ago, in sbbsechoã > > 3.13. My sbbsecho reports version 3.15?ã >ã > DM> Yes. I'm not sure of your point.ã >ã > Thanks again for looking into this.ã >ã > I wanted to send you my logs and notes from my experiments with pointã > netmail. If I understand the logic, a point that has a boss node definedã > in sbbsecho.ini should have mail host-routed to the boss.ããOnly if the point itself is not a configured linked node (in echofg) and the point isn't one of your own configured FTN AKAs.ãã > I'm runningã > sbbsecho 3.20, recently updated from the nightly archives.ã >ã > It appears that point mail isn't being host-routed, which the commit youã > referenced appears to suggest.ã >ã > I did the following:ã >ã > 1. I defined the boss node, 2:221/1 in sbbsecho.ini. I created a netmail toã > 2:221/1:58 in SBBS. When I run SBBSECHO, I see the netmail being packed.ã >ã >ã > C:\Users\kweiske>sbbsechoã >ã > SBBSecho v3.20-Win32 (master/aa33f300f) - Synchronet FidoNetã > EchoMail Tosserã >ã > Loading configuration files from c:\sbbs\ctrl\ SBBSechoã > 3.20-Win32 master/aa33f300f Feb 15 2023 MSC 1929 (PID 5580)ã > invoked with options: Configured: 6 archivers, 84 linked-nodes,ã > 8 echolists NetMail directory: c:\sbbs\binkit\netmail\ Secureã > Inbound directory: c:\sbbs\binkit\inbox\ Non-secure Inboundã > directory: c:\sbbs\binkit\inbox\ Outbound (BSO root) directory:ã > c:\sbbs\binkit\outbox\ Reading ../data/AREAS.BBS Exportingã > Outbound NetMail from c:\sbbs\data\mail toã > c:\sbbs\binkit\netmail\*.msg ... NetMail msg #13487 fromã > poindexter FORTRAN to 1:103/1 (1:103/1): already sent NetMailã > msg #29046 from Kurt Weiske to August Abolins (2:221/1.58):ã > Exporting NetMail message #29046 from Kurt Weiske toã > August Abolins (2:221/1.58) Created NetMail (4.msg) from Kurtã > Weiske (1:218/700) to August Abolins (2:221/1.58), attr: 0183,ã > subject: AnotherããThat's not very fun to try to read. :-) Do you mind not re-wrapping the log lines you paste here?ããã > Packing Outbound NetMail from c:\sbbs\binkit\netmail\*.msg ...ã > Node (2:221/1.58) successfully locked via:ã > ../binkit/outbox.002\00dd0001.pnt\0000003a.bsy Adding NetMailã > (4.msg) to new packet for 2:221/1.58:ã > ../binkit/outbox.002\00dd0001.pnt\0000003a.cut Deletingã > c:\sbbs\binkit\netmail\4.msg (from line 5344)ã >ã > Touching outgoing semfile: ../data/binkout.now Writing 33 areasã > to ../data/badareas.lst Deletingã > ../binkit/outbox.002\00dd0001.pnt\0000003a.bsy (from line 2963)ã > Deleting c:\sbbs\ctrl\sbbsecho.bsy (from line 2969) SBBSechoã > (PID 5580) exiting with error level 0, NetMail(0 imported, 1ã > exported, 1 packed)ããMy guess is that you have 2:221/1.58 explicitly listed as a linked node in echofg?ã-- ã digital man (rob)ããSling Blade quote #10:ãMorris: I stand on the hill, not for thrill, but for the breath of a fresh killãNorco, CA WX: 61.4øF, 16.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Re: routing to pointsã By: Digital Man to Kurt Weiske on Thu Feb 16 2023 01:20 pmããDM> My guess is that you have 2:221/1.58 explicitly listed as a linked node inãDM> echofg?ããNo, only 2:221/1. ããI saved the log files and commentary to https://realitycheckbbs.org/sbbsecho.txt, that should be easier to read.ã--- SBBSecho 3.20-Win32ã * Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Re: routing to pointsã By: Kurt Weiske to Digital Man on Thu Feb 16 2023 01:39 pmãã > Re: Re: routing to pointsã > By: Digital Man to Kurt Weiske on Thu Feb 16 2023 01:20 pmã >ã > DM> My guess is that you have 2:221/1.58 explicitly listed as a linked nodeã > DM> in echofg?ã >ã > No, only 2:221/1.ã >ã > I saved the log files and commentary toã > https://realitycheckbbs.org/sbbsecho.txt, that should be easier to read.ãã$ wget https://realitycheckbbs.org/sbbsecho.txtã--2023-02-16 17:34:01-- https://realitycheckbbs.org/sbbsecho.txtãResolving realitycheckbbs.org (realitycheckbbs.org)... failed: Name or service not known.ãwget: unable to resolve host addressã-- ã digital man (rob)ããThis Is Spinal Tap quote #9:ãDavid St. Hubbins: I mean, it's not your job to be as confused as Nigel.ãNorco, CA WX: 61.7øF, 16.0% humidity, 0 mph NE wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Re: routing to pointsã By: Digital Man to Kurt Weiske on Thu Feb 16 2023 05:34 pmãã > Re: Re: routing to pointsã > By: Kurt Weiske to Digital Man on Thu Feb 16 2023 01:39 pmã >ã > > Re: Re: routing to pointsã > > By: Digital Man to Kurt Weiske on Thu Feb 16 2023 01:20 pmã >ã > > DM> My guess is that you have 2:221/1.58 explicitly listed as a linkedã > > DM> node in echofg?ã >ã > > No, only 2:221/1.ã >ã > > I saved the log files and commentary toã > > https://realitycheckbbs.org/sbbsecho.txt, that should be easier to read.ã >ã > $ wget https://realitycheckbbs.org/sbbsecho.txtã > --2023-02-16 17:34:01-- https://realitycheckbbs.org/sbbsecho.txtã > Resolving realitycheckbbs.org (realitycheckbbs.org)... failed: Name orã > service not known.ã > wget: unable to resolve host addressããAlso, the detail we're looking for would be in your sbbsecho.log file, yet you seem to be copying/pasting from the console output of sbbsecho.ã-- ã digital man (rob)ããBreaking Bad quote #17:ãYour breath could knock the buzzard off a shit wagon. - Hank SchraderãNorco, CA WX: 61.7øF, 16.0% humidity, 0 mph NE wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Re: routing to pointsã By: Digital Man to Kurt Weiske on Thu Feb 16 2023 05:34 pmãã > Re: Re: routing to pointsã > By: Kurt Weiske to Digital Man on Thu Feb 16 2023 01:39 pmã >ã > > Re: Re: routing to pointsã > > By: Digital Man to Kurt Weiske on Thu Feb 16 2023 01:20 pmã >ã > > DM> My guess is that you have 2:221/1.58 explicitly listed as a linkedã > > DM> node in echofg?ã >ã > > No, only 2:221/1.ã >ã > > I saved the log files and commentary toã > > https://realitycheckbbs.org/sbbsecho.txt, that should be easier to read.ã >ã > $ wget https://realitycheckbbs.org/sbbsecho.txtã > --2023-02-16 17:34:01-- https://realitycheckbbs.org/sbbsecho.txtã > Resolving realitycheckbbs.org (realitycheckbbs.org)... failed: Name orã > service not known.ã > wget: unable to resolve host addressããI also tried reality.synchro.net with HTTPS, but you don't have your TLS cert set correctly:ã $ wget https://reality.synchro.net/sbbsecho.txtã--2023-02-16 17:46:48-- https://reality.synchro.net/sbbsecho.txtãResolving reality.synchro.net (reality.synchro.net)... 98.210.238.44ãConnecting to reality.synchro.net (reality.synchro.net)|98.210.238.44|:443...ãconnected.ãThe certificate's owner does not match hostnameããI tried reality.synchro.net:8000 via HTTP, but it downloads a SHOUTcast error message file instead.ã-- ã digital man (rob)ããThis Is Spinal Tap quote #36:ãBobbi Flekman: Money talks, and bullshit walks.ãNorco, CA WX: 61.7øF, 16.0% humidity, 0 mph NE wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Re: routing to pointsã By: Digital Man to Kurt Weiske on Thu Feb 16 2023 05:34 pmãã > Re: Re: routing to pointsã > By: Kurt Weiske to Digital Man on Thu Feb 16 2023 01:39 pmã >ã > > Re: Re: routing to pointsã > > By: Digital Man to Kurt Weiske on Thu Feb 16 2023 01:20 pmã >ã > > DM> My guess is that you have 2:221/1.58 explicitly listed as a linkedã > > DM> node in echofg?ã >ã > > No, only 2:221/1.ããDo you have points of 2:221/1 configured in echocfg->Linked Nodes?ããDo you have 2:ALL or 2:221/ALL configured in echocfg->Linked Nodes with routing specified?ã-- ã digital man (rob)ããBreaking Bad quote #13:ãI got twenty bucks that says he's a beaner. - Hank SchraderãNorco, CA WX: 53.0øF, 21.0% humidity, 0 mph NE wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Re: routing to pointsã By: Digital Man to Kurt Weiske on Thu Feb 16 2023 05:44 pmãã > Re: Re: routing to pointsã > By: Digital Man to Kurt Weiske on Thu Feb 16 2023 05:34 pmã >ã > > Re: Re: routing to pointsã > > By: Kurt Weiske to Digital Man on Thu Feb 16 2023 01:39 pmã > >ã > > > Re: Re: routing to pointsã > > > By: Digital Man to Kurt Weiske on Thu Feb 16 2023 01:20 pmã >ã > > > DM> My guess is that you have 2:221/1.58 explicitly listed as a linkedã > > > DM> node in echofg?ã >ã > > > No, only 2:221/1.ã >ã > > > I saved the log files and commentary toã > > > https://realitycheckbbs.org/sbbsecho.txt, that should be easier toã > > > read.ã >ã > > $ wget https://realitycheckbbs.org/sbbsecho.txtã > > --2023-02-16 17:34:01-- https://realitycheckbbs.org/sbbsecho.txtã > > Resolving realitycheckbbs.org (realitycheckbbs.org)... failed: Name orã > > service not known.ã > > wget: unable to resolve host addressã >ã > Also, the detail we're looking for would be in your sbbsecho.log file, yetã > you seem to be copying/pasting from the console output of sbbsecho.ããI looked back through the history of messages in this sub and it appers thatãwe had almost the exact same conversation in May of last year (Subject: "Host-routed netmail to points"). You were pasting BinkIT log output here instead of the relevant portions of sbbsecho.log and then you finally concluded the discussion with this:ãã-------------------------------------8<---------------------------------------ã DM> The sbbsecho.log file is the relevant log to be looking at in thisã DM> case. --ããI looked in the log and saw some weird entries showing 5 digit zone numbers.ãOn a lark, I tried changing "Fuzzy Zone Operation" in echocfg to "no", andãnow I'm seeing the routing messages in my sbbsecho.log.ããIf I can reproduce the error again, I'll post the log files. For now, itãseems like it's behaving as expected.ããThanks for your help!ã-------------------------------------8<---------------------------------------ããI don't think anything changed in SBBSecho in this regard since that time.ã-- ã digital man (rob)ããBreaking Bad quote #12:ã[Walt] Looks like Keith Richards with a glass a warm milk! - Hank SchraderãNorco, CA WX: 52.8øF, 20.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Digital Man wrote to Kurt Weiske <=-ããCompiling answers to a handful of messages:ããNot sure why https://realitycheckbbs.org/sbbsecho.txt wouldn't resolveãfor you - I was able to ssh into dreamhost, my web host on the outsideãand see it OK using Lynx. Maybe it was a transient issue?ããI was able to get through to https://reality.synchro.net and saw theãerror on the cert mismatch. Is there a way to pass a secondary hostnameãto letsyncrypt.js? Odd, since one of my subdomains hosted on the bbs,ãradio.realitycheckbbs.org works with my LE cert.ããI did have an entry for 2:ALL in my sbbsecho.log, but I removed it andãstill saw the same behavior.ããI didn't see anything in my sbbsecho.log corresponding to that snippetãfrom the event log, I'll crank up the log level and see what I can see.ãããããããããã ã--- MultiMail/Win v0.52ã * Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Re: routing to pointsã By: Kurt Weiske to Digital Man on Thu Feb 16 2023 10:30 pmãã > -=> Digital Man wrote to Kurt Weiske <=-ã >ã > Compiling answers to a handful of messages:ã >ã > Not sure why https://realitycheckbbs.org/sbbsecho.txt wouldn't resolveã > for you - I was able to ssh into dreamhost, my web host on the outsideã > and see it OK using Lynx. Maybe it was a transient issue?ããYeah, works now.ãã > I was able to get through to https://reality.synchro.net and saw theã > error on the cert mismatch. Is there a way to pass a secondary hostnameã > to letsyncrypt.js?ããYes, the [domains] section of ctrl/letsencrypt.iniãwiki.synchro.net/module:letsyncrypt#domainsãã > Odd, since one of my subdomains hosted on the bbs,ã > radio.realitycheckbbs.org works with my LE cert.ã >ã > I did have an entry for 2:ALL in my sbbsecho.log,ããSo there would be a different "Routing NetMail" log line in that case (if that 2:ALL linked node had a route specified).ãã > but I removed it and still saw the same behavior.ããWhen? What does the log report?ãã > I didn't see anything in my sbbsecho.log corresponding to that snippetã > from the event log, I'll crank up the log level and see what I can see.ããThe relevant log lines are "INFO" level.ã-- ã digital man (rob)ããSling Blade quote #8:ãKarl Childers: I don't reckon I got no reason to kill nobody.ãNorco, CA WX: 46.5øF, 27.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Re: routing to pointsã By: Digital Man to Kurt Weiske on Thu Feb 16 2023 06:32 pmãããI took out the 2:ALL statement in sbbsecho.ini, changed the log level to debugging, created a netmail for 2:221/1.58, and saw this in my log file:ããRouting NetMail (4.msg) to boss-node 2:221/1ãNode (2:221/1) successfully locked via: ../binkit/outbox.002\00dd0001.bsyãAdding NetMail (4.msg) to new packet for 2:221/1: ../binkit/outbox.002\00dd0001.cutãDeleting c:\sbbs\binkit\netmail\4.msg (from line 5344)ããWhich looks like the expected behavior - 2:221/1 is listed in my linked nodes list.ã--- SBBSecho 3.20-Win32ã * Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Digital Man wrote to Kurt Weiske <=-ãã DM> I also tried reality.synchro.net with HTTPS, but you don't have yourã DM> TLS cert set correctly:ã DM> $ wget https://reality.synchro.net/sbbsecho.txtã DM> --2023-02-16 17:46:48-- https://reality.synchro.net/sbbsecho.txtã DM> Resolving reality.synchro.net (reality.synchro.net)... 98.210.238.44ã DM> Connecting to reality.synchro.netã DM> (reality.synchro.net)|98.210.238.44|:443... connected.ã DM> The certificate's owner does not match hostnameãã DM> I tried reality.synchro.net:8000 via HTTP, but it downloads a SHOUTcastã DM> error message file instead. --ã ã--- MultiMail/Win v0.52ã þ Synchronet þ .: realitycheckbbs.org :: scientia potentia est :.ã

Re: Re: routing to pointsã By: Kurt Weiske to Digital Man on Thu Feb 16 2023 10:52 pmãã > Re: Re: routing to pointsã > By: Digital Man to Kurt Weiske on Thu Feb 16 2023 06:32 pmã >ã >ã > I took out the 2:ALL statement in sbbsecho.ini, changed the log level toã > debugging, created a netmail for 2:221/1.58, and saw this in my log file:ã >ã > Routing NetMail (4.msg) to boss-node 2:221/1ã > Node (2:221/1) successfully locked via: ../binkit/outbox.002\00dd0001.bsyã > Adding NetMail (4.msg) to new packet for 2:221/1:ã > ../binkit/outbox.002\00dd0001.cutã > Deleting c:\sbbs\binkit\netmail\4.msg (from line 5344)ã >ã > Which looks like the expected behavior - 2:221/1 is listed in my linkedã > nodes list.ããCool. So do we now want to change the expected behavior?ããWhile analyzing this section of sbbsecho.c, I did notice this change which struck me as potentially undesireable:ãhttps://gitlab.synchro.net/main/sbbs/-/commit/ffe69b43623db42984a286433e62f4256ããWith this change (apparently as the result of a suggestion or request by Alterego), if the destination address is 1:2/3.1, but our local system has an AKA of 1:2/3.2, no routing would occur (to a boss node or based on explicit routing configured in echocfg->Linked Nodes) and that seems like a bug to me. But still unrelated to your observations.ã-- ã digital man (rob)ããBreaking Bad quote #26:ãYour commercials suck ass. I've seen better acting in an epileptic whorehouse.ãNorco, CA WX: 59.6øF, 20.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Re: routing to pointsã By: poindexter FORTRAN to Digital Man on Thu Feb 16 2023 10:21 pmãã > -=> Digital Man wrote to Kurt Weiske <=-ã >ã > DM> I also tried reality.synchro.net with HTTPS, but you don't have yourã > DM> TLS cert set correctly:ã > DM> $ wget https://reality.synchro.net/sbbsecho.txtã > DM> --2023-02-16 17:46:48-- https://reality.synchro.net/sbbsecho.txtã > DM> Resolving reality.synchro.net (reality.synchro.net)... 98.210.238.44ã > DM> Connecting to reality.synchro.netã > DM> (reality.synchro.net)|98.210.238.44|:443... connected.ã > DM> The certificate's owner does not match hostnameã >ã > DM> I tried reality.synchro.net:8000 via HTTP, but it downloads a SHOUTcastã > DM> error message file instead. --ããThis reply appears to have been cut off (only included quoted text). Just FYI.ã-- ã digital man (rob)ããRush quote #23:ãPlus ca change, plus c'est la meme choseãNorco, CA WX: 59.6øF, 20.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Re: routing to pointsã By: Digital Man to Kurt Weiske on Fri Feb 17 2023 10:59 amãã>> Which looks like the expected behavior - 2:221/1 is listed in my linkedã>> nodes list.ããDM> Cool. So do we now want to change the expected behavior?ããWould it be correct to assume that my 2:ALL "linked node" entry in echocfg was being applied to my point netmail, and because no routing was specified in the 2:ALL entry, that sbbsecho packet the point netmail according to the wildcard entry? It seems like when I removed the 2:ALL entry that sbbsecho packed point mail for the boss (that *was* defined in sbbsecho.ini.)ããIf that's the case, that would fit the behavior I was seeing.ããSince Synchronet doesn't know how to route to a point, I'd think it would make to sense to first pack all point netmail for the Boss node and then let explicit linked node entries or catch-all entries handle mail routing/flavor to the boss.ããThen, if you had a specific routing arrangement with a node, you could specify them in the linked node section. If not, a zone:ALL rule could route/flavor the mail to the boss however you choose.ããThis would simplify sending replies to point netmail, in my opinion.ããOr, am I missing something?ããThanks again for your time in looking into this.ãã--kã--- SBBSecho 3.20-Win32ã * Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Re: routing to pointsã By: Kurt Weiske to Digital Man on Fri Feb 17 2023 12:01 pmãã > Re: Re: routing to pointsã > By: Digital Man to Kurt Weiske on Fri Feb 17 2023 10:59 amã >ã > >> Which looks like the expected behavior - 2:221/1 is listed in my linkedã > >> nodes list.ã >ã > DM> Cool. So do we now want to change the expected behavior?ã >ã > Would it be correct to assume that my 2:ALL "linked node" entry in echocfgã > was being applied to my point netmail, and because no routing was specifiedã > in the 2:ALL entry, that sbbsecho packet the point netmail according to theã > wildcard entry? It seems like when I removed the 2:ALL entry that sbbsechoã > packed point mail for the boss (that *was* defined in sbbsecho.ini.)ããThe 2:ALL linked node entry would have only played a role *if* it had a route specified. And in that case, yes, the NetMail would be routed, but to the specified 2:ALL route, not the point's boss node.ãã > If that's the case, that would fit the behavior I was seeing.ããThe sbbsecho.log file would include an INFO-level "Routing NetMail" line (withOUT "boss-node") in this case. If the log doesn't include that, then this is not happening.ãã > Since Synchronet doesn't know how to route to a point, I'd think it wouldã > make to sense to first pack all point netmail for the Boss node and then letã > explicit linked node entries or catch-all entries handle mail routing/flavorã > to the boss.ã >ã > Then, if you had a specific routing arrangement with a node, you couldã > specify them in the linked node section. If not, a zone:ALL rule couldã > route/flavor the mail to the boss however you choose.ã >ã > This would simplify sending replies to point netmail, in my opinion.ã >ã > Or, am I missing something?ããI think an explicit linked node configuration should always take precedence. No?ããI'm not sure what you mean by "Synchronet doesn't konw how to route to a point". You can tell SBBSecho (not Synchronet) how to route to points both explicity and with wildcards and there's the boss-node fall-back if the boss-node is explicity configured.ã-- ã digital man (rob)ããSynchronet/BBS Terminology Definition #32:ãFREQ = File RequestãNorco, CA WX: 63.6øF, 19.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Re: routing to points ã By: Digital Man to Kurt Weiske on Fri Feb 17 2023 12:58 pm ã ãDM> I'm not sure what you mean by "Synchronet doesn't konw how to route to a ãDM> point". You can tell SBBSecho (not Synchronet) how to route to points both ãDM> explicity and with wildcards and there's the boss-node fall-back if the ãDM> boss-node is explicity configured. ã ãI'm mis-using some of the terminology. ã ãSBBSecho, unless told otherwise by specifying the boss node in sbbsecho.ini, will create an outbound packet for the full point address, and binkit is unable to deliver the mail.ã ãIf you define the boss node, SBBSecho will create a packet containing the point's netmail for the boss node, which makes sense.ã ãSince points are not in the network's nodelist and are dependent on the boss node to receive and deliver files on its behalf, why not automatically route all point mail to their respective boss nodes by default?ã ã ã ã--- SBBSecho 3.20-Win32ã * Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Re: routing to pointsã By: Kurt Weiske to Digital Man on Fri Feb 17 2023 02:39 pmãã > Re: Re: routing to pointsã > By: Digital Man to Kurt Weiske on Fri Feb 17 2023 12:58 pmã >ã > DM> I'm not sure what you mean by "Synchronet doesn't konw how to route to aã > DM> point". You can tell SBBSecho (not Synchronet) how to route to pointsã > DM> both explicity and with wildcards and there's the boss-node fall-back ifã > DM> the boss-node is explicity configured.ã >ã > I'm mis-using some of the terminology.ã >ã > SBBSecho, unless told otherwise by specifying the boss node in sbbsecho.ini,ã > will create an outbound packet for the full point address, and binkit isã > unable to deliver the mail.ã >ã > If you define the boss node, SBBSecho will create a packet containing theã > point's netmail for the boss node, which makes sense.ã >ã > Since points are not in the network's nodelist and are dependent on the bossã > node to receive and deliver files on its behalf, why not automatically routeã > all point mail to their respective boss nodes by default?ããI think SBBSecho changed to do that. Do you mind creating a feature request atãhttps://gitlab.synchro.net/main/sbbs/-/issues and providing this detail?ããThe code we're discussing now was added 3 years ago (at your request) and a request for test results was made by me at the time (in the commit message), but I don't think ever got those results/feedback. I'd like to better track theãchange request/rationale and the results this time. Thanks,ã-- ã digital man (rob)ããSynchronet/BBS Terminology Definition #89:ãXJS = External JavaScript (SSJS embedded within HTML/CSS)ãNorco, CA WX: 66.0øF, 17.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Re: routing to pointsã By: Digital Man to Kurt Weiske on Fri Feb 17 2023 02:59 pmããDM> I think SBBSecho changed to do that. Do you mind creating a feature requestãDM> at https://gitlab.synchro.net/main/sbbs/-/issues and providing this detail?ããWill do.ããDM> The code we're discussing now was added 3 years ago (at your request) and aãDM> request for test results was made by me at the time (in the commitãDM> message), but I don't think ever got those results/feedback. I'd like toãDM> better track the change request/rationale and the results this time.ããI think there were two issues going on at the time, happy to help this time.ã--- SBBSecho 3.20-Win32ã * Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Re: routing to pointsã By: Digital Man to Kurt Weiske on Fri Feb 17 2023 10:59 amãã > With this change (apparently as the result of a suggestion or request byã > Alterego), if the destination address is 1:2/3.1, but our local system hasã > an AKA of 1:2/3.2, no routing would occur (to a boss node or based onã > explicit routing configured in echocfg->Linked Nodes) and that seems like aã > bug to me. But still unrelated to your observations.ããWhy does that seem to be a bug?ããã...ëîåïãã---ã þ Synchronet þ AnsiTEX bringing back videotex but with ANSIã

Re: Re: routing to pointsã By: deon to Digital Man on Sat Feb 18 2023 10:30 amãã > Re: Re: routing to pointsã > By: Digital Man to Kurt Weiske on Fri Feb 17 2023 10:59 amã >ã > > With this change (apparently as the result of a suggestion or request byã > > Alterego), if the destination address is 1:2/3.1, but our local systemã > > has an AKA of 1:2/3.2, no routing would occur (to a boss node or based onã > > explicit routing configured in echocfg->Linked Nodes) and that seems likeã > > a bug to me. But still unrelated to your observations.ã >ã > Why does that seem to be a bug?ããI would think if my system had an AKA of 1:2/3.2 and I wanted to send a netmail to 1:2/3.1, it should still be auto-routed to the boss note (1:2/3.0) by default. No?ã-- ã digital man (rob)ããSynchronet "Real Fact" #39:ãSynchronet first supported Windows NT v6.x (a.k.a. Vista/Win7) w/v3.14a (2006)ãNorco, CA WX: 64.1øF, 17.0% humidity, 5 mph N wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Re: routing to pointsã By: Digital Man to deon on Fri Feb 17 2023 04:18 pmãã > > Why does that seem to be a bug?ã >ã > I would think if my system had an AKA of 1:2/3.2 and I wanted to send aã > netmail to 1:2/3.1, it should still be auto-routed to the boss noteã > (1:2/3.0) by default. No?ããSo you cant have a direct link to 1:2/3.1?ããã...ëîåïãã---ã þ Synchronet þ AnsiTEX bringing back videotex but with ANSIã

So you cant have a direct link to 1:2/3.1?ã de> ããnot unless you have a point list with 1:2/3.1fni noitcennoc s'ãconnection info in it.ããJohn H. Guilloryãcall sign KF5QEOãURL: kf5qeo.servebbs.netãKF5QEO's Shack BBSãã... Tech support is just a busy signal awayãã--- Mystic BBS v1.12 A48 (Linux/64)ã * Origin: KF5QEO's Shack -- kf5qeo.servebbs.netã

I would think if my system had an AKA of 1:2/3.2 and I wanted to send a netmaiã> to 1:2/3.1, it should still be auto-routed to the boss note (1:2/3.0) by defauã> . No?ããI would certainly think so.ããã * SLMR 2.1a * Are you pulling my leg! ...nahh, that's just the dog!ãã---ã þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTPã

deon wrote to Digital Man <=-ãã de> So you cant have a direct link to 1:2/3.1?ããYou can, if you specify 1:2/3.1 in echocfg and provide a source address.ããThere seems to have been some definition drift with points. When Iãstarted out, the whole idea behind a point was to have a mail-only orãprivate system that wasn't accessible during ZMH, or wasn't up 24/7. Theãpoint initiated contact with the boss, and the point was, by design,ãunreachable by systems using a nodelist.ããThe point would connect to the boss, not vice versa. Everything that wasãto go to the point was routed through the boss first. No one, even theãboss, would need a direct route to the point.ãããã... Powered By Celeron (Tualatin). Engineered for the future.ã--- MultiMail/Win v0.52ã * Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Re: routing to pointsã By: deon to Digital Man on Sat Feb 18 2023 10:05 pmãã > Re: Re: routing to pointsã > By: Digital Man to deon on Fri Feb 17 2023 04:18 pmã >ã > > > Why does that seem to be a bug?ã >ã > > I would think if my system had an AKA of 1:2/3.2 and I wanted to send aã > > netmail to 1:2/3.1, it should still be auto-routed to the boss noteã > > (1:2/3.0) by default. No?ã >ã > So you cant have a direct link to 1:2/3.1?ããSure, but I also might not. The way this requested-enhancement was implemented,ãit wouldn't make any difference: the mail would not be routed to the boss.ã-- ã digital man (rob)ããSynchronet "Real Fact" #27:ãRob Swindell (digital man) was born approximately 4 hours before the Unix epochãNorco, CA WX: 66.2øF, 20.0% humidity, 0 mph NE wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Re: routing to pointsã By: John Guillory to deon on Sat Feb 18 2023 08:33 amãã > not unless you have a point list with 1:2/3.1fni noitcennoc s'ã > connection info in it.ã >ã > John H. Guilloryã > call sign KF5QEOã > URL: kf5qeo.servebbs.netã > KF5QEO's Shack BBSã >ããoh, now i see. your url is wrong. that is why you are not connectable.ãyou are using a free bbs server the person setup for you on synchronetbbs.orgãsadã---ã þ Synchronet þ ::: BBSES.info - free BBS services :::ã

Re: Re: routing to pointsã By: Digital Man to deon on Sat Feb 18 2023 11:38 amãã > > > > Why does that seem to be a bug?ã >ã > > > I would think if my system had an AKA of 1:2/3.2 and I wanted to sendã > > > a netmail to 1:2/3.1, it should still be auto-routed to the boss noteã > > > (1:2/3.0) by default. No?ã >ã > > So you cant have a direct link to 1:2/3.1?ã >ã > Sure, but I also might not. The way this requested-enhancement wasã > implemented, it wouldn't make any difference: the mail would not be routedã > to the boss.ããOh, in that case I agree it might be a bug.ããI would have thought, if I'm a point, all mail would go to my boss (for final delivery), unless I had a specific relationship (and thus a configuration) directly to another system (including other points, either with a same boss as me, or a different boss).ããã...ëîåïãã---ã þ Synchronet þ AnsiTEX bringing back videotex but with ANSIã

Re: Re: routing to pointsã By: deon to Digital Man on Sun Feb 19 2023 09:28 amãã > Re: Re: routing to pointsã > By: Digital Man to deon on Sat Feb 18 2023 11:38 amã >ã > > > > > Why does that seem to be a bug?ã >ã > > > > I would think if my system had an AKA of 1:2/3.2 and I wanted toã > > > > send a netmail to 1:2/3.1, it should still be auto-routed to theã > > > > boss note (1:2/3.0) by default. No?ã >ã > > > So you cant have a direct link to 1:2/3.1?ã >ã > > Sure, but I also might not. The way this requested-enhancement wasã > > implemented, it wouldn't make any difference: the mail would not beã > > routed to the boss.ã >ã > Oh, in that case I agree it might be a bug.ã >ã > I would have thought, if I'm a point, all mail would go to my boss (forã > final delivery), unless I had a specific relationship (and thus aã > configuration) directly to another system (including other points, eitherã > with a same boss as me, or a different boss).ããThe logic was changed/fixed in a commit today. Try it out. Are you also Alterego?ã-- ã digital man (rob)ããRush quote #84:ãLooming low & ominous, twilight premature t-heads rumbling a distance overtureãNorco, CA WX: 66.9øF, 21.0% humidity, 0 mph E wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

Re: Re: routing to pointsã By: Kurt Weiske to deon on Sat Feb 18 2023 08:11 amãã > The point would connect to the boss, not vice versa. Everything that wasã > to go to the point was routed through the boss first. No one, even theã > boss, would need a direct route to the point.ããAnd it could still be that way "by default", right?ããMy point (no pun intended), is if the point defines some direct links, then they should be honoured, as well as the ability to receive direct connections from other systems (if the sysop desired).ããã...ëîåïãã---ã þ Synchronet þ AnsiTEX bringing back videotex but with ANSIã

Re: Re: routing to pointsã By: Digital Man to deon on Sat Feb 18 2023 02:57 pmãã > The logic was changed/fixed in a commit today. Try it out. Are you alsoã > Alterego?ããCool.ããI'm not actually using any points at the moment, but I probably will down the track. So I'll let you know if something is not up.ããI used the alias Alterego at some point, but dont anymore.ãã > > > > > I would think if my system had an AKA of 1:2/3.2 and I wanted toã > > > > > send a netmail to 1:2/3.1, it should still be auto-routed to theã > > > > > boss note (1:2/3.0) by default. No?ããFollowing on with this example, if I'm 1:2/3.2 and I want to send a Netmail to 1:2/4.2, *and* I have a configuration with 1:2/4.0 will sbbsecho package up my netmail for 1:2/4 or 1:2/3?ããIf it uses 1:2/3, I assume I can overrite it with a route 1:2/4.ALL to 1:2/4.0?ããã...ëîåïãã---ã þ Synchronet þ AnsiTEX bringing back videotex but with ANSIã

Re: Re: routing to pointsã By: deon to Digital Man on Sun Feb 19 2023 10:59 amãã > Re: Re: routing to pointsã > By: Digital Man to deon on Sat Feb 18 2023 02:57 pmã >ã > > The logic was changed/fixed in a commit today. Try it out. Are you alsoã > > Alterego?ã >ã > Cool.ã >ã > I'm not actually using any points at the moment, but I probably will downã > the track. So I'll let you know if something is not up.ã >ã > I used the alias Alterego at some point, but dont anymore.ã >ã > > > > > > I would think if my system had an AKA of 1:2/3.2 and I wantedã > > > > > > to send a netmail to 1:2/3.1, it should still be auto-routedã > > > > > > to the boss note (1:2/3.0) by default. No?ã >ã > Following on with this example, if I'm 1:2/3.2 and I want to send a Netmailã > to 1:2/4.2, *and* I have a configuration with 1:2/4.0 will sbbsecho packageã > up my netmail for 1:2/4 or 1:2/3?ããThe netmail would be routed to 1:2/4.0.ãã > If it uses 1:2/3, I assume I can overrite it with a route 1:2/4.ALL toã > 1:2/4.0?ããSBBSecho doesn't do any routing based on the originating-address, only the destination address.ã-- ã digital man (rob)ããThis Is Spinal Tap quote #40:ãMorty the Mime: Come on, don't talk back, mime is money, come on, move it.ãNorco, CA WX: 57.5øF, 32.0% humidity, 6 mph SE wind, 0.00 inches rain/24hrsã---ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã

deon wrote to Kurt Weiske <=-ãã de> My point (no pun intended), is if the point defines some direct links,ã de> then they should be honoured, as well as the ability to receive directã de> connections from other systems (if the sysop desired).ããThat flies against the notion that defined a point - a private systemãthat doesn't connect directly to the rest of the world, because it's notãup 24/7 or isn't able to honor ZMH.ããThat being said, Z2 may see things differently; they distribute aãpoint list publicly - in the traditional sense a point list is just usedãby the boss node.ããIf a point is accessible and makes arrangements to share their contactãinfo with an upstream node, that node can enter the information neededãto connect in the linked nodes section of sbbsecho, and the upstreamãnode can connect directly. That would override the default rule.ããããã... Onward, to meatspace!ã--- MultiMail/Win v0.52ã * Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)ã þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.netã