Current (Known) Issues in ZCS 8.6 Build 1153

When composing a new message, using the tab key should get one into the body text area fairly quickly.

What I'm seeing currently is that it takes something like 34 keyboard tabs to get to the body text area in HTML Compose, and it seems to never go there in ASCII/Text Compose. It seems to select many other fields/buttons first.

If try to block some Applications in 8.6 in the Mobile Activesync Policy, looks like doesn't work, so I've tried to Wipe my devices and nothing happens:
1.- iPad Mini
2.- Android 4.4 in a VM environment
3.- iPhone 5

But when you click in the Wipe the Device, under Admin Console or in the user Web Client.

Bug 97304Upgrading from 8.5.1 to 8.6 doesn't check the local proxy variables and it fails the upgrade.

When upgrading, the Script validates the license against https://license.zimbra.com. If your Server is behind a proxy the upgrade script (and also the license activation itself) ignores the Proxy System Variable.

IE can not be set for compatibility mode when it interacts with ZCS 8.6 . Various signs of this are - warning about using an 'unsupported browser', blank emails when viewed or forwarded, login goes to the mobile or html/basic interface.

Bug 96991Zimbra Desktop does not work with ZCS 8.6.0 with shipped version of JRE

ZD will be unable to connect to the ZCS 8.6 server, error will be something like "Remote host closed connection during handshake".

Bug 96123User wants to be able to use "/" and quotes in task titles - FIXED in ZCS 8.6 Patch 1 -

User will be warned that task names can not have :

You'll get a pop-up box: Cannot save. you have errors that must be corrected: The subject cannot contain / (forward slash). "(double quote), or :(colon)

Tasks that were created in older ZCS versions that used those characters will prompt with that warning and force the user to rename when they are accessed in ZCS 8.6 .

Outlook Express handshake error

In Zimbra Collaboration 8.6, using as a Mail client Outlook Express, clients can receive the error about the CA, ca_unkown message, more info in the next Community Thread.
This issue is related with the next Bug - Bug 97232