6.8 Facilitating Addressing through GroupWise Gateways

Current GroupWise Gateways, such as the GroupWise Gateway 2.0 for Microsoft* Exchange and the GroupWise Gateway 3.0 for Lotus Notes*, provide convenient addressing features for users on both sides of the gateway. Earlier GroupWise gateways made use of addressing rules to simplify addressing through the gateway. Setting up addressing rules is not necessary for current GroupWise gateways.

Addressing rules let you search for text in an address and replace it with other text. Addressing rules are created at the system level and enabled by domain. Gateway-specific instructions are available on the GroupWise Gateways documentation page. The following sections provide some general instructions for setting up addressing rules:

6.8.1 Creating an Addressing Rule

  1. In ConsoleOne, click Tools > GroupWise System Operations > Addressing Rules.

    Define Addressing Rules dialog box
  2. Click New to display the New Addressing Rule dialog box.

    New Addressing Rule dialog box
  3. Fill in the following fields:

    Description: Specify a short description for the rule. The description is what appears when the rule is listed in the Addressing Rules dialog box.

    Name: Specify the name you want to use for the rule.

    Search String: Specify the text string that determines which addresses the rule is applied to. You can use an asterisk as a wildcard to represent one or more characters. For example, if you want the rule to apply to all addresses with JSmith as the userID, specify jsmith.*.* (the first asterisk represents the post office and the second represents the domain).

    Replace With: Specify the replacement text. You can use variables (%1, %2, and so forth) to reference the wildcard text used in the search string. For example, if you use two wildcards in the search string, you could use two variables (%1 and %2) to insert the matched wildcard text into the replacement string. %1 (replace string 1) replaces the first wildcard in the search string, %2 replaces the second wildcard, and so on. The replacement variables must be placed in the string according to the order required for the explicit address, not according to their numerical order (for example, %2 could come before %1).

    Using the jsmith.*.* example, assume that you want to replace jsmith with jjones. You would specify jjones.%1.%2. The resulting addressing would include the same post office and domain but a different userID.

  4. If desired, you can test the rule on an address. To do so, specify an address in the Test Address dialog box (the address does not have to be real) > click Test to see the results.

  5. Click OK to add the rule to the list.

    The rule is automatically enabled, which means that it is available for use. To apply it to a domain, however, you need to enable it in the domain. For instructions, see Section 6.8.2, Enabling an Addressing Rule.

  6. If necessary, select the rule, then use the up-arrow and down-arrow to move the rule to the position in which you want it executed.

    Addressing rules are executed in the order they are listed. When an addressing rule is applied to an address, no further addressing rules are applied.

  7. When you are finished creating rules, click OK to close the Define Addressing Rules dialog box.

6.8.2 Enabling an Addressing Rule

After you create an addressing rule, you need to enable it in the domains where you want it applied.

  1. In ConsoleOne, right-click the Domain object, then click Properties.

    Domain object property page
  2. Click GroupWise > Addressing Rules.

    The list displays all addressing rules that have been made available in the system. However, an addressing rule does not apply to the domain until you enable it.

    Domain object property page with the Addressing Rules list displayed
  3. Click the check box in front of an addressing rule to enable it.

  4. When you are finished enabling rules, click OK to save your changes.