Phantom forwarding (Full Version)

All Forums >> [Microsoft Exchange 2000] >> Message Routing



Message


Smallguy -> Phantom forwarding (24.Oct.2006 3:45:15 PM)

here is the situation

when ever a meeting request is sent to John Doe a NDR is received saying that Jane Doe did not receive the message. Jane doe is not part of the meeting and was not included as a recipient. This happens when anyone sends a meeting request to John Doe (including my self to rule out user error)

when did it start? After my boss deleted Jane Doe's account from AD, thus exchange.

Environment: exchange 2000, Windows 2000

what have I done.

1. Looked through all outlook settings on John Doe's computer ... no rules set up or forwarding that I can find.

2. Checked his account in exchange for forwarding and delegation

3. Went to in exchange system manager and turned and check the email tracking. Email gets sorted and put in John does; inbox.. thne nothing else in the logs.

4. I've check group member ships for Jane Doe and she is not in any groups any more

the exact error message (with out real users names or server name)

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

Subject: test Sent: 10/20/2006 3:30 PM

The following recipient(s) could not be reached:

Jane Doe on 10/20/2006 3:30 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.
<mail.xyz.com #5.1.1>

anyways I'm at a loss here if anyone has any ideas please let me know. I know I could recreate the email address but I want a fix not a band-aid

if there is any info that can help solve this let me know







jchong -> RE: Phantom forwarding (24.Oct.2006 3:47:05 PM)

Sometimes it's a phantom rule. Try this article.

Accepting or denying a meeting request causes a "5.1.1" non-delivery report in Exchange Server
http://support.microsoft.com/kb/312433




Smallguy -> RE: Phantom forwarding (24.Oct.2006 4:04:48 PM)

Thank you very much

I posted this on a few other forums nad recieved no replies

I don't know why I didn't find this on the ms site but it seems to have resolved our issue




Page: [1]