Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 42529  |
|  deon to Digital Man  |
|  sbbsecho and bad packets  |
|  21 Oct 25 17:46:42  |
 TZUTC: 1100 MSGID: 51998.dove-syncdisc@12:1/2 2d5d2d70 REPLY: 55057.sync@1:103/705 2d5d2f97 PID: Synchronet 3.21a-Linux master/b7d3db6c3 Sep 28 2025 GCC 10.2.1 TID: SBBSecho 3.30-Linux master/88b423313 Sep 29 2025 GCC 12.2.0 COLS: 80 BBSID: ALTERANT CHRS: CP437 2 FORMAT: flowed NOTE: FSEditor.js v1.105 Re: sbbsecho and bad packets By: Digital Man to deon on Mon Oct 20 2025 11:04 pm Howdy, > The standard (FTS-1) only has that one definition of the DateTime field in > packets and it includes the (single) Null byte. So I don't think the > requirement of the Null byte has really ever been ambiguous. Are we reading different versions of FTS-1? http://ftsc.org/docs/fts-0001.016 I see a DateTime mentioned in B.1 (the stored message), and in C.1 (the packed message). I've been referencing to the C.1 reference all along. ...лоеп --- ю Synchronet ю AnsiTEX bringing back videotex but with ANSI * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705) SEEN-BY: 10/0 1 102/401 103/1 17 705 105/81 106/201 124/5016 128/187 SEEN-BY: 129/14 153/7715 154/110 218/0 1 215 601 610 700 840 860 880 SEEN-BY: 226/30 227/114 229/110 206 317 400 426 428 470 700 705 266/512 SEEN-BY: 280/464 291/111 301/1 320/219 322/757 342/200 396/45 460/58 SEEN-BY: 633/280 712/848 902/26 5075/35 PATH: 103/705 218/700 229/426 |
[ << oldest | < older | list | newer > | newest >> ]