Zimbra Desktop 7.3.0 is Now Available — Based on Nw.js with Support for Linux 64-bits and More!

Zimbra Desktop gives you access to all of your email accounts in one place, whether you are online or offline! What is Zimbra Desktop? It is a free and open source email client application available for Windows, Mac and Linux.

Introducing Zimbra Desktop 7.3.0.


What’s new in Zimbra Desktop 7.3.0

Zimbra Desktop 7.3.0 replaces the Prism framework with Nw.js for all platforms as a main feature, but there’s more!

What’s New
106372 Replace Prism framework with Nw.js for all platforms
96507 New auto-update framework for Windows and Mac OS X
65456 Support 64-bit ZD builds for linux
105422 Spell check while composing new email not working in 7.3
104738 Support for Indonesian Language
105047 Windows: Make Zimbra Desktop default email application (mailto protocol)

Fixed issues in Zimbra Desktop 7.3.0

Zimbra Desktop 7.3.0 includes a long list of fixed issues which you can find here. Here are the highlights:

Fixed Issues

100636 Installation of ZD in silent mode fails on windows OS (Java not found error)
106135 Date format for “Sync messages to fixed date” on add new account page is incorrect and causes problem
106989 Need administrator privileges for running auto update on Zimbra Desktop(Windows 7, Windows 10)
107007 Windows: zdesktop.exe(jetty) process does not get killed immediately when ZD is closed from system tray
106001 ZD UI process(NW) crashes on accessing a shared briefcase folder
106241 Update registry keys in Windows OS when “mailto” handler is set/unset in ZD.
106478 ZD installation failing with openjdk version “1.8.0_91”
64657 Unable to paste an image inline
106992 When Java is not found by ZD installer, it should clarify that “Oracle” Java was not found
107154 Show original option is not working for calendar appointment
96770 Remove prism related code while changing locale
99763 Thai locale not displaying correctly (only on Mac)
106985 Zimbra Desktop on Mac OS X cannot read Thai language
106100 Support older themes in Zimbra Desktop
46088 The ‘From’ column is named ‘step 3.’
104571 INTL – Note for standard message on shared folders not showing when language is set to other than English
38619 Need mechanism to turn off or remind later for auto updates in ZDC
99919 Advanced Date search do not work for Thai, Korea, Chinese, Hongkong, Turkey

HTML Rendering bugs

79801 Email message display is truncated, but reply shows full content
100397 image/page not displayed correctly in attachment message
101880 Unable to view the complete email
93616 Message chopped off at bottom so can’t read it properly
104444 HTML rendering issues
107277 An email with an image content missing in ZD.
99512 Responsive HTML email fails to render

Zimbra Desktop is now Linux 64-bit compatible

As we mentioned in the What’s New section, one of the most requested features from our Zimbra Desktop customers was to natively support Linux in 64-bits. With the 7.3.0 version, we are thrilled to announce you can now install Zimbra Desktop in any Linux based in 64-bit.

Please follow the steps from our wiki to install Zimbra Desktop in Linux 64-bits:

As usual, your feedback is really important for us, so please don’t hesitate to let us know here, on our dedicated Forum about Zimbra Desktop what do you think, improvements, bugs, etc.

, , , , , ,

20 Responses to Zimbra Desktop 7.3.0 is Now Available — Based on Nw.js with Support for Linux 64-bits and More!

  1. Ajay May 3, 2017 at 9:36 AM #

    Hello Jorge,

    When we are likely to get support of IDN hosting and EAI in Zimbra community edition.
    Please confirm.


  2. Tim Pearson May 9, 2017 at 5:38 PM #

    With the 64 bit version (and maybe the 32 as well) – closing ZD will completely terminate the program rather than just minimizing it to the system tray. Is there a way to fix this? I’m seeing it on all 64 bit 7.3 installs.

    • Jorge de la Cruz May 9, 2017 at 6:49 PM #

      Hi Tim,
      We are closing the whole app, as expected in other tabs. We received feedback, and even Customers tickets saying they were expecting to close both (ui and server) as you know ZD it’s based in two pieces. So we’ve implemented it that way. How many users do you have running ZD which are being affected by this?

      Best regards

  3. Robert Oteri May 9, 2017 at 8:48 PM #

    After upgrading to 7.3 the entire Application and Server shut down when closing ZD. The icon in the tray disappears and the application/server must be restarted. Checking Task Manager also reveals both portions of ZD closed. This is effecting 100+ users on 32bit installs. Very, very undesirable behavior.

    • Jorge de la Cruz May 10, 2017 at 8:33 AM #

      Hi Robert,
      As mentioned early it was a expected behavior as other Windows apps act the same. I’m going to create a bug about it, and consider to add a setting you can edit in Preferences to have both experiences.

      Best regards and thank you for using Zimbra Desktop

    • Jorge de la Cruz May 10, 2017 at 10:22 AM #

      Robert, please find the ticket here – https://bugzilla.zimbra.com/show_bug.cgi?id=107941 We are currently working on improvements like this and others for a future release of ZD 7.3.1, it shouldn’t take long.

      thank you

    • Robert Oteri May 15, 2017 at 5:49 PM #


      Thanks for the link. I eventually found it on my own, after creating a support case (I closed the case). For those of us that have used ZD since the beginning, this behavior change is huge. I tried the ‘workaround’ in the mentioned in Bug Report, but it didn’t change anything. Rolling back to 7.2.8 regardless, as this change has had a negative impact on our environment.

      Another negative has come up because of this. There is no way to prevent ZD from checking for updates. At least there is no GUI way to do it. Now I have to teach my users the unhealthy habit of ignoring an update prompt. #TheStruggleIsReal

  4. Stefan May 12, 2017 at 9:37 AM #


    I know of the workaround, I did the changes in the config file, but after clicking x and opening Zimbra again from the tray icon, the window loses it’s dimensions, from full screen before the x clicking to windowed mode, and it’s annoying. I use Zimbra just because of the tray functionality. I downgraded to 7.2.8. until the bug is resolved(but now every 1-2 days the update window appears…)

    If they add the option to also run into tray-mode(as the newly submitted bug says it will), if they base their fix into the changing of the config file, the window-mode bug will appear…so they have to make a fix to the fix :)

  5. Störm May 18, 2017 at 2:38 PM #

    Hey Jorge, will Zimbra Desktop theme be updated at least, or even better the Universal UI provided for Zimbra Desktop users too?
    ZD is currently languishing and looking decrepit – with not even the Serenity theme available! :s
    Many thanks for the improvements

  6. Miguel Ordonez May 18, 2017 at 3:10 PM #

    Hi Excelent!

  7. Eliz May 23, 2017 at 5:55 PM #

    My colleague, who uses at Macbook, upgraded her Zimbra Desktop a couple of weeks ago and now attachments won’t open; she’s required to save them, which is extra steps and annoying. We’ve looked under Preferences and can’t find a setting to change.

  8. Valery June 6, 2017 at 7:43 AM #

    In ZD 7.3.0 I cannot open attachment but only save it. There is no dialog asking what to do “save or open” like in 7.2.8 version. Is it made for security purposes ?

    • Jorge de la Cruz June 6, 2017 at 10:18 AM #

      Hi Valery,
      It’s an expected behavior as per the new NW.js, we are working to improve this workflow in future releases.

      Best regards

  9. Valery June 9, 2017 at 11:28 AM #

    > It’s an expected behavior as per the new NW.js, we are working to improve this workflow in future releases.
    Hi Jorge ! May be it will be useful. I found that there is no problem to open attachments in pdf format. Works fine. Problems with files in format of: docx, xlsx, jpeg, tiff.

  10. Alessandro July 6, 2017 at 11:12 AM #

    For the attachment there is a bug: https://bugzilla.zimbra.com/show_bug.cgi?id=107952
    but there aren’t news about it.
    Temporary i want to downgrade to 7.2 version, can someone explain the correct procedure? I can simply remove the 7.3 and reinstall 7.2? I have to resyncronize all the emails or not?

    • Jorge de la Cruz July 6, 2017 at 1:08 PM #

      Hi Alessandro,
      Good news are we have been finished the development to fix this, and we are aiming August 3rd for a GA date.

      Best regards

  11. Jay July 23, 2017 at 12:10 AM #

    Is Zimbra desktop still open source? I ask because every time I click on the download link I get nothing but a big runaround.

    • Jorge de la Cruz July 23, 2017 at 2:37 PM #

      Hi Jay,
      Yes, Zimbra Desktop is Open Source, what are the issues you are facing to download the product?

      Best regards

  12. RD August 28, 2017 at 12:12 PM #

    Followed the instructions for Debian/Ubuntu (installed as root then the last command as the user)
    got it to work (7.3.3) on Debian 8.9, but had to do this:

    It was complaining that zdrun.pl.tmp doesnt exist, so I created it:
    cp /opt/zimbra/zdesktop/linux/zdrun.pl /opt/zimbra/zdesktop/linux/zdrun.pl.tmp

    Then there were some access rights issues so:
    chmod -R g+wrx /opt/zimbra/zdesktop/
    chgrp -R “user” /opt/zimbra/zdesktop/linux/zdrun.pl

    Then error: preserving times for ‘/opt/zimbra/zdesktop/linux/node-webkit/package.json’: Operation not permitted
    comment out the exit1…..node-webkit… line in

    then launch /opt/zimbra/zdesktop/linux/zdrun.pl
    press CTRL+Z and bg to run in the background

    Not sure what the exit1 line does other than exiting with status 1 if that condition is met, but it seems to work fine so far.

  13. Patur September 14, 2017 at 12:47 PM #

    How to Fixing Zimbra 7.3.1

    Problem accessing /zimbra/desktop/console.jsp. Reason:

    Caused by:

    java.lang.UnsupportedClassVersionError: com/zimbra/cs/taglib/tag/i18n/GetLocaleRequestTag
    at org.apache.jsp.desktop.console_jsp._jspx_meth_fmt_getLocaleRequest_0(Unknown Source)
    at org.apache.jsp.desktop.console_jsp._jspService(Unknown Source)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:109)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:814)
    at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:389)
    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:486)
    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:380)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:814)
    at com.zimbra.webClient.servlet.JspServlet.service(JspServlet.java:64)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
    at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(SetHeaderFilter.java:79)
    at com.zimbra.webClient.filters.SetHeaderFilter.doFilter(SetHeaderFilter.java:239)
    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
    at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
    at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:218)
    at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
    at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
    at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:422)
    at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
    at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230)
    at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
    at org.mortbay.jetty.Server.handle(Server.java:326)
    at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:585)
    at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:971)
    at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
    at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
    at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:415)
    at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:429)
    at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)

Copyright © 2022 Zimbra, Inc. All rights reserved.

All information contained in this blog is intended for informational purposes only. Synacor, Inc. is not responsible or liable in any manner for the use or misuse of any technical content provided herein. No specific or implied warranty is provided in association with the information or application of the information provided herein, including, but not limited to, use, misuse or distribution of such information by any user. The user assumes any and all risk pertaining to the use or distribution in any form of any subject matter contained in this blog.

Legal Information | Privacy Policy | Do Not Sell My Personal Information | CCPA Disclosures