Home > Microsoft Exchange Tips > Exchange Server Administration Tips > Custom-recipient primary-address problems
Exchange Tips:
EMAIL THIS
 TIPS & NEWSLETTERS TOPICS 

EXCHANGE SERVER ADMINISTRATION TIPS

Custom-recipient primary-address problems


Serdar Yegulalp
05.05.2003
Rating: --- (out of 5)


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


In Exchange 5.5, custom recipient's primary addresses are stored as X.400 addresses, but each custom recipient will also have an external Internet address. Many administrators are a little confused by this approach, and assume that something in the way the addresses are created by default causes X.400 addresses to be the primary address type. To that end, they may try to change a primary address from X.400 to an Internet address, and often believe the only way to accomplish this is by deleting the X.400 address and providing an SMTP address instead.

This approach backfires, unfortunately, and any custom recipient address modified in this fashion will throw back a "User Unknown" error when mail arrives for them.

Part of the reason for why Exchange 5.5 does this has to do with the reason for the existence of an X.400 address, which is used in Exchange 5.5 for describing where the object is in the Exchange directory, but not the address it uses for external e-mail. Delete the X.400 name in Exchange and you rob Exchange of the ability to know where the user account is in its own internal hierarchy, in effect making mail unroutable to that account. The e-mail address may be valid, but Exchange has no idea what to do with it anymore.

The best way to switch to SMTP as being the primary way to refer to custom recipients is to change the "E-Mail" address at the bottom of the custom recipient's General tab to be an SMTP address. If the custom recipient has one X.400 address, you can modify it so it looks like the X.400 addresses assigned by Exchange to the mailboxes. (If there are two X.400 addresses, make one of them the primary X.400 for the Exchange organization you're using, and either keep the old one as a secondary proxy address or delete it.)

Exchange 2000 uses Active Directory for its internal directory, and substitutes the X.400 internal addressing scheme with Windows' own GUID (Globally Unique Identifier) addressing. This way, an object can be renamed, moved to another organization or domain, or what have you, but it will still maintain a unique, internally-addressable identity that has nothing to do with its external e-mail address.


Serdar Yegulalp is the editor of the Windows 2000 Power Users Newsletter. Check out his Windows 2000 blog at www.thegline.com/win2kblog/ for his latest advice and musings on the world of Windows network administrators – please share your thoughts as well!


Rate this Tip
To rate tips, you must be a member of SearchExchange.com.
Register now to start rating these tips. Log in if you are already a member.




Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


RELATED CONTENT
Exchange Server Administration Tips
Top 10 Microsoft Exchange Server tips of 2008
Database changes that enhance Exchange Server 2007 fault tolerance
How continuous replication methods affect Exchange 2007 log shipping
Analyzing Exchange ActiveSync data from .CSV report files
How to run Exchange Management Shell cmdlets in Exchange Server 2007
Eliminate .PST file use for secure email retention in Exchange 2007
Exchange Server 2007 log shipping and continuous replication
Benefits of backing up Exchange Server with Microsoft's DPM 2007
Exchange Server 2007 replication and database transaction basics
Microsoft Exchange Server 2003 database recovery methods

Microsoft Exchange Server 5.5
Migrating mailboxes from Exchange Server 5.5 to Windows SBS 2003
Remove Exchange 5.5 servers from a mixed mode Exchange environment
Solve server problems with the Exchange Troubleshooting Assistant tool
Best approaches for upgrading Exchange 5.5 to Exchange 2000 or 2003
Sharing free/busy calendar information between disparate Exchange 5.5 and Exchange 2003 organizations
Can we install another instance of Exchange Server on a second domain controller?
Connecting an Exchange 5.5 server to a new domain controller
Duplicating Exchange 5.5 Global Address views in Exchange Server 2003
Importing an Exchange 5.5 Global Address List into Exchange 2003 Active Directory
Is it safe to upgrade directly from Exchange 5.5 to Exchange Server 2003?
Microsoft Exchange Server 5.5 Research

RELATED RESOURCES
2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
Search Bitpipe.com for the latest white papers and business webcasts
Whatis.com, the online computer dictionary

DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.



Email Server Solutions: Exchange 2007, Exchange 2003, Exchange 2000, SharePoint
HomeNewsTopicsITKnowledge ExchangeTipsAsk the ExpertsMultimediaWhite PapersIT Downloads
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides enterprise IT professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective IT purchase decisions and managing their organizations' IT projects - with its network of technology-specific Web sites, events and magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Site Map




All Rights Reserved, Copyright 2004 - 2009, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts