Switched Hosted Exchange providers.  Now, Outlook users get errors using autofill.

Posted on 2012-09-19
Last Modified: 2012-09-24

I just recently switched Hosted Exchange providers.  People using Outlook that try to email me get error messages.  I've been able to tell the ones that use Outlook 2010 to click on the X next to my email address is the drop down on autofill when sending a new message.  Then they type in my email address and then it works fine.  Although, if there are users that use the same Exchange provider, even though I've edited their NK2 file (they have Outlook 2007) and deleted my email out of it, it still tries to send to my old box in the old provider which has been deleted.  I guess I'm not so worried about that problem as I am the rest.  Is there any trick to have people that send email using the autofill not need to go through this, especially with Outlook 2007?  Any other suggestions?  Thanks!
Question by:kendalltech
    LVL 12

    Accepted Solution

    When you switch to a new exchange provider, the following functions are broken:
    1. Sending e-mail using the auto fill cache
    2. Replying to old e-mail that was received from other Exchange users when you're on the old provider

    The reason for this is that e-mail sent from one exchange user to another does not route using the SMTP e-mail address but rather property called "legacy exchanged DN" (details here if you want them: This is effectively the internal email address that Exchagne uses when sending mail between users. When you move to a new provider, you get new user accounts with new legacy Exchange DNs. When you try to send e-mail using one of the two methods above, which use the old legacy DN, you get a delivery failure.

    One way to work around this is to add the old legacy Exchange DNs to your user objects in the new hoster. You can add it using what is called an X500 proxy, which is basically a way of linking the old legacy DN to the new user account so mail still ends up in the right place. Details on doing it are here: Unfortunately, doing this requires administrative access to the Exchange server and most hosted providers will not allow this, though you can ask.

    The other workaround is the following:
    1. Have users clear out there Nickname caches
    2. Tell users that if they reply to e-mail received from a Exchange user while they were using the old hoster, when they hit "reply" they should manually delete the user names in the TO and CC fields and type them in again, which will cause the new legacy DN to be used.
    LVL 2

    Author Closing Comment

    Well done Julian123!  Thanks so much for the detailed and accurate answer to my question!

    Featured Post

    Free Trending Threat Insights Every Day

    Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

    Join & Write a Comment

    Local Continuous Replication is a cost effective and quick way of backing up Exchange server data. The following article describes the steps required to configure Local Continuous Replication. Also, the article tells you how to restore from a backup…
    In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
    The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

    733 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    21 Experts available now in Live!

    Get 1:1 Help Now