->  WT> Hi Hector, one improvement could be the new messages flag in each
->  WT> conference to know the difference between private and public so 
-> that new  WT> messages indicated would not show when it's private and 
-> not available to  WT> you.

-> I read this four times, and I don't understand what you mean by this. 
-> :-)

-> If its not available to you, how can it be a new message?  How would
-> you know its there anyway.

-> Whats the basic problem?  Whats the "relationship" of private/public
-> in regards to NEW messges presented to you?   Are you just trying
-> to say that you want to know in the MESSAGE LIST whether is private
-> or public mail?


Covered this in another conference, when someone was posting "Reset
pointer" messages.

wcNav shows which conferences have new mail by showing the conference
name in bold. Apparently this is triggered by comparing the high message
number in the conference with the last-read marker.

However, if the only messages after your last-read marker are message
you don't have read rights to (private mail not to/from you), then when
you open the conference listed in bold there's nothing new there for you
to read. To make matters worse, the conference stays bold the next time
you log in, even if there haven't been any new mail (since there wasn't
anything you were allowed to read, your last-read marker wasn't
updated, so it's still lower than the high message number).

Improved logic would have wcNav (or the server -- whichever end does
this) compare the last-read marker to the high message number, and
*THEN* start checking to see if any of the "new" messages are visible to
this user. As soon as it finds one, it can mark the conference bold
(there's new mail that's visible to this user). If it gets to the high
message pointer without finding one (all the new messages aren't
visible to this user because they're private and he can't read private
mail), then it wouldn't mark the conference bold.
--- Platinum Xpress/Win/WINServer v3.1