Person doesnt exist but name stiil rejects when a calendar request is

[Techgoober]

We have an executive secretary "Marge" that has been gone for quite some time, and her 5.5 email account does not exist any more. When sending a calendar request to one of the Execs she used to do scheduling for this message is immediately returned to the person scheduling the appt: (asterisks added for my protection)


From: System Administrator
Sent: Monday, April 24, 2006 9:25 AM
To: Marge
Subject: Undeliverable: Updated: Blah Blah Blah

Your message did not reach some or all of the intended recipients.

Subject: Updated: Blah Blah Blah

Sent: 4/24/2006 9:25 AM

The following recipient(s) could not be reached:

Marge on 4/24/2006 9:25 AM
The recipient name is not recognized
The MTS-ID of the original message is: c=US;a=
;p=a********;l=N*******-060424142447Z-3109
MSEXCH:MSExchangeMTA:AI_KC:N*******




does anyone have an idea where I should start tracking this down at?

 

[zbnet]

Delegate setting on the Exec mailbox still has an entry for her (now deleted) mailbox - unlike DLs, Delegate backlinks are not automatically removed when you delete a mailbox.

You can only access the Delegate tab from an Outlook client accessing the Exec's mailbox, it's not accessible from the Admin program.

 

[Techgoober]

Okay, the Exec was on an IBM laptop, running Microsoft Outlook 2003, which has caching on it...
I went in and looked at his global address book, and there was the old secretaries address. So I unchecked the "Use Cached Exchange Mode" in the account setup and closed out of the program. I reopened it and rechecked the box to reload the address book. She was gone!

Your response wasn't exactly right, because I had already made sure she was deleted from the Delegate links, BUT, it put me back on the track to relook at the Execs laptop for Caching of any type...

THANKS!! for all your help...

Jeff

 

[zbnet]

My response was as accurate as it could be with the information you revealed in your original post. You didn't tell us what you had already tried, nor what other config you had other than 5.5.

I'm glad your problem is sorted out now.