I do believe that's what is called a W.A.D. (Works As Designed) The N2K file has to be "taught" again the frequent email recipients that a user emails to. It will take 1 or more selections of the correct email from the GAL to teach the N2K file again.
Mailboxes on Exchange, just like user accounts in AD has a unique identifier, even if you use the same user account for a user that has left and come back, if you have deleted the mailbox, the new mailbox, either created on the same AD account or a newly created account, still has a unique identifier, and the old one will not be associated with it. It is called the Directory Name in Exchange, and typically is a numerical (older Exchange version) or the users default email address minus the @ domainname.com or a combination of those two if it is a common name (JSmith for example). (From my observations.) I believe that the Exchange Directory Name could be hacked using ADSIEdit, but I'm not certain on that as I have never used ADSIEdit for that purpose. Our Help Desk techs have been trained to instruct users that call with this issue, to delete the entry from the N2K file, and then instruct the user to select the account from the GAL a couple of times. The reason it's a W.A.D. is although you have done everything according to the "rules", what you are doing only affects the server/domain side of things, the N2K file is a local workstation file, not server side. It has to be changed to reflect the server/domain side of things. Now, was that verbose enough for you? Sheesh, I'm tired just from typing all that.....;) On Thu, Jan 28, 2010 at 10:11 AM, John Hornbuckle < [email protected]> wrote: > We have users come and go, and sometimes they come back again. When they > go, I delete them in AD and in Exchange (2007). If they come back, I > recreate them. > > > > The problem I’ve noticed is that e-mail sent to users who have been > re-added seems to bounce back to the sender if the sender had previously > sent that user a message (before they were deleted and re-added) and the > recipient’s address is stored in Outlook’s .NK2 file. The NK2 file must > contain some behind-the-scenes stuff beyond just the obvious e-mail address, > because the recipients’ addresses aren’t changing and yet messages to them > are bouncing. And when you pick the recipient’s name from Outlook’s > drop-down list, the message **appears** to be correctly addressed using > our standard firstname.lastn...@domain structure. > > > > We can work around this by deleting the recipient’s name from sender’s > drop-down list / NK2 file. Then the sender can reach the recipient with no > problem, and the recipient’s address is added back to the sender’s NK2 file > and works from that point forward. > > > > But what’s up with that? > > > > > > > > John Hornbuckle > > MIS Department > > Taylor County School District > > www.taylor.k12.fl.us > > > > > > NOTICE: Florida has a broad public records law. Most written communications > to or from this entity are public records that will be disclosed to the > public and the media upon request. E-mail communications may be subject to > public disclosure. > > -- Sherry Abercrombie "Any sufficiently advanced technology is indistinguishable from magic." Arthur C. Clarke Sent from Keller, TX, United States
