Hello All I have an exchange 2010 server. Im getting in the most of the computer an issue with de GAL: When an user send an email to one specific email account, it recieves an email that the email cant be delivered. Checking the email, it appears that emaill address is something like: IMCEAEX-_O=COMPANYNAME_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=Contacte7c7d452@SERVER.LOCAL The weird thing, is that happens in more than one computer, but sending to diferent mail accounts. Something, work deleting outlook cache, sometimes, updating the gal... I have notice, that instead taking the email address from the GAL; i take it from all address list --> All contacts it works fine Is there any way i can rebuild the GAL on the server or create it again? I have make a get-offlineaddressbook | update-offlineaddressbook , and them force to download the GAL on the outlook (and clean the cache.. etc) but did not work Thanks!!!!!

This user was either migrated from another organization or his account was deleted and recreated changing his legacyExchangeDN attribute. The sender of this message picked the name from his nickname cache or replied to an old message. There are two options I can share with you. 1. Instruct the sender to pick the name out of the address book. Delete his nickname cache file (.NK2) if necessary. 2. In the properties of the intended recipient add a new "other" address of type X500 (no dot) with the following value: /O=COMPANYNAME/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN=Contacte7c7d452@SERVER.LOCAL See how what I typed in derives from the address in the NDR? You can also change the legacyExchangeDN attribute of the recipient, but I don't recommend that because it can have other side effects. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

On Thu, 12 May 2011 18:26:56 +0000, Ed Crowley [MVP] wrote: > > >This user was either migrated from another organization or his account was deleted and recreated changing his legacyExchangeDN attribute. The sender of this message picked the name from his nickname cache or replied to an old message. There are two options I can share with you. > >1. Instruct the sender to pick the name out of the address book. Delete his nickname cache file (.NK2) if necessary. > >2. In the properties of the intended recipient add a new "other" address of type X500 (no dot) with the following value: > >/O=COMPANYNAME/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN=Contacte7c7d452@SERVER.LOCAL I'd leave off the "@server.local". I'm pretty sure that gets slapped on the end when the categorizer tries to find the address. That usually works, at least for me. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

This user was either migrated from another organization or his account was deleted and recreated changing his legacyExchangeDN attribute. The sender of this message picked the name from his nickname cache or replied to an old message. There are two options I can share with you. 1. Instruct the sender to pick the name out of the address book. Delete his nickname cache file (.NK2) if necessary. 2. In the properties of the intended recipient add a new "other" address of type X500 (no dot) with the following value: /O=COMPANYNAME/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN=Contacte7c7d452@SERVER.LOCAL See how what I typed in derives from the address in the NDR? You can also change the legacyExchangeDN attribute of the recipient, but I don't recommend that because it can have other side effects. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." Thanks! I have solved this specific issue with the user recreating the .ost and deleting all the cache from outlook. I will save the answer,a dn when happens again i will try that. As far i understand, you mean in the server, in the mailbox properties, right? Thanks!

You would add that address, X500:O=COMPANYNAME/OU=EXCHANGE ADMINISTRATIVE GROUP (FYDIBOHF23SPDLT)/CN=RECIPIENTS/CN=Contacte7c7d452 to the mailbox, yes.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."