TIP: Click on subject to list as thread! ANSI
echo: synchronet
to: Ragnarok
from: Wilfred van Velzen
date: 2021-10-04 22:34:00
subject: Re: makenl sbbsecho and n

Hi Ragnarok,

On 2021-10-04 20:27:08, I wrote to you:

 >>> I don't know how synchronet works, so maybe this is "automatic", but I
 >>> think there should be an exception for this route:
 >>>
 >>> 39:943/ALL shouldn't be routed to 39:90/0 ! Because you would get those
 >>> messages back immediately, and a loop is born...
 >>>
 Ra>> Hi Wilfred! i don't route 39:943/all to 39:90/0

 WvV> You shouldn't but it seems you do!?

 Ra>> now, for the z39 i have:

 Ra>> 39:90/0 my boss -> your node :)
 Ra>> 39:ALL route to 39:90/0
 Ra>> 39:943/100 (my downlink node for testing)

 WvV> There is no "39:943/all no route"...?

What I was afraid of, is happening. I sent a test netmail to the none existing node 39:943/999, and this is what happend:

From the latest "bouncing" version of the netmail, when I caught it:

Via 39:943/0 @20211004.192054.UTC SBBSecho 3.14-Linux master/6722f2783
Via 39:90/0 @20211004.192210.843.UTC FMail-lnx64(Toss) 2.1.0.18-B20170815
Via 39:943/0 @20211004.192253.UTC SBBSecho 3.14-Linux master/6722f2783
Via 39:90/0 @20211004.192421.250.UTC FMail-lnx64(Toss) 2.1.0.18-B20170815
Via 39:943/0 @20211004.192654.UTC SBBSecho 3.14-Linux master/6722f2783
Via 39:90/0 @20211004.192827.694.UTC FMail-lnx64(Toss) 2.1.0.18-B20170815
Via 39:943/0 @20211004.193102.UTC SBBSecho 3.14-Linux master/6722f2783
Via 39:90/0 @20211004.193159.285.UTC FMail-lnx64(Toss) 2.1.0.18-B20170815
Via 39:943/0 @20211004.193458.UTC SBBSecho 3.14-Linux master/6722f2783
Via 39:90/0 @20211004.193621.548.UTC FMail-lnx64(Toss) 2.1.0.18-B20170815
Via 39:943/0 @20211004.193859.UTC SBBSecho 3.14-Linux master/6722f2783
Via 39:90/0 @20211004.194045.768.UTC FMail-lnx64(Toss) 2.1.0.18-B20170815
Via 39:943/0 @20211004.194358.UTC SBBSecho 3.14-Linux master/6722f2783
Via 39:90/0 @20211004.194521.068.UTC FMail-lnx64(Toss) 2.1.0.18-B20170815
Via 39:943/0 @20211004.194558.UTC SBBSecho 3.14-Linux master/6722f2783
Via 39:90/0 @20211004.194716.218.UTC FMail-lnx64(Toss) 2.1.0.18-B20170815
Via 39:943/0 @20211004.194959.UTC SBBSecho 3.14-Linux master/6722f2783
Via 39:90/0 @20211004.195125.831.UTC FMail-lnx64(Toss) 2.1.0.18-B20170815
Via 39:943/0 @20211004.195358.UTC SBBSecho 3.14-Linux master/6722f2783
Via 39:90/0 @20211004.195517.289.UTC FMail-lnx64(Toss) 2.1.0.18-B20170815
Via 39:943/0 @20211004.195759.UTC SBBSecho 3.14-Linux master/6722f2783
Via 39:90/0 @20211004.195925.747.UTC FMail-lnx64(Toss) 2.1.0.18-B20170815
Via 39:943/0 @20211004.200159.UTC SBBSecho 3.14-Linux master/6722f2783
Via 39:90/0 @20211004.200319.518.UTC FMail-lnx64(Toss) 2.1.0.18-B20170815
Via 39:943/0 @20211004.200619.UTC SBBSecho 3.14-Linux master/6722f2783
Via 39:90/0 @20211004.200740.613.UTC FMail-lnx64(Toss) 2.1.0.18-B20170815
Via 39:943/0 @20211004.201019.UTC SBBSecho 3.14-Linux master/6722f2783


Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
                                                                               
* Origin: FMail development HQ (2:280/464)

SOURCE: echomail via QWK@pharcyde.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.