ZCO and Exchange accounts

Is anyone here using Outlook 2010 with ZCO and Exchange accounts ?

Which way is it better to set this up, add Exchange to the Zimbra profile or add Zimbra to a profile that already includes Exchange ?

Has anyone encountered any specific problems with either of these set ups ?

The services can be added in either order, but you can't add Exchange to Zimbra within an Outlook session. (You have to use the Mail applet in the control Panel, whereas adding Zimbra to Exchange can be done in Outlook.)
Exchange insists on making itself the default store for incoming mail.
See the usage notes attached to Bug 12518 for some more detail.
Thanks
David

I fail to see what functionality I loose adding Zimbra as a second account

I don't have an Exchange account but some of my users do.

I do have Zimbra set up with IMAP in Outlook. When I added ZCO as a second account all seems to work fine.

What am I missing ?

I'll attach the "Usage notes" from Bug 12518 which I think spell out the key differences.

The issue of Exchange having to be the default store is less problematic with Outlook 2010 (where, unlike older versions, your Sent Items will still be synchronized to the Zimbra server) but delegate functions (Open Other User's Folder etc) cannot currently be supported with any Outlook version when you combine Exchange and Zimbra in one profile.

Cheers
David

Great, you have been a lot of help

Thank you

The last part of the 12518 file, under Delegates, states :

"There are some outstanding issues with delegate functionality which have not yet been fully addressed. For the moment, for all Outlook versions, the use of the Zimbra delegate functions, Open Other User's Folder and Send On Behalf Of, cannot be supported in a profile where Zimbra does not provide the default store."

This suggests that if an Exchange account is added to a Zimbra profile it should work without issue.

Is this only the case for "Build: zco: 7.0.0.6255" and above or has it been added to zco 6.x at any point ?

Edit : sorry - I mean it should work without issue in OL2010

> This suggests that if an Exchange account is added to a Zimbra profile it should work without issue.
Unfortunately not, since Exchange makes itself the default store even when added to an existing profile.

> Is this only the case for "Build: zco: 7.0.0.6255" ... ?
Yes. The changes have not been rolled back into 6.x.

David

So what happens with multiple exchange accounts - as 2010 is supposed to support ? Surely they can't all become the default !

My users have been getting a lot of errors along the lines of:

Code:

---

You can't send a message on behalf of this user unless you have permission
to do so. Please make sure you're sending on behalf of the correct sender,
or request the necessary permission. If the problem continues, please
contact your helpdesk.

---

and :

Code:

---

#MSEXCH:MSExchangeIS:/DC=com/DC=xxxx:xxxxxxxx[xxx:0x00000xxx:0x000000xx]
#SMTP#

---

when sending mail from their Zimbra accounts after adding an exchange account.

Also there's a lot of confusion happening in their sent items folders, as would be expected with the SMTP error.

I have found some stuff that might help here and here, although the second link basically tells me it's an issue with a setting on the Exchange server to which no-one friendly has access. This also makes me wonder if even an IMAP account would work with this Exchange server if I set up a VPN for them.

Is there any work around for this ? If not is there any hope of Exchange and Zimbra ever playing nice in the near future ? We're on the verge of buying a pro licence but this is a real show stopper - the Outlook connector is a BIG thing for these people.

EDIT : we're on v6 - will v7 do this ?

Ok - running 7.1.2 now with updated zco and still the same error messages as above.

This really doesn't work for contractors who have to use Exchange accounts next to their own email.

Am I right in thinking bug 50278 is covering this ? I'm trying to gather logs for bug report. If 50278 isn't related I'll open a fresh bug.

Sorry. I've not had a chance to look at this yet.
I think it would make sense to raise a separate bug covering the specific issues which you are seeing, and referencing the 2 related bugs - 50278 and 12518.
Thanks
David