User manual NOVELL GROUPWISE 7 ASYNC GATEWAY INSTALLATION AND ADMINISTRATION

[. . . ] Novell Confidential Manual (ENU) 21 December 2004 Novell GroupWise® Async Gateway 7 INSTALLATION AND ADMINISTRATION September 8, 2006 www. novell. com GUIDE Novell Confidential Manual (ENU) 21 December 2004 Legal Notices Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. [. . . ] The marketing domain has two different Async Gateways, the first with abc as the ID and the second with xyz as the ID. Your Async Gateway is installed in the Sales domain. Address Syntax (entered by user): margaret#xyz. com Search String: *#*. com Replacement String: sales. async:'%2':marketing. po1. %1 Results (explicit address): sales. async:'xyz':marketing. po1. margaret Enabling and Disabling Addressing Rules Previously created addressing rules can be enabled in any domain in your GroupWise system. When a rule applies, the process ends and no more rules are processed. To enable or disable addressing rules: 1 Browse to and right-click a Domain object, then click Properties. 2 Click GroupWise > Addressing Rules. 3 Select the Addressing Rules check box to enable the addressing rule in this domain. 4 Click Test to make sure it is being applied correctly. 5 From the Run Addressing Rules dialog box, enter an address as if you were a user sending a message. The Results field displays the resolved address that would be sent to the other GroupWise system. If the rule you selected is not being applied, check the other rules that precede it in the rules list. Address strings are evaluated against the rules in the order the rules are listed. Changing the Addressing Rule Order Addressing rules are applied in the order they are encountered. If a rule is applied to an address string, the search for a rule ends. You can, however, rearrange the order of the rules to create a different sequence. 1 In the list of rules for a domain, select a rule, then click the up-arrow or down-arrow to change its order in the list. Creating an External Domain Structure Another way to simplify addressing between two GroupWise sites with an async-to-async connection is to create an external GroupWise domain structure that duplicates the domain structure of the external GroupWise site. This method requires manual creation of an external Configuring the Async Gateway 61 Novell Confidential Manual (ENU) 21 December 2004 domain in your system for every primary or secondary domain in the external system to ensure that your local GroupWise system has the message routing information it needs to send messages to external GroupWise users. When you complete the external domain structure, it looks like the local domain structure of the external system, but you have no administrative rights over the domains at the external site. The GroupWise administrator at the other site also needs to construct the external domain structure to represent yours, but that administrator has no administrative rights over the domains at your site. When you create the external domains locally, you must also link them to the local domain where the Async Gateway resides. The links provide further information about the domains at the other site and how they communicate through the gateway. To create links in both systems, you and the system administrator at the other site must contact each other to obtain two important pieces of information: The other system's domain structure; that is, the names of the domains The name of the domain on the other system where the gateway is located With this information, both system administrators can create the links needed to accommodate communication through the Async Gateway. "Basic Addressing Syntax" on page 62 "Simplifying Address Syntax to Domain. Post_Office. UserID" on page 62 "Simplifying Address Syntax to Post_Office. UserID" on page 65 "Simplifying Address Syntax to UserID" on page 66 Basic Addressing Syntax Each of the elements in the domain. post_office. user address syntax are required by GroupWise to send to any other GroupWise destination, whether or not the user enters them on the address line. How GroupWise Validates this Syntax The GroupWise client recognizes the domain name (the first element in the syntax) and verifies it is a legitimate GroupWise object, an external domain linked to the local system through a gateway link. The presence of an external domain name in the syntax alerts the GroupWise MTA to identify the gateway link and to send the message to the appropriate gateway (in this case, Async). [. . . ] The MTA output queue is the input queue for the POA in the sender's post office. Stage 21: POA in Sender's Post Office The POA in the sender's post office updates the sender's message database (msg 0-24. db file) with the Delivered status information (and possibly Opened if the recipient has opened the message). Stage 22: Sender When the sender checks his or her Out Box in the GroupWise client, the message displays a status of Delivered for each recipient (and possibly Opened if the recipient has opened the message). 136 GroupWise 7 Async Gateway Installation and Administration Guide Novell Confidential Manual (ENU) 21 December 2004 Message Flow from the GroupWise Windows Client in Remote Mode to the Async Gateway 1 15 2 WPCSIN 0-7 ROFDATA msg. db user. db wprof. db WPGWSEND WPGWRECV WPCSOUT OFS 0-7 3 12 14 13 4 WPCSIN 0-7 WPCSOUT ADS 0-7 WPGATE ASYXXX GWOUT CONNECTION ID CMP 1-3 GWIN CONNECTION ID CMP WPCSIN 0-7 7 WPCSOUT GATEWAY ID 9 0-7 11 10 5 6 WPCSIN 0-7 OFMSG msg024. db OFUSER userxxx. db OFFILES FD0-7F WPCSOUT ADS 0-7 OFS 0-7 8 POA MTA Stage 1: Remote User The GroupWise user, who is not currently connected to the network, sends a message to another GroupWise user or creates a request for items from the Master Mailbox. Stage 2: Remote User's GroupWise Client When the Remote user sends a message to another GroupWise user, the GroupWise client performs the following actions: Adds the message to the Remote message database (msg. db file) on the user's remote computer. Creates a pointer in the Remote user database (user. db file) so the message appears in the Out Box on the user's remote computer. Places attachments larger than 2 KB in the rofdata directory and creates pointers from the message to its attachments on the user's remote computer. (For database efficiency, messages and recipient lists larger than 2 KB are also handled as attachments. ) Creates a copy of the message in the priority 1 subdirectory of the Remote input queue on the user's remote computer. [. . . ]