Re: Corrupt Message Headers
  By: Digital Man to Nightfox on Sat Mar 30 2019 09:59 pm

 >> I haven't seen that problem on my BBS with my reader, and haven't
 >> heard about this from other sysops using my reader either.  The way it
 >> marks a message as read is by loading the message header without
 >> expanded fields (using MsgBase.get_msg_header()), applying the
 >> MSG_READ attribute, and then saving the header back to the messagebase
 >> (using MsgBase.put_msg_header()). I wouldn't expect that to corrupt
 >> the header. 

 DM> It's always possible I hosed something up in a recent commit to CVS. Are
 DM> you running the latest and greatest?

I wasn't, but just now I updated to the latest binaries (built today, 3/31). 
Now I'm seeing an error with my message reader - After reading a new message to
me, my reader will add the MSG_READ attribute and save it back to the msgbase. 
With the latest binaries, I'm now seeing this error when calling
MsgBase.put_msg_header():

!JavaScript  ../xtrn/DigDist/MsgReader/DDMsgReader.js line 1529: Error: Error
-110 adding SENDERNETADDR field to message header

I wasn't seeing that error before.  I'm not sure what would cause that error. 
My reader caches the message headers (it has an array of saved message headers)
and it was applying the attribute to the cached header and then trying to save
it to the msgbase.  As a workaround, I tried the following:
- Load the message header from the messagebase (without expanded fields)
- Apply the new attribute (MSG_READ)
- Save that header back to the msgbase
However, on the first tep, when reading the header from the msgbase, it got a
null object.

Nightfox

---
 ■ Synchronet ■ Digital Distortion: digitaldistortionbbs.com
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)