Environment
Novell GroupWise 8
Situation
GroupWise® enables you to retain user messages until they have been
copied from message databases to another storage location. This means
that a user cannot perform any action, such as emptying the mailbox
Trash, that results in a message being removed from the message
database before it has been copied.
For more information about Message Retention, please see: How Message Retention Works.
Sometimes users cannot purge deleted messages. There are at least two known reasons for this:
1. This can happen when a) the GroupWise Administrator or user had modified the Cleanup options to not purge items until they are backed up and b) the item has not been backed up.
2. On rare occasions, this happens when a third-party uses a GroupWise API (put_LastRetentionDate) that sets the "Modified Retention Timestamp" in the Account Object.
For more information about Message Retention, please see: How Message Retention Works.
Sometimes users cannot purge deleted messages. There are at least two known reasons for this:
1. This can happen when a) the GroupWise Administrator or user had modified the Cleanup options to not purge items until they are backed up and b) the item has not been backed up.
2. On rare occasions, this happens when a third-party uses a GroupWise API (put_LastRetentionDate) that sets the "Modified Retention Timestamp" in the Account Object.
Resolution
1. This can happen when a) the GroupWise Administrator or user had modified the Cleanup options to not purge items until they are backed up and b) the item has not been backed up.
If this is the case, and the GroupWise Administrator wants to prevent messages from being purged from the system until they are backed up, then the messages need to be backed up.
2. On rare occasions, this happens when a third-party uses a GroupWise API (put_LastRetentionDate) that sets the "Modified Retention Timestamp" in the Account Object.
If this is the case, the GroupWise Administrator will need to run the GroupWise Timestamp Utility (from 802 or later) to clear the "Modified Retention Timestamp" value.
If this is the case, and the GroupWise Administrator wants to prevent messages from being purged from the system until they are backed up, then the messages need to be backed up.
2. On rare occasions, this happens when a third-party uses a GroupWise API (put_LastRetentionDate) that sets the "Modified Retention Timestamp" in the Account Object.
If this is the case, the GroupWise Administrator will need to run the GroupWise Timestamp Utility (from 802 or later) to clear the "Modified Retention Timestamp" value.