On an Exchange 2007 server, I change a typo on an alias from firstname.lastname2@ourdomain.com to firstname.lastname@ourdomain.com. In the mailbox properties for the end user in the Exchange Management console the name has been altered in each place, but mail is still being delivered to the old email address. Any help would be greatly appreciated.

On Thu, 25 Mar 2010 04:15:46 +0000, jwmms1 wrote:>>>On an Exchange 2007 server, I change a typo on an alias from firstname.lastname2@ourdomain.com to firstname.lastname@ourdomain.com. In the mailbox properties for the end user in the Exchange Management console the name has been altered in each place, but mail is still being delivered to the old email address. >>Any help would be greatly appreciated. Could you explain what it was you changed? Was it the "alias" or wasit a SMTP proxy address? Or was it a "name"?If it was the SMTP proxy address, did you leave the old address as asecondary SMTP proxy address?Messages sent inside your organization use the legagyExchangeDN as theaddress. Changing the SMTP proxy addresses won't have any effect onthat.---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

Hi Jwmms1, Please in user's properties | E-mail addresses tab, make sure firstname.lastename2@outdomian.com is removed. If you change the Alias in General tab, it will create a new SMTP address, but the old one is still there. If you have further questions, please let me know. Thanks, Elvis

The name has been corrected in the Properties | E-mail addresses tab. The firstname.lastname2@ourdomain.com has been changed to firstname.lastname@ourdomain.com. When I send a message to the corrected addresss, I get: The recipient's e-mail address was not found in the recipient's e-mail system. Microsoft Exchange will not try to redeliver this message for you. Please check the e-mail address and try resending this message, or provide the following diagnostic text to your system administrator. Any ideas? Jesse

Hi Jesse, How did you send the email? Via MAPI or SMTP/pop3 mode? I suggest you verify the proxyaddresses and legacyexchangeDN attribute in ADSIedit.msc. (Expand Domain | CN=Users | problematic user properties). a. When the message is submitted by using SMTP client, the SMTP address is used to submit the message. In addition, the Sender and Recipient are resolved by searching the proxyAddresses attribute. For example, if the recipient’s SMTP domain is configured as authoritative domains but the recipient email address cannot be found in proxyAddresses attribute of all the users. Then, a NDR message will be generated indicated that the user does not exist. In contrast, if the message sent to an external recipient, nevertheless, the recipient email address can be found in the proxyaddresses attribute of the local user, the message will be delivered to the local user instead of the external recipient. b. When the message is submitted by using MAPI client such as Outlook or OWA, the legacyExchangeDn is used to submit the message. Therefore, if the submitted recipient’s legacyExchangeDn cannot be found in AD user object, a NDR message will be generated indicated that the recipient does not exist. The issue can be caused by several factors. You need to check: 1) Whether the issue occurs sending a new message or replying an old message? If you reply a message, the MAPI property PR_SENDER_EMAIL_ADDRESS of the original message is used to submitted the legacyExchangeDn. If the property is not matched the current legacyExchangeDN of the user in AD, the NDR message will be received. 2) If the issue also occurs when sending a new message, you need to check NK2 (Outlook Autocomplete) file, Offline Address Book files which will be used to submit the recipient’s LegacyExchangeDN. You can rename the NK2 file and have Outlook works in Online Mode to narrow down the issue. If the issue persists, could you please paste the “the following diagnostic text” here? Thanks, Elvis

Elvis: The proxyAddress is correct and mail will flow into the account. The issue seems to be that the Exchange GAL is holding firstname.lastname2@ourdomain.com instead of being updated to the revised address.

What other information may I provide that may offer assistance with this error? By way of correction, internal nor external email messages are being delivered to the affected account Thanks.

So, are you sending the test messages by typing in the new correct email address, or just choosing the user from the GAL? If you are choosing from the GAL, it may take some time for the correct address to show up there, as it fist has to be generated, and then if you are running your clients in cached mode it also hsa to propagate to the clients. Have you tried sending via Outlook Web Access? It's address book will be live as opposed to the offline copy that gets sent to the Outlook clients usually on a daily basis.

Elvis: The proxyAddress is correct and mail will flow into the account. The issue seems to be that the Exchange GAL is holding firstname.lastname2@ourdomain.com instead of being updated to the revised address. Try to update the GAL so that it contains the new address like this: update-GlobalAddressBook "YourGALName" OR to update all get-GlobalAddressBook |update-GlobalAddressBook and then try sending the email to the user. And if trying from Outlook then u must first update the address lists and then generate the Offline Address Book. Plz see this to generate the OAB manually: www.exchangeGeek.wordpress.com Regards,Laeeq Qazi|Team Lead(Exchange + Sharepoint + BES + DynamicsCRM) www.HostingController.com

The problem was the result of an Active Directory replication issue that was occuring on this child domain. I cleared up the AD issue and the Exchange issue resolved itself! Huh, who knew? Thanks much for all the help and support