Users moved to a different post office does not see new items in shared folders

  • 7000956
  • 17-Jul-2008
  • 26-Apr-2012


Novell GroupWise 7.0
Novell GroupWise 7.0.1
Novell GroupWise 7.0.2
Novell GroupWise 7.0.3
Novell GroupWise 7.0.3 HP1


GroupWise users who has received some shared folders in his/her mailbox needs to be moved to a post office different than the one where the owner of the shares resides.

After the move, the user does not see anymore the new items placed in the shared folders, the shared folder functionality is broken.

The move operation, in some circumstances, breaks the shared folders synchronization mechanism.


The issue has been reported to the Engineering and has been fixed starting from GroupWise 7.0.3 HP2.

Action that will prevent the issue to occur if you are using affected GroupWise builds:

  1. Remove all the shares before performing the user move, and share everything back from the owners mailboxes once the move has been successfully completed;
  2. If possible, move the owner of the shares in the same post office where the users receiving the shares have been moved

Please note that upgrading to GroupWise 7.0.3 HP2 or later will allow to perform users move without breaking any shared folder, however will not fix the shares already broken from previously preformed moves. In order to restore the shared folders functionalities for the already affected users, you have to proceed as follows:

  1. Have the owner to unshare the folder with the users who are experiencing the issue;
  2. Verify from the affected users mailboxes that the shared folder has been actually removed, and if not, remove it manually;
  3. Have the owner to share again the folder with the intended users;
  4. Have the users to accept again the shared folder.
This procedure may not be effective if you are not running GroupWise 7.0.3 HP1 or later.

This issue may affect also shared calendars and shared address books.

Additional Information

Lab test outlined that moving to a different post office the owner of the shared folders, instead of the user who received the shares, does not introduce the issue.