Novell GROUPWISE 7 TROUBLESHOOTING

Novell GroupWise®

Setember 29, 2006

www.novell.com

TROUBLESHOOTING 3: MESSAGE

FLOW AND DIRECTORY STRUCTURE

Legal Notices

Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.

Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.

Copyright © 1993-2006 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.

Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed on the Novell Legal Patents Web page (http://www.novell.com/company/legal/patents/) and one or more additional patents or pending patent applications in the U.S. and in other countries.

Novell, Inc. 404 Wyman Street, Suite 500 Waltham, MA 02451 U.S.A. www.novell.com

Online Documentation: To access the online documentation for this and other Novell products, and to get

updates, see the Novell Documentation Web site (http://www.novell.com/documentation).

Novell Trademarks

For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/

trademarks/tmlist.html).

Third-Party Materials

All third-party trademarks are the property of their respective owners.

Contents

About This Guide 9

Part I Message Flow Diagrams 11

1 Message Delivery in the Local Post Office 13

1.1 Online Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

1.2 Caching Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

1.3 Remote Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2 Message Delivery to a Different Post Office 19

2.1 TCP/IP Link Open: Transfer between Post Offices Successful . . . . . . . . . . . . . . . . . . . . . . . . 19

2.2 TCP/IP Link Closed: Transfer between Post Offices Delayed . . . . . . . . . . . . . . . . . . . . . . . . . 22

3 Message Delivery to a Different Domain 27

3.1 TCP/IP Link Open: Transfer between Domains Successful . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3.2 TCP/IP Link Closed: Transfer between Domains Delayed . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4 Message Delivery to and from the Internet 35

4.1 TCP/IP Link: Outbound Transfer to the Internet Successful . . . . . . . . . . . . . . . . . . . . . . . . . . 35

4.2 TCP/IP Link: Outbound Transfer to the Internet Delayed or Unsuccessful . . . . . . . . . . . . . . . 38

4.3 Mapped/UNC Link: Outbound Transfer to the Internet Successful . . . . . . . . . . . . . . . . . . . . . 41

4.4 Mapped/UNC Link: Outbound Transfer to the Internet Delayed or Unsuccessful . . . . . . . . . . 43

4.5 TCP/IP Link: Inbound Transfer from the Internet Successful. . . . . . . . . . . . . . . . . . . . . . . . . . 47

4.6 Mapped/UNC Link: Inbound Transfer from the Internet Successful . . . . . . . . . . . . . . . . . . . . 49

5 Message Delivery through a Modem Connection 51

5.1 “Hit the Road” Process in Online Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

5.2 Modem Link through the Async Gateway in Remote Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . 53

6 Administrative Database Update 59

Part II Directory Structure Diagrams 61

7 Message Transfer/Storage Directories 63

7.1 Domain Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

7.1.1 domain directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

7.1.2 wpcsin directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

7.1.3 wptools directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

7.1.4 wpgate directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

7.1.5 wpcsout directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

7.1.6 mtaname file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Contents 5

7.1.7 wpdomain.db file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

7.1.8 wpdomain.dc file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

7.1.9 wphost.dc file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

7.1.10 gwdom.dc file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

7.1.11 gwpo.dc file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

7.1.12 viewcopy.log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

7.2 Post Office Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

7.2.1 post_office directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

7.2.2 wpcsin directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

7.2.3 gwdms directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

7.2.4 ofmsg directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

7.2.5 ofuser directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

7.2.6 offiles directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

7.2.7 ofviews directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

7.2.8 ofwork directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

7.2.9 ofdirect directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

7.2.10 oftemp directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

7.2.11 wpcsout directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

7.2.12 wphost.db file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

7.2.13 gwpo.dc file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

7.2.14 ngwguard.db file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

7.2.15 ngwguard.dc file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

7.2.16 ngwguard.fbk file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

7.2.17 ngwguard.rfl file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

7.2.18 ngwcheck.db . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

7.3 MTA Local Queue Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

7.3.1 mslocal directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

7.3.2 msglog directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

7.3.3 gwinprog directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

7.3.4 mshold directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

7.3.5 domainms directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

7.3.6 postx directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

7.3.7 gatewayx directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

7.3.8 domainx directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

7.3.9 0-7 directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

7.3.10 mtaname files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

7.3.11 gwvsscan directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

7.3.12 mtaconv directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

7.4 Internet Agent Queue Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

7.4.1 domain\wpgate\gwia directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

7.4.2 gwia directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

7.5 WebAccess Agent Queue Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

7.5.1 domain\wpgate\webac70a directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

7.5.2 000.prc directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

7.5.3 wpcsin directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

7.5.4 wpcsout directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

7.5.5 gwhold directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

7.5.6 gwprob directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

7.5.7 template directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

7.5.8 commgr.cfg file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

7.5.9 comint.cfg file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

7.5.10 mimetype.cfg file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

7.5.11 gwac.db file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

7.5.12 gwac.dc file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

7.6 Caching Mailbox Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

7.6.1 \novell\groupwise\gwxxxxxx directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

7.6.2 rofdata directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

7.6.3 wpcsin directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

6 GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure

7.6.4 wpcsout\ofs directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

7.6.5 wpgwsend directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

7.6.6 wpgwrecv directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

7.6.7 remoten.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

7.7 Remote Mailbox Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

7.7.1 remote_mailbox directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

7.7.2 rofdata directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

7.7.3 wpcsin directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

7.7.4 wpcsout\ofs directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

7.7.5 wpgwsend directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

7.7.6 wpgwrecv directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

7.7.7 remoten.log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

8 Agent Installation Directories 107

8.1 GroupWise Agent Installation (POA and MTA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

8.1.1 NetWare Installation Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

8.1.2 Linux Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

8.1.3 Windows Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

8.2 Internet Agent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

8.2.1 NetWare Installation Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

8.2.2 Linux Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

8.2.3 Windows Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

8.3 WebAccess Agent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

8.3.1 NetWare Installation Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

8.3.2 Linux Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

8.3.3 Windows Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

8.3.4 Document Viewer Agent Working Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

8.4 Monitor Agent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

8.4.1 Linux Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

8.4.2 Windows Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

8.5 Apache/Tomcat Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

8.5.1 NetWare Installation Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

8.5.2 Linux Installation Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

9 Software Distribution Directory 155

9.1 NetWare/Windows Software Distribution Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

9.1.1 \grpwise\software directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

9.1.2 agents directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

9.1.3 domain directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

9.1.4 po directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

9.1.5 client directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

9.1.6 gwcheck directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

9.1.7 ofviews directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

9.1.8 ppforms directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

9.1.9 uwl directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

9.1.10 admin directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

9.1.11 internet directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

9.1.12 license directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

9.1.13 common directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

9.1.14 docs directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

9.2 Linux Software Distribution Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

9.2.1 /opt/novell/groupwise/software directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

9.2.2 agents directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

9.2.3 domain directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

9.2.4 po directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

9.2.5 client directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

9.2.6 ofviews directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

9.2.7 admin directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

9.2.8 internet directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

9.2.9 license directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

9.2.10 docs directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

9.2.11 gwinst directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

10 GroupWise Client Installation Directories 173

10.1 Windows Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

10.1.1 c:\novell\groupwise. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

10.1.2 grpwise.exe file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

10.1.3 gwtip.exe file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

10.1.4 notify.exe file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

10.1.5 addrbook.exe file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

10.1.6 htrsetup.exe file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

10.1.7 gwimpexe.exe file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

10.1.8 gwmailto.exe file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

10.1.9 gwreload.exe file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

10.1.10 gwsync.exe file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

10.1.11 pdaconnect.exe file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

10.1.12 ngwguard.dc file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

10.1.13 wprof.dc file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

10.1.14 *.dll files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

10.1.15 *.ocx files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

10.1.16 *.flt files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

10.1.17 *.chm files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

10.1.18 gwcheck directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

10.1.19 ofviews directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

10.1.20 ppforms directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

10.2 Cross-Platform Client on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

10.2.1 /opt/novell/groupwise/client directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

10.2.2 bin directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

10.2.3 lib directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

10.2.4 jre directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

10.2.5 logs directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

10.3 Cross-Platform Client on Macintosh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

10.3.1 /Applications/GroupWise.app directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

10.3.2 Contents directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

10.3.3 MacOS directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

10.3.4 Resources directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

10.3.5 lib directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

10.3.6 Java directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Part III Documentation Updates 181

A June 15, 2006 (GroupWise 7 SP1) 183

8 GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure

About This Guide

This Novell® GroupWise® Troubleshooting 3 Guide provides diagrams to help you understand the structure and functioning of your GroupWise system. The guide is divided into the following sections:

 “Message Flow Diagrams” on page 11

 “Directory Structure Diagrams” on page 61

Other sources of troubleshooting assistance include:

 Novell Support (http://www.novell.com/support)

 Novell Support Knowledgebase (http://www.novell.com/support/supportcentral)

 GroupWise 7 Support Forums (http://support.novell.com/forums/2gw.html)

 Novell GroupWise Support Community (http://www.novell.com/support/

browse.do?WidgetName=BROWSE_PRODUCT&BROWSE_PRODUCT.TaxoName=SG_S upportGoals&NodeType=leaf&NodeName=GroupWise&TaxoName=SG_SupportGoals&BR OWSE_PRODUCT.isProductTaxonomy=true&BROWSE_PRODUCT.NodeId=SG_GROUP WISE_1_1&BROWSE_PRODUCT.NodeType=leaf&BROWSE_PRODUCT.thisPageUrl=% 2Fproduct%2Fproducts.do&NodeId=SG_GROUPWISE_1_1&id=m1&AppContext=AC_Site Central)

 GroupWise Cool Solutions (http://www.novell.com/coolsolutions/gwmag/index.html)

Audience

This guide is intended for network administrators who install and administer GroupWise..

Feedback

We want to hear your comments and suggestions about this manual and the other documentation included with this product. Please use the User Comments feature at the bottom of each page of the online documentation, or go to www.novell.com/documentation/feedback.html and enter your comments there.

Documentation Updates

For the most recent version of GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure, visit the GroupWise 7 Documentation Web site (http://www.novell.com/documentation/

gw7).

Additional Documentation

For additional GroupWise documentation, see the following guides at the GroupWise 7

Documentation Web site (http://www.novell.com/documentation/gw7):

 Installation Guide

 Administration Guide

 Multi-System Administration Guide

About This Guide

 Interoperability Guide

 Troubleshooting 1: Error Messages

 Troubleshooting 2: Solutions to Common Problems

 GroupWise Client User Guides

 GroupWise Client Frequently Asked Questions (FAQ)

Documentation Conventions

In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.

A trademark symbol (

, ®, etc.) denotes a Novell trademark. An asterisk denotes a third-party

trademark.

When a single pathname can be written with a backslash for some platforms or a forward slash for other platforms, the pathname is presented with a backslash. Users of platforms that require a forward slash, such as Linux*, should use forward slashes as required by your software.

When a startup switch can be written with a forward slash for some platforms or a double hyphen for other platforms, the startup switch is presented with a forward slash. Users of platforms that require a double hyphen, such as Linux, should use double hyphens as required by your software.

10 GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure

Message Flow Diagrams

This part of Troubleshooting 3: Message Flow and Directory Structure helps you understand how

messages travel between GroupWise

users and how administrative updates to GroupWise

databases occur.

 Chapter 1, “Message Delivery in the Local Post Office,” on page 13

 Chapter 2, “Message Delivery to a Different Post Office,” on page 19

 Chapter 3, “Message Delivery to a Different Domain,” on page 27

 Chapter 4, “Message Delivery to and from the Internet,” on page 35

 Chapter 5, “Message Delivery through a Modem Connection,” on page 51

 Chapter 6, “Administrative Database Update,” on page 59

Message Flow DiagramsI11

12 GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure

Message Delivery in the Local Post Office

The GroupWise® 7 client always uses client/server access to the post office but it can interact with the POA for the post office in different ways. For a review, see “Using Different GroupWise Modes

(Online, Caching, and Remote)” in “Getting Started” in the GroupWise 7 Windows Client User

Guide.

 Section 1.1, “Online Mode,” on page 13

 Section 1.2, “Caching Mode,” on page 15

 Section 1.3, “Remote Mode,” on page 18

1.1 Online Mode

This message flow diagram illustrates how a GroupWise message travels from one user to another in the local post office when the client and POA communicate by way of TCP/IP and the users are accessing their Online mailboxes.

Figure 1-1 Message Flow in Online Mode

POA

wpcsin

0-7

ofmsg

msgnnn.db

ofuser

userxxx.db

offiles

fdo-7f

wpcsout

ads

0-7

ofs

0-7

Table 1-1 Message Flow in Online Mode Stages

Stage Icon Description

The user sends a message to recipients in the same post office. The

Sender

access mode setting for the post office is Client/Server Only.

Message Delivery in the Local Post Office

Stage Icon Description

The GroupWise client communicates with the POA by way of TCP/IP. Sender’s GroupWise Client

The POA receives the message from the GroupWise client and POA for Local Post Office

performs the following actions for the sender:

 Adds the message to the message database (msgnnn.db)

assigned to the sender.

 Creates a pointer in the sender’s user database (userxxx.db)

so the message appears in the sender’s mailbox as a sent item.

 Places attachments larger than 2 KB in one of the

post_office\offiles\fd0-F6 subdirectories and creates

pointers from the message to its attachments. (For database efficiency, messages and distribution lists larger than 2 KB are also handled as attachments.)

The POA also performs the following actions for the recipient:

 Creates a pointer in each recipient’s user database

(userxxx.db) to the message in the message database (msgnnn.db) so the new message appears in the recipient’s mailbox.

 Updates the message in the message database (msgnnn.db)

with a Delivered status for each recipient.

POA for Local Post Office

Recipient’s GroupWise Client

Recipient

Recipient’s GroupWise Client

POA for Local Post Office

Sender

The POA communicates to the GroupWise client by way of TCP/IP that

a new message has arrived.

The Notify component of the recipient’s GroupWise client notifies the

recipient that a new message has arrived.

Each recipient opens the message in the GroupWise client.

Each recipient’s GroupWise client communicates the Opened status to

the POA by way of TCP/IP.

The POA receives the Opened status from the GroupWise client and

updates the message in the message database with the Opened

status for each recipient who opens the message.

The POA communicate the Opened status to the sender’s GroupWise

client by way of TCP/IP.

When the sender checks the sent items in his or her mailbox in the

GroupWise client, the message displays a status of Delivered for each

recipient (and possibly Opened as well if the recipient has opened the

message).

14 GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure

1.2 Caching Mode

This message flow diagram illustrates how a GroupWise message travels from one user to another in the local post office when the users are accessing their Caching mailboxes.

Figure 1-2 Message Flow in Caching Mode

Table 1-2 Message Flow in Caching Mode Stages

Stage Icon Description

rofdata

msg.db user.db

wprof.db

wpcsin

POA

wpcsin

0-7

ofmsg

msgnnn.db

ofuser

userxxx.db

offiles

fdo-7f

wpcsout

ads

ofs

0-7

10 7

rofdata

msg.db user.db

wprof.db

wpcsin

Sender

The user sends a message to recipients in the same post office. The user is in Caching mode.

Message Delivery in the Local Post Office 15

Stage Icon Description

The GroupWise client updates the sender’s Caching mailbox Sender’s GroupWise Client

(\novell\groupwise\gwxxxxxxx\rofdata) by performing the

following actions:

 Adds the message to the message database

(rofdata\msg.db) in the Caching mailbox. This database is local equivalent of the msgnnn.db database in the post office.

 Creates a pointer in the sender’s user database

(rofdata\user.db) in the Caching mailbox so the message appears in the sender’s mailbox as a sent item. This database is the local equivalent of the userxxx.db database in the post office.

 Places attachments larger than 2 KB in the rofdata

subdirectory in the Caching mailbox and creates pointers from the message to its attachments. (For database efficiency, messages and distribution lists larger than 2 KB are also handled as attachments.) There is no local equivalent to the offiles subdirectory in the post office, so attachments are placed directly in the rofdata subdirectory in the Caching mailbox.

 Places a copy of the message in the rofdata\wpcsin\1

priority subdirectory to await the next connection to the POA.

In Caching mode, sending a message always initiates an immediate Sender’s GroupWise Client

connection with the POA in order to send the message. The

GroupWise client communicates the message to the POA and deletes

the copy in the rofdata\wpcsin\1 priority subdirectory when the

POA has processed the message.

POA for Local Post Office

The POA receives the message from the GroupWise client and

performs the following actions for the sender to update the sender’s

Online mailbox:

 Adds the message to the message database (msgnnn.db)

assigned to the sender in the post office.

 Creates a pointer in the sender’s user database (userxxx.db) in

the post office.

 Places attachments larger than 2 KB in one of the

post_office\offiles\fd0-F6 subdirectories in the post

office and creates pointers from the message to its attachments. (For database efficiency, messages and distribution lists larger than 2 KB are also handled as attachments.)

The POA also performs the following actions for the recipients to

update their Online mailboxes:

 Creates a pointer in each recipient’s user database

(userxxx.db) to the message in the message database (msgnnn.db) in the post office so that the new message appears in each recipient’s mailbox.

 Updates the message in the message database (msgnnn.db) in

the post office with a Delivered status for the recipients.

16 GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure

Stage Icon Description

Because the recipients are also in Caching mode, they do not receive POA for Local Post Office

POA for Local Post Office

Recipient’s GroupWise Client

immediate notification that a new message has arrived in their Online

mailboxes. Based on the Send/Retrieve All Marked Accounts Every nn

Minutes option under Accounts > Account Options > General, each

recipient’s GroupWise client sends a request to the POA for items that

have arrived in the recipient’s Online mailbox since the last connection

with the POA.

The POA responds by sending information to update each recipient’s

Caching mailbox and communicates to the GroupWise client that a

new message has arrived.

Each recipient’s GroupWise client updates the recipient’s Caching

mailbox by performing the following actions:

 Adds the message to the message database

(rofdata\msg.db) in the recipient’s Caching mailbox.

 Creates a pointer in the recipient’s user database

(rofdata\user.db) to the message in the message database (rofdata\msg.db) so the new message appears in the recipient’s Caching mailbox.

The Notify component of each recipient’s GroupWise client notifies the Recipient’s GroupWise Client

recipient that a new message has arrived.

Recipient

Recipient’s GroupWise Client

POA for Local Post Office

Recipient’s GroupWise Client

POA for Local Post Office

Each recipient opens the message in the GroupWise client.

Each recipient’s GroupWise client generates an Opened status and

places it in the rofdata\wpcsin\1 priority subdirectory to await the

next connection with the POA.

When each recipient sends a message or the time specified by the

Send/Receive All Marked Accounts Every nn Minutes option has

elapsed, each recipient’s GroupWise client connects with the POA and

communicates the Opened status to the POA, along with any other

data that needs to be uploaded to the recipient’s Online mailbox.

The POA receives the Opened status from the GroupWise client and

updates the message in the sender’s message database with the

Opened status.

Because the sender is in Caching mode, the sender does not

immediately receive the Opened status. Based on the sender’s actions

and caching schedule, the sender’s GroupWise client eventually sends

a request to the POA for items that have arrived in the sender’s Online

mailbox since the last synchronization of the Caching mailbox.

The POA responds by sending information to update the sender’s

Caching mailbox and communicates the Opened status to the sender’s

GroupWise client.

Message Delivery in the Local Post Office 17

Stage Icon Description

The sender’s GroupWise client updates the sender’s Caching mailbox Recipient’s GroupWise Client

by performing the following action:

 Updates the message in the message database

(rofdata\msg.db) with a Delivered and Opened status for each recipient.

When the sender checks the sent items in his or her mailbox in the Sender

GroupWise client, the message displays a status of Delivered and

Opened for each recipient.

1.3 Remote Mode

Before you can use Remote mode, you must create a Remote mailbox on your computer and have a connection to your master GroupWise system. See Chapter 5, “Message Delivery through a Modem

Connection,” on page 51.

18 GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure

Message Delivery to a Different Post Office

The MTA handles message transfer between post offices.

 Section 2.1, “TCP/IP Link Open: Transfer between Post Offices Successful,” on page 19

 Section 2.2, “TCP/IP Link Closed: Transfer between Post Offices Delayed,” on page 22

The message flow diagrams in GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure focus on TCP/IP links because they are the most common and convenient (unless you

have a post office and a domain on the same server). For diagrams that include mapped/UNC links, see GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. For an explanation of link types and link protocols, see “Understanding Link Configuration” in “Domains” in the

GroupWise 7 Administration Guide.

2.1 TCP/IP Link Open: Transfer between Post Offices Successful

This message flow diagram illustrates how a GroupWise® message travels from one user to another between post offices in the same domain when the TCP/IP link between the post office and the domain is open.

Figure 2-1 Message Flow When the TCP/IP Link is Open

POAa

wpcsin

0-7

ofmsg

msgnnn.db

ofuser

userxxx.db

offiles

fdo-7f

wpcsout

ads

ofs

0-7

MTA

mslocal

gwinprog

mshold

wpcsin

0-7

wpcsout

ads

0-7

domainms

posta

0-7

postb

0-7

gatewayx

0-7

domainx

0-7

POAb

wpcsin

0-7

ofmsg

msgnnn.db

ofuser

userxxx.db

offiles

fdo-7f

wpcsout

ads

ofs

0-7

Message Delivery to a Different Post Office

Table 2-1 Message Flow When the TCP/IP Link is Open Stages

Stage Icon Description

Sender

Sender’s GroupWise Client

POA for Sender’s Post Office

The user sends a message to recipients in a different post office in the same domain.

In this diagram, the access mode setting in the local post office is Client/ Server Only.

The GroupWise client communicates the message to the POA by way of TCP/IP.

The POA receives the message from the GroupWise client and performs the following actions for the sender:

 Adds the message to the message database (msgnnn.db) assigned to

the sender.

 Creates a pointer in the sender’s user database (userxxx.db) so the

message appears in the sender’s mailbox as a sent item.

 Places attachments larger than 2 KB in one of the

post_office\offiles\fd0-F6 subdirectories and creates pointers

from the message to its attachments. (For database efficiency, messages and distribution lists larger than 2 KB are also handled as attachments.)

 Creates a copy of the message in the appropriate priority 0-7

subdirectory of the MTA input queue in the sender’s post office, in case the TCP/IP link to the MTA is currently closed.

POA for Sender’s Post Office

MTA for Local Domain

The POA then communicates the message to the MTA by way of TCP/IP, and deletes the copy in the MTA input queue because the TCP/IP transfer to the MTA was successful.

To see what happens if the TCP/IP link to the MTA is closed, see

Section 2.2, “TCP/IP Link Closed: Transfer between Post Offices Delayed,” on page 22.

The MTA receives the message and places it into the MTA “in progress” (gwinprog) queue.

The MTA then communicates the message to the POA in the recipient’s post office by way of TCP/IP. When the transmission is successful, the MTA deletes the message from the MTA “in progress” queue.

If the TCP/IP link to the recipient’s post office is closed, the message is placed in the closed post office’s holding queue in the MTA’s mslocal directory for later transfer. The resulting message flow is parallel to what occurs when a domain is closed. See Section 3.2, “TCP/IP Link Closed:

Transfer between Domains Delayed,” on page 31 for a similar message flow

that illustrates how messages to closed locations are handled.

20 GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure

Stage Icon Description

POA for Recipient’s Post Office

POA for Local Post Office

When the POA receives the new message from the MTA, it places it into the MTA output queue in the post office (wpcsout\ofs\0-7) on behalf of the MTA. Then, the POA for the recipient’s post office performs the following actions:

 Adds the message to the message database (msgnnn.db)

corresponding to the one assigned to the sender.

 Creates a pointer in the recipient’s user database (userxxx.db) so

the new message appears in the recipient’s mailbox and updates the notification information in the user database so the recipient can be notified of the message.

 Places attachments larger than 2 KB in one of the

post_office\offiles\fd0-F6 subdirectories and creates pointers from the message to its attachments. (For database efficiency, messages and distribution lists larger than 2 KB are also handled as attachments.)

 Creates a Delivered status message in the appropriate priority 0-7

subdirectory of the MTA input queue in the recipient’s post office. It also communicates the Delivered status message directly to the MTA by way of TCP/IP. When that transmission is successful, the copy in the MTA input queue is deleted.

The POA communicates to the GroupWise client by way of TCP/IP that a new message has arrived.

Recipient’s GroupWise Client

Recipient

Recipient’s GroupWise Client

POA for Recipient’s Post Office

MTA for Local Domain

POA in Sender’s Post Office

The Notify component of the recipient’s GroupWise client notifies the recipient that a new message has arrived.

Each recipient opens the message in the GroupWise client.

Each recipient’s GroupWise client communicates the Opened status message to the POA by way of TCP/IP.

The POA for the recipient’s post office communicates the status message to the MTA by way of TCP/IP.

The MTA places the status message into the MTA “in progress” (gwinprog) queue.

The MTA communicates the status message to the POA for the sender’s post office by way of TCP/IP.

The POA for the sender’s post office updates the sender’s message database (msgnnn.db) with the Delivered status information (and possibly Opened as well if the recipient has opened the message).

Message Delivery to a Different Post Office 21

Stage Icon Description

POA for Local

The POA communicates the status to the sender’s GroupWise client by way of TCP/IP.

Post Office

Sender

When the sender checks the sent items in his or her mailbox in the GroupWise client, the message displays a status of Delivered for each recipient (and possibly Opened as well if the recipient has opened the message).

2.2 TCP/IP Link Closed: Transfer between Post Offices Delayed

This message flow diagram illustrates how a GroupWise message travels from one user to another between post offices in the same domain when the TCP/IP link between the post office and the domain is closed.

Figure 2-2 Message Flow When the TCP/IP Link is Closed

wpcsin

POAa

wpcsin

0-7

ofmsg

msgnnn.db

ofuser

userxxx.db

offiles

fdo-7f

wpcsout

ads

ofs

0-7

MTA

mslocal

0-7

wpcsout

ads

gwinprog

0-7

mshold

domainms

posta

0-7

postb

0-7

gatewayx

0-7

domainx

0-7

POAb

wpcsin

0-7

ofmsg

msgnnn.db

ofuser

userxxx.db

offiles

fdo-7f

wpcsout

ads

ofs

0-7

22 GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure

Table 2-2 Message Flow When the TCP/IP Link is Closed Stages

Stage Icon Description

Sender

Sender’s GroupWise Client

POA for Sender’s Post Office

The user sends a message to recipients in a different post office in the same domain.

In this diagram, the access mode setting in the local post office is Client/ Server Only.

The GroupWise client communicates the message to the POA by way of TCP/IP.

The POA receives the message from the GroupWise client and performs the following actions for the sender:

 Adds the message to the message database (msgnnn.db) assigned

to the sender.

 Creates a pointer in the sender’s user database (userxxx.db) so the

message appears in the sender’s mailbox as a sent item.

 Places attachments larger than 2 KB in one of the

post_office\offiles\fd0-F6 subdirectories and creates

pointers from the message to its attachments. (For database efficiency, messages and distribution lists larger than 2 KB are also handled as attachments.)

 Creates a copy of the message in the appropriate priority 0-7

subdirectory of the MTA input queue in the sender’s post office, in case the TCP/IP link to the MTA is currently closed.

POA for Sender’s Post Office

MTA for Local Domain

The POA then attempts to communicate the message to the MTA by way of TCP/IP, but the MTA does not respond. The POA leaves the copy of the message in the MTA input queue and periodically attempts to contact the MTA. When the MTA responds again, the POA communicates the message and deletes the copy in the MTA input queue after the TCP/IP transmission to the MTA is successful.

The MTA receives the message and places it into the MTA “in progress” (gwinprog) queue.

Link Closed: Transfer between Domains Delayed,” on page 31.

Message Delivery to a Different Post Office 23

Stage Icon Description

POA for Recipient’s Post Office

POA for Local Post Office

Recipient’s GroupWise Client

When it receives the new message, the POA for the recipient’s post office performs the following actions:

 Adds the message to the message database (msgnnn.db)

corresponding to the one assigned to the sender.

 Creates a pointer in the recipient’s user database (userxxx.db) so

the new message appears in the recipient’s mailbox and updates the notification information in the user database so the recipient can be notified of the message.

 Places attachments larger than 2 KB in one of the

 Creates a Delivered status message in the appropriate priority 0-7

subdirectory of the MTA input queue in the recipient’s post office. It also communicates the Delivered status message directly to the MTA by way of TCP/IP and when that transmission is successful, the copy in the MTA input queue is deleted.

The POA communicates to the GroupWise client by way of TCP/IP that a new message has arrived.

The Notify component of the recipient’s GroupWise client notifies the recipient that a new message has arrived.

Recipient

Recipient’s GroupWise Client

POA for Recipient’s Post Office

MTA for Local Domain

POA in Sender’s Post Office

Each recipient opens the message in the GroupWise client.

Each recipient’s GroupWise client communicates the Opened status message to the POA by way of TCP/IP.

The POA for the recipient’s post office communicates the status message to the MTA by way of TCP/IP.

The MTA places the status message into the MTA “in progress” (gwinprog) queue.

The MTA communicates the status message to the POA for the sender’s post office by way of TCP/IP.

The POA for the sender’s post office updates the sender’s message database (msgnnn.db) with the Delivered status information (and possibly Opened as well if the recipient has opened the message).

24 GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure

Stage Icon Description

POA for Local Post Office

Sender

The POA communicates the Opened status to the sender’s GroupWise client by way of TCP/IP.

Message Delivery to a Different Post Office 25

26 GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure

Message Delivery to a Different Domain

The MTA handles message transfer between domains.

 Section 3.1, “TCP/IP Link Open: Transfer between Domains Successful,” on page 27

 Section 3.2, “TCP/IP Link Closed: Transfer between Domains Delayed,” on page 31

The message flow diagrams in GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure focus on TCP/IP links because they are the most common and convenient (unless you

have two domains on the same server). For diagrams that include mapped/UNC links, see

GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. For an explanation of

link types and link protocols, see “Understanding Link Configuration” in “Domains” in the

GroupWise 7 Administration Guide.

3.1 TCP/IP Link Open: Transfer between Domains Successful

This message flow diagram illustrates how a GroupWise® message travels from one user to another when the domains are connected by a TCP/IP link and the link is open.

Figure 3-1 Message Flow When the TCP/IP Link is Open

wpcsin

POAa

wpcsin

0-7

ofmsg

msgnnn.db

ofuser

userxxx.db

offiles

fdo-7f

wpcsout

ads

ofs

MTAa

mslocal

0-7

wpcsout

ads

gwinprog

0-7

mshold

domainms

posta

0-7

postb

0-7

gatewayx

0-7

domainx

0-7

7 15

6 16

MTAb

mslocal

wpcsin

0-7

wpcsout

ads

gwinprog

0-7

mshold

domainms

posta

0-7

postb

0-7

gatewayx

0-7

domainx

0-7

POAb

wpcsin

0-7

ofmsg

msgnnn.db

ofuser

userxxx.db

offiles

fdo-7f

wpcsout

ads

ofs

0-7

Message Delivery to a Different Domain

Table 3-1 Message Flow When the TCP/IP Link is Open Stages

Stage Icon Description

Sender

Sender’s GroupWise Client

POA for Sender’s Post Office

The user sends a message to recipients in a post office in a different domain.

In this diagram, the access mode setting for the local post office is Client/Server Only.

The GroupWise client communicates the message to the POA by way of TCP/ IP.

The POA receives the message from the GroupWise client and performs the following actions for the sender:

 Adds the message to the message database (msgnnn.db) assigned to

the sender.

 Creates a pointer in the sender’s user database (userxxx.db) so the

message appears in the sender’s mailbox as a sent item.

 Places attachments larger than 2 KB in one of the

post_office\offiles\fd0-F6 subdirectories and creates pointers

from the message to its attachments. (For database efficiency, messages and distribution lists larger than 2 KB are also handled as attachments.)

 Creates a copy of the message in the appropriate priority 0-7

subdirectory of the MTA input queue in the sender’s post office, in case the TCP/IP link to the MTA is currently closed.

The POA then communicates the message to the MTA for the sender’s domain by way of TCP/IP, and deletes the copy in the MTA input queue because the TCP/IP transfer to the MTA was successful.

To see what would happen if the TCP/IP link to the MTA is closed, see

Section 2.2, “TCP/IP Link Closed: Transfer between Post Offices Delayed,” on page 22.

MTA for Sender’s Domain

MTA for Recipient’s Domain

The MTA for the sender’s domain receives the message and places it into the MTA “in progress” (gwinprog) queue.

The MTA for the sender’s domain then communicates the message to the MTA for the recipient’s domain by way of TCP/IP.

If the TCP/IP link to the recipient’s domain is closed, the message is placed in the closed domain’s holding queue in the MTA’s mslocal directory for later transfer. See Section 3.2, “TCP/IP Link Closed: Transfer between Domains

Delayed,” on page 31.

The MTA for the recipient’s domain receives the message and places it into the MTA “in progress” (gwinprog) queue.

The MTA for the recipient’s domain then communicates the message to the POA in the recipient’s post office by way of TCP/IP.

28 GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure

Stage Icon Description

POA for Recipient’s Post Office

Recipient’s GroupWise Client

When it receives the new message, the POA for the recipient’s post office performs the following actions:

 Adds the message to the message database (msgnnn.db) corresponding

to the one assigned to the sender.

 Creates a pointer in the recipient’s user database (userxxx.db) so the

new message appears in the recipient’s mailbox and updates the notification information in the user database so the recipient can be notified of the message.

 Places attachments larger than 2 KB in one of the

 Creates a Delivered status message in the appropriate priority 0-7

The POA for the recipient’s post office communicates to the GroupWise client by way of TCP/IP that a new message has arrived.

The Notify component of the recipient’s GroupWise client notifies the recipient that a new message has arrived.

Recipient

Recipient’s GroupWise Client

POA for Recipient’s Post Office

MTA for Recipient’s Domain

MTA for Sender’s Domain

Each recipient opens the message in the GroupWise client.

Each recipient’s GroupWise client communicates the Opened status message to the POA by way of TCP/IP.

The POA for the recipient’s post office communicates the status message to the MTA for the recipient’s domain by way of TCP/IP.

The MTA for the recipient’s domain places the status message into the MTA “in progress” (gwinprog) queue.

The MTA for the recipient’s domain communicates the status message to the MTA for the sender’s domain by way of TCP/IP.

The MTA for the sender’s domain places the status message into the MTA “in progress” (gwinprog) queue.

Message Delivery to a Different Domain 29

Stage Icon Description

MTA for

The MTA for the sender’s domain communicates the status message to the

POA for the sender’s post office by way of TCP/IP. Sender’s Domain

POA for Sender’s

The POA for the sender’s post office updates the sender’s message database

(msgnnn.db) with the Delivered status information (and possibly Opened as

well if the recipient has opened the message). Post Office

POA for

The POA for the sender’s post office communicates the status to the sender’s

GroupWise client by way of TCP/IP. Sender’s Post Office

Sender

When the sender checks the sent items in his or her mailbox in the GroupWise

client, the message displays a status of Delivered for each recipient (and

possibly Opened as well if the recipient has opened the message).

3.2 TCP/IP Link Closed: Transfer between Domains Delayed

This message flow diagram illustrates how a GroupWise message travels from one user to another when the domains are connected by a TCP/IP link and the link is closed.

Figure 3-2 Message Flow When the TCP/IP Link is Closed

wpcsin

POAa

wpcsin

0-7

ofmsg

msgnnn.db

ofuser

userxxx.db

offiles

fdo-7f

wpcsout

ads

ofs

MTAa

mslocal

0-7

wpcsout

ads

gwinprog

0-7

mshold

domainms

posta

0-7

postb

0-7

gatewayx

0-7

domainx

0-7

7 15

MTAb

mslocal

wpcsin

0-7

wpcsout

ads

gwinprog

0-7

mshold

domainms

posta

0-7

postb

0-7

gatewayx

0-7

domainx

0-7

POAb

wpcsin

0-7

ofmsg

msgnnn.db

ofuser

userxxx.db

offiles

fdo-7f

wpcsout

ads

ofs

0-7

30 GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure

+ 145 hidden pages

Novell GROUPWISE 7 TROUBLESHOOTING

Specifications and Main Features

Frequently Asked Questions

User Manual

Part I Message Flow Diagrams 11

1 Message Delivery in the Local Post Office 13

2 Message Delivery to a Different Post Office 19

3 Message Delivery to a Different Domain 27

4 Message Delivery to and from the Internet 35

5 Message Delivery through a Modem Connection 51

6 Administrative Database Update 59

Part II Directory Structure Diagrams 61

7 Message Transfer/Storage Directories 63

8 Agent Installation Directories 107

9 Software Distribution Directory 155

10 GroupWise Client Installation Directories 173

Part III Documentation Updates 181

A June 15, 2006 (GroupWise 7 SP1) 183

About This Guide

Message Delivery in the Local Post Office

1.1 Online Mode

1.2 Caching Mode

1.3 Remote Mode

Message Delivery to a Different Post Office

2.1 TCP/IP Link Open: Transfer between Post Offices Successful

2.2 TCP/IP Link Closed: Transfer between Post Offices Delayed

Message Delivery to a Different Domain

3.1 TCP/IP Link Open: Transfer between Domains Successful

3.2 TCP/IP Link Closed: Transfer between Domains Delayed