Disappearing messages

I have users that are complaining about entire INBOX messages disappearing (which they may or may not find in the TRASH)

Originally, the mail databases were iNotes50 template, but upgraded to iNotes60.ntf when the servers were upgraded to 6.01 CF1. I’ve compacted, ran fixup, etc. I’ve created a new mail message for one user and he still sees this happen. I pulled up his new mail database on a client, and the INBOX was empty.

Any suggestions?

Subject: Disappearing messages

You are not the only one. A lot of people have been complaining about messages that disappear, or even worse : the whole Inbox that disappears.

If you check some of the other threads (search for words like replication, inbox, disappear) you’ll see plenty of people with problems related to their inbox.

I was able to get some user’s inboxes fixed by doing I-can’t-remember-what-exactly while other user’s Inbox were beyond repair…

The server upgrade went sooooo fine. I could have known the upgrade of the mailfiles would cause major problems

Litrik De Roy.

Subject: RE: Disappearing messages

We are also experiencing this problem. We only have about 30 people using iNotes right now, but we are looking to implement across the whole company. Out of the 30, 2 have seen this happen. Once person selected all documents and marked them all read. The next time he looked at his inbox, all of the messages in his inbox were in the trash. Is there some fix for this problem.

Mike

Subject: RE: Disappearing messages

I can always duplicate this by using the “Mark all as Read” feature. Sine I use an ICM and have mail databases replicating between two servers, users may hit a replica that shows messgase as RED. Besides telling users not to do the Mark-all-as-Read, I still haven’t found a good reason or answer to this problem.

Subject: RE: Disappearing messages

That is what I found as well. When I select “Mark all read”, after a little bit of time, all messages end up going to the Trash. I have tried multiple things. Does anyone know if this is fixed in a later release?