Domino aliases cause problems in multi-domain scenarios

book

Article ID: 100040310

calendar_today

Updated On:

Description

Description

When using CloudLink to sync Domino properties, there are no options as to which properties are synced. We create aliases (alternate names in the [EmailAcct] table) based on several properties we find, like common name.  In particular, from the primary SMTP email address, we appear to take local-part (the portion left of the @), and create an alias from this.

This causes problems if a customer is archiving across multiple domains, as that alias cannot be assumed to be unique. 

Consider a company archiving from a.domain.com and b.domain.com.  They have an archiving user, bob@a.domain.com.  CloudLink assigns the local-part, "bob", as an alias for this user.  Now mail arrives for a different user (not in Arctera Unified Platform), bob@b.domain.com.  Since we can't resolve the SMTP address, we try matching various aliases, and since the local-part matches the existing alias bob, we assign the mail to user bob@a.domain.com, rather than assigning it to Unassigned Legacy.

Arctera Corporation has acknowledged that the above-mentioned issue is present in the version(s) of the product(s) referenced in this article.

 

This issue is currently under investigation by Arctera. Pending the outcome of the investigation, this issue may be resolved by way of a cumulative hotfix or service pack in the current or future versions of the software. However, this particular issue is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Arctera Sales representative or the Arctera Sales group to discuss these concerns. For information on how to contact Arctera Sales, please see http://arctera.com.

Issue/Introduction

Domino aliases cause problems in multi-domain scenarios

Additional Information

JIRA: CFT-561 JIRA: CFT-561