Re: "Your message....was read"

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: jim (jim_at_NOSPAM.com)
Date: 03/03/05


Date: Thu, 3 Mar 2005 15:02:36 -0500

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.

"Matthew Byrd [MSFT]" <matbyrd@online.microsoft.com> wrote in message
news:OpuYlKCIFHA.3500@TK2MSFTNGP14.phx.gbl...
> 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" <jim@NOSPAM.com> wrote in message
> news:%23YBtN2BIFHA.3376@TK2MSFTNGP14.phx.gbl...
> > 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
> >
> >
>
>



Relevant Pages

  • Re: "Your message....was read"
    ... > 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: ...
    (microsoft.public.exchange2000.general)
  • Re: "Your message....was read"
    ... that the unintended recipient does not exisit in any of nested DLs or any ... DLs nested within the nested DLs ... and looking at the Exchange General Tab under Delivery Options. ...
    (microsoft.public.exchange2000.misc)
  • Re: "Your message....was read"
    ... that the unintended recipient does not exisit in any of nested DLs or any ... DLs nested within the nested DLs ... and looking at the Exchange General Tab under Delivery Options. ...
    (microsoft.public.outlook)
  • Re: "Your message....was read"
    ... that the unintended recipient does not exisit in any of nested DLs or any ... DLs nested within the nested DLs ... and looking at the Exchange General Tab under Delivery Options. ...
    (microsoft.public.exchange2000.admin)
  • Re: "Your message....was read"
    ... that the unintended recipient does not exisit in any of nested DLs or any ... DLs nested within the nested DLs ... and looking at the Exchange General Tab under Delivery Options. ...
    (microsoft.public.exchange2000.general)