We have some problems with our Blackberry users. For some of them, documents that they i've read are turing back to unread on their device. Everything is synchronise with the Notes client.
In the advanced db option, here's the info
I've read technote 1159331from IBM and few others from RIM but nothing useful.
The only thing we see right now, is the interraction with our archiving process from Symantec. This process reads every mails to see if it can be archive. We wonder if it can modify in some sort, the documents.
Subscribe to:
Post Comments (Atom)
2 comments:
Not sure if this will help you out or not but we have seen similar issues with our archiving solution. It is not in our code but rather how RIM reads the messages.
Issue: http://www.blackberry.com/btsc/microsites/search.do?cmd=displayKC&docType=kc&externalId=KB13221&sliceId=2&docTypeID=DT_SUPPORTISSUE_1_1&dialogID=77002419&stateId=1%200%2075800319
Overview
Sent items that are over seven days old are sent to the BlackBerry smartphone again.
Cause
When the BlackBerry Enterprise Server scans for new mail messages in a BlackBerry smartphone user's mail file, it checks the ModifiedDate field on the message to determine if it is new. It also performs a second check on the message's DeliveredDate field to determine if it is over seven days old. However, this field does not exist for Sent Items in Lotus Domino, so the second check is not performed.
There is a Mail Archiving tool used within the Lotus Domino messaging server. This tool may make a change to the message after sever days, which alters the ModifiedDate field. When the ModifiedDate field is updated, the BlackBerry Enterprise Server may send the message to the BlackBerry smartphone again because the second check on the DeliveredDate does not tell it that the message has already been sent.
In addition, if state database pruning removes the message document, the Sent Item is sent again.
Resolution
Upgrade to BlackBerry Enterprise Server software version 4.1.4 Maintenance Release 3 or later for Lotus Domino.
Workaround: http://www.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB03849&sliceId=SAL_Public&dialogID=43876341&stateId=1%200%2043870800
Post a Comment