Hi All,

New ZIN in Z1:
Pvt,100,Ozz_Nixon,Crestview_FL,Ozz_Nixon,-Unpublished-,300

There is nothing to test. And a Pvt node is not allowed in a ZIN section anyway.

Nodes:
,111,Alien_Signals_BBS,Dutton_ON,Scott_Carter Down,550,Point_Of_No_Return,Toronto_ON,Mark_Da_Silva
Were removed from Net 229.

Node:
,2,Election_Coodinator,Buffalo_NY,Robert_Wolfe
In R13, is still present in the Z2 weekly, that's probably because of: Zone,1,North_America_(309)

Which is 2 days behind the current day. :-(


Regards, Wilfred


--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)

Hi All,

On 2025-11-07 11:57:04, I wrote to you:

Node:
,2,Election_Coodinator,Buffalo_NY,Robert_Wolfe
In R13, is still present in the Z2 weekly, that's probably because of: Zone,1,North_America_(309)

Which is 2 days behind the current day. :-(

This RIN is now also gone from the Z2 nodelist.

Node: ,20,Omicron_Theta,Memphis_TN,Robert_Wolfe is still present in net 261.


Other than that, there are no noteworthy changes this week.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)

Hi All,

The nodes of Stephen_Hurd in net 103 are updated.
Node 1 had an INA flag added:
1:103/1 bbsdev.net:24554 2001:19f0:6000:94c9::81:241 Ok.
1:103/1 bbsdev.net:24554 45.32.81.241 Ok.
Node 13 is no longer Pvt:
1:103/13 wd1cks.org:24554 2001:19f0:6000:94c9::68:234 Ok.
1:103/13 wd1cks.org:24554 45.32.68.234 Ok.
Node 17 had the ITN flag removed

Only issue remaining in net 103 is with the host:

1:103/0 realitycheckbbs.org:24554 73.158.236.238 No such AKA.

In net 135 node was removed:
,230,Nite_Eyes_BBS,Davie_FL,Alex_Corris

New RIN in R19: ,42,CosmoNET_BBS,Sallisaw_OK,Brian_Scott,-Unpublished-,300,XA,INA:chipcunk.synchro.net,IBN

It is not a CM node, but if it isn't online you don't expect a TCP/IP connect at all:
+ 21 Nov 12:40:29 [21570] call to 1:19/42@fidonet
21 Nov 12:40:31 [21570] trying chipcunk.synchro.net [74.208.78.19]...
21 Nov 12:40:31 [21570] connected
+ 21 Nov 12:40:31 [21570] outgoing session with chipcunk.synchro.net:24554 [74.208.78.19]
? 21 Nov 12:40:31 [21570] recv: connection closed by foreign host
+ 21 Nov 12:40:31 [21570] done (to 1:19/42@fidonet, failed, S/R: 0/0 (0/0 bytes))

Node 2:221/360 has got the IVM flag added. There is a TCP/IP connect at the default IVM poort (3141), but I can't test the protocol. ;-)

New node in net 341: ,207,Citrick_BBS,Tenerife,Tanausu_Martin_Gonzalez,-Unpublished-,300,CM,XW,IBN:citlmbbs.synchro.net
Connect OK with: BinkIT/2.42,JSBinkP/4,sbbs3.21a/FreeBSD

Node 2:5031/52 was put on Hold.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)

Hello Wilfred,

On Friday November 21 2025 12:52, you wrote to All:

New RIN in R19: ,42,CosmoNET_BBS,Sallisaw_OK,Brian_Scott,-Unpublished-,300,XA,INA:chip cunk.synchro.net,IBN

It is not a CM node, but if it isn't online you don't expect a TCP/IP connect at all:

Or a connect anyway, despite the ZMH restriction. I get a connect:

+ 21:50 [5920] call to 1:19/42@fidonet
21:50 [5920] trying f42.n19.z1.binkp.net [157.250.195.244]...
21:50 [5920] connected
+ 21:50 [5920] outgoing session with f42.n19.z1.binkp.net:24554
[157.250.195.244]
- 21:50 [5920] OPT CRAM-MD5-bae787e19231ee85a60856e1309fd668 CRYPT
+ 21:50 [5920] Remote requests MD mode
+ 21:50 [5920] Remote requests CRYPT mode
- 21:50 [5920] SYS The Ham Shack BBS
- 21:50 [5920] ZYZ Brian Scott
- 21:50 [5920] LOC Siloam Springs, Ar.
- 21:50 [5920] NDL 115200,TCP,BINKP
- 21:50 [5920] TIME Sat Nov 22 2025 14:50:03 GMT-0600 (CST)
- 21:50 [5920] VER BinkIT/2.42,JSBinkP/4,sbbs3.21a/Linux binkp/1.1
+ 21:50 [5920] addr: 1:19/42@fidonet


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)

Hi Michiel,

On 2025-11-22 21:51:18, you wrote to me:

New RIN in R19:
,42,CosmoNET_BBS,Sallisaw_OK,Brian_Scott,-Unpublished-,300,XA,INA:chi
pcunk.synchro.net,IBN

It is not a CM node, but if it isn't online you don't expect a TCP/IP
connect at all:

MvdV> Or a connect anyway, despite the ZMH restriction. I get a connect:

MvdV> + 21:50 [5920] call to 1:19/42@fidonet
MvdV> 21:50 [5920] trying f42.n19.z1.binkp.net [157.250.195.244]...
MvdV> 21:50 [5920] connected
MvdV> + 21:50 [5920] outgoing session with f42.n19.z1.binkp.net:24554
MvdV> [157.250.195.244]
MvdV> - 21:50 [5920] OPT CRAM-MD5-bae787e19231ee85a60856e1309fd668 CRYPT
MvdV> + 21:50 [5920] Remote requests MD mode
MvdV> + 21:50 [5920] Remote requests CRYPT mode
MvdV> - 21:50 [5920] SYS The Ham Shack BBS
MvdV> - 21:50 [5920] ZYZ Brian Scott
MvdV> - 21:50 [5920] LOC Siloam Springs, Ar.
MvdV> - 21:50 [5920] NDL 115200,TCP,BINKP
MvdV> - 21:50 [5920] TIME Sat Nov 22 2025 14:50:03 GMT-0600 (CST)
MvdV> - 21:50 [5920] VER BinkIT/2.42,JSBinkP/4,sbbs3.21a/Linux binkp/1.1
MvdV> + 21:50 [5920] addr: 1:19/42@fidonet

Same here, now...


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)

Hello Wilfred!

21 Nov 25 12:52, you wrote to all:

Node 2:221/360 has got the IVM flag added. There is a TCP/IP connect
at the default IVM poort (3141), but I can't test the protocol. ;-)

Attempting to poll using my OS/2 VMODEM capable system resulted in "NO CARRIER" so there still seems to be some kind of issue. I can confirm that ITN sessions to the listed port are answered by FrontDoor/2 and mbcico was able to negotiate a successful WaZOO/EMSI session.

Andrew

--- GoldED+/LNX 1.1.5-b20250409
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

Sunday November 23 2025 07:09, Andrew Leary wrote to Wilfred van Velzen:

Hello Wilfred!

21 Nov 25 12:52, you wrote to all:

Node 2:221/360 has got the IVM flag added. There is a TCP/IP
connect at the default IVM poort (3141), but I can't test the
protocol. ;-)

Attempting to poll using my OS/2 VMODEM capable system resulted in "NO
CARRIER" so there still seems to be some kind of issue. I can
confirm that ITN sessions to the listed port are answered by
FrontDoor/2 and mbcico was able to negotiate a successful WaZOO/EMSI session.

Thanks for testing.

There might to be some issue with inbound vmodem connections via haproxy. :)

'Tommi

--- GEcho/2 1.20/Pro
* Origin: * RBB * Lake Ylo * Finland * (2:221/360)

Sunday November 23 2025 14:58, Tommi Koivula wrote to Andrew Leary:

Attempting to poll using my OS/2 VMODEM capable system resulted
in "NO
CARRIER" so there still seems to be some kind of issue. I can
confirm that ITN sessions to the listed port are answered by
FrontDoor/2 and mbcico was able to negotiate a successful
WaZOO/EMSI session.

Thanks for testing.

There might to be some issue with inbound vmodem connections via
haproxy. :)

However, I tried to poll you but I get:

1-23 17:16 Outgoing to 24.62.213.214 from COM5 on port/socket 3141
1-23 17:16 TCP/IP says "Connection refused"
1-23 17:16 Outgoing to 24.62.213.214 from COM5 on port/socket 3141
1-23 17:16 TCP/IP says "Connection refused"

'Tommi

--- GEcho/2 1.20/Pro
* Origin: * RBB * Lake Ylo * Finland * (2:221/360)

Hello Tommi!

23 Nov 25 17:17, you wrote to me:

Attempting to poll using my OS/2 VMODEM capable system resulted
in "NO
CARRIER" so there still seems to be some kind of issue. I can
confirm that ITN sessions to the listed port are answered by
FrontDoor/2 and mbcico was able to negotiate a successful
WaZOO/EMSI session.

Thanks for testing.

There might to be some issue with inbound vmodem connections via
haproxy. :)

However, I tried to poll you but I get:

1-23 17:16 Outgoing to 24.62.213.214 from COM5 on port/socket 3141
1-23 17:16 TCP/IP says "Connection refused"
1-23 17:16 Outgoing to 24.62.213.214 from COM5 on port/socket 3141
1-23 17:16 TCP/IP says "Connection refused"

I had turned the firewall rule off while testing something and promptly forgot to re-enable it. Fixed now.

Andrew

--- GoldED+/LNX 1.1.5-b20250409
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

Sunday November 23 2025 12:33, Andrew Leary wrote to Tommi Koivula:

1-23 17:16 Outgoing to 24.62.213.214 from COM5 on port/socket
3141 1-23 17:16 TCP/IP says "Connection refused" 1-23 17:16
Outgoing to 24.62.213.214 from COM5 on port/socket 3141 1-23
17:16 TCP/IP says "Connection refused"

I had turned the firewall rule off while testing something and
promptly forgot to re-enable it. Fixed now.

Yes, the port is now open, but I cannot connect.


ATDT "#BBS.BNBBBS.NET"
NO CARRIER


11-23 19:58 Outgoing to 24.62.213.214 from COM5 on port/socket 3141
11-23 19:58 We are negotiating with the remote
11-23 19:58 COM5 disconnected
11-23 19:58 Outgoing to 24.62.213.214 from COM5 on port/socket 3141
11-23 19:58 We are negotiating with the remote
11-23 19:58 COM5 disconnected
11-23 19:58 Outgoing to 24.62.213.214 from COM5 on port/socket 3141
11-23 19:58 We are negotiating with the remote
11-23 19:58 COM5 disconnected

23 Nov 19:58:40 XEN Mailing noname (1:320/119)
23 Nov 19:58:40 XEN Assuming ID 2:221/360@fidonet
23 Nov 19:58:40 XEN Dialling bbs.bnbbbs.net (cm,vmp,tel)
23 Nov 19:58:43 XEN No connect (no carrier)
23 Nov 19:58:46 XEN Mailing noname (1:320/119)
23 Nov 19:58:46 XEN Assuming ID 2:221/360@fidonet
23 Nov 19:58:46 XEN Dialling bbs.bnbbbs.net (cm,vmp,tel)
23 Nov 19:58:49 XEN No connect (no carrier)

Well, I'll turn IVM off, like it has been for many years. ITN works. ;)

'Tommi

--- GEcho/2 1.20/Pro
* Origin: * RBB * Lake Ylo * Finland * (2:221/360)

Hi All,

On 2025-11-21 12:52:26, I wrote to you:

Only issue remaining in net 103 is with the host:

1:103/0 realitycheckbbs.org:24554 73.158.236.238 No such AKA.

No change here.

New RIN in R19: ,42,CosmoNET_BBS,Sallisaw_OK,Brian_Scott,-Unpublished-,300,XA,INA:chi pcunk.synchro.net,IBN

It is not a CM node, but if it isn't online you don't expect a TCP/IP connect
at all

The system name, location, and INA for this RIN were updated: ,42,The_Ham_Shack_BBS,Siloam_Springs_AR,Brian_Scott,-Unpublished-,300,XA,INA:hamshack.synchro.net,IBN

Connect OK with: BinkIT/2.42,JSBinkP/4,sbbs3.21a/Linux


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)

Hi All,

New node in net 124: ,75,The_Ham_Shack_BBS,Siloam_Springs_AK,Brian_Scott,-Unpublished-,300,CM,XW,INA:hamshack.synchro.net,IBN
This is the same system as RIN 1:19/42. So connect, but this new AKA hasn't been configured yet.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)

Hi Tommi,

On 2025-11-23 19:59:43, you wrote to Andrew Leary:

Well, I'll turn IVM off, like it has been for many years.

Confirmed, it has been removed from your nodelist entries. ;-)


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)

Wilfred van Velzen wrote to All <=-

Hi All,

On 2025-11-21 12:52:26, I wrote to you:

Only issue remaining in net 103 is with the host:

1:103/0 realitycheckbbs.org:24554 73.158.236.238 No such AKA.

No change here.

That's not a nodelist issue, that's a configuration issue on my board -
which I've fixed. My board wasn't configured with 1023/0. Thanks for
letting me know.



--- MultiMail/Win v0.52
* Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)

Hi Kurt,

On 2025-11-29 10:10:15, you wrote to me:

Only issue remaining in net 103 is with the host:

1:103/0 realitycheckbbs.org:24554 73.158.236.238 No such AKA.

No change here.

That's not a nodelist issue,

That depends on how you look at it. Reality is different from the nodelist. ;-)

that's a configuration issue on my board - which I've fixed. My board wasn't configured with 1023/0. Thanks for letting me know.

Not yet:

Parsing nodelist file /home/fido/zadaily/makenl/out/zadaily.333
Nodelist for Saturday, November 29, 2025 -- Day number 333 parsed, 935 IP-nodes processed (0.013 sec)
Calling '1:103/0'. Call time: '0000-2400' UTC.
Now is: 2159 UTC.
realitycheckbbs.org, 24554
Calling 1:103/0 (73.158.236.238:24554)
OPT CRAM-MD5-7418ea8b688dd86826317567bd34e120 CRYPT
SYS realitycheckBBS
ZYZ Kurt Weiske
LOC Aptos, CA
NDL 115200,TCP,BINKP
TIME Sat Nov 29 2025 13:59:02 GMT-0800 (Pacific Standard Time)
VER BinkIT/2.41,JSBinkP/4,sbbs3.21a/Win32 binkp/1.1
address: 1:218/700@fidonet
address: 1:218/1@fidonet
address: 1:10/1@fidonet
address: 1:13/0@fidonet
address: 1:218/0@fidonet
address: 1:10/0@fidonet
address: 700:100/20@spooknet
address: 21:4/122@fsxnet
address: 1337:3/178@tqwnet
address: 911:1415/0@zeronet
No such AKA.



Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)

Wilfred van Velzen wrote to Kurt Weiske <=-

That's not a nodelist issue,

That depends on how you look at it. Reality is different from the nodelist. ;-)

that's a configuration issue on my board - which I've fixed. My board wasn't configured with 1023/0. Thanks for letting me know.

Not yet:

Parsing nodelist file /home/fido/zadaily/makenl/out/zadaily.333
Nodelist for Saturday, November 29, 2025 -- Day number 333 parsed, 935 IP-nodes processed (0.013 sec) Calling '1:103/0'. Call time:
'0000-2400' UTC.
Now is: 2159 UTC.
realitycheckbbs.org, 24554
Calling 1:103/0 (73.158.236.238:24554)
OPT CRAM-MD5-7418ea8b688dd86826317567bd34e120 CRYPT
SYS realitycheckBBS
ZYZ Kurt Weiske
LOC Aptos, CA
NDL 115200,TCP,BINKP
TIME Sat Nov 29 2025 13:59:02 GMT-0800 (Pacific Standard Time)
VER BinkIT/2.41,JSBinkP/4,sbbs3.21a/Win32 binkp/1.1
address: 1:218/700@fidonet
address: 1:218/1@fidonet
address: 1:10/1@fidonet
address: 1:13/0@fidonet
address: 1:218/0@fidonet
address: 1:10/0@fidonet
address: 700:100/20@spooknet
address: 21:4/122@fsxnet
address: 1337:3/178@tqwnet
address: 911:1415/0@zeronet
No such AKA.

According to this, he's also RC13 (which he is not).

Come on, Weiske. Do better ferchrissakes. You're a fuckin RC,
supposedly. Quit acting like a clueless n00b.



... So easy, a child could do it. Child sold separately.
=== MultiMail/Linux v0.52
--- SBBSecho 3.32-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)

* Originally in NODELIST-POLICE
* Crossposted in OS2
28 Nov 25 12:39, Wilfred van Velzen wrote to Tommi Koivula:

Well, I'll turn IVM off, like it has been for many years.

Confirmed, it has been removed from your nodelist entries. ;-)

Yep, VMODEM was pretty nice once, but that was 30 years ago, before BinkP. ;-)

But I still wonder why it works locally in my home network, but does not over the internet. Can anyone confirm a working VMODEM link over the internet? There are not so many IVM flags in the nodelist and some of those are not VMODEM but TELNET servers.

'Tommi

---
* Origin: * RBB * Lake Ylo * Finland * (2:221/360)

Hi Kurt,

On 2025-11-29 22:59:28, I wrote to you:

1:103/0 realitycheckbbs.org:24554 73.158.236.238 No such AKA.

No change here.

That's not a nodelist issue,

that's a configuration issue on my board - which I've fixed. My board
wasn't configured with 1023/0. Thanks for letting me know.

Not yet:

Parsing nodelist file /home/fido/zadaily/makenl/out/zadaily.333
Nodelist for Saturday, November 29, 2025 -- Day number 333 parsed, 935 IP-nodes processed (0.013 sec) Calling '1:103/0'. Call time: '0000-2400' UTC.
Now is: 2159 UTC. realitycheckbbs.org, 24554 Calling 1:103/0 (73.158.236.238:24554) OPT CRAM-MD5-7418ea8b688dd86826317567bd34e120 CRYPT SYS
realitycheckBBS ZYZ Kurt Weiske LOC Aptos, CA NDL 115200,TCP,BINKP TIME Sat
Nov 29 2025 13:59:02 GMT-0800 (Pacific Standard Time) VER BinkIT/2.41,JSBinkP/4,sbbs3.21a/Win32 binkp/1.1
address: 1:218/700@fidonet
address: 1:218/1@fidonet
address: 1:10/1@fidonet
address: 1:13/0@fidonet
address: 1:218/0@fidonet
address: 1:10/0@fidonet
address: 700:100/20@spooknet
address: 21:4/122@fsxnet
address: 1337:3/178@tqwnet
address: 911:1415/0@zeronet
No such AKA.

Still not fixed:

Calling '1:103/0'. Call time: '0000-2400' UTC.
Now is: 1138 UTC.
realitycheckbbs.org, 24554
Calling 1:103/0 (73.158.236.238:24554)
OPT CRAM-MD5-2f51796bc88f8ff6226132dfa55f80a5 CRYPT
SYS realitycheckBBS
ZYZ Kurt Weiske
LOC Aptos, CA
NDL 115200,TCP,BINKP
TIME Fri Dec 05 2025 03:38:53 GMT-0800 (Pacific Standard Time)
VER BinkIT/2.41,JSBinkP/4,sbbs3.21a/Win32 binkp/1.1
address: 1:218/700@fidonet
address: 1:218/1@fidonet
address: 1:10/1@fidonet
address: 1:218/0@fidonet
address: 1:10/0@fidonet
address: 700:100/20@spooknet
address: 21:4/122@fsxnet
address: 1337:3/178@tqwnet
address: 911:1415/0@zeronet
No such AKA.

But the 1:13/0 aka is at least gone! ;-)


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)

Hi All,

On 2025-11-28 12:41:38, I wrote to you:

New node in net 124: ,75,The_Ham_Shack_BBS,Siloam_Springs_AK,Brian_Scott,-Unpublished-,300 ,CM,XW,INA:hamshack.synchro.net,IBN

This is the same system as RIN 1:19/42. So connect, but this new AKA hasn't been configured yet.

Not fixed yet.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)

Hi All,

New node in net 229: ,134,The_Montreal_Geek_Times,Montreal_QC,Dimitri_Papadopoulos,-Unpublished-,300,CM,INA:bbs.greektimes.ca,IBN
Connect OK with BinkIT/2.42,JSBinkP/4,sbbs3.21a/Linux

Host entry 1:320/0 and node 1:320/119, got the IVM flag removed. ;-)

New node in net 135: ,260,Overfit,Bridgetown_Barbados,John_Merritt,-Unpublished-,300,CM,INA:overfit.retrievo.xyz,IBN
Connect OK with BinkIT/2.42,JSBinkP/4,sbbs3.21a/Linux

New node in net 280: ,2070,The_Forze,Almere,Robbert_Langezaal,-Unpublished-,300,CM,IBN:bbs.theforze.eu
Connect with Mystic/1.12A49 binkp/1.0
But:
address: 2:280/9999@fidonet
No such AKA.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)

05 Dec 25 12:54, Wilfred van Velzen wrote to All:

Host entry 1:320/0 and node 1:320/119, got the IVM flag removed. ;-)

+1 ;)

'Tommi

--- FastEcho/2 1.46.1 Revival
* Origin: ==========================>>> (2:221/1.1530)

Wilfred van Velzen wrote to Kurt Weiske <=-

Still not fixed:

Calling '1:103/0'. Call time: '0000-2400' UTC.

Yes, adding 103/0 introduced an issue with mail routing. I've taken it
out while we sort things out. You don't need to send any more emails,
I'm aware of the issue and will resolve it when feasible.



--- MultiMail/Win v0.52
* Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)

Hi All,

On 2025-12-05 12:54:44, I wrote to you:

New node in net 280: ,2070,The_Forze,Almere,Robbert_Langezaal,-Unpublished-,300,CM,IBN:bbs .theforze
.eu Connect with Mystic/1.12A49 binkp/1.0
But:
address: 2:280/9999@fidonet
No such AKA.

Not fixed yet. :-(


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)

Hi All,

New node in net 154: ,120,The_Noise_forest,Richfield_MN,Matt_Jurcich,-Unpublished-,300,CM,INA:thenoiseforest.invisik.net,IBN
Calling 1:154/120 (74.95.142.91:24554)
error (Connection timed out)

New node in net 105: ,15,Angstridden_BBS,Portland_OR,Steve_Layton,-Unpublished-,300,CM,IBN:angstridden.net
Connect with gobinkdgo/0.1
I have never heard of that mailer!?

New node in net 3634: ,61,The_Looney_Bin_BBS,Sunset_Beach_NC_USA,Patrick_Finnerty,-Unpublished-,300,INA:looneybinbbs.com,CM,IBN
Connect Ok with: Mystic/1.12A48

Down node 2:463/407 was removed. That could have been an oportunity to update another node in net 463:
2:463/877 bbs.ncc.org.ua:24554 2a01:d5:0:21b:f1d0:2:463:877 Error: Connection timed out
2:463/877 bbs.ncc.org.ua:24554 62.205.153.104 Error: Connection timed out
Maybe it's a temporary problem. The last time I checked this node in May this year it was ok.

Node 2:5031/78 is no longer on Hold. Connect with: binkd/1.1a-115/Linux

New host name for Host and node in net 371. Also a new IBN port number for the Host, and the IVM flag added for the node.
Connect ok with: binkd/1.1a-115/Linux (2:371/0) and binkd/1.1a-115/OS2 (2:371/52)
For 2:371/52 there is "Xenia Mailer 1.99.00 OS/2" responding on the ITN port, and a tcp/ip connect on the IVM port. I can't test the protocols


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)

Hi All,

On 2025-12-12 13:09:20, I wrote to you:

New node in net 154: ,120,The_Noise_forest,Richfield_MN,Matt_Jurcich,-Unpublished-,300,CM, INA:thenoiseforest.invisik.net,IBN
Calling 1:154/120 (74.95.142.91:24554) error
(Connection timed out)

Not fixed yet.

Down node 2:463/407 was removed. That could have been an oportunity
to update another node in net 463:
2:463/877 bbs.ncc.org.ua:24554 2a01:d5:0:21b:f1d0:2:463:877
Error: Connection timed out
2:463/877 bbs.ncc.org.ua:24554 62.205.153.104
Error: Connection timed out

Maybe it's a temporary problem. The last time I checked this node in
May this year it was ok.

It was temporary, because I can connect now.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)

Hi All,

The prolog was updated with the seasonal wishes (and remarks and requests ;-))...

Node 1:229/705 is no longer Pvt, and got ,CM,INA:halcyonbbs.scisweb.org,IBN added.
Timeout on IPv6, connect on IPv4 with: BinkIT/2.41,JSBinkP/4,sbbs3.20d/Linux

Attempted new RIN entry in R19:
;E ,43,Fireside_BBS,Little_Flock_AR,Vincent_Jacobs,-Unpulished-,300,XA,INA:firesidebbs/com,IBN
;E -- Invalid phone number -- '-Unpulished-'
And the INA is also wrong. But there is a connect on the corrected INA, with: BinkIT/2.41,JSBinkP/4,sbbs3.20d/Win32

New node in net 6035: ,5,f5.n6035.z2.binkp.net,Zheleznogorsk,Vitaliy_Poluhin,-Unpublished-,300,MO,CM,IBN,INA:f5.n6035.z2.binkp.net
Connect OK with: binkd/1.1a-49/Win32 binkp/1.1


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)

On 19/12/25 12:38 you wrote:

The prolog was updated with the seasonal wishes (and remarks and requests ;-))...

New one ;-)

;S Ollands: Hartstikke Zalige Kerst en Nieuwjaar

--
Carlos
--- Hotdoged/2.13.5/Android
* Origin: cyberiada (2:341/234.12)

Hi Carlos,

On 2025-12-19 17:51:27, you wrote to me:

The prolog was updated with the seasonal wishes (and remarks and
requests ;-))...

New one ;-)

;S Ollands: Hartstikke Zalige Kerst en Nieuwjaar

That sounds abour right! ;-)


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: NPC Station (2:280/464)

Hi All,

On 2025-12-19 12:38:28, I wrote to you:

Node 1:229/705 is no longer Pvt, and got ,CM,INA:halcyonbbs.scisweb.org,IBN
added. Timeout on IPv6, connect on IPv4 with: BinkIT/2.41,JSBinkP/4,sbbs3.20d/Linux

IPv6 issue not fixed yet.

Attempted new RIN entry in R19: ;E,43,Fireside_BBS,Little_Flock_AR,Vincent_Jacobs,-Unpulished-,300,XA ,INA:firesidebbs/com,IBN
;E -- Invalid phone number -- '-Unpulished-'
And the INA is also wrong. But there is a connect on the corrected
INA, with: BinkIT/2.41,JSBinkP/4,sbbs3.20d/Win32

This nodelist entry is fixed.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.5-B20251222
* Origin: NPC Station (2:280/464)

Hi All,

New node in net 135: ,205,CW_Shack_BBS,Winter_Park_FL,Tom_Moore,-Unpublished-,300,CM,INA:cwshack.ddns.net,IBN
Connect with: BinkIT/2.42,JSBinkP/4,sbbs3.21a/Linux

Node 2:5053/49 was put on Hold. (Not tested, it is IMI only)

New node in net 633: Pvt,10,PyGate-FTN-UsenetGateway,Tullamarine_Vic,Stephen_Walsh,-Unpublished-,300,MO
There is nothing to test. ;-)


Bye, Wilfred.

--- FMail-lnx64 2.3.2.5-B20251222
* Origin: NPC Station (2:280/464)

Hi All,

On 2025-12-12 13:09:20, I wrote to you:

New node in net 154:

,120,The_Noise_forest,Richfield_MN,Matt_Jurcich,-Unpublished-,300,CM,

INA:thenoiseforest.invisik.net,IBN WvV> Calling 1:154/120

(74.95.142.91:24554) error WvV> (Connection timed out)

Not fixed yet.

We're working on it. I can connect to him, but opening that port to the world is one of the things he needs to finish yet.

Holidays are getting in the way :)


--- AfterShock/Android 1.7.5
* Origin: South of Heaven - Chaos rampant, an age of distrust (1:154/30.1)

Hi Mike,

On 2025-12-27 21:38:31, you wrote to me:

New node in net 154:

,120,The_Noise_forest,Richfield_MN,Matt_Jurcich,-Unpublished-,300,CM,

INA:thenoiseforest.invisik.net,IBN WvV> Calling 1:154/120

(74.95.142.91:24554) error WvV> (Connection timed out)

Not fixed yet.

We're working on it. I can connect to him, but opening that port to
the world is one of the things he needs to finish yet.

1 Minute job!?

Holidays are getting in the way :)

You could mark the node 'Hold' for the time being...


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hi Mike,

On 2025-12-28 12:28:49, I wrote to you:

New node in net 154:

,120,The_Noise_forest,Richfield_MN,Matt_Jurcich,-Unpublished-,300,CM,

INA:thenoiseforest.invisik.net,IBN WvV> Calling 1:154/120

(74.95.142.91:24554) error WvV> (Connection timed out)

Not fixed yet.

We're working on it. I can connect to him, but opening that port to
the world is one of the things he needs to finish yet.

1 Minute job!?

Holidays are getting in the way :)

You could mark the node 'Hold' for the time being...

As of today, I still get a timeout, and there is no change of status in the nodelist...


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hi All,

New node in net 322: ,320,Lost_Crypt_BBS,Worcester_MA,Rick_Svyzek,-Unpublished-,300,CM,INA:bbs.lostcrypt.com,IBN
Connect with BinkIT/2.41,JSBinkP/4,sbbs3.20d/Win32
But:
address: 1:320/9999@fidonet
No such AKA.

New node in net 221: Pvt,40,ParaSite_BBS,Kotka,Kimmo_Viitanen,-Unpublished-,300,IBN
There is nothing to test...


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hi Wilfred.

02 Jan 26 13:16:38, you wrote to All:

New node in net 221: Pvt,40,ParaSite_BBS,Kotka,Kimmo_Viitanen,-Unpublished-,300,IBN
There is nothing to test...

Network 221 segment updated, but as you know in R20 you have to wait a week...

'Tommi

---
* Origin: Point One (2:221/1.1)

Hi Tommi,

On 2026-01-02 18:59:23, you wrote to me:

New node in net 221:
Pvt,40,ParaSite_BBS,Kotka,Kimmo_Viitanen,-Unpublished-,300,IBN
There is nothing to test...

Network 221 segment updated, but as you know in R20 you have to wait a week...

I don't, but there are no daily updates in R20?


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hi Wilfred.

02 Jan 26 18:18:42, you wrote to me:

New node in net 221:
Pvt,40,ParaSite_BBS,Kotka,Kimmo_Viitanen,-Unpublished-,300,IBN
There is nothing to test...

Network 221 segment updated, but as you know in R20 you have to
wait a week...

I don't, but there are no daily updates in R20?

Yep. As you can see, the updates get into the Z2DAILY's only once in a week:

=== Cut ===
grep "Host,221,Finland" Z2DAILY.3* Z1DAILY.337:Host,221,Finland_(331),Ylojarvi,Tommi_Koivula,-U Z1DAILY.338:Host,221,Finland_(331),Ylojarvi,Tommi_Koivula,-U Z1DAILY.339:Host,221,Finland_(338),Ylojarvi,Tommi_Koivula,-U Z1DAILY.340:Host,221,Finland_(338),Ylojarvi,Tommi_Koivula,-U Z1DAILY.341:Host,221,Finland_(338),Ylojarvi,Tommi_Koivula,-U Z1DAILY.342:Host,221,Finland_(338),Ylojarvi,Tommi_Koivula,-U Z1DAILY.343:Host,221,Finland_(338),Ylojarvi,Tommi_Koivula,-U Z1DAILY.344:Host,221,Finland_(338),Ylojarvi,Tommi_Koivula,-U Z1DAILY.345:Host,221,Finland_(338),Ylojarvi,Tommi_Koivula,-U Z1DAILY.346:Host,221,Finland_(345),Ylojarvi,Tommi_Koivula,-U Z1DAILY.347:Host,221,Finland_(345),Ylojarvi,Tommi_Koivula,-U Z1DAILY.348:Host,221,Finland_(345),Ylojarvi,Tommi_Koivula,-U Z1DAILY.349:Host,221,Finland_(345),Ylojarvi,Tommi_Koivula,-U Z1DAILY.350:Host,221,Finland_(345),Ylojarvi,Tommi_Koivula,-U Z1DAILY.351:Host,221,Finland_(345),Ylojarvi,Tommi_Koivula,-U Z1DAILY.352:Host,221,Finland_(345),Ylojarvi,Tommi_Koivula,-U Z1DAILY.353:Host,221,Finland_(352),Ylojarvi,Tommi_Koivula,-U Z1DAILY.354:Host,221,Finland_(352),Ylojarvi,Tommi_Koivula,-U Z1DAILY.355:Host,221,Finland_(352),Ylojarvi,Tommi_Koivula,-U Z1DAILY.356:Host,221,Finland_(352),Ylojarvi,Tommi_Koivula,-U Z1DAILY.357:Host,221,Finland_(352),Ylojarvi,Tommi_Koivula,-U Z1DAILY.358:Host,221,Finland_(352),Ylojarvi,Tommi_Koivula,-U Z1DAILY.359:Host,221,Finland_(352),Ylojarvi,Tommi_Koivula,-U Z1DAILY.360:Host,221,Finland_(359),Ylojarvi,Tommi_Koivula,-U Z1DAILY.361:Host,221,Finland_(359),Ylojarvi,Tommi_Koivula,-U Z1DAILY.362:Host,221,Finland_(359),Ylojarvi,Tommi_Koivula,-U Z1DAILY.363:Host,221,Finland_(359),Ylojarvi,Tommi_Koivula,-U Z1DAILY.364:Host,221,Finland_(359),Ylojarvi,Tommi_Koivula,-U Z1DAILY.365:Host,221,Finland_(359),Ylojarvi,Tommi_Koivula,-U
=== Cut ===

'Tommi

---
* Origin: Point One (2:221/1.1)

Hi Tommi,

On 2026-01-02 20:36:14, you wrote to me:

New node in net 221:
Pvt,40,ParaSite_BBS,Kotka,Kimmo_Viitanen,-Unpublished-,300,IBN
There is nothing to test...

Network 221 segment updated, but as you know in R20 you have to
wait a week...

I don't, but there are no daily updates in R20?

Yep. As you can see, the updates get into the Z2DAILY's only once in a week:

=== Cut ===
grep "Host,221,Finland" Z2DAILY.3* Z1DAILY.337:Host,221,Finland_(331),Ylojarvi,Tommi_Koivula,-U

...

Z1DAILY.365:Host,221,Finland_(359),Ylojarvi,Tommi_Koivula,-U
=== Cut ===

I see...

Have you discussed this with your RC ?


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hi All,

On 2026-01-02 13:16:39, I wrote to you:

New node in net 322: ,320,Lost_Crypt_BBS,Worcester_MA,Rick_Svyzek,-Unpublished-,300,CM,INA :bbs.lost
crypt.com,IBN Connect with BinkIT/2.41,JSBinkP/4,sbbs3.20d/Win32
But:
address: 1:320/9999@fidonet
No such AKA.

This is not fixed yet.

New node in net 221: Pvt,40,ParaSite_BBS,Kotka,Kimmo_Viitanen,-Unpublished-,300,IBN
There is nothing to test...

This one changed this week to:

,40,ParaSite_BBS,Kotka,Kimmo_Viitanen,-Unpublished-,300,CM,XA,INA:bbs.parasite.fi,IBN,ITN:2323

Connect OK with: BBBS/Li6 v4.10 Toy-7
On the ITN port I get a login prompt for a BBS immediately, and don't see an emsi string, so that might not be correct.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hi All,

In Region 17, nets 105 and 134 were removed. Probably a mistake, because most node in net 105 and some in 134 are connectable.

New node in net 333: ,802,WebPoint_VeleNo_BBs,Verona,Thomas_Bampi,-Unpublished-,300,CM,XA,MO,INA:webpoint.velenobbs.net
With only an INA, this is a broken entry. And there are no connects on the binkp and telnet ports.

There is a new R42C: Region,42,Czech_Republic_and_Slovakia,CZ_SK,Karel_Kral,-Unpublished-,300,XW,MO,CM,IBN,INA:f39.n423.z2.binkp.net,PING
Connect OK with: binkd/1.1a-115/Linux

Changes in R42 net 421:
Node 79, no longer has the Hub, flag.
Nodes 79 and 790 had the (redundant) ,U,NC flags removed
Nodes 7901 and 7902 were removed.

Node 3:633/408 was marked Down.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

09 Jan 26 12:31, Wilfred van Velzen wrote to All:

New node in net 221:
Pvt,40,ParaSite_BBS,Kotka,Kimmo_Viitanen,-Unpublished-,300,IBN
There is nothing to test...

This one changed this week to:

,40,ParaSite_BBS,Kotka,Kimmo_Viitanen,-Unpublished-,300,CM,XA,INA:bbs. parasite.fi,IBN,ITN:2323

Connect OK with: BBBS/Li6 v4.10 Toy-7
On the ITN port I get a login prompt for a BBS immediately, and don't
see an emsi string, so that might not be correct.

=== Cut ===
XEN Mailing ParaSite BBS (2:221/40)
XEN Assuming ID 2:221/360@fidonet
XEN Dialling bbs.parasite.fi (t2323,cm)
XEN Connected at 57600 bps /ARQ/TEL TO 135.181.205.36
XEN Called: [c[0!
XEN They're awake
XEN EMSI Transmit
XEN EMSI SEND: Successful
XEN EMSI Receive
XEN Address: 2:221/40
XEN Link codes: 8N1,RH1
XEN Compatibility: HYD,ARC,XMA
XEN Mailer: BBBS/Li6 4.10 Toy-7/#656 (110)
XEN Name: ParaSite BBS
XEN City: Kotka Finland
XEN Sysop: Kimmo Viitanen
XEN Speed: 300
XEN Flags: IBN
XEN EMSI RECV: Successful
XEN Hydra mailsession
XEN HYDRA: Other's HydraRev=01 Dec 1992
XEN HYDRA: Other's App.Info 'BBBS/Li6 4.10 Toy-7'
XEN HYDRA: Using link options 'ASC,UUE,C32,DEV'
XEN HYDRA: Window tx=16384 rx=16384
XEN HSEND: End of batch
XEN HRECV: End of batch
XEN HYDRA: Completed
XEN Nothing to send to 2:221/40@fidonet
XEN HSEND: End of batch
XEN HRECV: End of batch
XEN HYDRA: Completed
XEN End of mail session
XEN Connection for 0:07 min.
XEN Exit requested from keyboard
XEN Xenia Mailer 1.98.06+ OS/2 : end (10)
=== Cut ===

'Tommi

--- FastEcho/2 1.46.1 Revival
* Origin: ==========================>>> (2:221/1.254)

Hi Tommi,

On 2026-01-09 19:31:59, you wrote to me:

,40,ParaSite_BBS,Kotka,Kimmo_Viitanen,-Unpublished-,300,CM,XA,INA:bbs
.
parasite.fi,IBN,ITN:2323

Connect OK with: BBBS/Li6 v4.10 Toy-7
On the ITN port I get a login prompt for a BBS immediately, and don't
see an emsi string, so that might not be correct.

=== Cut ===
XEN Mailing ParaSite BBS (2:221/40)
XEN Assuming ID 2:221/360@fidonet
XEN Dialling bbs.parasite.fi (t2323,cm)
XEN Connected at 57600 bps /ARQ/TEL TO 135.181.205.36
XEN Called: [c[0!
XEN They're awake
XEN EMSI Transmit
XEN EMSI SEND: Successful
XEN EMSI Receive
XEN Address: 2:221/40
XEN Link codes: 8N1,RH1
XEN Compatibility: HYD,ARC,XMA
XEN Mailer: BBBS/Li6 4.10 Toy-7/#656 (110)
XEN Name: ParaSite BBS
XEN City: Kotka Finland
XEN Sysop: Kimmo Viitanen
XEN Speed: 300
XEN Flags: IBN
XEN EMSI RECV: Successful
XEN Hydra mailsession
XEN HYDRA: Other's HydraRev=01 Dec 1992
XEN HYDRA: Other's App.Info 'BBBS/Li6 4.10 Toy-7'
XEN HYDRA: Using link options 'ASC,UUE,C32,DEV'
XEN HYDRA: Window tx=16384 rx=16384
XEN HSEND: End of batch
XEN HRECV: End of batch
XEN HYDRA: Completed
XEN Nothing to send to 2:221/40@fidonet
XEN HSEND: End of batch
XEN HRECV: End of batch
XEN HYDRA: Completed
XEN End of mail session
XEN Connection for 0:07 min.
XEN Exit requested from keyboard
XEN Xenia Mailer 1.98.06+ OS/2 : end (10)
=== Cut ===

Thanks for testing!


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hi All,

New node in net 214: Pvt,44,W6RAY_AMPRNET_Packet-FTN_Gateway,Wilsonia_CA,Ray_Quinn,-Unpublished-,300,MO,IBN
MO and IBN flag should be removed, because they serve no purpose for a Pvt node.

Net 105 and 134 are back in R17.

Net 105 could use a few updates:

1:105/0 hub.awesomenet.us:24556 66.94.120.186 Ok.
1:105/1 hub.awesomenet.us:24556 66.94.120.186 Ok.
1:105/7 digdist.synchro.net:24554 50.46.162.90 Ok.
1:105/10 bbs.abon.us:24554 66.94.120.186 Ok.
1:105/11 bbs.wh2bbs.us:24555 66.94.120.186 Ok.
1:105/15 angstridden.net 198.199.100.20 Ok.
1:105/44 x-bit.org:24555 50.109.246.46 Ok.
1:105/45 bbs.4d2.org:24554 45.43.14.195 Ok.
1:105/46 x-bit.org:24550 50.109.246.46 Ok.
1:105/81 hub.awesomenet.us:24556 66.94.120.186 Ok.
1:105/85 os2.abon.us:24557 76.144.42.114 Error: Connection timed out
1:105/420 20ForBeers.com:24554 73.180.14.18 Ok.
1:105/500 fqbbs.synchro.net:24554 76.115.96.245 Ok.
1:105/1000 acmebbs.ddns.net - Error: Cannot getaddrinfo - Name or service not known

Net 134 is in a terrible state:

1:134/0 nc.fido134.net:24554 198.48.156.154 Error: Connection timed out 1:134/0 nc.fido134.net:24554 2600:3c04:e002:3101:f1d0:1:134:0 Error: Connection timed out
1:134/100 echohub.fido134.net:24554 178.128.187.153 Error: Connection timed out
1:134/100 echohub.fido134.net:24554 2600:3c04:e002:3101:f1d0:1:134:100 Error: Connection timed out
1:134/101 binkp.undermine.ca:24554 104.246.233.149 Ok.
1:134/101 binkp.undermine.ca:24554 2600:3c04:e002:3101:f1d0:1:134:0 Error: Connection timed out
1:134/102 shellshockbbs.ddns.net - Error: Cannot getaddrinfo - Name or service not known
1:134/103 bbs.technocentrist.com:24554 172.105.22.6 Error: Connection refused
1:134/301 i2ibbs.ddns.net - Error: Cannot getaddrinfo - Name or service not known
1:134/302 bbs.epochbbs.com:24554 172.105.106.228 Error: Connection timed out
1:134/302 bbs.epochbbs.com:24554 2a06:a004:4020:beef:f1d0:1:134:302 Error: Connection timed out
1:134/303 bbs.canerduh.com:24554 24.64.95.197 Ok.
1:134/303 bbs.canerduh.com:24554 2604:3d09:227f:eb7c:19:a08b:78ab:5e16 Ok.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hi All,

On 2026-01-09 13:09:03, I wrote to you:

New node in net 333: ,802,WebPoint_VeleNo_BBs,Verona,Thomas_Bampi,-Unpublished-,300,CM,XA, MO,INA:webpoint.velenobbs.net
With only an INA, this is a broken entry. And there are no connects
on the binkp and telnet ports.

No change...

There is a bbs website (binkterm-php) though, when you put the hostname in your browser...

Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hi All,

Node 5 in net 6035 is back: ,5,f5.n6035.z2.binkp.net,Zheleznogorsk,Vitaliy_Poluhin,-Unpublished-,300,MO,CM,IBN,INA:f5.n6035.z2.binkp.net
Connect OK with: binkd/1.1a-49/Win32

Node 408 in net 633 is no longer down:

There is a binkp connection, but it ends with an error?

+ 30 Jan 12:30:47 [23012] call to 3:633/408@fidonet
30 Jan 12:30:47 [23012] trying newt.aliens.ph [157.245.58.138]...
30 Jan 12:30:47 [23012] connected
+ 30 Jan 12:30:47 [23012] outgoing session with newt.aliens.ph:24554 [157.245.58.138]
- 30 Jan 12:30:47 [23012] OPT CRAM-MD5-2ccacd75f8585863f6c5afb07ee31c18
+ 30 Jan 12:30:47 [23012] Remote requests MD mode
- 30 Jan 12:30:47 [23012] WWIVVER 5.9.03749 (Feb 22 2025, 12:04:55)
- 30 Jan 12:30:47 [23012] SYS aliens' abode
- 30 Jan 12:30:47 [23012] ZYZ Xenos
- 30 Jan 12:30:47 [23012] VER networkb/5.9.03749 binkp/1.0
- 30 Jan 12:30:47 [23012] LOC Unknown
- 30 Jan 12:30:47 [23012] OPT CRC
- 30 Jan 12:30:47 [23012] WWIV @61.wwivnet
- 30 Jan 12:30:47 [23012] WWIV @6.rushnet
+ 30 Jan 12:30:47 [23012] addr: 20000:20000/61@wwivnet (n/a or busy)
+ 30 Jan 12:30:47 [23012] addr: 20000:20000/6@rushnet (n/a or busy)
+ 30 Jan 12:30:47 [23012] addr: 3:633/408@fidonet
? 30 Jan 12:30:47 [23012] rerror: Error (NETWORKB-0004): Unable to find common nodes in: 2:280/464@fidonet 39:39/0@amiganet
+ 30 Jan 12:30:47 [23012] done (to 3:633/408@fidonet, failed, S/R: 0/0 (0/0 bytes))

Another broken binkp implementation?


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hello Wilfred,

On Friday January 30 2026 12:46, you wrote to All:

Node 5 in net 6035 is back: ,5,f5.n6035.z2.binkp.net,Zheleznogorsk,Vitaliy_Poluhin,-Unpublished-,3 00,MO,CM,IBN,INA:f5.n6035.z2.binkp.net Connect OK with: binkd/1.1a-49/Win32

Check.

Node 408 in net 633 is no longer down:

There is a binkp connection, but it ends with an error?

[..]

12:30:47 [23012] addr: 20000:20000/61@wwivnet (n/a or busy) + 30 Jan 12:30:47 [23012] addr: 20000:20000/6@rushnet (n/a or busy) + 30 Jan 12:30:47 [23012] addr: 3:633/408@fidonet ? 30 Jan 12:30:47 [23012]
rerror: Error (NETWORKB-0004): Unable to find common nodes in: 2:280/464@fidonet 39:39/0@amiganet + 30 Jan 12:30:47 [23012] done (to 3:633/408@fidonet, failed, S/R: 0/0 (0/0 bytes))

Another broken binkp implementation?

Same poblem here.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)

Hi Wilfred!

Friday January 30 2026 12:46, you wrote to All:

Node 408 in net 633 is no longer down:

There is a binkp connection, but it ends with an error?

+ 30 Jan 12:30:47 [23012] call to 3:633/408@fidonet

[...skipped...]

rerror: Error (NETWORKB-0004): Unable to find common nodes in: 2:280/464@fidonet
39:39/0@amiganet + 30 Jan 12:30:47 [23012] done (to 3:633/408@fidonet, failed, S/R: 0/0 (0/0 bytes))

Another broken binkp implementation?

Confirming.

[18:47:45 brorabbit devel]$ callip -c ~/etc/callip.conf -b -f 3:633/408
You have actual version.
Parsing nodelist file /home/fido/nodelist/nodelist.367
Nodelist for Friday, January 30, 2026 -- Day number 030 parsed, 947 IP-nodes processed (0.052 sec)
Calling '3:633/408'. Call time: '0000-2400' UTC.
Now is: 1548 UTC.
newt.aliens.ph, 24554
Calling 3:633/408 (157.245.58.138:24554)
OPT CRAM-MD5-2d0a17d41c8cafb03ddaed44c8e4f244
WWIVVER 5.9.03749 (Feb 22 2025, 12:04:55)
SYS aliens' abode
ZYZ Xenos
VER networkb/5.9.03749 binkp/1.0
LOC Unknown
OPT CRC
WWIV @61.wwivnet
WWIV @6.rushnet
address: 20000:20000/61@wwivnet
address: 20000:20000/6@rushnet
address: 3:633/408@fidonet
Got binkp error: Error (NETWORKB-0004): Unable to find common nodes in: 2:460/58.1@fidonet.

Does not remove leading space before the address.

Have a nice night.
Stas Mishchenkov.

--- Have You daily sexual life? Hide it proper from Your wife! ;)
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi All,

On 2026-01-30 12:46:17, I wrote to you:

Node 408 in net 633 is no longer down:

There is a binkp connection, but it ends with an error?

+ 30 Jan 12:30:47 [23012] call to 3:633/408@fidonet
30 Jan 12:30:47 [23012] trying newt.aliens.ph [157.245.58.138]...
30 Jan 12:30:47 [23012] connected

...

? 30 Jan 12:30:47 [23012] rerror: Error (NETWORKB-0004): Unable to
find common nodes in: 2:280/464@fidonet

No change here...


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hi All,

New node in net 226: ,20,Silfen_Path_BBS,Columbus_OH,Petar_Smilajkov,-Unpublished-,300,INA:bbs.silfenpath.com,IBN
Connect OK with: Mystic/1.12A49

XA flags are now fixed to XW for node 1:153/149, and removed for node 1:153/150.

New node in net 250: ,18,Frontier_BBS,Redhill_Surrey,Dave_Parker,-Unpublished-,300,CM,XX,INA:frontierbbs.co.uk,IBN
Connect OK with: BinkIT/2.42,JSBinkP/4,sbbs3.21b/Linux
The XX flag is wrong for a Synchronet system with freqit. It doesn't support 'Update requests'. So if freqit is configured it should be XW, otherwise it should be removed.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hi All,

On 2026-02-06 12:38:52, I wrote to you:

New node in net 250: ,18,Frontier_BBS,Redhill_Surrey,Dave_Parker,-Unpublished-,300,CM,XX,I NA:frontierbbs.co.uk,IBN
Connect OK with: BinkIT/2.42,JSBinkP/4,sbbs3.21b/Linux

The XX flag is wrong for a Synchronet system with freqit. It doesn't support 'Update requests'. So if freqit is configured it should be
XW, otherwise it should be removed.

The XX flag was removed for this node in this weeks nodelist...


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hi All,

There are no other noteworthy changes in this weeks nodelist...

Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hi All,

The net 450 host was changed to: Host,450,Minsk_Net,Mogilev_Belarus,Alexey_Korotkov,-Unpublished-,300,CM,IBN,INA:82.209.239.18,INA:unnamed.by
This is a new AKA for the Region system.
Connect OK with: binkd/1.1a-115/Linux
Nodes 102 and 1024 were removed and only 3 Pvt nodes remain in this net.

Effectively only 2 none-Pvt nodes remain in R45, they are both connectable with binkp.

In net 5053, Hub 58 was changed to:
;E HOLD HUB,58,AroundFamilyNode,Saratov_Russia,Alexander_Kruglikov,-Unpublished-,300,CM,IBN,INA:fido.kruglikov.info,BEER:lager,PING,TRACE,U,ENC,NEC
;E -- Invalid keyword -- 'HOLD HUB'

Also node 400 was put on Hold. There is indeed a Connection refused on the binkp port for the given host name.

New node in net 712: ,730,bbs.intaa.net,Tokyo_Japan,Yoshito_Uchiyama,-Unpublished-,300,CM,XX,INA:bbs.intaa.net,IBN
Connection refused on IPv6, Connect OK on IPv4 with: binkd/1.1a-115/386BSD


In the Z2PNT list the R45 (Belarus) segment was removed. It was last updated on 2020-01-29, and there were only 2 nodes left in this segment.

Now all Region segments in the Z2PNT list are recently updated (oldest one is from 2026-01-19). That doesn't mean the contents of the segments is accurate, but at least there is an active RPK (system).


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hello Wilfred,

On Friday February 20 2026 12:34, you wrote to All:

In net 5053, Hub 58 was changed to:
;E HOLD HUB,58,AroundFamilyNode,Saratov_Russia,Alexander_Kruglikov,-Unpublishe d-,300,CM,IBN,INA:fido.kruglikov.info,BEER:lager,PING,TRACE,U,ENC,NEC
;E -- Invalid keyword -- 'HOLD HUB'

But it is still connectable.

Also node 400 was put on Hold. There is indeed a Connection refused on
the binkp port for the given host name.

Indeed, no connection.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)

Hi Michiel,

On 2026-02-22 16:36:39, you wrote to me:

In net 5053, Hub 58 was changed to:
;E HOLD
HUB,58,AroundFamilyNode,Saratov_Russia,Alexander_Kruglikov,-Unpublishe
d-,300,CM,IBN,INA:fido.kruglikov.info,BEER:lager,PING,TRACE,U,ENC,NEC
;E -- Invalid keyword -- 'HOLD HUB'

MvdV> But it is still connectable.

Indeed connect with: binkd/1.1a-115/Linux

You will have to ask the Host about the why! ;-)


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

�ਢ��, Wilfred!

22 䥢 26 17:39, Wilfred van Velzen ��ᠫ(�) � Michiel van der Vlist:

;E HOLD
HUB,58,AroundFamilyNode,Saratov_Russia,Alexander_Kruglikov,-Unpu
blished-,300,CM,IBN,INA:fido.kruglikov.info,BEER:lager,PING,TRACE,U,
ENC,NEC ;E -- Invalid keyword -- 'HOLD HUB'

MvdV>> But it is still connectable.

Indeed connect with: binkd/1.1a-115/Linux
You will have to ask the Host about the why! ;-)

Because Hold is not Down =)

� ������訬� ��������ﬨ, Alexander.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: Insufficient Disk Space,please delete Windows. Please! (2:5053/58)

Hello Alexander,

On Wednesday February 25 2026 21:50, you wrote to Wilfred van Velzen:

MvdV>>> But it is still connectable.

Indeed connect with: binkd/1.1a-115/Linux
You will have to ask the Host about the why! ;-)

Because Hold is not Down =)

But now it is:

;E DOWN,Hub,58,AroundFamilyNode,Saratov_Russia,Alexander_Kruglikov,-Unpublish ;E -- Invalid Node number -- 'Hub'


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)

�ਢ��, Michiel!

*** �⢥� �� ᮮ�饭�� �� CarbonArea (���� ��� ����).

26 䥢 26 09:39, Michiel van der Vlist ��ᠫ(�) � Alexander Kruglikov:

Indeed connect with: binkd/1.1a-115/Linux
You will have to ask the Host about the why! ;-)

Because Hold is not Down =)

MvdV> But now it is:
MvdV> ;E
MvdV> DOWN,Hub,58,AroundFamilyNode,Saratov_Russia,Alexander_Kruglikov,-Un
MvdV> publish ;E -- Invalid Node number -- 'Hub'

I told my NC that it doesn't work that way, but he has his own vision =(
I'll try to say it again =)

� ������訬� ��������ﬨ, Alexander.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: Windows NT - ����⪠ �� ��⪠... (2:5053/58)

Hello Alexander,

On Thursday February 26 2026 13:35, you wrote to me:

Indeed connect with: binkd/1.1a-115/Linux
You will have to ask the Host about the why! ;-)

Because Hold is not Down =)

MvdV>> But now it is:
MvdV>> ;E DOWN,Hub,58,AroundFamilyNode,Saratov_Russia,Alexander_Kruglikov
MvdV>> ,-Un publish ;E -- Invalid Node number -- 'Hub'

I told my NC that it doesn't work that way, but he has his own vision
=( I'll try to say it again =)

What is the plan? Both your nodes are marked down. That seems to be the idea anyway. But you are still here and 5053/58 is still up and running.

So what IS the plan?


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)

�ਢ��, Michiel!

*** �⢥� �� ᮮ�饭�� �� CarbonArea (���� ��� ����).

26 䥢 26 12:59, Michiel van der Vlist ��ᠫ(�) � Alexander Kruglikov:

MvdV> What is the plan? Both your nodes are marked down. That seems to be
MvdV> the idea anyway. But you are still here and 5053/58 is still up and
MvdV> running. So what IS the plan?

Transfer of some services for some R50 echos to another node, or a point, and the subsequent complete shutdown of 2:5053/58. "Hold" is now due to the fact, that some particularly boring nodes in R50 are annoyed, that other nodes provide 2:5053/58 communication, which is missing from the nodelist.

I asked to immediately remove 2:5053/400 from the nodelist, but my NC decided that it should go through Hold and Down, don't ask why, I don't know myself.

� ������訬� ��������ﬨ, Alexander.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: IBM - �� ���� "�����" (2:5053/58)

Hello Alexander,

On Thursday February 26 2026 23:16, you wrote to me:

MvdV>> So what IS the plan?

Transfer of some services for some R50 echos to another node, or a
point, and the subsequent complete shutdown of 2:5053/58. "Hold" is
now due to the fact, that some particularly boring nodes in R50 are annoyed, that other nodes provide 2:5053/58 communication, which is missing from the nodelist.

I asked to immediately remove 2:5053/400 from the nodelist, but my NC decided that it should go through Hold and Down, don't ask why, I
don't know myself.

So 5053/58 and 5053/400 will eventually be totally removed from the nodelist?

You will be leaving us? :-(


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)

�ਢ��, Michiel!

*** �⢥� �� ᮮ�饭�� �� CarbonArea (���� ��� ����).

27 䥢 26 09:56, Michiel van der Vlist ��ᠫ(�) � Alexander Kruglikov:

MvdV> So 5053/58 and 5053/400 will eventually be totally removed from the
MvdV> nodelist?
MvdV> You will be leaving us? :-(

To my great regret yes(

� ������訬� ��������ﬨ, Alexander.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: It is not a programm, it requires MS Windows... (2:5053/58)

Hi All,

On 2026-02-20 12:34:26, I wrote to you:

In net 5053, Hub 58 was changed to:
;E HOLD HUB,58,AroundFamilyNode,Saratov_Russia,Alexander_Kruglikov,-Unpublished-,300,C
M,IBN,INA:fido.kruglikov.info,BEER:lager,PING,TRACE,U,ENC,NEC ;E -- Invalid
keyword -- 'HOLD HUB'

It is now:

;E DOWN,Hub,58,AroundFamilyNode,Saratov_Russia,Alexander_Kruglikov,-Unpublished-,300,CM,IBN,INA:fido.kruglikov.info,BEER:lager,PING,TRACE,U,ENC,NEC
;E -- Invalid Node number -- 'Hub'

So still not correct.

New node in net 712: ,730,bbs.intaa.net,Tokyo_Japan,Yoshito_Uchiyama,-Unpublished-,300,CM, XX,INA:bbs.intaa.net,IBN
Connection refused on IPv6, Connect OK on IPv4 with: binkd/1.1a-115/386BSD

IPv6 is now working.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hi All,

Node 1:220/10 was removed.

In net 275 the following node got an INA update: ,89,Diamond_Mine_Online_BBS,Fredericksburg_VA,Dave_Perrussel,-Unpublished-,300,CM,INA:sbbs.dmine.net,ITN,IBN
Connection timed out

RIN 1:19/50 was removed. I get a connect OK with: binkd/1.1a-113/OS2 ?

Node 2:5022/145 was put on Hold. I get a connect OK with: binkd/1.1a-49/Win32 ?

Hold Node 2:5022/43 was removed.

Node 2:5053/400 was changed from Hold to Down.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hello Alexander,

On Friday February 27 2026 13:47, you wrote to me:

MvdV>> So 5053/58 and 5053/400 will eventually be totally removed from
MvdV>> the nodelist? You will be leaving us? :-(

To my great regret yes(

Very sad. :-(

There is absolutely no way to resolve the conflict?


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)

�ਢ��, Michiel!

*** �⢥� �� ᮮ�饭�� �� CarbonArea (���� ��� ����).

27 䥢 26 18:20, Michiel van der Vlist ��ᠫ(�) � Alexander Kruglikov:

MvdV>>> So 5053/58 and 5053/400 will eventually be totally removed
MvdV>>> from the nodelist? You will be leaving us? :-(

To my great regret yes(

MvdV> Very sad. :-(
MvdV> There is absolutely no way to resolve the conflict?

This is not a conflict, but rather a lack of time and desire to resolve possible conflicts =)

� ������訬� ��������ﬨ, Alexander.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: Windows NT: Only 16 megs needed to play Minesweeper! (2:5053/58)

Hi All,

On 2026-02-27 12:14:33, I wrote to you:

It is now:

;E DOWN,Hub,58,AroundFamilyNode,Saratov_Russia,Alexander_Kruglikov,-Unpublishe
d-,300,CM,IBN,INA:fido.kruglikov.info,BEER:lager,PING,TRACE,U,ENC,NEC ;E --
Invalid Node number -- 'Hub'

So still not correct.

This error was resolved in Z2DAILY.059 ...


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hello Alexander,

On Monday March 02 2026 13:05, you wrote to me:

MvdV>>>> So 5053/58 and 5053/400 will eventually be totally removed
MvdV>>>> from the nodelist? You will be leaving us? :-(

To my great regret yes(

MvdV>> Very sad. :-(
MvdV>> There is absolutely no way to resolve the conflict?

This is not a conflict, but rather a lack of time and desire to
resolve possible conflicts =)

Too bad.

5053/58 is now also listed as Down. But I can still connect. I suppose it will actually go down real soon now? So I can remove you from the IPv6 list?


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)

�ਢ��, Michiel!

*** �⢥� �� ᮮ�饭�� �� CarbonArea (���� ��� ����).

02 ��� 26 13:24, Michiel van der Vlist ��ᠫ(�) � Alexander Kruglikov:

MvdV>>> Very sad. :-( There is absolutely no way to resolve the conflict?

This is not a conflict, but rather a lack of time and desire to
resolve possible conflicts =)

MvdV> Too bad.

Me too, but it's going away.

MvdV> 5053/58 is now also listed as Down. But I can still connect. I suppose
MvdV> it will actually go down real soon now?

Yes, in about two weeks. I am currently reviewing the publication of the rules in the moderated echo and some other mailing lists from the point address.

MvdV> So I can remove you from the IPv6 list?

Yes, after two or three weeks, the node will stop responding. /400 is already off.

� ������訬� ��������ﬨ, Alexander.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: ASCII (pronounce: ass-key) (2:5053/58)

Hi Alexander,

On 2026-03-02 17:13:35, you wrote to Michiel van der Vlist:

MvdV>> So I can remove you from the IPv6 list?

Yes, after two or three weeks, the node will stop responding. /400 is already
off.

And node 400 is already removed from the daily nodelists today...

Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hi Wilfred,

On 2026-02-27 12:31:00, I wrote to All:

In net 275 the following node got an INA update: ,89,Diamond_Mine_Online_BBS,Fredericksburg_VA,Dave_Perrussel,-Unpubli shed-,300,CM,INA:sbbs.dmine.net,ITN,IBN Connection timed out

No improvement here.

Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hi All,

New node in net 154: ,130,Amnesia_BBS,Minneapolis_MN,James_Cunningham,-Unpublished-,300,CM,INA:amnesiabbs.duckdns.org,IBN
Connect OK with: BinkIT/2.42,JSBinkP/4,sbbs3.21b/Linux

New node in net 2320: ,106,Captest,Frankfort_KY,Mike_Powell,-Unpublished-,300,CM,MO,XA,INA:capitolcityonline.net,IBN:24556
Connect OK with: binkd/1.1a-115/Linux

New RIN in R19: ,44,The_Dark_Side,Conroe_TX,Gabe_Harriman,-Unpublished-,300,XA,INA:bbs.mynameisgabe.com,IBN
Connect OK with Mystic/1.12A49

Node 414 in net 633 became Pvt

New node in net 633: ,416,v1ntagebbs,Gippsland_Vic,Tom_Aberdeen,-Unpublished-,300,CM,IBN:v1ntagebbs.net
Connect OK with: BinkIT/2.42,JSBinkP/4,sbbs3.21d/Linux


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hi All,

New node in net 218: ,630,The_Rusty_Connection,Fremont_CA,Kimball_Anderson,-Unpublished-,300,CM,XX,INA:bbs.kortyard.net,IBN
Connect with: binkd/1.1a-115/FreeBSD binkp/1.1

But there seems to be a configuration issue:

address: 1:218/630@fidonet
Error: No AKAs in common domains or all AKAs are busy.

Or maybe a hanging control file?


Down nodes 2:5053/49 and 2:5053/58 are removed. I still get a connect OK at 2:5053/58 ...?


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

�ਢ��, Wilfred!

13 ��� 26 13:00, Wilfred van Velzen ��ᠫ(�) � All:

Down nodes 2:5053/49 and 2:5053/58 are removed. I still get a connect
OK at 2:5053/58 ...?

Some leisurely sysops are in no hurry to change subscriptions and netmail routing. And our N5053C is apparently in a hurry to kick me out of the nodelist =)))))) (or this process is automated).

I think that in three or four days, 5053/58 will stop responding.

� ������訬� ��������ﬨ, Alexander.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: Kingdom Come - �� ��� �� Condom Kings ! (2:5053/58)

Hi Alexander!

Friday March 13 2026 16:48, you wrote to Wilfred van Velzen:

Down nodes 2:5053/49 and 2:5053/58 are removed. I still get a
connect
OK at 2:5053/58 ...?

Some leisurely sysops are in no hurry to change subscriptions and netmail routing. And our N5053C is apparently in a hurry to kick me out of the nodelist =)))))) (or this process is automated).

I think that in three or four days, 5053/58 will stop responding.

And I'm one of those lazy asses? ;)

Have a nice night.
Stas Mishchenkov.

--- Have You daily sexual life? Hide it proper from Your wife! ;)
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Wilfred van Velzen wrote to All <=-

address: 1:218/630@fidonet
Error: No AKAs in common domains or all AKAs are busy.

Or maybe a hanging control file?

Worked here... I'm their uplink.

C:\sbbs\nodelist>binkpoll 1:218/630

JSexec v3.21a-Win32 master/4fa2ba380 - Execute Synchronet JavaScript
Module
Compiled Dec 13 2025 22:00 with MSC 1944

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.42 invoked with options: -l 1:218/630
Attempting poll for node 1:218/630@fidonet
JSBinkP/4 callout to 1:218/630@fidonet started
Connecting to 1:218/630@fidonet at bbs.kortyard.net:24554
Peer version: binkd/1.1a-115/FreeBSD
Will encrypt session.
Authentication successful: secure
c:\sbbs\exec\binkit.js executed in 2.24 seconds



--- MultiMail/Win v0.52
* Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)

Hi Kurt,

On 2026-03-14 08:32:34, you wrote to me:

address: 1:218/630@fidonet
Error: No AKAs in common domains or all AKAs are busy.

Or maybe a hanging control file?

Worked here...

Same here now. The problem cleared up about 9 hours after my first test (my binkd kept trying every hour)...

That happens with these kind of errors, if binkd or the system is reset...


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hi All,

On 2026-03-13 13:00:56, I wrote to you:

New node in net 218: ,630,The_Rusty_Connection,Fremont_CA,Kimball_Anderson,-Unpublished-,3 00,CM,XX,INA:bbs.kortyard.net,IBN
Connect with: binkd/1.1a-115/FreeBSD binkp/1.1

But there seems to be a configuration issue:

address: 1:218/630@fidonet
Error: No AKAs in common domains or all AKAs are busy.

Or maybe a hanging control file?

I now get:

Calling '1:218/630'. Call time: '0000-2400' UTC.
bbs.kortyard.net, 24554
Calling 1:218/630 (216.218.216.244:24554)
error (Connection refused)


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hi All,

New node in net 266: ,325,Jersey_Jam,Budd_Lake_NJ,Brian_Piper,-Unpublished-,300,CM,INA:jerseyjam.com,IBN
Connect OK with: BinkIT/2.42,JSBinkP/4,sbbs3.21e/Win32

The entry for the RC50 system and aka's changed host name from fido.hubahuba.su to fido.huba715.ru
They (still) resolve to the same IPv4 and IPv6 addresses and connect OK.

The entry for the RC80 system and aka's changed IBN: from 35.192.92.175 to fido.rbt.net.br
The host name resolves to the same IPv4 and connects OK.

New nodes in net 801: Pvt,199,Net_PE_BBS,Recife_PE,Ioram_Sette,-Unpublished-,300 Hold,204,Micronet_BBS,Florianopolis_SC,Luiz_Pacheco,-Unpublished-,300,CM,IBN:micronet.ddns.net:2323
Hold,205,Telesc_BBS,Florianopolis_SC,Mauro_Benedetta,-Unpublished-,300,CM,IBN:bbs.telesc.net.br

Testing 204 gives a 'no route to host'.
205 Gives a connect OK with: BinkIT/2.42,JSBinkP/4,sbbs3.21b/Linux on both IPv4 and IPv6


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hello Wilfred,


On Friday March 20 2026 12:17, you wrote to All:

Hold,204,Micronet_BBS,Florianopolis_SC,Luiz_Pacheco,-Unpublished-,300, CM,IBN:micronet.ddns.net:2323 Hold,205,Telesc_BBS,Florianopolis_SC,Mau ro_Benedetta,-Unpublished-,300,CM,IBN:bbs.telesc.net.br

Testing 204 gives a 'no route to host'.
205 Gives a connect OK with: BinkIT/2.42,JSBinkP/4,sbbs3.21b/Linux on
both IPv4 and IPv6

I already entered 4:801/205 in the IPv6 list om 14 March. But in the binkp handshake he calls himself Mauro Paes Correa, not Mauro Benedetta.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)

Hi Wilfred!

Friday March 20 2026 11:57, you wrote to All:

New node in net 218:
,630,The_Rusty_Connection,Fremont_CA,Kimball_Anderson,-Unpublished-,
3
00,CM,XX,INA:bbs.kortyard.net,IBN
Connect with: binkd/1.1a-115/FreeBSD binkp/1.1

But there seems to be a configuration issue:

address: 1:218/630@fidonet
Error: No AKAs in common domains or all AKAs are busy.

Or maybe a hanging control file?

I now get:

Calling '1:218/630'. Call time: '0000-2400' UTC.
bbs.kortyard.net, 24554
Calling 1:218/630 (216.218.216.244:24554)
error (Connection refused)

[18:03:35 brorabbit logs]$ callip -c ~/etc/callip.conf -s -f 1:218/630
You have actual version.
Parsing nodelist file /home/fido/nodelist/nodelist.367
Nodelist for Friday, March 20, 2026 -- Day number 079 parsed, 948 IP-nodes processed (0.052 sec)
Calling '1:218/630'. Call time: '0000-2400' UTC.
Now is: 1503 UTC.
bbs.kortyard.net, 24554
Calling 1:218/630 (216.218.216.244:24554)
OPT CRAM-MD5-da80bdfb263e8cb59944261c1e4013ee
SYS The Rusty Connection
ZYZ Kimball Anderson
LOC Fremont, CA USA
NDL 115200,TCP,BINKP
TIME Fri, 20 Mar 2026 08:03:59 -0700
VER binkd/1.1a-115/FreeBSD binkp/1.1
address: 1:218/630@fidonet
TRF 0 0
OPT EXTCMD NR GZ BZ2
216.218.216.244 - Ok.
Session with 1:218/630 done.

Have a nice night.
Stas Mishchenkov.

--- Have You daily sexual life? Hide it proper from Your wife! ;)
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi Michiel!

Friday March 20 2026 13:29, you wrote to Wilfred van Velzen:

MvdV> I already entered 4:801/205 in the IPv6 list om 14 March. But in the
MvdV> binkp handshake he calls himself Mauro Paes Correa, not Mauro
MvdV> Benedetta.

Hm...

[18:04:00 brorabbit logs]$ callip -c ~/etc/callip.conf -s -f 4:801/205
You have actual version.
Parsing nodelist file /home/fido/nodelist/nodelist.367
Nodelist for Friday, March 20, 2026 -- Day number 079 parsed, 948 IP-nodes processed (0.053 sec)
Node 4:801/205 not found.

Have a nice night.
Stas Mishchenkov.

--- Have You daily sexual life? Hide it proper from Your wife! ;)
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi Stas.

20 Mar 26 18:06:56, you wrote to Michiel van der Vlist:

MvdV>> I already entered 4:801/205 in the IPv6 list om 14 March. But in
MvdV>> the binkp handshake he calls himself Mauro Paes Correa, not Mauro
MvdV>> Benedetta.

Hm...

[18:04:00 brorabbit logs]$ callip -c ~/etc/callip.conf -s -f 4:801/205
You have actual version.
Parsing nodelist file /home/fido/nodelist/nodelist.367
Nodelist for Friday, March 20, 2026 -- Day number 079 parsed, 948
IP-nodes processed (0.053 sec) Node 4:801/205 not found.

Parsing nodelist file ./nodelist.ndl
Nodelist for Friday, March 20, 2026 -- Day number 079 parsed, 948 IP-nodes processed (0.056 sec)
Node 4:801/205 not found.

Hold,205,Telesc_BBS,Florianopolis_SC,Mauro_Benedetta,-Unpublished-,300,CM,IBN:bbs.telesc.net.br

"Hold" -> "Not found" ?

'Tommi

---
* Origin: Point One (2:221/1.1)

Hi Stas,

On 2026-03-20 18:04:16, you wrote to me:

New node in net 218:
,630,The_Rusty_Connection,Fremont_CA,Kimball_Anderson,-Unpublished-
,300,CM,XX,INA:bbs.kortyard.net,IBN
Connect with: binkd/1.1a-115/FreeBSD binkp/1.1

But there seems to be a configuration issue:

address: 1:218/630@fidonet
Error: No AKAs in common domains or all AKAs are busy.

Or maybe a hanging control file?

I now get:

Calling '1:218/630'. Call time: '0000-2400' UTC.
bbs.kortyard.net, 24554
Calling 1:218/630 (216.218.216.244:24554)
error (Connection refused)

[18:03:35 brorabbit logs]$ callip -c ~/etc/callip.conf -s -f 1:218/630
You have actual version.
Parsing nodelist file /home/fido/nodelist/nodelist.367
Nodelist for Friday, March 20, 2026 -- Day number 079 parsed, 948 IP-nodes processed (0.052 sec) Calling '1:218/630'. Call time: '0000-2400' UTC. Now is:
1503 UTC. bbs.kortyard.net, 24554 Calling 1:218/630 (216.218.216.244:24554) OPT CRAM-MD5-da80bdfb263e8cb59944261c1e4013ee SYS The
Rusty Connection ZYZ Kimball Anderson LOC Fremont, CA USA NDL 115200,TCP,BINKP
TIME Fri, 20 Mar 2026 08:03:59 -0700
VER binkd/1.1a-115/FreeBSD binkp/1.1
address: 1:218/630@fidonet
TRF 0 0
OPT EXTCMD NR GZ BZ2
216.218.216.244 - Ok.
Session with 1:218/630 done.

# callipf -f 1:218/630
Parsing nodelist file /home/fido/zadaily/makenl/out/zadaily.079
Nodelist for Friday, March 20, 2026 -- Day number 079 parsed, 948 IP-nodes processed (0.013 sec)
Calling '1:218/630'. Call time: '0000-2400' UTC.
Now is: 1644 UTC.
bbs.kortyard.net, 24554
Calling 1:218/630 (216.218.216.244:24554)
error (Connection refused)

My IP seems to be blocked on his firewall. If I try it from another IP, I get the same result as you... Whatever...


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hi Stas,

On 2026-03-20 18:06:56, you wrote to Michiel van der Vlist:

MvdV>> I already entered 4:801/205 in the IPv6 list om 14 March. But in
MvdV>> the binkp handshake he calls himself Mauro Paes Correa, not Mauro
MvdV>> Benedetta.

Hm...

[18:04:00 brorabbit logs]$ callip -c ~/etc/callip.conf -s -f 4:801/205
You have actual version.
Parsing nodelist file /home/fido/nodelist/nodelist.367
Nodelist for Friday, March 20, 2026 -- Day number 079 parsed, 948 IP-nodes processed (0.053 sec) Node 4:801/205 not found.

You need to use '-i' because the node is Hold. ;-)


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hi Wilfred.

20 Mar 26 17:48, you wrote to Stas Mishchenkov:

Hm...

[18:04:00 brorabbit logs]$ callip -c ~/etc/callip.conf -s -f
4:801/205 You have actual version. Parsing nodelist file
/home/fido/nodelist/nodelist.367 Nodelist for Friday, March 20,
2026 -- Day number 079 parsed, 948 IP-nodes
processed (0.053 sec) Node 4:801/205 not found.

You need to use '-i' because the node is Hold. ;-)

Oh. ;-)

Nodelist for Friday, March 20, 2026 -- Day number 079 parsed, 992 IP-nodes processed (0.021 sec)
Calling '4:801/205'. Call time: '0000-2400' UTC.
Now is: 1703 UTC.
bbs.telesc.net.br, 24554
Calling 4:801/205 (2a0f:85c1:c30:1002:48:217:13:13:24554)
OPT CRAM-MD5-23be9f10d5d8e13a4cc4f8651d8f6628 CRYPT
SYS BBS TELESC.NET.BR
ZYZ Mauro Paes Correa
LOC Urussanga, Santa Catarina, BR
NDL 115200,TCP,BINKP
TIME Fri Mar 20 2026 14:03:49 GMT-0300
VER BinkIT/2.42,JSBinkP/4,sbbs3.21b/Linux binkp/1.1
address: 4:801/205@fidonet
2a0f:85c1:c30:1002:48:217:13:13 - Ok.
Session with 4:801/205 done.
Calling 4:801/205 (138.117.192.72:24554)
OPT CRAM-MD5-22944834d0cfc97213754d4c78b65c88 CRYPT
SYS BBS TELESC.NET.BR
ZYZ Mauro Paes Correa
LOC Urussanga, Santa Catarina, BR
NDL 115200,TCP,BINKP
TIME Fri Mar 20 2026 14:03:56 GMT-0300
VER BinkIT/2.42,JSBinkP/4,sbbs3.21b/Linux binkp/1.1
address: 4:801/205@fidonet
138.117.192.72 - Ok.
Session with 4:801/205 done.

'Tommi

--- GoldED+/LNX 1.1.5-b20260304
* Origin: nntps://news.fidonet.fi (2:221/360)

Wilfred van Velzen wrote to All <=-

I now get:

Calling '1:218/630'. Call time: '0000-2400' UTC.
bbs.kortyard.net, 24554
Calling 1:218/630 (216.218.216.244:24554)
error (Connection refused)

This is getting ridiculous. I'm his uplink and have polled just fine.
What's the issue here?



--- MultiMail/Win v0.52
* Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)

13 Mar 2026 13:00, you wrote to All:

address: 1:218/630@fidonet
Error: No AKAs in common domains or all AKAs are busy.

I can connect ok.

+ 20 Mar 20:17:58 [2928] done (to 1:218/630@fidonet, OK, S/R: 0/0 (0/0 bytes))

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234)

Hi Kurt,

On 2026-03-20 10:55:38, you wrote to me:

I now get:

Calling '1:218/630'. Call time: '0000-2400' UTC.
bbs.kortyard.net, 24554
Calling 1:218/630 (216.218.216.244:24554)
error (Connection refused)

This is getting ridiculous. I'm his uplink and have polled just fine. What's the issue here?

I suspect my IP is blocked on his firewall. I can also connect from a different IP adres...

Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hi Kurt,

On 2026-03-20 21:07:19, I wrote to you:

I now get:

Calling '1:218/630'. Call time: '0000-2400' UTC.
bbs.kortyard.net, 24554
Calling 1:218/630 (216.218.216.244:24554)
error (Connection refused)

This is getting ridiculous. I'm his uplink and have polled just fine.
What's the issue here?

I suspect my IP is blocked on his firewall. I can also connect from a different IP adres...

I still get the connection refused.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hi All,

On 2026-03-20 12:17:32, I wrote to you:

New nodes in net 801: Pvt,199,Net_PE_BBS,Recife_PE,Ioram_Sette,-Unpublished-,300 Hold,204,Micronet_BBS,Florianopolis_SC,Luiz_Pacheco,-Unpublished-,300,CM,IBN:m
icronet.ddns.net:2323 Hold,205,Telesc_BBS,Florianopolis_SC,Mauro_Benedetta,-Un
published-,300,CM,IBN:bbs.telesc.net.br

Testing 204 gives a 'no route to host'.
205 Gives a connect OK with: BinkIT/2.42,JSBinkP/4,sbbs3.21b/Linux on both
IPv4 and IPv6

No change...


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Hi All,

In net 341: Down,202,Vampire_BBS,Madrid,Antonio_Hernandez_Lopez,... node was removed.

Other than that, and the removal of the seasonal wishes from the prolog (hi Ward! ;-)), there were no noteworthy changes this week...


Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)

Wilfred van Velzen wrote to Kurt Weiske <=-

I suspect my IP is blocked on his firewall. I can also connect from a different IP adres...

I still get the connection refused.

If I saw a random IP banging on my binkp port, I might block it too.



--- MultiMail/Win v0.52
* Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)

Hi Kurt,

On 2026-03-28 12:25:08, you wrote to me:

I suspect my IP is blocked on his firewall. I can also connect from
a different IP adres...

I still get the connection refused.

If I saw a random IP banging on my binkp port, I might block it too.

I never "banged" his binkp port. I did one connection test. And the next week when I tested again I seemed to be blocked.

Bye, Wilfred.

--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)