Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    SYNCHRONET    |    Rob Swindell fetishistic worship forum    |    43,341 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 42,479 of 43,341    |
|    Digital Man to deon    |
|    sbbsecho and bad packets    |
|    05 Oct 25 18:09:51    |
      TZUTC: -0700       MSGID: 55008.sync@1:103/705 2d4923bf       REPLY: 51946.dove-syncdisc@12:1/2 2d485f9b       PID: Synchronet 3.21a-Linux master/2287878bd Sep 27 2025 GCC 12.2.0       TID: SBBSecho 3.30-Linux master/88b423313 Sep 29 2025 GCC 12.2.0       COLS: 80       BBSID: VERT       CHRS: CP437 2       FORMAT: flowed       NOTE: FSEditor.js v1.105        Re: sbbsecho and bad packets        By: deon to Digital Man on Sun Oct 05 2025 11:04 pm               > Hey DM,        >        > Since updating a few days ago, I've now got a bunch of bad packet in my        > inbound, and all have been marked bad "msg-hdr".        >        > pktdump rev 1.18 - Dump FidoNet Packets        >        > Opening df43a202.msg-hdr.bad        > df43a202.msg-hdr.bad Packet Type 2e (prod: 10FF, rev: 1.9) from 3:633/280 to        > 3:633/509        > df43a202.msg-hdr.bad 00003A Corrupted Message Header (DateTime)        > df43a202.msg-hdr.bad 000658 Corrupted Message Header (DateTime)        > df43a202.msg-hdr.bad 000B83 Corrupted Message Header (DateTime)        > df43a202.msg-hdr.bad 001273 Corrupted Message Header (DateTime)        > df43a202.msg-hdr.bad 001FAC Corrupted Message Header (DateTime)        > root@alterant:/opt/sbbs/fido/inbound# pktdump df74da02.msg-hdr.bad        > pktdump rev 1.18 - Dump FidoNet Packets        >        > Opening df74da02.msg-hdr.bad        > df74da02.msg-hdr.bad Packet Type 2e (prod: 10FF, rev: 1.9) from 3:633/280 to        > 3:633/509        > df74da02.msg-hdr.bad 00003A Corrupted Message Header (DateTime)        >        > When I look at a few, it looks like SBBSecho (and pktdump) thinks they are        > bad because of DateTime, but they look ok to me:              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.       --         digital man (rob)              Rush quote #42:       Media messiahs preying on my fears, pop culture prophets playing in my ears       Norco, CA WX: 72.7øF, 63.0% humidity, 12 mph W wind, 0.00 inches rain/24hrs       --- SBBSecho 3.30-Linux        * 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 >>   ]
(c) 1994, bbs@darkrealms.ca