The legacyExchangeDN on the mailbox is changing. That's what's referred to in 
the NK2 file - the email address could read 
[email protected]<mailto:[email protected]> - but so long as that 
legacyExchangeDN matches nothing in AD, it'll bounce.

A workaround is to export the old legacyExchangeDN from the object before you 
delete it, then if that user does come back you can add it as an X500 address 
as an alias.

Hth

Richard

From: [email protected] 
[mailto:[email protected]] On Behalf Of John 
Hornbuckle
Sent: 28 January 2010 16:12
To: MS-Exchange Admin Issues
Subject: E-mail bouncing if user has been deleted then re-added

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<mailto: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.

Reply via email to