Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,200,Outpost_BBS,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,10,The_Byte_Museum,Wharton_TX,Matt_Bedynek,-Unpublished-,300,INA:ftn.bytemuseum.org,IBN,ICM,MO,MN,PING,XA
,51,bbs.bofh.it,Milano,Marco_d'Itri,-Unpublished-,300,ICM,XA,MO,IBN,IFC,ITN:60177,U,ENC
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115
,9999,R50_Hold,Moscow,Alex_Barinov,-Unpublished-,300,MO,IEM:huba715@yandex.ru,IMI,ICM
,400,Demos_Plus,Moscow,Gatekeeper,-Unpublished-,300,ICM,IBN,IFC,INA:ddt.demos.su
,806,Elinora_Station,Shchyolkovo,Sergey_Dorozhkin,-Unpublished-,9600,XW,MO,ICM,ITN:60177,IFC:60179,IBN:24554,INA:93.123.250.176
,921,Abdulla_Tukaew's_Mail_Station,Moscow,Andrew_Savin,-Unpublished-,300,ICM,IBN,INA:fido.bibirevo.net,INA:f921.n5020.z2.binkp.net
,1313,fido.stabilis.ru,Moscow,Sergey_V._Efimoff,-Unpublished-,300,ICM,IBN,INA:fido.stabilis.ru
,9696,SDS,Moscow,Alexander_N_Skovpen,-Unpublished-,300,XX,ICM,IBN,INA:skovpen.org
,828,f828.n5020.z2.binkp.net,Moscow,Kirill_Temnenkov,-Unpublished-,300,ICM,IBN,INA:f828.n5020.z2.binkp.net,U,ENC
,8086,Z80_Station,Moscow,Pavel_Osipov,-Unpublished-,300,MO,IBN,ICM,INA:f8086.n5020.z2.binkp.net
Hub,5020,Freezer,Moscow,Alex_Barinov,-Unpublished-,300,MO,ICM,IBN,INA:fido.hubahuba.su,IEM:hubahuba@infoline.su,ITX,IMI
Host,5021,Tver_Net,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru,U,NC
Hub,29,All-Privet,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru,U,ENC
,5021,Net5021_Netmail_Gate,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru
,12,T-Station,Kaluga,Alexander_Fyodorov,-Unpublished-,300,ICM,IFC,IBN,INA:62.148.154.95
Host,5024,Vladimir_Net,Vladimir_Russia,Victor_Smirnov,-Unpublished-,9600,ICM,IBN,INA:n3.net5024.ru
,3,Shadow_bbs,Vladimir,Victor_Smirnov,-Unpublished-,300,ICM,IBN,INA:n3.net5024.ru,U,NC
,1024,NEWLEO,Vladimir,Leonid_Novikov,-Unpublished-,300,ICM,IBN,INA:n1024.net5024.ru
Host,5029,Ryazan_Net,Ryazan,Alexey_Bugrov,-Unpublished-,300,ICM,IBN,INA:ftn.avblabs.ru
,9,The_Power_of_Music_2,Ryazan,Ilya_Katargin,-Unpublished-,300,ICM,IBN,INA:ftn.astcrg.ru
,32,AVB_Labs_BBS,Ryazan,Alexey_Bugrov,-Unpublished-,300,ICM,IBN,INA:ftn.avblabs.ru,U,NC
,7,Wayfarer,Stary_Oscol,Evgeny_Vetrov,-Unpublished-,300,ICM,IBN,INA:smekal.ru,U,NPK
Host,5061,Rostov_Net,Rostov-on-Don,Eugene_Gladchenko,-Unpublished-,300,MO,ICM,IBN,INA:f15.n5061.z2.binkp.net
Host,5075,Net_Togliatti,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.subbotin.org
Hub,128,Dewy_News,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.dewy.ru
,35,FireFox_Station,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.subbotin.org,BEER:stout,BEER:sour_ale,BEER:strong_ale
,37,Warlock_BBS,Togliatti,Andrew_Komardin,-Unpublished-,300,MO,ICM,IBN,INA:fido.warlocktlt.ru
Host,5076,YaNAO_Net,Noviy_Urengoy,Andrew_Rogov,-Unpublished-,300,MO,IBN,ICM,INA:178.216.154.110,#20
,207,SevES_TE,Noviy_Urengoy,Andrew_Rogov,-Unpublished-,300,MO,IBN,ICM,INA:207.grumbler.org,#20
Host,5095,Podolsk_Net,Podolsk_Russia,Sergey_V._Efimoff,-Unpublished-,300,MO,ICM,IBN,INA:n5095.stabilis.ru
Host,5097,Night_Flame,Ukhta,Tema_Zelikin,-Unpublished-,300,ICM,IBN,INA:nightflame.info
,31,Night_Flame,Ukhta,Tema_Zelikin,-Unpublished-,300,ICM,IBN,INA:nightflame.info

35 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,200,Outpost_BBS,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,10,The_Byte_Museum,Wharton_TX,Matt_Bedynek,-Unpublished-,300,INA:ftn.bytemuseum.org,IBN,ICM,MO,MN,PING,XA
,51,bbs.bofh.it,Milano,Marco_d'Itri,-Unpublished-,300,ICM,XA,MO,IBN,IFC,ITN:60177,U,ENC
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115
,9999,R50_Hold,Moscow,Alex_Barinov,-Unpublished-,300,MO,IEM:huba715@yandex.ru,IMI,ICM
,400,Demos_Plus,Moscow,Gatekeeper,-Unpublished-,300,ICM,IBN,IFC,INA:ddt.demos.su
,806,Elinora_Station,Shchyolkovo,Sergey_Dorozhkin,-Unpublished-,9600,XW,MO,ICM,ITN:60177,IFC:60179,IBN:24554,INA:93.123.250.176
,921,Abdulla_Tukaew's_Mail_Station,Moscow,Andrew_Savin,-Unpublished-,300,ICM,IBN,INA:fido.bibirevo.net,INA:f921.n5020.z2.binkp.net
,1313,fido.stabilis.ru,Moscow,Sergey_V._Efimoff,-Unpublished-,300,ICM,IBN,INA:fido.stabilis.ru
,9696,SDS,Moscow,Alexander_N_Skovpen,-Unpublished-,300,XX,ICM,IBN,INA:skovpen.org
,828,f828.n5020.z2.binkp.net,Moscow,Kirill_Temnenkov,-Unpublished-,300,ICM,IBN,INA:f828.n5020.z2.binkp.net,U,ENC
,8086,Z80_Station,Moscow,Pavel_Osipov,-Unpublished-,300,MO,IBN,ICM,INA:f8086.n5020.z2.binkp.net
Hub,5020,Freezer,Moscow,Alex_Barinov,-Unpublished-,300,MO,ICM,IBN,INA:fido.hubahuba.su,IEM:hubahuba@infoline.su,ITX,IMI
Host,5021,Tver_Net,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru,U,NC
Hub,29,All-Privet,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru,U,ENC
,5021,Net5021_Netmail_Gate,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru
,12,T-Station,Kaluga,Alexander_Fyodorov,-Unpublished-,300,ICM,IFC,IBN,INA:62.148.154.95
Host,5029,Ryazan_Net,Ryazan,Alexey_Bugrov,-Unpublished-,300,ICM,IBN,INA:ftn.avblabs.ru
,9,The_Power_of_Music_2,Ryazan,Ilya_Katargin,-Unpublished-,300,ICM,IBN,INA:ftn.astcrg.ru
,32,AVB_Labs_BBS,Ryazan,Alexey_Bugrov,-Unpublished-,300,ICM,IBN,INA:ftn.avblabs.ru,U,NC
,7,Wayfarer,Stary_Oscol,Evgeny_Vetrov,-Unpublished-,300,ICM,IBN,INA:smekal.ru,U,NPK
Host,5061,Rostov_Net,Rostov-on-Don,Eugene_Gladchenko,-Unpublished-,300,MO,ICM,IBN,INA:f15.n5061.z2.binkp.net
Host,5075,Net_Togliatti,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.subbotin.org
Hub,128,Dewy_News,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.dewy.ru
,35,FireFox_Station,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.subbotin.org,BEER:stout,BEER:sour_ale,BEER:strong_ale
,37,Warlock_BBS,Togliatti,Andrew_Komardin,-Unpublished-,300,MO,ICM,IBN,INA:fido.warlocktlt.ru
Host,5076,YaNAO_Net,Noviy_Urengoy,Andrew_Rogov,-Unpublished-,300,MO,IBN,ICM,INA:178.216.154.110,#20
,207,SevES_TE,Noviy_Urengoy,Andrew_Rogov,-Unpublished-,300,MO,IBN,ICM,INA:207.grumbler.org,#20
Host,5095,Podolsk_Net,Podolsk_Russia,Sergey_V._Efimoff,-Unpublished-,300,MO,ICM,IBN,INA:n5095.stabilis.ru
Host,5097,Night_Flame,Ukhta,Tema_Zelikin,-Unpublished-,300,ICM,IBN,INA:nightflame.info
,31,Night_Flame,Ukhta,Tema_Zelikin,-Unpublished-,300,ICM,IBN,INA:nightflame.info

32 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hi All,

On 2025-06-04 12:00:02, Michiel van der Vlist wrote to you:

MvdV> The ICM flag was meant as a transition mechanism for accomodating
MvdV> nodes that were running CM for the IP part and non CM for the
MvdV> POTS/ISDN part.

MvdV> See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

MvdV> The CM flag implies ICM: ICM should not be used unless CM is impossible.

MvdV> So IP only nodes should carry the CM flag, not the ICM flag.

MvdV> This is a list of nodes with a misplaced ICM flag:

There are 3 systems less in this weeks report.

These were fixed in the nodelist:

Host,5024,Vladimir_Net,Vladimir_Russia,Victor_Smirnov,-Unpublished-,9600,ICM,IBN,INA:n3.net5024.ru
,3,Shadow_bbs,Vladimir,Victor_Smirnov,-Unpublished-,300,ICM,IBN,INA:n3.net5024.ru,U,NC
,1024,NEWLEO,Vladimir,Leonid_Novikov,-Unpublished-,300,ICM,IBN,INA:n1024.net5024.ru



Bye, Wilfred.

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

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,200,Outpost_BBS,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,10,The_Byte_Museum,Wharton_TX,Matt_Bedynek,-Unpublished-,300,INA:ftn.bytemuseum.org,IBN,ICM,MO,MN,PING,XA
,51,bbs.bofh.it,Milano,Marco_d'Itri,-Unpublished-,300,ICM,XA,MO,IBN,IFC,ITN:60177,U,ENC
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115
,9999,R50_Hold,Moscow,Alex_Barinov,-Unpublished-,300,MO,IEM:huba715@yandex.ru,IMI,ICM
,400,Demos_Plus,Moscow,Gatekeeper,-Unpublished-,300,ICM,IBN,IFC,INA:ddt.demos.su
,806,Elinora_Station,Shchyolkovo,Sergey_Dorozhkin,-Unpublished-,9600,XW,MO,ICM,ITN:60177,IFC:60179,IBN:24554,INA:93.123.250.176
,921,Abdulla_Tukaew's_Mail_Station,Moscow,Andrew_Savin,-Unpublished-,300,ICM,IBN,INA:fido.bibirevo.net,INA:f921.n5020.z2.binkp.net
,1313,fido.stabilis.ru,Moscow,Sergey_V._Efimoff,-Unpublished-,300,ICM,IBN,INA:fido.stabilis.ru
,9696,SDS,Moscow,Alexander_N_Skovpen,-Unpublished-,300,XX,ICM,IBN,INA:skovpen.org
,828,f828.n5020.z2.binkp.net,Moscow,Kirill_Temnenkov,-Unpublished-,300,ICM,IBN,INA:f828.n5020.z2.binkp.net,U,ENC
,8086,Z80_Station,Moscow,Pavel_Osipov,-Unpublished-,300,MO,IBN,ICM,INA:f8086.n5020.z2.binkp.net
Hub,5020,Freezer,Moscow,Alex_Barinov,-Unpublished-,300,MO,ICM,IBN,INA:fido.hubahuba.su,IEM:hubahuba@infoline.su,ITX,IMI
Host,5021,Tver_Net,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru,U,NC
Hub,29,All-Privet,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru,U,ENC
,5021,Net5021_Netmail_Gate,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru
,12,T-Station,Kaluga,Alexander_Fyodorov,-Unpublished-,300,ICM,IFC,IBN,INA:62.148.154.95
Host,5029,Ryazan_Net,Ryazan,Alexey_Bugrov,-Unpublished-,300,ICM,IBN,INA:ftn.avblabs.ru
,9,The_Power_of_Music_2,Ryazan,Ilya_Katargin,-Unpublished-,300,ICM,IBN,INA:ftn.astcrg.ru
,32,AVB_Labs_BBS,Ryazan,Alexey_Bugrov,-Unpublished-,300,ICM,IBN,INA:ftn.avblabs.ru,U,NC
,7,Wayfarer,Stary_Oscol,Evgeny_Vetrov,-Unpublished-,300,ICM,IBN,INA:smekal.ru,U,NPK
Host,5061,Rostov_Net,Rostov-on-Don,Eugene_Gladchenko,-Unpublished-,300,MO,ICM,IBN,INA:f15.n5061.z2.binkp.net
Host,5075,Net_Togliatti,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.subbotin.org
Hub,128,Dewy_News,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.dewy.ru
,35,FireFox_Station,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.subbotin.org,BEER:stout,BEER:sour_ale,BEER:strong_ale
,37,Warlock_BBS,Togliatti,Andrew_Komardin,-Unpublished-,300,MO,ICM,IBN,INA:fido.warlocktlt.ru
Host,5076,YaNAO_Net,Noviy_Urengoy,Andrew_Rogov,-Unpublished-,300,MO,IBN,ICM,INA:178.216.154.110,#20
,207,SevES_TE,Noviy_Urengoy,Andrew_Rogov,-Unpublished-,300,MO,IBN,ICM,INA:207.grumbler.org,#20
Host,5095,Podolsk_Net,Podolsk_Russia,Sergey_V._Efimoff,-Unpublished-,300,MO,ICM,IBN,INA:n5095.stabilis.ru
Host,5097,Night_Flame,Ukhta,Tema_Zelikin,-Unpublished-,300,ICM,IBN,INA:nightflame.info
,31,Night_Flame,Ukhta,Tema_Zelikin,-Unpublished-,300,ICM,IBN,INA:nightflame.info

32 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,200,Outpost_BBS,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,10,The_Byte_Museum,Wharton_TX,Matt_Bedynek,-Unpublished-,300,INA:ftn.bytemuseum.org,IBN,ICM,MO,MN,PING,XA
,51,bbs.bofh.it,Milano,Marco_d'Itri,-Unpublished-,300,ICM,XA,MO,IBN,IFC,ITN:60177,U,ENC
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115
,9999,R50_Hold,Moscow,Alex_Barinov,-Unpublished-,300,MO,IEM:huba715@yandex.ru,IMI,ICM
,400,Demos_Plus,Moscow,Gatekeeper,-Unpublished-,300,ICM,IBN,IFC,INA:ddt.demos.su
,806,Elinora_Station,Shchyolkovo,Sergey_Dorozhkin,-Unpublished-,9600,XW,MO,ICM,ITN:60177,IFC:60179,IBN:24554,INA:93.123.250.176
,921,Abdulla_Tukaew's_Mail_Station,Moscow,Andrew_Savin,-Unpublished-,300,ICM,IBN,INA:fido.bibirevo.net,INA:f921.n5020.z2.binkp.net
,1313,fido.stabilis.ru,Moscow,Sergey_V._Efimoff,-Unpublished-,300,ICM,IBN,INA:fido.stabilis.ru
,9696,SDS,Moscow,Alexander_N_Skovpen,-Unpublished-,300,XX,ICM,IBN,INA:skovpen.org
,828,f828.n5020.z2.binkp.net,Moscow,Kirill_Temnenkov,-Unpublished-,300,ICM,IBN,INA:f828.n5020.z2.binkp.net,U,ENC
,8086,Z80_Station,Moscow,Pavel_Osipov,-Unpublished-,300,MO,IBN,ICM,INA:f8086.n5020.z2.binkp.net
Hub,5020,Freezer,Moscow,Alex_Barinov,-Unpublished-,300,MO,ICM,IBN,INA:fido.hubahuba.su,IEM:hubahuba@infoline.su,ITX,IMI
Host,5021,Tver_Net,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru,U,NC
Hub,29,All-Privet,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru,U,ENC
,5021,Net5021_Netmail_Gate,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru
,12,T-Station,Kaluga,Alexander_Fyodorov,-Unpublished-,300,ICM,IFC,IBN,INA:62.148.154.95
Host,5029,Ryazan_Net,Ryazan,Alexey_Bugrov,-Unpublished-,300,ICM,IBN,INA:ftn.avblabs.ru
,9,The_Power_of_Music_2,Ryazan,Ilya_Katargin,-Unpublished-,300,ICM,IBN,INA:ftn.astcrg.ru
,32,AVB_Labs_BBS,Ryazan,Alexey_Bugrov,-Unpublished-,300,ICM,IBN,INA:ftn.avblabs.ru,U,NC
,7,Wayfarer,Stary_Oscol,Evgeny_Vetrov,-Unpublished-,300,ICM,IBN,INA:smekal.ru,U,NPK
Host,5061,Rostov_Net,Rostov-on-Don,Eugene_Gladchenko,-Unpublished-,300,MO,ICM,IBN,INA:f15.n5061.z2.binkp.net
Host,5075,Net_Togliatti,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.subbotin.org
Hub,128,Dewy_News,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.dewy.ru
,35,FireFox_Station,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.subbotin.org,BEER:stout,BEER:sour_ale,BEER:strong_ale
,37,Warlock_BBS,Togliatti,Andrew_Komardin,-Unpublished-,300,MO,ICM,IBN,INA:fido.warlocktlt.ru
Host,5076,YaNAO_Net,Noviy_Urengoy,Andrew_Rogov,-Unpublished-,300,MO,IBN,ICM,INA:178.216.154.110,#20
,207,SevES_TE,Noviy_Urengoy,Andrew_Rogov,-Unpublished-,300,MO,IBN,ICM,INA:207.grumbler.org,#20
Host,5095,Podolsk_Net,Podolsk_Russia,Sergey_V._Efimoff,-Unpublished-,300,MO,ICM,IBN,INA:n5095.stabilis.ru
Host,5097,Night_Flame,Ukhta,Tema_Zelikin,-Unpublished-,300,ICM,IBN,INA:nightflame.info
,31,Night_Flame,Ukhta,Tema_Zelikin,-Unpublished-,300,ICM,IBN,INA:nightflame.info

32 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,200,Outpost_BBS,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,10,The_Byte_Museum,Wharton_TX,Matt_Bedynek,-Unpublished-,300,INA:ftn.bytemuseum.org,IBN,ICM,MO,MN,PING,XA
,51,bbs.bofh.it,Milano,Marco_d'Itri,-Unpublished-,300,ICM,XA,MO,IBN,IFC,ITN:60177,U,ENC
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115
,9999,R50_Hold,Moscow,Alex_Barinov,-Unpublished-,300,MO,IEM:huba715@yandex.ru,IMI,ICM
,400,Demos_Plus,Moscow,Gatekeeper,-Unpublished-,300,ICM,IBN,IFC,INA:ddt.demos.su
,806,Elinora_Station,Shchyolkovo,Sergey_Dorozhkin,-Unpublished-,9600,XW,MO,ICM,ITN:60177,IFC:60179,IBN:24554,INA:93.123.250.176
,921,Abdulla_Tukaew's_Mail_Station,Moscow,Andrew_Savin,-Unpublished-,300,ICM,IBN,INA:fido.bibirevo.net,INA:f921.n5020.z2.binkp.net
,1313,fido.stabilis.ru,Moscow,Sergey_V._Efimoff,-Unpublished-,300,ICM,IBN,INA:fido.stabilis.ru
,9696,SDS,Moscow,Alexander_N_Skovpen,-Unpublished-,300,XX,ICM,IBN,INA:skovpen.org
,828,f828.n5020.z2.binkp.net,Moscow,Kirill_Temnenkov,-Unpublished-,300,ICM,IBN,INA:f828.n5020.z2.binkp.net,U,ENC
,8086,Z80_Station,Moscow,Pavel_Osipov,-Unpublished-,300,MO,IBN,ICM,INA:f8086.n5020.z2.binkp.net
Hub,5020,Freezer,Moscow,Alex_Barinov,-Unpublished-,300,MO,ICM,IBN,INA:fido.hubahuba.su,IEM:hubahuba@infoline.su,ITX,IMI
Host,5021,Tver_Net,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru,U,NC
Hub,29,All-Privet,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru,U,ENC
,5021,Net5021_Netmail_Gate,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru
,12,T-Station,Kaluga,Alexander_Fyodorov,-Unpublished-,300,ICM,IFC,IBN,INA:62.148.154.95
Host,5029,Ryazan_Net,Ryazan,Alexey_Bugrov,-Unpublished-,300,ICM,IBN,INA:ftn.avblabs.ru
,9,The_Power_of_Music_2,Ryazan,Ilya_Katargin,-Unpublished-,300,ICM,IBN,INA:ftn.astcrg.ru
,32,AVB_Labs_BBS,Ryazan,Alexey_Bugrov,-Unpublished-,300,ICM,IBN,INA:ftn.avblabs.ru,U,NC
,7,Wayfarer,Stary_Oscol,Evgeny_Vetrov,-Unpublished-,300,ICM,IBN,INA:smekal.ru,U,NPK
Host,5061,Rostov_Net,Rostov-on-Don,Eugene_Gladchenko,-Unpublished-,300,MO,ICM,IBN,INA:f15.n5061.z2.binkp.net
Host,5075,Net_Togliatti,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.subbotin.org
Hub,128,Dewy_News,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.dewy.ru
,35,FireFox_Station,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.subbotin.org,BEER:stout,BEER:sour_ale,BEER:strong_ale
,37,Warlock_BBS,Togliatti,Andrew_Komardin,-Unpublished-,300,MO,ICM,IBN,INA:fido.warlocktlt.ru
Host,5076,YaNAO_Net,Noviy_Urengoy,Andrew_Rogov,-Unpublished-,300,MO,IBN,ICM,INA:178.216.154.110,#20
,207,SevES_TE,Noviy_Urengoy,Andrew_Rogov,-Unpublished-,300,MO,IBN,ICM,INA:207.grumbler.org,#20
Host,5095,Podolsk_Net,Podolsk_Russia,Sergey_V._Efimoff,-Unpublished-,300,MO,ICM,IBN,INA:n5095.stabilis.ru
Host,5097,Night_Flame,Ukhta,Tema_Zelikin,-Unpublished-,300,ICM,IBN,INA:nightflame.info
,31,Night_Flame,Ukhta,Tema_Zelikin,-Unpublished-,300,ICM,IBN,INA:nightflame.info

32 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,200,Outpost_BBS,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,10,The_Byte_Museum,Wharton_TX,Matt_Bedynek,-Unpublished-,300,INA:ftn.bytemuseum.org,IBN,ICM,MO,MN,PING,XA
,51,bbs.bofh.it,Milano,Marco_d'Itri,-Unpublished-,300,ICM,XA,MO,IBN,IFC,ITN:60177,U,ENC
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115
,9999,R50_Hold,Moscow,Alex_Barinov,-Unpublished-,300,MO,IEM:huba715@yandex.ru,IMI,ICM
,400,Demos_Plus,Moscow,Gatekeeper,-Unpublished-,300,ICM,IBN,IFC,INA:ddt.demos.su
,806,Elinora_Station,Shchyolkovo,Sergey_Dorozhkin,-Unpublished-,9600,XW,MO,ICM,ITN:60177,IFC:60179,IBN:24554,INA:93.123.250.176
,921,Abdulla_Tukaew's_Mail_Station,Moscow,Andrew_Savin,-Unpublished-,300,ICM,IBN,INA:fido.bibirevo.net,INA:f921.n5020.z2.binkp.net
,1313,fido.stabilis.ru,Moscow,Sergey_V._Efimoff,-Unpublished-,300,ICM,IBN,INA:fido.stabilis.ru
,9696,SDS,Moscow,Alexander_N_Skovpen,-Unpublished-,300,XX,ICM,IBN,INA:skovpen.org
,828,f828.n5020.z2.binkp.net,Moscow,Kirill_Temnenkov,-Unpublished-,300,ICM,IBN,INA:f828.n5020.z2.binkp.net,U,ENC
,8086,Z80_Station,Moscow,Pavel_Osipov,-Unpublished-,300,MO,IBN,ICM,INA:f8086.n5020.z2.binkp.net
Hub,5020,Freezer,Moscow,Alex_Barinov,-Unpublished-,300,MO,ICM,IBN,INA:fido.hubahuba.su,IEM:hubahuba@infoline.su,ITX,IMI
Host,5021,Tver_Net,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru,U,NC
Hub,29,All-Privet,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru,U,ENC
,5021,Net5021_Netmail_Gate,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru
,12,T-Station,Kaluga,Alexander_Fyodorov,-Unpublished-,300,ICM,IFC,IBN,INA:62.148.154.95
Host,5029,Ryazan_Net,Ryazan,Alexey_Bugrov,-Unpublished-,300,ICM,IBN,INA:ftn.avblabs.ru
,9,The_Power_of_Music_2,Ryazan,Ilya_Katargin,-Unpublished-,300,ICM,IBN,INA:ftn.astcrg.ru
,32,AVB_Labs_BBS,Ryazan,Alexey_Bugrov,-Unpublished-,300,ICM,IBN,INA:ftn.avblabs.ru,U,NC
,7,Wayfarer,Stary_Oscol,Evgeny_Vetrov,-Unpublished-,300,ICM,IBN,INA:smekal.ru,U,NPK
Host,5061,Rostov_Net,Rostov-on-Don,Eugene_Gladchenko,-Unpublished-,300,MO,ICM,IBN,INA:f15.n5061.z2.binkp.net
Host,5075,Net_Togliatti,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.subbotin.org
Hub,128,Dewy_News,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.dewy.ru
,35,FireFox_Station,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.subbotin.org,BEER:stout,BEER:sour_ale,BEER:strong_ale
,37,Warlock_BBS,Togliatti,Andrew_Komardin,-Unpublished-,300,MO,ICM,IBN,INA:fido.warlocktlt.ru
Host,5076,YaNAO_Net,Noviy_Urengoy,Andrew_Rogov,-Unpublished-,300,MO,IBN,ICM,INA:178.216.154.110,#20
,207,SevES_TE,Noviy_Urengoy,Andrew_Rogov,-Unpublished-,300,MO,IBN,ICM,INA:207.grumbler.org,#20
Host,5095,Podolsk_Net,Podolsk_Russia,Sergey_V._Efimoff,-Unpublished-,300,MO,ICM,IBN,INA:n5095.stabilis.ru
Host,5097,Night_Flame,Ukhta,Tema_Zelikin,-Unpublished-,300,ICM,IBN,INA:nightflame.info
,31,Night_Flame,Ukhta,Tema_Zelikin,-Unpublished-,300,ICM,IBN,INA:nightflame.info

32 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,200,Outpost_BBS,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,10,The_Byte_Museum,Wharton_TX,Matt_Bedynek,-Unpublished-,300,INA:ftn.bytemuseum.org,IBN,ICM,MO,MN,PING,XA
,51,bbs.bofh.it,Milano,Marco_d'Itri,-Unpublished-,300,ICM,XA,MO,IBN,IFC,ITN:60177,U,ENC
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115
,9999,R50_Hold,Moscow,Alex_Barinov,-Unpublished-,300,MO,IEM:huba715@yandex.ru,IMI,ICM
,400,Demos_Plus,Moscow,Gatekeeper,-Unpublished-,300,ICM,IBN,IFC,INA:ddt.demos.su
,806,Elinora_Station,Shchyolkovo,Sergey_Dorozhkin,-Unpublished-,9600,XW,MO,ICM,ITN:60177,IFC:60179,IBN:24554,INA:93.123.250.176
,921,Abdulla_Tukaew's_Mail_Station,Moscow,Andrew_Savin,-Unpublished-,300,ICM,IBN,INA:fido.bibirevo.net,INA:f921.n5020.z2.binkp.net
,1313,fido.stabilis.ru,Moscow,Sergey_V._Efimoff,-Unpublished-,300,ICM,IBN,INA:fido.stabilis.ru
,9696,SDS,Moscow,Alexander_N_Skovpen,-Unpublished-,300,XX,ICM,IBN,INA:skovpen.org
,828,f828.n5020.z2.binkp.net,Moscow,Kirill_Temnenkov,-Unpublished-,300,ICM,IBN,INA:f828.n5020.z2.binkp.net,U,ENC
,8086,Z80_Station,Moscow,Pavel_Osipov,-Unpublished-,300,MO,IBN,ICM,INA:f8086.n5020.z2.binkp.net
Hub,5020,Freezer,Moscow,Alex_Barinov,-Unpublished-,300,MO,ICM,IBN,INA:fido.hubahuba.su,IEM:hubahuba@infoline.su,ITX,IMI
Host,5021,Tver_Net,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru,U,NC
Hub,29,All-Privet,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru,U,ENC
,5021,Net5021_Netmail_Gate,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru
,12,T-Station,Kaluga,Alexander_Fyodorov,-Unpublished-,300,ICM,IFC,IBN,INA:62.148.154.95
Host,5029,Ryazan_Net,Ryazan,Alexey_Bugrov,-Unpublished-,300,ICM,IBN,INA:ftn.avblabs.ru
,9,The_Power_of_Music_2,Ryazan,Ilya_Katargin,-Unpublished-,300,ICM,IBN,INA:ftn.astcrg.ru
,32,AVB_Labs_BBS,Ryazan,Alexey_Bugrov,-Unpublished-,300,ICM,IBN,INA:ftn.avblabs.ru,U,NC
,7,Wayfarer,Stary_Oscol,Evgeny_Vetrov,-Unpublished-,300,ICM,IBN,INA:smekal.ru,U,NPK
Host,5061,Rostov_Net,Rostov-on-Don,Eugene_Gladchenko,-Unpublished-,300,MO,ICM,IBN,INA:f15.n5061.z2.binkp.net
Host,5075,Net_Togliatti,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.subbotin.org
Hub,128,Dewy_News,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.dewy.ru
,35,FireFox_Station,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.subbotin.org,BEER:stout,BEER:sour_ale,BEER:strong_ale
,37,Warlock_BBS,Togliatti,Andrew_Komardin,-Unpublished-,300,MO,ICM,IBN,INA:fido.warlocktlt.ru
Host,5076,YaNAO_Net,Noviy_Urengoy,Andrew_Rogov,-Unpublished-,300,MO,IBN,ICM,INA:178.216.154.110,#20
,207,SevES_TE,Noviy_Urengoy,Andrew_Rogov,-Unpublished-,300,MO,IBN,ICM,INA:207.grumbler.org,#20
Host,5095,Podolsk_Net,Podolsk_Russia,Sergey_V._Efimoff,-Unpublished-,300,MO,ICM,IBN,INA:n5095.stabilis.ru
Host,5097,Night_Flame,Ukhta,Tema_Zelikin,-Unpublished-,300,ICM,IBN,INA:nightflame.info
,31,Night_Flame,Ukhta,Tema_Zelikin,-Unpublished-,300,ICM,IBN,INA:nightflame.info

32 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,200,Outpost_BBS,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,10,The_Byte_Museum,Wharton_TX,Matt_Bedynek,-Unpublished-,300,INA:ftn.bytemuseum.org,IBN,ICM,MO,MN,PING,XA
,51,bbs.bofh.it,Milano,Marco_d'Itri,-Unpublished-,300,ICM,XA,MO,IBN,IFC,ITN:60177,U,ENC
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115
,9999,R50_Hold,Moscow,Alex_Barinov,-Unpublished-,300,MO,IEM:huba715@yandex.ru,IMI,ICM
,400,Demos_Plus,Moscow,Gatekeeper,-Unpublished-,300,ICM,IBN,IFC,INA:ddt.demos.su
,806,Elinora_Station,Shchyolkovo,Sergey_Dorozhkin,-Unpublished-,9600,XW,MO,ICM,ITN:60177,IFC:60179,IBN:24554,INA:93.123.250.176
,921,Abdulla_Tukaew's_Mail_Station,Moscow,Andrew_Savin,-Unpublished-,300,ICM,IBN,INA:fido.bibirevo.net,INA:f921.n5020.z2.binkp.net
,1313,fido.stabilis.ru,Moscow,Sergey_V._Efimoff,-Unpublished-,300,ICM,IBN,INA:fido.stabilis.ru
,9696,SDS,Moscow,Alexander_N_Skovpen,-Unpublished-,300,XX,ICM,IBN,INA:skovpen.org
,828,f828.n5020.z2.binkp.net,Moscow,Kirill_Temnenkov,-Unpublished-,300,ICM,IBN,INA:f828.n5020.z2.binkp.net,U,ENC
,8086,Z80_Station,Moscow,Pavel_Osipov,-Unpublished-,300,MO,IBN,ICM,INA:f8086.n5020.z2.binkp.net
Hub,5020,Freezer,Moscow,Alex_Barinov,-Unpublished-,300,MO,ICM,IBN,INA:fido.hubahuba.su,IEM:hubahuba@infoline.su,ITX,IMI
Host,5021,Tver_Net,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru,U,NC
Hub,29,All-Privet,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru,U,ENC
,5021,Net5021_Netmail_Gate,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru
,12,T-Station,Kaluga,Alexander_Fyodorov,-Unpublished-,300,ICM,IFC,IBN,INA:62.148.154.95
Host,5029,Ryazan_Net,Ryazan,Alexey_Bugrov,-Unpublished-,300,ICM,IBN,INA:ftn.avblabs.ru
,9,The_Power_of_Music_2,Ryazan,Ilya_Katargin,-Unpublished-,300,ICM,IBN,INA:ftn.astcrg.ru
,32,AVB_Labs_BBS,Ryazan,Alexey_Bugrov,-Unpublished-,300,ICM,IBN,INA:ftn.avblabs.ru,U,NC
,7,Wayfarer,Stary_Oscol,Evgeny_Vetrov,-Unpublished-,300,ICM,IBN,INA:smekal.ru,U,NPK
Host,5061,Rostov_Net,Rostov-on-Don,Eugene_Gladchenko,-Unpublished-,300,MO,ICM,IBN,INA:f15.n5061.z2.binkp.net
Host,5075,Net_Togliatti,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.subbotin.org
Hub,128,Dewy_News,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.dewy.ru
,35,FireFox_Station,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.subbotin.org,BEER:stout,BEER:sour_ale,BEER:strong_ale
,37,Warlock_BBS,Togliatti,Andrew_Komardin,-Unpublished-,300,MO,ICM,IBN,INA:fido.warlocktlt.ru
Host,5076,YaNAO_Net,Noviy_Urengoy,Andrew_Rogov,-Unpublished-,300,MO,IBN,ICM,INA:178.216.154.110,#20
,207,SevES_TE,Noviy_Urengoy,Andrew_Rogov,-Unpublished-,300,MO,IBN,ICM,INA:207.grumbler.org,#20
Host,5095,Podolsk_Net,Podolsk_Russia,Sergey_V._Efimoff,-Unpublished-,300,MO,ICM,IBN,INA:n5095.stabilis.ru
Host,5097,Night_Flame,Ukhta,Tema_Zelikin,-Unpublished-,300,ICM,IBN,INA:nightflame.info
,31,Night_Flame,Ukhta,Tema_Zelikin,-Unpublished-,300,ICM,IBN,INA:nightflame.info

32 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115
,9999,R50_Hold,Moscow,Alex_Barinov,-Unpublished-,300,MO,IEM:huba715@yandex.ru,IMI,ICM
,400,Demos_Plus,Moscow,Gatekeeper,-Unpublished-,300,ICM,IBN,IFC,INA:ddt.demos.su
,806,Elinora_Station,Shchyolkovo,Sergey_Dorozhkin,-Unpublished-,9600,XW,MO,ICM,ITN:60177,IFC:60179,IBN:24554,INA:93.123.250.176
,921,Abdulla_Tukaew's_Mail_Station,Moscow,Andrew_Savin,-Unpublished-,300,ICM,IBN,INA:fido.bibirevo.net,INA:f921.n5020.z2.binkp.net
,1313,fido.stabilis.ru,Moscow,Sergey_V._Efimoff,-Unpublished-,300,ICM,IBN,INA:fido.stabilis.ru
,9696,SDS,Moscow,Alexander_N_Skovpen,-Unpublished-,300,XX,ICM,IBN,INA:skovpen.org
,828,f828.n5020.z2.binkp.net,Moscow,Kirill_Temnenkov,-Unpublished-,300,ICM,IBN,INA:f828.n5020.z2.binkp.net,U,ENC
,8086,Z80_Station,Moscow,Pavel_Osipov,-Unpublished-,300,MO,IBN,ICM,INA:f8086.n5020.z2.binkp.net
Hub,5020,Freezer,Moscow,Alex_Barinov,-Unpublished-,300,MO,ICM,IBN,INA:fido.hubahuba.su,IEM:hubahuba@infoline.su,ITX,IMI
Host,5021,Tver_Net,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru,U,NC
Hub,29,All-Privet,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru,U,ENC
,5021,Net5021_Netmail_Gate,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru
,12,T-Station,Kaluga,Alexander_Fyodorov,-Unpublished-,300,ICM,IFC,IBN,INA:62.148.154.95
Host,5029,Ryazan_Net,Ryazan,Alexey_Bugrov,-Unpublished-,300,ICM,IBN,INA:ftn.avblabs.ru
,9,The_Power_of_Music_2,Ryazan,Ilya_Katargin,-Unpublished-,300,ICM,IBN,INA:ftn.astcrg.ru
,32,AVB_Labs_BBS,Ryazan,Alexey_Bugrov,-Unpublished-,300,ICM,IBN,INA:ftn.avblabs.ru,U,NC
,7,Wayfarer,Stary_Oscol,Evgeny_Vetrov,-Unpublished-,300,ICM,IBN,INA:smekal.ru,U,NPK
Host,5061,Rostov_Net,Rostov-on-Don,Eugene_Gladchenko,-Unpublished-,300,MO,ICM,IBN,INA:f15.n5061.z2.binkp.net
Host,5075,Net_Togliatti,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.subbotin.org
Hub,128,Dewy_News,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.dewy.ru
,35,FireFox_Station,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.subbotin.org,BEER:stout,BEER:sour_ale,BEER:strong_ale
,37,Warlock_BBS,Togliatti,Andrew_Komardin,-Unpublished-,300,MO,ICM,IBN,INA:fido.warlocktlt.ru
Host,5076,YaNAO_Net,Noviy_Urengoy,Andrew_Rogov,-Unpublished-,300,MO,IBN,ICM,INA:178.216.154.110,#20
,207,SevES_TE,Noviy_Urengoy,Andrew_Rogov,-Unpublished-,300,MO,IBN,ICM,INA:207.grumbler.org,#20
Host,5095,Podolsk_Net,Podolsk_Russia,Sergey_V._Efimoff,-Unpublished-,300,MO,ICM,IBN,INA:n5095.stabilis.ru
Host,5097,Night_Flame,Ukhta,Tema_Zelikin,-Unpublished-,300,ICM,IBN,INA:nightflame.info
,31,Night_Flame,Ukhta,Tema_Zelikin,-Unpublished-,300,ICM,IBN,INA:nightflame.info

29 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hi All,

On 2025-07-30 12:00:01, Michiel van der Vlist wrote to you:

MvdV> The ICM flag was meant as a transition mechanism for accomodating
MvdV> nodes that were running CM for the IP part and non CM for the
MvdV> POTS/ISDN part.

MvdV> See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

MvdV> The CM flag implies ICM: ICM should not be used unless CM is impossible.

MvdV> So IP only nodes should carry the CM flag, not the ICM flag.

MvdV> This is a list of nodes with a misplaced ICM flag:

The following systems are no longer in this report:

,200,Outpost_BBS,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,10,The_Byte_Museum,Wharton_TX,Matt_Bedynek,-Unpublished-,300,INA:ftn.bytemuseum.org,IBN,ICM,MO,MN,PING,XA
,51,bbs.bofh.it,Milano,Marco_d'Itri,-Unpublished-,300,ICM,XA,MO,IBN,IFC,ITN:60177,U,ENC

The first 2 had the ICM changed to CM. The latter had the ICM just removed...


Bye, Wilfred.

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

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115
,9999,R50_Hold,Moscow,Alex_Barinov,-Unpublished-,300,MO,IEM:huba715@yandex.ru,IMI,ICM
,400,Demos_Plus,Moscow,Gatekeeper,-Unpublished-,300,ICM,IBN,IFC,INA:ddt.demos.su
,806,Elinora_Station,Shchyolkovo,Sergey_Dorozhkin,-Unpublished-,9600,XW,MO,ICM,ITN:60177,IFC:60179,IBN:24554,INA:93.123.250.176
,921,Abdulla_Tukaew's_Mail_Station,Moscow,Andrew_Savin,-Unpublished-,300,ICM,IBN,INA:fido.bibirevo.net,INA:f921.n5020.z2.binkp.net
,1313,fido.stabilis.ru,Moscow,Sergey_V._Efimoff,-Unpublished-,300,ICM,IBN,INA:fido.stabilis.ru
,9696,SDS,Moscow,Alexander_N_Skovpen,-Unpublished-,300,XX,ICM,IBN,INA:skovpen.org
,828,f828.n5020.z2.binkp.net,Moscow,Kirill_Temnenkov,-Unpublished-,300,ICM,IBN,INA:f828.n5020.z2.binkp.net,U,ENC
,8086,Z80_Station,Moscow,Pavel_Osipov,-Unpublished-,300,MO,IBN,ICM,INA:f8086.n5020.z2.binkp.net
Hub,5020,Freezer,Moscow,Alex_Barinov,-Unpublished-,300,MO,ICM,IBN,INA:fido.hubahuba.su,IEM:hubahuba@infoline.su,ITX,IMI
Host,5021,Tver_Net,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru,U,NC
Hub,29,All-Privet,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru,U,ENC
,5021,Net5021_Netmail_Gate,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru
,12,T-Station,Kaluga,Alexander_Fyodorov,-Unpublished-,300,ICM,IFC,IBN,INA:62.148.154.95
Host,5029,Ryazan_Net,Ryazan,Alexey_Bugrov,-Unpublished-,300,ICM,IBN,INA:ftn.avblabs.ru
,9,The_Power_of_Music_2,Ryazan,Ilya_Katargin,-Unpublished-,300,ICM,IBN,INA:ftn.astcrg.ru
,32,AVB_Labs_BBS,Ryazan,Alexey_Bugrov,-Unpublished-,300,ICM,IBN,INA:ftn.avblabs.ru,U,NC
,7,Wayfarer,Stary_Oscol,Evgeny_Vetrov,-Unpublished-,300,ICM,IBN,INA:smekal.ru,U,NPK
Host,5061,Rostov_Net,Rostov-on-Don,Eugene_Gladchenko,-Unpublished-,300,MO,ICM,IBN,INA:f15.n5061.z2.binkp.net
Host,5075,Net_Togliatti,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.subbotin.org
Hub,128,Dewy_News,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.dewy.ru
,35,FireFox_Station,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.subbotin.org,BEER:stout,BEER:sour_ale,BEER:strong_ale
,37,Warlock_BBS,Togliatti,Andrew_Komardin,-Unpublished-,300,MO,ICM,IBN,INA:fido.warlocktlt.ru
Host,5076,YaNAO_Net,Noviy_Urengoy,Andrew_Rogov,-Unpublished-,300,MO,IBN,ICM,INA:178.216.154.110,#20
,207,SevES_TE,Noviy_Urengoy,Andrew_Rogov,-Unpublished-,300,MO,IBN,ICM,INA:207.grumbler.org,#20
Host,5095,Podolsk_Net,Podolsk_Russia,Sergey_V._Efimoff,-Unpublished-,300,MO,ICM,IBN,INA:n5095.stabilis.ru
Host,5097,Night_Flame,Ukhta,Tema_Zelikin,-Unpublished-,300,ICM,IBN,INA:nightflame.info
,31,Night_Flame,Ukhta,Tema_Zelikin,-Unpublished-,300,ICM,IBN,INA:nightflame.info

29 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115
,9999,R50_Hold,Moscow,Alex_Barinov,-Unpublished-,300,MO,IEM:huba715@yandex.ru,IMI,ICM
,400,Demos_Plus,Moscow,Gatekeeper,-Unpublished-,300,ICM,IBN,IFC,INA:ddt.demos.su
,806,Elinora_Station,Shchyolkovo,Sergey_Dorozhkin,-Unpublished-,9600,XW,MO,ICM,ITN:60177,IFC:60179,IBN:24554,INA:93.123.250.176
,921,Abdulla_Tukaew's_Mail_Station,Moscow,Andrew_Savin,-Unpublished-,300,ICM,IBN,INA:fido.bibirevo.net,INA:f921.n5020.z2.binkp.net
,1313,fido.stabilis.ru,Moscow,Sergey_V._Efimoff,-Unpublished-,300,ICM,IBN,INA:fido.stabilis.ru
,9696,SDS,Moscow,Alexander_N_Skovpen,-Unpublished-,300,XX,ICM,IBN,INA:skovpen.org
,828,f828.n5020.z2.binkp.net,Moscow,Kirill_Temnenkov,-Unpublished-,300,ICM,IBN,INA:f828.n5020.z2.binkp.net,U,ENC
,8086,Z80_Station,Moscow,Pavel_Osipov,-Unpublished-,300,MO,IBN,ICM,INA:f8086.n5020.z2.binkp.net
Hub,5020,Freezer,Moscow,Alex_Barinov,-Unpublished-,300,MO,ICM,IBN,INA:fido.hubahuba.su,IEM:hubahuba@infoline.su,ITX,IMI
Host,5021,Tver_Net,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru,U,NC
Hub,29,All-Privet,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru,U,ENC
,5021,Net5021_Netmail_Gate,Tver,Yuri_Kosivtsov,-Unpublished-,300,MO,ICM,IBN,INA:kosivtsov.ru
,12,T-Station,Kaluga,Alexander_Fyodorov,-Unpublished-,300,ICM,IFC,IBN,INA:62.148.154.95
Host,5029,Ryazan_Net,Ryazan,Alexey_Bugrov,-Unpublished-,300,ICM,IBN,INA:ftn.avblabs.ru
,9,The_Power_of_Music_2,Ryazan,Ilya_Katargin,-Unpublished-,300,ICM,IBN,INA:ftn.astcrg.ru
,32,AVB_Labs_BBS,Ryazan,Alexey_Bugrov,-Unpublished-,300,ICM,IBN,INA:ftn.avblabs.ru,U,NC
,7,Wayfarer,Stary_Oscol,Evgeny_Vetrov,-Unpublished-,300,ICM,IBN,INA:smekal.ru,U,NPK
Host,5061,Rostov_Net,Rostov-on-Don,Eugene_Gladchenko,-Unpublished-,300,MO,ICM,IBN,INA:f15.n5061.z2.binkp.net
Host,5075,Net_Togliatti,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.subbotin.org
Hub,128,Dewy_News,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.dewy.ru
,35,FireFox_Station,Togliatti,Eugene_Subbotin,-Unpublished-,300,MO,ICM,IBN,INA:fido.subbotin.org,BEER:stout,BEER:sour_ale,BEER:strong_ale
,37,Warlock_BBS,Togliatti,Andrew_Komardin,-Unpublished-,300,MO,ICM,IBN,INA:fido.warlocktlt.ru
Host,5076,YaNAO_Net,Noviy_Urengoy,Andrew_Rogov,-Unpublished-,300,MO,IBN,ICM,INA:178.216.154.110,#20
,207,SevES_TE,Noviy_Urengoy,Andrew_Rogov,-Unpublished-,300,MO,IBN,ICM,INA:207.grumbler.org,#20
Host,5095,Podolsk_Net,Podolsk_Russia,Sergey_V._Efimoff,-Unpublished-,300,MO,ICM,IBN,INA:n5095.stabilis.ru
Host,5097,Night_Flame,Ukhta,Tema_Zelikin,-Unpublished-,300,ICM,IBN,INA:nightflame.info
,31,Night_Flame,Ukhta,Tema_Zelikin,-Unpublished-,300,ICM,IBN,INA:nightflame.info

29 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hi All,

On 2025-08-20 12:00:01, Michiel van der Vlist wrote to you:

MvdV> The ICM flag was meant as a transition mechanism for accomodating
MvdV> nodes that
MvdV> were running CM for the IP part and non CM for the POTS/ISDN part.

MvdV> See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

MvdV> The CM flag implies ICM: ICM should not be used unless CM is impossible.

MvdV> So IP only nodes should carry the CM flag, not the ICM flag.

MvdV> This is a list of nodes with a misplaced ICM flag:


MvdV> ,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,
MvdV> ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE ,666,PlanStatio
MvdV> n,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

MvdV> 2 lines match

All nodes in R50 were fixed in this regard. So we went from 29 to 2 in this report!


Bye, Wilfred.

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

Hello Wilfred,

On Wednesday August 20 2025 12:53, you wrote to All:

All nodes in R50 were fixed in this regard. So we went from 29 to 2 in this report!

Yes, R50 cleaned up. Well done Alex!


Cheers, Michiel

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

Hello All,

Wednesday August 20 2025 12:00, I wrote to you:

This is a list of nodes with a misplaced ICM flag:

,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublish ed-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE ,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN ,INA:46.63.89.115

2 lines match

The second one is in net 4624. Attempts to connect to the IP nodes in net 4624 result in a time out. Dialling the numbers of the POTS nodes results in a message to the effect of "this number is not in use". Net 4624 is dead. Has been for a long time. It should be removed from the nodelist.


Cheers, Michiel

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

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello Michiel,

On Wednesday October 08 2025 12:00, I wrote to All:

,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN ,INA:46.63.89.115

That's 4624/666

Net 4624 is dead. Dialling the telephone numbers result in a recording that roughly translates to: "this number is not in use". Attempts to make a binkp connect result in a time out.

RC46 does not respond to netmail or e-mail.


Cheers, Michiel

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

Michiel van der Vlist wrote to Michiel van der Vlist <=-

,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN ,INA:46.63.89.115

That's 4624/666

Net 4624 is dead. Dialling the telephone numbers result in a recording that roughly translates to: "this number is not in use". Attempts to
make a binkp connect result in a time out.

RC46 does not respond to netmail or e-mail.

Sounds like Z2C should be firing some people.

Then again, he can't even fix his own nodelist (Zone) segment (re:
2:2/29).



... He does the work of 3 Men...Moe, Larry & Curly
=== MultiMail/Linux v0.52
--- SBBSecho 3.29-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)

Hello Dan,

On Wednesday October 08 2025 22:00, you wrote to me:

Net 4624 is dead. Dialling the telephone numbers result in a
recording that roughly translates to: "this number is not in
use". Attempts to make a binkp connect result in a time out.

RC46 does not respond to netmail or e-mail.

Sounds like Z2C should be firing some people.

Just firing people is not going to solve the problem. Finding replacements willing and able to do the job AND acceptable to all parties concerned in a country at war and partly occupied is next to impossible...


Cheers, Michiel

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

Michiel van der Vlist wrote to Dan Clough <=-

Net 4624 is dead. Dialling the telephone numbers result in a
recording that roughly translates to: "this number is not in
use". Attempts to make a binkp connect result in a time out.

RC46 does not respond to netmail or e-mail.

Sounds like Z2C should be firing some people.

Just firing people is not going to solve the problem. Finding replacements willing and able to do the job AND acceptable to all
parties concerned in a country at war and partly occupied is next to impossible...

Okay, let's do nothing then.

If we're going to do nothing, why bother mentioning the disfunction at
all?

Doing nothing fixes nothing. Firing people and *trying* to replace them
may fix everything. But... let's do nothing. It's easier that way.




... Pros are those who do their jobs well, even when they don't feel like it. === MultiMail/Linux v0.52
--- SBBSecho 3.29-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)

Hello Dan,

On Thursday October 09 2025 21:39, you wrote to me:

RC46 does not respond to netmail or e-mail.

Sounds like Z2C should be firing some people.

Just firing people is not going to solve the problem. Finding
replacements willing and able to do the job AND acceptable to
all parties concerned in a country at war and partly occupied is
next to impossible...

"next to impossible" != "impossible"

Okay, let's do nothing then.

Your idea, not mine.

If we're going to do nothing, why bother mentioning the disfunction at
all?

I do not propose "we" do nothing.

Doing nothing fixes nothing.

Then why propose it?

Firing people and *trying* to replace them may fix everything.

That's the wrong order. Replacements have to be found before firing the ones in position.

Fixing the problem of a disfunctional RC is obviously the job of the ZC. I was just pointing out the hurdles in this particular situation. Maybe the ZC could place the region in custody. For starters he could remove the nets that are obviously dead. (4614 and 4624)

And move Moldova (net 469) out of region 46. It is not enirely dead. The host is gone but 469/122 is still on-line. He could be moved to Region 56. (Z2 catch all)


Cheers, Michiel

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

Michiel van der Vlist wrote to Dan Clough <=-

RC46 does not respond to netmail or e-mail.

Sounds like Z2C should be firing some people.

Just firing people is not going to solve the problem. Finding
replacements willing and able to do the job AND acceptable to
all parties concerned in a country at war and partly occupied is
next to impossible...

"next to impossible" != "impossible"

You're replying to what YOU said, not what I said.

Okay, let's do nothing then.

Your idea, not mine.

Maybe all you Euro-boys are like this? This sounds like the twisting, redirecting, diversionary tactics of Beeeeeorn or Ward.

If we're going to do nothing, why bother mentioning the disfunction at
all?

I do not propose "we" do nothing.

Well, yes, you did.

Doing nothing fixes nothing.

Then why propose it?

It was /sarcasm/. I guessed you missed that.

Firing people and *trying* to replace them may fix everything.

That's the wrong order. Replacements have to be found before firing the ones in position.

No, they don't. You lose nothing by firing non-existant people. Fire
them and then offer the job to someone.

Fixing the problem of a disfunctional RC is obviously the job of the
ZC.

Yup, as I said. But he does nothing, as usual. Perhaps he's the one
that needs to be fired.

I was just pointing out the hurdles in this particular situation.
Maybe the ZC could place the region in custody. For starters he could remove the nets that are obviously dead. (4614 and 4624)

Sure, except for the fact that the ZC doesn't do his job.

And move Moldova (net 469) out of region 46. It is not enirely dead.
The host is gone but 469/122 is still on-line. He could be moved to Region 56. (Z2 catch all)

Sure, except..... well, you know.

I am just pointing out that there are TWO problems here - a non-existant
RC, and an (effectively) non-existant ZC.



... Apathy Error: Strike any key...or none, for that matter.
=== MultiMail/Linux v0.52
--- SBBSecho 3.29-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)

Hello Dan,

On Friday October 10 2025 14:48, you wrote to me:

Sounds like Z2C should be firing some people.

Just firing people is not going to solve the problem. Finding
replacements willing and able to do the job AND acceptable to
all parties concerned in a country at war and partly occupied
is next to impossible...

"next to impossible" != "impossible"

You're replying to what YOU said, not what I said.

I am clearyfing what I wrote in attempt to point out what you seemed to have missed. That clearyfication is addressed TO YOU.

Okay, let's do nothing then.

Your idea, not mine.

Maybe all you Euro-boys are like this? This sounds like the twisting, redirecting, diversionary tactics of Beeeeeorn or Ward.

"Euro-boys"? "Beeeeeorn"? If you are refering to the Fidonews Editor, his name is Björn. If you continue in this ad hominem way I will stop responding to you.

Other that that: it was YOU that wrote "let's do nothing", not me.

If we're going to do nothing, why bother mentioning the disfunction
at all?

I do not propose "we" do nothing.

Well, yes, you did.

No, I did not. I was merely pointing out some of the hurdles that are on he road, I did not write that we do nothing. You read what you wanted to read, not what was there.

Doing nothing fixes nothing.

Then why propose it?

It was /sarcasm/. I guessed you missed that.

Sarcasm is best avoided in a medium that crosses language barriers, Too easy to lose in translation.

Firing people and *trying* to replace them may fix everything.

That's the wrong order. Replacements have to be found before
firing the ones in position.

No, they don't. You lose nothing by firing non-existant people. Fire them and then offer the job to someone.

That does not work in Fidonet where jobs are linked to a chalm in a technical chain. Removing a region entry or replacing it with a non-functional dummy will break the nodelist.

Fixing the problem of a disfunctional RC is obviously the job of
the ZC.

Yup, as I said. But he does nothing, as usual.

That you do not see it does not mean it is not there.

Perhaps he's the one that needs to be fired.

Firing the ZC does not solve the problem of a non functional RC.

I was just pointing out the hurdles in this particular
situation. Maybe the ZC could place the region in custody. For
starters he could remove the nets that are obviously dead. (4614
and 4624)

Sure, except for the fact that the ZC doesn't do his job.

Ever heard of silent diplomacy?

And move Moldova (net 469) out of region 46. It is not enirely
dead. The host is gone but 469/122 is still on-line. He could be
moved to Region 56. (Z2 catch all)

Sure, except..... well, you know.

No, I do not know.

I am just pointing out that there are TWO problems here - a
non-existant RC, and an (effectively) non-existant ZC.

ZC2 exists and responds to netmail.


Cheers, Michiel

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

Michiel van der Vlist wrote to Dan Clough <=-

Firing people and *trying* to replace them may fix everything.

That's the wrong order. Replacements have to be found before
firing the ones in position.

No, they don't. You lose nothing by firing non-existant people. Fire them and then offer the job to someone.

That does not work in Fidonet where jobs are linked to a chalm in a technical chain. Removing a region entry or replacing it with a non-functional dummy will break the nodelist.

It's already broken. What would removing non-existant nodes/nets hurt? They're already not reachable. Rather than break the nodelist, this
would bring it closer to being correct/accurate. Isn't that the goal?

Fixing the problem of a disfunctional RC is obviously the job of
the ZC.

Yup, as I said. But he does nothing, as usual.

That you do not see it does not mean it is not there.

Well, how long has this RC been disfunctional? Seems like it's been
quite a long time to me. What corrective actions has the ZC taken that
I can't see?

Perhaps he's the one that needs to be fired.

Firing the ZC does not solve the problem of a non functional RC.

It might, if the replacement ZC fired the non functional RC and replaced
him.

I was just pointing out the hurdles in this particular
situation. Maybe the ZC could place the region in custody. For
starters he could remove the nets that are obviously dead. (4614
and 4624)

Sure, except for the fact that the ZC doesn't do his job.

Ever heard of silent diplomacy?

Sure, it's another one of those non-functional idealogical fantasies
that doesn't actually work. It also takes forever, and in the end
nothing changes, it just takes..... forever to know it.

And move Moldova (net 469) out of region 46. It is not enirely
dead. The host is gone but 469/122 is still on-line. He could be
moved to Region 56. (Z2 catch all)

Sure, except..... well, you know.

No, I do not know.

See above regarding "the fact that the ZC doesn't do his job".

I am just pointing out that there are TWO problems here - a
non-existant RC, and an (effectively) non-existant ZC.

ZC2 exists and responds to netmail.

Perhaps, but would you agree that there's more to the ZC job than simply responding to netmail?

Do you think if I netmailed him, he could explain the 2:2/29 nodelist
entry that he doesn't fix? Can YOU explain that one to me?




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

Hi Michiel!

Thursday October 09 2025 16:10, you wrote to Dan Clough:

Net 4624 is dead. Dialling the telephone numbers result in a
recording that roughly translates to: "this number is not in
use". Attempts to make a binkp connect result in a time out.

RC46 does not respond to netmail or e-mail.

Sounds like Z2C should be firing some people.

MvdV> Just firing people is not going to solve the problem.

In the case of P46, it will be just a firing people.

MvdV> Finding replacements willing and able to do the job

That problem have no solution for now.

MvdV> AND acceptable to all parties concerned in a country at war and
MvdV> partly occupied is next to impossible...

It was acceptable a few years ago and I don't see the problem for now. However, the most point is no connection ability across r46.

Have a nice night.
Stas Mishchenkov.

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

Hi Dan!

Thursday October 09 2025 21:39, you wrote to Michiel van der Vlist:

Net 4624 is dead. Dialling the telephone numbers result in a
recording that roughly translates to: "this number is not in
use". Attempts to make a binkp connect result in a time out.

RC46 does not respond to netmail or e-mail.

Sounds like Z2C should be firing some people.

Just firing people is not going to solve the problem. Finding
replacements willing and able to do the job AND acceptable to all
parties concerned in a country at war and partly occupied is next to
impossible...

Okay, let's do nothing then.

If we're going to do nothing, why bother mentioning the disfunction at all?

Doing nothing fixes nothing. Firing people and *trying* to replace them may fix everything. But... let's do nothing. It's easier that way.

There is a solution, but some sysops may not like it for political reasons. For this point, I fully support Ward's decision to wait for the logical conclusion of current events in the world.

Have a nice night.
Stas Mishchenkov.

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

Hi Stas,

On 2025-10-14 21:01:42, you wrote to Michiel van der Vlist:

MvdV>> AND acceptable to all parties concerned in a country at war and
MvdV>> partly occupied is next to impossible...

It was acceptable a few years ago and I don't see the problem for now. However, the most point is no connection ability across r46.

I think the none existing nets should be removed. If the RC can't/won't do it, the ZC can do it for him imho...

The remaining nets can also be moved to R56, if a (replacement) RC can't be found that is willing to do the "job".

Bye, Wilfred.

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

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello, Stas!

Tuesday October 14 2025 21:12, you wrote to Dan Clough:

reasons. For this point, I fully support Ward's decision to wait for
the logical conclusion of current events in the world.

Agree. Let's wait until Putin's death and the fall of his regime.

Best regards,
dp.

--- GoldED+/OSX 1.1.5-b20250409
* Origin: All is good in St. John's Wood (2:5001/100.1)

Hi Wilfred!

Tuesday October 14 2025 21:16, you wrote to me:

MvdV>>> AND acceptable to all parties concerned in a country at war and
MvdV>>> partly occupied is next to impossible...

It was acceptable a few years ago and I don't see the problem for now.
However, the most point is no connection ability across r46.

I think the none existing nets should be removed. If the RC can't/won't do it, the ZC can do it for him imho...

That's right. IMHO.

The remaining nets can also be moved to R56, if a (replacement) RC
can't be found that is willing to do the "job".

No. This may lead to confusion in these networks and disruption of connectivity.

Have a nice night.
Stas Mishchenkov.

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

Hi Stas,

On 22 Oct 25 08:17, Stas Mishchenkov wrote to Wilfred van Velzen:
about: "IP only nodes with ICM flag":

The remaining nets can also be moved to R56, if a (replacement) RC
can't be found that is willing to do the "job".

No. This may lead to confusion in these networks and disruption of connectivity.

I don't think that will be a big problem. The Host and nodenumbers can stay the same. Only the routing between to the hosts and the RC need to change, so the Host should be available to make changes to his config...


Wilfred.

--- FMail-W64 2.3.2.3-B20250509
* Origin: point@work (2:280/464.112)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

Wednesday February 04 2026 12:00, I wrote to you:

,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN ,INA:46.63.89.115

Net 4624 is dead. All the listed telephone numbers respond with a recorded message to the effect of "this number is not in use".

The IP nodes give a time out.

Cheers, Michiel

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

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)

Hello All,

The ICM flag was meant as a transition mechanism for accomodating nodes that were running CM for the IP part and non CM for the POTS/ISDN part.

See also: fts-5001.006 paragraph 5.11. Flag Redundancies.

The CM flag implies ICM: ICM should not be used unless CM is impossible.

So IP only nodes should carry the CM flag, not the ICM flag.

This is a list of nodes with a misplaced ICM flag:


,110,Seans_Elist_Maintainer,Johnson_City_TN_USA,Sean_Dennis,-Unpublished-,300,ICM,XX,INA:bbs.outpostbbs.net,IBN,IFC,IFT,ITN:60177,PING,TRACE
,666,PlanStation,Khmelnitsky,Vova_Dmitrishin,-Unpublished-,300,ICM,IBN,INA:46.63.89.115

2 lines match

--- Ftoolsw32 post
* Origin: Nodelist Police Station (2:280/5555)