Message Does Not Arrive between Post Offices

Problem:  A message from a user in Post Office A is not being delivered to a user in Post Office B in the same domain.

Action:  Review the stages of message flow between post offices. See "Message Delivery to a Different Post Office" in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure.

Action:  Answer the following question:

Can other users in Post Office A send messages to other users in Post Office B?
Yes

See Problem with an Individual User in Either Post Office.
No

See Problem between Post Offices for Multiple Users.
Don/t Know

See Problem between Post Offices for Multiple Users.

Problem with an Individual User in Either Post Office 

  1. Stop the MTA for the domain.

  2. 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.)

  3. Check the post_office\wpcsin\6 directory in the sender's post office.

    Has a new message file appeared in the post_office\wpcsin\6 directory?
    No

    The GroupWise client was unable to create the message file. The user might not have sufficient rights to the directory if using direct access mode. Correct the problem, then repeat the test.
    Yes

    The sender can successfully send messages. Continue below.

  4. Stop the POA for Post Office B.

  5. Restart the MTA in the domain. Observe the MTA agent console for any sign of problems.

  6. Check the post_office\wpcsout\ofs\6 directory in Post Office B.

    Has a new message file appeared in the post_office\wpcsout\ofs\6 directory?
    No

    See Problem between Post Offices for Multiple Users.
    Yes

    The message transferred successfully between post offices. Continue below.

  7. Restart the POA for Post Office B. Observe the POA agent console for any sign of problems.

  8. 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 POA was unable to pick up the message. Correct the problem, then repeat the test.
    Yes

    The POA has successfully picked up the message. Continue below.

  9. Check the recipient's mailbox.

    Does the new message appear in the recipient's mailbox?
    Yes

    The POA has successfully delivered the message this time. Repeat the test with a different user.
    No

    The POA was unable to deliver the message. Continue below.

  10. Check the ownership of the recipient's user database (userxxx.db).

    Does the ownership of the user database match the recipient's network login ID?
    No

    Reset the ownership on the userxxx.db file, then repeat the test.
    Yes

    Continue below.

  11. Check the ownership of the message database (msgnn.db) in the recipient's post office that corresponds to the message database assigned to the sender in the sender's post office.

    Is the ownership of the message database correct?
    No

    Reset the ownership on the msgnn.db, then repeat the test.
    Yes

    Continue below.

  12. In ConsoleOne®, perform maintenance to correct any problems with the databases. See "Maintaining User/Resource and Message Databases" in "Databases" in the GroupWise 6.5 Administration Guide. Then repeat the test.

  13. 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 

  1. Stop the MTA for the domain.

  2. 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.)

  3. Check the post_office\wpcsin\6 directory in Post Office A.

    Has a new message file appeared in the post_office\wpcsin\6 directory?
    No

    See Problem with an Individual User in Either Post Office.
    Yes

    The sender can successfully send messages. Continue below.

  4. Stop the POA for Post Office B.

  5. Restart the MTA for the domain. Observe the MTA agent console for any sign of problems.

  6. Check the post_office\wpcsout\ofs\6 directory in Post Office B.

    Has a new message file appeared in the post_office\wpcsout\ofs\6 directory?
    No

    See Problem with Access to Post Office B.
    Yes

    The MTA has successfully transferred the file to the POA in the recipient's post office. Continue below.

  7. Restart the POA for Post Office B. Observe the POA agent console for any sign of problems.

  8. 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 

  1. Start ConsoleOne with read/write rights to the post office.

  2. Open the browser window.

  3. Double-click the eDirectoryTM container where the domain is located, then select the Domain object.

  4. Click Tools > GroupWise Utilities > Link Configuration.

  5. Check the link from the domain to Post Office B.

    Does the link from the domain to the post office specify the correct IP address, UNC path, or mapped path to the post office directory for the recipient's post office?
    No

    Correct the information. Restart the MTA. Observe the MTA agent console for any sign of problems. Repeat the test.
    Yes

    The link to recipient's post office is correct. Continue below.

  6. 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.

    Are the IP address and TCP port number for the POA correct?
    No

    Correct the information. Restart the POA in Post Office B. Observe the POA agent console for any sign of problems. Repeat the test.
    Yes

    The IP address and port for the POA are correct. Continue below.

  7. Check rights for the MTA to write files into the post_office\wpcsout\ofs\6 directory in Post Office B.

    Are the network rights in the post office correct?
    No

    Reset the rights in the post office, and repeat the test.
    Yes

    Continue below.

  8. Check for available disk space in the post_office\wpcsout\ofs\6 directory in Post Office B.

    Is there adequate disk space available in the post office?
    No

    Remove unnecessary files from the server to free up disk space, then repeat the test.

    Yes

    Continue below.

  9. 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.