TID: FMail-W32 2.1.3.7-B20170919
RFC-X-No-Archive: Yes
TZUTC: 0200
CHRS: CP850 2
MSGID: 2:280/5555 632a1b3c
REPLY: 2:341/234.1 63294cce
Hello Carlos,

On Monday September 19 2022 21:28, you wrote to Wilfred van Velzen:

 WV>> I think non-CM in combination with IBN, most of the time is an
 WV>> error in the nodelist. I never found a non-CM + IBN node that was
 WV>> actually just connectable at ZMH. And it doesn't make sense
 WV>> either.

 CN> A non-CM node doesn't have to be a ZMH-only node. As you know, it can
 CN> carry the ,Tyz flag. A sysop may not want or need to have her system
 CN> running 24 hours a day, for whatever reason.

Theoretically that is possible and a non CM binkp node is not against the
rules. But it is against common sense. Binkp connectibility requires an
internet connection and these days internet connetions are up 24/7. It takes
EFFORT to configure a binkp system for non CM operation, it strongy reduces
connectivity and there are no benefits that I can see. 

Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
 * Origin: http://www.vlist.eu (2:280/5555)
SEEN-BY: 1/123 15/0 90/1 103/705 105/81 106/201 114/705 709 120/340
SEEN-BY: 123/120 131 124/5016 129/305 331 153/757 7715 154/10 203/0
SEEN-BY: 218/700 840 220/70 221/0 6 226/17 227/114 229/110 111 112
SEEN-BY: 229/113 200 206 275 317 424 426 428 470 550 664 700 240/5832
SEEN-BY: 250/5 8 266/512 267/800 280/464 5003 5555 282/1038 292/854
SEEN-BY: 292/8125 298/25 301/1 305/3 310/31 317/3 320/219 322/757
SEEN-BY: 341/66 234 342/200 396/45 423/120 460/58 633/280 712/848
SEEN-BY: 770/1 100 340 772/210 220 230 2452/250 5019/40 5020/1042
SEEN-BY: 5053/58
PATH: 280/5555 464 770/1 317/3 229/426