Hello everybody,

we have a shared mailbox issue here, maybe someone know a best practise for
that? We are using shared mailbox access in Exchange Server 2007 SP1. Means,
a user has got his private MAPI mailbox and an additional MAPI mailbox like
"ITSupport". The ITSupport is shared with multiple users. Outlook 2007 SP1
is beeing used in Cache Mode. Works fine until now.

Now there are two Issues:

1) If a email message marked as "Sensitivity: Private" reaches the INBOX
from an Outlook Client (may be an Outlook Client from Organisation internal
or external) everybody sees "ITSupport - INBOX (1)" but there is no new item
in the inbox visible. If one of the users opens the mailbox as primary ("one
and only") mapi mailbox, the mailobject is visible. The users are having
FullAccess to the mailbox at the moment directly on the mailbox itself
("Manage Fullaccess" in EMC).

The only way to see PRIVATE email objects is by using the delegation tab in
combination with the "can see private objects". The Owner (which used this
ITSupport as secondary MAPI mailbox) cannot delegate himself. The FullAccess
and the Delegate rights are not usable in combination. We have to remove the
FullAccess so that the "can see private objects" is working.

We have lots of experience now with this situation and multiple solutions
but every solution has got a little thing we are not sure how to handle this
in the future administration concept. Is there any best practise? Especially
including the "SendAs" right. I assume that this situation was handled with
public folders in the past.

2) If the user is sending a mail from ITSupport with the FROM option in
Outlook the mail is stored in his privatemapi mailbox "SendItems". This is
by design we know. But what kind of best practise is availible to handle
this situation? We found some tools (Outlook Addons) which handle this, but
they need to be installed and are only running on a client with Outlook
opened. Not what the customer finds a good solution. The other way to send
using FROM and setting ITSupport on CC: with an "Mailbox - ITSupport"
serverbased rule "If mail from ITSupport - then copy to SendItems" would be
an solution, but the customer is not very amused by this step.

Hope anyone has got an nice answer!

Regards,
Roger

Nothing on that issue?

Regards,
Roger

What is the "issue"? It's helpful to copy the message you are replying to so
we know what the problem is and what suggestions were offered already.

--
Diane Poremsky [MVP - Outlook]
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:


EMO - a weekly newsletter about Outlook and Exchange:


Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com

You can access this newsgroup by visiting
http://www.microsoft.com/office/comm...s/default.mspx or point your
newsreader to msnews.microsoft.com.


"Roger Wassner" wrote in message
...
Nothing on that issue?

Regards,
Roger

Hi Diane,

the issue was my first post, right above your answer. We have tried multiple
ways to solve this in "pleasure", but we are still searching for the best
way, for a best practise. I really would like to know how others are
handling this. I guess others are using this "feature", too. Below the text
i have postet these days.

Regards,
Roger


"Roger Wassner" wrote in message
...
Hello everybody,

we have a shared mailbox issue here, maybe someone know a best practise
for that? We are using shared mailbox access in Exchange Server 2007 SP1.
Means, a user has got his private MAPI mailbox and an additional MAPI
mailbox like "ITSupport". The ITSupport is shared with multiple users.
Outlook 2007 SP1 is beeing used in Cache Mode. Works fine until now.

Now there are two Issues:

1) If a email message marked as "Sensitivity: Private" reaches the INBOX
from an Outlook Client (may be an Outlook Client from Organisation
internal or external) everybody sees "ITSupport - INBOX (1)" but there is
no new item in the inbox visible. If one of the users opens the mailbox as
primary ("one and only") mapi mailbox, the mailobject is visible. The
users are having FullAccess to the mailbox at the moment directly on the
mailbox itself ("Manage Fullaccess" in EMC).

The only way to see PRIVATE email objects is by using the delegation tab
in combination with the "can see private objects". The Owner (which used
this ITSupport as secondary MAPI mailbox) cannot delegate himself. The
FullAccess and the Delegate rights are not usable in combination. We have
to remove the FullAccess so that the "can see private objects" is working.

We have lots of experience now with this situation and multiple solutions
but every solution has got a little thing we are not sure how to handle
this in the future administration concept. Is there any best practise?
Especially including the "SendAs" right. I assume that this situation was
handled with public folders in the past.

2) If the user is sending a mail from ITSupport with the FROM option in
Outlook the mail is stored in his privatemapi mailbox "SendItems". This is
by design we know. But what kind of best practise is availible to handle
this situation? We found some tools (Outlook Addons) which handle this,
but they need to be installed and are only running on a client with
Outlook opened. Not what the customer finds a good solution. The other way
to send using FROM and setting ITSupport on CC: with an "Mailbox -
ITSupport" serverbased rule "If mail from ITSupport - then copy to
SendItems" would be an solution, but the customer is not very amused by
this step.

Hope anyone has got an nice answer!

Regards,
Roger

Unfortunately, this is a newsgroup and messages something get lost, deleted,
marked read, or not synced with all the servers in the farm, its not a forum
where the messages are grouped on one web page and you can "bump" your
message to the top of the new message list with the original message. So to
insure everyone can see it, you need to include the original if you want to
'bump' the message, or when you reply.

1. Private means only the actual mailbox owner acct can see it unless the
delegate has the correct permissions. I'm not aware of any 'best practices'
for dealing with it.

2. Unless there is something you can filter on for an after sending rule
(like specific words in the body) you'll need to use a utility or move the
message to the sent folder later. Or use the CC (or a BCC) method.

--
Diane Poremsky [MVP - Outlook]
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:


EMO - a weekly newsletter about Outlook and Exchange:


Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com

You can access this newsgroup by visiting
http://www.microsoft.com/office/comm...s/default.mspx or point your
newsreader to msnews.microsoft.com.


"Roger Wassner" wrote in message
...
Hi Diane,

the issue was my first post, right above your answer. We have tried
multiple ways to solve this in "pleasure", but we are still searching for
the best way, for a best practise. I really would like to know how others
are handling this. I guess others are using this "feature", too. Below the
text i have postet these days.

Regards,
Roger


"Roger Wassner" wrote in message
...
Hello everybody,

we have a shared mailbox issue here, maybe someone know a best practise
for that? We are using shared mailbox access in Exchange Server 2007 SP1.
Means, a user has got his private MAPI mailbox and an additional MAPI
mailbox like "ITSupport". The ITSupport is shared with multiple users.
Outlook 2007 SP1 is beeing used in Cache Mode. Works fine until now.

Now there are two Issues:

1) If a email message marked as "Sensitivity: Private" reaches the INBOX
from an Outlook Client (may be an Outlook Client from Organisation
internal or external) everybody sees "ITSupport - INBOX (1)" but there is
no new item in the inbox visible. If one of the users opens the mailbox
as primary ("one and only") mapi mailbox, the mailobject is visible. The
users are having FullAccess to the mailbox at the moment directly on the
mailbox itself ("Manage Fullaccess" in EMC).

The only way to see PRIVATE email objects is by using the delegation tab
in combination with the "can see private objects". The Owner (which used
this ITSupport as secondary MAPI mailbox) cannot delegate himself. The
FullAccess and the Delegate rights are not usable in combination. We have
to remove the FullAccess so that the "can see private objects" is
working.

We have lots of experience now with this situation and multiple solutions
but every solution has got a little thing we are not sure how to handle
this in the future administration concept. Is there any best practise?
Especially including the "SendAs" right. I assume that this situation was
handled with public folders in the past.

2) If the user is sending a mail from ITSupport with the FROM option in
Outlook the mail is stored in his privatemapi mailbox "SendItems". This
is by design we know. But what kind of best practise is availible to
handle this situation? We found some tools (Outlook Addons) which handle
this, but they need to be installed and are only running on a client with
Outlook opened. Not what the customer finds a good solution. The other
way to send using FROM and setting ITSupport on CC: with an "Mailbox -
ITSupport" serverbased rule "If mail from ITSupport - then copy to
SendItems" would be an solution, but the customer is not very amused by
this step.

Hope anyone has got an nice answer!

Regards,
Roger

Hi,

1. Private means only the actual mailbox owner acct can see it unless the
delegate has the correct permissions.

Yes right.
I find it a bad thing that FullAccess on the Mailbox Store does not overide
this thing. When a user has his private Mailbox and connected to another
MAPI Mailbox i.e. the shared mailbox we have the problem. He cannot delegate
himself to see private, needs to create another MAPI Profile, switch, and so
on. The users here arent IT guys dealing easy with this steps. Thought
somebody has the same situation.

need to use a utility or move the message to the sent folder later.
Or use the CC (or a BCC) method.

Yes right, too.
Thought somebody has a best practise on that.

Thank you for the answers.

Regards
Roger