[nos-bbs] JNOS error tracking new messages

[Michael Fox - N6MEF]

> -----Original Message-----
> From: nos-bbs <nos-bbs-bounces at lists.tapr.org> On Behalf Of Maiko
> Langelaar
> Sent: Sunday, October 14, 2018 3:56 PM
> To: TAPR xNOS Mailing List <nos-bbs at lists.tapr.org>
> Subject: Re: [nos-bbs] JNOS error tracking new messages
> 
> 
> > (#3)>
> > A foo
> > foo: 15 messages  -  4 new
> >
> > The number of new messages appears to be determined by looking at how
> many
> > messages have ID numbers greater than the number stored next to the
> user's
> > call sign in the spool/mail/foo.usr file.
> 
> Number of new messages is calculated by going through the index and
> actually
> counting the number of messages that have NOT been read. This calculation
> is
> done each time a user accesses their mailbox.
> 
> Each message has a BM_READ bit in the message status.
> 
> The 'messages' and 'new' are 'integer' values.
> 
> The number you see in foo.usr is the last message listed/read, and it is
> parsed as a 'long integer'.

Sorry, I should have been more clear.  In the problem I reported, I'm
referring to public/shared mailboxes, i.e. those listed in spool/areas.  In
that case, I don't know if the index plays role in tracking per-user read
status, since I don't know what info is in the index.  

BUT, it's easy to show (I previously provided examples), that the messages
marked read or unread are based on the number stored with the
userid/callsign in <mailbox>.usr.  This is very easy to duplicate by simply
changing the numbers in <mailbox>.usr.

Michael
N6MEF