Message Does Not Arrive between Domains

Problem: A message from a user in Domain A is not being delivered to a user in Domain B.
Action: Review the stages of message flow between domains. See Message Delivery to a Different Domain in GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure.
Action: Answer the question below:

Can other users in Domain A send messages to other users in Domain B?

Yes

See Problem with an Individual User in Either Domain.

No

See Problem between Domains for Multiple Users.

Don’t Know

See Problem between Domains for Multiple Users.

Problem with an Individual User in Either Domain  

  1. Stop the MTA for Domain A.

  2. Have the user in Domain A send a low priority test message to a recipient in Domain 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 files. The user might not have sufficient rights to the directory. Correct the problem, then repeat the test.

    Yes

    The sender can successfully send messages. Continue below.

  4. Stop the POA for the recipient’s post office in Domain B.

  5. Start the MTA for Domain A. Observe the MTA agent console for any sign of problems.

  6. Check the domain\wpcsin\6 directory in Domain B.

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

    No

    The message is not transferring between domains. See Problem between Domains for Multiple Users.

    Yes

    The message transferred successfully between domains. Continue below.

  7. Restart the POA for the recipient’s post office in Domain B. Observe the POA agent console for any sign of problems.

  8. Recheck the post_office\wpcsout\ofs\6 directory in the recipient’s post office in Domain 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 user database, then repeat the test.

    Yes

    Continue below.

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

    Is the ownership of the message database correct?

    No

    Reset the ownership on the message database, 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 7 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 Domains for Multiple Users  

  1. Stop the MTA for Domain A.

  2. Have the user in Domain 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 the sender’s post office.

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

    No

    See Problem with an Individual User in Either Domain.

    Yes

    The sender can successfully send messages. Continue below.

  4. Stop the POA and the MTA for Domain B.

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

  6. Check the domain\wpcsin\6 directory in Domain B.

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

    No

    See Problem with Access to Domain B.

    Yes

    The file has successfully transferred to Domain B. Continue below.

  7. Restart the MTA for Domain B. Observe the MTA agent console for any sign of problems.

  8. Check the post_office\wpcsout\ofs\6 directory in the recipient’s post office.

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

    No

    See Problem with Access to the Post Office in Domain B.

    Yes

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

  9. Restart the POA for the recipient’s post office in Domain B. Observe the POA agent console for any sign of problems.

  10. Recheck the post_office\wpcsout\ofs\6 directory in the recipient’s post office.

    Has the message file disappeared from the post_office\wpcsout\ofs\6 directory?

    No

    The message transferred successfully between domains and into the recipient’s post office, but the POA in the recipient’s post office is unable to pick up the file. See Step 8 in Problem with an Individual User in Either Domain.

    Yes

    The message transferred successfully between domains and into the recipient’s post office, and the POA in the recipient’s post office has picked up the file. If the message still does not arrive in the recipient’s mailbox, see Step 8 through Step 13 in Problem with an Individual User in Either Domain.

Problem with Access to Domain B  

  1. Start ConsoleOne with read/write rights to the domain.

  2. Open the browser window.

  3. Double-click the eDirectory container where Domain A is located, then select Domain A.

  4. Click Tools > GroupWise Utilities > Link Configuration.

  5. Check the link from Domain A to Domain B.

    Does the link from Domain A specify the correct IP address, UNC path, or mapped path to the domain directory for Domain B?

    No

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

    Yes

    The link to Domain B is correct. Continue below.

  6. If you are using TCP/IP links between domains, check the IP address and port displayed in the Network Address box of the MTA Identification page. See Using TCP/IP Links between Domains in Message Transfer Agent in the GroupWise 7 Administration Guide.

    Are the IP address and TCP port number for the MTA correct?

    No

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

    Yes

    The IP address and port for MTA are correct. Continue below.

  7. If you are using mapped or UNC links, check rights for the Domain A MTA to write files into the domain\wpcsin\6 directory in Domain B.

    Are the network rights in the domain correct?

    No

    Reset the rights in Domain B, and repeat the test.

    Yes

    Continue below.

  8. Check for available disk space in the domain\wpcsin\6 directory in Domain B.

    Is there adequate disk space available in the domain?

    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 Domain A MTA to write the file into the domain\wpcsin\6 directory in Domain B, see Novell Support.

Problem with Access to the Post Office in Domain B

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

  2. Open the browser window.

  3. Double-click the eDirectory container where Domain B is located, then select Domain B.

  4. Click Tools > GroupWise Utilities > Link Configuration.

  5. Check the link from Domain B to the recipient’s post office.

    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 in Domain B. 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 a TCP/IP link to the post office, check the IP address displayed in the Network Address box of the POA Identification page.

    Is the IP address and TCP port number for the POA correct?

    No

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

    Yes

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

  7. If you are using a mapped or UNC link to the post office, check rights for the Domain B MTA to write files into the post_office\wpcsout\ofs\6 directory in the post office.

    Are the network rights for 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 the recipient’s post office.

    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 Domain B MTA to write the file into the post_office\wpcsout\ofs\6 directory in the recipient’s post office, see Novell Support.