Re: Corrupt Message Headers
  By: DaiTengu to Digital Man on Fri Mar 29 2019 10:59 am

 >   Re:
 >   By:  to  on Thu Mar 28 2019 01:02 am
 >
 > So, I read your reply to my message yesterday. It came up fine, with header
 > information and everything. I didn't have time to pull the data, and thought
 > to myself "I'll get back to it later".
 >
 > Today, when bringing up this message to reply to it, the message header was
 > gone. Previous issues were in dove-general, and it appears to have spread to
 > dove-syncops, now.  I wonder if maybe DDMessageReader is doing something
 > when marking the message as read? I'm not actually sure how that works.
 >
 >  DM> If you disable DDMessageReader, do you still have an issue?
 >
 >  I'm going to have to give that a shot. Thus far, I think the pattern seems
 > to be that the header disappears when the message is marked as read by the
 > recipient. I'm not 100% on that, though, I'll have to do some more digging.
 >
 >
 >  DM> Well it's certainly possible to import messages without message-IDs.
 >  DM> Perhaps if you ran "chksmb -e" you'd see a pattern with the messages
 >  DM> that are missing message-IDs and identify the cause. In any case, it's
 >  DM> not a fatal issue normally.
 >
 > here's my current chksmb -e output on dove-general and dove-syncops, the two
 > echos that I've seen the issue crop up.
 >
 > https://pastebin.com/YacRr6XV
 >
 > After that, I tried a base fixsmb on dove-syncops, and here was the output:
 >
 > [root@bbs subs]# /sbbs/exec/fixsmb dove-syncops
 >
 > FIXSMB v2.10-Linux (rev 1.46) SMBLIB 2.60 - Rebuild Synchronet Message Base
 >
 > Opening dove-syncops
 > 99%  #9698  (703F20)
 > (704020) smb_getmsghdr returned -103:
 > smb_getmsghdr corrupt message header ID (2E 33 34 08) at offset 7356448
 > 99%
 > (704120) smb_getmsghdr returned -103:
 > smb_getmsghdr corrupt message header ID (20 20 63 31) at offset 7356704
 > 99%  #9708  (705820)
 > (705920) smb_getmsghdr returned -103:
 > smb_getmsghdr corrupt message header ID (2E 33 34 08) at offset 7362848
 > 99%
 > (705A20) smb_getmsghdr returned -103:
 > smb_getmsghdr corrupt message header ID (20 20 63 31) at offset 7363104
 > 100%
 > Sorting index...
 > Re-writing index...
 >
 > Saving message base status (9716 total messages).
 > Closing message base.
 > Done.

And after that, does chksmb still report errors? If so, I recommend using
smbutil to repair the msgbase:
http://wiki.synchro.net/util:smbutil#examples

                                            digital man

This Is Spinal Tap quote #37:
David St. Hubbins: We are Spinal Tap from the UK - you must be the USA!
Norco, CA WX: 65.0°F, 40.0% humidity, 2 mph ESE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.07-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)