Interesting post. I'm wondering, have you noticed this bug regarding the uniqueness check and contacts: <br> <br>* Create a mail-enabled user <br>* Create a mail-enabled contact with an external address. <br>* (wait for the RUS to process) <br>* Open the contact and change the 'mail' value from the 'general' tab to equal the primary address of the user in the previous step. <br>* OK out of the property sheet. <br> <br>DSA will alert you of the conflict, but if you open up the object again (or view it from LDAP), the conflicting change has indeed been written.

How would you explain this: <br>If I do an LDIFDE import with these fields, when I see user properties all the proxy addresses are set as default and appear bold. <br>Should I use &quot;SMTP&quot; in lower case? I haven't tried that yet. <br> <br>dn: cn=dlist01,ou=adc_import,dc=company,dc=com <br>changetype: add <br>objectClass: group <br>mailNickName: dlist01 <br>displayName: DL Fica 01 <br>proxyAddresses: SMTP:dlist01@company.com <br>proxyAddresses: SMTP:dlistsec@company.com <br>proxyAddresses: SMTP:dlistter@company.com <br>proxyAddresses: groupType: 8 <br>instanceType: 4

I've seen situations where changing the email address on the general tab causes the ADC to create custome recipients. Is this due to the proxy-sync scenario?

Is there a reason why the Exchange General tab is not exposed in ADModify.Net? If it was then we would be able to modify the targetAddress attribute for contacts and mail-enabled users. I think this would be a great addition to the tool.

After reading this article it seems that you can change the “targetAddress” from 'Users and Computers' snap-in to any email address (like a hotmail account) but you can only select an AD object (at least with Exch2k) <br>I thought I could put any address in that field in order to provide an easy “.forward” feature to the users through a web page. If I put a foreign address (like @Hotmail) through ADSIEdit or any other tool in the “targetAddress” field, the forwarding doesn’t work. <br>I have to do it with targetAddress -&gt;Contact AD object with foreign address. That’s the way MS says in some KB article, but it’s more troublesome and involves an administrative action. <br>Did I did anything wrong when I tried using “targetAddress” in this way? Is there any easier way to allow the users to set up their own “forwards”? <br>Thank You <br> <br>J Crespo

Can you think of any reason why moving a mailbox enabled user would cause the following:

Existing Primary SMTP Address demoted to secondary and new Primary SMTP generated (appended with number to maker unique) ie

before move:

Primary SMTP: Joe.Bloggs@MyDomain.com
Secondary smtp: none

After move:
Joe.Bloggs2@MyDomain.Com
Secondary smtp: Joe.Bloggs@MyDomain.com

But the Uniqueness Check works not if you change the eMail-Address over the General Tab (mail attribute), so editing here is useless.

Hi,

The process of moving a mailbox will not change its e-mail addresses. What comes to my mind is the possibility that the move is causing the mailbox to belong to a different recipient policy or something like that and the Recipient Update Service decided to update the e-mail addresses of the mailbox.

One suggestion is to set RUS to never run, do the move, inspect the mailbox to check its state, compare it to the policies and then let RUS run again and confirm if that is what is touching the e-mail address.

When you add an SMTP Address to an existing user account, Exchange (and we are talking Exchange 2003...