Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 8141  |
|  Wilfred van Velzen to Carlos Navarro  |
|  Re: non-CM nodes  |
|  20 Sep 22 08:40:59  |
 TID: FMail-lnx64 2.1.0.18-B20170815 RFC-X-No-Archive: Yes TZUTC: 0200 CHRS: UTF-8 2 PID: GED+LNX 1.1.5-b20161221 MSGID: 2:280/464 6329609c REPLY: 2:341/234.1 63294cce Hi Carlos, On 2022-09-19 21:28:28, you wrote to me: WV>> I think non-CM in combination with IBN, most of the time is an error WV>> in the nodelist. I never found a non-CM + IBN node that was actually WV>> just connectable at ZMH. And it doesn't make sense either. CN> A non-CM node doesn't have to be a ZMH-only node. As you know, it can carry CN> the ,Tyz flag. A sysop may not want or need to have her system running 24 CN> hours a day, for whatever reason. Either way, I have never seen this working correctly. Bye, Wilfred. --- FMail-lnx64 2.1.0.18-B20170815 * Origin: FMail development HQ (2:280/464) 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 226/17 227/114 229/110 111 112 113 SEEN-BY: 229/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 PATH: 280/464 770/1 317/3 229/426 |
[ << oldest | < older | list | newer > | newest >> ]