2:280/1049 thecoastbbs.nl:24554
2001:9e0:8547:7c01:ac0:77:8500:100 No such AKA.
2:280/2060 fidonet.aroundmyroom.com:24554 2001:1c00:c204:4300:f1d0:2:280:2060 No such AKA.
I tested the dutch nodes in your list.
On 2026-02-04 17:18:50, you wrote to Michiel van der Vlist:
2:280/1049 thecoastbbs.nl:24554
2001:9e0:8547:7c01:ac0:77:8500:100 No such AKA.
I get an OK for this node!?
Calling '2:280/1049'. Call time: '0000-2400' UTC.
thecoastbbs.nl, 24554
Calling 2:280/1049 (2001:9e0:8547:7c01:ac0:77:8500:100:24554)
address: 2:280/1049@fidonet
2001:9e0:8547:7c01:ac0:77:8500:100 - Ok.
So?
2:280/2060 fidonet.aroundmyroom.com:24554
2001:1c00:c204:4300:f1d0:2:280:2060 No such AKA.
Indeed point 2:280/2060.6 is answering on this IPv6 address! And not the node...
2:280/1049 thecoastbbs.nl:24554
2001:9e0:8547:7c01:ac0:77:8500:100 No such AKA.
I get an OK for this node!?
Calling '2:280/1049'. Call time: '0000-2400' UTC.
thecoastbbs.nl, 24554
Calling 2:280/1049 (2001:9e0:8547:7c01:ac0:77:8500:100:24554)
address: 2:280/1049@fidonet
2001:9e0:8547:7c01:ac0:77:8500:100 - Ok.
So?
Now I got "Ok" too. Hm.
2:280/2060 fidonet.aroundmyroom.com:24554
2001:1c00:c204:4300:f1d0:2:280:2060 No such AKA.
Indeed point 2:280/2060.6 is answering on this IPv6 address! And not the
node...
Does he know about it?
And what about "connection refused" and "no route to host" results?
So I tested your full list. I get a few Ok's, and a few 'No such
AKA''s:
I have dedicted "AKA Mismatch" report:
https://nodelist.fidonet.cc/analytics/aka-mismatch?days=30&limit=1000& includeZero=true
So I tested your full list. I get a few Ok's, and a few 'No such
AKA''s:
I have dedicted "AKA Mismatch" report:
https://nodelist.fidonet.cc/analytics/aka-mismatch?days=30&limit=1000&includeZ
ero=true
Note that in the particular case of 280/2060, the AKA mismatch only
occurs when connecting via IPv6. There is no problem when connecting
via IPv4. So you may have to split it up and test both protocols.
And you might want to look into these: 2:5058/108 2:201/111 2:5066/35
1:104/0 binkp.pharcyde.org:24554 2603:6000:dc00:44:f1d0:1:154:10 No
such AKA.
1:114/0 binkp.pharcyde.org:24554 2603:6000:dc00:44:f1d0:1:154:10 No
such AKA.
*List of IPv6 nodes
List of IPv6 nodes
By Michiel van der Vlist, 2:280/5555
Updated 29 Jan 2026
2:280/2060 fidonet.aroundmyroom.com:24554
2001:1c00:c204:4300:f1d0:2:280:2060 No such AKA.
Indeed point 2:280/2060.6 is answering on this IPv6 address! And not
the node...
Does he know about it?
If he doesn't respond here, I'll let him know. ;-)
Note that in the particular case of 280/2060, the AKA mismatch
only occurs when connecting via IPv6. There is no problem when
connecting via IPv4. So you may have to split it up and test both
protocols.
Wow, that's amazing! I never thought someone would provide different addresses on ipv4 and ipv6. It was really beyond my imagination.
New tests will handle such cases: I was testing both ipv4 and ipv6,
but saved node information only once (ipv6 preferred). This is
actually a good case, because now I am getting node information:
binkp ipv6
binkp ipv4
ifcico ipv6
ifcico ipv4
modem ifcico
and more to come..
If it's complicated, I am having a good time testing and fixing it :)
And what about "connection refused" and "no route to host" results?
So I tested your full list. I get a few Ok's, and a few 'No such AKA''s:
1:135/220 bbs.archaicbinary.net:24554 2001:470:1d:4aa::2
Ok.
2:222/2 bbbs.net:24554 2a10:a5c0:24f:f000::1 Ok.
2:280/1049 thecoastbbs.nl:24554
2001:9e0:8547:7c01:ac0:77:8500:100 Ok.
The others don't get a connect here either. Does this answer your question? ;-)
1:135/220 bbs.archaicbinary.net:24554 2001:470:1d:4aa::2
Ok.
Strange.
[14:38:05 brorabbit logs]$ callip -c ~/etc/callip.conf -b -f 1:135/220
You have actual version.
Parsing nodelist file /home/fido/nodelist/nodelist.367
Nodelist for Thursday, February 5, 2026 -- Day number 036 parsed, 949 IP-nodes
processed (0.052 sec) Calling '1:135/220'. Call time: '0000-2400' UTC. Now is:
1139 UTC. bbs.archaicbinary.net, 24554 Calling 1:135/220 (2001:470:1d:4aa::2:24554) error (Connection timed out) Calling 1:135/220 (167.114.108.156:24554) error (Connection timed out)
I've created a report that produces the same list, but based on
real-life tests (check "Download as Text" button):
https://nodelist.fidonet.cc/analytics/ipv6-node-list
Many Russian nodes got a 6UNS status. This is because the Russian
Internet is now heavily filtered and connections from Oracle Cloud
fail during drone attacks or when new anti VPN filters are applied by
the Russian censorship authorities.
I could test them from Russia, but I think that wouldn't be accurate
at all. It's better to show that those nodes are actually unstable for other FidoNet nodes.
1:104/0 binkp.pharcyde.org:24554 2603:6000:dc00:44:f1d0:1:154:10 No
such AKA.
1:114/0 binkp.pharcyde.org:24554 2603:6000:dc00:44:f1d0:1:154:10 No
such AKA.
These should be fixed.
Just "interim" NC numbers I never paid much attention to and never
added to binkd. The 2-3 nodes in each have no care
in the world to be NC, and don't want to change their node number.
C'est la vie.
Thanks for the report, though!
1:104/0 binkp.pharcyde.org:24554 2603:6000:dc00:44:f1d0:1:154:10
No such AKA.
1:114/0 binkp.pharcyde.org:24554 2603:6000:dc00:44:f1d0:1:154:10
No such AKA.
These should be fixed.
It MUST be fixed.
It doesn't need to be changed, it just needs to be added. It's
assumed that this isn't a particularly technically challenging task
for the network coordinator.
15 3:633/280 Stephen Walsh Native AusNetServers f
20 3:633/281 Stephen Walsh Native Internode
20 3:633/281 Stephen Walsh Native Leaptel IO
Tnx. The list has been updated.
I assume the IO for 281 is because you are running a port proxy to
make the Amiga accept IPv6?
*List of IPv6 nodes
List of IPv6 nodes
By Michiel van der Vlist, 2:280/5555
Updated 17 May 2026
Node Nr. Sysop Type Provider Remark
Hello Sean,
On Friday May 22 2026 22:05, you wrote to me:
Just added my ipv6 setup, should be working, tested a telnet from
a
remote pc to the ipv6 binkd and got the reply
2:263/1 Sean Rima f Sky.com
+ 03:16 [4004] call to 2:263/1@fidonet
03:16 [4004] trying binkd.rima.ie [2a06:5900:8194:100:acb:a059:6e85:1ded]...
? 03:16 [4004] connection to 2:263/1@fidonet failed: {W32 API
error 10060} Connection timed out
03:16 [4004] trying binkd.rima.ie [51.182.63.136]...
? 03:17 [4004] connection to 2:263/1@fidonet failed: {W32 API
error 10060} Connection timed out
03:17 [3216] the queue is empty, quitting...
Looks like you still have to configure the firewall and port
forwarding...
+ 03:16 [4004] call to 2:263/1@fidonet
03:16 [4004] trying binkd.rima.ie
[2a06:5900:8194:100:acb:a059:6e85:1ded]... ? 03:16 [4004]
connection
to 2:263/1@fidonet failed: {W32 API
error 10060} Connection timed out
03:16 [4004] trying binkd.rima.ie [51.182.63.136]...
? 03:17 [4004] connection to 2:263/1@fidonet failed: {W32 API
error 10060} Connection timed out
03:17 [3216] the queue is empty, quitting...
Looks like you still have to configure the firewall and port
forwarding...
Can you make a poll to my system so that we can see if outgoing IPv6
workd for you?
Can you make a poll to my system so that we can see if outgoing
IPv6 workd for you?
I can poll Ward and Kim in ipv6, but here goes
23 May 18:30:59 [68041] trying f5555.n280.z2.binkp.net[..]
[2001:4c3c:7d02:ff00:f1d0:2:280:5555]... 23 May 18:30:59 [68041]
connected + 23 May 18:30:59 [68041] outgoing session with
f5555.n280.z2.binkp.net:24554
[2001:4c3c:7d02:ff00:f1d0:2:280:5555] - 23 May 18:30:59 [68041]
OPT CRAM-MD5-f985e9a5aa2a24b81a88bb80f1ac7bee
Check:
+ 23 May 19:31:17 [3088] incoming session with
2a06:5900:8194:100:acb:a059:6e85:1ded
- 23 May 19:31:17 [3088] SYS There Can Only Be 1
- 23 May 19:31:17 [3088] ZYZ Sean Rima
- 23 May 19:31:17 [3088] LOC Letterfrack, Ireland
- 23 May 19:31:17 [3088] NDL 115200,TCP,BINKP
- 23 May 19:31:17 [3088] TIME Sat, 23 May 2026 18:30:59 +0100
- 23 May 19:31:17 [3088] VER binkd/1.1a-115/Linux binkp/1.1
So I will list you in the IPv6 list as "OO" (Outgoing Only) for the
time being.
Check:
+ 23 May 19:31:17 [3088] incoming session with
2a06:5900:8194:100:acb:a059:6e85:1ded
- 23 May 19:31:17 [3088] SYS There Can Only Be 1
- 23 May 19:31:17 [3088] ZYZ Sean Rima
- 23 May 19:31:17 [3088] LOC Letterfrack, Ireland
- 23 May 19:31:17 [3088] NDL 115200,TCP,BINKP
- 23 May 19:31:17 [3088] TIME Sat, 23 May 2026 18:30:59 +0100
- 23 May 19:31:17 [3088] VER binkd/1.1a-115/Linux binkp/1.1
So I will list you in the IPv6 list as "OO" (Outgoing Only) for the
time being.
Should be in and out now :)
Hi Sean,
On 2026-05-26 11:46:31, you wrote to Michiel van der Vlist:
Should be in and out now :)
Not yet, just moments ago...
Nodelist for Tuesday, May 26, 2026 -- Day number 146 parsed, 955
IP-nodes processed (0.013 sec) Calling '2:263/1'. Call time:
'0000-2400' UTC. Now is: 1102 UTC.
bbs.rima-iot.eu, 24554
Calling 2:263/1 (2a06:5900:8194:100:acb:a059:6e85:1ded:24554)
error (Connection timed out)
Calling 2:263/1 (51.182.63.136:24554)
error (No route to host)
+ 23 May 19:31:17 [3088] incoming session with
2a06:5900:8194:100:acb:a059:6e85:1ded
- 23 May 19:31:17 [3088] SYS There Can Only Be 1
- 23 May 19:31:17 [3088] ZYZ Sean Rima
- 23 May 19:31:17 [3088] LOC Letterfrack, Ireland
- 23 May 19:31:17 [3088] NDL 115200,TCP,BINKP
- 23 May 19:31:17 [3088] TIME Sat, 23 May 2026 18:30:59 +0100
- 23 May 19:31:17 [3088] VER binkd/1.1a-115/Linux binkp/1.1
So I will list you in the IPv6 list as "OO" (Outgoing Only) for
the time being.
Should be in and out now :)
Alas, not yet:
+ 14:28 [3904] call to 2:263/1@fidonet
14:28 [3904] trying binkd.rima.ie [2a06:5900:8194:100:acb:a059:6e85:1ded]...
? 14:29 [3904] connection to 2:263/1@fidonet failed: {W32 API
error 10060} Connection timed out
14:29 [3904] trying binkd.rima.ie [51.182.63.136]...
? 14:29 [3904] connection to 2:263/1@fidonet failed: {W32 API
error 10060} Connection timed out
14:29 [3796] the queue is empty, quitting...
Nodelist for Tuesday, May 26, 2026 -- Day number 146 parsed, 955
IP-nodes processed (0.013 sec) Calling '2:263/1'. Call time:
'0000-2400' UTC. Now is: 1102 UTC.
bbs.rima-iot.eu, 24554
Calling 2:263/1 (2a06:5900:8194:100:acb:a059:6e85:1ded:24554)
error (Connection timed out)
Calling 2:263/1 (51.182.63.136:24554)
error (No route to host)
I had rebooted the network which may explain that :)
Sean
I disabled the router firewall as mine is there anyway. Will have to investigate it
26 May 15:45:08 [2003] rc(3467)=0
- 26 May 15:45:13 [2003] incoming from 2a10:3781:5d5d:1:502:da7a:cc60:c396
Hi Sean,
On 2026-05-26 13:33:22, you wrote to me:
I had rebooted the network which may explain that :)
Sean
Should it be fixed now? Because it isn't...
Btw: Did you see my netmail about spamming the STATS area?
Hi Sean,
On 2026-05-26 15:47:08, you wrote to me:
I disabled the router firewall as mine is there anyway. Will have
to
investigate it
26 May 15:45:08 [2003] rc(3467)=0
- 26 May 15:45:13 [2003] incoming from
2a10:3781:5d5d:1:502:da7a:cc60:c396
It seems to be working now:
26 May 16:44:10 [28669] trying binkd.rima.ie [2a06:5900:8194:100:acb:a059:6e85:1ded]... 26 May 16:45:13 [28669] connected + 26 May 16:45:13 [28669] outgoing session with binkd.rima.ie:24554 [2a06:5900:8194:100:acb:a059:6e85:1ded] - 26 May 16:45:14 [28669] OPT CRAM-MD5-78625f2fdb13c472b8b848d3f56d87ee
Bye, Wilfred.
--- FMail-lnx64 2.3.4.1-B20260520
* Origin: FMail development HQ (2:280/464)
It seems to be working now:
Turned out I didn't need port forwarding but port triggering :)
ok, going to reboot after I send this, but should be ok
113 2:263/1 Sean Rima Naitive SKY-IE-BROADBAND OO
113 2:263/1 Sean Rima Naitive
SKY-IE-BROADBAND OO
I was checking something on the providers router and noticed that
the firewall settings had changed from what I set for ipv6. So I
switched them back and almost as soon as I did, I got an ipv6
incoming call
Yeah, it is working again:
+ 11:07 [3916] call to 2:263/1@fidonet
11:07 [3916] trying binkd.rima.ie [2a06:5900:8194:100:acb:a059:6e85:1ded]... 11:07 [3916] connected
+ 11:07 [3916] outgoing session with binkd.rima.ie:24554
[2a06:5900:8194:100:acb:a059:6e85:1ded]
- 11:07 [3916] OPT CRAM-MD5-3c88c17eaa1d8413a9e113adf61a1bee
+ 11:07 [3916] Remote requests MD mode
- 11:07 [3916] SYS There Can Only Be 1
- 11:07 [3916] ZYZ Sean Rima
- 11:07 [3916] LOC Letterfrack, Ireland
- 11:07 [3916] NDL 115200,TCP,BINKP
Shall I drop the "OO" in your listing?
I am ordering an Omada Fusion gateway to replace their router as
I don't like the fact that it is on the router for some settings
and on their app for others.
That is annoying indeed. Control should be in one place. We stay
tuned...
113 2:263/1 Sean Rima Naitive
SKY-IE-BROADBAND OO
I was checking something on the providers router and noticed that
the firewall settings had changed from what I set for ipv6. So I
switched them back and almost as soon as I did, I got an ipv6
incoming call
Yeah, it is working again:
+ 11:07 [3916] call to 2:263/1@fidonet
11:07 [3916] trying binkd.rima.ie [2a06:5900:8194:100:acb:a059:6e85:1ded]... 11:07 [3916] connected
+ 11:07 [3916] outgoing session with binkd.rima.ie:24554
[2a06:5900:8194:100:acb:a059:6e85:1ded]
- 11:07 [3916] OPT CRAM-MD5-3c88c17eaa1d8413a9e113adf61a1bee
+ 11:07 [3916] Remote requests MD mode
- 11:07 [3916] SYS There Can Only Be 1
- 11:07 [3916] ZYZ Sean Rima
- 11:07 [3916] LOC Letterfrack, Ireland
- 11:07 [3916] NDL 115200,TCP,BINKP
Shall I drop the "OO" in your listing?
Shall I drop the "OO" in your listing?
Leave it until I get a new gateway,
as for some reason, the ISPs router reset the firewall settings and stopped inbound ipv6 last night. Andthe Omada fusion gateway is not
going to work due to it only being SPF for inbound and only 1gbe for output
Will order a Ubiquiti one and start building a new network
as for some reason, the ISPs router reset the firewall settings
and stopped inbound ipv6 last night. Andthe Omada fusion gateway
is not going to work due to it only being SPF for inbound and
only 1gbe for output
Will order a Ubiquiti one and start building a new network
Good luck with upgrading your system. Let me know when you got it
working so we can update the listing.
113 2:263/1 Sean Rima Naitive SKY-IE-BROADBAND OO
Michiel van der Vlist wrote to Sean Rima <=-
113 2:263/1 Sean Rima Naitive SKY-IE-BROADBAND OO
Can you make me IO until BBBS can make outgoing calls. Have no
issues
now with the router sinbce the reset
OK, will do.
67 2:5020/736 Egor Glukhov Native RUWEB f
67 2:5020/736 Egor Glukhov Native RUWEB f
Replace it with 2:382/736 please. :-)
67 2:5020/736 Egor Glukhov Native RUWEB f
Replace it with 2:382/736 please. :-)Gladly.
Is your IPv6 ISP still RUWEB?
Can I request to have my system tested and see if it passes for IPv6
please?
Telnet: call.rofbbs.com:6800
SSH: call@call.rofbbs.com
Can I request to have my system tested and see if it passes
for IPv6 please?
Thanks for running the test, and sorry for sending you at the wrong target.
The correct address for mail is:
call.rofbbs.com port 24554 (IBN)
That resolves to my real endpoints on both protocols:
IPv4 68.169.145.190
IPv6 2605:8600:60:199d:aa5a:bfc6:5328:c881
Both answer on 24554 from where I can test, but that is from inside
my own network, so I would rather have your result than mine.
Would you mind trying once more against call.rofbbs.com?
While looking into this I also found my FidoNet nodelist entry is
out of date - it still lists INA:rofbbs.ddns.net,
which no longer resolves at all, plus an old location and phone number
and no IPV6 flag.
That would explain any node failing to reach me from the nodelist. I
am getting that corrected with my NC.
Thanks again for the help.
Hello Gary,
On 21 Sep 26 05:06, you wrote to me:
Thanks for running the test, and sorry for sending you at the wrong target.
[..]
The correct address for mail is:
call.rofbbs.com port 24554 (IBN)
OK, that's better.
+ 13:06 [2128] call to 1:154/50@fidonet
13:06 [2128] trying call.rofbbs.com
[2605:8600:60:199d:aa5a:bfc6:5328:c881]...
13:06 [2128] connected
+ 13:06 [2128] outgoing session with call.rofbbs.com:24554
[2605:8600:60:199d:aa5a:bfc6:5328:c881]
- 13:06 [2128] OPT CRAM-MD5-7d7b9984191ee4a8f2eec9404932c7ee
+ 13:06 [2128] Remote requests MD mode
- 13:06 [2128] SYS Reign of Fire BBS
- 13:06 [2128] ZYZ Gary McCulloch
- 13:06 [2128] LOC Chattanooga, TN
- 13:06 [2128] NDL 115200,TCP,BINKP
- 13:06 [2128] TIME Mon, 21 Sep 2026 07:06:44 -0400
- 13:06 [2128] VER AmiBinkD/10.35/Amiga binkp/1.1
+ 13:06 [2128] addr: 39:902/518@amiganet (n/a or busy)
+ 13:06 [2128] addr: 10:100/1@araknet (n/a or busy)
+ 13:06 [2128] addr: 64:500/1@cnet (n/a or busy)
+ 13:06 [2128] addr: 12:316/1@disciple (n/a or busy)
+ 13:06 [2128] addr: 1:154/50@fidonet
+ 13:06 [2128] addr: 314:413/1@pinet (n/a or busy)
+ 13:06 [2128] addr: 80:774/1@retronet (n/a or busy)
- 13:06 [2128] OPT EXTCMD
+ 13:06 [2128] Remote supports EXTCMD mode
+ 13:06 [2128] done (to 1:154/50@fidonet, OK, S/R: 0/0 (0/0 bytes))
That resolves to my real endpoints on both protocols:
IPv4 68.169.145.190
IPv6 2605:8600:60:199d:aa5a:bfc6:5328:c881
What is the name of you internet provider?
Both answer on 24554 from where I can test, but that is from inside my own network, so I would rather have your result than mine.
Indeed. Wrong firewall settings often are a cause of failed connects. But you got it right!
Would you mind trying once more against call.rofbbs.com?
See above.
While looking into this I also found my FidoNet nodelist entry is
out of date - it still lists INA:rofbbs.ddns.net,
I saw that and it confused me...
which no longer resolves at all, plus an old location and phonenumber
and no IPV6 flag.
There is no such thing as in IPv6 flag. It is the AAAA record associated woith the host name that signals IOv6 connectability.
That would explain any node failing to reach me from the nodelist. I am getting that corrected with my NC.
OK. So until then I will list you as a "prospective Member". You are connectible but not yet correctly listed in the nodelist. With a bit of luck that will be fixed next Friday. Or sooner in de daily list.
OK. So until then I will list you as a "prospective Member". You
are connectible but not yet correctly listed in the nodelist.
With a bit of luck that will be fixed next Friday. Or sooner in
de daily list.
That is the plan!!
My node should now be correct in the FidoNet nodelist.
+ call.rofbbs.com:6800 call@call.rofbbs.com 423-541-8271 IPv4 &
IPv6 + ACIS Member. AmigaNet ArakNet C=Net DescipleNet FidoNet PiNet RetroNet
My node should now be correct in the FidoNet nodelist.
Hi Gary.
25 Sep 26 04:44, you wrote to All:
My node should now be correct in the FidoNet nodelist.
Zone 1 nodelist looks better now. However ITN:6800 is not ok. There's only bbs, no mailer.
nodelist/Z1DAILY.268:,50,Reign_Of_Fire_BBS,Ooltewah_TN,Gary_McCulloch,1-4 23-541-8271,300,CM,INA:call.rofbbs.com,IBN,ITN:6800
nodelist/Z2DAILY.268:,50,Reign_Of_Fire_BBS,Franklin_WI,Gary_McCulloch,1-9 31-494-9100,300,CM,INA:rofbbs.ddns.net,IBN
'Tommi
--- GoldED+/LNX 1.1.5-b20260914
* Origin: nntps://news.fidonet.fi (2:221/1)
"ITN 23 Telnet connection using FTS-1 or any other protocol
designed for classic POTS and modem."
I don't think many people use a nodelist as any kind of BBS list,
though..
So my nodelist should be ITN:24554 ??
When I find BBS's that look interesting in The Telnet/Dial-Up BBS Guide I allways check if the nodelist mentions them too.
50,Reign_Of_Fire_BBS,Ooltewah_TN,Gary_McCulloch,1-423-541-8271,300,CM, INA:ca ll.rofbbs.com,IBN
The above nodelist now will reach the mailer at the default port of
24554 and it will also hit the mailer using Dial-Up. Not that anyone
uses it, but it does load Trapdoor for incoming mail.
A bit off-topic here but maybe you should list the speed your POTS line actually supports?
On Sun 27-Sep-2026 1:22p, Michiel Van Der Vlist@2:280/5555.0 said to Gary
McCulloch:
A bit off-topic here but maybe you should list the speed your
POTS line actually supports?
1200-38400 BPS.
I fixed your node entry, and set your baud rate to 38400. it should
show up in Fridays nodelist.
Hello, Mike!
Mike Miller wrote:
I fixed your node entry, and set your baud rate to 38400. it
should show up in Fridays nodelist.
38400 is not a valid entry. The largest value accepted in Fidonet is 33600.
I fixed your node entry, and set your baud rate to 38400. it should show up in Fridays nodelist.
Mike
... Intestines: Beta version of forks.
=== GoldED+/LNX 2.0.0-b20260914
--- SBBSecho 3.37-Linux
* Origin: War Ensemble - warensemble.com - Appleton, WI (1:154/30)
So, unless someone has been using the completely rewritten PD
version by Johan Billing and me, reintroducing the limitation, now
you can enter whatever number you like.
You mean that there are still *Cs that are still using Ben's old version?
I know that some has reintroduced the high ASCII block,
but why bother with the baud blocking that,
now that not a single
node has even bothered to see if my POTS line is still working,
after I asked for it?
And the difference between the two is...? Whay characters change
with the 4 from the 2?
now that not a single
node has even bothered to see if my POTS line is still working,
after I asked for it?
the kludges are for use on the message text, and not on the MSG
header, that are read before the text and its kludges.
@MSGID: 2:203/2 6abc50e2MvdV>> Your problem with the CHRS kludge not matching the used
@REPLY: 2:280/5555.6 6abc1f52
@PID: JamNNTPd/Win32 1
@CHRS: UTF-8 2
@TZUTC: 0200
@TID: CrashMail II/Win32 0.71
Michiel van der Vlist -> Björn Felten skrev 2026-09-29 22:28:
The only people having a problem with my kludge (the 2 or 4 is
never used, and you know it) are those who don't understand that the kludges are for use on the message text, and not on the MSG header,
that are read before the text and its kludges.
And if the kludge is only for the message text then the headers should
be ASCII only.
I hope that the moderator will take proper action...
| Sysop: | Dave Parker |
|---|---|
| Location: | Redhill, Surrey |
| Users: | 24 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 10:51:28 |
| Calls: | 246 |
| Files: | 12 |
| Messages: | 41,407 |