Re: Corrupt Message Headers
  By: Nightfox to Digital Man on Sun Mar 31 2019 05:21 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.
 DM>> Are you running the latest and greatest?

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

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

 Ni> I wasn't seeing that error before. I'm not sure what would cause that

Now that I've updated to today's binaries, I think I'm seeing the same issue as
DaiTengu now.  I read one of Vk3jed's messages to me, and after my reader
tried to mark his message as read, now the header of the message from Vk3jed
seems to be messed up.  In my reader's reader interface, now it says it's
written to 'All' instead of me, and the 'From' and 'Subject' are empty.  In my
reader's message list (where it displays the 'from', 'to', and subject, those
are empty after my reader tried to apply the 'read' attribute to the header in
the msgbase.

Nightfox

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