Fixed issues ZCS 8.7.7
Here is a list of all the items addressed in this Release.
|
Fixed Issues
|
|
|---|---|
| 107823 | ZCO fails to parse GetContactResponse with SMIME feature |
| 107824 | All context menu options stopped working after deleting trashed appointment and trying to take action from user calendar’s appointment |
| 107825 | Weekly Recurring Meeting not getting synced in Outlook 2016 |
| 107826 | Implement GetStreamingEvents EWS API(Phase 1) |
| 107827 | SMIME: Send Flag to Server in GetContactRequest API when SMIME is enabled |
| 106438 | Caldav Shared Calendar Sync not working correctly on latest mac versions |
| 104522 | Messages sent are stored as Unread in Sent Folder on Mail app |
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.6 and above, we have new steps to download and see our code:
Hello Jorge,
Using the RHEL7_64 version of the Open Source variant, the installation step for the Common Zimlets consistently fails when upgrading 8.7.5 to 8.7.7 (or 8.7.6). Errors are all of the following type:
Fri Apr 14 15:28:08 2017 Installing common zimlets…
Fri Apr 14 15:28:08 2017 com_zimbra_attachmail…
Fri Apr 14 15:28:08 2017 *** Running as zimbra user: /opt/zimbra/bin/zmzimletctl -l deploy zimlets/com_zimbra_attachmail.zip
[] INFO: Deploying Zimlet com_zimbra_attachmail in LDAP.
[] INFO: Installing Zimlet com_zimbra_attachmail on this host.
[] ERROR: Zimlet com_zimbra_attachmail has an invalid file path com_zimbra_attachmail_zh_HK.properties
com.zimbra.cs.zimlet.ZimletException: Cannot deploy Zimlet com_zimbra_attachmail. Error message: Invalid file path com_zimbra_attachmail_zh_HK.properties
at com.zimbra.cs.zimlet.ZimletException.CANNOT_DEPLOY(ZimletException.java:68)
at com.zimbra.cs.zimlet.ZimletUtil.installZimletLocally(ZimletUtil.java:692)
at com.zimbra.cs.zimlet.ZimletUtil.deployZimletLocally(ZimletUtil.java:618)
at com.zimbra.cs.zimlet.ZimletUtil.dispatch(ZimletUtil.java:1905)
at com.zimbra.cs.zimlet.ZimletUtil.main(ZimletUtil.java:2007)
[] ERROR: Error
com.zimbra.cs.zimlet.ZimletException: Cannot deploy Zimlet com_zimbra_attachmail. Error message: Invalid file path com_zimbra_attachmail_zh_HK.properties
at com.zimbra.cs.zimlet.ZimletException.CANNOT_DEPLOY(ZimletException.java:68)
at com.zimbra.cs.zimlet.ZimletUtil.installZimletLocally(ZimletUtil.java:692)
at com.zimbra.cs.zimlet.ZimletUtil.deployZimletLocally(ZimletUtil.java:618)
at com.zimbra.cs.zimlet.ZimletUtil.dispatch(ZimletUtil.java:1905)
at com.zimbra.cs.zimlet.ZimletUtil.main(ZimletUtil.java:2007)
Fri Apr 14 15:28:11 2017 failed. This may impact system functionality.
Fri Apr 14 15:28:11 2017 com_zimbra_proxy_config…
Fri Apr 14 15:28:11 2017 *** Running as zimbra user: /opt/zimbra/bin/zmzimletctl -l deploy zimlets/com_zimbra_proxy_config.zip
[] INFO: Deploying Zimlet com_zimbra_proxy_config in LDAP.
[] INFO: Installing Zimlet com_zimbra_proxy_config on this host.
[] ERROR: Zimlet com_zimbra_proxy_config has an invalid file path com_zimbra_proxy_config.xml
com.zimbra.cs.zimlet.ZimletException: Cannot deploy Zimlet com_zimbra_proxy_config. Error message: Invalid file path com_zimbra_proxy_config.xml
at com.zimbra.cs.zimlet.ZimletException.CANNOT_DEPLOY(ZimletException.java:68)
at com.zimbra.cs.zimlet.ZimletUtil.installZimletLocally(ZimletUtil.java:692)
at com.zimbra.cs.zimlet.ZimletUtil.deployZimletLocally(ZimletUtil.java:618)
at com.zimbra.cs.zimlet.ZimletUtil.dispatch(ZimletUtil.java:1905)
at com.zimbra.cs.zimlet.ZimletUtil.main(ZimletUtil.java:2007)
[] ERROR: Error
com.zimbra.cs.zimlet.ZimletException: Cannot deploy Zimlet com_zimbra_proxy_config. Error message: Invalid file path com_zimbra_proxy_config.xml
at com.zimbra.cs.zimlet.ZimletException.CANNOT_DEPLOY(ZimletException.java:68)
at com.zimbra.cs.zimlet.ZimletUtil.installZimletLocally(ZimletUtil.java:692)
at com.zimbra.cs.zimlet.ZimletUtil.deployZimletLocally(ZimletUtil.java:618)
at com.zimbra.cs.zimlet.ZimletUtil.dispatch(ZimletUtil.java:1905)
at com.zimbra.cs.zimlet.ZimletUtil.main(ZimletUtil.java:2007)
Fri Apr 14 15:28:14 2017 failed. This may impact system functionality.
etc, etc…
I’m trying to figure out what might be causing this. Do you have any ideas?
Thanks,
– Richard.
Interesting…
Before restoring my backup I decided to run some experiments. One of them was to manually run the zmzimletctl -l deploy command shown in the log, which nicely reproduced the same error. No surprise there.
What did surprise me is that running this command from ZCS 8.7.7 using the com_zimbra_*.zip file from ZCS 8.7.5 (which had worked fine before) yields the identical error, complaining about the same file inside of the zip file being deployed. This seems to indicate the problem isn’t with the zip file itself but the code running the deploy command.
Time to crack open the source code ;-)
– Richard.
Hi Richard,
I will try to reproduce this error, but until Wednesday it will not be possible to me.
Try it on your end if possible and let us know.
Thanks
Hello Jorge,
I wanted to give you a quick update to let you know that it appears the error originates from changes made to the class com.zimbra.cs.zimlet.ZimletUtil. I’m looking to compare the source code change between 8.7.5 and 8.7.[67] next.
Have a good weekend!
– Richard.
Hello again,
I think I found the problem, and it explains why not a lot of other people are reporting this.
In ZCS 8.7.6 code was added to check for absolute paths in Zimlets. One of those checks as it exists in 8.7.7 has:
file = new File(zimlet, fname);
if(!file.getCanonicalPath().startsWith(LC.zimlet_directory.value())) {
ZimbraLog.zimlet.error(String.format(“Zimlet %s has an invalid file path %s”, zimletName, fname));
throw ZimletException.CANNOT_DEPLOY(zimletName, “Invalid file path ” + fname, null);
}
On my system, /opt is a symbolic link to subdirectory another volume for storage purposes. This has never been a problem for all the Zimbra releases I’ve ran so far, starting back at 4.5.0 :-)
Unfortunately the line:
if(!file.getCanonicalPath().startsWith(LC.zimlet_directory.value())) {
cannot deal with this concept, as it compares the location of the file (which resolves to the name on the actual volume) against the desired zimlet directory based on the ‘/opt/zimbra’ path. The two don’t match, and an exception is thrown.
Very easily solved by using getCanonicalPath() on the zimlet_directory value as well. Something like:
String zimletDirPath = new File(LC.zimlet_directory.value()).getCanonicalPath();
if(!file.getCanonicalPath().startsWith(zimletDirPath))
(For optimization purposes you’d define zimletDirPath just prior to the for() loop that iterates through the ZimleFile entries.)
Should I submit a ticket for this or would you like to?
All the best,
– Richard.
Hi Richard
yes I suggest you to open a ticket.. so everyone can benefit from the fix!
Wonderful news. I will update 8.7.7…
I have exactly same ptoblem with zimlets
[zimbra@mx zimlets]$ zmzimletctl install $PWD/com_zextras_chat_open.zip
[] INFO: Installing Zimlet com_zextras_chat_open on this host.
[] ERROR: Zimlet com_zextras_chat_open has an invalid file path com_zextras_chat_open_de.properties
com.zimbra.cs.zimlet.ZimletException: Cannot deploy Zimlet com_zextras_chat_open. Error message: Invalid file path com_zextras_chat_open_de.properties
at com.zimbra.cs.zimlet.ZimletException.CANNOT_DEPLOY(ZimletException.java:68)
at com.zimbra.cs.zimlet.ZimletUtil.installZimletLocally(ZimletUtil.java:692)
at com.zimbra.cs.zimlet.ZimletUtil.dispatch(ZimletUtil.java:1915)
at com.zimbra.cs.zimlet.ZimletUtil.main(ZimletUtil.java:2007)
[] ERROR: Error
com.zimbra.cs.zimlet.ZimletException: Cannot deploy Zimlet com_zextras_chat_open. Error message: Invalid file path com_zextras_chat_open_de.properties
at com.zimbra.cs.zimlet.ZimletException.CANNOT_DEPLOY(ZimletException.java:68)
at com.zimbra.cs.zimlet.ZimletUtil.installZimletLocally(ZimletUtil.java:692)
at com.zimbra.cs.zimlet.ZimletUtil.dispatch(ZimletUtil.java:1915)
at com.zimbra.cs.zimlet.ZimletUtil.main(ZimletUtil.java:2007)
[zimbra@mx zimlets]$ cat /etc/redhat-release
CentOS Linux release 7.3.1611 (Core)
[zimbra@mx zimlets]$ uname -a
Linux mx 3.10.0-327.28.3.el7.x86_64 #1 SMP Thu Aug 18 19:05:49 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
And i have /opt/zimbra linked to another disk
[zimbra@mx zimlets]$ ll /opt/zimbra
lrwxrwxrwx. 1 root root 13 Jul 6 2016 /opt/zimbra -> /store/zimbra
Greetings,
The bug was submitted as:
Bug 107908 – Installation of / upgrade to ZCS 8.7.6 or 8.7.7 fails with Zimlet errors if /opt/zimbra contains symlink
https://bugzilla.zimbra.com/show_bug.cgi?id=107908
Cheers,
– Richard.
Hello,
Can someone confirm, if I can host my IDN domains and Zimbra will support EAI mailbox.
Thanks.
No Currently you can not host IDN domains and we currently dont support EAI mailbox.
Hello
No currently there is no provision for IDN domains or EAI mailbox. Zimbra do not support Email Address Internationalization (EAI) since EAI is the protocol that allows email addresses with IDNs in the domain part and/or Unicode (non-ASCII) characters in the Mailbox name to function within the traditional email environment and Zimbra Email software and services need to make specific changes to support EAI which is currently not in road-map. currently Zimbra systems do not recognize non-ASCII format (Internationalized Domain Names, or IDNs)
Tengo Zimbra 8.7.1 Open Source. Cuál es el procedimiento para actualizar a 8.7.7? Gracias! Saludos.
https://wiki.zimbra.com/wiki/Zimbra_Releases/8.7.7
then
https://wiki.zimbra.com/wiki/Zimbra_Releases/8.7.0/Upgrade
So what happened to the “Every 2 weeks” maintenance releases?
Hello,
Is it possible to migrate FROM ‘Xextras ZxChat’ TO ‘Zimbra Chat’ ? Retaining the Contact lists and Chat history…
Thanks,
Hi Daniel,
Not at the moment.
Best regards