Hi, Im not sure if this has come up before or not.. but we are running exchange 2000, and I had a user who installed google desktop and they were able to index and view emails from other mailboxes. Its not reading it locally or anything either.. no one has ever used the machine besides the user. I have not been able to identify any priveleges that he has that others do not. Any idea why this would be possible? And how can I prevent this, this is a huge security problem. Thanks! --Nate
you mean other users' mailboxes? I'm sure Google Desktop has nothing to do with this...sounds as if inappropriate permissions have been granted, somewhere...look in the Security tab of some of the mailboxes in question... -- Susan Conkey [MVP] "Smartmonkey" <ctmh@online.nospam> wrote in message news:eR2y$NahGHA.4864@TK2MSFTNGP03.phx.gbl... > Hi, > > Im not sure if this has come up before or not.. but we are running exchange > 2000, and I had a user who installed google desktop and they were able to > index and view emails from other mailboxes. > > Its not reading it locally or anything either.. no one has ever used the > machine besides the user. > > I have not been able to identify any priveleges that he has that others do > not. > > Any idea why this would be possible? And how can I prevent this, this is a > huge security problem. > > Thanks! > > --Nate > > > > > > >
Correct, sorry if i misslead but im not blaming google desktop search.. just trying to find out what has been previously set on exchange / ad that could cause this. Any thoughts on what privelege this user could have that would allow him to access other mailboxes?? "Susan" wrote in message news:ewikCjahGHA.4864@TK2MSFTNGP03.phx.gbl... > you mean other users' mailboxes? I'm sure Google Desktop has nothing to > do > with this...sounds as if inappropriate permissions have been granted, > somewhere...look in the Security tab of some of the mailboxes in > question... > > -- > Susan Conkey [MVP] > > > > "Smartmonkey" <ctmh@online.nospam> wrote in message > news:eR2y$NahGHA.4864@TK2MSFTNGP03.phx.gbl... >> Hi, >> >> Im not sure if this has come up before or not.. but we are running > exchange >> 2000, and I had a user who installed google desktop and they were able to >> index and view emails from other mailboxes. >> >> Its not reading it locally or anything either.. no one has ever used the >> machine besides the user. >> >> I have not been able to identify any priveleges that he has that others >> do >> not. >> >> Any idea why this would be possible? And how can I prevent this, this is >> a >> huge security problem. >> >> Thanks! >> >> --Nate >> >> >> >> >> >> >> > >
he's got to have "full mailbox" and/or "send as" permissions somewhere...either on the mailboxes in question, or somewhere higher in the hierarchy... -- Susan Conkey [MVP] "Nate" <ctmh@online.nospam> wrote in message news:OlQ4mIphGHA.4144@TK2MSFTNGP02.phx.gbl... > Correct, sorry if i misslead but im not blaming google desktop search.. just > trying to find out what has been previously set on exchange / ad that could > cause this. > > Any thoughts on what privelege this user could have that would allow him to > access other mailboxes?? > > > "Susan" wrote in message > news:ewikCjahGHA.4864@TK2MSFTNGP03.phx.gbl... > > you mean other users' mailboxes? I'm sure Google Desktop has nothing to > > do > > with this...sounds as if inappropriate permissions have been granted, > > somewhere...look in the Security tab of some of the mailboxes in > > question... > > > > -- > > Susan Conkey [MVP] > > > > > > > > "Smartmonkey" <ctmh@online.nospam> wrote in message > > news:eR2y$NahGHA.4864@TK2MSFTNGP03.phx.gbl... > >> Hi, > >> > >> Im not sure if this has come up before or not.. but we are running > > exchange > >> 2000, and I had a user who installed google desktop and they were able to > >> index and view emails from other mailboxes. > >> > >> Its not reading it locally or anything either.. no one has ever used the > >> machine besides the user. > >> > >> I have not been able to identify any priveleges that he has that others > >> do > >> not. > >> > >> Any idea why this would be possible? And how can I prevent this, this is > >> a > >> huge security problem. > >> > >> Thanks! > >> > >> --Nate > >> > >> > >> > >> > >> > >> > >> > > > > > >
