|
|
| Shad Lofgreen 2002-10-05, 8:35 pm |
| Very rarely this problem occurs but it is a security risk none the less.
Occasionally an email intended for User1 will be delivered to User2 although
user 2 was not an intended recipient nor were they BCC'd. I've checked to
make sure that no alternate recipients have been set up so now I am baffled.
I am using Exchange Server 2000 with SP2. Can anyone shed some light on
this problem. It has already sent sensitive information to the wrong
recipient and is a problem. Please reply to forum group.
Shad
| |
|
| I cannot see how this is possible ... I think it is a human error
"Shad Lofgreen" <shadSPAM@geoinsight.com> wrote in message
news:eRJWVdVTCHA.3968@tkmsftngp12...
> Very rarely this problem occurs but it is a security risk none the less.
> Occasionally an email intended for User1 will be delivered to User2
although
> user 2 was not an intended recipient nor were they BCC'd. I've checked to
> make sure that no alternate recipients have been set up so now I am
baffled.
> I am using Exchange Server 2000 with SP2. Can anyone shed some light on
> this problem. It has already sent sensitive information to the wrong
> recipient and is a problem. Please reply to forum group.
>
> Shad
>
>
| |
| Lanwench 2002-10-05, 8:35 pm |
| Either someone's fat-fingering it or they've got rules. There's no way the
server is doing this on its own.
"Shad Lofgreen" <shadSPAM@geoinsight.com> wrote in message
news:eRJWVdVTCHA.3968@tkmsftngp12...
> Very rarely this problem occurs but it is a security risk none the less.
> Occasionally an email intended for User1 will be delivered to User2
although
> user 2 was not an intended recipient nor were they BCC'd. I've checked to
> make sure that no alternate recipients have been set up so now I am
baffled.
> I am using Exchange Server 2000 with SP2. Can anyone shed some light on
> this problem. It has already sent sensitive information to the wrong
> recipient and is a problem. Please reply to forum group.
>
> Shad
>
>
| |
| Shad Lofgreen 2002-10-05, 8:35 pm |
| Can anyone else shed some light on this problem?
"Lanwench" <lanwench@heybuddy.donotsendme.unsolicitedmail.yahoo.com> wrote
in message news:#4UGrNcTCHA.1648@tkmsftngp08...
> Either someone's fat-fingering it or they've got rules. There's no way the
> server is doing this on its own.
>
> "Shad Lofgreen" <shadSPAM@geoinsight.com> wrote in message
> news:eRJWVdVTCHA.3968@tkmsftngp12...
> > Very rarely this problem occurs but it is a security risk none the less.
> > Occasionally an email intended for User1 will be delivered to User2
> although
> > user 2 was not an intended recipient nor were they BCC'd. I've checked
to
> > make sure that no alternate recipients have been set up so now I am
> baffled.
> > I am using Exchange Server 2000 with SP2. Can anyone shed some light on
> > this problem. It has already sent sensitive information to the wrong
> > recipient and is a problem. Please reply to forum group.
> >
> > Shad
> >
> >
>
>
| |
| Mark Fugatt 2002-10-05, 8:35 pm |
| I have to agree with Lanwench, there is no way the server is going to do
this, unless the recipient has a client side rule configured, I have used
Exchange a long time now and never seen it happen.
Enable message tracking and then use the Message Tracking Center to see
exactly what the messages route was, that might shed some more light on it.
--
Mark Fugatt
Pentech Office Solutions Inc
www.exchangetrainer.com and www.4mcts.com
Visit www.msexchange.org for practical information on Microsoft Exchange
--- Please respond to this newsgroup and not directly via Email ---
"Shad Lofgreen" <shadSPAM@geoinsight.com> wrote in message
news:#lRMO1gTCHA.3748@tkmsftngp08...
> Can anyone else shed some light on this problem?
>
>
> "Lanwench" <lanwench@heybuddy.donotsendme.unsolicitedmail.yahoo.com> wrote
> in message news:#4UGrNcTCHA.1648@tkmsftngp08...
> > Either someone's fat-fingering it or they've got rules. There's no way
the
> > server is doing this on its own.
> >
> > "Shad Lofgreen" <shadSPAM@geoinsight.com> wrote in message
> > news:eRJWVdVTCHA.3968@tkmsftngp12...
> > > Very rarely this problem occurs but it is a security risk none the
less. [colo
r=darkred]
> > > Occasionally an email intended for User1 will be delivered to User2
> > although
> > > user 2 was not an intended recipient nor were they BCC'd. I've[/color]
checked
> to
> > > make sure that no alternate recipients have been set up so now I am
> > baffled.
> > > I am using Exchange Server 2000 with SP2. Can anyone shed some light
on[co
lor=darkred]
> > > this problem. It has already sent sensitive information to the wrong
> > > recipient and is a problem. Please reply to forum group.
> > >
> > > Shad
> > >
> > >
> >
> >
>
>[/color]
| |
| Ed Woodrick 2002-10-05, 8:35 pm |
| What did the message headers say? Was the unintended recipient actually on
the recipients list? Look at the message in the Sent Items folder of the
sender. What does it say there. Normally situations like this can be traced
back to something at the sending user's end. Like a bad address in a
contact.
"Shad Lofgreen" <shadSPAM@geoinsight.com> wrote in message
news:eRJWVdVTCHA.3968@tkmsftngp12...
> Very rarely this problem occurs but it is a security risk none the less.
> Occasionally an email intended for User1 will be delivered to User2
although
> user 2 was not an intended recipient nor were they BCC'd. I've checked to
> make sure that no alternate recipients have been set up so now I am
baffled.
> I am using Exchange Server 2000 with SP2. Can anyone shed some light on
> this problem. It has already sent sensitive information to the wrong
> recipient and is a problem. Please reply to forum group.
>
> Shad
>
>
| |
| Joe Hurst 2002-10-05, 8:45 pm |
| I have also had this problem although I still haven't figured it out. I
have checked the senders outlook "sent" box and the message would be
addressed to a different person than who recieved it. I am also getting
occasionally messages sent by one user but they show up as "sent" by someone
else. One thing I have noticed is that it has only happened with internal
senders & recipients though. I am using Exchange 2K w/ sp3 on Win2K server.
"Shad Lofgreen" <shadSPAM@geoinsight.com> wrote in message
news:eRJWVdVTCHA.3968@tkmsftngp12...
> Very rarely this problem occurs but it is a security risk none the less.
> Occasionally an email intended for User1 will be delivered to User2
although
> user 2 was not an intended recipient nor were they BCC'd. I've checked to
> make sure that no alternate recipients have been set up so now I am
baffled.
> I am using Exchange Server 2000 with SP2. Can anyone shed some light on
> this problem. It has already sent sensitive information to the wrong
> recipient and is a problem. Please reply to forum group.
>
> Shad
>
>
| |
| Trevor Lawrence 2002-10-05, 8:45 pm |
| How similar are the names of the recipients involved? Did the message
originate from within your Exchange organisation? Is it possible the sender
typed in a name incorrectly and had it resolved to the unintended recipient
without noticing it?
Trevor
"Ed Woodrick" <ewoodrick@ed-com.net.no.spam> wrote in message
news:O9A4J#iTCHA.3556@tkmsftngp08...
> What did the message headers say? Was the unintended recipient actually on
> the recipients list? Look at the message in the Sent Items folder of the
> sender. What does it say there. Normally situations like this can be
traced
> back to something at the sending user's end. Like a bad address in a
> contact.
>
>
> "Shad Lofgreen" <shadSPAM@geoinsight.com> wrote in message
> news:eRJWVdVTCHA.3968@tkmsftngp12...
> > Very rarely this problem occurs but it is a security risk none the less.
> > Occasionally an email intended for User1 will be delivered to User2
> although
> > user 2 was not an intended recipient nor were they BCC'd. I've checked
to
> > make sure that no alternate recipients have been set up so now I am
> baffled.
> > I am using Exchange Server 2000 with SP2. Can anyone shed some light on
> > this problem. It has already sent sensitive information to the wrong
> > recipient and is a problem. Please reply to forum group.
> >
> > Shad
> >
> >
>
>
|
|
|
|