>> it is possible that the two "high water mark" pointers
are being used
 >> differently... one is a high water mark that denotes the highest message
 >> you have seen... the other denotes the highest message you have read...
 >> i've run into this particular situation with the various readers i use...
 >> oh yes, i'm also speaking from a JAM message base point of view...

 DE> Ok, so how do I fix that? I have tried everything I can think
 DE> of. Ele sees that the messages are new and unread, but OLMS doesn't
 DE> want to download them.

the only thing i can think of is to see what those pointers are set to and
reset them... i don't have a tool handy that can tell you this info but i
do run into it when i mix reading JAM message areas in RA and FD's FM and
TimED...

)\/(ark