Novell GROUPWISE 8 - POST OFFICES User manual

Post Offices
III
161
novdocx (en) 22 June 2009
III
Post Offices
Chapter 11, “Creating a New Post Office,” on page 163
Chapter 12, “Managing Post Offices,” on page 183

162 GroupWise 8 Administration Guide
novdocx (en) 22 June 2009

Creating a New Post Office
11
163
novdocx (en) 22 June 2009
11
Creating a New Post Office
As your GroupWise®system grows, you typically need to add new post offices.
Section 11.1, “Understanding the Purpose of Post Offices,” on page 163
Section 11.2, “Planning a New Post Office,” on page 164
Section 11.3, “Setting Up the New Post Office,” on page 175
Section 11.4, “What’s Next,” on page 179
Section 11.5, “Post Office Worksheet,” on page 179
IMPORTANT: If you are creating a new post office in a clustered GroupWise system, see the
GroupWise 8 Interoperability Guide before you create the post office:
11.1 Understanding the Purpose of Post Offices
The post office serves as an administrative unit for a group of users and is used for addressing
messages. Each GroupWise user has an address that consists of a user ID, the user’s post office
name, the GroupWise domain name, and, optionally, an Internet domain name.
The following diagram illustrates the logical organization of a GroupWise domain with multiple
post offices. The two post offices belong to the domain. All of the objects under each post office
belong to that post office.
Figure 11-1 GroupWise Domain with Multiple Post Offices
As illustrated above, each post office must have at least one Post Office Agent (POA) running for it.
The POA delivers messages to users’ mailboxes and performs a variety of post office and mailbox
maintenance activities.
When you add a new post office, you must link it to a domain. The link defines how messages travel
between the post office and its domain. Links are discussed in detail in Chapter 10, “Managing the
Links between Domains and Post Offices,” on page 145.
GroupWise
Distribution
Lists
Domain Message
Transfer
Agent
Post Office
GroupWise
Users
Post Office
Post
Office
Agent
Post
Office
Agent
GroupWise
Resources
GroupWise
Distribution
Lists
GroupWise
Users
GroupWise
Resources
GroupWise
Library

164 GroupWise 8 Administration Guide
novdocx (en) 22 June 2009
Physically, a post office consists of a set of directories that house all the information stored in the
post office. To view the structure of the post office directory, see “Post Office Directory” in
GroupWise 8 Troubleshooting 3: Message Flow and Directory Structure. The post office directory
contains user mailboxes and messages, as well as other vital information. For an overview, see
Section 35.3, “Information Stored in the Post Office,” on page 476.
11.2 Planning a New Post Office
This section provides the information you need in order to decide when, where, and how to create a
new post office. The “Post Office Worksheet” on page 179 lists all the information you need as you
set up your post office. You should print the worksheet and fill it out as you complete the tasks listed
below.
Section 11.2.1, “Determining When to Add a Post Office,” on page 164
Section 11.2.2, “Selecting the Domain That the Post Office Will Belong To,” on page 165
Section 11.2.3, “Determining the Context for the Post Office Object,” on page 166
Section 11.2.4, “Choosing the Post Office Name,” on page 168
Section 11.2.5, “Deciding Where to Create the Post Office Directory,” on page 168
Section 11.2.6, “Deciding Where to Install the Agent Software,” on page 170
Section 11.2.7, “Deciding How to Link the New Post Office,” on page 172
Section 11.2.8, “Selecting the Post Office Language,” on page 173
Section 11.2.9, “Selecting the Post Office Time Zone,” on page 173
Section 11.2.10, “Selecting a Software Distribution Directory,” on page 173
Section 11.2.11, “Selecting a Post Office Security Level,” on page 174
Section 11.2.12, “Deciding if You Want to Create a Library for the New Post Office,” on
page 174
After you have completed the tasks and filled out the “Post Office Worksheet” on page 179, you are
ready to continue with Section 11.3, “Setting Up the New Post Office,” on page 175.
11.2.1 Determining When to Add a Post Office
After you have your basic GroupWise system up and running, you might need to expand it. How do
you know when you should add a post office? The answer to this depends on your company
organization, the number of users on your network, and the physical limitations of your network
servers.
“Physical Organization” on page 164
“Logical Organization” on page 165
“Number of Users” on page 165
“Demand on the POA” on page 165
Physical Organization
If your network spans several sites, you might want to create post offices (if not domains) at each
physical location. This reduces the demands on long distance network links.

Creating a New Post Office 165
novdocx (en) 22 June 2009
Logical Organization
Processing messages within a post office is faster and typically generates less network traffic than
messages traveling between different post offices. As you expand GroupWise, you might find it
useful to add post offices in order to group users who frequently send mail to each other.
Grouping users into post offices, based upon company organization or job function, makes
administrative tasks, such as creating distribution lists, limiting Address Book visibility, and
distributing shared folders, easier. For example, some employees might work in corporate functions
like accounting and human resources. Other employees might be involved in sales and marketing
and frequently attend meetings together, requiring frequent busy searches. Some areas, for example
the production floor, might not need a workstation or user account for each individual.
Number of Users
Although a GroupWise post office can support more than 10,000 users, you should consider adding
a post office when an existing post office has more than about 1000 to 2500 users and you expect it
to keep growing. There are several reasons for this:
It minimizes the impact if you have a problem with a server.
It keeps the time required to perform post office and mailbox maintenance activities including
backups from becoming excessive.
It allows room to grow while maintaining best performance.
Therefore, a good post office size is about 1000 to 2500 users and include all of the resources (such
as equipment, company cars, and conference rooms) and distribution lists they might need.
Demand on the POA
The POA is a very flexible component of your GroupWise system. Many aspects of its functioning
are configurable, to meet the particular needs of the post office it services, no matter what the size.
In addition, you can choose to run multiple POAs for the same post office, in order to specialize its
functioning, as described in:
Section 38.1.3, “Configuring a Dedicated Client/Server POA,” on page 564
Section 38.2.2, “Configuring a Dedicated Message File Processing POA,” on page 567
Section 38.3.3, “Configuring a Dedicated Indexing POA,” on page 571
Section 38.4.2, “Configuring a Dedicated Database Maintenance POA,” on page 576
As a result, the choice is up to you whether you prefer a single, large post office, perhaps with
multiple POAs, or multiple smaller post offices, each with its own POA.
11.2.2 Selecting the Domain That the Post Office Will Belong To
A post office is associated with a specific domain, even though it might reside in a different
organizational unit in the Novell®eDirectoryTM tree. If you have just one domain, the new post
office will belong to it. If you want to create a new domain as well as a new post office, see
Chapter 8, “Creating a New Domain,” on page 119.

166 GroupWise 8 Administration Guide
novdocx (en) 22 June 2009
In a multiple post office system, the domain organizes post offices into a logical grouping for
addressing and routing purposes. Each user in the domain has a GroupWise address that consists of
the user’s GroupWise ID, the post office name, the GroupWise domain name, and optionally, an
Internet domain name.
Domains function as the main administration units for the GroupWise system. Post office
information is stored in the domain database, as well as in the post office database. Changes are
distributed to each post office database from the domain.
The items in the worksheet are listed in the order you enter them when setting up your post office.
This planning section does not follow the same order as the worksheet, but all worksheet items are
covered.
11.2.3 Determining the Context for the Post Office Object
The eDirectory context of the Post Office object determines how you administer the post office. The
post office can be created in any Organization or Organizational Unit container in any context as
long as it is in the same tree as the domain. The following diagrams provide some examples of how
post offices can be placed in the eDirectory tree:
“GroupWise Objects Reflect Physical Locations” on page 166
“GroupWise Objects Reflect Company Organization” on page 167
“GroupWise Objects Are Grouped with Servers” on page 167
“GroupWise Objects Are Located in a Separate GroupWise Container” on page 167
GroupWise Objects Reflect Physical Locations
The GroupWise system below focuses on the physical layout of the company. Because most mail
traffic is generated by users in the same location, the mail traffic across the WAN is minimized. An
organizational unit was created for each site. A domain and post office were created under each
organizational unit, corresponding to the city. The sites can be administered centrally or at each site.
Administrator rights can be assigned at the domain level.
Figure 11-2 A GroupWise System Following the Physical Layout of the Company
WORKSHEET
Under Item 3: GroupWise Domain, specify the GroupWise domain that the new post office will belong to.
WORKSHEET
Under Item 1: eDirectory Container, specify the name of the eDirectory container where you want to
create the new post office.

Creating a New Post Office 167
novdocx (en) 22 June 2009
GroupWise Objects Reflect Company Organization
The following GroupWise system focuses on departmental organization, as does the eDirectory tree.
GroupWise domains and post offices parallel eDirectory organizational units, placing the domains
and post offices within the organizational units containing the users that belong to them.
Figure 11-3 A GroupWise System Following the Departmental Organization of the Company
GroupWise Objects Are Grouped with Servers
Because domains and post offices have directory structures on network servers, you can also choose
to place the Domain and Post Office objects in the same context as the servers where the directories
reside, as shown in the following example.
Figure 11-4 A GroupWise System with the Domains and Post Offices Grouped with the Servers
GroupWise Objects Are Located in a Separate GroupWise Container
Domains and post offices can also be created in their own organizational unit. Administratively, this
approach makes it easier to restrict a GroupWise administrator’s object and property rights to
GroupWise objects only.

168 GroupWise 8 Administration Guide
novdocx (en) 22 June 2009
Figure 11-5 GroupWise Objects Located in Their Own Organizational Unit
11.2.4 Choosing the Post Office Name
The post office must be given a unique name. The name is used for addressing and routing purposes
within GroupWise, and might appear in the GroupWise Address Book.
The post office name can reflect a location, organization, department, and so on. For example, you
might want the domain name to be the location (for example, Provo) while the post office name is
one of the company’s departments (for example, Research). Name the new post office carefully.
After it is created, the name cannot be changed.
The post office name should consist of a single string. Use underscores (_) rather than spaces as
separators between words to facilitate addressing across the Internet. Do not use any of the
following invalid characters in the post office name:
11.2.5 Deciding Where to Create the Post Office Directory
Logically, the Post Office object resides in eDirectory and is administered through ConsoleOne®.
Physically, the post office has a directory structure for databases, message queues, and other files.
The post office directory structure can be created on any of the supported platforms listed in
“GroupWise Administration Requirements” in the GroupWise 8 Installation Guide. It can also be
ASCII characters 0-31 Comma ,
Asterisk * Double quote "
At sign @ Extended ASCII characters that are graphical or typographical symbols;
accented characters in the extended range can be used
Backslash \ Parentheses ( )
Braces { } Period .
Colon :
WORKSHEET
Under Item 2: Post Office Name, specify the post office name.
Under Item 9: Post Office Description, provide a description for the post office to help you identify its
function in the system.

Creating a New Post Office 169
novdocx (en) 22 June 2009
located on any platform that a POA running on a supported platform could access successfully. The
server where you create the post office directory structure can be in the same tree as the Post Office
object or in another tree.
Databases and directories in the post office are updated as messages are sent. Because the POA
typically makes these updates, we recommend that you place the post office directory on a server
that can be easily accessed by the POA and, depending on configuration, the MTA. Users typically
need a TCP/IP connection to the POA in order to access their mailboxes.
When you are planning the post office directory location and which users will belong to the post
office, consider the following:
Post Office Directory Space Requirements: You need a minimum of 50 MB for each user.
Because the message store can require considerable disk space, we recommend you allow each
user at least 200 MB of storage space. You should also take into consideration the size of
attachments, and your archive and delete policies. If message attachments are large and you are
not planning to require users to archive or delete old messages, allow more storage. If you are
creating libraries you need even more storage, depending on the size and number of documents.
For details about managing post office disk space, see Section 12.3, “Managing Disk Space
Usage in the Post Office,” on page 190.
Network Access by the POA: The POA must have direct network access (mapped drive or
file system mount) to the post office directory so that it can write to user databases
(
userxxx.db ) and message databases ( msgnnn.db ). This issue is discussed in detail in
Section 11.2.6, “Deciding Where to Install the Agent Software,” on page 170.
Security from User Access: Users typically access their mailboxes through a TCP/IP
connection to the POA. Therefore, users do not need access to the post office directory. You
should create it in a location you can easily secure; otherwise, you could have files
inadvertently moved or deleted.
Choose an empty directory for the new post office. If you want, the directory can reflect the name of
the post office, for example research for the Research post office. Use the following platform-
specific conventions:
Choose the name and path carefully. After the post office directory is created, it is difficult to rename
it. If the directory you specify does not exist, it is created when you create the post office. Do not
create the post office directory under another domain or post office directory.
NetWare: Use a maximum of 8 characters
Linux: Use only lowercase characters
Windows: No limitations.
WORKSHEET
Under Item 4: Post Office Database Location, specify the full path for the post office directory.

170 GroupWise 8 Administration Guide
novdocx (en) 22 June 2009
11.2.6 Deciding Where to Install the Agent Software
You must run a new instance of the POA for each new post office. To review the functions of the
POA for the post office, see Section 35.5, “Role of the Post Office Agent,” on page 481. For
complete POA installation instructions and system requirements, see “Installing GroupWise
Agents” in the GroupWise 8 Installation Guide.
When planning the installation of the POA, you need to consider how the new post office links to its
domain. For an overview of link configuration, see Chapter 10, “Managing the Links between
Domains and Post Offices,” on page 145.
The POA requires direct network access (mapped drive or file system mount) to the post office
directory so that it can write to user databases (userxxx.db) and message databases (msgnnn.db).
Consider the following alternatives when selecting a location for the POA:
“POA Access to the New Post Office: Local vs. Remote” on page 170
“MTA Access to the New Post Office: Mapped and UNC Links vs. TCP/IP Links” on page 171
“Cross-Platform Issues” on page 172
POA Access to the New Post Office: Local vs. Remote
Running the POA locally on the same server where the post office resides simplifies network
connections (no login is required), reduces network traffic, and protects database integrity. In the
following diagram, the agent software is installed on the same server where the domain and post
office reside.
Figure 11-6 Agent Software on the Same Server with the Domain and Post Office
Running the POA on a remote server allows you to place the heaviest processing load on your
highest performing server. In the following diagram, the agent software is installed on a different
server from where the domains and post offices reside.
Figure 11-7 Agent Software on a Different Server than the Domain and Post Office
WORKSHEET
Under Item 11: Agent Location, indicate whether you plan to run the POA on the same server where the
post office directory is located (recommended), or on a different server.
Under Item 12: Agent Platform, specify the platform where the POA will run (NetWare, Linux, or
Windows).
Acct-Dom
Acct-PO1
POA MTA
Dev-Dom
Dev-PO1
POA MTA
Dev-Dom
Dev-PO1
POA
MTA
Windows NetWare

Creating a New Post Office 171
novdocx (en) 22 June 2009
When you run the POA on a different server from where its directory structure and databases are
located, you need to provide adequate access.
MTA Access to the New Post Office: Mapped and UNC Links vs. TCP/IP Links
If a domain includes multiple post offices, the new post office will probably reside on different
server from where the domain is located. If you plan to use mapped or UNC links between the
domain and the new post office, the MTA requires the same access to the post office directory as it
requires to the domain directory.
Figure 11-8 MTA Access Using Mapped or UNC Links
To avoid these direct network access requirements between the MTA and a new post office, you can
use TCP/IP links between the domain and the new post office.
Figure 11-9 MTA Access Using TCP/IP Links
NetWare: If the NetWare®POA needs direct network access to another NetWare server where the
post office is located, you must add the /dn switch or the /user and /password switches to
the POA startup file to provide authentication information. Username and password
information can also be provided in the Remote File Server Settings box of the Post Office
Settings page in ConsoleOne.
Linux: If the Linux POA needs direct network access to another Linux server, you must mount
the file system where the post office is located before you start the Linux POA.
Windows: If the Windows POA needs direct network access to another Windows server where the
post office is located, you must map a drive to the other server before you start the
Windows POA.
NetWare: If the NetWare MTA needs direct network access to a new post office on another NetWare
server, you must add the /dn switch or the /user and /password switches to the MTA
startup file to provide authentication information.
Linux: N/A. The Linux MTA requires TCP/IP links to the POA.
Windows: If the Windows MTA needs direct network access to a new post office on another
Windows server, you must map a drive to the post office directory before you start the
MTA.
POA
Dev-Dom
Dev-PO1
POA
MTA MTA
Acct-Dom
Acct-PO1
POA
Dev-Dom
Dev-PO1
POA
MTA MTA
Acct-Dom
Acct-PO1

172 GroupWise 8 Administration Guide
novdocx (en) 22 June 2009
When using TCP/IP links, the MTA does not write message files into message queues in the post
office directory structure. Instead, the MTA communicates the information to the POA by way of
TCP/IP and then the POA uses its direct network access to write the information.
Cross-Platform Issues
In most cases, it is most efficient if you match the POA platform with the network operating system
where the post office resides. For example, if you create a new post office on a NetWare server, use
the NetWare POA.
If you decide not to run the POA on the same platform as the post office, the POA must still have
direct network access to the post office directory so that it can write to user databases (
userxxx.db )
and message databases (
msgnnn.db ). For example, you can set up the new post office on a NetWare
server and run the Windows POA on a Windows server to service it.
Figure 11-10 A Domain on a NetWare Server and the MTA on a Windows Server
However, the NetWare POA cannot service a post office located on a Windows server because
Windows does not support the required cross-platform connection.
If you are using mapped or UNC links to the new post office, the MTA must also have direct
network access to the post office directory so that it can write message files into the post office
message queues. You can, for example, run the agents on a Windows server while domains and post
offices are located on NetWare servers.
Figure 11-11 Agents on a Windows Server and Domains and Post Offices on a NetWare Server
Again, the opposite combination of NetWare agents servicing domains and post offices on Windows
servers is not an option because Windows does not support the required cross-platform connection.
To avoid these cross-platform access issues, use TCP/IP links between a domain and its post offices.
For more detailed information, see Section 40.7, “Cross-Platform Issues between Domains and Post
Offices,” on page 623.
11.2.7 Deciding How to Link the New Post Office
When you create a new post office, you have the opportunity to choose the type of link to use
between the new post office and its domain. Based on issues discussed in the preceding section, you
might decide to set up a TCP/IP link between the new post office and its domain.
Dev-Dom
Dev-PO1
POA
MTA
Windows NetWare
POA
Dev-Dom
Dev-PO1
POA
MTA MTA
Acct-Dom
Acct-PO1
NetWare Windows NetWare

Creating a New Post Office 173
novdocx (en) 22 June 2009
11.2.8 Selecting the Post Office Language
The post office language determines the sort order for items in the GroupWise Address Book.
The post office defaults to the same language as its domain unless you specify otherwise. For
example, if you set the domain and post office language to English-US, the Address Book items are
sorted according to English-US sort order rules. This is true even if some users in the post office are
running non-English GroupWise clients such as German or Japanese. Their client interface and Help
files are in German or Japanese, but the Address Book sort order is according to English-US
standards. Time, date, and number formats for the non-English clients defaults to the workstation
language.
11.2.9 Selecting the Post Office Time Zone
When a message is sent from a user in one time zone to a user in another time zone, GroupWise
adjusts the message’s time so that it is correct for the recipient’s time zone. For example, if a user in
New York (GMT -05:00, Eastern Time) schedules a user in Los Angeles (GMT -08:00, Pacific
Time) for a conference call at 4:00 p.m. Eastern Time, the appointment is scheduled in the Los
Angeles user’s calendar at 1:00 p.m. Pacific Time.
The domain time zone becomes the default time zone for each post office in the domain.
11.2.10 Selecting a Software Distribution Directory
A software distribution directory was created when your GroupWise system was initially set up. The
software distribution directory contains files that users need in order to set up the GroupWise
Windows or Linux/Mac client on their workstations. Additional software distribution directories
might have been created since that time to accommodate users in various locations, as described in
Section 4.9.1, “Creating a Software Distribution Directory,” on page 70.
You can select the most convenient software distribution directory for the new post office.
WORKSHEET
Under Item 13: Link to Domain, indicate the type of link you plan to set up between the new post office
and its domain.
WORKSHEET
Under Item 5: Post Office Language, specify the post office language.
WORKSHEET
Under Item 6: Time Zone, specify the time zone for the new post office.
WORKSHEET
Under Item 7: Software Distribution Directory, specify the name of the software distribution directory from
which users in the new post office will install the GroupWise client software on their Windows, Linux, or
Macintosh workstations.

174 GroupWise 8 Administration Guide
novdocx (en) 22 June 2009
11.2.11 Selecting a Post Office Security Level
Post office security settings affect two types of GroupWise users:
Users who do not set passwords on their mailboxes
Users who use LDAP passwords instead of GroupWise passwords to access their mailboxes
After a user sets a GroupWise password on his or her mailbox, the post office security level no
longer applies. The user is always prompted for the password unless the administrator has set certain
client options in ConsoleOne to prevent the password prompt, as described in Section 74.1.3,
“Managing GroupWise Passwords,” on page 1152.
In the absence of GroupWise passwords on user mailboxes, the post office security level takes
effect. By default, a new post office is created with high security, which provides protection to
GroupWise mailboxes through other types of authentication other than GroupWise passwords. In a
high security post office, you can choose between eDirectory authentication and LDAP
authentication:
eDirectory Authentication: If you use eDirectory authentication for a post office, users must
be logged in to eDirectory in order to access their GroupWise mailboxes.
LDAP Authentication: If you use LDAP authentication for a post office, users must
successfully authenticate to an LDAP server in order to access their GroupWise mailboxes.
In a low security post office, mailboxes are completely unprotected. Without a GroupWise
password, any user’s mailbox could be accessed by another user who knows how to use the @u-
userID startup switch. This security level is not recommended.
11.2.12 Deciding if You Want to Create a Library for the New
Post Office
If you anticipate that users on this post office will require document management services, you can
create a library at the same time you create the post office. The library is created with all of the
default library options including Store Documents at Post Office. Using a document storage area is
preferable to storing documents at the post office because a document storage area can be moved.
You should appropriately configure the library immediately after it is created, before users begin to
store documents there. See Part VII, “Libraries and Documents,” on page 305.
WORKSHEET
Under Item 10: Post Office Security Level, mark the security level for the post office. If you choose high
security, indicate the type of authentication you plan to use.
WORKSHEET
Under Item 8: Create Library, indicate whether or not you want to immediately create a library for the new
post office. You can always add a library to the post office at a later time.

Creating a New Post Office 175
novdocx (en) 22 June 2009
11.3 Setting Up the New Post Office
You should have already reviewed Section 11.2, “Planning a New Post Office,” on page 164 and
filled out Section 11.5, “Post Office Worksheet,” on page 179. Complete the following tasks to
create a new post office.
Section 11.3.1, “Creating the New Post Office,” on page 175
Section 11.3.2, “Configuring the POA for the New Post Office,” on page 178
Section 11.3.3, “Installing and Starting the New POA,” on page 178
Section 11.3.4, “Setting Up User Access to the New Post Office,” on page 179
11.3.1 Creating the New Post Office
1Make sure you are logged in to the tree where you want to create the post office.
This must be the same tree as the domain that the post office belongs to (worksheet item 3).
2In ConsoleOne, browse to and right-click the eDirectory container where you want to create the
post office (worksheet item 1), then click New > Object.
3Double-click GroupWise Post Office, then fill in the fields in the Create GroupWise Post Office
dialog box (worksheet items 2 through 8).
4Make sure the Configure Links and Define Additional Properties options are selected, then
click OK to display the Link Configuration Wizard.

176 GroupWise 8 Administration Guide
novdocx (en) 22 June 2009
5Follow the on-screen instructions to define how the post office links to its domain. When you
finish defining the link, ConsoleOne creates the Post Office object and displays the post office
Identification page.
6Fill in the Description field (worksheet item 9).
7Click GroupWise > Post Office Settings to display the Post Office Settings page.

Creating a New Post Office 177
novdocx (en) 22 June 2009
8Select the software distribution directory for the post office (worksheet item 7).
9If the POA will run on a different server from where the post office directory, a library, or a
document storage area is located, provide a username and password that enables the POA to
access the remote location (worksheet item 11).
10 Click GroupWise > Security to display the Security page.
11 Provide the post office security level and authentication type for the post office (worksheet item
10). For additional LDAP instructions, see Section 36.3.4, “Providing LDAP Authentication
for GroupWise Users,” on page 514.
12 Click OK to save the post office information.

178 GroupWise 8 Administration Guide
novdocx (en) 22 June 2009
11.3.2 Configuring the POA for the New Post Office
Although there are many POA settings, the default settings are sufficient to get your post office
operational. However, there are a few important settings that you can conveniently modify before
you install the agent software.
1In ConsoleOne, double-click the new Post Office object.
2Right-click the POA object, then click Properties to display the POA Identification page.
3Provide a description for the POA.
The description displays on the POA agent console as the POA runs.
4Select the platform where the POA will run (worksheet item 12).
5If you have created the post office in a clustered environment, follow the instructions in the
appropriate section of the GroupWise 8 Interoperability Guide.
6For more POA configuration options, see Section 12.11, “Changing POA Configuration to
Meet Post Office Needs,” on page 209.
7Click OK to save the POA configuration information.
11.3.3 Installing and Starting the New POA
To install the POA for the new post office to the location recorded under worksheet item 11, follow
the instructions in “Installing GroupWise Agents” in the GroupWise 8 Installation Guide.

Creating a New Post Office 179
novdocx (en) 22 June 2009
11.3.4 Setting Up User Access to the New Post Office
The post office access mode determines how GroupWise client users access their mailboxes. By
default, the GroupWise Windows and Linux/Mac clients use client/server access to the post office.
Client/server access provides the following benefits:
Client/server access provides the greatest level of security. Users do not need rights to the post
office directory because the GroupWise client does not write directly to databases in the post
office. All database updates are performed by the POA.
Client/server access eliminates the need for separate network logins and passwords. This
avoids problems with login restrictions, changing passwords, and insufficient network rights.
Client/server access allows the GroupWise client to maintain multiple simultaneous
connections to the post office.
With client/server access mode, proxy rights can be granted to any user visible in the Address
Book.
Historical Note: In GroupWise 5.x, the GroupWise client allowed the user to enter a path to the post
office directory to facilitate direct access mode. The GroupWise 6.xand later clients no longer offer
the user that option. However, you can force the GroupWise 6.xand later client to use direct access
mode by starting it with the /ph switch and providing the path to the post office directory.
Continue with Section 11.4, “What’s Next,” on page 179.
11.4 What’s Next
After you have created the new post office and started its POA, you are ready to expand the post
office by:
Adding users to the post office. See “Users” on page 211.
Defining groups of users (distribution lists) that GroupWise users can select when addressing
messages. See “Distribution Lists, Groups, and Organizational Roles” on page 275.
Defining resources (for example, conference rooms or company cars) that users can schedule.
See “Resources” on page 259.
Defining libraries and setting up Document Management Services. See “Libraries and
Documents” on page 305.
Setting up the GroupWise Windows or Linux/Mac client software so that GroupWise users can
run the client from Windows, Linux, or Macintosh workstations. See “Client” on page 1073.
Configuring the POA for optimal performance and security. See “Post Office Agent” on
page 473.
11.5 Post Office Worksheet
Use this worksheet as you complete the tasks in Section 11.2, “Planning a New Post Office,” on
page 164.

180 GroupWise 8 Administration Guide
novdocx (en) 22 June 2009
Item Explanation
1) eDirectory Container Specify the name of the eDirectory container where you plan to create the
new post office.
For more information, see Section 11.2.3, “Determining the Context for the
Post Office Object,” on page 166.
2) Post Office Name Specify a name for the new post office. Choose the name carefully. After
the post office is created, it cannot be renamed.
For more information, see Section 11.2.4, “Choosing the Post Office
Name,” on page 168.
3) GroupWise Domain Specify the domain this post office will belong to.
For more information, see Section 11.2.2, “Selecting the Domain That the
Post Office Will Belong To,” on page 165.
4) Post Office Database
Location
Specify the path for the post office directory. Choose the post office
directory carefully. After it is created, it is difficult to rename.
For more information, see Section 11.2.5, “Deciding Where to Create the
Post Office Directory,” on page 168.
5) Post Office Language Specify the post office language if it is different from the domain language.
For more information, see Section 11.2.8, “Selecting the Post Office
Language,” on page 173.
6) Post Office Time Zone Specify the time zone for the post office if it is different from the domain
time zone.
For more information, see See Section 11.2.9, “Selecting the Post Office
Time Zone,” on page 173.
7) Software Distribution
Directory:
Specify the name of the software distribution directory for the new post
office.
For more information, see Section 11.2.10, “Selecting a Software
Distribution Directory,” on page 173.
8) Create Library:
Yes
No
Mark whether or not you want to create a library for the new post office at
the same time you create the new post office.
For more information, see Section 11.2.12, “Deciding if You Want to Create
a Library for the New Post Office,” on page 174.
9) Post Office Description Provide a description for the new post office to help you identify its function
in the system.
10) Post Office Security
Level:
Low
High
eDirectory
authentication
LDAP authentication
Mark the security level for the post offices. For high security, mark the type
of authentication you plan to use.
For more information, see Section 11.2.11, “Selecting a Post Office
Security Level,” on page 174.