Restricting Message Size Between Post Offices - Novell GROUPWISE 8 - ADMINISTRATION Administration Manual

3 Set Max Thread Usage for Priming and Moves as needed.
By default, the POA allocates 30% of its client/server handler threads for priming mailboxes
for users who are using Caching mode for the first time. By default, the POA starts 10 client/
server handler threads, so in a default configuration, three threads are available for priming.
You might want to specify 60 or 80 so that 60% to 80% of POA threads are used for priming
mailboxes. You might also want to increase the number of client/server handler threads the
POA can start in order to handle the temporarily heavy load while users are priming their
mailboxes. See Section 38.1.2, "Adjusting the Number of Connections for Client/Server
Processing," on page
4 Click OK to save the new setting.
ConsoleOne then notifies the POA to restart so the new setting can be put into effect.
Corresponding Startup Switches You can also use the
file to configure the POA to handle multiple requests to prime mailboxes.
POA Web Console You can change the POA's ability to respond to caching requests for the current
POA session on the Configuration
Thread Usage for Priming and Live Moves. To increase the number of client/server threads, click
Client/Server Processing Threads under the Performance Settings heading.

36.2.7 Restricting Message Size between Post Offices

You can configure the POA to restrict the size of messages that users are permitted to send outside
the post office.
1 In ConsoleOne, click Tools > GroupWise Utilities > Link Configuration.
2 In the drop-down list, select the domain where the post office resides, then click Post Office
Links.
3 Double-click the post office where you want to restrict message size.
563.
page. Under the Client/Server Settings heading, click Max
/primingmax switch in the POA startup
Configuring the POA 507