Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NDR issue 1

Status
Not open for further replies.

hereigns

MIS
Sep 17, 2002
172
US
(W2K w/ spk 4 and Exchange 2K w/ spk 3)

When someone in our company sends an appointment invitation to Bob R. they get the following NDR (NOTE: this problem ONLY occurs when sending an invitation to Bob R.)

"The following recipient(s) could not be reached:
Jim Fox on 7/13/2006 3:51 PM
The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address.
<server.abc.com #5.1.1>"

Jim Fox no longer has a mailbox on our server it was deleted 2 years ago. I tried deleting Bob R.'s mailbox and user account which did not fix the problem (even renamed his user account).

I'm stumped on how/why this is happening. Any ideas would be appreciated.
 
Does Bob have Jim as a delegate on his Outlook account ?
 
Good question, from what I can tell he doesn't. I looked at associated delegates in Outlook and it is empty.
 
Jim might have been a delegate at one time. I *believe* that opening Outlook once with the /CleanServerRules switch will resolve that, but that also wipes out any existing server rules the user might have set.

Pat Richard, MCSE MCSA:Messaging CNA
Want to know how email works? Read for yourself -
 
58sniper,
That might work but I don't believe the switch is available in Outlook 2000. When I attempt to run it, it spits back, "command line argument is invalid, check the swtich".
 
I'm not familiar with ExMerge but will do my due dilegence and read up on the utility and go from there...thanks.
 
I contacted MS and they had me run a utility called MFCMapi.exe and delete a temp folder then restart the smtp service which seems to have fixed the issue. Yahoo!
 
Yep, we tried it on the client initially but ran into several problems in doing so. So, we did tried it on the server and all is well again.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top