Weekly nodelist report on noteworthy changes (311)
From Wilfred van Velzen@2:280/464 to All on Fri Nov 7 11:57:04 2025
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)
From Wilfred van Velzen@2:280/464 to All on Fri Nov 14 12:40:09 2025
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)
From Atreyu@1:229/426 to Wilfred Van Velzen on Sat Nov 8 18:52:46 2025
On 07 Nov 25 11:57:04, Wilfred Van Velzen said the following to All:
There is nothing to test. And a Pvt node is not allowed in a ZIN section anyway.
Sue me you Dutch twat.
Nick
--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)
From Wilfred van Velzen@2:280/464 to All on Fri Nov 21 12:52:26 2025
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)
From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Sat Nov 22 21:51:18 2025
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)
From Wilfred van Velzen@2:280/464 to Michiel van der Vlist on Sat Nov 22 23:52:29 2025
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)
From Andrew Leary@1:320/219 to Wilfred van Velzen on Sun Nov 23 07:09:22 2025
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.
From Tommi Koivula@2:221/360 to Andrew Leary on Sun Nov 23 14:58:33 2025
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)
From Tommi Koivula@2:221/360 to Andrew Leary on Sun Nov 23 17:17:33 2025
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)
From Andrew Leary@1:320/219 to Tommi Koivula on Sun Nov 23 12:33:26 2025
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.
From Tommi Koivula@2:221/360 to Andrew Leary on Sun Nov 23 19:59:43 2025
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)
From Wilfred van Velzen@2:280/464 to All on Fri Nov 28 12:32:39 2025
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)
From Wilfred van Velzen@2:280/464 to All on Fri Nov 28 12:41:38 2025
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)
From Wilfred van Velzen@2:280/464 to Tommi Koivula on Fri Nov 28 12:39:07 2025
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)
From Kurt Weiske@1:218/700 to Wilfred van Velzen on Sat Nov 29 10:10:15 2025
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.
From Wilfred van Velzen@2:280/464 to Kurt Weiske on Sat Nov 29 22:59:28 2025
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)
From Dan Clough@1:135/115 to Wilfred van Velzen on Sat Nov 29 21:48:43 2025
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)
From Tommi Koivula@2:221/360 to Wilfred van Velzen on Sun Nov 30 09:59:23 2025
* 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)
From Wilfred van Velzen@2:280/464 to Kurt Weiske on Fri Dec 5 12:40:03 2025
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)
From Wilfred van Velzen@2:280/464 to All on Fri Dec 5 12:42:53 2025
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)
From Wilfred van Velzen@2:280/464 to All on Fri Dec 5 12:54:44 2025
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)
From Tommi Koivula@2:221/1.1530 to Wilfred van Velzen on Fri Dec 5 19:54:17 2025
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. ;-)
From Kurt Weiske@1:218/700 to Wilfred van Velzen on Fri Dec 5 17:28:19 2025
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.
From Wilfred van Velzen@2:280/464 to All on Fri Dec 12 12:24:49 2025
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)
From Wilfred van Velzen@2:280/464 to All on Fri Dec 12 13:09:20 2025
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)
From Wilfred van Velzen@2:280/464 to All on Fri Dec 19 12:16:12 2025
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)
From Wilfred van Velzen@2:280/464 to All on Fri Dec 19 12:38:28 2025
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)
From Carlos Navarro@2:341/234.12 to Wilfred van Velzen on Fri Dec 19 17:51:27 2025
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)
From Wilfred van Velzen@2:280/464 to Carlos Navarro on Fri Dec 19 17:57:39 2025
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)
From Wilfred van Velzen@2:280/464 to All on Fri Dec 26 12:36:51 2025
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)
From Wilfred van Velzen@2:280/464 to All on Fri Dec 26 12:44:20 2025
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)
From Mike Miller@1:154/30.1 to Wilfred van Velzen on Sat Dec 27 21:38:31 2025
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)
From Wilfred van Velzen@2:280/464 to All on Fri Jan 2 13:16:39 2026
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)
From Tommi Koivula@2:221/1.1 to Wilfred van Velzen on Fri Jan 2 18:59:23 2026
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)
From Wilfred van Velzen@2:280/464 to Tommi Koivula on Fri Jan 2 18:18:42 2026
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)
From Tommi Koivula@2:221/1.1 to Wilfred van Velzen on Fri Jan 2 20:36:14 2026
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:
--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Fri Jan 9 12:31:06 2026
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...
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)
From Wilfred van Velzen@2:280/464 to All on Fri Jan 9 13:09:03 2026
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)
From Tommi Koivula@2:221/1.254 to Wilfred van Velzen on Fri Jan 9 19:31:59 2026
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...
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 ===
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)
From Wilfred van Velzen@2:280/464 to All on Fri Jan 16 13:29:15 2026
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)
From Wilfred van Velzen@2:280/464 to All on Fri Jan 16 13:35:14 2026
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)
From Wilfred van Velzen@2:280/464 to All on Fri Jan 23 12:35:01 2026
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)
From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Fri Jan 23 13:28:50 2026
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)
From Wilfred van Velzen@2:280/464 to Michiel van der Vlist on Fri Jan 23 17:57:52 2026
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)
From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Fri Jan 23 19:24:49 2026
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)
From Tommi Koivula@2:221/360 to Wilfred van Velzen on Fri Jan 23 21:15:28 2026
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 <[email protected]>
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
From Wilfred van Velzen@2:280/464 to Tommi Koivula on Fri Jan 23 21:21:49 2026
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)
From Alan Ianson@1:153/757 to Wilfred van Velzen on Fri Jan 23 15:47:52 2026
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)
From Wilfred van Velzen@2:280/464 to Alan Ianson on Sat Jan 24 02:20:39 2026
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)
From Alan Ianson@1:153/757 to Wilfred van Velzen on Fri Jan 23 17:37:34 2026
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)
From Tommi Koivula@2:221/360 to Wilfred van Velzen on Sat Jan 24 09:51:36 2026
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.
From Dan Clough@1:135/115 to Alan Ianson on Sat Jan 24 10:23:56 2026
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)
From Alan Ianson@1:153/757 to Dan Clough on Sat Jan 24 12:32:54 2026
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)
From Dan Clough@1:135/115 to Alan Ianson on Sat Jan 24 20:22:59 2026
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)
From Alan Ianson@1:153/757 to Dan Clough on Sat Jan 24 19:34:28 2026
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)
From Wilfred van Velzen@2:280/464 to All on Fri Jan 30 12:46:17 2026
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)
From Wilfred van Velzen@2:280/464 to Alan Ianson on Fri Jan 30 12:40:40 2026
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)
From Alan Ianson@1:153/757 to Wilfred van Velzen on Fri Jan 30 04:44:48 2026
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)
From Wilfred van Velzen@2:280/464 to Alan Ianson on Fri Jan 30 14:03:49 2026
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)
From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Fri Jan 30 15:26:40 2026
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)
From Stas Mishchenkov@2:460/5858 to Wilfred van Velzen on Fri Jan 30 18:49:00 2026
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)
From Wilfred van Velzen@2:280/464 to All on Fri Feb 6 12:22:38 2026
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)
From Wilfred van Velzen@2:280/464 to All on Fri Feb 6 12:38:52 2026
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)
From Wilfred van Velzen@2:280/464 to All on Fri Feb 13 12:42:04 2026
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)
From Wilfred van Velzen@2:280/464 to All on Fri Feb 13 12:45:30 2026
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)
From Wilfred van Velzen@2:280/464 to All on Fri Feb 20 12:34:26 2026
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)
From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Sun Feb 22 16:36:39 2026
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)
From Wilfred van Velzen@2:280/464 to Michiel van der Vlist on Sun Feb 22 17:39:37 2026
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)
From Alexander Kruglikov@2:5053/58 to Wilfred van Velzen on Wed Feb 25 21:50:49 2026
Åα¿óÑΓ, Wilfred!
22 ΣÑó 26 17:39, Wilfred van Velzen »¿ßá½(á) ¬ Michiel van der Vlist:
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)
From Michiel van der Vlist@2:280/5555 to Alexander Kruglikov on Thu Feb 26 12:59:47 2026
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)
From Alexander Kruglikov@2:5053/58 to Michiel van der Vlist on Thu Feb 26 23:16:15 2026
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.
From Michiel van der Vlist@2:280/5555 to Alexander Kruglikov on Fri Feb 27 09:56:56 2026
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)
From Alexander Kruglikov@2:5053/58 to Michiel van der Vlist on Fri Feb 27 13:47:28 2026
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)
From Wilfred van Velzen@2:280/464 to All on Fri Feb 27 12:14:33 2026
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)
From Wilfred van Velzen@2:280/464 to All on Fri Feb 27 12:31:00 2026
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)
From Michiel van der Vlist@2:280/5555 to Alexander Kruglikov on Fri Feb 27 18:20:06 2026
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)
From Alexander Kruglikov@2:5053/58 to Michiel van der Vlist on Mon Mar 2 13:05:58 2026
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.
From Wilfred van Velzen@2:280/464 to Alexander Kruglikov on Wed Mar 4 15:36:54 2026
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)
From Wilfred van Velzen@2:280/464 to Wilfred van Velzen on Fri Mar 6 12:15:59 2026
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)
From Wilfred van Velzen@2:280/464 to All on Fri Mar 6 12:37:23 2026
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)
From Wilfred van Velzen@2:280/464 to All on Fri Mar 13 13:00:56 2026
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)
From Alexander Kruglikov@2:5053/58 to Wilfred van Velzen on Fri Mar 13 16:48:07 2026
Åα¿óÑΓ, 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.
From Stas Mishchenkov@2:460/5858 to Alexander Kruglikov on Sat Mar 14 12:01:18 2026
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)
From Kurt Weiske@1:218/700 to Wilfred van Velzen on Sat Mar 14 08:32:34 2026
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
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
From Wilfred van Velzen@2:280/464 to Kurt Weiske on Sat Mar 14 17:20:35 2026
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)
From Wilfred van Velzen@2:280/464 to All on Fri Mar 20 11:57:09 2026
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.
--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Fri Mar 20 12:17:32 2026
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)
From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Fri Mar 20 13:29:41 2026
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)
From Stas Mishchenkov@2:460/5858 to Wilfred van Velzen on Fri Mar 20 18:04:16 2026
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.
[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)
From Stas Mishchenkov@2:460/5858 to Michiel van der Vlist on Fri Mar 20 18:06:56 2026
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)
From Tommi Koivula@2:221/1.1 to Stas Mishchenkov on Fri Mar 20 17:33:36 2026
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.
From Wilfred van Velzen@2:280/464 to Stas Mishchenkov on Fri Mar 20 17:44:30 2026
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.
[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)
From Wilfred van Velzen@2:280/464 to Stas Mishchenkov on Fri Mar 20 17:48:11 2026
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)
From Tommi Koivula@2:221/360 to Wilfred van Velzen on Fri Mar 20 19:36:08 2026
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.
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)
From Wilfred van Velzen@2:280/464 to All on Fri Mar 27 13:03:34 2026
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)
From Wilfred van Velzen@2:280/464 to All on Fri Mar 27 13:11:04 2026
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)
From Kurt Weiske@1:218/700 to Wilfred van Velzen on Sat Mar 28 12:25:08 2026
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.
From Wilfred van Velzen@2:280/464 to Kurt Weiske on Sun Mar 29 00:15:59 2026
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)
From Atreyu@1:229/426 to Kurt Weiske on Sat Mar 28 20:39:44 2026
On 28 Mar 26 12:25:08, Kurt Weiske said the following to Wilfred Van Velzen:
I still get the connection refused.
If I saw a random IP banging on my binkp port, I might block it too.
The Dutch like to bang things without asking, their usual foreplay of 2 hours of begging never works out for them.
Nick
--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)
From Wilfred van Velzen@2:280/464 to All on Fri Apr 3 12:19:56 2026
Hi All,
New RIN in R50: ,86,UA9278SWL,Nizhnevartovsk,Ivan_Zelenyi,-Unpublished-,300,CM,IMI:[email protected]
Not directly tested, but the email address seems to exist.
Bye, Wilfred.
--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)
From Ivan Zelenyi@2:50/86 to Wilfred van Velzen on Sun Apr 5 11:29:40 2026
Åα¿óÑΓ, Wilfred!
03 á»α 26 12:19, Wilfred van Velzen -> All:
[email protected] Not directly tested, but the email address seems to
exist.
Yes, this e-mail is for receiving bundles. At March 2026, Alexey 2:5020/8912 and I tested the work of fidonode-fidopoint by e-mail. now this is relevant in the case of a total "white list".
æ ¡á¿½πτΦ¿¼¿ »«ªÑ½á¡¿∩¼¿, Ivan.
nizhnevartovsk WX: +5?C, Humidity 93%, Wind ?8km/h, 993hPa, 0.0mm Fog
--- GoldED+/LNX 1.1.5-b20250409
* Origin: Living in interesting times (2:50/86)
From Tommi Koivula@2:221/1.1 to Wilfred van Velzen on Sun Apr 5 18:40:56 2026
* Originally in nodelist-police
* Crossposted in fmail_help
Hi Wilfred.
05 Apr 26 11:29:40, Ivan Zelenyi wrote to you:
[email protected] Not directly tested, but the email address seems to
exist.
Yes, this e-mail is for receiving bundles. At March 2026, Alexey 2:5020/8912 and I tested the work of fidonode-fidopoint by e-mail. now this is relevant in the case of a total "white list".
Fmail can send mail bundles via email. It would be nice if it could search the nodelist for IMI flags. ;-)
'Tommi
---
* Origin: Point One (2:221/1.1)
From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Sun Apr 5 19:18:18 2026
Hello Tommi,
On Sunday April 05 2026 18:40, you wrote to Wilfred van Velzen:
Yes, this e-mail is for receiving bundles. At March 2026, Alexey
2:5020/8912 and I tested the work of fidonode-fidopoint by
e-mail. now this is relevant in the case of a total "white list".
Fmail can send mail bundles via email.
Could. Past tense. FMAIL can only send via SMTP and no e-mail server accepts that any more. You need at least starttls or something like that.
It would be nice if it could search the nodelist for IMI flags. ;-)
No use, see above.
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)
From Tommi Koivula@2:221/1.1 to Michiel van der Vlist on Sun Apr 5 20:52:46 2026
Hi Michiel.
05 Apr 26 19:18:18, you wrote to me:
Yes, this e-mail is for receiving bundles. At March 2026, Alexey
2:5020/8912 and I tested the work of fidonode-fidopoint by
e-mail. now this is relevant in the case of a total "white list".
Fmail can send mail bundles via email.
Could. Past tense. FMAIL can only send via SMTP and no e-mail server accepts that any more. You need at least starttls or something like
that.
You're so wrong.
=== Cut ===
---------- Sun 2026-04-05, FMail-lnx64-2.3.2.6-Beta20260403 - Pack
18:37:30 Message #60 : 2:221/6 -> 2:221/1000
18:37:30 Moving /bbs/fmail/netmail/60.msg to /bbs/fmail/netmail-sent/184.msg
18:37:30 Backup /bbs/bso/fido/9d281ba0.pkt -> /bbs/fmail/backup/out/9d281ba0.pkt
18:37:30 Create /bbs/bso/fido/00dd03e8.clo
18:37:30 Sending new mail from 2:221/6.66 to 2:221/1000
18:37:30 Connecting to localhost (127.0.0.1) on port 25 (SMTP)
18:37:30 Sending mail for node 2:221/1000 to [email protected]
18:37:30 SMTP connection closed
18:37:30 Netmail: 1, Personal: 0, Hudson: 0, JAMbase: 0
18:37:30 Msgbase net: 0, echo: 0, dup: 0, bad: 0
18:37:30 Pack Active: 0.0076 sec.
=== Cut ===
Sent and received fine.
'Tommi
---
* Origin: Point One (2:221/1.1)
From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Sun Apr 5 21:36:54 2026
Hello Tommi,
On Sunday April 05 2026 20:52, you wrote to me:
Fmail can send mail bundles via email.
Could. Past tense. FMAIL can only send via SMTP and no e-mail
server accepts that any more. You need at least starttls or
something like that.
You're so wrong.
=== Cut ===
---------- Sun 2026-04-05, FMail-lnx64-2.3.2.6-Beta20260403 - Pack
18:37:30 Message #60 : 2:221/6 -> 2:221/1000
18:37:30 Moving /bbs/fmail/netmail/60.msg to /bbs/fmail/netmail-sent/184.msg 18:37:30 Backup /bbs/bso/fido/9d281ba0.pkt ->
/bbs/fmail/backup/out/9d281ba0.pkt 18:37:30 Create /bbs/bso/fido/00dd03e8.clo 18:37:30 Sending new mail from 2:221/6.66
to 2:221/1000 18:37:30 Connecting to localhost (127.0.0.1) on port 25 (SMTP) 18:37:30 Sending mail for node 2:221/1000 to [email protected] 18:37:30 SMTP connection closed 18:37:30
Netmail: 1, Personal: 0, Hudson: 0, JAMbase: 0 18:37:30 Msgbase
net: 0, echo: 0, dup: 0, bad: 0 18:37:30 Pack Active: 0.0076 sec.
=== Cut ===
Sent and received fine.
Yeah, if you have your own SMTP server....
None of the e-mail providers that I use still accept SMTP on port 25.
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)
From Wilfred van Velzen@2:280/464 to Tommi Koivula on Sun Apr 5 21:51:40 2026
* Originally in FMAIL_HELP
* Crossposted in NODELIST-POLICE
Hi Tommi,
On 2026-04-05 18:40:56, you wrote to me:
[email protected] Not directly tested, but the email address seems to
exist.
Yes, this e-mail is for receiving bundles. At March 2026, Alexey
2:5020/8912 and I tested the work of fidonode-fidopoint by e-mail. now
this is relevant in the case of a total "white list".
Fmail can send mail bundles via email. It would be nice if it could search the
nodelist for IMI flags. ;-)
It can send bundles via binkpd. It doesn't search the nodelist for IBN flags either... ?
Bye, Wilfred.
--- FMail-lnx64 2.3.2.6-B20251227
* Origin: FMail development HQ (2:280/464)
From Wilfred van Velzen@2:280/464 to Michiel van der Vlist on Sun Apr 5 21:53:36 2026
Hi Michiel,
On 2026-04-05 19:18:18, you wrote to Tommi Koivula:
Fmail can send mail bundles via email.
MvdV> Could. Past tense. FMAIL can only send via SMTP and no e-mail server accepts
MvdV> that any more. You need at least starttls or something like that.
In my experience, that is not true.
And as Tommi demonstrated, you can always setup your own mail server and use that as a relay.
Bye, Wilfred.
--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)
From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Mon Apr 6 10:30:16 2026
Hello Wilfred,
On Sunday April 05 2026 21:53, you wrote to me:
Fmail can send mail bundles via email.
MvdV>> Could. Past tense. FMAIL can only send via SMTP and no e-mail
MvdV>> server accepts that any more. You need at least starttls or
MvdV>> something like that.
In my experience, that is not true.
In my experience an e-mail client that is limited to SMTP over port 25 is pretty useless these days. I have not been able to find a server that will accept fmail's mail packets.
And as Tommi demonstrated, you can always setup your own mail server
and use that as a relay.
Setting up you own mail server is difficult these days. Most providers block incoming mail ports. So that mailserver would only serve to relay outgoing masil packets for fmail. That is too much effort for too little return.
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)
From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Mon Apr 6 11:48:13 2026
Hello Tommi,
On Sunday April 05 2026 20:52, you wrote to me:
Could. Past tense. FMAIL can only send via SMTP and no e-mail
server accepts that any more. You need at least starttls or
something like that.
You're so wrong.
=== Cut ===
---------- Sun 2026-04-05, FMail-lnx64-2.3.2.6-Beta20260403 - Pack
18:37:30 Message #60 : 2:221/6 -> 2:221/1000
18:37:30 Moving /bbs/fmail/netmail/60.msg to /bbs/fmail/netmail-sent/184.msg 18:37:30 Backup /bbs/bso/fido/9d281ba0.pkt ->
/bbs/fmail/backup/out/9d281ba0.pkt 18:37:30 Create /bbs/bso/fido/00dd03e8.clo 18:37:30 Sending new mail from 2:221/6.66
to 2:221/1000 18:37:30 Connecting to localhost (127.0.0.1) on port 25 (SMTP) 18:37:30 Sending mail for node 2:221/1000 to [email protected] 18:37:30 SMTP connection closed 18:37:30
Netmail: 1, Personal: 0, Hudson: 0, JAMbase: 0 18:37:30 Msgbase
net: 0, echo: 0, dup: 0, bad: 0 18:37:30 Pack Active: 0.0076 sec.
=== Cut ===
Sent and received fine.
-
So can we all use your SMTP server for relaying fmail's mail packets?
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)
From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Mon Apr 6 12:06:04 2026
Hello Tommi,
Monday April 06 2026 11:48, I wrote to you:
Sent and received fine.
So can we all use your SMTP server for relaying fmail's mail packets?
Guess not:
D:\fido\FMAIL>fmailw32 pack
FMail-W32-2.3.0.1-Beta20240319 - The Fast Echomail Processor
Copyright (C) 1991-2024 by FMail Developers - All rights reserved
Scanning netmail directory...
Packing messages...
Message #1 : 2:280/5555 -> 2:221/1000
Moving \FIDO\MAIL\1.msg to \FIDO\RSMAIL\11440.msg
Backup \FIDO\OUTBOUND\9d384f80.pkt -> \fido\oubackup\9d384f80.pkt
Create \FIDO\OUTBOUND\00dd03e8.flo
Sending new mail from 2:280/5555 to 2:221/1000
Connecting to 51.38.115.207 (51.38.115.207) on port 25 (SMTP)
Sending mail for node 2:221/1000 to [email protected]
Expected 250, received 450: SMTP server error
No RCPT TO: success reply
SMTP connection closed
So please enlighten me, why exactly was the HELO rejected? Is is because [email protected] is not a valid e-mail address? I tried again with a valid address, but I get the same error. ??
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)
From Tommi Koivula@2:221/360 to Michiel van der Vlist on Tue Apr 7 15:38:53 2026
So please enlighten me, why exactly was the HELO rejected? Is is because [email protected] is not a valid e-mail address? I tried again with a
valid address, but I get the same error. ??
You need to send FQDN when talking to my Postfix. Now your FMail sends just "Fido" which doesn't resolve. I don't think you can change that behaviour in FMail so it's better to use your own local mail server. Or just forget the whole thing. :)
'Tommi
--- FastEcho/2 1.46.1 Revival
* Origin: nntp://rbb.fidonet.fi - Finland (2:221/360.0)
From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Tue Apr 7 16:31:33 2026
So please enlighten me, why exactly was the HELO rejected? Is is
because [email protected] is not a valid e-mail address? I tried
again with a valid address, but I get the same error. ??
You need to send FQDN when talking to my Postfix. Now your FMail sends just "Fido" which doesn't resolve. I don't think you can change that behaviour in FMail
There are just two things I can configure for this function:
1) My e-mail adress
2) SMTP server to use.
I should add that this has worked inm the past when my provider's SMTP server still accepted raw SMTP on port 25.
Do you consider it a bug in Fmail that your SMTP server rejects me, or is it something in you SMTP server? Like requiring an additional authorisation?
so it's better to use your own local mail server. Or just forget the
whole thing. :)
I think I will just forget it like I actually did many years ago when providers stopt accepting raw SMTP. Installing my own local mail server just for this purpose is too much. I never was enthousiastic about Fido over e-mail anyway. So I will indeed just forget it. For me this function of Fmail is unusable.
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)
From Wilfred van Velzen@2:280/464.112 to Tommi Koivula on Tue Apr 7 16:55:53 2026
Hi Tommi,
On 07 Apr 26 15:38, Tommi Koivula wrote to Michiel van der Vlist:
about: "Weekly nodelist report on noteworthy changes (093)":
So please enlighten me, why exactly was the HELO rejected? Is is because [email protected] is not a valid e-mail address? I tried again with a
valid address, but I get the same error. ??
You need to send FQDN when talking to my Postfix. Now your FMail sends just "Fido" which doesn't resolve. I don't think you can change that behaviour in FMail
Do you think a hardcoded 'fidonet.org' in FMail would work for everyone?
From Tommi Koivula@2:221/360 to Michiel van der Vlist on Tue Apr 7 21:16:18 2026
Hi Michiel.
07 Apr 26 16:31, you wrote to me:
You need to send FQDN when talking to my Postfix. Now your FMail
sends just "Fido" which doesn't resolve. I don't think you can
change that
behaviour in FMail
There are just two things I can configure for this function:
1) My e-mail adress
2) SMTP server to use.
I should add that this has worked inm the past when my provider's SMTP server still accepted raw SMTP on port 25.
Times change.. Nowadays it is not so easy to send mail, for example to @gmail.com from ipv6 address. ;)
Do you consider it a bug in Fmail that your SMTP server rejects me, or
is it something in you SMTP server?
My server simply checks the hostname in HELO. It is intentional. Helps with spammers.
From Tommi Koivula@2:221/360 to Wilfred van Velzen on Tue Apr 7 21:23:06 2026
Hi Wilfred.
07 Apr 26 16:55, you wrote to me:
You need to send FQDN when talking to my Postfix. Now your FMail
sends just "Fido" which doesn't resolve. I don't think you can
change that
behaviour in FMail
Do you think a hardcoded 'fidonet.org' in FMail would work for
everyone?
For sure better than "Fido". The real reverse of the sender would be better.
From Wilfred van Velzen@2:280/464 to Tommi Koivula on Tue Apr 7 21:18:29 2026
Hi Tommi,
On 2026-04-07 21:23:06, you wrote to me:
You need to send FQDN when talking to my Postfix. Now your FMail
sends just "Fido" which doesn't resolve. I don't think you can
change that behaviour in FMail
Do you think a hardcoded 'fidonet.org' in FMail would work for
everyone?
For sure better than "Fido". The real reverse of the sender would be better.
That would require an other setting, and too much work for a mostly unused funtion...
Bye, Wilfred.
--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to Tommi Koivula on Tue Apr 7 21:36:30 2026
Hi Tommi,
On 2026-04-07 21:18:29, I wrote to you:
You need to send FQDN when talking to my Postfix. Now your FMail
sends just "Fido" which doesn't resolve. I don't think you can
change that behaviour in FMail
Do you think a hardcoded 'fidonet.org' in FMail would work for
everyone?
For sure better than "Fido". The real reverse of the sender would be
better.
That would require an other setting, and too much work for a mostly unused
funtion...
I was looking at the code, and it turns out on both linux and windows it uses the gethostname() function (which is posix) to get the string to put behind the HELO command.
On linux this returns the same string as the 'uname -n' command. On windows it's the output of the 'hostname' command. And probably just the computer name, something Michiel could set himself if he likes to experiment with this. ;-)
Bye, Wilfred.
--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)
From Tommi Koivula@2:221/360 to Wilfred van Velzen on Wed Apr 8 12:03:39 2026
On 7.4.2026 22.36, Wilfred van Velzen wrote:
You need to send FQDN when talking to my Postfix. Now your FMail TK>>>> sends just "Fido" which doesn't resolve. I don't think you can
change that behaviour in FMail
Do you think a hardcoded 'fidonet.org' in FMail would work for
everyone?
For sure better than "Fido". The real reverse of the sender would be TK>> better.
That would require an other setting, and too much work for a mostly unused
funtion...
I was looking at the code, and it turns out on both linux and windows it
uses the gethostname() function (which is posix) to get the string to
put behind the HELO command.
On linux this returns the same string as the 'uname -n' command. On
windows it's the output of the 'hostname' command. And probably just the computer name, something Michiel could set himself if he likes to
experiment with this. ;-)
So it *IS* working pretty much as it should. ;-)
'Tommi
--- FastEcho/2 1.46.1 Revival
* Origin: nntp://rbb.fidonet.fi - Finland (2:221/360.0)
From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Wed Apr 8 12:28:25 2026
Hello Wilfred,
On Tuesday April 07 2026 21:36, you wrote to Tommi Koivula:
I was looking at the code, and it turns out on both linux and windows
it uses the gethostname() function (which is posix) to get the string
to put behind the HELO command.
On linux this returns the same string as the 'uname -n' command. On windows it's the output of the 'hostname' command. And probably just
the computer name, something Michiel could set himself if he likes to experiment with this. ;-)
I did some experiments. Let's move this to the FMAIL_HELP area.
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)
From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Wed Apr 8 12:28:32 2026
Hello Tommi,
On Wednesday April 08 2026 12:03, you wrote to Wilfred van Velzen:
I was looking at the code, and it turns out on both linux and
windows it uses the gethostname() function (which is posix) to get
the string to put behind the HELO command.
On linux this returns the same string as the 'uname -n' command. On
windows it's the output of the 'hostname' command. And probably just
the computer name, something Michiel could set himself if he likes
to experiment with this. ;-)
So it *IS* working pretty much as it should. ;-)
No, it is not. See my comment in FMAIL_HELP.
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)
From Wilfred van Velzen@2:280/464 to Tommi Koivula on Wed Apr 8 13:26:00 2026
* Originally in NODELIST-POLICE
* Crossposted in FMAIL_HELP
Hi Tommi,
On 2026-04-08 12:03:39, you wrote to me:
I was looking at the code, and it turns out on both linux and windows
it uses the gethostname() function (which is posix) to get the string
to put behind the HELO command. On linux this returns the same string
as the 'uname -n' command. On windows it's the output of the 'hostname'
command. And probably just the computer name, something Michiel could
set himself if he likes to experiment with this. ;-)
So it *IS* working pretty much as it should. ;-)
You would guess so given the function name. But in practice it's not (see Michiels test)...
Bye, Wilfred.
--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Fri Apr 10 12:59:39 2026
Hi All,
New node in net 154: ,140,The_Down-Lo,Minneapolis_MN,Brian_Davidson,-Unpublished-,300,CM,INA:binkp.winzlo.com,IBN
Connect with: BinkIT/2.42,JSBinkP/5,sbbs3.21f/Linux
New node in net 229: ,114,Va2rfc_BBS,Les_Mechins_QC,Richard_Murray,-Unpublished-,300,CM,INA:va2rfc.photorm.net,IBN
Host va2rfc.photorm.net not found: 3(NXDOMAIN)
In net 633, no longer Pvt: ,414,Wicked_Garden_BBS,Burnside_Vic,Hung_Tran,-Unpublished-,300,CM,IBN:wgbbs.ddns.net
Connect with: BinkIT/2.42,JSBinkP/4,sbbs3.21e/Win32
Node in net 712 was removed: ,730,bbs.intaa.net,Tokyo_Japan,Yoshito_Uchiyama,-Unpublished-,300,CM,XX,INA:bbs.intaa.net,IBN
I still get a connect OK on both IPv4 and IPv6, with: binkd/1.1a-115/386BSD ?
Node 27 status in net 902 changed from Hold to Down:
Bye, Wilfred.
--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)
From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Fri Apr 10 13:09:25 2026
Hello Wilfred,
On Friday April 10 2026 12:59, you wrote to All:
New node in net 154: ,140,The_Down-Lo,Minneapolis_MN,Brian_Davidson,-Unpublished-,300,CM,IN A:binkp.winzlo.com,IBN Connect with:
BinkIT/2.42,JSBinkP/5,sbbs3.21f/Linux
Check.
New node in net 229: ,114,Va2rfc_BBS,Les_Mechins_QC,Richard_Murray,-Unpublished-,300,CM,INA :va2rfc.photorm.net,IBN Host va2rfc.photorm.net not found: 3(NXDOMAIN)
idem.
In net 633, no longer Pvt: ,414,Wicked_Garden_BBS,Burnside_Vic,Hung_Tran,-Unpublished-,300,CM,IBN :wgbbs.ddns.net Connect with: BinkIT/2.42,JSBinkP/4,sbbs3.21e/Win32
Node in net 712 was removed: ,730,bbs.intaa.net,Tokyo_Japan,Yoshito_Uchiyama,-Unpublished-,300,CM,X X,INA:bbs.intaa.net,IBN I still get a connect OK on both IPv4 and
IPv6, with: binkd/1.1a-115/386BSD ?
Same here, still connects. So I wonder why it was removed. It was a relatively new node. Just a few weeks old.
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)
From Wilfred van Velzen@2:280/464 to Michiel van der Vlist on Fri Apr 10 13:55:04 2026
Hi Michiel,
On 2026-04-10 13:09:25, you wrote to me:
New node in net 229:
,114,Va2rfc_BBS,Les_Mechins_QC,Richard_Murray,-Unpublished-,300,CM,IN
A:va2rfc.photorm.net,IBN Host va2rfc.photorm.net not found:
3(NXDOMAIN)
MvdV> idem.
And bad it was already entered in the nodelist... :-(
Node in net 712 was removed:
,730,bbs.intaa.net,Tokyo_Japan,Yoshito_Uchiyama,-Unpublished-,300,CM,
XX,INA:bbs.intaa.net,IBN I still get a connect OK on both IPv4 and
IPv6, with: binkd/1.1a-115/386BSD ?
MvdV> Same here, still connects. So I wonder why it was removed. It was a relatively
MvdV> new node. Just a few weeks old.
I've already asked the Host...
Bye, Wilfred.
--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)
From Ivan Zelenyi@2:50/86.1 to Michiel van der Vlist on Fri Apr 17 06:53:40 2026
Hello, Michiel van der Vlist.
On 07.04.2026 16:31 you wrote:
I think I will just forget it like I actually did many years ago
when providers stopt accepting raw SMTP. Installing my own local
mail server just for this purpose is too much. I never was
enthousiastic about Fido over e-mail anyway. So I will indeed just
forget it. For me this function of Fmail is unusable.
Does Fmail support SSL/TLS?
I use a script to read ?lo-files (with hex number of my link) and then send packets using mutt+msmtp (with SSL).
--
With best regards,
Ivan Zelenyi
--- Hotdoged/2.13.5/Android
* Origin: Yggdrasil mesh point at HUAWEI EVE-LX9N (2:50/86.1)
From Michiel van der Vlist@2:280/5555 to Ivan Zelenyi on Fri Apr 17 09:13:41 2026
Hello Ivan,
On Friday April 17 2026 06:53, you wrote to me:
I think I will just forget it like I actually did many years ago
when providers stopt accepting raw SMTP. Installing my own local
mail server just for this purpose is too much. I never was
enthousiastic about Fido over e-mail anyway. So I will indeed
just forget it. For me this function of Fmail is unusable.
Does Fmail support SSL/TLS?
No.
I use a script to read ?lo-files (with hex number of my link) and then send packets using mutt+msmtp (with SSL).
That would be the better aproach. If you wish to support Fido Over E-mail...
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)
From Wilfred van Velzen@2:280/464 to All on Fri Apr 17 12:19:20 2026
Hi All,
New node in net 280: ,1043,Falcon_BBS,Boxtel,Michel_van_Osenbruggen,-Unpublished-,300,CM,XX,IBN:fido.falconbbs.nl
I get: Host fido.falconbbs.nl not found: 3(NXDOMAIN)
But on 'falconbbs.nl' I get a connect with: BinkIT/2.42,JSBinkP/5,sbbs3.21f/Linux. So either the IBN: or the host name needs to be fixed.
The single node Region 93 is on Hold. I indeed get a 'Connection refused' when testing this system.
Bye, Wilfred.
--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Fri Apr 17 12:19:49 2026
Hi All,
On 2026-04-10 12:59:39, I wrote to you:
New node in net 229: ,114,Va2rfc_BBS,Les_Mechins_QC,Richard_Murray,-Unpublished-,300,CM,IN A:va2rfc.photorm.net,IBN
Host va2rfc.photorm.net not found: 3(NXDOMAIN)
Same result but on 'photorm.net' I get a connect with Mystic/1.12A49. So either the INA: or the host name needs to be fixed.
Node in net 712 was removed: ,730,bbs.intaa.net,Tokyo_Japan,Yoshito_Uchiyama,-Unpublished-,300,CM, XX,INA:bbs.intaa.net,IBN
I still get a connect OK on both IPv4 and IPv6,
with: binkd/1.1a-115/386BSD ?
This node is back in the nodelist.
Bye, Wilfred.
--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)
From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Fri Apr 17 13:35:58 2026
Hello Wilfred,
On Friday April 17 2026 12:19, you wrote to All:
New node in net 280:
a returning node.
,1043,Falcon_BBS,Boxtel,Michel_van_Osenbruggen,-Unpublished-,300,CM,XX ,IBN:fido.falconbbs.nl I get: Host fido.falconbbs.nl not found: 3(NXDOMAIN)
Try bbs.falconbbs.nl
But on 'falconbbs.nl' I get a connect with: BinkIT/2.42,JSBinkP/5,sbbs3.21f/Linux.
IPv4. on bbs.falconbbs.nl you get an IPv6 connect.
So either the IBN: or the host name needs to be fixed.
Yep.
The single node Region 93 is on Hold. I indeed get a 'Connection
refused' when testing this system.
So RIP R93.
It seems Fernando is cleaning out the dead wood in Z4.
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)
From Wilfred van Velzen@2:280/464 to Michiel van der Vlist on Fri Apr 17 14:31:39 2026
Hi Michiel,
On 2026-04-17 13:35:58, you wrote to me:
New node in net 280:
MvdV> a returning node.
,1043,Falcon_BBS,Boxtel,Michel_van_Osenbruggen,-Unpublished-,300,CM,XX
,IBN:fido.falconbbs.nl I get: Host fido.falconbbs.nl not found:
3(NXDOMAIN)
MvdV> Try bbs.falconbbs.nl
Doesn't make much difference:
# host falconbbs.nl
falconbbs.nl has address 87.251.38.7
falconbbs.nl mail is handled by 200 connect.virtiso.nl.
falconbbs.nl mail is handled by 100 mx-1.virtiso.nl.
# host bbs.falconbbs.nl
bbs.falconbbs.nl has address 87.251.38.7
bbs.falconbbs.nl has IPv6 address 2001:7b8:622:103:87:251:38:7
Except for IPv6. But I don't get an IPv6 binkp connection...
But on 'falconbbs.nl' I get a connect with:
BinkIT/2.42,JSBinkP/5,sbbs3.21f/Linux.
MvdV> IPv4. on bbs.falconbbs.nl you get an IPv6 connect.
Not at the moment.
The single node Region 93 is on Hold. I indeed get a 'Connection
refused' when testing this system.
MvdV> So RIP R93.
That 1 node Region wasn't really necessary in the first place.
MvdV> It seems Fernando is cleaning out the dead wood in Z4.
And that's a good thing! ;-)
Bye, Wilfred.
--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)
From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Fri Apr 17 15:00:07 2026
Hello Wilfred,
On Friday April 17 2026 14:31, you wrote to me:
MvdV>> Try bbs.falconbbs.nl
Doesn't make much difference:
# host falconbbs.nl
falconbbs.nl has address 87.251.38.7
falconbbs.nl mail is handled by 200 connect.virtiso.nl.
falconbbs.nl mail is handled by 100 mx-1.virtiso.nl.
# host bbs.falconbbs.nl
bbs.falconbbs.nl has address 87.251.38.7
bbs.falconbbs.nl has IPv6 address 2001:7b8:622:103:87:251:38:7
Except for IPv6. But I don't get an IPv6 binkp connection...
But on 'falconbbs.nl' I get a connect with:
BinkIT/2.42,JSBinkP/5,sbbs3.21f/Linux.
MvdV>> IPv4. on bbs.falconbbs.nl you get an IPv6 connect.
Not at the moment.
He is probably still tuning. I get an IPv6 connect at bbs.falconbbs.nl.
The single node Region 93 is on Hold. I indeed get a 'Connection
refused' when testing this system.
MvdV>> So RIP R93.
That 1 node Region wasn't really necessary in the first place.
MvdV>> It seems Fernando is cleaning out the dead wood in Z4.
And that's a good thing! ;-)
+1
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)
From Wilfred van Velzen@2:280/464 to Michiel van der Vlist on Fri Apr 17 17:34:13 2026
Hi Michiel,
On 2026-04-17 15:00:07, you wrote to me:
MvdV>>> on bbs.falconbbs.nl you get an IPv6 connect.
Not at the moment.
MvdV> He is probably still tuning. I get an IPv6 connect at bbs.falconbbs.nl.
Me too, but you have to be really patient. I just timed a first response time, after starting the connection, of 2 minutes and 10 seconds...
Bye, Wilfred.
--- FMail-lnx64 2.3.2.6-B20251227
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Fri Apr 24 12:51:47 2026
Hi All,
New node in net 123: ,1256,Legends_of_Yesteryear,Huntsville_AL_USA,Dallas_Vinson,-Unpublished-,300,CM,INA:furmenservices.net,IBN
Connect with: Mystic/1.12A48, but 'No such AKA' result. Node had 1:123/256 configured as AKA.
New node in net 3636: ,62,The_Last_Telegraph_Office,Madison_NC_USA,David_Dalton,-Unpublished-,300,INA:bbs.acornabbey.us,CM,IBN
Connect with: binkd/1.1a-115/Linux
New node in net 246: ,1011,JebuSoft,Spiegelberg,Jens_Busch,-Unpublished-,300,CM,MO,XA,INA:bbs.dev42.com,IBN
Host bbs.dev42.com not found: 2(SERVFAIL)
Bye, Wilfred.
--- FMail-lnx64 2.3.3.1-B20260417
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Fri Apr 24 12:55:11 2026
Hi All,
On 2026-04-17 12:19:20, I wrote to you:
New node in net 280: ,1043,Falcon_BBS,Boxtel,Michel_van_Osenbruggen,-Unpublished-,300,CM, XX,IBN:fido.falconbbs.nl
I get: Host fido.falconbbs.nl not found: 3(NXDOMAIN)
The IBN: for this node was changed to bbs.falconbbs.nl. Both the old and new host name now correctly resolve.
XX flag should be XW though. Because Synchronet's freqit currently doesn't support Wazoo update requests.
Bye, Wilfred.
--- FMail-lnx64 2.3.3.1-B20260417
* Origin: NPC Station (2:280/464)
From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Fri Apr 24 13:33:28 2026
Hello Wilfred,
On Friday April 24 2026 12:51, you wrote to All:
New node in net 123: ,1256,Legends_of_Yesteryear,Huntsville_AL_USA,Dallas_Vinson,-Unpublish ed-,300,CM,INA:furmenservices.net,IBN Connect with: Mystic/1.12A48,
but 'No such AKA' result. Node had 1:123/256 configured as AKA.
Confirmed.
New node in net 3636: ,62,The_Last_Telegraph_Office,Madison_NC_USA,David_Dalton,-Unpublished -,300,INA:bbs.acornabbey.us,CM,IBN Connect with: binkd/1.1a-115/Linux
1:3634/62 works better.
^
New node in net 246: ,1011,JebuSoft,Spiegelberg,Jens_Busch,-Unpublished-,300,CM,MO,XA,INA:b bs.dev42.com,IBN Host bbs.dev42.com not found: 2(SERVFAIL)
Confirmed.
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)
From Wilfred van Velzen@2:280/464 to Michiel van der Vlist on Fri Apr 24 14:10:15 2026
Hi Michiel,
On 2026-04-24 13:33:28, you wrote to me:
New node in net 3636:
,62,The_Last_Telegraph_Office,Madison_NC_USA,David_Dalton,-Unpublishe
d-,300,INA:bbs.acornabbey.us,CM,IBN
Connect with: binkd/1.1a-115/Linux
MvdV> 1:3634/62 works better.
MvdV> ^
Sorry, typo... ;-)
Bye, Wilfred.
--- FMail-lnx64 2.3.3.1-B20260417
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Fri May 1 12:05:32 2026
Hi All,
Node 1:261/20 got the XW flag added. But I don't think filerequests are working at this node:
+ 01 May 11:20:14 [22889] call to 1:261/20@fidonet
01 May 11:20:14 [22889] trying brinkbbs.org [69.201.5.244]...
01 May 11:20:14 [22889] connected
+ 01 May 11:20:14 [22889] outgoing session with brinkbbs.org:24554 [69.201.5.244]
- 01 May 11:20:15 [22889] SYS Over The Brink BBS
- 01 May 11:20:15 [22889] ZYZ Robert Wolfe
- 01 May 11:20:15 [22889] LOC Niagara Falls, NY USA
- 01 May 11:20:15 [22889] VER PxOnline/10.0b22 binkp/1.1
? 01 May 11:20:15 [22889] Cannot find domain for zone 1, assuming 'fidonet'
+ 01 May 11:20:15 [22889] addr: 1:261/20@fidonet
+ 01 May 11:20:15 [22889] addr: 99:1/6@pxnet (n/a or busy)
? 01 May 11:20:15 [22889] Cannot find domain for zone 719, assuming 'fidonet'
+ 01 May 11:20:15 [22889] addr: 719:550/12@fidonet
+ 01 May 11:20:15 [22889] addr: 46:10/125@agoranet (n/a or busy)
+ 01 May 11:20:15 [22889] addr: 21:5/105@fsxnet (n/a or busy)
+ 01 May 11:20:15 [22889] addr: 86:100/14@nixnet (n/a or busy)
+ 01 May 11:20:15 [22889] addr: 618:100/14@micronet (n/a or busy)
+ 01 May 11:20:15 [22889] sending /home/fido/outbound.001/01050014.req as decdfa41.req (9)
+ 01 May 11:20:15 [22889] sent: /home/fido/outbound.001/01050014.req (9, 9.00 CPS, 1:261/20@fidonet)
? 01 May 11:20:15 [22889] recv: connection closed by foreign host
+ 01 May 11:20:15 [22889] holding 1:261/20@fidonet (2026/05/01 12:20:15)
+ 01 May 11:20:15 [22889] done (to 1:261/20@fidonet, failed, S/R: 1/0 (9/0 bytes))
01 May 11:20:15 [22889] restoring poll with `f' flavour
01 May 11:20:15 [22889] session closed, quitting...
Node was removed in net 261: Pvt,1466,Owls_Anchor,Columbia_MD,Dale_Shipp,-Unpublished-,9600,XX,MO
Node 1:340/1101 got the XW flag added. But there is a problem delivering the .req file:
+ 01 May 11:50:15 [24974] call to 1:340/1101@fidonet
01 May 11:50:15 [24974] trying shsbbs.net [174.27.202.232]...
01 May 11:50:15 [24974] connected
+ 01 May 11:50:15 [24974] outgoing session with shsbbs.net:24554 [174.27.202.232]
- 01 May 11:50:15 [24974] OPT CRAM-MD5-8f5fd27c040d5899abfe611b51b7e4ee
+ 01 May 11:50:15 [24974] Remote requests MD mode
- 01 May 11:50:15 [24974] SYS Shurato's Heavenly Sphere
- 01 May 11:50:15 [24974] ZYZ Martin Kazmaier
- 01 May 11:50:15 [24974] LOC Boise, ID USA
- 01 May 11:50:15 [24974] NDL 115200,TCP,BINKP
- 01 May 11:50:15 [24974] TIME Fri, 1 May 2026 03:50:15 -0600
- 01 May 11:50:15 [24974] VER binkd/1.1a-115/Win32 binkp/1.1
+ 01 May 11:50:15 [24974] addr: 1:340/1101@fidonet
+ 01 May 11:50:15 [24974] addr: 10:100/55@Araknet (n/a or busy)
+ 01 May 11:50:15 [24974] addr: 21:2/148@fsxnet (n/a or busy)
+ 01 May 11:50:15 [24974] addr: 42:12/1@sfnet (n/a or busy)
+ 01 May 11:50:15 [24974] addr: 316:36/41@whispnet (n/a or busy)
+ 01 May 11:50:15 [24974] addr: 618:300/50@micronet (n/a or busy)
+ 01 May 11:50:15 [24974] addr: 1337:3/185@tqwnet (n/a or busy)
+ 01 May 11:50:15 [24974] addr: 911:1208/2@zeronet (n/a or busy)
+ 01 May 11:50:15 [24974] addr: 777:777/5@xleague (n/a or busy)
+ 01 May 11:50:15 [24974] addr: 954:300/2@hobbynet (n/a or busy)
+ 01 May 11:50:15 [24974] addr: 999:300/2@health (n/a or busy)
? 01 May 11:50:15 [24974] got M_BSY: No AKAs in common domains or all AKAs are busy
+ 01 May 11:50:15 [24974] holding 1:340/1101@fidonet (2026/05/01 12:50:15)
+ 01 May 11:50:15 [24974] done (to 1:340/1101@fidonet, failed, S/R: 0/0 (0/0 bytes))
01 May 11:50:15 [24974] session closed, quitting...
Node 2:2/0 and aka's have an updated IMI. Test was succesfull.
Down node 2:292/140 was removed.
POTS only node 2:5053/59 was put on Hold.
All nodes in net 633 were changed from IBN:<host name> to INA:<host name>,IBN form.
There was one typo made in this change: INA::bbs.tassiebob.com for node 420.
Bye, Wilfred.
--- FMail-lnx64 2.3.3.1-B20260417
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Fri May 1 11:58:42 2026
Hi All,
On 2026-04-24 12:51:47, I wrote to you:
New node in net 246: ,1011,JebuSoft,Spiegelberg,Jens_Busch,-Unpublished-,300,CM,MO,XA,INA: bbs.dev42.com,IBN
Host bbs.dev42.com not found: 2(SERVFAIL)
Host name for this node was fixed to bbs.devs42.com.
Connect OK with: Mystic/1.12A48
Bye, Wilfred.
--- FMail-lnx64 2.3.3.1-B20260417
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Fri May 1 11:59:29 2026
Hi All,
On 2026-04-24 12:55:11, I wrote to you:
New node in net 280:
,1043,Falcon_BBS,Boxtel,Michel_van_Osenbruggen,-Unpublished-,300,CM,
XX,IBN:fido.falconbbs.nl
XX flag should be XW though. Because Synchronet's freqit currently doesn't support Wazoo update requests.
This was fixed.
Bye, Wilfred.
--- FMail-lnx64 2.3.3.1-B20260417
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Fri May 8 12:08:44 2026
Hi All,
Nodes 228, 393, 395 and 6502 were removed from net 138.
This is the state of the remaining nodes in net 138:
1:138/0 bbs.retroarchive.org:24554 75.145.20.102 Ok.
1:138/142 bbs.retroarchive.org:24554 75.145.20.102 Ok.
1:138/391 216.211.176.87:24554 216.211.176.87 Error: Connection timed out
1:138/397 lunarout.synchro.net:24554 73.11.233.93 Ok.
New net in R50: Host,5051,Simbirsk_Net,Simbirsk_Russia,Vladimir_Isakov,-Unpublished-,300,CM,IBN,INA:fido.pdp11.ru
,44,Digital,Simbirsk,Vladimir_Isakov,-Unpublished-,300,IBN,INA:fido.pdp11.ru,U,NC,NPK
,45,Pluto_Station,Simbirsk,Andrey_Sokolov,-Unpublished-,300,IBN,INA:ftn.da-systems.ru
2:5051/0 fido.pdp11.ru:24554 5.188.163.102 No such AKA.
2:5051/44 fido.pdp11.ru:24554 5.188.163.102 Ok. binkd/1.1a-115/Linux
2:5051/45 ftn.da-systems.ru:24554 5.188.163.103 Ok. binkd/1.1a-115/Linux
Bye, Wilfred.
--- FMail-lnx64 2.3.3.1-B20260417
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Fri May 8 12:12:32 2026
Hi All,
On 2026-05-01 12:05:32, I wrote to you:
Node 1:261/20 got the XW flag added. But I don't think filerequests
are working at this node:
My binkd kept trying during the week. On wednesday it could deliver the .req file and got a .rst in response. So the XW flag is now correct.
Node 1:340/1101 got the XW flag added. But there is a problem
delivering the .req file:
+ 01 May 11:50:15 [24974] call to 1:340/1101@fidonet
? 01 May 11:50:15 [24974] got M_BSY: No AKAs in common domains or all AKAs are busy
Not resolved yet.
All nodes in net 633 were changed from IBN:<host name> to INA:<host name>,IBN form. There was one typo made in this change: INA::bbs.tassiebob.com for node 420.
The typo was fixed. No other changes in net 633.
Bye, Wilfred.
--- FMail-lnx64 2.3.3.1-B20260417
* Origin: NPC Station (2:280/464)
From Tommi Koivula@2:221/1.1 to Wilfred van Velzen on Fri May 8 14:00:20 2026
Hi Wilfred.
Node 1:340/1101 got the XW flag added. But there is a problem
delivering the .req file:
+ 01 May 11:50:15 [24974] call to 1:340/1101@fidonet
? 01 May 11:50:15 [24974] got M_BSY: No AKAs in common domains or
all AKAs are busy
Not resolved yet.
Freq processed, but it took 3 minutes.
=== Cut ===
08-May-2026 13.41.33 Connect To 174.27.150.38 #24554
08-May-2026 13.41.33 Establishing BinkP transfer protocol
08-May-2026 13.41.33 M_NUL : OPT CRAM-MD5-a34783718a6348327bb1bb5a4f27c0ee
08-May-2026 13.41.33 Station : Shurato's Heavenly Sphere
08-May-2026 13.41.33 Address : 1:340/1101 10:100/55 21:2/148 42:12/1 316:36/
08-May-2026 13.41.33 SysOp : Martin Kazmaier from Boise, ID USA
08-May-2026 13.41.33 Number : "shsbbs.net"
08-May-2026 13.41.33 Flags : 115200,TCP,BINKP
08-May-2026 13.41.33 Mailer : binkd/1.1a-115/Win32 binkp/1.1
08-May-2026 13.41.33 Time : Fri, 8 May 2026 04:41:34 -0600
08-May-2026 13.41.33 Non-password session
08-May-2026 13.41.33 M_NUL : OPT EXTCMD GZ BZ2
08-May-2026 13.41.33 Remote submitted insecure session
08-May-2026 13.41.33 Handshake time - 0 seconds
08-May-2026 13.41.33 Nothing for them
08-May-2026 13.41.33 Sending 'C:\bbs\bso\fido.001\0154044D.REQ' (7b)
08-May-2026 13.44.37 Sent deleted '0154044D.REQ'
08-May-2026 13.44.37 SEND: End of batch
08-May-2026 13.44.37 Receiving 'E62319FF.Pkt' (466b)
08-May-2026 13.44.37 Received 'C:\bbs\inbound\E62319FF.Pkt'
08-May-2026 13.44.37 Receiving 'allfiles.txt' (16,623,849b)
08-May-2026 13.45.27 332476 CPS, Received 'C:\bbs\inbound\allfiles.txt'
08-May-2026 13.45.28 RECE: End of batch
=== Cut ===
'Tommi
---
* Origin: FPoint One (2:221/1.1)
From Wilfred van Velzen@2:280/464 to Tommi Koivula on Fri May 8 13:19:09 2026
Hi Tommi,
On 2026-05-08 14:00:20, you wrote to me:
Node 1:340/1101 got the XW flag added. But there is a problem
delivering the .req file:
+ 01 May 11:50:15 [24974] call to 1:340/1101@fidonet
? 01 May 11:50:15 [24974] got M_BSY: No AKAs in common domains or
all AKAs are busy
Not resolved yet.
Freq processed, but it took 3 minutes.
I still get:
+ 08 May 12:55:51 [4149] call to 1:340/1101@fidonet
08 May 12:55:51 [4149] trying shsbbs.net [174.27.150.38]...
08 May 12:55:51 [4149] connected
+ 08 May 12:55:51 [4149] outgoing session with shsbbs.net:24554 [174.27.150.38] - 08 May 12:55:51 [4149] OPT CRAM-MD5-603ba0218b37ddf5f7447c4d4f50acee
+ 08 May 12:55:51 [4149] Remote requests MD mode
- 08 May 12:55:51 [4149] SYS Shurato's Heavenly Sphere
- 08 May 12:55:51 [4149] ZYZ Martin Kazmaier
- 08 May 12:55:51 [4149] LOC Boise, ID USA
- 08 May 12:55:51 [4149] NDL 115200,TCP,BINKP
- 08 May 12:55:51 [4149] TIME Fri, 8 May 2026 04:55:52 -0600
- 08 May 12:55:51 [4149] VER binkd/1.1a-115/Win32 binkp/1.1
+ 08 May 12:55:51 [4149] addr: 1:340/1101@fidonet
+ 08 May 12:55:51 [4149] addr: 10:100/55@Araknet (n/a or busy)
+ 08 May 12:55:51 [4149] addr: 21:2/148@fsxnet (n/a or busy)
+ 08 May 12:55:51 [4149] addr: 42:12/1@sfnet (n/a or busy)
+ 08 May 12:55:51 [4149] addr: 316:36/41@whispnet (n/a or busy)
+ 08 May 12:55:51 [4149] addr: 618:300/50@micronet (n/a or busy)
+ 08 May 12:55:51 [4149] addr: 1337:3/185@tqwnet (n/a or busy)
+ 08 May 12:55:51 [4149] addr: 911:1208/2@zeronet (n/a or busy)
+ 08 May 12:55:51 [4149] addr: 777:777/5@xleague (n/a or busy)
+ 08 May 12:55:51 [4149] addr: 954:300/2@hobbynet (n/a or busy)
+ 08 May 12:55:51 [4149] addr: 999:300/2@health (n/a or busy)
? 08 May 12:55:51 [4149] got M_BSY: No AKAs in common domains or all AKAs are busy
+ 08 May 12:55:51 [4149] holding 1:340/1101@fidonet (2026/05/08 13:55:51)
+ 08 May 12:55:51 [4149] done (to 1:340/1101@fidonet, failed, S/R: 0/0 (0/0 bytes))
08 May 12:55:51 [4149] session closed, quitting...
Bye, Wilfred.
--- FMail-lnx64 2.3.3.1-B20260417
* Origin: NPC Station (2:280/464)
From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Fri May 8 14:31:44 2026
Hello Wilfred,
On Friday May 08 2026 12:08, you wrote to All:
2:5051/0 fido.pdp11.ru:24554 5.188.163.102 No such AKA. 2:5051/44 fido.pdp11.ru:24554 5.188.163.102 Ok.
PDP11 ? He wouldn't really run Fido om a PDP11 would he? ;-)
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)
From Wilfred van Velzen@2:280/464 to Michiel van der Vlist on Fri May 8 17:29:24 2026
Hi Michiel,
On 2026-05-08 14:31:44, you wrote to me:
2:5051/0 fido.pdp11.ru:24554 5.188.163.102 No such AKA.
2:5051/44 fido.pdp11.ru:24554 5.188.163.102 Ok.
MvdV> PDP11 ? He wouldn't really run Fido om a PDP11 would he? ;-)
You will have to ask the sysop. ;-)
Bye, Wilfred.
--- FMail-lnx64 2.3.3.1-B20260417
* Origin: NPC Station (2:280/464)
From Kurt Weiske@1:218/700 to Michiel van der Vlist on Fri May 8 10:16:15 2026
Michiel van der Vlist wrote to Wilfred van Velzen <=-
2:5051/0 fido.pdp11.ru:24554 5.188.163.102 No such AKA. 2:5051/44 fido.pdp11.ru:24554 5.188.163.102 Ok.
PDP11 ? He wouldn't really run Fido om a PDP11 would he? ;-)
Remember the usenet posts from kremvax.su and kgbvax.su?
From Michiel van der Vlist@2:280/5555 to Kurt Weiske on Sat May 9 03:13:37 2026
Hello Kurt,
On Friday May 08 2026 10:16, you wrote to me:
2:5051/0 fido.pdp11.ru:24554 5.188.163.102 No such
AKA.
2:5051/44 fido.pdp11.ru:24554 5.188.163.102 Ok.
PDP11 ? He wouldn't really run Fido om a PDP11 would he? ;-)
Remember the usenet posts from kremvax.su and kgbvax.su?
Nope, never heard of it. Never cared much about usenet.
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)
From Kurt Weiske@1:218/700 to Michiel van der Vlist on Sat May 9 11:29:53 2026
Michiel van der Vlist wrote to Kurt Weiske <=-
Remember the usenet posts from kremvax.su and kgbvax.su?
Nope, never heard of it. Never cared much about usenet.
It was an april fools' post during the cold war.
... Find a safe part and use it as an anchor
--- MultiMail/Win v0.52
* Origin: http://realitycheckbbs.org | tomorrow's retro tech (1:218/700)
From Michiel van der Vlist@2:280/5555 to Kurt Weiske on Sat May 9 21:32:21 2026
Hello Kurt,
On Saturday May 09 2026 11:29, you wrote to me:
Michiel van der Vlist wrote to Kurt Weiske <=-
Remember the usenet posts from kremvax.su and kgbvax.su?
Nope, never heard of it. Never cared much about usenet.
It was an april fools' post during the cold war.
OK....
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)
From Wilfred van Velzen@2:280/464 to All on Fri May 15 12:14:53 2026
Hi All,
On 2026-05-08 12:08:44, I wrote to you:
This is the state of the remaining nodes in net 138:
1:138/391 216.211.176.87:24554 216.211.176.87 Error:
Connection timed out
No change here.
2:5051/0 fido.pdp11.ru:24554 5.188.163.102 No such AKA.
No change here.
Bye, Wilfred.
--- FMail-lnx64 2.3.3.1-B20260417
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Fri May 15 12:22:12 2026
Hi All,
New node in net 135: ,382,Tomcat_BBS,Titusville_FL,Ricky_DeLuco,-Unpublished-,300,CM,INA:tomcatbbs.ddns.net,IBN
Connect OK with: Mystic/1.12A48
New node in net 3634: ,59,Shift_Bits_BBS,Gastonia_NC_USA,Stacy_Caudle,-Unpublished-,300,INA:bbs.shift-bits.com,CM,IBN
Connect OK with: binkd/1.1a-115/Linux
Node 2:201/127 has been marked as Down. I get a connect OK on both IPv6 and IPv4 ?
Bye, Wilfred.
--- FMail-lnx64 2.3.3.1-B20260417
* Origin: NPC Station (2:280/464)
From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Sun May 17 11:56:41 2026
Hello Wilfred,
On Friday May 15 2026 12:22, you wrote to All:
Node 2:201/127 has been marked as Down. I get a connect OK on both
IPv6 and IPv4 ?
Same here. I get a connection with binkd/1.1a-115/Linux binkp/1.1.
So maybe the Down is an error?
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)
From Tommi Koivula@2:221/360 to Michiel van der Vlist on Sun May 17 20:18:22 2026
On Sun, 17 May 2026 08:56:40 +0200 Michiel van der Vlist wrote:
MVDV> WV> Node 2:201/127 has been marked as Down. I get a connect OK
MVDV> WV> on both IPv6 and IPv4 ?
MVDV>
MVDV> Same here. I get a connection with binkd/1.1a-115/Linux binkp/1.1.
MVDV>
MVDV> So maybe the Down is an error?
As for some reason he was not in my IPv6 list, I flagged him as a "new one". I did indeed check his reachability but not until after it was pointed out that he was listed as Down.
Tnx fr the feed back.
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Nodelist Police Station (2:280/5555)
From Ward Dossche@2:292/854 to Tommi Koivula on Mon May 18 08:59:01 2026
From Wilfred van Velzen@2:280/464 to All on Fri May 22 12:30:37 2026
Hi All,
New node in net 114: ,20,Imperial_Scout_Service,Chino_Valley_AZ,Jeff_Brissette,-Unpublished-,300,CM,INA:iiss.bluesunconsulting.com,IBN
Connect OK, with: Mystic/1.12A48
Down node 2:5022/145 was removed.
Bye, Wilfred.
--- FMail-lnx64 2.3.4.1-B20260520
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Fri May 22 12:34:51 2026
Hi All,
On 2026-05-15 12:22:12, I wrote to you:
Node 2:201/127 has been marked as Down. I get a connect OK on both
IPv6 and IPv4 ?
No change here. (Still marked Down, and still connectable)
Bye, Wilfred.
--- FMail-lnx64 2.3.4.1-B20260520
* Origin: NPC Station (2:280/464)
From Wilfred van Velzen@2:280/464 to All on Fri May 29 11:57:45 2026
Hi All,
New node in net 3634: ,63,North_River_BBS,Shawboro_NC_USA,Ed_Wentworth,-Unpublished-,300,INA:bbs.nrbbs.org,CM,IBN
Connect OK with: BinkIT/2.42,JSBinkP/4,sbbs3.21e/Win32
New node in net 5083: ,87,Vitos_Station,Astana_Kazakhstan,Vitaliy_Byalik,-Unpublished-,300,XX,MO,CM,IBN,INA:r1cbw.ru
Connect OK with: binkd/0.9.9-stable/Win32
Bye, Wilfred.
--- FMail-lnx64 2.3.4.1-B20260520
* Origin: NPC Station (2:280/464)
Who's Online
Recent Visitors
Godfather
Thu May 21 09:34:48 2026
from
Underground, Us
via
Telnet
Gullytaucher
Sun Feb 22 07:08:12 2026
from
Traunreut, Germany
via
Telnet
Gullytaucher
Sun Feb 22 06:46:12 2026
from
Traunreut, Germany
via
Telnet
Bishop
Sat Feb 14 20:00:36 2026
from
Philadelphia
via
Telnet