Software

Ask something
Discussion Locked

email account does not exist

0 helpful
8 replies

by dreynolds

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We are using Exchange 2003 and Outlook 2003. Some users receive the following message when sending an appointment to a different person (usersa).

The following recepient(s) could not be reached:
Usreb and Date
The e-mail account does not exist at the organization this message was set to.

Userb was removed from the Network months ago. Why do we get it and how do I eliminate it?

8 replies

by mroux

Hi

I have had this problem where userb was set as a delegate on usera's account and "Delegate receives copies of meeting-related messages sent to me" is checked. Try deleting userb from usera's delegates.

by frank_roussel

I have the same issue right now.

There is no delegates in user's Outlook, and userb has been deleted from the network, so obviously, not member of any groups.

Any more ideas?

by uppalpati

Hi dreynolds,

Its my pleasure to answer your query.
USERB should have been delegate on USERA mailbox.Please remove USERB from delegates list.

Then in Active directory,Check USERA account >Go to Exchange general > Delivery options > Send on behalf >Remove USERB from the list.

That should resolve the issue.

by sapphire1

mail account has been deleted and only SID can be seen in the exchange advanced - mailbox rights. email address cannot be seen under the send on behalf box on the delivery options. How do you remove the SID, even the enterprise admin doesn't have access to do this?

by sapphire1

how can sid be removed from mail box rights appears as though even the enterprise admin is unable to remove the sid. Sid belongs to person's mail account that has now been deleted. Person had be made delegated user on mailbox. Now messages are be returned to those that setup meeting requests saying the email address no longer exists.

by dgreco

I found this elsewhere and copied it for you:
This is easy to fix!
We've had this problem multiple times. All you need to do to fix it is go to the person who used to have this delegate, add a delegate and save it and then remove the delegate. This re-writes the permissions table and corrects the problem. See http://support.microsoft.com/kb/312433/en-us for more info.

This discussion is closed to new replies.