Hi All,

New node in net 450: Pvt,220,InfoSecDJ_Home,Mensk,Dmitry_Janushkevich,-Unpublished-,300,MO
The MO flag can be removed.

In net 5003, node has an updated INA: ,16,Crazy_Programmer,Inta,Sergey_Potashev,-Unpublished-,300,CM,IBN,INA:212.55.99.168
Connection refused

New node in net 3634: ,56,ReTR0aKTiV,Greensboro_NC_USA,Rob_Koliha,-Unpublished-,300,INA:retr0aktiv.com,CM,IBN
Connect with: Mystic/1.12A47

Host,124,DALLAS_TX_AREA,Mesquite_TX,Ruben_Figueroa,-Unpublished-,300,CM,INA:pbmystic.rdfig.net:24,IBN:pbmystic.rdfig.net:24555
The INA with port number (?) has been added. There's a bbs answering on port 24.
Port numbers don't belong on INA flags and the nodelist is not a bbs list. :-(

In the same net: Pvt,1113,Nibbles_&_Bytes,Richardson_TX,Ron_Bemis,-Unpublished-,300,XA
The XA flag has been added. Why? We can't connect to this node, so there is no use for the XA flag.

And all these had changes too: ,5013,Prison_Board,Mesquite_TX,Ruben_Figueroa,1-972-329-0781,33600,V34,V32b,V42b,CM,XA,IBN:rdfig.net:2324,IBN:rdfig.net:24555,IVM:rdfig.net
,5014,Mystic_Prison_Board,Mesquite_TX,Ruben_Figueroa,-Unpublished-,300,CM,XA,INA:pbmystic.rdfig.net:24,IBN:pbmystic.rdfig.net:24555
,5015,PCBoard_Prison_BBS,Mesquite_TX,Dario_Figueroa,-Unpublished-,300,CM,XA,INA:pbmystic.rdfig.net:1023,IBN:pbmystic.rdfig.net:24554
,5016,End_Of_The_Line_BBS,Plano_Tx,Nigel_Reed,-Unpublished-,300,CM,XA,INA:ipv4.endofthelinebbs.com,IBN:ipv4.endofthelinebbs.com:24554
,5017,XM_Core_BBS,Dallas_TX,Dwight_Spencer,-Unpublished-,300,CM,XA,INA:bbs.dapla.net,IBN:bbs.dapla.net:24554
,5018,Shakey_BBS,Allen_TX,Von_Wallace,-Unpublished-,300,CM,XA,INA:shakeybbs.com,IBN:shakeybbs.com:24554
,5019,Southern_Charm_BBS,Plano_Tx,Lawrence_Stockman,-Unpublished-,300,CM,XA,INA:southerncharmbbs.com,IBN:southerncharmbbs.com:24554
,5020,Stellar_Darkness_BBS,Toronto_Canada,Mike_Da_Costa,-Unpublished-,300,CM,XA,INA:stellardarkness.com:2023,IBN:stellardarkness.com:24554
There are multiple things wrong:
- Port numbers on INA's.
- Superfluous INA's.
- Default binkp port (24554) listed on IBN's.

And testing the net for connectivity, makes you want to cry:

1:124/0 pbmystic.rdfig.net:24555 75.87.11.243 No such AKA.
1:124/5009 FMLYNET.DYNDNS.ORG - Error: Cannot getaddrinfo - Name or service not known
1:124/5013 rdfig.net:2324 75.87.11.242 Error: Connection timed out 1:124/5013 rdfig.net:24555 75.87.11.242 Ok.
1:124/5014 pbmystic.rdfig.net:24555 75.87.11.243 Error: Socket read error. 1:124/5015 pbmystic.rdfig.net:24554 75.87.11.243 Error: Connection refused
1:124/5016 ipv4.endofthelinebbs.com:24554 192.138.210.158 Ok.
1:124/5017 bbs.dapla.net:24554 104.21.5.58 Error: Connection timed out 1:124/5017 bbs.dapla.net:24554 172.67.133.5 Error: Connection timed out 1:124/5017 bbs.dapla.net:24554 2606:4700:3032::ac43:8505 Error: Connection timed out
1:124/5017 bbs.dapla.net:24554 2606:4700:3035::6815:53a Error: Connection timed out
1:124/5018 shakeybbs.com - Error: Cannot getaddrinfo - Name or service not known
1:124/5019 southerncharmbbs.com - Error: Cannot getaddrinfo - Name or service not known
1:124/5020 stellardarkness.com:24554 15.197.142.173 Error: Connection timed out
1:124/5020 stellardarkness.com:24554 3.33.152.147 Error: Connection timed out

BTW: Nodes 5018 and 5020 are new entries.

There was one good change though in this net! The "node": Hold,9999,Net124_New_Test_Node,Anytown_US,New_Sysop,-Unpublished-,300,CM,XA
Has been removed.


Regards, NPC

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

Hello Nodelist,

On Friday May 27 2022 12:38, you wrote to All:

New node in net 450: Pvt,220,InfoSecDJ_Home,Mensk,Dmitry_Janushkevich,-Unpublished-,300,MO
The MO flag can be removed.

"Should" be removed.

In net 5003, node has an updated INA: ,16,Crazy_Programmer,Inta,Sergey_Potashev,-Unpublished-,300,CM,IBN,INA :212.55.99.168 Connection refused

Same here.

New node in net 3634: ,56,ReTR0aKTiV,Greensboro_NC_USA,Rob_Koliha,-Unpublished-,300,INA:retr 0aktiv.com,CM,IBN Connect with: Mystic/1.12A47

Check!

Host,124,DALLAS_TX_AREA,Mesquite_TX,Ruben_Figueroa,-Unpublished-,300,C M,INA:pbmystic.rdfig.net:24,IBN:pbmystic.rdfig.net:24555 The INA with
port number (?) has been added. There's a bbs answering on port
24. Port numbers don't belong on INA flags and the nodelist is not a
bbs list. :-(

Another NC that has no idea...

In the same net: Pvt,1113,Nibbles_&_Bytes,Richardson_TX,Ron_Bemis,-Unpublished-,300,XA
The XA flag has been added. Why? We can't connect to this node, so
there is no use for the XA flag.

Or: why a Pvt node. IMNSHO if it has the connectibility of a Pointm it should BE a Point.

And all these had changes too: ,5013,Prison_Board,Mesquite_TX,Ruben_Figueroa,1-972-329-0781,33600,V34

[..]

wrong: - Port numbers on INA's. - Superfluous INA's. - Default binkp
port (24554) listed on IBN's.

[..]

And testing the net for connectivity, makes you want to cry:

1:124/0 pbmystic.rdfig.net:24555 75.87.11.243 No such AKA. 1:124/5009 FMLYNET.DYNDNS.ORG - Error: Cannot getaddrinfo -

[..]

If there was an NC test, he would not have passed...

There was one good change though in this net! The "node": Hold,9999,Net124_New_Test_Node,Anytown_US,New_Sysop,-Unpublished-,300, CM,XA Has been removed.

Good!


Cheers, Michiel

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

Hi, Michiel!

28 ¬ © 22 16:06, Michiel van der Vlist -> Nodelist Police Commissioner:

Host,124,DALLAS_TX_AREA,Mesquite_TX,Ruben_Figueroa,-Unpublished-,300,
CM,INA:pbmystic.rdfig.net:24,IBN:pbmystic.rdfig.net:24555 The INA
with port number (?) has been added. There's a bbs answering on port
24. Port numbers don't belong on INA flags and the nodelist is not a
bbs list. :-(

MvdV> Another NC that has no idea...

... and have "No such AKA" error. ;)

Have nice nights.
Stas Mishchenkov.

--- ‘ ¬ë© ¬®© ¯à®¢¥à¥­­ë© à¥æ¥¯â - ᪠§ âì ¦¥­¥, çâ® å®ç¥èì ¡®àé .
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hello Nodelist.

<On 27May2022 12:38 Nodelist Police Commissioner (2:280/464) wrote a message to All regarding Weekly nodelist report on noteworthy changes (147) >

Host,124,DALLAS_TX_AREA,Mesquite_TX,Ruben_Figueroa,-Unpublished-,3 00,CM,INA:pbmystic.rdfig.net:24,IBN:pbmystic.rdfig.net:24555
The INA with port number (?) has been added. There's a bbs
answering on port 24. Port numbers don't belong on INA flags and
the nodelist is not a bbs list. :-(

Where does the port number other than standard for the BBS and binkd belong?

I'll get with Ruben about these:

In the same net: Pvt,1113,Nibbles_&_Bytes,Richardson_TX,Ron_Bemis,-Unpublished-,300
,XA The XA flag has been added. Why? We can't connect to this
node, so there is no use for the XA flag.

And all these had changes too: ,5013,Prison_Board,Mesquite_TX,Ruben_Figueroa,1-972-329-0781,33600 ,V34,V32b,V42b,CM,XA,IBN:rdfig.net:2324,IBN:rdfig.net:24555,IVM:rd fig.net ,5014,Mystic_Prison_Board,Mesquite_TX,Ruben_Figueroa,-Unpublished- ,300,CM,XA,INA:pbmystic.rdfig.net:24,IBN:pbmystic.rdfig.net:24555 ,5015,PCBoard_Prison_BBS,Mesquite_TX,Dario_Figueroa,-Unpublished-, 300,CM,XA,INA:pbmystic.rdfig.net:1023,IBN:pbmystic.rdfig.net:24554 ,5016,End_Of_The_Line_BBS,Plano_Tx,Nigel_Reed,-Unpublished-,300,CM ,XA,INA:ipv4.endofthelinebbs.com,IBN:ipv4.endofthelinebbs.com:2455
4
,5017,XM_Core_BBS,Dallas_TX,Dwight_Spencer,-Unpublished-,300,CM,XA ,INA:bbs.dapla.net,IBN:bbs.dapla.net:24554 ,5018,Shakey_BBS,Allen_TX,Von_Wallace,-Unpublished-,300,CM,XA,INA: shakeybbs.com,IBN:shakeybbs.com:24554 ,5019,Southern_Charm_BBS,Plano_Tx,Lawrence_Stockman,-Unpublished-, 300,CM,XA,INA:southerncharmbbs.com,IBN:southerncharmbbs.com:24554 ,5020,Stellar_Darkness_BBS,Toronto_Canada,Mike_Da_Costa,-Unpublish ed-,300,CM,XA,INA:stellardarkness.com:2023,IBN:stellardarkness.com
:24554
There are multiple things wrong:
- Port numbers on INA's.
- Superfluous INA's.
- Default binkp port (24554) listed on IBN's.

And testing the net for connectivity, makes you want to cry:

1:124/0 pbmystic.rdfig.net:24555 75.87.11.243 No such AKA. 1:124/5009 FMLYNET.DYNDNS.ORG - Error: Cannot
getaddrinfo - Name or service not known
1:124/5013 rdfig.net:2324 75.87.11.242 Error: Connection timed
out 1:124/5013 rdfig.net:24555 75.87.11.242 Ok.
1:124/5014 pbmystic.rdfig.net:24555 75.87.11.243 Error: Socket
read error. 1:124/5015 pbmystic.rdfig.net:24554
75.87.11.243 Error: Connection refused
1:124/5016 ipv4.endofthelinebbs.com:24554 192.138.210.158 Ok.
1:124/5017 bbs.dapla.net:24554 104.21.5.58 Error:
Connection timed out 1:124/5017 bbs.dapla.net:24554
172.67.133.5 Error: Connection timed out 1:124/5017 bbs.dapla.net:24554 2606:4700:3032::ac43:8505 Error:
Connection timed out
1:124/5017 bbs.dapla.net:24554 2606:4700:3035::6815:53a
Error: Connection timed out
1:124/5018 shakeybbs.com - Error: Cannot getaddrinfo -
Name or service not known
1:124/5019 southerncharmbbs.com - Error: Cannot
getaddrinfo - Name or service not known
1:124/5020 stellardarkness.com:24554 15.197.142.173 Error: Connection timed out
1:124/5020 stellardarkness.com:24554 3.33.152.147 Error: Connection timed out

BTW: Nodes 5018 and 5020 are new entries.

There was one good change though in this net! The "node": Hold,9999,Net124_New_Test_Node,Anytown_US,New_Sysop,-Unpublished-, 300,CM,XA Has been removed.

Best regards,
Marc

--- timEd/2 1.10.y2k+
* Origin: Sursum Corda! BBS-Huntsville,AL-bbs.sursum-corda.com (1:396/45)

Hello Marc,

On Sunday May 29 2022 23:39, you wrote to Nodelist Police Commissioner:

Where does the port number other than standard for the BBS and binkd belong?

The port number for binkd (if other than the standard 24554) should be behind the IBN flag. There is no place for the BBS port in the nodelist.

See FTS-5001.006 par 5.9

http://ftsc.org/docs/fts-5001.006


Cheers, Michiel

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

Hello Marc,

On 2022-05-29 23:39:22, you wrote to me:

Host,124,DALLAS_TX_AREA,Mesquite_TX,Ruben_Figueroa,-Unpublished-,3
00,CM,INA:pbmystic.rdfig.net:24,IBN:pbmystic.rdfig.net:24555
The INA with port number (?) has been added. There's a bbs
answering on port 24. Port numbers don't belong on INA flags and
the nodelist is not a bbs list. :-(

Where does the port number other than standard for the BBS and binkd belong?

Michiel answered that one.

I'll get with Ruben about these:

Thanks.


Regards, NPC.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: NPC Station (2:280/464)

Hello Michiel.

<On 30May2022 08:08 Michiel van der Vlist (2:280/5555) wrote a message to Marc Lewis regarding Weekly nodelist report on noteworthy changes (147) >

Where does the port number other than standard for the BBS and binkd belong?

MvdV> The port number for binkd (if other than the standard 24554)
MvdV> should be behind the IBN flag. There is no place for the BBS port
MvdV> in the nodelist.

MvdV> See FTS-5001.006 par 5.9

It would *seem* that a non-standard port to reach the BBS itself should be included after an ITN: entry somehow. Is this not correct? Even after reading the FTS-5001.006 5.9 I'm still a bit confused. How is someone that runs on a non-standard telnet port be listed?

Thanks in advance.

Best regards,
Marc

--- timEd/2 1.10.y2k+
* Origin: Sursum Corda! BBS-Huntsville,AL-bbs.sursum-corda.com (1:396/45)

Hello Marc,

30 May 22 18:32, you wrote to Michiel van der Vlist:

Hello Michiel.

<On 30May2022 08:08 Michiel van der Vlist (2:280/5555) wrote a message
to Marc Lewis regarding Weekly nodelist report on noteworthy changes

(147) >>

Where does the port number other than standard for the BBS and
binkd belong?

MvdV>> The port number for binkd (if other than the standard 24554)
MvdV>> should be behind the IBN flag. There is no place for the BBS
MvdV>> port in the nodelist.

MvdV>> See FTS-5001.006 par 5.9

It would *seem* that a non-standard port to reach the BBS itself
should be included after an ITN: entry somehow. Is this not correct?
Even after reading the FTS-5001.006 5.9 I'm still a bit confused. How
is someone that runs on a non-standard telnet port be listed?

AFAIK, ITN is for a telnet-reachable mailer with EMSI.
check my record in the nodelist

Regards,
--
dp

telnet://bbs.roonsbbs.hu:1212 <<=-

... 10:16am up 14 days, 20:03:36, load: 74 processes, 276 threads.
--- GoldED/2 1.1.4.7+EMX
* Origin: Roon's BBS - Budapest, HUNGARY +36-1-4454412 (2:371/52)

Hello Daniel,

On Tuesday May 31 2022 08:22, you wrote to Marc Lewis:

AFAIK, ITN is for a telnet-reachable mailer with EMSI.

Or FTS-0001 or FTs-0006. The key owrd is /mailer/

From FTS-5001.006:

ITN 23 Telnet connection using FTS-1 or any other protocol
designed for classic POTS and modem.

check my record in the nodelist

Check. There is an EMSI mailer answering at port 1212. You carry no MO flag, so one may expect a BBS behind the mailer. And indeed there is. The point however is that the ITN flag in the nodelist signals the presence of a MAILER running a POTS protocol. (at the given port)

Your listing is correct.


Cheers, Michiel

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

Hello Daniel,

On 2022-05-31 08:22:53, you wrote to Marc Lewis:

MvdV>>> There is no place for the BBS port in the nodelist.

MvdV>>> See FTS-5001.006 par 5.9

It would *seem* that a non-standard port to reach the BBS itself
should be included after an ITN: entry somehow. Is this not correct?
Even after reading the FTS-5001.006 5.9 I'm still a bit confused. How
is someone that runs on a non-standard telnet port be listed?

AFAIK, ITN is for a telnet-reachable mailer with EMSI.

Indeed. And as Michiel said above, there is no place for BBS ports in the nodelist. The nodelist should only contain connect information for mailers.

I think a lot of the nodes with an ITN flag in the current nodelist actually don't have a telnet connectable mailer, and those ITN flags should be removed.

check my record in the nodelist

IBN,ITN:1212,INA:bbs.studio64.hu

It would be better if the INA was in front of the IBN or ITN, but I don't think it a strict requirement, and with only 1 INA there can't be any confusion about which Ixx flag it applies too.


Regards, NPC.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: NPC Station (2:280/464)

Hello Marc,

On Monday May 30 2022 18:32, you wrote to me:

MvdV>> See FTS-5001.006 par 5.9

It would *seem* that a non-standard port to reach the BBS itself
should be included after an ITN: entry somehow. Is this not correct?

It is not correct. The nodelist is NOT a BBS list. The ITN flag in the nodelist indicates a MAILER runing a POTS protocol. If no port number is given, it answers on port 23.

Like with a POTS mailer there may or may not be a BBS /behind/ the mailer. But there must always be a mailer.

Even after reading the FTS-5001.006 5.9 I'm still a bit confused. How
is someone that runs on a non-standard telnet port be listed?

If there is a mailer answering on the non standard pot 23, the port number is in the parameter field of the ITN flag. E.g. ITN:1234.

There may or may not be a BBS behind the mailer at that port. But there is no way to just list the BBS. Like in the POTS age, there was no way to list a BBS without a front end mailer on the listed phone number. For that one needs a BBS list.


Cheers, Michiel

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

Hello Nodelist,

On Tuesday May 31 2022 09:42, you wrote to Daniel Path:

I think a lot of the nodes with an ITN flag in the current nodelist actually don't have a telnet connectable mailer, and those ITN flags should be removed.

I have the same suspicion. But there are too many nodes carrying an ITN flag, I am too lazy to manually test them all or write a script for it.


Cheers, Michiel

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

Hello Michiel,

On 2022-05-31 13:34:40, you wrote to me:

I think a lot of the nodes with an ITN flag in the current nodelist
actually don't have a telnet connectable mailer, and those ITN flags
should be removed.

MvdV> I have the same suspicion. But there are too many nodes carrying an ITN
MvdV> flag, I am too lazy to manually test them all or write a script for it.

Maybe Stas can write a (perl) script for this? He's already done it for IBN... ;-)

Regards, NPC.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: NPC Station (2:280/464)

Hello Nodelist,

On Tuesday May 31 2022 14:21, you wrote to me:

MvdV>> I have the same suspicion. But there are too many nodes
MvdV>> carrying an ITN flag, I am too lazy to manually test them all
MvdV>> or write a script for it.

Maybe Stas can write a (perl) script for this? He's already done it
for IBN... ;-)

Let us wait and see... ;-)


Cheers, Michiel

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

Hello Nodelist.

<On 30May2022 10:37 Nodelist Police Commissioner (2:280/464) wrote a message to Marc Lewis regarding Re:Weekly nodelist report on noteworthy changes (147) >

Where does the port number other than standard for the BBS and binkd belong?

Michiel answered that one.

I'll get with Ruben about these:

Thanks.

You should see a major revision of that Net's segment. Hopefully it'll meet spec. We did our best to figure out what goes where in the listings. Non-answering nodes are going to be carrying the "DOWN" flag as well until he gets word back from them about their system statuses.

Best regards,
Marc

--- timEd/2 1.10.y2k+
* Origin: Sursum Corda! BBS-Huntsville,AL-bbs.sursum-corda.com (1:396/45)