Exchange not sending mail to ONE mailbox

[NATCAT]

Hi All,

I am having an interesting problem where one user is no longer recieving email. RIght now all of the messages meant for that mailbox are stuck in the local queue for delivery.

So far I have rebooted (both computers) applied updates and ran the Exchange Best Practices Analyzer to no avail.

Is there a way to find out if a mailbox is corrupt, or recreate the mailbox and save the user's current email ?

 

[N0ktar]

You can export the mail from Outlook into PST and recreate the mailbox.

 

[RichardHuang]

You may check the Alias and name resolution for that mailbox. Do other users see that mailbox as correct name?

 

[NATCAT]

Actual we see the alias (when you type the first few letters in the to box) as Marvo(MARGO). Though when I check her info in AD its always Marvo.

Is this what you meant by alias ?

 

[NATCAT]

I will try to recreate the mailbox after hours and let everyone know if that made a difference.

Is there another way to troubleshoot problems with the individual mailboxes ?

 

[RichardHuang]

This is probably the reason. The exchange might resolve the user as Margo, however it can't find the correspondent info in AD. You could check the details of that account (go through all the tabs of the user properties) and make sure everywhere is correct. In addition, use adsiedit to check the user attributes.

 

[NATCAT]

Using ADSI edit and checking in AD users and computers the name correct name is used throughout.
Could it be an issue on the actual computer ?

 

[RichardHuang]

No, it is unlikely the computer problem. Did you check the attribute of LegancyExchangeDN for that user under ADSIedit?

 

[NATCAT]

Found it !! under the Legacy Exchange. cn=margo where it should be marvo

I'll figure out how to change it and let you know the outcome.

 

[RichardHuang]

To change the attribute of LagancyExchangeDN, just highlight it and click on Edit. It may take one or two days for the outlook client to get updated, unless you use the none-cached mode on the client.

 

[NATCAT]

The change was made to the name but there is no difference.
I am currently running the eseutil tool to see if that would help

 

[NATCAT]

We use cached mode. Why 1-2 days to update ? I've rebooted all 3 computers involved (the DC, exchsrvr and the user's PC) but this hasn't made a difference.
Defragging the database using eseutil and checking the consistency of the datastore with isinteg hasn't been fruitfull either.

 

[RichardHuang]

You can try the following to see if this helps:
1. Go to Exchange system manager, recipient update service, right click on recipient update service and click Rebuild
2. Go to Outlook client, change the account mode to none-cached mode, and then click on Tools - Send/Receive - Download Address Book

The above steps should update the Global Address on the client instantaneously.

 

[NATCAT]

Hi Richards,
Thanks for your help on this so far.Its been a learning experience.

I've rebuilt the update service and modified the account information as you suggested. But still no luck.

 

[RichardHuang]

If you send the user (Marvo) an email through web mail (OWA), can the user receive it? If yes, then you are in right track. Sometimes, the outlook auto-completion remembers the wrong info as well. You can delete the auto completion info for that user in outlook client.

 

[NATCAT]

Sending mail via OWA still makes no difference. And to add to the confusion one mail message was recieved by that mailbox today.

I am about to delete the user from AD and recreate another user with the same name. I'll let you know how it turns out.

 

[geranimo666]

Hi NATCAT-

I have been following your situation and am just curious on what results you've had since recreating the user account in A
AD..

thanks for any info
geranimo

 

[NATCAT]

Hi,
I've recreated the user and we seem to be getting email. Unfortunately I've had to delete all the messages for her in the local queue that refused to be delivered. But losing 9 messages vs not getting mail at all is a good tradeoff I think.

I will check in tomorrow to let you know if the problem has re-occured.

Again thanks for your help Richard.