Wednesday, April 25, 2012 8:20 PM
I have a user that all of her e-mail when leaving our Exchange 2007 environment the FROM/REPLY TO address gets changed to a IMCEAX style address.
I can't find anything wrong with her mailbox, any suggestions on troubleshooting this?
Her AD user object does have a \ character in the display name, CN and distinguished name. We're not sure how that got their so maybe just renaming the object will fix this. We haven't tried this yet as we don't control the AD objects, only the Exchange objects.
- Edited by JMeyer2009 Wednesday, April 25, 2012 8:25 PM
Thursday, April 26, 2012 12:15 AM
Have you disconnected and reconnected this mailbox recently?
Whats the behaviour in Outlook web access? If it works well in OWA then it something wrong with the outlook profile or config
Have you tried to clean nk2cache file in outlook n then send a test email?
Lets open up outlook and click on new mail message
Go to options and then click on Direct Replies to
Check for option "Have replies sent to", See if it shows the correct name.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Hasnain Shaikh| My blogs: http://messagingserversupport.com
- Proposed As Answer by Terence Yu Thursday, April 26, 2012 2:36 AM
Thursday, April 26, 2012 2:35 AM
That the IMCEA encapsulation occurs is telling you that there is no valid SMTP address for the user.
1. It is nk2 cache file problem
2. It is AD user problem. You can’t control AD object.
Maybe you can create new database and move it to new database.
If it doesn’t work, you can create X500 address for i.
If it doesn’t work, you have to modify or recreate AD account.
TechNet Community Support
- Edited by Terence Yu Thursday, April 26, 2012 2:48 AM
Monday, May 07, 2012 7:14 AM
Monday, May 07, 2012 4:22 PMWe found where one of our on premise identity management tools was messing up the legacy Exchange DN. We fixed that and the problem went away. Thanks for all of the other ideas/places to check for this type of error though. Thanks.
- Marked As Answer by Terence Yu Tuesday, May 08, 2012 12:45 AM