Chat now with support
Chat with Support

Coexistence Manager for GroupWise 1.7.1 - User Guide

About the Coexistence Manager for GroupWise documentation suite Introduction Coexistence Manager for GroupWise Directory Connector
Directory Connector overview Installation and configuration DC Management Console Connector Creation Wizard Connector Advanced Settings Running and stopping the Directory Connector service
Coexistence Manager for GroupWise Mail Connector Coexistence Manager for GroupWise Free/Busy Connector The Log Viewer Appendix A: Known limitations Appendix B: Troubleshooting Appendix C:Configuring Coexistence Manager for GroupWise logging

Management Console screen: Mail Connector | Advanced Message Settings

| Advanced Message Settings

This screen offers performance-tuning features.

Send Keep-Alives During Processing: Coexistence Manager for GroupWise’s Mail Connector is configured to send an SMTP NOOP every 30 seconds, to keep the server from timing out when processing larger messages. You can disable and enable this feature by the checkbox here, and/or set the time interval to some other value:

Send Keep-Alive Message Every __ Seconds: Number of seconds Coexistence Manager for GroupWise will wait before sending the first NOOP and each successive NOOP (if Send Keep-Alives is enabled). Default=30.
Response Message Mail From Address: The email address that will appear as the sender of Coexistence Manager for GroupWise’s NOOP messages.

Performance Tuning:

Maximum Message Process Time: Maximum time, in minutes, that Coexistence Manager for GroupWise will spend processing a message before reporting a failure. Default=4 minutes.
Message Connection Inactivity Time: Maximum time, in minutes, that Coexistence Manager for GroupWise will wait for a data reply before giving up and terminating the connection. Default=30 seconds.
Maximum Memory Usage Per Message: If a message is larger than the value (in kilobytes) you specify here, the remaining data will overflow into a temp file, residing in the Temporary File Directory specified in the accompanying text box. Default=32 kilobytes.

Management Console screen: Mail Connector | Address Rewriting

| Address Rewriting

These settings specify how email addresses should be changed in messages processed by Coexistence Manager for GroupWise.

Rewrite GroupWise Addresses (checkbox, only for coexistence with GroupWise 7): Determines whether the Mail Connector will rewrite addresses sent from GroupWise 7, to replace them with reply-able SMTP format addresses.

IMPORTANT: This rewrite feature should be used only when coexisting with a GroupWise 7 environment. The GroupWise configuration required to support coexistence with version 7 produces the source addresses that require translating. This feature will not be used with GroupWise 8 servers.

To enable this rewrite feature, mark the checkbox and then enter values for:

Internet Domains: The domain name that Coexistence Manager for GroupWise should use when rewriting addresses to SMTP form (e.g., contoso.com). Coexistence Manager for GroupWise will parse the GroupWise source address (e.g., jsmith.gwpo.gwdomain@osh- kosh.contoso.com) to obtain the user name portion of the address (preceding the "@" symbol) and, if the SMTP domain matches this specified rewrite domain, will form the new SMTP address by appending this domain to the user name. For the above examples, Coexistence Manager for GroupWise would rewrite the source address as jsmith@contoso.com. Note that you may enter multiple domain names here, separated by commas.
GroupWise Domains: The names of GroupWise domains in GroupWise addresses to be rewritten by this feature. For example, a GroupWise address user29.gwpo.gwdomain@contoso.com or user29.gwpo.gwdomain@oshkosh.contoso.com, will be rewritten if gwdomain is specified as a GroupWise Domain. Note that you may enter multiple domain names here, separated by commas.

SMTP Address Rewriting (available only if Rewrite GroupWise Addresses above is enabled): These features let you tell Coexistence Manager for GroupWise to automatically remove undesirable portions of the left-hand sides of email addresses as they are emitted from some GroupWise environments. This feature can be applied independently (by separate checkboxes) to either, neither or both of MAIL FROM (Sender) and/or RCPT TO (Recipients) commands. Note that the Rewrite GroupWise Addresses feature above applies only to MIME (internal message content) and not to addresses used in SMTP transmissions unless either or both of these SMTP options are selected.

Management Console screen: Mail Connector | Message Content Limits

| Message Content Limits

These limits let Coexistence Manager for GroupWise enforce certain compatibilities between the GroupWise and Exchange environments.

Maximum Subject Line Length: The longest message Subject line Coexistence Manager for GroupWise will permit, in number of characters. If a Subject line exceeds this length, the Mail Connector will truncate the line and insert ellipsis (...). The default of 1975 is the maximum allowed by a local Microsoft Exchange, and should be plenty in most local-Exchange environments. But if coexisting with Office 365, this limit should be set much lower, to 255.

Maximum Number of MIME Parts: The maximum number of MIME bodies Coexistence Manager for GroupWise will allow in multipart messages. Coexistence Manager for GroupWise will bounce a message with more than this number of MIME bodies. The default limit of 5000 is very high. If coexisting with Office 365, the limit should be lowered to 250.

Management Console screen: Mail Connector | Notification Messages

| Notification Messages

You can customize the notices Coexistence Manager for GroupWise inserts to notify recipients of conversion issues, which may include suggestions to compensate for known limitations. For example, a message may suggest that the recipient manually update his/her calendar, or verify that a particular appointment has been added.

NOTE: Remember that any new information or changes entered in this screen are saved to the Messages File only when you save the configuration file—by selecting Save Configuration File on the File menu. If you exit the Management Console without saving the configuration, any new information or changes entered in this screen (or any other Management Console screen) will be lost.

All of the notification message information is saved in a separate .xml file, which you must specify as the:

Messages File: The path (including filename) of the .xml file containing the Coexistence Manager for GroupWise notification messages. The other values on this screen are saved in the file you specify, and the Coexistence Manager for GroupWise Mail Connector draws your preferred message from this file.
To view or customize notification messages:

Repeat this process for as many message types as you want to customize.

1
In the folder tree to the left of the Description, Plain Text Message and HTML Message fields, select the message you want to view or customize. When you select the message in the folder tree, the fields show the associated current values for:
Description (uneditable, FYI only): A name and/or brief description of the circumstances that would cause this message to be sent.
Plain Text Message: The message, in plain-text format, Coexistence Manager for GroupWise should insert into plain-text emails to notify recipients.
HTML Message: The message, in HTML format, Coexistence Manager for GroupWise should insert into HTML emails to notify recipients. Note: This field appears grayed-out and uneditable for NDR-type messages and some other message types.
2
To customize either or both the Plain Text Message and HTML Message fields: Click your cursor into the text box, and use familiar text-editing features to add, delete and/or edit the text box contents.
While you are editing, two buttons at the bottom of the screen let you:
Insert Variable...: Calls a pop-up list of defined variables (for the date, time, message sender, etc.) from which you may select one to insert inline into the text of a Plain Text Message or HTML Message (see above). A message may, for example, cite the proposed date and time of a meeting invitation, which will vary with every instance of the message.
Use Default Message: Restores the default message values into the Plain Text and HTML Message fields above. Any custom message data that may already appear in the fields will be lost.
Related Documents