Resolution
fact
Directory and Resource Administrator 7.0
fact
Directory and Resource Administrator 7.0 SP1
symptom
The 'Delivery Restriction' property of the template account is being modified when cloning the Exchange 5.5 mailbox.
symptom
When cloning an Exchange 5.5 Mailbox, the template account's mailbox is modified to include the newly cloned account to the ?Delivery Restrictions? on the template account.
symptom
When cloning a template account with an Exchange 5.5 mailbox, which is configured to only receive incoming mail from itself on the Delivery Restrictions tab, the template account's mailbox is modified after the cloning process, to include the newly cloned user account to the Delivery Restrictions.
symptom
The newly cloned mailbox is created correctly, however the template account instead of only displaying itself, also displays the newly cloned account to receive mail from on the Delivery Restrictions tab.
cause
This problem occurs because the property in question is a back linked property, which Directory and Resource Administrator (DRA) clones during the cloning process. For example, if you are updating mailbox Bob to say that they can accept mail from Sue, this sets an auth-orig-bl property on Sue specifying that she can send mail to Bob, as well as an auth-orig property on Bob, which says that Sue can send Bob mail. If DRA were to copy Sue, the new mailbox would be able to send mail to Bob since we copy the auth-orig-bl.
fix
Directory and Resource Administrator 7.0
fact
Directory and Resource Administrator 7.0 SP1
symptom
The 'Delivery Restriction' property of the template account is being modified when cloning the Exchange 5.5 mailbox.
symptom
When cloning an Exchange 5.5 Mailbox, the template account's mailbox is modified to include the newly cloned account to the ?Delivery Restrictions? on the template account.
symptom
When cloning a template account with an Exchange 5.5 mailbox, which is configured to only receive incoming mail from itself on the Delivery Restrictions tab, the template account's mailbox is modified after the cloning process, to include the newly cloned user account to the Delivery Restrictions.
symptom
The newly cloned mailbox is created correctly, however the template account instead of only displaying itself, also displays the newly cloned account to receive mail from on the Delivery Restrictions tab.
cause
This problem occurs because the property in question is a back linked property, which Directory and Resource Administrator (DRA) clones during the cloning process. For example, if you are updating mailbox Bob to say that they can accept mail from Sue, this sets an auth-orig-bl property on Sue specifying that she can send mail to Bob, as well as an auth-orig property on Bob, which says that Sue can send Bob mail. If DRA were to copy Sue, the new mailbox would be able to send mail to Bob since we copy the auth-orig-bl.
fix
This problem is resolved in DRA 7.5 and later. In order to resolve the above described problem, upgrade to the latest version of DRA.
The following workaround can also be implemented:
Modify the template account's mailbox property so that the template account is not configured to accept incoming mail from itself on the Delivery Restrictions tab. Instead, configure it to accept incoming mail from another template account only. By doing so you still have the template account configured to not receive mail from other users and if the Delivery Restrictions is not set to itself, Directory and Resource Administrator will not clone this property.
Additional Information
Formerly known as NETIQKB38532