"Your message....was read"

[jim]

I've got a user who claims that every time she sends a message to a
particular group of people (about 20), she always gets a read receipt email
from somebody it wasn't sent to. I've checked all the recipients mailboxes
and i can't find any rules or delegate access that would account for this.

I tracked the message on the Exchange server (2000/SP3) and the only thing
it shows is that she definitely sent the message and the unintended
recipient definitely received it. Based on the tracking info it looks like
she intended to send him the message, but looking at the email directly you
can see that she clearly did not.

Is there a simple way i can track down how this message is being
misdirected? All parties are using Outlook2k3/SP1. We're running
Exchange2K in native mode.

Thanks in advance!

*Incidentally, this KB article was no help at all:
http://support.microsoft.com/default.aspx?scid=kb;en-us;222163

 

[Matthew Byrd [MSFT]]

Hi Jim,

It is most likly that the email is being sent to the unwanted user thru one
of three means:

1) Nested DL:
Ensure that if there are DLs within the DL that the Originator is sending to
that the unintended recipient does not exisit in any of nested DLs or any
DLs nested within the nested DLs

2) AD side configuration to forward all mail to mailbox X:
It is possible that one of the users in the DL has been configured in AD to
have all of their mail forwarded to a given user, contact, or DL. You can
check this by looking at the properties of all of the users in the DL in AD
and looking at the Exchange General Tab under Delivery Options. You will
want to look for the forwarding address.

3) Someone has configured a rule that forward the email to the unintended
recipient:

For #3 or for other forwarding you may need to go thru a process of
elimination. Take all of the users out of the DL except one ... send a test
messages from the originators outlook to the DL ... Repeat for each user in
the DL until you locate the users that is causing the email to get sent to
the unintended recipient.

Hope this helps,
--
Matthew Byrd
Microsoft PSS

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

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

 

[jim]

So there's no simple way to track the path of the message? It's going to
take a while to parse through every mailbox.

 

[Jim Schwartz]

Unless the group is very large, have the person send 1 message (separately)
to each recipient. Who ever has the setup will generate the second receipt.

 

[Brian Higgins]

or just save some time and do a general process of elimination... send 1
message to half the users, another to the 2nd half, see which message gets
the return from. keep cutting users in half till you've narrowed it down...
it's allot faster then one by one.

 

[Pat Cai[MSFT]]

Hi Jim,

I am afraid we have to send the test message to each recipient separately
in that DL. It is the only workaround to find out the problematic mailbox
currently. After detect the problematic mailbox, if the problem is caused
by a corrupted forward rule that could not be deleted in any snap-ins,
please refer to this article to remove it:

312433 How to use Mdbvu32.exe to identify and remove a delegate rule from a
mailbox in Exchange Server
http://support.microsoft.com/?id=312433

I fully understand your frustrations with this issue. Actually, I once had
this concern myself and submitted this suggestion to our product team
recently. We desire a special utility to fast detect this problem. Please
understand that Microsoft strives to engineer our products to satisfy the
needs of as many people as possible. Any product change is based on
customers' survey and feedback. So I also invite you to directly submit
your ideas or comments to us anytime via either of the following outlets.
Internet:
http://register.microsoft.com/mswish/suggestion.asp
Email:
mailto:[email protected]

Regards,

Pat Cai
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada. This and
other support options are available here:

BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/

If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default.aspx?scid=/international.aspx.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.