Hello Zimbra Friends, Customers & Partners,
Zimbra 9.0.0 Kepler Patch 29 and 8.8.15 James Prescott Joule Patch 36 are here.
This patch fixes 2 issues that where introduced with Kepler 9.0.0-Patch-28 & 8815 Joule-Patch-35 Patch.
- In the previous patch ClamAV was upgraded to the latest upstream version, unfortunately this broke attachment scanning, this new patch restores the attachment scanning functionality. Should you have disabled attachment scanning you can re-enable it by running:
zmprov ms `zmhostname` zimbraAttachmentsScanEnabled TRUE zmcontrol restart
- In the previous patch spell and convertd services failed to start on mailstore nodes in a multi node setup. This has been fixed by recompiling Apache with existing PCRE library.
Please refer to the release notes for the patch installation on Red Hat and Ubuntu platforms.
Release Notes:
Please refer Zimbra Releases for latest releases and Zimbra Security Center for security updates.
Thanks,
Your Zimbra Team
Hi Barry
this is not clear to me . Did patch 35 100% brake attachment scanning? Or is that limited to only some users in specific cases?
Thanks
I think it is not enabled by default, so in that case you would not have noticed the difference. In any case the latest patch fixes the regression so you can enable it now.
Hi
I can confirm that this patch solves the attach scanning problema.
Release 9.0.0.GA.3924. Patch 9.0.0_P29
Regards.
Hello,
We are experiencing an error when users are trying to send emails via Persona. The error message is like in a thread post on the forum.
https://forums.zimbra.org/viewtopic.php?f=15&t=67503&p=307877#p307877
Thank you
Hello,
What is your version and patchlevel?
You can try and install: https://github.com/Zimbra-Community/shared-mailbox-toolkit
Then create 2 new user accounts and share the userB account with userA using maximum permissions as in the screenshot. Then send and email with the userA account as the userB, and send this email to a third user. If the error does not come, it means some permissions are not set correctly on the accounts that have the issue.
If it also does not work with the new accounts, it is a different issue.