So if I understand this correctly, I would need to create an alias in the Exchange 2003 Active Directory where my user account is listed and add the X500 legacy DN address. Then I would need to add the X500 address to my Exchange 2010 linked mailbox?
________________________________ From: Steve Hart [mailto:sh...@wrightbg.com] Sent: Friday, August 20, 2010 5:20 PM To: MS-Exchange Admin Issues Subject: RE: OAB and GAL Entries The answer is to add the X500 address to the new user account. The data you need is in the bounced email. I struggled a lot with the proper formatting of the address, but this format is working for a sample user: o=wright+20business+20graphics_ou=wbgkent_cn=recipients_cn=bwilli...@wrightbg.com<mailto:o=wright+20business+20graphics_ou=wbgkent_cn=recipients_cn=bwilli...@wrightbg.com> The +20 signifies a space. Note the underscores. Note that AFAIK these bounces only apply to internal users. Outlook caches SMTP addresses for external users, so outside people send email in to your users just fine. Since the problem only affects internal users, another solution is to manually delete the address entries in their Outlook, if you only had a few senders with a few problems. Another ugly solution is to delete or rename the Outlook .nk2 file, but then the user will lose all Outlook cached addresses, which usually isn't acceptable. Steve Hart Network Administrator 503.491.4343 -Direct | 503.492.8160 - Fax ________________________________ From: Chris Pohlschneider [mailto:chris.pohlschnei...@hollowayusa.com] Sent: Friday, August 20, 2010 2:00 PM To: MS-Exchange Admin Issues Subject: RE: OAB and GAL Entries Steve, I do get bounce backs involving IMCEAx kinds of address since I have moved my mailbox from my Exchange 2003 Org down to the Exchange 2010 resource forest. If I reply to an e-mail that was sent before I moved my mailbox, I get these bounce backs since the sender is in my original Exchange 2003 Org. Then on the flipside, a user in the Exchange 2003 Org tries to send me an e-mail from the auto-complete entry, it fails and says that it cannot be delivered because their auto-complete entry is pointing to my X500 address. I cannot figure out the best way to fix this. ________________________________ From: Steve Hart [mailto:sh...@wrightbg.com] Sent: Friday, August 20, 2010 12:21 PM To: MS-Exchange Admin Issues Subject: RE: OAB and GAL Entries Auto-complete is a function of Outlook, independent of anything done in OAB or GAL. Adding to the problem, in my experience is that Outlook caches AD names rather than email addresses for local users, so when you set up a new user account using a "reused" email address, Outlook auto-completes with the old directory name. Are you getting bounce backs involving IMCEAx kinds of addresses? Steve Hart Network Administrator 503.491.4343 -Direct | 503.492.8160 - Fax ________________________________ From: Chris Pohlschneider [mailto:chris.pohlschnei...@hollowayusa.com] Sent: Friday, August 20, 2010 8:48 AM To: MS-Exchange Admin Issues Subject: OAB and GAL Entries Hello, I believe I already know the answer to this question, but I would like to bounce this off some more intelligent individuals about Exchange than I. We have an Exchange 2010 Resource forest (not my idea) and have no GAL sync utility (not my idea either) to sync between the forests. When we move a mailbox from an Exchange 2003 Forest to the Exchange 2010 forest and a user from the Exchange 2003 forest tries to send an e-mail to the same mailbox that has been moved to the Exchange 2010 resource forest, it does not work. When they send the e-mail, the auto-complete resolves the e-mail address to the Exchange Organization that they used to be a member and that is why the message fails. Until the user deletes that old auto complete entry and then types in the full e-mail address of the moved mailbox, only then can they send a message. My question is would a GAL sync utility take care of this issue? If a GAL sync utility would not resolve this, is there any other known way to get around this? I have users complaining about this and I knew that I would. Just trying to convince non-technical management on the best course of action to resolve this. Chris Pohlschneider Holloway Sportswear Network Administrator chris.pohlschnei...@hollowayusa.com<mailto:chris.pohlschnei...@hollowayusa.com> 937-494-2559
