Message Does Not Arrive between Post Offices
Message Delivery to a Different Post Officein GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure.
Problem with an Individual User in Either Post Office
Stop the MTA for the domain.
Have the user in Post Office A send a low priority test message to a recipient in Post Office B. (It’s a good idea to test message flow using a low priority message because the low priority message queue is typically empty.)
Check the post_office\wpcsin\6 directory in the sender’s post office.
Stop the POA for Post Office B.
Restart the MTA in the domain. Observe the MTA agent console for any sign of problems.
Check the post_office\wpcsout\ofs\6 directory in Post Office B.
Restart the POA for Post Office B. Observe the POA agent console for any sign of problems.
Recheck the post_office\wpcsout\ofs\6 directory in Post Office B.
Check the recipient’s mailbox.
Check the ownership of the recipient’s user database (userxxx.db).
Check the ownership of the message database (msgnnn.db) in the recipient’s post office that corresponds to the message database assigned to the sender in the sender’s post office.
In ConsoleOne®, perform maintenance
to correct any problems with the databases. See Maintaining
User/Resource and Message Databases
in Databases
in
the GroupWise
7 Administration Guide. Then repeat the test.
If the message flow problem has not been resolved by following the above troubleshooting steps, see Novell® Support .
Problem between Post Offices for Multiple Users
Stop the MTA for the domain.
Have the user in Post Office A send a low priority test message. (It’s a good idea to test message flow using a low priority message because the low priority message queue is typically empty.)
Check the post_office\wpcsin\6 directory in Post Office A.
Stop the POA for Post Office B.
Restart the MTA for the domain. Observe the MTA agent console for any sign of problems.
Check the post_office\wpcsout\ofs\6 directory in Post Office B.
Restart the POA for Post Office B. Observe the POA agent console for any sign of problems.
Recheck the post_office\wpcsout\ofs\6 directory in Post Office B.
|
Has the message file disappeared from the post_office\wpcsout\ofs\6 directory? |
|
|---|---|
|
No |
The message transferred successfully between post offices, but the POA in Post Office B is unable to pick up the file. See Step 8 in Problem with an Individual User in Either Post Office. |
|
Yes |
The message transferred successfully between post offices, and the POA in Post Office B has picked up the file. If the message still does not arrive in the recipient’s mailbox, see Step 9 through Step 13 in Problem with an Individual User in Either Post Office. |
Problem with Access to Post Office B
Start ConsoleOne with read/write rights to the post office.
Open the browser window.
Double-click the eDirectory™ container where the domain is located, then select the Domain object.
Click Tools > GroupWise Utilities > Link Configuration.
Check the link from the domain to Post Office B.
If you are using client/server access to Post Office B, check the IP address and port displayed in the Network Address box of the POA Identification page.
Check rights for the MTA to write files into the post_office\wpcsout\ofs\6 directory in Post Office B.
Check for available disk space in the post_office\wpcsout\ofs\6 directory in Post Office B.
If these troubleshooting steps have not enabled the MTA to write the file into the post_office\wpcsout\ofs\6 directory in the recipient’s post office, see Novell Support.