1. Manuals
  2. Brands
  3. Novell Manuals
  4. Software
  5. GROUPWISE 7 - POST OFFICES
  6. Manual

Novell GROUPWISE 7 - POST OFFICES Manual

Hide thumbs Also See for GROUPWISE 7 - POST OFFICES:
Table of Contents

Advertisement

Quick Links

Download this manual
Post Offices
I I I
Chapter 11, "Creating a New Post Office," on page 155
Chapter 12, "Managing Post Offices," on page 175
III
Post Offices
153

Advertisement

Table of Contents
loading

Related Manuals for Novell GROUPWISE 7 - POST OFFICES

Summary of Contents for Novell GROUPWISE 7 - POST OFFICES

  • Page 1 Post Offices I I I Chapter 11, “Creating a New Post Office,” on page 155 Chapter 12, “Managing Post Offices,” on page 175 Post Offices...
  • Page 2 154 GroupWise 7 Administration Guide...

  • Page 3: Creating A New Post Office

    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 155 Section 11.2, “Planning a New Post Office,” on page 156 Section 11.3, “Setting Up the New Post Office,”...
  • Page 4 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 7 Troubleshooting 3: Message Flow and Directory Structure.

  • Page 5: Selecting The Domain That The Post Office Will Belong To

    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 eDirectory tree. If you have just one domain, the new post office will belong to it.

  • Page 6: Determining The Context For The Post Office Object

    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.
  • Page 7 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. A GroupWise System Following the Departmental Organization of the Company Figure 11-3 GroupWise Objects Are Grouped with Servers...

  • Page 8: Choosing The Post Office Name

    GroupWise Objects Located in Their Own Organizational Unit Figure 11-5 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.

  • Page 9: Deciding Where To Install The Agent Software

    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.
  • Page 10 complete POA installation instructions and system requirements, see “Installing GroupWise Agents” in the GroupWise 7 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,”...
  • Page 11 ® NetWare: If the NetWare POA needs direct network access to another NetWare server where the post office is located, you must add the switch or the /user /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.

  • Page 12: Deciding How To Link The New Post Office

    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).

  • Page 13: Selecting The Post Office Language

    WORKSHEET Under Item 14: Link to Domain, indicate the type of link you plan to set up between the new post office and its domain. 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.

  • Page 14: Selecting A Post Office Security Level

    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.
  • Page 15 11.3 Setting Up the New Post Office You should have already reviewed Section 11.2, “Planning a New Post Office,” on page 156 filled out Section 11.5, “Post Office Worksheet,” on page 171. Complete the following tasks to create a new post office. Section 11.3.1, “Creating the New Post Office,”...
  • Page 16 5 Follow 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. 6 Fill in the Description field (worksheet item 7 Click GroupWise >...
  • Page 17 8 Provide the network type for the post office location (worksheet item 10). 9 Select the software distribution directory for the post office (worksheet item 10 If 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...

  • Page 18: Configuring The Poa For The New Post Office

    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. 1 In ConsoleOne, double-click the new Post Office object.

  • Page 19: Setting Up User Access To The New Post Office

    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 Cross-Platform 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.
  • Page 20 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 158. 2) Post Office Name Specify a name for the new post office.
  • Page 21 Item Explanation 11) Post Office Security Mark the security level for the post offices. For high security, mark the type Level: of authentication you plan to use. For more information, see Section 11.2.11, “Selecting a Post Office Security Level,” on page 166.
  • Page 22 174 GroupWise 7 Administration Guide...

  • Page 23: Managing Post Offices

    Managing Post Offices ® As your GroupWise system grows and evolves, you might need to perform the following maintenance activities on post offices: Section 12.1, “Connecting to the Domain That Owns a Post Office,” on page 175 Section 12.2, “Editing Post Office Properties,” on page 176 Section 12.3, “Managing Disk Space Usage in the Post Office,”...

  • Page 24: Editing Post Office Properties

    The domain marked with the red underscore is the primary domain. For a discussion of cross-platform connection issues, see Section 4.1, “Select Domain,” on page 12.2 Editing Post Office Properties After creating a post office, you can change some post office properties. Other post office properties cannot be changed.
  • Page 25 These post office settings are discussed in the following sections: Section 11.2.10, “Selecting a Software Distribution Directory,” on page 165 Section 11.3.4, “Setting Up User Access to the New Post Office,” on page 171 4 Click GroupWise > Client Access Settings to display the Client Access Settings page. The client access settings are discussed in the following sections: Section 12.5, “Tracking and Restricting Client Access to the Post Office,”...
  • Page 26 ® All users in the post office are listed, no matter where their Novell eDirectory objects are located in the tree. Here you can add, delete, and move users in the post office. See “Users” on page 201. 6 Click GroupWise > Resources to display the Resources page.
  • Page 27 All distribution lists in the post office are listed, no matter where their eDirectory objects are located in the tree. This is a convenient place to delete distribution lists from the post office. “Distribution Lists, Groups, and Organizational Roles” on page 261.
  • Page 28 You need to set up aliases for a post office only if you are using GroupWise gateways. For a list of gateways, see the GroupWise Gateways Documentation Web site (http://www.novell.com/ documentation/gwgateways). 10 Click GroupWise > Internet Addressing to display the Internet Addressing page.
  • Page 29 For instructions on setting the security level for the post office, see Section 11.2.11, “Selecting a Post Office Security Level,” on page 166. 12 Click GroupWise > Default WebAccess to display the Default WebAccess page. Use this page to designate the default WebAccess gateway for the post office. See “WebAccess”...
  • Page 30 12.3 Managing Disk Space Usage in the Post Office Many users are prone to save every message and attachment they ever receive. You can moderate this behavior by implementing disk space management: Section 12.3.1, “Preparing to Implement Disk Space Management,” on page 182 Section 12.3.2, “Setting Mailbox Size Limits,”...

  • Page 31: Setting Mailbox Size Limits

    4 In the Action field, select Analyze/Fix Databases. 5 As options to the action, select Contents, Fix Problems, and Reset User Disk Space Totals. Make sure all other options are deselected. 6 On the Databases tab, select User. Make sure all other types of databases are deselected. 7 Click Run, then click OK to acknowledge that the Mailbox/Library Maintenance task has been sent to the POA.
  • Page 32 4 Select User Limits. 5 Specify the maximum number of megabytes allowed for each user’s mailbox. Unless disk space is extremely limited, 200 MB is a comfortable mailbox size to enforce. The maximum size limit that you can set for mailboxes is 4 GB. However, GroupWise databases themselves have no inherent maximum size limit.

  • Page 33: Enforcing Mailbox Size Limits

    12.3.3 Enforcing Mailbox Size Limits If existing GroupWise users are having difficulty fitting their mailboxes into the established mailbox size limits, you can assist them by reducing their mailboxes for them. Users should be warned before this action is taken. 1 In ConsoleOne, select a Post Office object.
  • Page 34 plain text instead, in order to decrease the size of the message so that it falls within the message size restriction. There are four levels at which you can restrict message size: “Within the Post Office” on page 186 “Between Post Offices” on page 187 “Between Domains”...

  • Page 35: Preventing The Post Office From Running Out Of Disk Space

    4 Select User Limits. 5 Specify in kilobytes the largest message that users can send. 6 Click OK, then click Close to save the maximum message size setting. Between Post Offices You can configure the POA to restrict the size of messages that it allows to pass outside the local post office.
  • Page 36 the POA to stop processing messages, so that disk space usage in the post office cannot increase until the disk space problem is resolved. 1 In ConsoleOne, double-click a Post Office object, right-click its POA object, then click Properties. 2 Click GroupWise > Agent Settings, then adjust the settings in the Disk Check Interval and Disk Check Delay fields as described in Section 36.4.2, “Scheduling Disk Space Management,”...
  • Page 37 7 Click Create to define your own disk check actions, then give the new action a unique name. 8 Configure the actions for the POA to take in order to relieve the low disk space condition. Use the Results or Notification tab if you want to receive notification about the POA’s response to the low disk space condition.

  • Page 38: An Alternative To Disk Space Management In The Post Office

    13 Select the new disk space management event. 14 Click OK to close the Scheduled Events page. ConsoleOne then notifies the POA to restart so the new disk space management event can be put into effect. 12.3.6 An Alternative to Disk Space Management in the Post Office If you want to place more responsibility for disk space management onto GroupWise client users, you can require that they run the client in Caching mode, where all messages can be stored on user...

  • Page 39: Auditing Mailbox License Usage In The Post Office

    Caching mailboxes. Make sure that users understand their responsibilities to back up their Caching mailboxes, as described in: “Backing Up Your Mailbox” in “Managing Your Mailbox” in the GroupWise 7 Windows Client User Guide “Backing Up Your Mailbox” in “Managing Your Mailbox”...
  • Page 40 The Microsoft Outlook Plug-In for GroupWise 5.5 A third-party plug-in to the GroupWise client API A mobile device with mailbox synchronization capabilities provided by GroupWise Mobile Server (GMS) or Research in Motion* (RIM*) BlackBerry* Enterprise Server* (BES). A mailbox requires a limited client license only (and is marked as a limited client license mailbox) if access to it has been limited to the following: The GroupWise WebAccess client A GroupWise Windows or WebAccess client via the Proxy feature...

  • Page 41: Tracking And Restricting Client Access To The Post Office

    4 In the Show Accounts without Activity for nn Days field, select the number of days you want to use for the inactivity report. Using the default setting (60 days) causes the Mailbox/Library Maintenance program to indicate the mailboxes that have not had any activity within the last 60 days. 5 If you want write the report to a log file, click the Logging tab, then specify a name for the log file.
  • Page 42 IMPORTANT: Because the POA provides the version tracking and enforces the client lockout, this functionality applies only to GroupWise clients that are accessing the post office in client/server mode (not direct access mode). To help you better monitor and track which versions of the GroupWise client are being used to access the post office, you can specify a preferred GroupWise client version for the post office.

  • Page 43: Refreshing The Client View Files In The Post Office

    or date specified in the Release Version and Release Date fields. For example, if you entered 6.0.0 in the Release Version field and April 6, 2001 12:00 AM in the Release Date field and selected this option for both, any GroupWise client that is older than version 6.0 or is dated before April 6, 2001 12:00 AM is not allowed access to the post office.

  • Page 44: Moving A Post Office

    can continue to access the post office; after they exit, they cannot access the post office again until the post office is enabled. A post office must be disabled if you are rebuilding the post office database (wphost.db). You might also want to disable a post office when you are doing a complete GroupWise system backup.

  • Page 45: Deleting A Post Office

    1 Make sure all users are out of the post office, then disable logins to the post office. See Section 12.7, “Disabling a Post Office,” on page 195. 2 Back up the post office. See Chapter 31, “Backing Up GroupWise Databases,” on page 407.
  • Page 46 2 Click GroupWise > Resources, then delete any resources that still belong to the post office. See Section 16.5, “Deleting a Resource,” on page 256. You must delete resources before users, because users who own resources cannot be deleted without assigning a new owner in the same post office. 3 Click GroupWise >...
  • Page 47 “Uninstalling the Windows GroupWise Agents” 12.10 Changing POA Configuration to Meet Post Office Needs Because the POA delivers messages to mailboxes, responds in real time to client/server users, and maintains all databases located in the post office, its functioning affects the post office and all users who belong to the post office.

This manual is also suitable for:

Groupwise 7

Table of Contents