Novell GROUPWISE 7 - POST OFFICE AGENT User manual

Post Office Agent
IX
novdocx (en) 11 December 2007
461
IX
Post Office Agent
Chapter 35, “Understanding Message Delivery and Storage in the Post Office,” on page 463
Chapter 36, “Configuring the POA,” on page 475
Chapter 37, “Monitoring the POA,” on page 515
Chapter 38, “Optimizing the POA,” on page 547
Chapter 39, “Using POA Startup Switches,” on page 565

462 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007

Understanding Message Delivery and Storage in the Post Office
35
novdocx (en) 11 December 2007
463
35
Understanding Message Delivery
and Storage in the Post Office
A post office is a collection of user mailboxes and GroupWise®objects. Messages are delivered into
mailboxes by the Post Office Agent (POA). The following topics help you understand the post office
and the functions of the POA:
Section 35.1, “Post Office Representation in ConsoleOne,” on page 463
Section 35.2, “Post Office Directory Structure,” on page 464
Section 35.3, “Information Stored in the Post Office,” on page 464
Section 35.4, “Post Office Access Mode,” on page 468
Section 35.5, “Role of the Post Office Agent,” on page 469
Section 35.6, “Message Flow in the Post Office,” on page 471
Section 35.7, “Cross-Platform Issues in the Post Office,” on page 471
35.1 Post Office Representation in ConsoleOne
In ConsoleOne®, post offices are container objects that contain at least one POA object, as shown
below:
Figure 35-1 ConsoleOne View Showing the POA Object
Although each post office is linked to a domain, it does not display as subordinate to the domain in
the Console View. However, using the GroupWise View, you can display post offices as subordinate
to the domains to which they are linked in your GroupWise system.

464 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
Figure 35-2 GroupWise View Showing Post Offices in Relationship to Domains
35.2 Post Office Directory Structure
Physically, a post office consists of a set of directories that house all the information stored in the
post office. See “Post Office Directory” in GroupWise 7 Troubleshooting 3: Message Flow and
Directory Structure.
35.3 Information Stored in the Post Office
The following types of information are stored in the post office:
Section 35.3.1, “Post Office Database,” on page 464
Section 35.3.2, “Message Store,” on page 464
Section 35.3.3, “Guardian Database,” on page 466
Section 35.3.4, “Agent Input/Output Queues in the Post Office,” on page 466
Section 35.3.5, “Libraries (optional),” on page 467
All databases in the post office should be backed up regularly. How often you back up GroupWise
databases depends on the reliability of your network and hardware. See Section 31.2, “Backing Up a
Post Office,” on page 407.
35.3.1 Post Office Database
The post office database (wphost.db) contains all administrative information for the post office,
including a copy of the GroupWise Address Book. This information is necessary for users to send
messages to others in the GroupWise system.
35.3.2 Message Store
GroupWise messages are made up of three parts:
Message Header: The message header contains addressing information including the sender’s
address, recipient’s address, message priority, status level, and a pointer that links the header to
the message body.

Understanding Message Delivery and Storage in the Post Office 465
novdocx (en) 11 December 2007
Message Body: The message body contains the message text in an encrypted format and a
distribution list containing user IDs of the sender and recipients.
File Attachments (optional): File attachments can be any type of file that is attached to the
message.
The message store consists of directories and databases that hold messages. The message store is
shared by all members of the post office so only one copy of a message and its attachments is stored
in the post office, no matter how many members of the post office receive the message. This makes
the system more efficient in terms of message processing, speed, and storage space.
All information in the message store is encrypted to prevent unauthorized access.
The message store contains the following components:
“User Databases” on page 465
“Message Databases” on page 465
“Attachments Directory” on page 466
User Databases
Each member of the post office has a personal database (userxxx.db) which represents the user’s
mailbox. The user database contains the following:
Message header information
Pointers to messages
Folder assignments
Personal groups
Personal address books
Rules
Contacts
Checklists
Categories
Junk Mail lists
When a member of another post office shares a folder with one or more members of the local post
office, a “prime user” database (puxxxxx.db) is created to store the shared information. The
“prime user” is the owner of the shared information.
Local user databases and prime user databases are stored in the ofuser directory in the post office.
Message Databases
Each member of the post office is arbitrarily assigned to a message database (msgnnn.db) where
the body portions of messages are stored. Many users in a post office share a single message
database. There can be as many as 255 message databases (numbered 0 through 254) in a post
office. Message databases are stored in the ofmsg directory in the post office.
Historical Note: Prior to GroupWise 7, the POA created a maximum of 25 message databases per
post office. The current maximum of 255 message databases speeds up message delivery and
minimizes user impact if a database is damaged.

466 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
Outgoing messages from local senders are stored in the message database assigned to each sender.
Incoming messages from users in other post offices are stored in the message database that
corresponds to the message database assigned to the sender in his or her own post office. In each
case, only one copy of the message is stored in the post office, no matter how many members of the
post office it is addressed to.
Attachments Directory
The attachments directory (offiles) contains subdirectories that store file attachments, message
text, and distribution lists that exceed 2 KB. Items of this size are stored more efficiently as files
than as database records. The message database contains a pointer to where each item is found.
35.3.3 Guardian Database
The guardian database (ngwguard.db) serves as the master copy of the data dictionary
information for the following subordinate databases in the post office:
User databases (userxxx.db)
Message databases (msgnnn.db)
Prime user databases (puxxxxx.db)
Library databases (dmsh.db and dmxxnn01-FF.db)
The guardian database is vital to GroupWise functioning. Therefore, the POA has an automated
back-up and roll-forward process to protect it. The POA keeps a known good copy of the guardian
database called ngwguard.fbk. Whenever it modifies the ngwguard.db file, the POA also
records the transaction in the roll-forward transaction log called ngwguard.rfl. If the POA
detects damage to the ngwguard.db file on startup or during a write transaction, it goes back to
the ngwguard.fbk file (the “fall back” copy) and applies the transactions recorded in the
ngwguard.rfl file to create a new, valid and up-to-date ngwguard.db.
In addition to the POA back-up and roll-forward process, you should still back up the
ngwguard.db, ngwguard.fbk, and ngwguard.rfl files regularly to protect against media
failure. Without a valid ngwguard.db file, you cannot access your e-mail. With current
ngwguard.fbk and ngwguard.rfl files, a valid ngwguard.db file can be rebuilt should the
need arise.
The ngwguard.dc file is the structural template for building the guardian database and its
subordinate databases. Also called a dictionary file, the ngwguard.dc file contains schema
information, such as data types and record indexes. If this dictionary file is missing, no additional
databases can be created in the post office.
35.3.4 Agent Input/Output Queues in the Post Office
Each post office contains agent input/output queues where messages are deposited and picked up for
processing by the POA and the MTA. The MTA transfers messages into and out of the post office,
while the POA handles message delivery.
For illustrations of the processes presented below, see “Message Delivery to a Different Post Office”
and “Message Delivery to a Different Domain” in GroupWise 7 Troubleshooting 3: Message Flow
and Directory Structure.

Understanding Message Delivery and Storage in the Post Office 467
novdocx (en) 11 December 2007
MTA Output Queue in the Post Office
The MTA output queue in each post office is the post_office\wpcsout directory.
If the MTA has a mapped or UNC link to the post office, the MTA writes user messages directly into
its output queue, which requires write access to the post office. If the MTA has a TCP/IP link to the
post office, the MTA transfers user messages to the POA by way of TCP/IP. The POA then stores the
messages in the MTA output queue on behalf of the MTA, so the MTA does not need write access to
the post office.
The post_office\wpcsout\ofs subdirectory is where the MTA transfers user messages for
delivery by the POA to users’ mailboxes in the local post office.
The MTA post_office\wpcsout\ads subdirectory is where the MTA transfers
administrative messages instructing the POA admin thread to update the post office database
(wphost.db).
POA Input Queue in the Post Office
The POA input queue in each post office is the post_office\wpcsout directory, which is the
same as the MTA output queue.
The post_office\wpcsout\ofs subdirectory is where the POA picks up user messages
deposited there by the MTA and updates the local message store, so users receive their messages.
The post_office\wpcsout\ads subdirectory is where the POA admin thread picks up
administrative messages deposited there by the MTA and updates the post office database
(wphost.db).
POA Output Queue in the Post Office
The POA output queue (post_office\wpcsin) is where the POA deposits user messages for the MTA
to transfer to other domains and post offices.
Historical Note: In earlier versions of GroupWise, the GroupWise client wrote user messages to the
POA output queue when using direct access to the post office. In GroupWise 6.xand later, client/
server access to the post office is the preferred method.
MTA Input Queue in the Post Office
The MTA input queue in each post office (post_office\wpcsin) is the same as the POA
output queue. The MTA picks up user messages deposited there by the POA and transfers them to
other domains and post offices.
For a mapped or UNC link between the domain and post office, the MTA requires read/write access
rights to its input/output queues in the post office. For a TCP/IP link, no access rights are required
because messages are communicated to the MTA by way of TCP/IP.
35.3.5 Libraries (optional)
A library is a collection of documents and document properties stored in a database system that can
be managed and searched. You do not need to set up libraries unless you are using GroupWise
Document Management Services (DMS). See Part VII, “Libraries and Documents,” on page 291.

468 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
Library Databases
The databases for managing libraries are stored in the gwdms directory and its subdirectories in the
post office.
The dmsh.db file is a database shared by all libraries in the post office. It contains information
about where each library in the post office is located.
Each library has its own subdirectory in the gwdms directory. In each library directory, the
dmxxnn01-FF.db files contain information specific to that library, such as document properties
and what users have rights to access the library.
Document Storage Areas
The actual documents in a library are not kept in the library databases. They are kept in a document
storage area, which consists of a series of directories for storing document files. Documents are
encrypted and stored in BLOBs (binary large objects) to make document management easier. A
document, its versions, and related objects are stored together in the same BLOB.
A document storage area might be located in the post office directory structure, or in some other
location where more storage space is available. If it is located in the post office, the document
storage area can never be moved. Therefore, storing documents in the post office directory structure
is not usually recommended. If it is stored outside the post office, a document storage area can be
moved when additional disk space is required.
35.4 Post Office Access Mode
The GroupWise 6.xand later Windows client and the GroupWise 6.5 and later Cross-Platform client
both use client/server access mode to the post office. This requires a TCP/IP connection between the
GroupWise clients and the POA in order for users to access their mailboxes. Benefits of client/server
access include:
Load Balancing: The workload is split between the client workstation and the POA on another
server. The POA can perform a processor-intensive request while the client is doing something
else.
Database Integrity: The GroupWise client does not need write access to databases in the post
office. Therefore, client failures cannot damage databases.
Reduced Network Traffic: Requests are processed on the POA server and only the results are
sent back across the network to the client workstation.
Tighter Security: Client users do not need to log in to the server where the post office is
located. This eliminates the need for users to have write access to the post office directory.
Scalability: More concurrent users can be supported in a single post office.
Platform Independence: The GroupWise client on any platform can access the post office by
way of TCP/IP communication with the POA.
Simplified Client Connections: The GroupWise client can communicate with any POA in the
GroupWise system. Any POA can then redirect the client to connect to the correct POA for the
users’ post office.
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

Understanding Message Delivery and Storage in the Post Office 469
novdocx (en) 11 December 2007
the user that option. However, you can force the GroupWise 6.xand later client to use direct access
by starting it with the /ph switch and providing the path to the post office directory.
35.5 Role of the Post Office Agent
The GroupWise Post Office Agent (POA) delivers messages to users’ mailboxes, connects users to
their post offices in client/server access mode, updates post office databases, indexes messages and
documents, and performs other post office-related tasks. You must run at least one POA for each
post office.
The following sections help you understand the various functions of the POA:
Section 35.5.1, “Client/Server Processing,” on page 469
Section 35.5.2, “Message File Processing,” on page 470
Section 35.5.3, “Other POA Functions,” on page 470
35.5.1 Client/Server Processing
Using client/server access mode, the GroupWise client maintains one or more TCP/IP connections
with the POA and does not access the post office directly. Consequently, the performance of the
POA in responding to requests from the GroupWise client directly affects the GroupWise client’s
responsiveness to users. To provide the highest responsiveness to client users, you can configure a
POA just to handle client/server processing. See Section 38.1.3, “Configuring a Dedicated Client/
Server POA,” on page 550.
When using client/server access mode, the GroupWise client can be configured to control how much
time it spends actually connected to the POA.
In Online mode, the client is continuously connected.
In Caching mode, the client connects at regular intervals to check for incoming messages and
also whenever the client user sends a message. Address lookup is performed locally. Caching
mode allows the POA to service a much higher number of users than Online Mode.
In Remote mode, the client connects whenever the client user chooses, such as when using a
brief modem connection to download and upload messages.
NOTE: Remote mode is not currently available in the Cross-Platform client.
For more information about the client modes available with client/server access mode, see “Using
Caching Mode” and “Using Remote Mode” in the GroupWise 7 Windows Client User Guide and
“Using Caching Mode” in the GroupWise 7 Cross-Platform Client User Guide.
Client/server access mode also allows users to access their GroupWise mailboxes from POP and
IMAP clients, in addition to the GroupWise client. See Section 36.2.3, “Supporting IMAP Clients,”
on page 490.
In client/server mode, the POA can provide and, if necessary, force secure SSL connections with all
clients. See Section 36.3.3, “Securing the Post Office with SSL Connections to the POA,” on
page 498.

470 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
35.5.2 Message File Processing
Messages from users in other post offices arrive in the local post office in the form of message files
deposited in the POA input queue. See Section 35.3.4, “Agent Input/Output Queues in the Post
Office,” on page 466.
The POA picks up the message files and updates all user and message databases to deliver incoming
messages in the local post office. To provide timely delivery for a large volume of incoming
messages, you can configure a POA just to handle message file processing. See Section 38.2.2,
“Configuring a Dedicated Message File Processing POA,” on page 553.
35.5.3 Other POA Functions
In addition to client/server processing (interacting with client users) and message file processing
(delivering messages), the POA:
Performs indexing tasks for document management. See Section 38.3.1, “Regulating
Indexing,” on page 555.
Performs scheduled maintenance on databases in the post office. See Section 36.4.1,
“Scheduling Database Maintenance,” on page 507.
Monitors and manages disk space usage in the post office. See Section 36.4.2, “Scheduling
Disk Space Management,” on page 510.
Restricts the size of messages that users can send outside the post office. See Section 36.2.8,
“Restricting Message Size between Post Offices,” on page 495.
Primes users’ mailboxes for Caching mode. See Section 36.2.7, “Supporting Forced Mailbox
Caching,” on page 494.
Performs nightly user upkeep so users do not need to wait while the GroupWise client performs
it; also creates a downloadable version of the system Address Book for Remote and Caching
users. See Section 36.4.3, “Performing Nightly User Upkeep,” on page 513.
Provides LDAP authentication and LDAP server pooling. See Section 36.3.4, “Providing
LDAP Authentication for GroupWise Users,” on page 501.
Prevents unauthorized access to the post office. See Section 36.3.5, “Enabling Intruder
Detection,” on page 506.
Tracks the GroupWise client software in use in the post office. See Section 36.2.6, “Checking
What GroupWise Clients Are in Use,” on page 492.
Automatically detects and repairs invalid information in user databases (userxxx.db) and
message databases (msgnnn.db) for the local post office by using an efficient multi-threaded
process. See Section 38.4.1, “Adjusting the Number of POA Threads for Database
Maintenance,” on page 559.
Automatically detects and repairs invalid information in the post office database
(wphost.db).
Automatically detects and repairs damage to the guardian database (ngwguard.db) in the
post office.
Updates the post office database whenever GroupWise users, resources, post offices, or other
GroupWise objects are added, modified, or deleted.
Replicates shared folders between post offices.
Executes GroupWise client rules.

Understanding Message Delivery and Storage in the Post Office 471
novdocx (en) 11 December 2007
Processes requests from GroupWise Remote users.
35.6 Message Flow in the Post Office
To see how messages are delivered using client/server access mode, see “Message Delivery in the
Local Post Office” in GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure.
35.7 Cross-Platform Issues in the Post Office
GroupWise is designed to function in a variety of environments. The GroupWise Windows client
runs on the following platforms:
Windows 2000
Windows XP
Windows 2003
The GroupWise Cross-Platform client runs on the following platforms:
Linux
Macintosh
In addition, GroupWise users can access their mailboxes without using a GroupWise client through
the following applications:
GroupWise WebAccess (see “WebAccess” on page 853)
POP and IMAP clients such as Netscape* Mail, Eudora* Pro, Microsoft Outlook, and
Entourage*
MAPI clients such as Microsoft Mail and cc:Mail*
SOAP clients such as Evolution
Post offices can be located on the following platforms:
Novell®NetWare®
Windows Server
Linux
The GroupWise agents can run on the following platforms:
Novell NetWare
Windows Server
Linux
In general, GroupWise is most efficient if you match the agent platform with the network operating
system, so the POA and the post office should be on the same platform, and the client should be on a
compatible platform. Those with mixed networks might wonder what combinations are possible.
You have several alternatives.
Section 35.7.1, “Client/Post Office Platform Independence through Browser Technology,” on
page 472

472 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
Section 35.7.2, “Client/Post Office Platform Independence through Client/Server Mode,” on
page 472
Section 35.7.3, “POA/Post Office Platform Dependencies Because of Direct Access
Requirements,” on page 472
35.7.1 Client/Post Office Platform Independence through
Browser Technology
If your GroupWise users want to access their mailboxes through POP3, IMAP4, or SOAP clients, it
makes no difference what platform their post offices are located on. However, users are limited to
the client capabilities of their POP3, IMAP4, or SOAP clients.
If you install GroupWise WebAccess on a Web server, GroupWise users can still access their
mailboxes through their browsers and with more native GroupWise features available. See
“WebAccess” on page 853 for more information.
35.7.2 Client/Post Office Platform Independence through
Client/Server Mode
The GroupWise 6.5 and later Windows client and the Cross-Platform client require Client/Server
access mode. With this configuration, it makes no difference what platform users’ post offices are
located on. The GroupWise client accesses the post office by communicating with the POA using
TCP/IP, which is a platform-independent protocol.
35.7.3 POA/Post Office Platform Dependencies Because of
Direct Access Requirements
The POA must have direct access to the post office directory. Therefore, the POA must be able to
log in to the server where the post office is located and must be able to write to the databases and
directories located in the post office.
Although the recommended configuration is for the POA and the post office to be on the same
platform and preferably on the same server, some variation is possible. The table below summarizes
the various combinations of POA and post office platforms and indicates which combinations work
for direct access and which ones do not for GroupWise 7.x:
Table 35-1 POAs and Platforms Supported for Direct Access
1For these combinations, an NFS* connection is required, which is not a supported configuration
for the agents.
NetWare POA Linux POA Windows POA
Post Office on NetWare Yes Not supported1Yes
Post Office on Linux Not supported1Yes Yes
Post Office on Windows No2Yes Yes
Post Office on
Macintosh
No3No3No3

Understanding Message Delivery and Storage in the Post Office 473
novdocx (en) 11 December 2007
2The NetWare POA cannot service a post office on a Windows server because Windows does not
support the required cross-platform connection.
3Post offices cannot be created on Macintosh computers.

474 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007

Configuring the POA
36
novdocx (en) 11 December 2007
475
36
Configuring the POA
For detailed instructions about installing and starting the POA for the first time, see “Installing
GroupWise Agents” in the GroupWise 7 Installation Guide.
As your GroupWise®system grows and evolves, you might need to modify POA configuration to
meet the changing needs of the post office it services. The following topics help you configure the
POA:
Table 36-1 Configuring the POA
36.1 Performing Basic POA Configuration
POA configuration information is stored as properties of its POA object in eDirectoryTM. The
following topics help you modify the POA object in ConsoleOne®and change POA configuration to
meet changing system configurations:
Section 36.1.1, “Creating a POA Object in eDirectory,” on page 476
Section 36.1.2, “Configuring the POA in ConsoleOne,” on page 477
Section 36.1, “Performing
Basic POA Configuration,” on
page 475
Creating a POA Object in eDirectory
Configuring the POA in ConsoleOne
Changing the Link Protocol between the Post Office and the
Domain
Binding the POA to a Specific IP Address
Moving the POA to a Different Server
Adjusting the POA for a New Post Office Location
Adjusting the POA Logging Level and Other Log Settings
Section 36.2, “Configuring
User Access to the Post
Office,” on page 486
Using Client/Server Access to the Post Office
Simplifying Client/Server Access with a GroupWise Name Server
Supporting IMAP Clients
Supporting SOAP Clients
Supporting CAP Clients
Checking What GroupWise Clients Are in Use
Supporting Forced Mailbox Caching
Restricting Message Size between Post Offices
Section 36.3, “Configuring
Post Office Security,” on
page 496
Securing Client/Server Access through a Proxy Server
Securing the Post Office with SSL Connections to the POA
Providing LDAP Authentication for GroupWise Users
Enabling Intruder Detection
Configuring Trusted Application Support
Section 36.4, “Configuring
Post Office Maintenance,” on
page 507
Scheduling Database Maintenance
Scheduling Disk Space Management
Performing Nightly User Upkeep

476 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
Section 36.1.3, “Changing the Link Protocol between the Post Office and the Domain,” on
page 481
Section 36.1.4, “Binding the POA to a Specific IP Address,” on page 483
Section 36.1.5, “Moving the POA to a Different Server,” on page 484
Section 36.1.6, “Adjusting the POA for a New Post Office Location,” on page 484
Section 36.1.7, “Adjusting the POA Logging Level and Other Log Settings,” on page 485
36.1.1 Creating a POA Object in eDirectory
When you create a new post office, one POA object is automatically created for it. You can set up
additional POAs for an existing post office if message traffic in the post office is heavy. To
accomplish this, you must create additional POA objects as well.
To create a new POA object in Novell®eDirectory:
1In ConsoleOne, browse to and right-click the Post Office object for which you want to create a
new POA object, then click New > Object.
2Double-click GroupWise Agent to display the Create GroupWise Agent dialog box.
3Type a unique name for the new POA. The name can include as many as 8 characters. Do not
use any of the following invalid characters in the name:
You use this name with the /name startup switch when you start the new POA.
The Type field is automatically set to Post Office.
4Select Define Additional Properties.
5Click OK.
The POA object is automatically placed within the Post Office object.
6Review the information displayed for the first four fields on the Identification page to ensure
that you are creating the correct type of Agent object in the correct location.
ASCII characters 0-13 Comma ,
Asterisk * Double quote "
At sign @ Extended ASCII characters that are graphical or typographical symbols;
accented characters in the extended range can be used
Braces { } Parentheses ( )
Colon : Period .

Configuring the POA 477
novdocx (en) 11 December 2007
7In the Description field, type one or more lines of text describing the POA.
This description displays on the POA server console as the POA runs. When you run multiple
POAs on the same server, the description should uniquely identify each one. If multiple
administrators work at the server where the POA runs, the description could include a note
about who to contact before stopping the POA.
8In the Platform field, select the platform (NetWare, Linux, or Windows) where the POA will
run.
9Continue with Section 36.1.2, “Configuring the POA in ConsoleOne,” on page 477.
36.1.2 Configuring the POA in ConsoleOne
The advantage to configuring the POA in ConsoleOne, as opposed to using startup switches in a
POA startup file, is that the POA configuration settings are stored in eDirectory.
1In ConsoleOne, expand the eDirectory container where the Post Office object is located.
2Expand the Post Office object.
3Right-click the POA object, then click Properties.
The table below summarizes the POA configuration settings in the POA object properties pages and
how they correspond to POA startup switches (as described in Chapter 39, “Using POA Startup
Switches,” on page 565). The table also includes settings on the Post Office object that correspond
to POA startup switches.
Table 36-2 POA Configuration Settings
ConsoleOne Properties Pages
and Settings Corresponding Tasks and Startup Switches
POA Identification Page

478 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
Domain.PO
Distinguished Name
Name
Agent Type
Description
Platform
See Section 36.1.1, “Creating a POA Object in eDirectory,” on
page 476.
POA Agent Settings Page
Message File Processing See Section 38.2.2, “Configuring a Dedicated Message File Processing
POA,” on page 553.
See also /nomf, /nomfhigh, and /nomflow.
Message Handler Threads See Section 38.2.1, “Adjusting the Number of POA Threads for
Message File Processing,” on page 552.
See also /threads.
Enable TCP/IP (for C/S) See Section 36.2.1, “Using Client/Server Access to the Post Office,” on
page 486 and Section 38.1.3, “Configuring a Dedicated Client/Server
POA,” on page 550.
See also /notcpip.
TCP Handler Threads See Section 38.1.2, “Adjusting the Number of Connections for Client/
Server Processing,” on page 549.
See also /tcpthreads.
Max Physical Connections
Max Application Connections
See Section 38.1.2, “Adjusting the Number of Connections for Client/
Server Processing,” on page 549.
See also /maxphysconns and /maxappconns.
Enable Caching See /nocache.
CPU Utilization (NLM)
Delay Time (NLM)
See Section 38.5, “Optimizing CPU Utilization for the NetWare POA,” on
page 562.
See also /cpu and /sleep.
Max Thread Usage for Priming
and Moves
See Section 36.2.7, “Supporting Forced Mailbox Caching,” on
page 494.
See also /primingmax.
Enable IMAP
Max IMAP Threads
See Section 36.2.3, “Supporting IMAP Clients,” on page 490.
See also /imap and /imapmaxthreads.
Enable SOAP
Max SOAP Threads
See Section 36.2.4, “Supporting SOAP Clients,” on page 491.
See also /soap and /soapmaxthreads.
Enable SNMP
SNMP Community "Get"
String
See Section 37.6, “Using an SNMP Management Console,” on
page 540.
See also /nosnmp.
Disable Administration
Task Processing
See /noada.
HTTP User Name
HTTP Password
See Section 37.2.1, “Setting Up the POA Web Console,” on page 531.
See also /httpuser and /httppassword.
Network Address Page
ConsoleOne Properties Pages
and Settings Corresponding Tasks and Startup Switches

Configuring the POA 479
novdocx (en) 11 December 2007
TCP/IP Address
IPX/SPX Address
See Section 36.2.1, “Using Client/Server Access to the Post Office,” on
page 486 and Section , “Using TCP/IP Links between the Post Office
and the Domain,” on page 481.
See also /ip.
Proxy Server Address See Section 36.3.1, “Securing Client/Server Access through a Proxy
Server,” on page 496.
Bind Exclusively to
TCP/IP Address
See Section 36.1.4, “Binding the POA to a Specific IP Address,” on
page 483
See also /ip.
Message Transfer See Section , “Using TCP/IP Links between the Post Office and the
Domain,” on page 481.
See also /mtpinipaddr,/mtpinport, /mtpoutipaddr,/mtpoutport, /
mtpsendmax, and /mtpssl.
HTTP See Section 37.2.1, “Setting Up the POA Web Console,” on page 531.
See also /httpport and /httpssl.
Local Intranet Client/Server
Internet Proxy Client/Server
See Section 36.2.1, “Using Client/Server Access to the Post Office,” on
page 486 and Section , “Using TCP/IP Links between the Post Office
and the Domain,” on page 481.
See also /port, /internalclientssl, and /externalclientssl.
IMAP See Section 36.2.3, “Supporting IMAP Clients,” on page 490.
See also /imapport, /imapssl, and /imapsslport.
SOAP See Section 36.2.4, “Supporting SOAP Clients,” on page 491.
See also /soapport and /soapssl.
QuickFinder Page
Enable QuickFinder Indexing
Start QuickFinder Indexing
QuickFinder Interval
See Section 38.3.1, “Regulating Indexing,” on page 555 and
Section 38.3.2, “Configuring a Dedicated Indexing POA,” on page 556.
See also /qfbaseoffset,/qfbaseoffsetinminute, /qfinterval, /
qfintervalinminute, and /noqf.
Maintenance Page
Enable Auto DB Recovery See /norecover.
Maintenance Handler
Threads
See Section 38.4.1, “Adjusting the Number of POA Threads for
Database Maintenance,” on page 559.
See also /gwchkthreads and /nogwchk.
Perform User Upkeep
Start User Upkeep
Generate Address Book for
Remote
Start Address Book
Generation
See Section 36.4.3, “Performing Nightly User Upkeep,” on page 513.
See also /nuuoffset, /nonuu, /rdaboffset, and /nordab.
Disk Check Interval
Disk Check Delay
See Section 36.4.2, “Scheduling Disk Space Management,” on
page 510.
POA Log Settings Page
ConsoleOne Properties Pages
and Settings Corresponding Tasks and Startup Switches

480 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
After you install the POA software, you can further configure the POA using a startup file. See
Chapter 39, “Using POA Startup Switches,” on page 565 to survey the many ways the POA can be
configured.
Log File Path
Logging Level
Max Log File Age
Max Log Disk Space
See Section 37.3, “Using POA Log Files,” on page 538.
See also /log, /logdays, /logdiskoff, /loglevel, and /logmax.
POA Scheduled Events
Page
Disk Check Event See Section 36.4.2, “Scheduling Disk Space Management,” on
page 510.
Mailbox/Library Maintenance
Event
See Section 36.4.1, “Scheduling Database Maintenance,” on page 507.
POA SSL Settings Page
Certificate File
SSL Key File
Password
See Section 36.3.3, “Securing the Post Office with SSL Connections to
the POA,” on page 498.
See also /certfile, /keyfile, /keypassword.
Post Office Settings Page
Remote User Name
Remote Password
See /user and /password.
Post Office Client Access
Settings Page
Lock Out Older GroupWise
Clients
Minimum Client Release
Version
Minimum Client Release Date
See Section 36.2.6, “Checking What GroupWise Clients Are in Use,” on
page 492.
See also /gwclientreleasedate, /gwclientreleaseversion, and /
enforceclientversion.
Enable Intruder Detection
Incorrect Logins Allowed
Incorrect Login Reset Time
Lockout Reset Time
See Section 36.3.5, “Enabling Intruder Detection,” on page 506.
See also /intruderlockout, /incorrectloginattempts, /
attemptsresetinterval, and /lockoutresetinterval.
Post Office Security Page
LDAP Authentication See Section 36.3.4, “Providing LDAP Authentication for GroupWise
Users,” on page 501.
See also /ldapipaddr, /ldapport, /ldapuser, /ldappwd, /
ldapuserauthmethod, /ldapdisablepwdchg, /ldapssl, /ldapsslkey,/
ldaptimeout, and /noldapx.
See also /ldapippooln, /ldappoolresettime, /ldapportpooln, /ldapsslpooln,
and /ldapsslkeypooln
ConsoleOne Properties Pages
and Settings Corresponding Tasks and Startup Switches