Subj : sbbsecho and bad packets
To   : deon
From : Digital Man
Date : Sun Oct 05 2025 18:09:51

  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)

.