Move Mailbox Via C++ get BERR_PROXY_NOT_UNIQUE

[Ken]

Hello. I am getting what appears to be a "replication" issue error when I try to move a mailbox via DAPI/MAPI calls.
Here's my setup
2 Sites and the e-mail generators do not add any site specific info to the new e-mails. So, KRB@company.com created on Site1 is SMTP:KRB@company.com and created on Site2, it would be exactly the same.

I export the mailstores, delete the mailbox from Site1 via DAPI calls. Then within the same function try to create the mailbox on Site2 via DAPI. This fails with BERR_PROXY_NOT_UNIQUE because it still thinks that KRB@company.com is a valid e-mail address since replication couldn't have happened in this short time frame. Is there any way I can "tweak" the address book so it doesn't think it is a duplicate? This will happen with EVERY user in this configuration.

I "could" detect this error, and modify the SMTP(or X400/MSMail) e-mail address to make it unique, but that's not what is most convenient to the user since they don't want them to change. If the e-mail address generators put specific "site" information in the e-mail KRB@Site1.company.com, I translate this to the destination site (KRB@Site2.company.com) during the move, so there is no duplicate problem in this case.

Any info would be appreciated

[Craig Hoeferkamp]

If the mailbox does not need to have the same attributes or naming conventions, make the setting for alias generation differently on each server that will change the directory name and allow the creation to occur. This is the way we do it, until MS opens up the API for forced replication.

C


------------
Ken at 3/21/00 10:12:06 AM


Hello. I am getting what appears to be a "replication" issue error when I try to move a mailbox via DAPI/MAPI calls.
Here's my setup
2 Sites and the e-mail generators do not add any site specific info to the new e-mails. So, KRB@company.com created on Site1 is SMTP:KRB@company.com and created on Site2, it would be exactly the same.

I export the mailstores, delete the mailbox from Site1 via DAPI calls. Then within the same function try to create the mailbox on Site2 via DAPI. This fails with BERR_PROXY_NOT_UNIQUE because it still thinks that KRB@company.com is a valid e-mail address since replication couldn't have happened in this short time frame. Is there any way I can "tweak" the address book so it doesn't think it is a duplicate? This will happen with EVERY user in this configuration.

I "could" detect this error, and modify the SMTP(or X400/MSMail) e-mail address to make it unique, but that's not what is most convenient to the user since they don't want them to change. If the e-mail address generators put specific "site" information in the e-mail KRB@Site1.company.com, I translate this to the destination site (KRB@Site2.company.com) during the move, so there is no duplicate problem in this case.

Any info would be appreciated