Certain users can not empty items from the trash

  • 7014553
  • 12-Feb-2014
  • 12-Feb-2014

Environment

Novell GroupWise 2012
Novell GroupWise 8

Situation

Certain users can not empty items from the trash. Email retention is enabled and running.
 
Items reappear after they have been deleted.
 
The digest retention keeps reverting back to 1970.
 
User: testacct
  Backup Time:             Thursday,  5 November 2009 6:44pm
  Restore Time:            unknown
  Digest Retention Time:   Thursday,  1 January 1970 12:00am
  Modified Retention Time: unknown
 
Mail can be deleted if the digest retention timestamp is updated manually using the gwtmstmp.exe utility.
 
gwtmstmp.exe /p c:\po /s /n /u-testacct

Successfully set retention timestamp for all users on post office at c:\po
 
gwtmstmp.exe /p c:\po /u-testacct
User: testacct
  Backup Time:             Thursday,  5 November 2009 6:44pm
  Restore Time:            unknown
  Digest Retention Time:   Wednesday, 12 February 2014 1:28pm
  Modified Retention Time: Wednesday, 12 February 2014 1:28pm
 
Trusted applications using IMAP may report a "sent items.dup1" folder during the sync and the sent items might never get synchronized.
 
 

Resolution

For those case you can try to fix such problems by using either standalone version of GWCheck or run the same check from ConsoleOne with following options (described here for a standalone version):

1. Database type -> Post Office
2. Database Path -> use a browse button to navigate in a location where is a wphost.db, the Post Office database
3. Post Office Name -> fill in a Post Office name.
4. Object type -> select User/Resource and type either a MailboxID or directly a user database file name.
5. Action -> leave default Analyze/Fix Databases.
6. Activate (only) Contents and Fix problems check boxes.
7. Database tab -> activate only the User option
8. Misc tab -> here type a string resfldr (or use alias string FOLDERRESET)
9. Run.

In a check log you will see extra lines, similar to following:

- checking Folder records
- Record 3 updated successfully
- Record 22 updated successfully
- Record 5 updated successfully
- Record 24 updated successfully
- Record 14 updated successfully
- Record 26 updated successfully
- Record 7 updated successfully
- Record 9 updated successfully
- Record 11 updated successfully