Novell GROUPWISE 7 - TROUBLESHOOTING 2 Troubleshooting Manual page 67

Does the ownership of the user database match the recipient's network login
ID?
Reset the ownership on the userxxx.db file, then repeat the
No
test.
Continue below.
Yes
11 Check the ownership of the message database
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?
Reset the ownership on the msgnnn.db, then repeat the
No
test.
Continue below.
Yes
®
12 In ConsoleOne , perform maintenance to correct any problems with the
databases. See "Maintaining User/Resource and Message
"Databases" in the GroupWise 7 Administration
test.
13 If the message flow problem has not been resolved by following the
above troubleshooting steps, see
support.novell.com).
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
Has a new message file appeared in the post_office\wpcsin\6 directory?
See "Problem with an Individual User in Either Post Office"
No
on page
The sender can successfully send messages. Continue
Yes
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
B.
(msgnnn.db)
®
Novell Support (http://
directory in Post Office A.
65.
in the
Databases" in
Guide. Then repeat the
directory in Post Office
Message Does Not Arrive 67