<div>
Make sure that when you imported the targetAddress attribute was populated with the target email address?
</div>


Make sure that when you imported the targetAddress attribute was populated with the target email address?

<div>
<div class="content wysiwyg-content">
Hi Experts,<br />
<br />
I have been testing the CSVDE tool (<a href="http://technet.microsoft.com/en-us/library/cc732101(WS.10).aspx" rel="ugc">http://technet.microsoft.com/en-us/library/cc732101(WS.10).aspx</a>) with the goal of bulk importing contacts from another organisation. I want the contacts mail-enabled, so they must have their primary SMTP record imported.<br />
<br />
In my testing I imported the proxyAddresses attribute, which contains all the associated email addresses for a contact, and found that mail routing failed to these contacts. The message tracker in Exchange 2003 system manager showed these messages are submitted to the categoriser and then go no further. I then noticed that the contacts contained x.400 attributes from their original organisation; could this be why the message routing was failing?<br />
<br />
I created a manual contact with primary SMTP, and allowed my default recipient policy to create a couple more email addresses, and email to this contact works fine.<br />
<br />
I guess the easy answer is that I only need to import the SMTP record in the proxyAddresses attribute, but I'd like to know why the x.400 record had the effect of preventing mail routing please.<br />

</div>
</div>


Hi Experts,

I have been testing the CSVDE tool (http://technet.microsoft.com/en-us/library/cc732101(WS.10).aspx) with the goal of bulk importing contacts from another organisation. I want the contacts mail-enabled, so they must have their primary SMTP record imported.

In my testing I imported the proxyAddresses attribute, which contains all the associated email addresses for a contact, and found that mail routing failed to these contacts. The message tracker in Exchange 2003 system manager showed these messages are submitted to the categoriser and then go no further. I then noticed that the contacts contained x.400 attributes from their original organisation; could this be why the message routing was failing?

I created a manual contact with primary SMTP, and allowed my default recipient policy to create a couple more email addresses, and email to this contact works fine.

I guess the easy answer is that I only need to import the SMTP record in the proxyAddresses attribute, but I'd like to know why the x.400 record had the effect of preventing mail routing please.


Importing contacts in to Active Directory with SMTP attribute

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).