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,

New node in net 153: ,150,Claude's_BBS,Vancouver_BC,Matthew_Asham,-Unpublished-,300,CM,XA,INA:claudes.lovelybits.org,IBN
Connect with BinktermPHP/1.6.7
XA flag can't be correct for an IBN only node.

The binkp protocol implementation for this software can be improved:
? 23 Jan 12:12:13 [18460] unexpected password from the remote on outgoing call: `'
? 23 Jan 12:12:13 [18460] rerror: Authentication failed

Hub flag was removed for node 36 in net 423.

Down node 5 in net 6035 was removed.


Bye, Wilfred.

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

Hello Wilfred,

On Friday January 23 2026 12:35, you wrote to All:

New node in net 153: ,150,Claude's_BBS,Vancouver_BC,Matthew_Asham,-Unpublished-,300,CM,XA,I NA:claudes.lovelybits.org,IBN Connect with BinktermPHP/1.6.7 XA flag
can't be correct for an IBN only node.

The binkp protocol implementation for this software can be improved:
? 23 Jan 12:12:13 [18460] unexpected password from the remote on
outgoing call: `' ? 23 Jan 12:12:13 [18460] rerror: Authentication
failed

I vaguely recall that some implementation have "only accept secure link" set by default... :-(


Cheers, Michiel

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

Hi Michiel,

On 2026-01-23 13:28:50, you wrote to me:

New node in net 153:
,150,Claude's_BBS,Vancouver_BC,Matthew_Asham,-Unpublished-,300,CM,XA,
INA:claudes.lovelybits.org,IBN Connect with BinktermPHP/1.6.7 XA flag
can't be correct for an IBN only node.

The binkp protocol implementation for this software can be improved:
? 23 Jan 12:12:13 [18460] unexpected password from the remote on
outgoing call: `' ? 23 Jan 12:12:13 [18460] rerror: Authentication
failed

MvdV> I vaguely recall that some implementation have "only accept secure link" set
MvdV> by default... :-(

That was/is Mystic. But I don't know if that is the case here. BinktermPHP seems to send an empty password to unknown nodes...

Bye, Wilfred.

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

Hello Wilfred,

On Friday January 23 2026 17:57, you wrote to me:

The binkp protocol implementation for this software can be
improved: ? 23 Jan 12:12:13 [18460] unexpected password from the
remote on outgoing call: `' ? 23 Jan 12:12:13 [18460] rerror:
Authentication failed

MvdV>> I vaguely recall that some implementation have "only accept
MvdV>> secure link" set by default... :-(

That was/is Mystic. But I don't know if that is the case here.
BinktermPHP seems to send an empty password to unknown nodes...

Hmmm, at first it wasn't clear to me where that error message came from. Now when I read it again, it seems to come from the binkd originating the call in respons to an empty password being send by the called binkd...


Cheers, Michiel

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

On Fri, 23 Jan 2026 15:57:52 +0100 Wilfred van Velzen wrote:

WV>> New node in net 153:
WV>> ,150,Claude's_BBS,Vancouver_BC,Matthew_Asham,-Unpublished-,300,CM,XA,
WV>> INA:claudes.lovelybits.org,IBN Connect with BinktermPHP/1.6.7 XA flag
WV>> can't be correct for an IBN only node.

WV>> The binkp protocol implementation for this software can be improved:
WV>> ? 23 Jan 12:12:13 [18460] unexpected password from the remote on
WV>> outgoing call: `' ? 23 Jan 12:12:13 [18460] rerror: Authentication
WV>> failed

MvdV> I vaguely recall that some implementation have "only accept secure link" set
MvdV> by default... :-(

That was/is Mystic. But I don't know if that is the case here. BinktermPHP seems to send an empty password to unknown nodes...

21:02 [1137173] call to 1:153/150@fidonet
21:02 [1137173] trying claudes.lovelybits.org [167.114.155.230]...
21:02 [1137173] connected
21:02 [1137173] binkp init done, socket # is 3
21:02 [1137173] outgoing session with claudes.lovelybits.org:24554 [167.114.155.230]
21:02 [1137173] send message NUL SYS news.fidonet.fi
21:02 [1137173] send message NUL ZYZ Tommi Koivula <tommi@fidonet.fi>
21:02 [1137173] send message NUL LOC EU
21:02 [1137173] send message NUL NDL CM,IBN,MO
21:02 [1137173] send message NUL TIME Fri, 23 Jan 2026 21:02:40 +0200
21:02 [1137173] send message NUL VER binkd/1.1a-115/Linux binkp/1.1
21:02 [1137173] - our ip 51.38.115.207 35059
21:02 [1137173] send message ADR 2:221/6@fidonet
21:02 [1137173] send message NUL OPT NDA EXTCMD CRYPT GZ BZ2
21:02 [1137173] touched /bbs/bso/fido.001/00990096.csy
21:02 [1137173] rcvd msg NUL SYS Claude's BBS
21:02 [1137173] SYS Claude's BBS
21:02 [1137173] rcvd msg NUL ZYZ Claude the Coder
21:02 [1137173] ZYZ Claude the Coder
21:02 [1137173] rcvd msg NUL LOC Vancouver, Canada
21:02 [1137173] LOC Vancouver, Canada
21:02 [1137173] rcvd msg NUL VER BinktermPHP/1.6.7 binkp/1.0
21:02 [1137173] VER BinktermPHP/1.6.7 binkp/1.0
21:02 [1137173] remote uses binkp v.1.0
21:02 [1137173] rcvd msg NUL TIME Fri, 23 Jan 2026 19:02:42 UTC
21:02 [1137173] TIME Fri, 23 Jan 2026 19:02:42 UTC
21:02 [1137173] rcvd msg ADR 1:153/150
21:02 [1137173] Cannot find domain for zone 1, assuming 'fidonet'
21:02 [1137173] created /bbs/bso/fido.001/00990096.bsy
21:02 [1137173] addr: 1:153/150@fidonet
21:02 [1137173] send message NUL TRF 0 0
21:02 [1137173] send message PWD -

It seems that I'm sending a password "-" here. Which is interpreted incorrect as a password?

21:02 [1137173] rcvd msg PWD
21:02 [1137173] unexpected password from the remote on outgoing call: `'
21:02 [1137173] rcvd msg OK insecure
21:02 [1137173] removing flo: /bbs/bso/fido.001/00990096.dlo
21:02 [1137173] unlinked `/bbs/bso/fido.001/00990096.dlo'
21:02 [1137173] send message EOB
21:02 [1137173] rcvd msg EOB
21:02 [1137173] there were 2 msgs in this batch
21:02 [1137173] done (to 1:153/150@fidonet, OK, S/R: 0/0 (0/0 bytes))
21:02 [1137173] processing kill list
21:02 [1137173] unlinked `/bbs/bso/fido.001/00990096.bsy'
21:02 [1137173] binkp deinit done...
21:02 [1137173] session closed, quitting...
21:02 [1137173] unlinked `/bbs/bso/fido.001/00990096.csy'
21:02 [1137173] bsy_remove_all: done
21:02 [1137171] rc(1137173)=0
21:02 [1137171] the queue is empty, quitting...
21:02 [1137171] downing clientmgr...
21:02 [1137171] bsy_remove_all: done


--
'Tommi

--- FMail-lnx64 2.3.2.6-B20260117
* Origin: nntp://news.fidonet.fi (2:221/360.0)

Hi Tommi,

On 2026-01-23 21:15:28, you wrote to me:

21:02 [1137173] send message PWD -

It seems that I'm sending a password "-" here. Which is interpreted incorrect
as a password?

21:02 [1137173] rcvd msg PWD
21:02 [1137173] unexpected password from the remote on outgoing call: `'

I haven't studied the binkp protocol, so I'm not sure what is supposed to happen. You could compare it to the logs of a crash call to a regular binkd node?


Bye, Wilfred.

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

New node in net 153:
,150,Claude's_BBS,Vancouver_BC,Matthew_Asham,-Unpublished-,300,CM,XA,
INA:claudes.lovelybits.org,IBN Connect with BinktermPHP/1.6.7 XA flag
can't be correct for an IBN only node.

The XA flag can be correct for a IBN node. AFAIK Synchronet and Binkd (with a little help) support file requests if so configured.

I don't think 153/150 supports file request at this point, though it is on the todo list. I'll get clarification about that from Matthew.

The binkp protocol implementation for this software can be improved:
? 23 Jan 12:12:13 [18460] unexpected password from the remote on
outgoing call: `' ? 23 Jan 12:12:13 [18460] rerror: Authentication
failed

I vaguely recall that some implementation have "only accept secure link"

set

by default... :-(

That was/is Mystic. But I don't know if that is the case here. BinktermPHP seems to send an empty password to unknown nodes...

Current versions of Mystic does't do that anymore. :)

I'm not sure if Matthew reads this area but I am sure he would welcome bug reports at 153/150 for anyone so inclined.

--- BBBS/Li6 v4.10 Toy-7
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hi Alan,

On 2026-01-23 15:47:52, you wrote to me:

New node in net 153:
,150,Claude's_BBS,Vancouver_BC,Matthew_Asham,-Unpublished-,300,CM,XA,
INA:claudes.lovelybits.org,IBN Connect with BinktermPHP/1.6.7 XA flag
can't be correct for an IBN only node.

The XA flag can be correct for a IBN node.

Nope, it can't be. Bark protocol is strictly for modem connections or virtual ones on a ITN connection, but not on a binkp (IBN) connection.

So with IBN, you can only have Wazoo file request, so XX or XW.

AFAIK Synchronet and Binkd (with a little help) support file requests
if so configured.

But only XW, because it doesn't support 'update requests', currently.

I don't think 153/150 supports file request at this point, though it
is on the todo list. I'll get clarification about that from Matthew.

So any X? flag is currently wrong!

That was/is Mystic. But I don't know if that is the case here.
BinktermPHP seems to send an empty password to unknown nodes...

Current versions of Mystic does't do that anymore. :)

Good!

I'm not sure if Matthew reads this area but I am sure he would welcome
bug reports at 153/150 for anyone so inclined.

He should connect here then! ;-)


Bye, Wilfred.

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

New node in net 153:
,150,Claude's_BBS,Vancouver_BC,Matthew_Asham,-Unpublished-,300,CM,XA, >>>>> INA:claudes.lovelybits.org,IBN Connect with BinktermPHP/1.6.7 XA flag >>>>> can't be correct for an IBN only node.

The XA flag can be correct for a IBN node.

Nope, it can't be. Bark protocol is strictly for modem connections or virtual ones on a ITN connection, but not on a binkp (IBN) connection.

So with IBN, you can only have Wazoo file request, so XX or XW.

Oh, right. I get XA, XX and XW mixed up..

--- BBBS/Li6 v4.10 Toy-7
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

On Fri, 23 Jan 2026 19:21:48 +0100 Wilfred van Velzen wrote:

TK> 21:02 [1137173] send message PWD -

TK> It seems that I'm sending a password "-" here. Which is interpreted
TK> incorrect as a password?

TK> 21:02 [1137173] rcvd msg PWD
TK> 21:02 [1137173] unexpected password from the remote on outgoing call: `'

I haven't studied the binkp protocol, so I'm not sure what is supposed
to happen. You could compare it to the logs of a crash call to a regular binkd node?

No "rcvd msg PWD" from any other binkp node I tried. Passworded link or not.

'Tommi

--- FMail-lnx64 2.3.2.6-B20260117
* Origin: news://news.fidonet.fi (2:221/360.0)

Alan Ianson wrote to Wilfred van Velzen <=-

New node in net 153:
,150,Claude's_BBS,Vancouver_BC,Matthew_Asham,-Unpublished-,300,CM,XA,
INA:claudes.lovelybits.org,IBN Connect with BinktermPHP/1.6.7 XA flag
can't be correct for an IBN only node.

The XA flag can be correct for a IBN node.

Nope, it can't be. Bark protocol is strictly for modem connections or

virtual

ones on a ITN connection, but not on a binkp (IBN) connection.

So with IBN, you can only have Wazoo file request, so XX or XW.

Oh, right. I get XA, XX and XW mixed up..

And yet, you make "authoritive" statements which are incorrect, without bothering to check your facts before blurting them out, even when you self-admit to being "mixed up" about them. Pfffffttt.




... Ignorance can be cured. Stupid is forever.
=== MultiMail/Linux v0.52
--- SBBSecho 3.34-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)

New node in net 153:
,150,Claude's_BBS,Vancouver_BC,Matthew_Asham,-Unpublished-,300,CM,XA, >>>>>> INA:claudes.lovelybits.org,IBN Connect with BinktermPHP/1.6.7 XA flag >>>>>> can't be correct for an IBN only node.

The XA flag can be correct for a IBN node.

Nope, it can't be. Bark protocol is strictly for modem connections or

virtual

ones on a ITN connection, but not on a binkp (IBN) connection.

So with IBN, you can only have Wazoo file request, so XX or XW.

Oh, right. I get XA, XX and XW mixed up..

And yet, you make "authoritive" statements which are incorrect, without bothering to check your facts before blurting them out, even when you self-admit to being "mixed up" about them. Pfffffttt.

I am not making "authorative" statements but you are right, I mixed up XA, XX and XW.

--- BBBS/Li6 v4.10 Toy-7
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Alan Ianson wrote to Dan Clough <=-

New node in net 153:
,150,Claude's_BBS,Vancouver_BC,Matthew_Asham,-Unpublished-,300,CM,XA,
INA:claudes.lovelybits.org,IBN Connect with BinktermPHP/1.6.7 XA flag
can't be correct for an IBN only node.

The XA flag can be correct for a IBN node.

Nope, it can't be. Bark protocol is strictly for modem connections or
virtual ones on a ITN connection, but not on a binkp (IBN)
connection.
So with IBN, you can only have Wazoo file request, so XX or XW.

Oh, right. I get XA, XX and XW mixed up..

And yet, you make "authoritive" statements which are incorrect, without bothering to check your facts before blurting them out, even when you self-admit to being "mixed up" about them. Pfffffttt.

I am not making "authorative" statements but you are right, I mixed up
XA, XX and XW.

"The XA flag can be correct for a IBN node."

You wouldn't call that an authoritive statement?

What *would* you call it?



... Never assume the obvious is true!
=== MultiMail/Linux v0.52
--- SBBSecho 3.34-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)

I am not making "authorative" statements but you are right, I mixed up
XA, XX and XW.

"The XA flag can be correct for a IBN node."

I explained already that I mixed up the XA and XW flag.

You wouldn't call that an authoritive statement?

I have no "authority".

What *would* you call it?

I mixed up the XA and XW flag as I have said already. Several times.

I have no interest in carrying this (or anything else) on with you. If you really need to hear from me, use netmail.

--- BBBS/Li6 v4.10 Toy-7
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

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)

Hi Alan,

On 2026-01-23 17:37:34, you wrote to me:

New node in net 153:
,150,Claude's_BBS,Vancouver_BC,Matthew_Asham,-Unpublished-,300,CM,X
A,INA:claudes.lovelybits.org,IBN
Connect with BinktermPHP/1.6.7 XA flag
can't be correct for an IBN only node.

The XA flag can be correct for a IBN node.

Nope, it can't be. Bark protocol is strictly for modem connections or
virtual ones on a ITN connection, but not on a binkp (IBN) connection.

So with IBN, you can only have Wazoo file request, so XX or XW.

Oh, right. I get XA, XX and XW mixed up..

I noticed it's fixed in the Z1 version of the nodelist, but not yet in the Z2 and Z3 versions. In the those versions the Z1 segment is stuck at day 028 (so 2 days behind) for some reason...?


Bye, Wilfred.

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

I noticed it's fixed in the Z1 version of the nodelist, but not yet in the Z2 and Z3 versions. In the those versions the Z1 segment is stuck at day 028
(so days behind) for some reason...?

I just sent in a fresh segment with that info yesterday or the day before. It may take a short time for that to propagate to z2 and 3.

--- BBBS/Li6 v4.10 Toy-7
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hi Alan,

On 2026-01-30 04:44:48, you wrote to me:

I noticed it's fixed in the Z1 version of the nodelist, but not yet in
the Z2 and Z3 versions. In the those versions the Z1 segment is stuck
at day 028 (so days behind) for some reason...?

I just sent in a fresh segment with that info yesterday or the day before. It
may take a short time for that to propagate to z2 and 3.

I have no doubt about it, it will. ;-)


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)