Re: ghost recipient cn't be reached

Jeff,

Please have a look at the following article.

251168 XCLN: Meeting Request Generates Non-Delivery Report for a Recipient
Not
http://support.microsoft.com/?id=251168

Note, the delegate(s) you need to remove would be on the recipient's client,
not the sender's client.

Hope this helps.


--
Greg Mansius [MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.


"JeffO" <jeff.oreilly@denverNOSPAMwater.org> wrote in message
news:0bfa01c34ba7$152b5990$a401280a@phx.gbl...
> I had two users inthe same department quit. The two
> replacements inherited the old PCs. The PCs were already
> set up to do several scheduled tasks that included Access,
> Excel, VMS, Monarch Pro, Windows Task Sceduler, and
> Outlook XP. Not being an accountant, and with everyone
> paranoid that some unknown task might get broken, they
> wanted me to migrate all the old users' stuff to the new
> profiles.
> The pace here is so fast, I don't remember what I did. I
> know I didn't migrate Outlook files, because they contain
> personal emails, etc. There may have been other files in
> their profile that were copied straight over from the old
> profiles.
>
> But here's the problem:
> When each sends a meeting request to anyone, they get an
> error that "The following recipient(s) could not be
> reached:" and one of the previous employees is named. Her
> name doesn't exist in any list that can be found. Since
> the new employees hadn't any accumulations of saved mail,
> I had one account erased on the Exchange server and
> rebuilt from scratch - but the problem persists.
> I've uninstalled Outlook, reinstalled, searched the
> registry, search the hard drive... the old employee's name
> keeps popping up like a bad dream.
> All other things are working great.
>
> Anyone have any idea where her name might be hiding?
> It's almost certainly on the PC, not the Exchange server.