Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 1503  |
|  Stephen Hurd to Mike Powell  |
|  Re: Kannons and Katapults - R  |
|  06 Dec 25 22:04:19  |
 TZUTC: 0000 MSGID: 82.fido-doorgame@1:103/1 2d99deb5 REPLY: 834.f_doors@1:2320/105 2d998fab PID: Synchronet 3.21a-FreeBSD master/1c123cf4a Oct 24 2025 Clang 19.1.7 TID: SBBSecho 3.31-FreeBSD master/151b255a6 Nov 02 2025 Clang 19.1.7 BBSID: BBSDEV CHRS: ASCII 1 FORMAT: flowed NOTE: FSEditor.js v1.105 Re: Re: Kannons and Katapults - R By: Mike Powell to Stephen Hurd on Sat Dec 06 2025 11:14 am > I then used the telnet protocol to connect and I still got the same > double-CR issue I had before. So apparently it recognizes ATNETx as a valid > string but otherwise knows not what it means.... or I need to send it a > different way. It's possible that the telnet support doesn't do anything with NVT CRs, I didn't dig in too deeply into the source, just noticed that it does do at least some option negotiation and will track the current state. So likely you only need to do this if you need to accept or send character 255 (which is a special telnet character) such as for uploads and downloads. --- SBBSecho 3.31-FreeBSD * Origin: BBSDev.net - The BBS Developers Network (1:103/1) SEEN-BY: 10/0 1 102/401 103/1 17 705 105/81 106/201 124/5016 128/187 SEEN-BY: 129/14 305 153/7715 154/110 218/0 1 109 215 601 700 810 840 SEEN-BY: 218/860 880 900 226/30 227/114 229/110 112 134 200 206 307 SEEN-BY: 229/317 400 426 428 470 664 700 705 266/512 291/111 301/1 SEEN-BY: 320/219 322/757 342/200 396/45 633/280 712/848 902/26 5020/400 SEEN-BY: 5075/35 PATH: 103/1 218/700 229/426 |
[ << oldest | < older | list | newer > | newest >> ]