Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 42480  |
|  deon to Digital Man  |
|  sbbsecho and bad packets  |
|  06 Oct 25 13:07:44  |
 
TZUTC: 1100
MSGID: 51948.dove-syncdisc@12:1/2 2d49255c
REPLY: 55008.sync@1:103/705 2d4923bf
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 Sun Oct 05 2025 06:09 pm
> Looks to me like the DateTime is missing the NUL terminator:
> 00000040 79 02 79 02 00 00 00 00 30 33 20 4f 63 74 20 32 |y.y.....03 Oct
> 2| 00000050 35 20 20 30 37 3a 31 37 3a 34 37 20 41 6c 6c 00 |5 07:17:47
> All.|
>
> > Why is SBBSecho marking them bad?
>
> The sbbsecho.log should say the reason why, but it's probably the same
> reason.
I didnt think DateTime was a null terminated string? Its 20 Bytes in the
packed message header (FTS-0001.16 C.1).
"A packed message has a number of fixed length
fields followed by four null terminated strings."
(those being: to/from/subject and text are null terminated).
Or have a missed something?
...лоеп
---
ю 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 >> ]