Zimbra Collaboration 8.7.6 is Now Available

728-90-spo-banner-synacor
Were you wondering when native Chat would arrive in Zimbra Collaboration? It is here! Today, in Zimbra Collaboration 8.7.6 and in an early status introducing Chat and Zimbra Drive, a NextCloud/OwnCloud integration. We strongly recommend that you test these features on a staging or pre-production environment and provide us with feedback in these forums: Zimbra Chat Forum and Zimbra Drive Forum.

And some more great news! This Release includes the Ephemeral back-end, in Beta status. This major change in Zimbra architecture allows enabling protection against CSRF and cookie-reuse attacks without increasing load on LDAP.

Fixed issues ZCS 8.7.6

Here is a list of all the items addressed in this Release.

What’s New
Zimbra Chat *early release – Starting in Zimbra Collaboration 8.7.6, Zimbra includes a free and GPLv2 Chat product embedded in Zimbra, please click here for more information
Zimbra Drive *early release – Starting in Zimbra Collaboration 8.7.6, Zimbra includes a free and GPLv2 OwnCloud/NextCloud product embedded in Zimbra, please click here for more information
Ephemeral Backend – 17.13 release includes a beta release of a major change in Zimbra architecture that allows enabling protection against CSRF and cookie-reuse attacks without increasing load on LDAP and without causing the issues outlined in the following tickets:
106867 LDAP replicas not in sync with master
104858 Multiple auth tokens for same account are registered in LDAP
104947 Backup does not start
104922 Operational problem with our LDAP master
98274 Replication error for ldap server
94659 LDAP seems to hang
98386 Errors: webclient – auth credentials have expired
97408 Error Auth_Expired (auth credentials have expired) after upgrade
98530 Nightly server lockups
105203 Inconsistent account data
Security Fixes
107712 Improper limitation of file paths [CWE-22]
107684 Improper handling of privileges [CWE-280]

Bonus: Slide deck

We have released a slide deck about What’s New in Zimbra Collaboration 8.7.x, and we hope you like it. Follow us on Twitter and LinkedIn to keep up-to-date about upcoming webinars for Zimbra Collaboration, Zimbra Talk and Zimbra Suite Plus.

Click here if the slide deck is not working for you.

Quick note about our git repository and our Open Source Code

Downloading and building our Zimbra code? Keep reading…

Starting with ZCS 8.7.2 and above, we have new steps to download and see our code:

Note: Code is just published as it is. The objective is for people to see the code changes. There are some tweaks required for the build. We are working on restructuring.

Links

  • Read the Release Notes for Zimbra Collaboration 8.7.6 here
  • Download Zimbra Collaboration 8.7.6 here
  • Forum about Installation and Upgrade here

, , , , , , ,

13 Responses to Zimbra Collaboration 8.7.6 is Now Available

  1. Jered March 30, 2017 at 9:28 PM #

    The Zimbra Drive “more information” link above goes to the Chat ticket in Bugzilla.

    The “download” link _still_ requires a tedious sales leadgen form EVERY SINGLE TIME. Can you _please_ do something about this?

    • Jorge de la Cruz
      Jorge de la Cruz March 30, 2017 at 11:51 PM #

      Hi Jered,
      Fixed the link, sorry about that. If you are trying to download Zimbra OSE, use the zimbra.org site, no form required.

      Best regards

    • Jered March 31, 2017 at 6:04 AM #

      Whoa; I did not know that site existed; thanks! BTW, on zimbra.org the “Download” menu bar item takes me directly to the OSE download page (yay!), but the banner image “Download” goes back over to the leadgen form.

  2. Richard April 7, 2017 at 11:46 PM #

    Greetings,

    I’m afraid there’s something wrong with the RHEL 7 / CentOS 7 download, either with the file itself or with both the md5 and sha256 checksum files.

    Despite numerous downloads, they consistently fail:

    SHA256 checksum FAILED!
    WANTED : 2ddd8252ea86fc900e795b05c5d22a350dd86d1c753304f8fb168e0e3d8507b5 zcs-8.7.6_GA_1776.RHEL7_64.20170326144124.tgz
    RECEIVED: 5613a06e84d164562e96ffe79871cd8098e4c0d80ad257f00f130a64c19fb4c3 zcs-8.7.6_GA_1776.RHEL7_64.20170326144124.tgz

    The bad value is consistently the same.

    The download for RHEL 6 / CentOS 6 is fine, but that’s not the one I’m looking for :-)

    Thanks for looking into this!

    – Richard.

    • Jorge de la Cruz
      Jorge de la Cruz April 8, 2017 at 1:39 AM #

      Hi Richard,
      Take a look now, we have uploaded a new build, and it’s possible you were hitting an old build due to the cache, try it now.

      Best regards

    • Richard April 8, 2017 at 2:37 AM #

      Hi Jorge,

      Thanks for the quick reply. I retried, but I’m afraid the behavior did not change. I still get the following bad checksum values on fresh downloads of zcs-8.7.6_GA_1776.RHEL7_64.20170326144124.tgz:

      MD5: 4aff3d435ecddd72f84dee9c2e896c38
      (.md5 file has dd6e71321e1d292443a3b57f5f40ccb6)

      SHA256:5613a06e84d164562e96ffe79871cd8098e4c0d80ad257f00f130a64c19fb4c3
      (.sha256 file has: 2ddd8252ea86fc900e795b05c5d22a350dd86d1c753304f8fb168e0e3d8507b5)

      Any chance the checksum files were not updated to match the new build? Could you perhaps run md5sum or sha256sum on a known good file to double check?

      Thanks much,

      – Richard.

    • Jorge de la Cruz
      Jorge de la Cruz April 8, 2017 at 12:10 PM #

      hi Richard,
      You can check md5 for the new file here:
      https://wiki.zimbra.com/wiki/Recovering_from_upgrade_failure#CentOS.2FRHEL_6.2F7_upgrade_ZCS_8.6_or_earlier_to_ZCS_8.7.6

      Which means your new file is correct, the md5 we have on the website can be still cached, try to download that md5 file again, but still, your md5 is good to go :)

      Best regards

    • Richard April 8, 2017 at 9:06 PM #

      Hi Jorge,

      Thanks for the note. The downloaded .md5 file had the correct MD5 checksum, but the download .tgz file did not. Today that finally changed, so whatever prevented the server from providing the correct file before has either been flushed out or it expired (in case of caching). Yay.

      Going to install 8.7.6 shortly, after making a backup.

      Thanks for your help!

      – Richard.

  3. ZAXI April 9, 2017 at 11:34 AM #

    Hi,
    Is there any “how to” to upgrade from zimbra 8.7.1 to 8.7.6?
    Regards.

    • Jorge de la Cruz
      Jorge de la Cruz April 9, 2017 at 7:56 PM #

      Hi ZAXI,
      Not at the moment, but as usual:
      1.- Make a backup, or snapshot, or both better
      2.- Download ZCS 8.7.6 package
      3.- Extract ZCS 8.7.6 package and move to the folder
      4.- Run the script ./install.sh and follow all the steps, you can ommit the DB check if you want in order to save time, but better you actually run it
      5.- If all went good, you are now in 8.7.6

      Let us know

    • Jorge de la Cruz
      Jorge de la Cruz April 9, 2017 at 7:56 PM #

      Hi ZAXI,
      Not at the moment, but as usual:
      1.- Make a backup, or snapshot, or both better
      2.- Download ZCS 8.7.6 package
      3.- Extract ZCS 8.7.6 package and move to the folder
      4.- Run the script ./install.sh and follow all the steps, you can omit the DB check if you want in order to save time, but better you actually run it
      5.- If all went good, you are now in 8.7.6

      Let us know

  4. Dennis April 11, 2017 at 10:11 AM #

    Hi Jorge,

    what was the reason for the new build?


    we have uploaded a new build

    Any critical issues for people who are using the package before?

Leave a Reply